Select the Context for this datastore if you want to source data from this datastore

Working with Integration Interfaces 11-13 8. If you want ODI to automatically generate temporary indexes to optimize the execution of this join, select the index type to create from the Temporary Index On lists. This step is optional. To delete a join between source datastores of an interface: 1. In the Source Diagram, select the join.

2. Right-click and select Delete.

To display the data or the number of rows resulting from a join: 1. In the Source Diagram, select the join.

2. Right-click and select Number of Lines to display the number of rows returned by

the join or Display Data to display the result of the join. A window containing the data or the number of rows resulting from the join appears.

11.3.5 Define the Mappings

A mapping defines the transformations on one or several source columns to load one target column. Empty mappings are automatically filled when you add a source or target datastore by column name matching. The user-defined mapping always takes precedence over automatic mapping. To regenerate the automatic mapping by column name matching:

1. Right-click the target datastore.

2. Select Redo Auto Mapping.

The target datastore columns are automatically mapped on the source datastores columns with the same name. To define the mapping of a target column:

1. In the Target Datastore Panel, select the column of the target datastore to display

the Property Inspector.

2. In the Diagram Property tab of the Property Inspector, modify the

Implementation to create the required transformation. The columns of all the tables in the model can be drag-and-dropped into the text. You may call the expression Editor by clicking Launch Expression Editor. 3. Optionally, click Check the expression in the DBMS to validate the expression. 4. Select the execution location: Source, Target or Staging Area. Some limitations exist when designing mappings. When a mapping does not respect these limitations, a red cross icon appears on the target column in the Target Datastore Panel. For example: ■ Mappings that contain constants cannot be mapped on the source without having selected a source datastore. Note: The creation of temporary indexes may be a time consuming operation in the overall flow. It is advised to review the execution statistics and to compare the execution time saved with the indexes to the time spent creating them. 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.