Siebel Connector for Oracle Applications > Overview of Siebel Connector for Oracle Applications > Architecture >

Data Transformation Maps and Data Transformation Engine

After the internal and external integration objects are created, a Data Transformation Map is used to transform data contained in the two objects. During run-time, a data transformation map is passed to the Siebel Data Transformation Engine (DTE) along with an internal and an external integration object. The map defines the relationships of data elements between the two integration objects. The DTE transforms the data following the map definitions.

Depending on the direction of data transfer, the internal and external integration objects may serve as either the DTE input or output. For example, when information flows inbound from an Oracle to a Siebel application, the external integration object is the DTE input and the output goes to the internal integration object. The arrangement is reversed for an outbound data flow.

A data transformation map is provided for each integration point in the Siebel Connector for Oracle Applications' packaged integration. You may customize a map to meet your requirements or create a new one as part of a new integration point definition. Data transformation maps are defined two ways: by using the Business Service Editor to write an eScript or by using the Siebel Data Mapper.