Siebel Connector for Oracle Applications > Developer Procedures > Understanding the Oracle Applications Wizard >

Working with Integration Objects

SQL integration objects are metadata that define the schema of a table hierarchy in the external Oracle database. These objects contain integration components that map directly to Oracle tables and views. They also incorporate the primary key and foreign key relationships that exist between the tables in the external database.

Using Metadata to Create Integration Objects

As it creates integration objects, the Oracle Applications wizard retrieves metadata information from FND tables in the external Oracle database. Figure 9 shows the relationship between the Oracle Applications integration objects and the Oracle Applications database tables.

Figure 9. Relationship Between SQL Integration Objects and SQL Database Tables

NOTE:  An Oracle Applications integration object may have SQL as the base object, enabling the Adapter to validate the objects.

Obtaining Oracle Application Metadata

The Oracle Wizard uses the DB Adapter to obtain information about Oracle Applications metadata. In this process, the Wizard passes integration objects to the DB Adapter that indicate where and how the Adapter should fetch the information. The Adapter obtains the following Oracle Applications database information for the wizard:

• Names of the tables that will be used to create the integration objects
• Names and properties of the table columns
• Referential constraints of the tables
• Foreign key columns of given foreign key relationships
• Primary key columns of the tables

Oracle Tables Containing Metadata

The Wizard uses metadata contained in the following Oracle Applications tables:

• FND_APPLICATION
• FND_TABLES
• FND_COLUMNS
• FND_FOREIGN_KEYS
• FND_FOREIGN_KEY_COLUMNS
• FND_PRIMARY_KEYS
• FND_PRIMARY_KEY_COLUMNS

See the Oracle Application Technical Reference Manuals for descriptions of these tables.

Metadata Integration Objects Used to Query the SQL Adapter

The Oracle Applications wizard uses the following metadata integration objects to query the DB Adapter for needed information:

• Oracle Wizard Get Tables—Used to query for all tables of an application. Cached locally to facilitate mapping of names to IDs and IDs to names.
• Oracle Wizard Get Children—Used to query for children of a table. The Primary Key Application ID and Primary Key Table ID are set as search specifications.
• Oracle Wizard Get Table All—Used to query for the columns, primary key fields, and foreign key fields of a table. A query is made with respect to a specific foreign key that is set as a search specification on the FND_FOREIGN_KEYS component.