From the tree in the Lookup Table pane on the right, do one of the following:

11-14 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ Mappings that contain reference source columns cannot be mapped on the target. ■ A mandatory column should be mapped. ■ A mapping mapped in one dataset must be mapped in all other datasets.

5. Check the Update boxes if you want the mapping to be executed in Insert or

Update operations. You can also check the UD1 to UD10 boxes to enable KM-specific options on columns. These options are optional, and must be used if the Knowledge Module documentation indicates it. Otherwise, they are ignored.

6. Check Active Mapping if you want this mapping to be used for the execution of

the interface. Note that if you enter a mapping text in a disabled mapping, this mapping will automatically be enabled.

11.3.6 Define the Interface Flow

In the Flow tab, you define the loading and integration strategies for mapped data. Oracle Data Integrator automatically computes the flow depending on the configuration in the interfaces diagram. It proposes default KMs for the data flow. The Flow tab enables you to view the data flow and select the KMs used to load and integrate data. In the flow, the following items appear: ■ Source Sets : Source Datastores that are within the same dataset, located on the same physical data server and which are joined with Joins located on the Source are grouped in a single source set in the flow diagram. A source set represents a group of datastores that can be extracted at the same time. ■ DataSets : Datasets appear as yellow boxes in the Staging Area. ■ Staging Area : It appears as a box that includes the different datasets, the target if located on the same data server, and possibly some of the sources if located on the same data server. ■ Target : It appears as a separate box if it is located in a different schema from the staging area If the Staging Area Different from Target option is selected. You use the following KMs in the flow: ■ LKM : They define how data is moved. One LKM is selected for each Source Set for moving data from the sources to the staging area. It can be also selected to move data from the Staging Area - when different from the Target - to the Target, when a single technology IKM is selected for the Staging Area. ■ IKM : They define how data is integrated into the target. One IKM is typically selected on the Target. When the staging area is different from the target, the selected IKM can be a multi-technology IKM that moves and integrates data from the Staging Area into the Target. Tip: Before proceeding, you can check the consistency and errors in your diagram by clicking the Display Interface Errors Report in the Source Diagram Toolbar. This report will show you errors that may exist in your interface such as mappings incorrectly located. At this stage, you may receive some errors because the Knowledge Modules are not selected yet for this interface. Working with Integration Interfaces 11-15 To change the LKM in use: 1. In the Flow tab, select one of the Source Sets or the Staging Area, if it is not into the Target group, by clicking its title. The Property Inspector opens for this object.

2. If you are working on a Source Set, change the Name of this source set. This step is

optional and improves readability of the flow.

3. Select a LKM from the LKM Selector list.

4. KMs are set with default options that work in most use cases. You can optionally modify the KM Options. Note that KM options of the previous KM are retained using homonymy when switching from a KM to another. By changing KMs several times you might lose custom KM option values. To change the IKM in use: 1. In the Flow tab, select the Target by clicking its title. The Property Inspector opens for this object.

2. In the Property Inspector, select a IKM from the IKM Selector list.

3. Check the Distinct option if you want to automatically apply a DISTINCT

statement on your data flow and avoid possible duplicate rows. 4. KMs are set with default options that work in most use cases. You can optionally modify the KM Options. Note that KM options of the previous KM are retained using homonymy when switching from a KM to another. By changing KMs several times you might lose custom KM option values. An important option to set is FLOW_CONTROL. This option triggers flow control and requires that you set up flow control.

11.3.7 Set up Flow Control and Post-Integration Control

In an integration interface, it is possible to set two points of control. Flow Control checks the data in the incoming flow before it gets integrated into the target, and Post-Integration Control checks the target datastore as if in a static check at the end of the interface. Note: Only KMs that have already been imported in the project can be selected in the interface. Make sure that you have imported the appropriate KMs in the project before proceeding. Note: Knowledge modules with an Incremental Update strategy, as well as flow control, require that you set an update key for the target datastore of the interface. Note: For more information on the KMs and their options, refer to the KM description and to the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator.