Siebel Connector for Siebel eBusiness Applications > Customizing the Connector > Integration Object Modification >

Adding ModId Fields


To improve performance, Siebel EAI Adapter and Incremental Snapshot use ModId fields to determine whether a specific record in a table has been modified. You must add ModId fields to Siebel Connector for Siebel eBusiness Applications integration objects to support Incremental Snapshot. To do this, modify the definition of integration components.

To add ModId fields to integration components

  1. In the "table" property of a buscomp definition, find the base table of the corresponding buscomp.
  2. Find the extension tables of this base table and identify the tables that require one additional field based on the criterion below.

    Criterion for the addition of one additional field: If the name of the extension table appears in the join property of any of the field definitions for the buscomp, but not in the list when you click on the Join icon in the Object Explorer.

  3. For each of the extension tables identified in Step 2, add one field to the integration component definition with a name of <Extension table name>.Mod Id.

    NOTE:  This is complex. The main reason to do this is to keep track of the modification numbers of each of base table and extension table for that buscomp. However, you do not need the modification number of the extension table if that table is explicitly joined. Any changes to explicitly joined tables will be recovered by Siebel Adapter when an upsert is called, as long as you keep the definition of the joined field in the buscomp.

  4. For each of the ModId fields (including ModId which is generated automatically by Integration Object Builder) in the integration component definition specify a user property called ModId. Set the value field to Y.
  5. Repeat Step 2 through Step 4 for each integration component defined in the integration object.

    NOTE:  If the integration component represents a Multi-Value Group (MVG), add a user property MVGFieldName or AssocFieldName, depending on whether the MVG is associated or not, and set the value to ModId.

    NOTE:  To find out whether an MVG has an association, go to the corresponding BusComp/Multi Value Link. Then go to the link definition by drilling down from the Destination Link field. If there is an Inter Table field specified, it is an association and the user property should be set to AssocFieldName = ModId. Otherwise, set the user property to MVGFieldName = Mod Id.

Siebel Connector for Siebel eBusiness Applications