Bookshelf v7.5: Parameters Used for Deletes in Both the Header and Process Sections

Table 14 provides descriptions of the parameters that can appear in the header and process sections of the EIM configuration file, and which are specific to delete processes.

Table 14. Delete Process Parameters for the EIM Configuration File - Header and Process Sections
Command	Description
CASCADE DELETE ONLY	(Default = FALSE). Set this parameter to TRUE to delete child records with nullable foreign keys when the parent record is deleted. If FALSE, then when EIM deletes a parent record, it sets the foreign keys of the child records to NULL.
CLEAR INTERFACE TABLE	This parameter specifies whether existing rows in the EIM table for the given batch number should be deleted. Valid values are true (the default unless DELETE EXACT = TRUE) and false (the default if DELETE EXACT = FALSE).
DELETE ALL ROWS	Used for deleting all rows in table; default is FALSE. Note: Use this parameter with caution. For more information on this parameter, see DELETE ALL ROWS Parameter.
DELETE EXACT	Delete using user key matching algorithm with rows in EIM table; default is FALSE. For more information on this parameter, see DELETE EXACT Parameter.
DELETE SKIP PRIMARY	This parameter specifies whether EIM should perform a cascade update to the primary child column. The default value is TRUE.
DELETE MATCHES	SQL WHERE fragment deletion criteria. Example: DELETE MATCHES = EIM_ACCOUNT, (NAME LIKE "TST_ACCT%").
DELETE ROWS	This parameter specifies whether rows from the target base table can be deleted. Valid values are TRUE (the default) and FALSE. This parameter can prevent deletions from one table while allowing them in others. For example, the following parameter setting prevents deletion of rows from the S_ADDR_ORG table: `DELETE ROWS=S_ADDR_ORG, FALSE` Note: Use the FALSE setting for DELETE ROWS carefully. Inappropriate use can result in dangling foreign key pointers.
IGNORE BASE COLUMNS	Specifies base table columns to be ignored by the import process. Use commas to separate column names, which can be qualified with base table names. Required and user key columns cannot be ignored. Use this parameter to improve performance when updating all but a few columns. The default is to not ignore any base table columns.
UPDATE ROWS	Specifies whether foreign key references can be updated. This parameter can be used to prevent the updating of foreign key references with a setting of FALSE. The default value is TRUE, which affects all tables. To affect only specific tables, you can specify a table name. For example: `UPDATE ROWS = S_CONTACT, TRUE` The UPDATE ROWS parameter also prevents updates in one table while allowing them in others. If this parameter is set to FALSE, EIM does not update rows in the specified base table. If you need to specify multiple tables, use one UPDATE ROWS statement for each table. Note: Use the FALSE setting for UPDATE ROWS carefully. Inappropriate use can result in dangling foreign key pointers.

NOTE: You must use one of the following delete parameters described in this section: DELETE EXACT, DELETE MATCHES, or DELETE ALL ROWS.

DELETE EXACT Parameter

This parameter specifies the base table rows to delete by using user key values specified in the EIM table. By default, delete exact = false. If DELETE EXACT is set to TRUE, you must use the ONLY BASE TABLES parameter in conjunction with this parameter to identify the base tables.

NOTE: Do not use ONLY BASE TABLES with the target base table and nontarget base tables, because the EIM table record cannot specify just one record to be deleted.

Although this parameter can be used to delete rows from both target and nontarget base tables, use the delete exact parameter to delete only nontarget base tables containing user keys. Rows in nontarget base tables that do not contain user keys will not be deleted. For example, you cannot use the DELETE EXACT parameter to update the S_ACTION_ARG table and the S_ESCL_ACTION table because there are no user keys defined for these tables.

As another example, you can use DELETE EXACT to delete any of the nontarget base tables such as S_ADDR_PER and S_ACCNT_POSTN using the EIM_ACCOUNT table. In this case, the EIM_ACCOUNT table would need to be loaded with records that would singularly identify the S_ACCNT_POSTN or the S_ADDR_PER record to be deleted.

To use the DELETE EXACT parameter to delete data from base tables other than the target base table, specify the user key columns only for a single base table for each row in the EIM table. When specifying rows for exact deletion, make sure any columns not necessary to specify the row to be deleted are NULL to avoid problems with deleting from the wrong base table. EIM tries to enforce this behavior by requiring other user key columns to be NULL. If a row cannot be identified as clearly referring to a row in a single base table, that row will fail to be deleted.

Deleting from Base Tables Other Than the Target Base Table explains how to delete data from base tables other than the target base table using the DELETE EXACT parameter with the following scenario as an example. In this example, EIM_ACCOUNT is mapped to base tables including S_ORG_EXT, S_ORG_PROD, and S_ORG_INDUST. You want to delete data only from S_ORG_PROD, and not delete data from S_ORG_EXT or any other base tables. See To delete data from base tables other than the target base table.

DELETE MATCHES Parameter

This parameter specifies a where clause expression for filtering base table rows. The value is in two parts: the Siebel base table name and the filter expression that goes against the target base table. An example would be:

DELETE MATCHES = S_ORG_EXT, (LAST_UPD > '2000-06-22' AND LAST_UPD < '2000-06-23')

The expression is a self-contained where clause expression (without the where) and should use only literal values or column names (optionally prefixed with the base table name). There must also be a space separating the operator from the operand in this expression (a space must be added between > and '). When deleting rows for a specific date, you should use date ranges as shown in the example instead of setting the date equal to a specific date. By default, delete matches expressions are not used.

This parameter will only write the user keys values of the deleted target table rows to the EIM table columns. It will not write values of nonuser keys columns or nontarget table rows column values to the EIM table. The deleted rows cannot be reimported using the EIM table rows written by the EIM delete process, because they will not contain all the original information.

Only use this parameter to delete rows from target base tables. Rows will be deleted from the target base table even if the DELETE ROWS parameter is set to FALSE for that table.

CAUTION: Do not use the DELETE MATCHES parameter to delete rows from S_PARTY based tables. For example, using the criteria "DELETE MATCHES = S_PARTY, (CREATED > xxxxx)" will cause all records of S_PARTY that matches this criteria to be deleted from the database.

DELETE ALL ROWS Parameter

This parameter specifies that all rows in the target base table are to be deleted. Valid values are true and false (the default). Existing values in the EIM table and delete matches expressions are ignored.

CAUTION: Use the DELETE ALL ROWS = TRUE setting with extreme caution. It will delete all rows in the named base table including any seed data. Do not remove unnecessary seed data by deleting all rows from the S_LST_OF_VAL base table. If you do so, you will not be able to reimport "clean"data and you will be forced to rebuild the seed data or restore from backup. To selectively delete rows, use the DELETE EXACT or DELETE MATCHES expressions.