Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Enterprise Integration Manager Administration Guide > EIM: Examples of Common Usage > EIM Import Process Examples > Example of Importing Primary KeysIn order to import a primary column, you must populate the following interface columns:
The intersection row must exist before setting the primary. If you want to import the intersection row and set it as the primary at the same time, you must also populate the interface columns that map to the intersection table's required columns. If you want to update the S_ORG_EXT.PR_POSTN_ID primary column with the EIM_ACCOUNT interface table, you must populate:
NOTE: You can find the S_ORG_EXT.PR_POSTN_ID primary's intersection table using Siebel Tools. In Table, query and select S_ORG_EXT > Column, then query and select PR_POSTN_ID > Primary Inter Table Name property value. The following are .IFB settings that you can use when running an EIM task that populates an EIM table to update a S_ORG_EXT row's PR_POSTN_ID primary position to reference the S_POSTN row: PASSWORD = "<SADMIN's password>" RUN PROCESS = Update S_ORG_EXT.PR_POSTN_ID [Update S_ORG_EXT.PR_POSTN_ID] ONLY BASE TABLES = S_PARTY, S_ORG_EXT, S_ACCNT_POSTN INSERT ROWS = S_ORG_EXT, FALSE ONLY BASE COLUMNS = S_PARTY.PARTY_UID, \ There are some cases that require you to include the MISC SQL parameter to set the primaries. For more information, see MISC SQL Parameter. |
![]() ![]() |
Siebel Enterprise Integration Manager Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |