Siebel EIM

How are CREATED and CREATED_BY columns populated using EIM?

In standard Siebel applications, ‘CREATED’ and ‘CREATED_BY’ are system columns that will be automatically populated when importing data via EIM. The starting time of the EIM server task and login information of the employee starting the EIM server task populates these columns. There is no EIM mapping from the Siebel Interface tables to the CREATED and CREATED_BY columns in any of the base tables.

How can users determine if there is an interface mapping to a particular table or column and which interface tables or columns can be used for importing to this base table or base column?

This information pertains to Siebel version 3.x, 4.x, 5.x, 6.x and 7.x.

In order to find this information, please follow the steps outlined below:

1. Launch the Siebel client with /h option and navigate to the view in the Graphical User Interface (GUI) that has the field.

2. Choose Help > About View

3. Note which applet the field belongs to

4. Launch the Siebel Tools client

5. Navigate to the Applet Object in the Object Explorer

Can the PRIV_FLG column of S_CONTACT base table be updated using EIM? (Private_Flag is used to enforce Personal Contacts)

No. The S_CONTACT.PRIV_FLG is not part of the user key to the S_CONTACT table. However, it is included in the criteria used by Enterprise Integration Manager (EIM) to locate an existing row in the S_CONTACT table (It is a required column, but not a part of user key). Currently it is not possible to update the S_CONTACT.PRIV_FLG using EIM. For contacts loaded using EIM, the only supported value for the PRIV_FLG is "N".

How can I tune my EIM batches to improve performance?

Here are some options that can be tried to improve Enterprise Integration Manager (EIM) performance:

Check to make sure all the standard indices are in existence for the tables involved.

Limit tables and columns to be processed using ONLY BASE TABLES/COLUMNS configuration parameters to minimize the work that EIM has to perform.

What are the various Enterprise Integration Manager Interface Table Keys and do they need to be populated

There are three types of keys present for Siebel interface tables. They are User Key, Required User Keys, and Non-Required User Keys. Before performing an Enterprise Integration Manager (EIM) process, it is very important to examine which columns are defined as User Key columns, which are Required User Keys. User keys cannot be updated using EIM. EIM can be used to update non-user key columns only based on user key columns.

 

Why is the SQL not traced in the EIM tasks log file despite setting SQL Trace Flags to 8?

This happens when the Enterprise Integration Manager (EIM) component's Component Event Configuration - SQL Tracing Event Type log level value is not set to 4.

Set the Component Event Configuration for the SQL Tracing Event Type to 4 in order to enable SQL tracing. For 7.0.x, the defaulted value is not 4, and need to be set explicitly.

 For version 7:

It has a default value of 1, which means it only writes events of "severity" level of Informational (1) or more severe.

How can file attachments be imported via EIM?

1. Put the file to be attached in the Siebel_Server\input directory (i.e. ABC.doc)

 

2. In the EIM_SR_DTL table, populate:

SR_SR_NUM

SR_BU

ATT_FILE_NAME ('ABC')

ATT_FILE_EXT ('DOC')

ATT_FILE_SRC_TYPE  ('FILE')

 

3. Run EIM to import file attachment to S_SR_ATT table.

 

4. A new .saf file will be generated in the file system after EIM loading.