Universal Remote Codes TV

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

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".

The Enterprise Integration Manager (EIM) is designed for importing large volumes of data. Most failures are caused by data errors. It is usually faster and easier to correct the data errors and resubmit the corrected rows as part of a subsequent batch than to reprocess an entire batch.

It is not possible to delete or merge these types of records through Enterprise Integration Manager (EIM).

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.

When importing data from _XMIF or some other Interface table users might encounter the following error message in the trace file:

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.

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.

Primary associations can be set using the Primary Flag; for example, in EIM_ACCOUNT there is an ACC_PR_POSTN column that is defaulted to “N”, but when set to “Y”, EIM will attempt to update the Primary Position in the relevant account in S_ORG_EXT.PR_POSTN_ID. 

In a typical data migration application using EIM, the IFB file contains a large number of sub-processes, which are called from the main process (SHELL). Often while running the EIM process, there are situations, when we would like to run only a sub set of these processes. Such situations normally arise in testing environments, when we prefer running only those processes for which testing needs to be performed.