0
Principles of Standard Data Transfer
Contents:
Tasks of standard data transfer
Documentation for data transfer
SAP record layout structure
SAP AG 1999
© SAP AG BC420 4-1
0.2
Standard Data Transfer: Unit Objectives
At the conclusion of this unit, you will be able to:
Obtain documentation on data transfer
Describe the rules for data formatting
Explain the structure of an SAP record layout
SAP AG 1999
© SAP AG BC420 4-2
0.3
Course Overview Diagram
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 AG BC420 4-3
0.4
Standard Transfer Overview
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.
© SAP AG BC420 4-4
0.5
Interfaces for Standard Data Transfer
RFBIDE00
FI
RMDATIND SAP System
MM
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.
© SAP AG BC420 4-5
0.6
Tasks in Standard Transfer
External
format
Formatting data
Mapping data
SAP record
layout structure
e.g. RFBIDE00
Customer data Document data
SAP AG 1999
The slide shows the important steps in a standard data transfer :
The external data is reformatted into the SAP format
The external fields are assigned to the SAP record layout fields
With DX-WB the SAP standard process can be selected and the data transfer started
© SAP AG BC420 4-6
0.7
Documentation from DX-WB
Help Application help
General help on data transfer
Data transfer techniques
Data transfer before Release 4.6A FI
Data transfer objects in CA
applications MM
LO
SD
HR
PP
SAP AG 1999
The DX-WB documentation is in the DX-WB itself.
© SAP AG BC420 4-7
0.8
Converting Data
External format SAP format SAP record
layout
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).
© SAP AG BC420 4-8
0.9
Formatting
External format SAP format
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:
The data must be in character format
The individual fields must not be longer than the defined SAP field.
If the data is shorter than the defined SAP field, you have to left align the data in the field (fill the
right hand side with blank characters).
Note: If you use BAPIs and IDocs for the transfer, there might be exceptions.
For conversions user-specific settings must be taken into account (e.g. fixed value settings in the user
profile) except for BAPIs and IDocs.
User-specific settings are the date format and the decimal setting.
If the data is transferred online, the authorizations and fixed values of the user who is starting the
transfer are used.
A user must be specified for background processing. This user should have the same user-specific
settings. Occasionally this use might have different authorizations, for example, in the production
system where the data is actually transferred.
Note: Different authorizations and settings may result in errors when the data is transferred (for
example, no authorization for the company code).
© SAP AG BC420 4-9
0.10
Mapping
SAP Format SAP Record Layout
...
...
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.
© SAP AG BC420 4-10
0.11
General Record Layout Structure
Record Layout Types
0 Session Header
1 Transaction Header Data
2 Transaction Data 1 Data for one data record
2 Transaction Data 2
1 Transaction Header Data
... Transaction Data 1 Data for one data record
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.
© SAP AG BC420 4-11
0.12
Example of Record Layout Type 0
0 Session header
...
Field Name Short Description Field Content
STYPE Record type 0 BI session name
GROUP Group name session_1 Client in which the session is to
MANDT Client 100 be processed
USNAM User ID BC420-00 User for the background processing
START Start date 01.01.2000
XKEEP Keep flag X Session locked until date specified
NODATA No batch input /
Should the session be kept after it
has been correctly processed?
NO DATA flag
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.
© SAP AG BC420 4-12
0.13
General Record Layout Structure
1 Transaction Header Data
2 Transaction Data
Field Name Description Field Contents
STYPE Record type 1 or 2 Record Type
GROUP Table name ........ Structure
...... ...... ........
SAP AG 1999
Transaction header data
These structures hold data for one transaction. You enter the transaction and the entries you made
on the initial screen of the transaction to this structure. This includes, among other entries, the
transaction code and key fields such as account group, company code key, document type, account
number, and document number.
Transaction data
These structures contain the master record and document position data. This includes the addresses
of your business partners and the document position amounts.
The different structures are described using record types. For the transaction data, specify the
structure name in addition to the record type.
The structures for batch input are defined in the ABAP Dictionary, where you can display the
individual structures.
© SAP AG BC420 4-13
0.14
Example: Record Layout Customer
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
Example of the record layout structures of the customer transfer.
See the documentation for the description of the individual structures.
© SAP AG BC420 4-14
0.15
Supported Methods
Customers Documents Vendors
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 BC420 4-15
0.16
Principles of Standard Data Transfer: Unit Summary
You are now able to:
Obtain documentation on data transfer
Describe the rules for data formatting
Explain the structure of an SAP record layout
SAP AG 1999
© SAP AG BC420 4-16
