The syntax of EXPORT MATCHES and DELETE MATCHES has been changed in version 7.x./8.x This information was not available in the Siebel Bookshelf.The following are the correct syntax for the EXPORT MATCHES and DELETE MATCHES parameters:
All the addresses are now being stored in the S_ADDR_PER base table instead of S_ADDR_ORG base table. This was done because of the data model changed for version 7 and the S_ADDR_ORG will be obsolete.
PARTY_TYPE_CD, PARTY_UID, ROOT_PARTY_FLG are the required columns in S_PARTY table which have to populated while doing an import of party records(like contact, position, etc.) using Enterprise Integration Manager (EIM).
S_REVN table was introduced in Siebel version 7.0 which is used to store Revenue data. For example Revenue by an employee on an Opportunity, an Agreement, a Service Request, etc.
Enterprise Integration Manager (EIM) interacts with data objects (tables and columns) via SQL statements. How those queries are executed by the database in use is directly related to the EIM performance.
If you are using EIM interface tables, you can explicitly set primary addresses for accounts. If you are not using EIM interface tables, you can still set primary addresses using IF interface tables.
Complete the following procedure: To populate the PR_PROD_LN_ID column in the S_PROD_INT base tablePopulate the S_PROD_INT base table using the EIM_PROD_INT interface table.
You can only use EIM to import bulk data from legacy systems into the Siebel database. Only ACT! 2.0 and ACT! 3.0 have File/Import functionality for data import into Siebel. You can use “Exporter for ACT!” to export ACT!
EIM will not interfere with Siebel VB code because Siebel VB works at the business component and business object level, and EIM works at the table level.
Each interface table imports data into one or more target base tables.For example, EIM_ACCOUNT imports into S_ORG_EXT, S_ACCNT_POSTN, S_ADDR_ORG, S_ORG_INDUST, S_ORG_PROD, S_ORG_REL, S_ORG_SYN, S_ORG_TYPE, S_TERR, and S_TERR_ITEM.