Modification IDs
To determine which Mod Id fields must be used as part of a Modification Key, you expose Mod Id fields for tables whose columns might be updated by that integration object. In some situations you might have to add corresponding integration component fields as well as business component fields.
When using Modification IDs, the following behaviors are present:
All fields must be present in the integration object instance for the Mod Key to be used.
Only one defined Modification Key is present for each integration component. Unlike for User Keys, multiple Mod Keys are not allowed.
About the Modification ID for a Base Table
The integration component field Mod Id for a base table is created by the Integration Object Builder Wizard, but you must make sure it is active if it is needed for your business processes.
About the Modification ID for an Extension Table
An extension table’s Mod Id field is accessible as extension table name.Mod Id in the business component, for example, S_ORG_EXT_X.Mod Id. However, if your business processes require this field, then you must manually add it to the integration object definition by copying the Mod Id field and changing the properties.
About the Modification ID for a Joined Table
A joined table’s Mod Id field must be manually added in both business component and integration object definitions. Business component Mod Id fields for joined tables must:
-
Be prefixed with CX string and preferably followed by the name of the join
-
Be Joined over the correct join
-
Have MODIFICATION_NUM specified as underlying column of type DTYPE_INTEGER