As the XML runtime of AIF is used to process the data sets, a runtime configuration group can be specified. This allows you to define whether the messages are processed in the same session or background jobs are created. Furthermore, this defines how many messages are processed within one run or package.

 

There are no default settings for uploading a file. To upload a file, the minimum information required is the file type, file content, and text type. To map the file to the interface, the structure name and the field name, to where the file content is moved during the upload, is required:

• File Type defines whether the file should be read in binary mode or in text mode.
• File Content defines what the content of the file looks like. There are following file content types:
  • Flat Structure
  • Complex Structure: The file content can be mapped into a complex structure, which may contain header, substructures, and sub tables. In this case, you have to maintain a substructure determination in Customizing for the SAP Application Interface Framework under Configure File Adapter.-
  • User Defined: Customer-specific mapping can be done using a customer-specific function module, the name of which has to be stored in the Mapping Function field.-
  • XML: Mapping is done via Extensible Stylesheet Language Transformation (XSLT) or Simple Transformation (ST). The transformation name must be stored in the Transformation field.-
  • Depending on the selection done in the File Content field, different fields are displayed in the Customizing of the field adapter configuration.
• Text Type: defines where the file content should be separated into individual fields during the file upload. The following options are possible:
  • Special Character as Separator: The individual fields are separated by a special character in the file (e.g., in case of CSV files). The separator needs to be maintained in the Field Separator field.-
  • Fixed Field Lengths: The length of the individual fields is correctly represented in the file and no special field separator is used.-
  • One Field per Line: Each field has exactly one line in the file.
• Structure Name: Name of the raw structure used in the AIF interface.
• Field Name: defines the component of the structure, maintained in the Structure Name field, to where the file content is moved during upload. This component can also be a table type. In this case, the line type of this table type has to fit to the data that you upload with the file.

 

Source Structure

To be able to process files in AIF, you need a DDIC structure that matches the file. How do you create this structure?

• Check the file and the content.
  • In which form is the data contained in the file? Does the file contain a data table or only a single record? How long are the different fields?
• Create a corresponding DDIC structure.
  • If the file contains a data table, the DDIC structure requires a table to store the different entries from the file. The line type is defined by the different fields of the file.

   

  • Depending on the raw structure used, AIF creates one or multiple messages. If the file contains a data table and the raw structure resamples the table with a corresponding table type, AIF only creates one message per file. If the raw structure is a structure that resamples one line of the file, AIF creates a new message for every line in the selected file.

 

For example, the file contains a table with IDs, names, and cities. The ID is 6 characters long. The name can be 30 characters long and the city can be 60 characters long.

 

In this case, the source structure must contain a table containing the different entries. The table is defined by the different fields of the file.

 

The line type is a structure with the following fields: ID Char 6, Name Char 30, and City Char 60. This structure is used as line type for the table. The table is then included into the source structure.

 

Destination Structure