Inbound Flat File scenario

USE:

Inbound flat file interface that will test EDIFACT Orders96A.

PROCEDURE:

1. Go to transaction /INT4/IFTT_CONF and create a new object definition, e.g.:
   1. Object Definition ID: B2B_EDIFACT
   2. Description: Inbound B2B
   3. Name: Dummy
   4. Namespace: Dummy
      

   
   
   In the Name and Namespace fields, we should provide the interface name and namespace used in the ICO of the tested interface. 
   
   
   
   

2. Go to Object Variables and define variables names and descriptions. You can declare an unlimited number of variables. Always try to give the variable a meaningful description. 

   
   
   
   
   

3. After selecting a single variable, move to Variable Processing. Here you define actions for every variable declared in the previous step. For more specific information, check the Variable processing section.   

   
   Be aware that for constructing XPath Expressions for flat files, we should use Expression language for flat files.
   
   
4. In the DB Comparison rule section, provide tables, which will be used for comparison, and the next set selection criteria, Match. Criteria and Comparison Details. 
   
   
   1. Provide database tables 
      
      
      
   2. Provide data for selection for step #1. Here you define which values will Int4 IFTT look for in the header table of the document to find the newly created document for comparison on the ECC site. 
      
   3. Define comparison details for the VBAK table: names of the fields to be compared and rules that should be applied.
      
      
      
   4. Provide data for selection for step #2. In this stage, we repeat the step from point b) but this time for the VBAP table. For more info on how to fill this section, check Selection Criteria.
      
      
      
      
   5. In Matching Criteria for step #2, type the proper field name. For more info on how to fill this section, check Matching Criteria. 
      
      
      
   6. Define comparison details for the VBAP table: names of the fields to be compared and rules that should be applied.
      
      
      
5. Add Additional Parameters
   
   
   
   
   1. PI business component name
   2. PI communication channel name
   3. Flag for Flat File interfaces
   4. Flat File Line Separator
   5. PI Business party name
   6. Message Version fetched from PI 
      
      For more info on how to fill this section, check Additional Parameters.
      
6. Create a number range assigned to a specific variable or multiple variables in the variable processing section. For more info on how to fill this section, check Number ranges.