This section describes how to analyze the SAP structures required for the data transfer file.
To load the data into the R/3 System (task type LOA), SAP provides one or more program types for each object type.
Task Type |
Program Type |
Description |
LOA |
BAPI |
Loads the data into R/3 using a BAPI |
BINP |
Loads the data into R/3 using batch input | |
DINP |
Loads the data into R/3 using direct input | |
FUNC |
Loads the data into R/3 using a function module | |
REPO |
Loads the data into R/3 using a report |
You can select the programs, function modules or BAPIs for the program types of the task type LOA using input help.
You can use the tools to analyze the associated SAP structures.
The Data Transfer Workbench can generate data definitions for the programming languages C, Cobol
a nd PL1 .If you create a data transfer file with the required application data, you can use this file to test the data transfer.
Prerequisites
You have identified the SAP business object types for the data to be transferred.
Procedure
In the Data Transfer Workbench choose Goto ® Tools ® Files and data structures.
The Data Transfer - Tools screen appears.
Create File
To create a data transfer file (input file) - use F1 help and input help, if available: Use F1 field help.
Create File
A data transfer file in SAP format is created without data.
This file contains all the required structure information.
You can use this information to identify the required R/3 data structures.
You can manually enter application data into this file.
Create file with data
Provided that the application has a program to create test data, you can create a file with this test data.
EDI Customizing settings are required for the program type BAPI. The application program creates IDocs that are written with these settings into a file.
Specify a logical system when you create the file. A logical system is an application system in which the applications work together in a common database.
You can then generate the settings for this logical system.
The required authorizations are contained in the role ALE Administrator (SAP_BC_MID_ALE_ADMIN).
Alternatively, you can also carry out these steps manually to generate the Customizing settings. If you use the program type BAPI to create a file, you have to make the following settings in the R/3 Implementation Guide under Basis ® Application Link Enabling (ALE):
Sending and Receiving Systems
Logical Systems
Name Logical System
If you use Create file with data, You have to make further settings:
Sending and Receiving Systems
Systems in Network
Asynchronous Processing
Assign Ports
Enter a file name with a physical directory.
Modeling and Implementing ALE Business Processes
Partner Profiles and Time of Processing
Maintain Partner Profiles
The partner profiles are valid for the message type assigned to the BAPI. This is required for filling the IDoc control record. The message types for the individual applications can be found in
Check File
You can check the file syntax.

If the file is in SAP record layout format, the sequence of the record layout structure is checked.
If the file is in IDoc format, all the EDI inbound processing checks are run.
To save objects not processed via a BAPI as an IDoc in R/3, your input file must not contain any errors.
Proceed as follows:
Display File
Choose Display file.
An overview of the file contents appears.
The field values are formatted according to the settings defined by the user. For example, the date format 1303200 may be formatted as 13.03.2000.
Familiarize yourself with the structures.
Copy File
The data transfer file can be copied between application and presentation servers.
This file can
only be copied in the structure of the selected business object.The transfer file data must be transferred to the R/3 System in a fixed length.
Proceed as follows:
The data transfer file is copied without being changed You normally select this option for copying between applications servers.
This option is only possible for copying a file from the application server to the presentation server. The data is converted into the presentation format and the individual fields are delimited by a tabulator. Normally you would want to use your data in a table calculation program on the front-end.
This option can only be used for copying a file from the presentation server to the application server. During this copying process, the data is converted into the SAP format and copied to the required fixed length. This option is normally chosen if you want to copy your data from a spreadsheet program to an application server.

When the data is copied it is saved temporarily in the main memory. If you have a large dataset, the roll area could overflow. The copy process would then terminate. If you have a large dataset use the copy function of the operating system.
Change File
You can fill the file with application data, change existing data or add more data.
Choose Change file.
An overview of the file contents in the SAP format appears.
You can change individual lines by selecting one and choosing Structure ® Change or by double-clicking on it.
The detail display of the individual fields of the structure in the SAP format appears. You can display further details of fields by double-clicking on a field.
Display Object Type Structures and Program/Method.
To display the structures of object types and the program/method choose Structure ® Display.
A list of the details of the structures and fields is displayed. You can download this list to your PC.
Familiarize yourself with the structure.
Creating Data Definitions for External Programs
If you use other programming languages (C, Cobol or PL/1), you can create data definitions with the correct target structure.
Choose Goto ® Tools ® Files and data structures, Structure ® Generate.
Result
You have familiarized yourself with the structures and fields.