Professional Documents
Culture Documents
Contents:
Tasks of standard data transfer
Documentation for data transfer
SAP record layout structure
SAP AG 1999
SAP AG 1999
Call Transaction
Batch Input
Direct Input
TA Recorder
7 12 IDoc BAPI
9
10
11 12
Principles of Standard
Data Tansfer 44
DX Workbench 11
3 5
LSM Workbench
8 10 11
6 13
Basics
2 Datenübernahme 14
1 Course Overview
SAP AG 1999
SAP Record
Layout
Structure
BAPI
SAP IDoc
Structure
Flat SAP
Structure
SAP AG 1999
The following describes the basics of data transfer in the standard system using the transfer programs
delivered from SAP.
RFBIDE00
FI
SAP Record
Layout Structure
RPUSTD00
HR
SAP AG 1999
SAP supplies standard data transfer programs that require specific SAP-configured interfaces called
SAP record layout structures. The external data transferred through these layout structures must be in
a compatible format.
The interface definitions are set in the SAP System and can be used as the basis for projection and
planning of the transfer procedure.
External
format
Formatting data
Mapping data
SAP record
layout structure
e.g. RFBIDE00
PP
SAP AG 1999
Formatting Assignment
Conversion
SAP AG 1999
The external data can be converted into the SAP record layout in one step or in two separate steps
(formatting and assigning).
There are important rules to follow for the formatting and assignment (next slides).
1) Value $ USD
2) Type
Typ C , P , INT Type C
3) Decimal point
, or .
Consider user
settings
4) Date 2000.23.06
01/02/2000
SAP AG 1999
If you use a transfer program, the external data must be formatted the same as for an online user who
enters the values using the keyboard. The following rules apply:
...
...
How is the external
data mapped to
the record layouts?
SAP AG 1999
The standard transfer programs expects the file to be in the corresponding SAP record layout format.
The data must correspond to this record layout structure. However, you do not have to use all of the
record layout structures.
Some structures must be used (required), while others are optional; this depends on the application.
For information about which structures are required and which are optional, see the documentation
for the record layout structures.
0 Session Header
2 Transaction Data 2
Transaction Data 2
This is the next batch input
0 Session Header session
...
SAP AG 1999
The data records contained in the sequential file must be in a format that can be read by an SAP
standard transfer method.
Each transfer program expects the file to be in this general SAP record layout format.
Each record layout contains individual structures, each of which is defined in the ABAP Dictionary.
The structure descriptions and the layout of the sequential file depend on the application; the
structures and layouts are described in the documentation for the standard transfer procedure.
If a new session header is added to the structure, the existing session is closed and a new session is
generated.
0 Session header
...
SAP AG 1999
Each session contains a session header (record type 0), also called a session header record. The
session header record contains administration data about the batch input file to be created. All other
records of the sequential file up to the next session header are assigned to the current session.
Note: If the transfer is carried out in the background, the user specified in the session header for the
authorization check is used. This means that the authorizations and settings of the fixed values in the
user profile are used for checking.
If the stop indicator is set (= ‘X‘), the processed session remains in the system, otherwise it is
deleted.
In the field NODATA you specify the character that will later be used as the NODATA indicator.
2 Transaction Data
SAP AG 1999
0 BGR00
1 BKN00 Header data for customers
2 BKNA1 General customer data
2 BKNB1 Company code data
2 BKNBK Bank details
2 BKNVA ...
2 BKNVK
2 BKNB5 Dunning data
2 BKNZA ...
2 BKNKA
2 BKNKK
2 BKNVV
2 BKNVD
2 BKNVI
2 BKNVL
2 BKNVP
2 BKNAT
2 BKNBW
2 BIADDR2
2 BWRF4
2 BWRF12
SAP AG 1999
RFBIDE00
RFBIBL00
RFBIKR00
CT
DI
SAP AG 1999
Every application provides transfer programs. Which methods can be used (BI, CT, or DI) depends
on the individual programs. You cannot influence this.
If your data is in the SAP record layout structure and the relevant program supports several methods,
you can use all of the methods without having to change the structure or the contents of the file.
An example of this is program RFBIBL00, which transfers FI documents. You can use any of the
three methods with this program.
SAP AG 1999