BC420_46C - 005Principles of Standard Data Transfer

8/11/2019 BC420_46C - 005Principles of Standard Data Transfer

1/14

0

SAP AG 1999

Tasks of standard data transfer

Documentation for data transfer

SAP record layout structure

Contents:

Principles of Standard Data Transfer

SAP AG BC420 5-1


2/14

0.2

SAP AG 1999

Obtain documentation on data transfer

Describe the rules for data formattin

!"plain the structure of an SAP record layout

At the conclusion of this unit# you $ill be able to:

Standard Data Transfer: %nit Ob&ecti'es

SAP AG BC420 5-2


3/14

0.(

SAP AG 1999

Course O'er'ie$ DiaramCourse O'er'ie$ Diaram

Daten)bernahme

D* +orkbench

,S- +orkbench

Principles of StandardData Tansfer

Direct.nput

/AP

TA0

ecorder

Course O'er'ie$

/atch

.nput

CallTransaction

(

!D

/asics1

3 406

40

5

44

4

4(

42

44

42

4

2

66

44

SAP AG BC420 5-3


4/14

0.

SAP AG 1999

Standard Transfer O'er'ie$

Flat SAP

Structure

SAP Record

Layout

Structure

SAP IDoc

Structure

/AP

The following describes the basics of data transfer in the standard system using the transfer programs

delivered from SAP.

SAP AG BC420 5-4


5/14

0.6

SAP AG 1999

nterfaces for Standard Data Transfer

-DAT7D

8/D!00

P%STD0099

88

----

SAP Record

Layout Structure

SAP Record

Layout Structure

SAP Record

Layout Structure

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


6/14

0.

SAP AG 1999

Con'ertin Data

Formatting

External format SAP format

Assignment

Conversion

SAP record

layout

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 5-6


7/14

0.1

SAP AG 1999

8ormattin

Typ C # P # 7T

4; 02>2000

Type C

Consider user

settings

%SD

External format SAP format

"f you use a transfer program# the external data must be formatted the same as for an online user who

enters the values using the $eyboard. The following rules apply%

The data must be in character format

The individual fields must not be longer than the defined SAP field.

"f 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 blan$ characters!.

&ote% "f you use 'AP"s and "(ocs for the transfer# there might be exceptions.

)or conversions user-specific settings must be ta$en into account e.g. fixed value settings in the user

profile! except for 'AP"s and "(ocs.*ser-specific settings are the date format and the decimal setting.

"f the data is transferred online# the authori+ations and fixed values of the user who is starting the

transfer are used.

A user must be specified for bac$ground processing. This user should have the same user-specific

settings. ,ccasionally this user might have different authori+ations# for example# in the production

system where the data is actually transferred.

&ote% (ifferent authori+ations and settings may result in errors when the data is transferred for

example# no authori+ation for the company code!.

SAP AG BC420 5-7


8/14

0.3

SAP AG 1999

-appin

How is te external

data ma!!ed to

te record layouts"

. . .

. . .

SAP Format SAP Record Layout

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

)or information about which structures are required and which are optional# see the documentation

for the record layout structures.

SAP AG BC420 5-8


9/14

0.5

SAP AG 1999

!"ample: ecord ,ayout Structure

Record Layout #y!es

Session Header

Transaction Header Data

#is is te next $atc in!ut

session

. . .

. . .

0

Transaction Data 1

Transaction Data 2


Transaction Data 1

Transaction Data 2

Session Header

4

2

2

4

0

Data for one data record

Data for one data record

The data records contained in the sequential file must be in a format that can be read by an SAP

standard transfer method.

/ach transfer program expects the file to be in this general SAP record layout format.

/ach record layout contains individual structures# each of which is defined in the A'AP (ictionary.

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.

"f a new session header is added to the structure# the existing session is closed and a new session is

generated.

SAP AG BC420 5-9


10/14

0.40

SAP AG 1999

!"ample: ecord ,ayout Type 0

Session header0

STYPE

GROUPMANDT

USNAM

START

XKEEP

NODATA

F!"# N$%! S&'() D!*+(,)' F!"# C')!)

R!+'(# ).,!

G('/, $%!C"!)

U*!( D

S)$() #$)!

K!!, "$

N' $)+& ,/)

0

*!**'1100

BC420-00

01012000

X

. . .

%I session name

Client in wic te session is to$e !rocessed

&ser for te $ac'ground !rocessing

Sould te session $e 'e!t after it

as $een correctly !rocessed"() DA#A flag

Session loc'ed until date s!ecified

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

&ote% "f the transfer is carried out in the bac$ground# the user specified in the session header for the

authori+ation chec$ is used. This means that the authori+ations and settings of the fixed values in the

user profile are used for chec$ing.

"f the stop indicator is set 1 232!# the processed session remains in the system# otherwise it is

deleted.

"n the field &,(ATA you specify the character that will later be used as the &,(ATA indicator.

SAP AG BC420 5-10


11/14

0.44

SAP AG 2001

!"ample: ecord ,ayout Types 4 and 2

STYPEGROUP

F!"# N$%! D!*+(,)' F!"# C')!)*

R!+'(# ).,!T$"! $%!

1 '( 2

4

2


Transaction Data

Record #y!eStructure

The number of record layout types and their structures differsaccordin to the selected application

Transaction header data

These structures hold data for one transaction. 4ou 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 $ey fields such as account group# company code $ey# 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. )or the transaction data# specify the

structure name in addition to the record type.

The structures for batch input are defined in the A'AP (ictionary# where you can display the

individual structures.

SAP AG BC420 5-11


12/14

0.42

SAP AG 1999

!"ample: ecord ,ayout Customer

BGR00

BKN00

0

42

2

BKNA1

BKNB1

BKNBK

BKNVA

BKNVK

BKNB5

BKNZA

BKNKA

BKNKK

BKNVV

BKNVD

BKNVI

BKNVL

BKNVP

BKNAT

BKNB

BIADDR2

BR!"

BR!12

2

2

2

2

2

22

2

2

2

2

2

2

2

2

2

2

*eneral customer dataHeader data for customers

Com!any code data

%an' details

Dunning data

+++

+++

/xample of the record layout structures of the customer transfer.

See the documentation for the description of the individual structures.

SAP AG BC420 5-12


13/14

0.4(

SAP AG 1999

Supported -ethods

8/D!008//,00

8/?00

CT

D

DocumentsCustomers


14/14

0.4

SAP AG 1999

Obtain documentation on data transfer

Describe the rules for data formattin

!"plain the structure of an SAP record layout

@ou are no$ able to:

Principles of Standard Data Transfer: %nit Summary

SAP AG BC420 5-14

BC420_46C - 005Principles of Standard Data Transfer

Documents

Transcript of BC420_46C - 005Principles of Standard Data Transfer