Data Mapping for ASI Release Independence

Within data synchronization, a data map translates the data in the form of integration objects between an internal integration object and an interface integration object, making ASIs release-independent.

Data synchronization services use data mapping to translate data between integration objects and support a subset of methods that are used by the EAI Siebel adapter, such as Insert, Update, and Delete. See Data Synchronization Methods for ASIs for more information. An ASI usually requires two types of data maps—one for each direction, as shown in the following image. For more information about data mapping, see Business Processes and Rules: Siebel Enterprise Application Integration.

Mapping Between Integration Objects. In this image, there is an Internal Interface Object between Siebel Application and the Input Data Map/Output Data Map, and an External Interface Object between Input Data Map/Output Data Map and the External Application.

For ASIs using data synchronization services, there are two types of data mapping—implicit data mapping and explicit data mapping.