0

DX-WB Tools: Contents

 Editing files using the DX-WB

 Creating test data for the data transfer

 SAP AG 1999

© SAP AG BC420 5-1

0.2
DX-WB Tools: Unit Objectives

At the conclusion of this unit, you will be able to:

 Create files
 Change and display files
 Copy files
 Generate test data for data transfer

 SAP AG 1999

© SAP AG BC420 5-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 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.

© SAP AG BC420 5-3

0.4
DX-WB: Tools

Goto Analyse files and data structures

The object type

from the BOR

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 BC420 5-4

0.5
Function: Create File

 Creates initial file under specified path/file name

 File contains all the structures of the object

 Session header is filled

Field Name Initial Value

STYPE 0
GROUP Object name
MANDT Current client
USNAM Current user
START ..
XKEEP
NODATA /

 Structures are preassigned with “/”.

Exception:
Field Name Initial Value
STYPE 1 or 2
TBNAM Structure name

 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 BC420 5-5

0.6
Function: Create File with Data

 Needs a program that can create test data

 The program must be provided by the
application

File with the test data

(Overview: see appendix 01)

 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.

© SAP AG BC420 5-6

0.7
Function: Display/Change File

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

Structure editor enables the Name2 Name 2 /

individual structures to be ORT01 Ort Berlin
changed
LAND1 Land DE

... ... /

 SAP AG 1999

 The file display template contains the following information:

 The number of data records is displayed in the title. This shows how many transactions the transfer
file contains.
 The fields of the transfer object are displayed in predefined length and sequence for each structure.
So you can identify which fields of a structure are required in which length and sequence. By
double clicking on a structure line you can see the fields of the structure.
 The different hierarchy levels of a data record are indicated in different colors:

Hierarchy level 1:green

Hierarchy level 2:yellow
Hierarchy level 3: blue
Hierarchy level 4:gray
 You can print the transfer file (Table -> Print)
 Note that only the first 100 characters of each structure are displayed in the overview.
 Note: This functionality applies only for BI and DI.

© SAP AG BC420 5-7

0.8
Function: Copy File

Source Target

Application server Application server

Remote server Remote server
File type File type
File name File name
Presentation server Presentation server
File name File name

All the structures of the selected

transfer object can be copied

 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:

 Copy without converting

The data transfer file is coped unmodified

 Conversion of fixed length -> Delimited tabulator

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.

 Conversion of delimited tabulator -> Fixed length

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.

© SAP AG BC420 5-8

0.9
Structure Operations

Duplicate structure rows

Delete structure rows

Edit blocks in structure

Structure Contents

BGR00 Session header record 0Session1 003 ...

BKN00 Header data 1 1XD01 Z-00-1000
BKNA1 General 2BKNA1 / John
...

 SAP AG 1999

 You can edit the structure of an imported file as follows:

 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.

 Choose Copy or Cut.

 Place the cursor on the row in front of the location where you want to add the copied or cut block
to.

 Choose Insert clipboard.

© SAP AG BC420 5-9

0.10
Creating Test Data in DX-WB

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

Test data can be ...

inserted into the record Name1 Name 1 Smith
Search help
layout structure Name2 Name 2 /
ORT01 Ort Berlin
LAND1 Land DE

... ... /

 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.

© SAP AG BC420 5-10

0.11
Mapping Plan

Creating the mapping plan on paper

Target structure Source structure

Name Type Lg Description Name Lg Initial Notes

...
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.

© SAP AG BC420 5-11

0.12
NODATA Indicator

 The default NODATA indicator is “/”

 Enter the NODATA indicator in fields that do not need to be

transferred

 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).

© SAP AG BC420 5-12

0.13
Function: Check File

The file structure is checked in accordance

with the standard structure description

0 Session header

1 Transaction header data

2 Transaction data 1

2 Transaction data 2

1 Transaction header data

 SAP AG 1999

 You can check the structure of a file.

 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.

© SAP AG BC420 5-13

0.14
Record Layout - Displaying Structure (2)

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.

© SAP AG BC420 5-14

0.15
Record Layout - Generating Structure (1)

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.

© SAP AG BC420 5-15

0.16
Record Layout - Generating Structure (2)

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

Output 0050 is the

Name of output file customer
Local file system master
Generate alignment fields

 SAP AG 1999

 The displayed utility considerably simplifies conversion in the external system.

 You can select the data transfer object for extracting the structure definitions. This sets the required
SAP structures and creates them in a file in the programming language.

© SAP AG BC420 5-16

0.17
DX-WB Tools: Unit Summary

You are now able to:

 Create files
 Change and display files
 Copy files
 Generate test data for data transfer

 SAP AG 1999

© SAP AG BC420 5-17

 DX-WB Tools Exercises

Unit: DX-WB Tools

Topic: Creating test data

 Creating test data in the DX-WB.

The address data for debtors have to be transfered. To do this,

use program RFBIDE00. You have determined the fields or data
to be transferred, in the external system. Identify the appropriate
fields in the record layout structure.

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:

Field name Decription: Length: Type: Field value:

C_NO Customer number 4 Char 4537
NAME Customer name 30 Char George Miller
SEARCH Search term 20 Char Miller
C_TYPE Customer type 4 Char 0004
A_DATA Street 40 Char 2907 Eagle Drive.
B_DATA City 30 Char Los Angeles
ZIP Zip code 10 Char 92660
CO Country 2 Char US
SPO Language 1 Char E
TELF Phone no. 16 Char 925-644-944

© SAP AG BC420 5-18

 VAT Sales tax identification 20 Char 0302052345
number

Note: Use the necessary VAT no. for your country.

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.

For the assignment (mapping) of the data, the following is

applicable for the fields of the record layout structure:
1. The name of the session = Debitor-##
2. Client = Logon client
3. User name = BC420-##
4. Customer number = Z-##-2200
5. Company Code = 0001
6. Account group = KUNA
7. Transaction code = XD01
8. Country = convert from U to US
9. Reconciliation account = 120000
10. Create old debtor number in the field BKNB1-ALTKN
11. The field customer type in the legacy data is not needed.
12. All remaining fields from 1-1

© SAP AG BC420 5-19

2 Start the DX-WB and go to the DX-WB tools.
2-1 Create the empty file BC420_DEB_##.TES
Choose the following settings:
- Object type: KNA1
– Program type: BINP
- Program/Method: RFBIDE00
Note: Make sure you select the program type BINP and not REPO!
2-2 Delete the structures that are not needed (only the first four structures are
needed!)
2-3 Go to the structure editor. Copy the values from the list for a test data record.
2-4 Save the file before leaving the editor.
2-5 Check the structure (function: Check file)

3 Test the file in a run.

3-1 Create the run CT_TEST-## with the description Test with CT under your
project and the subproject DEB-##.
3-2 In the run CT_TEST-##, create the following task:
- Task: IMP_TEST-##
- Description: Test Transfer
- Task type: LOA
- Program type: REPO
3.3 Select the program SAPBC420_PRPD_RFBIDE00_CT.
Use the file name you created before: BC420_DEB_##.TES
3-4 Start the run and confirm the tasks manually.
3-5 Take a look at the log!

4 Use the transaction FD03 (Display debtor) to check if the debtor has been created
correctly.

© SAP AG BC420 5-20