立即与支持人员聊天
与支持团队交流

Identity Manager 9.1.1 - Administration Guide for Connecting to Oracle E-Business Suite

Mapping an Oracle E-Business Suite in One Identity Manager Synchronizing Oracle E-Business Suite
Setting up initial synchronization of Oracle E-Business Suite Customizing the synchronization configuration Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing E-Business Suite user accounts and employees Login information Managing entitlement assignments Mapping of E-Business Suite objects in One Identity Manager Handling of E-Business Suite objects in the Web Portal Basic configuration data Configuration parameters for managing Oracle E-Business Suite Permissions required for synchronizing with Oracle E-Business Suite Default project templates for synchronizing an Oracle E-Business Suite Editing system objects Example of a schema extension file

Table definitions

The <Tables> tag can contain any number of table definitions in <Table> tags. This makes it possible to name all tables or view from which data for a single object of this schema type is required. The underlying required information for a table is defined in the attributes of the <Table> tag.

Table 9: Attributes of a table definition

Attribute

Description

Name

Name of the table (without schema name).

Schema

Name of the Oracle schema.

APK

Name of a column that can be an alternative primary key. This column is always loaded.

USN

Name of a column that stores information about the last object modifications. If the column LAST_UPDATE_DATE exists, this is used as change information by default and does not have to be specified explicitly.

WhereClause

WHERE clause for restricting the results set.

JoinParentTable

Name of a parent table when a join operation is carried out on a schema type higher up in the hierarchy.

JoinParentColumn

Comma-delimited list of columns in a parent table when a Join operation is carried out on a schema type higher up in the hierarchy (full notation).

JoinChildColumn

Comma-delimited list of columns in the currently defined table to be joined to the columns from JoinParentColumn in the Join operation (full notation). The sequence of columns in the list determines which columns are joined to each other.

View

Name of the view if there is a view for the table that filters the table contents based on the current database edition.

Example: Specify the FND_RESPONSIBILITY_TL# view for the FND_RESPONSIBILITY_TL table.

Example

<Tables>

...

<Table Name="FND_RESPONSIBILITY_TL" View="FND_RESPONSIBILITY_TL#" Schema="APPLSYS" APK="" USN="APPLSYS.FND_RESPONSIBILITY_TL.LAST_UPDATE_DATE" WhereClause="APPLSYS.FND_RESPONSIBILITY_TL.LANGUAGE='$SYSLANGU$'" JoinParentColumn="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID,APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" JoinParentTable="FND_RESPONSIBILITY" JoinChildColumn="APPLSYS.FND_RESPONSIBILITY_TL.RESPONSIBILITY_ID,APPLSYS.FND_RESPONSIBILITY_TL.APPLICATION_ID" />

...

</Tables>

Primary key definition

The <PK> tags within the <Table> section name the primary key columns of a table. The name of the column is specified in the Column attribute. To define primary keys with multiple columns, enter each column in a separate tag. You can use any number of <PK> tags in a table definition.

Table 10: Attribute of a primary key definition

Attribute

Description

Column

Name of the primary key column (full notation).

Example

<PK Column="APPLSYS.FND_RESPONSIBILITY_TL.RESPONSIBILITY_ID" />

Column pairs in the hierarchy

The <ParentTableFK> tags within the <Table> section describe the column pairs that are to be equated with the table of the superordinate schema type in a Join operation.

Table 11: Attributes of a column pair

Attribute

Description

Column

Name of the column in the current defined table.

ParentColumn

Name of the column in the table of the superordinate schema type.

Example

<ParentTableFK Column="APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" ParentColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

Example of a complete table definition

<Object SchemaName="ORA-Responsibility" ParentSchemaName="ORA-Application" DisplayPattern="%vrtDistinguishedName%" IsReadOnly="true" UseDistinct="false">

<ObjectKey>

<Key Column="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID" IsDNColumn="true" IsReferencedColumn="true" X500Abbreviation="RE" />

<Key Column="APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" />

</ObjectKey>

<Tables>

<Table Name="FND_RESPONSIBILITY" View="FND_RESPONSIBILITY#" Schema="APPLSYS" APK="" USN="" WhereClause="" JoinParentTable="" JoinParentColumn="" JoinChildColumn="" >

<PK Column="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID" />

<ParentTableFK Column="APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" ParentColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

</Table>

<Table Name="FND_RESPONSIBILITY_TL" View="FND_RESPONSIBILITY_TL#" Schema="APPLSYS" APK="" USN="APPLSYS.FND_RESPONSIBILITY_TL.LAST_UPDATE_DATE" WhereClause="APPLSYS.FND_RESPONSIBILITY_TL.LANGUAGE='$SYSLANGU$'" JoinParentColumn="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID,APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" JoinParentTable="FND_RESPONSIBILITY" JoinChildColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" >

<PK Column="APPLSYS.FND_RESPONSIBILITY_TL.RESPONSIBILITY_ID" />

</Table>

<Table Name="FND_APPLICATION" View="FND_APPLICATION#" Schema="APPLSYS" APK="" USN="" WhereClause="" JoinParentTable="FND_RESPONSIBILITY" JoinParentColumn="APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" JoinChildColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" >

<PK Column="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

</Table>

</Tables>

</Object>

Explanation

The definition above shows the declaration of the ORA-Responsibility schema type as it is used internally by the Oracle E-Business Suite connector.

The schema type is subordinate to the ORA-Application schema type in the hierarchy (ParentSchemaName). It has to object key columns (APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID and APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID), of which only one is included as a part of the distinguished name IsDNColumn="true". The column APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID is a part of the DistinguishedName of the superordinate schema type, which is added automatically at the end.

For the selection of all properties, records from the tables FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL and FND_APPLICATION are queried by a Join operation. The columns for the Join operation are specified in the relevant attributes JoinParentColumn and JoinChildColumn.

The description text is read from the table FND_RESPONSIBILITY_TL in the language specified by the database connection configuration. For this reason, the symbolic variable $SYSLANGU$ is used in the Where clause. For more information, see Symbolic variables in WHERE clauses.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级