Siebel EIM

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:

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.

1. Before using the utility, the user needs to create the view S_EIM_MAP_V in the database. The database platform independent script for creating the view is create_EIM_MAP_V.sql and can be found in <dbsrvr>\common directory.

To map a new table an EIM interface table using the EIM Table Mapping Wizard
1. Lock the project.
 2. Select Table object type in the Object Explorer.
 

MISC SQL parameter is introduced in Siebel 7 to allow EIM to set the following Primary Child Foreign Keys:

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.

To define multiple Extended Parameters values, use a backslash before quote. Reference the example to see how to use this feature:

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.

PARTY_UID requires users to populate it with a unique value. The PARTY_UID column is used by several users to store a unique legacy system identifier.

Integration Manager (EIM) reports the following low-severity error when the foreign key value in the base table does not match with value in the interface table (Note: The following example is based on Siebel version 7.0.4 data model):