Updating the Siebel Database

After you have completed the initial import of enterprise data, you can periodically use EIM to update the Siebel database. For example, if you add a new product line, it may be efficient to load the data into your enterprise inventory management database and then import it into the Siebel database. Use the steps described in Import Data Process Flow, although the scope of the update import is usually significantly smaller than that of an initial data import.

Caution: If you have active mobile Web clients, do not disable the Enable Transaction Logging system preference in the Administration - Siebel Remote screen. If you disable this system preference, the server database and mobile Web client databases will not be synchronized after the import.

By default, when importing information, EIM performs both inserts and updates based on the content of the batch set. EIM first examines the set of information to determine which rows in the batch already exist in the Siebel database:

• Batch rows matching existing base rows are used to update the database.

• Batch rows that do not match base rows are used to perform inserts.

See INSERT ROWS and UPDATE ROWS Parameters for further information.

In some circumstances, you may need to suppress inserts and updates. For more information on adjusting parameters to suppress an insert or update, see Suppressing Data When Updating Existing Databases.

Note: You can use EIM to update only non-user key columns; EIM does not support modification of existing user key columns. To update user key columns in S_ORG_EXT, S_PROD_INT, S_PROD_EXT, S_PARTY tables use EIM_ORG_EXT_UK, EIM_PROD_INT_UK, EIM_PROD_EXT_UK, and EIM_PARTY_UK. The postfix UK denotes user key. For more information, see Fields That Cannot Be Updated.