Bookshelf Home | Contents | Index | Search | PDF

Siebel Enterprise Integration Manager Administration Guide > Introduction >

What's New

---

The following functionality is new in this release.

• S_PARTY table. S_PARTY table has been introduced into the Siebel Data Model in Siebel 7. The S_PARTY table is the target base table, while S_ORG_EXT, S_CONTACT, S_USER, and S_POSTN now become extension tables of the S_PARTY table. The S_EMPLOYEE table is obsolete in version Siebel 7. These schema changes have a direct effect on EIM behavior.

  S_ORG_BU table. With multi-org, each account can belong to one or more organizations. S_ORG_BU is the intersection table that holds the many-to-many relationship between the organizations and the accounts.For Siebel Industry Applications (SIA) version 7.5.x, there is no mapping in the EIM_ACCNT_CUT interface table to the S_ORG_BU table. However EIM_ACCOUNT and EIM_ORG_BU interface tables are mapped to S_ORG_BU. EIM_ACCOUNT or EIM_ORG_BU can be used to populate S_ORG_BU.

• MISC SQL parameter. Siebel 7 introduces a new parameter, MISC SQL. This is used to set certain primary child foreign keys, such as S_CONTACT.PR_OU_ADDR_ID and S_POSTN.PR_EMP_ID. When using MISC SQL in Siebel 7 to set primary child foreign keys, EIM does NOT log any transactions for mobile users. This parameter should only be used for initial data loading. For more information, see Parameters Used for Imports in Both the Header and Process Sections.
• DELETE SKIP PRIMARY parameter. This new parameter controls whether EIM performs a cascade update to the primary child column. The default value is TRUE. For more information, see Parameters Used for Deletes in Both the Header and Process Sections.
• SKIP BU_ID DEFAULT parameter. SKIP BU_ID DEFAULT specifies whether the virtual null key is to be skipped for the BU_ID column. This parameter applies to import, delete, and merge processes because the foreign key must be resolved before these processes can run. For more information, see Process Section Parameters Generic to All EIM Processes.
• UTLEIMDIFF.EXE Utility. The Siebel Data Model changes from release to release and EIM mappings change accordingly. You can use the UTLEIMDIFF utility to find EIM mapping differences between two repositories for a list of EIM tables that you input. The results can be used to help you update your EIM data loading scripts, programs, and so on. For more information, see Finding Differences in EIM Tables between Repositories.
• EIM Table Mapping Wizard. Siebel Tools includes an EIM Table Mapping wizard to assist in adding mappings to extensions to the data model:
  • Add new customer columns to existing Siebel tables.
  • Add new extension tables.
  • Add new intersection tables.
• EIM_PROD_INT_UK. EIM_PROD_INT_UK in Siebel 7 can be used to update user key columns in S_PROD_INT, such as NAME and VENDR_OU_ID. INTEGRATION_ID is an alternative user key in S_PROD_INT. The EIM engine uses this new user key to update traditional user key columns.
• LOG TRANSACTIONS TO FILE. Siebel 7 introduces a new parameter, LOG TRANSACTIONS TO FILE. EIM now logs transactions into DX files stored in the File_System\EIM directory. A marker transaction is created in the S_DOCK_TXN_LOG table. For more information, see Header Section Parameters Generic to All EIM Processes.
• DELETE MATCHES and EXPORT MATCHES behavior changed. The behavior of these parameters has changed as part of the new S_PARTY model. These parameters can now affect extension tables. These parameters also have a new argument. For more information on DELETE MATCHES, see Parameters Used for Deletes in Both the Header and Process Sections, and for more information on EXPORT MATCHES, see Parameters Used for Exports in Both the Header and Process Sections.
• Deleting records from S_NOTE* and S_*_SKILL_IT tables. Previously you could not delete from the S_NOTE* and S_*_SKILL_IT tables because they did not have a primary user key. Now you can delete records from S_NOTE* and S_*_SKILL_IT tables without deleting records from the parent tables using EIM_NOTE_DEL and EIM_SKLI_DEL, respectively.
• Improved Delete and Merge performance. Delete and Merge performance is improved if you create some specific temporary indexes first. For more information, see Additional Indexes on EIM Tables.
• Oracle INSERT APPEND MODE parameter. This new parameter helps avoid deadlocks when running parallel EIM processes. For more information, see Process Section Parameters Used for Imports.
• ATTACHMENT DIRECTORY parameter. Specifies the directory to be used for importing attachments. For more information, see Parameters Used for Imports in Both the Header and Process Sections.
• CASCADE DELETE ONLY parameter. This new parameter determines how child records are handled when the parent record is deleted. For more information, see Parameters Used for Deletes in Both the Header and Process Sections.
• EIM SCHEMA CACHE parameter. This caches the column relations. For more information, see Parameters Used for Deletes in Both the Header and Process Sections.
• DUP_RECORD_IN_EIM_TBL status value. This new IF_ROW_STAT value was added to indicate that the row was eliminated because it is a duplicate (has the same user key) of another row in the EIM table (within the same batch). For more information, see Table 12 in Viewing a List of Imported Rows.
• PRIMARY KEYS ONLY parameter is no longer supported. You should no longer use this parameter in the EIM configuration file.

Bookshelf Home | Contents | Index | Search | PDF