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

Integration Objects

Integration objects are application-neutral representations of common data elements that are exchanged between Siebel Applications and Oracle Applications. When instantiated during run-time, they are used to hold the content of the data being sent from one application to the other. Two integration objects are typically defined for each data flow—an internal data object that represents Siebel Applications data and an external object that represents the corresponding data object in Oracle Applications.

For example, to import customer data from Oracle Applications into Siebel Applications as accounts, you must define an external integration object that represents the Oracle Applications' Customer data and another internal integration object that represents the corresponding Siebel Account business component. The Customer data from Oracle Applications may be imported directly from Oracle base tables or from database views.

On the other hand, to export Siebel account information to Oracle Applications through Oracle's Open Interface Tables, the external business objects must represent data definitions of the Interface Tables.

Two integration objects are provided for each integration point of the Siebel Connector for Oracle Applications' packaged integration. You may configure these objects for your specific needs or create new objects as part of a new integration point definition.