Loading Phase LKM Overview of the SOA XREF KM Process

Oracle SOA Suite Cross References 30-7 3. Create a logical schema called XREF pointing to the physical schema. containing the cross reference table. See Creating a Logical Schema in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information.

30.3.2 Setting up the Project

Import the following KMs into your project, if they are not already in your project: ■ IKM SQL Control Append SOA XREF ■ LKM SQL to SQL SOA XREF or LKM MSSQL to SQL SOA XREF if using Microsoft SQL Server

30.3.3 Designing an Interface with the Cross-References KMs

To create an integration interface, which both loads a target table from several source tables and handles cross references between one of the sources and the target, run the following steps: 1. Create an interface with the source and target datastores which will have the cross references. 2. Create joins, filters and mappings as usual. Mapping the Common ID : If you want to map in a target column the Common ID generated for the cross reference table, check the UD1 flag for this column and enter a dummy mapping. For example a constant value such as’X’. 3. In the Flow tab of the interface, select the source set containing the source table to cross reference, and select the LKM SQL to SQL SOA XREF or LKM MSSQL to SQL SOA XREF if the source data store is in Microsoft SQL Server. 4. Specify the KM options as follows: ■ Specify in SRC_PK_EXPRESSION the expression representing the Source Primary Key value that you want to store in the XREF table. If the source table has just one column defined as a key, enter the column name for example SEQ_NO. If the source key has multiple columns, specify the expression to use for deriving the key value. For example, if there are two key columns SEQ_NO and DOC_DATE in the table and you want to store the concatenated value of those columns as your source value in the XREF table enter SEQ_NO || DOC_ DATE. This option is mandatory. ■ Optionally set the SRC_UPDATE_DELETE_ACTION to impact the source table, as described in Section 30.1.3.3, UpdatingDeleting Processed Records LKM

5. Select your staging area in the Flow tab of the interface and select the IKM SQL

Control Append SOA XREF . 6. Specify the KM options as follows: ■ XREF_DATA_STRUCTURE: Enter New to use the new XREF_DATA Table structure. Otherwise enter Legacy to use legacy XREF_DATA Table. Default is New. Configure the options depending on the table structure you are using, as specified in Section 30.1.1.3, Handling Cross Reference Table Structures 30-8 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator ■ XREF_SYS_GUID_EXPRESSION: Enter the expression to be used to computing the Common ID. This expression can be for example: – a database sequence SEQUENCE_NAME.NEXTVAL – a function returning a global unique Id SYS_GUID for Oracle and NewID for SQL Server ■ XREF_ROWNUMBER_EXPRESSION: This is the value that is pushed into the Row Number column. Use the default value of GUID unless you have the need to change it to a sequence. ■ FLOW_CONTROL: Set to YES in order to be able to use the CKM Oracle.

30.4 Knowledge Module Options Reference

This section lists the KM options for the following Knowledge Modules: ■ LKM SQL to SQL SOA XREF ■ LKM MSSQL to SQL SOA XREF ■ IKM SQL Control Append SOA XREF Note: If the target table doesnt have any placeholder for the Common ID and you are for example planning to populate the source identifier in one of the target columns, you must use the standard mapping rules of ODI to indicate which source identifier to populate in which column. If the target column that you want to load with the Common ID is a unique key of the target table, it needs to be mapped. You must put a dummy mapping on that column. At runtime, this dummy mapping will be overwritten with the generated common identifier by the integration knowledge module. Make sure to flag this target column with UD1.