One Source Multiple Staging Configuration

30-2 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator provides support for either updating some attributes like a status field or purging the source records once they have been successfully processed to the target system.

30.1.1.2 Cross Reference Table Structures

The XREF data can be stored in multiple cross reference tables and in two formats: ■ Generic legacy table - The table name is XREF_DATA and the table structure stores the cross references for all entities. The table format is as follows: XREF_TABLE_NAME NOT NULL VARCHAR22000 XREF_COLUMN_NAME NOT NULL VARCHAR22000 ROW_NUMBER NOT NULL VARCHAR248 VALUE NOT NULL VARCHAR22000 IS_DELETED NOT NULL VARCHAR21 LAST_MODIFIED NOT NULL TIMESTAMP6 This table stores cross references for multiple entities. In this table: – XREF_TABLE_NAME is the name of the cross reference table – XREF_COLUMN_NAME is the name of the column to be populated. This column name, for example the application name, is used as a unique identifier for the cross reference table. – ROW_NUMBER stores a unique identifier Row Number for a given entity instance, regardless of the application – VALUE is the value of the record identifier for a given entity in this application A specific XREF_COLUMN_NAME entry called COMMON exists to store a generated identifier that is common to all applications. For example, an ORDER existing in both SIEBEL and EBS will be mapped in a generic table as shown below: ■ Custom new table structure - The table is specific to one entity and has a custom structure. For example: ROW_ID VARCHAR248 NOT NULL PK, APP1 VARCHAR2100, APP2 VARCHAR2100, ... COMMON VARCHAR2100, LAST_MODIFIED TIMESTAMP NOT NULL Where: – Columns such as APP1 and APP2 are used to store PK values on different applications and link to the same source record – ROW_ID Row Number is used to uniquely identify records within a XREF data table. Table 30–1 Example of an XREF_DATA Partial XREF_TABLE_NAME XREF_COLUMN_NAME ROW_NUMBER VALUE ORDER SIEBEL 100012345 SBL_101 ORDER EBS 100012345 EBS_002 ORDER COMMON 100012345 COM_100 Oracle SOA Suite Cross References 30-3 – COM holds the common value for the integration layer and is passed among participating applications to establish the cross reference The same ORDER existing in both SIEBEL and EBS would be mapped in a custom XREF_ORDER table as shown below: See Section 30.3.3, Designing an Interface with the Cross-References KMs and Section 30.4, Knowledge Module Options Reference for more information.

30.1.1.3 Handling Cross Reference Table Structures

The IKM SQL Control Append SOA XREF provides the following parameters to handle these two table structures: ■ XREF_DATA_STRUCTURE: This option can be set to legacy to use the XREF_ DATA generic table, or to new to use the custom table structure. If using the generic table structure, you must set the following options: ■ XREF_TABLE_NAME: Value inserted in the XREF_TABLE_NAME column of the XREF_DATA table. In the example above See Table 30–1 this option would be ORDER. ■ XREF_COLUMN_NAME: Value inserted in the XREF_COLUMN_NAME column of the XREF_DATA table. This value corresponds to the application that is the target of the current interface. In the example above See Table 30–1 , this option would take either the value SIEBEL or EBS depending on which system is targeted. If using the custom table structure, you must use the following options: ■ XREF_DATA_TABLE: Name of the cross reference table. It defaults to XREF_DATA. In the example above See Table 30–2 , this table name would be XREF_ORDER. ■ XREF_DATA_TABLE_COLUMN: Name of the column that stores the cross references for the application that is the target of the current interface. In the example above See Table 30–2 , this option would take either the value SIEBEL or EBS depending on which system is targeted.

30.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules KM listed in Table 30–3 for handling SOA cross references XREF. These new Knowledge Modules introduce parameters to support SOA cross references. See Section 30.1.1.2, Cross Reference Table Structures and Section 30.3.3, Designing an Interface with the Cross-References KMs for more information on these parameters. Table 30–2 Example of a Custom Table: XREF_ORDERS Partial ROW_ID SIEBEL EBS COMMON 100012345 SBL_101 EBS_002 COM_100 30-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator

30.1.3 Overview of the SOA XREF KM Process

To load the cross reference tables while performing integration with Oracle Data Integrator, you must use the SOA XREF knowledge modules. These knowledge modules will load the cross reference tables while extracting or loading information across systems. The overall process can be divided into the following three main phases:

1. Loading Phase LKM

2. Integration and Cross-Referencing Phase IKM

3. UpdatingDeleting Processed Records LKM

30.1.3.1 Loading Phase LKM

During the loading phase, a Source Primary Key is created using columns from the source table. This Source Primary Key is computed using a user-defined SQL expression that should return a VARCHAR value. This expression is specified in the SRC_PK_ EXPRESSION KM option. For example, for a source Order Line Table aliased OLINE in the interface you can use the following expression: TO_CHAROLINE.ORDER_ID || - || TO_CHAROLINE.LINE_ID This value will be finally used to populate the cross reference table. Table 30–3 SOA XREF Knowledge Modules Knowledge Module Description LKM SQL to SQL SOA XREF This KM replaces the LKM SQL to SQL ESB XREF. This KM supports cross references while loading data from a standard ISO source to any ISO-92 database. Depending of the option SRC_UPDATE_DELETE_ACTION, this LKM can DELETE or UPDATE source records. The LKM SQL to SQL SOA XREF has to be used in conjunction with the IKM SQL Control Append SOA XREF in the same interface. LKM MSSQL to SQL SOA XREF This KM replaces the LKM MSSQL to SQL ESB XREF. This KM is a version of the LKM SQL to SQL SOA XREF optimized for Microsoft SQL Server. IKM SQL Control Append SOA XREF This KM replaces the IKM SQL Control Append ESB XREF. This KM provides support for cross references while integrating data in any ISO-92 compliant database target table in truncateinsert append mode. This KM provides also data control: Invalid data is isolated in an error table and can be recycled. When loading data to the target, this KM also populates PKGUID XREF table on a separate database. This IKM SQL Control Append SOA XREF has to be used in conjunction with the LKM SQL to SQL SOA XREF or LKM MSSQL to SQL SOA XREF. Note: In order to maintain the cross referencing between source and target systems, the LKM and IKM supporting cross referencing must be used in conjunction.