Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
SAP AG 1999
Create files
Change and display files
Copy files
Generate test data for data transfer
SAP AG 1999
Call Transaction
Batch Input
Direct Input
TA Recorder
7 12 IDoc BAPI
9
10
11 12
Principles of Standard 4
Data Tansfer
DX Workbench 55 11
3 LSM Workbench
8 10 11
6 13
Basics
2 Datenübernahme 14
1 Course Overview
SAP AG 1999
With some data transfer objects you can create a file with test data. Data from R/3 is inserted into a
file.
The function is available for standard transfer programs (BI,CT,DI) and BAPIs
Note: This function is not available for all data transfer programs. It is application-dependent.
See appendix 01 for an overview of the objects that can use this function.
Standard
Data transfer program
transfer
Object type KNA1 program for
Task type Load data into R/3 customers
Program type BINP
Program / method RFBIDE00 File name
Input file
File type P
File name \\trans02\transpr\BC420_DEBI.SAP
SAP AG 1999
To use the tools of the DX-WB, you have to specify the program or the method for the data transfer.
Proceed as follows:
Select the relevant object type in your application.
Select the supported program type.
Select the supported program or method.
Note: Use the F4 input help
Then you must specify the file name and the directory in which this is stored or should be created. A
physical or logical path/file name should be specified. (For more information about logical file
names see the unit on sequential files)
The path shown is valid for Release 4.6A
For the Release 4.6B the valid path is Goto -> Analyze files and data structures.
SAP AG 1999
When you create a file for a selected object and method, this file is an initialized file. It contains all
the structures that the object supports.
If you are using a standard transfer program, the associated record layout always contains a session
header.
Structures are predefined with the NODATA character only for BI or DI. This is not required for
BAPIs.
SAP AG 1999
With some data transfer objects you can create a file with test data. Data from R/3 is inserted into a
file.
This function is not available for all transfer programs. It is application-dependent.
See appendix 01 for an overview of the objects that can use this function.
The function is available for standard transfer programs (BI,CT,DI) and BAPIs.
Structure Contents
Record name
BGR00 Session record 0Mappe1 003 ... BKNA1 Customers
BKN00 Header date 1 1XD01 Z-00-1000 Data record
BKNA1 Standard 2BKNA1 / John Field Name Short Description Field Contents
...
STYPE Record type 2
Disp
lay/c TBNAM Table name BKNA1
hang
e
...
Name1 Name 1 Smith
... ... /
SAP AG 1999
Source Target
SAP AG 1999
The data transfer file can be copied between the application and presentation servers.
The data transfer programs expect the transfer file to have a fixed length.
The following conversions are possible:
This copy function can only be used to copy from the application server to the presentation
server. The data is copied into a format and the data is delimited by a tabulator.
This copy function can only be used to copy from the presentation server to the application
server. The data is copied to a fixed length.
Structure Contents
SAP AG 1999
Delete:
Place the cursor on the row you want to delete and choose Delete row.
Copy:
Place the cursor on the row you want to duplicate and choose Duplicate row. The system duplicates
the row and adds it to the structure.
Select block:
Place the cursor on the first row of the block you want to edit.
Choose Select block. The block is selected and now has a gray background.
Place the cursor on the last row of the block you want to edit.
Place the cursor on the row in front of the location where you want to add the copied or cut block
to.
Structure Contents
Record name
BGR00 Session record 0session1 003 ... BKNA1 Customers
BKN00 Header data 1 1XD01 Z-00-1000 Data record
BKNA1 Standard 2BKNA1 / John Field nameShort Description Field Contents
...
STYPE Record type 2
TBNAM Table name BKNA1
... ... /
SAP AG 1999
You can enter values for the individual fields in change mode. Most of the fields have input help.
Note: All fields that are not needed must be filled with the NODATA character.
...
BKNA1-ANRED CHAR 5 Title x K2TIL 5 M
BKNA1-NAME1 CHAR 35 Name 1 x K3NAM 30 M
BKNA1-SORTL CHAR 10 Sort field ? Must still be clarified
BKNA1-STRAS CHAR 35 Street x K3STR 30 M
BKNA1-PFACH CHAR 10 Post box x K4PFA 10 M
BKNA1-ORT01 CHAR 35 City x K4ORT 35 M
BKNA1-PSTLZ CHAR 10 Postal code x K4PST 10 M
BKNA1-SPRAS CHAR 2 Language I DE Always DE
M = Move
T = Table
I = Initial (fixed value)
P = Program
SAP AG 1999
Before you create test data the fields in the non-SAP system should be formatted and assigned to the
fields in the SAP system. This is best done in a table.
For the file created from the DX - WB, all fields are
automatically filled with the NODATA indicator.
/
/
/
/
/
SAP AG 1999
Fields in the SAP record layout structure that are not needed for data transfer, must be filled with the
NODATA indicator. This means that these fields or field values will not be used during data transfer.
If a field is not filled with the NODATA indicator, it will be transferred with the value SPACE. This
could create severe problems, as the SPACE value may overwrite existing values in the system.
Note: This only applies to batch input (BI) and direct input (DI).
0 Session header
2 Transaction data 1
2 Transaction data 2
SAP AG 1999
If you have selected an object that uses the SAP standard transfer program, it is checked against
the record layout structure.
If the file is in IDoc format, all the EDI inbound processing checks are carried out.
If a BAPI is used for the transfer, so that non-processed objects can be stored in an IDoc in R/3,
your file must be free of errors. If you save objects with errors to a file, you can ignore all the
messages about missing inbound partner profiles.
BEGIN_SEGMENT_SECTION COBOL
BEGIN_DXOB 00500000 X(12) VALUE SPACE.
. . .
BEGIN_GROUP 1 Mapping Tool
LEVEL 02
STATUS MANDATORY
...
BEGIN_SEGMENT BGR00
LEVEL 02 Description of
STATUS MANDATORY segment BGR00
...
BEGIN_FIELDS
NAME STYPE
Field descriptions
TEXT Record type for BI interface
...
NAME GROUP
TEXT Queue group name
...
NAME MANDT
TEXT Client
...
NAME USNAM
TEXT Queue user ID / historically
determined
...
NAME NODATA
TEXT No batch input for this field
...
SAP AG 1999
After you choose Structure Display, a list of information about all included structures and fields
appears. You can download this list to your PC.
Some external mapping tools use this list for defining and generating the SAP target structures
during conversion.
Structure Generate
External System
COBOL
X(12) VALUE SPACE.
. . .
ABAP
ABAP Program
Program
Transfer Program
ABAP Dictionary
External Structure Definitions
External Data
COBOL
COBOL Include
SAP Structure
St Definitions
PL/1
PL/1
C
C
RPG
RPG
Choose Language
SAP AG 1999
After you choose Structure Generate you can translate SAP Structures (stored in the ABAP
Dictionary) into other programming languages, such as Cobol, and store them in the file system as
Include files.
For this process, the SAP System supports the creation of transfer programs in C, COBOL, PL/1, and
P_RPG. You use the ABAP program RDDSRCG0 to generate the structure descriptions in the
relevant programming language.
Structure
Structure for
for programming
programming language
language COBOL
X(12) VALUE SPACE.
. . .
Programming language
COBOL
PL/1
C Generates SAP
P_RPG structures in the
selected programming
Table selection language
Data transfer object 0050
Activity type
SAP AG 1999
SAP AG 1999
File: BC420_DEB_##.TES
Subproject: DEB_##
Run: CT_TEST_##
Load Program: SAPBC420_PRPD_RFBIDE00_CT
1 First do the mapping (assignment of the fields) on a piece of paper. The external data
should be mapped onto the record layout structure of program RFBIDE00. Afterwards
a test data record must be generated using this mapping plan in the DX-WB. Create the
run CT-TEST-## in the DX-WB and test the data record.
1-1 The database from the legacy system contains the following fields:
1-2 Create the mapping plan for the record layout structure of program
RFBIDE00. The following list contains the necessary record layout structures
and the most important fields :
BGR00, BKN00, BKNA1, BKNB1
1-3 Assign the fields of the legacy system to the fields of the SAP record layout
structure (mapping). For assistance use the online transaction and read the field
descriptions of the fields. Use the following abbreviations for the conversion
method:
- F: Fixed value
- V: Variable
- M: Move
- M+C: Move + Convert
1-4 Under Coding/Comment fill in the necessary field value or the Rule/Comment.
4 Use the transaction FD03 (Display debtor) to check if the debtor has been created
correctly.