In the toolbar menu, click Reverse-Engineer.

3-10 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator The .BAD and .ERROR files are located in the same directory as the file being read and are named after this file, with a .BAD and .ERROR extension. ■ Null if error inactive trace : The row is kept in the flow and the erroneous value is replaced by null. ■ Null if error active trace : The row is kept in the flow, the erroneous value is replaced by null, and an reason of the error is written to the .ERROR file. Multi-Record Files Support Oracle Data Integrator is able to handle files that contain multiple record formats. For example, a file may contain records representing orders these records have 5 columns and other records representing order lines these records having 8 columns with different datatypes. The approach in Oracle Data Integrator consists in considering each specific record format as a different datastore. Example 3–1 Multi Record File This example uses the multi record file orders.txt. It contains two different record types: orders and order lines. Order records have the following format: REC_CODE,ORDER_ID,CUSTOMER_ID,ORDER_DATE Order lines records have the following format REC_CODE,ORDER_ID,LINE_ID,PRODUCT_ID,QTY Order records are identified by REC_CODE=ORD Order lines are identified by REC_CODE=LIN To handle multi record files as a source interface of an integration interface: 1. Create a File Model using a logical schema that points to the directory containing the source file. 2. Identify the different record formats and structures of the flat file. In Example 3–1 two record formats can be identified: one for the orders and one for the order lines. 3. For each record format identified, do the following: 1. Create a datastore in the File Model for each type of record. For Example 3–1 create two datastores. 2. In the Definition tab of the Datastore Editor, enter a unique name in the Name field and enter the flat file name in the Resource Name field. Note that the resource name is identical for all datastores of this model. For Example 3–1 you can use ORDERS and ORDER_LINES as the name of your datastores. Enter orders.txt in the Resource Name field for both datastores.

3. In the Files tab, select, depending on the format of your flat file, Fixed or

Delimited from the File Format list and specify the record and field separators. 4. In the Columns tab, enter the column definitions for this record type. 5. One or more columns can be used to identify the record type. The record code is the field value content that is used as distinguishing element to be found in the file. The record code must be unique and allows files with several record