Explicit Data Mapping for Integration Objects

You must define an explicit data map whenever a component or field name of an interface integration object does not exactly match the component or field name of the internal interface object.

Oracle provides prebuilt explicit data maps for its ASIs. These data maps make sure that the ASIs are release-independent.

Note: To preserve the release-independent properties of fields, do not alter Siebel-defined explicit data maps except when you deactivate fields.