Siebel EIM

How are index hints used in an EIM process

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. Since optimization modes used by Siebel application differ among database platforms, index hints usages by EIM are different.

There are two EIM parameters related to index hints:

 USE ESSENTIAL INDEX HINTS (TRUE by default)
USE INDEX HINTS (FALSE by default)

How should EXPORT MATCHES and DELETE MATCHES be used in Siebel?

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:

 

If the interface table's target table is not S_PARTY:

- It allows syntax of:

How can users generate an Enterprise Integration Manager Log file in Siebel

In Siebel application, follow the steps below to generate an Enterprise Integration Manager (EIM) detailed log file:

1. From User Interface, navigate to View > Site Map > Server Administration > Components


2. Select Enterprise Integration Manager as the component and choose the tab 'Component Event Configuration'.
 

3. Find the following 'Event Type':

SQL Tracing
SQL Summary
Task Configuration
Component Tracing.

Why is the Primary ID not populated during an EIM task even though the corresponding EIM mapping columns are appropriately populated in the Interface table

When encountering  the Primary ID not populated during an EIM task even though the corresponding EIM mapping columns are appropriately populated in the Interface table issue modify the IFB file to include the PRIMARY KEYS ONLY = TRUE parameter. This will force EIM to update only the primary key values like PR_POSTN_ID, PR_EMP_ID etc.

What values must be populated for PARTY_TYPE_CD, PARTY_UID and ROOT_PARTY_FLG columns in S_PARTY table using EIM

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). The following are the description of these columns and the possible values it can hold:

 

PARTY_TYPE_CD:

PARTY_TYPE_CD is used to indicate what type of party data is being imported. It can have the following values: