EIM does not evaluate the logic from the BC Layer (or above); it only evaluates the data layer, tables, columns and their properties. The LOV Type on the table level and BC level should thus be always consistent.
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.
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! 4.0 or 2000 Contacts, Notes/History, Activity, Group, Sales and E-Mail data into commadelimited files. For information on ACT! products, visit their website at http://www.actaddons.com.
Several columns are mandatory. Others are conditionally mandatory, depending on the conditions of your import. Your Siebel application offers two methods for determining mandatory columns. You can use Siebel Tools to view each column in an interface table and its target base table columns. You can also refer to Siebel Interface Tables Reference. By adhering to Siebel’s recommended import sequence, you make sure that the appropriate data dependencies are established.
Yes, EIM supports various case values defined for base table columns in Siebel Tools. EIM will adjust the case value of an interface table column according to the Force Case property of the corresponding base table column.
The S_PARTY table is the parent of many Person or Organization related objects in Siebel. For example, S_CONTACT, S_ORG_EXT, S_POSTN, S_EMP_PER are all child objects of S_PARTY.
Relationship between two different PARTY objects, example: Account and Contact or Employees and Positions is stored in the intersection table S_PARTY_PER. For example, if an Account has three different contacts then there will be 3 records in the S_PARTY_PER table.
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):
EIM_ORDER
------------
BL_ACCNT_BI
BL_ACCNT_LOC
BL_ACCNT_NAME
BL_ADDR_NAME
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.
The following are benefits to this approach:
a) Allows updating information that tends to change (Name for example)
b) Allows greater control of the data manipulation (loading, updating, exporting etc) processes in an automated fashion.
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.
S_REVN table replaces S_OPTY_PROD and S_OPTY_POSTN table in Siebel version 6.0.
As of Siebel version 7.0, S_OPTY_PROD is obsolete and S_OPTY_POSTN is no longer used to store revenue records.
To define multiple Extended Parameters values, use a backslash before quote. Reference the example to see how to use this feature:
i:\sbsrvr\bin\srvrmgr.exe /g gateway /e entServer /s SIEBDEVSRVR /u sadmin /p passwd /c "START TASK FOR COMPONENT EIM WITH CONFIG=htcontacts_tpl2.ifb, ExtendedParams=\"BatchNum1=200001,BatchNum2=200002-200003\", CONNECT=SiebSrvr_CRMSIEBDEV, ERRORFLAGS=1, TRACEFLAGS=0, SQLFLAGS=0"