BC420_46C - 010Data Transfer Using EDI

8/11/2019 BC420_46C - 010Data Transfer Using EDI

1/56

0

SAP AG 1999

EDI / IDoc basics

Data transfer using LSMW and IDocs

IDoc administration

Contents:

Data Transfer Using EDI

SAP AG BC420 10-1


2/56

0.2

SAP AG 1999

Describe data ec!ange using IDocs

Transfer data in LSMW using IDocs

Carr" out t!e re#uired administrati$e ste%s for

IDoc transfer

&t t!e conc'usion of t!is unit "ou (i'' be ab'e to:

Data Transfer Using EDI: Unit )b*ecti$es

SAP AG BC420 10-2


3/56

0.+

SAP AG 1999

Course )$er$ie( Diagram

Daten,berna!me

D- Worbenc!

LSM Worbenc!

rinci%'es of Standard

Data Tansfer

DirectIn%ut

&I

T&1

ecorder

Course )$er$ie(

0atc!

In%ut

Ca''Transaction

+

EDI

asics

3

4 506

6

55

57

5+

52

55

52

5

2

505055

7

SAP AG BC420 10-3


4/56

0.7

SAP AG 1999


EDI / IDoc asicsEDI / IDoc asics

LSMW and IDocsLSMW and IDocs

IDoc &dministrationIDoc &dministration

SAP AG BC420 10-4


5/56

0.3

SAP AG 1999

E'ectronic Data Interc!ange

Company 2Company 1 Data exchange with

EDI

EDI stands for Electronic Data Interchange and describes the electronic exchange of structured

business data between the different applications.

SAP AG BC420 10-5


6/56

0.8

SAP AG 1999

Unternehmen-2

R/3

S&

documents

External

system

Eterna'

documents

R/3 System

Electronic data

exchange

IDoc conce%t

synchrono!s

IDoc Conce%t

Unternehmen-1Com%an" 5

Com%an" 2

IDoc is an SAP standard format for exchanging data between systems. IDoc stands for intermediate

document.

It has two important concepts:

Message-oriented the data is also in the applications! but in different formats "the application

documents#. $he IDoc format unites the different formats of the applications. It is irrele%ant whether

the applications ha%e been programmed by SAP or by a different software %endor.

Asynchronous &efore an application document is created! data may already be present in the IDoc.

$his is important if! for example! data containing errors has been transferred. $he application

document should only be created! if the data in the IDoc has been corrected.

$he IDoc format used for EDI is an EDI standard. $he translation into other EDI standards has the

ad%antage that you can communicate with more than one partner. 'ithin the ()* System only IDoc formats are used. $he EDI subsystem handles all the con%ersions

into other EDI standards. $his has the ad%antage that SAP applications only ha%e to +now the IDoc

format and not possibly se%eral EDI standards this ma+es it easier to maintain the programs.

SAP AG BC420 10-6


7/56

0.

SAP AG 1999

R/3

S&

documents

External

system

Intermediate

Documents

EDI subs"stemEterna'

documents Converter

R/3 System

EDI

EDI asics

Unternehmen-1

Unternehmen-2

Com%an" 5

Com%an" 2

$he EDI architecture consists of:

EDIenabled applications: they support automatic processing of business processes.

IDoc interface: de%eloped as an open interface consisting of IDocs "intermediate documents# and

function modules that ma+e up the interface to the application.

EDI subsystem: con%erts the IDocs into EDI messages and %ice %ersa. $his element of the EDI

architecture is not pro%ided by SAP.

$he main component of the IDoc interface is the IDoc type. IDoc is an SAP standard that specifies

the structure and the format of the data to be transferred. It has been de%eloped using the standards

EDI,A-$ and ASI /01. -ontrol records enable IDocs to be uni2uely identified. $he status records

record the IDoc status on its way from the application to its trading partner.

SAP AG BC420 10-7


8/56

0.4

SAP AG 2001

R/3

"andelsgesellscha#t

$I%I%E-1 Electronic DataInterchange

EDI subs"stem

R/3

"andelsgesellscha#t

$I%I%E-2

%E !sing IDocs

EDI messages

External system

EDI and &LE

Commercia' com%an"

branc! 5

Commercia' com%an"

branc! 2

$wo concepts need to be defined here:

EDI: Electronic data exchange between different autonomous enterprises

A3E: Electronic data exchange between different application systems within your own

enterprise.

Systems can either directly exchange IDocs "e.g. ()* with ()*# %ia A3E or %ia EDI subsystems or

con%ert data into other EDI standards and then exchange it. $he application that wants to use EDI

must be IDocenabled. $his means that the application must be able to write)read its own data

to)from an appropriate IDoc type.

Example:

$o sa%e processing costs! branch 1wants to exchange ,I documents using IDocs with branch 2. Alsobranch 0 wants to send ,I documents %ia EDI to an external system.

SAP AG BC420 10-8


9/56

0.6

SAP AG 2001

IDoc

&he control record contains

administrati'e in#ormation -

sender( recei'er and

message)

Contro' recordIDoc ID, partner, IDoc type and

message, external structure

Data record

Status record

Control part with segment

names (for structuring the

following application data)

IDoc ID, messages

&he data records contain

the segments and

administrati'e in#ormation

a*o!t the segments)

&he stat!s records contain all

the processing stat!ses and

messages etc)

IDoc Structure

Each IDoc in the SAP database consists of :

precisely one control record!

data records! that include application data in their segments and describe the hierarchy in

which these segments are organi4ed in the Idoc! and

status records! that record the processing steps of the IDoc.

An IDoc that is transferred with an external system does not contain any status records.

An important part of the control recordis the IDoc ID that is assigned internally in the system. $he

ID is uni2ue.

Status confirmation messages "from the external system# always refer to this number. $he controlrecord includes the +ey fields of the partner profiles and the last processing status.

$he data records consist of the control part and the application part. $he unstructured part of the

application data gets a structure from the segment name in the control part. $he data type of the

segment fields is character.

$he status records log stages that an IDoc has passed through! for example! created5 or ready for

dispatch5. It is therefore important information for monitoring and communication purposes. $he

external system "next system# sends bac+ status confirmations %ia the processing stations about

inbound IDocs into that system. $he status confirmations only contain status records "for port type

file5#. If the status confirmation reports communication errors! exception handling begins. A

wor+flow may be triggered whereby the responsible persons will be informed.

SAP AG BC420 10-9


10/56

0.50

SAP AG 1999

FIDCCP01

E1FIKPF

E1FISEG

E1FISEC

E1FISET

+asic type, Complete $I doc!ment

Doc!ment header

osition data #or $I doc!ment

Data #or a one-time c!stomer / 'endor

Control data #or $I doc!ment

E1FINBU $I-R data

Structure of an IDoc Data 1ecord

I!" t#$es

9ierarc!" dis%'a")b*ect name FIDCCP01

A business process usually corresponds to a specificIDoc typethat holds the data for the process.

An IDoc type is defined by its segments and the segment hierarchy! order! and whether they are

repeatable. $his information is stored in the control part of the data records.

$he segment hierarchy can be displayed in a tree with some segments as children of parent segments.

$his allows you to arrange the application data.

$he IDoc types deli%ered from SAP are called basic types! which can be combined with customer

enhancements according to set rules.

$o display the layout of an IDoc type! go to the EDI &asis menu "'E*6 transaction 7 $ools

&usiness -ommunication IDoc &asis IDoc $ypes# and chooseDisplay tree.

$he example shows a part "simplified# of the basic type ,ID--P60 ",I document#.

SAP AG BC420 10-10


11/56

0.55

SAP AG 1999

FIDCCP01

E1FIKPF

Segment fields

E1FISEG

E1FISEC

IDoc: Complete FI documentBasic type released Released as of Release 31I Display for release

Version 3 of IDoc record types: IDoc record types SAP Release 4!

FI"ID#C: documment $eader %complete document&

Se'ment definition ()FI*PF!!) Released as of Release 4+A

re,uired min-ma. !!!!!!!!!1-!!!!!!!!!1

FI"ID#C: item data

FI"ID#C: data

BUKRS /lo0al uni,ue company codeInternal len't$ !!!!!+ (.ternal len't$ !!!!!+ #ffset !!!!+3

Data typeCAR Data element B2*RS/#B

Company codes t$at

...

...

$ield descriptions o# segment #ields

optional min-ma. !!!!!!!!!1-!!!!!!!555

.ptional segmentossi*le n!m*er o#

these segments

optional min-ma. !!!!!!!!!1-!!!!!!!555

T!e IDoc asic T"%e

$he example shows an extract of the basic type 5,ID--P605 ",I document#. " $ransaction: 'E8*#.

SAP AG BC420 10-11


12/56


13/56

0.5+

SAP AG 1999

IDoc and Message T"%e ?5@

%ast name $irst name

Stra0e Stadt Region

User ID System ro#ile

IDoc t"%e EMIA=05

Message t"%e

EM&DD

Message t"%e

EMSBS

Employee

Smit! T!omas Smit! T!omas

D52+7 T70 &dmin

Em%'o"ee s"stem %rofi'e

Street City Region

1ose &$e Ae( Bor 05

IDoc

Instantiate Instantiate

Em%'o"ee address

IDoc

IDoc types are no more than data structure descriptions. $he IDoc type EPI, contains all the

information about an employee.

essage types are %iews of an IDoc type.

essage type EPADD is a %iew of the employee?s address data.

essage type EPS@S is a %iew of the employee?s system authori4ations.

If data is a%ailable in this form "e.g. in a file or table#! it is +nown as an an IDoc.

SAP AG BC420 10-13


14/56

0.57

SAP AG 1999

IDoc and Message T"%e ?2@

IDoc t"%e EMIA=05 IDoc t"%e EMIA=02

&ype

1e'ease 7.0 1e'ease 7.8

R/3 R/3

1e'ease 7.01e'ease 7.8

IDoc t"%e EMIA=05

Message t"%e EMSBS

IDoc t"%e EMIA=02

Message t"%e EMSBS

artner & artner

artner %rofi'e for & artner %rofi'e for


Stra0e Stadt Region


Street City Region


Stra0e Stadt Region


Street City Region

Message t"%e

EMSBS

In different releases a message type can refer to different IDoc basic types.

SAP AG BC420 10-14


15/56

0.53

SAP AG 1999

artner rofi'e: )utbound

ort 5

/tm%/fi'e


16/56

0.58

SAP AG 2001

R/3

R/3

P!st d!"ument

C%e"& $artner

'ind $!rt

Create 5 master

IDoc

Communication

IDocs

IDoc Settings for Data Dis%atc!

+ranch 2+ranch 1

$he data flow is always obser%ed from the standpoint of the ()* System. So if data is sent from the

()* System to an external system using IDocs! this is +nown as outbound processing.

;utbound processing includes posting the application document! creating the associated outbound

IDoc "for A3E distribution! possibly se%eral communication IDocs#! finding the business partner and

the port! and transferring the IDoc through the port to the external system.

In the exampleBranch 1has to define its outbound IDoc interface:

In the port description &ranch 0 defines the system to which it want to send the IDocs and the

technical settings.

In the partner profiles branch 1 specifiesbranch 2 as the partnerfor the message ,ID--0and

enters the defined port. "In the ()* System created outbound IDocs! also called communicationIDocs can be archi%ed in the company and then deleted from the system.#

SAP AG BC420 10-16


17/56

0.5

SAP AG 1999

+ranch 2+ranch 1

IDoc interface &LE ser$ices

Business (!r&)*!+

S& a%%'ication

2 1

&%%'ication IDoc

Communication

IDocs

rinci%'es of Inbound rocessing

R/3Document

'hen data is recei%ed from an external system and processed in ()*! it is +nown as inbound

processing. IDocs are passed to the IDoc interface and sa%ed in ()*.

Data can be processed in the following ways:

0# $he direct wayusing a function module that transfers the IDoc data into the application

document.

$his is +nown as 5direct inbound processing5.

A3E ser%ices can pro%ide data filtering and %ersion handling! if re2uired.

;nly the IDoc processed by A3E ser%ices is sa%ed in the database. $his is the application IDoc.

1# $he indirect way using SAP &usiness 'or+flow. Depending on the partner profile settings the

IDoc is con%erted into a document and transferred to the application.

SAP AG BC420 10-17


18/56

0.54

SAP AG 1999

!"ument

C%e"& $artner

C%e"& $!rt

,rr!r %and*in

Aot )

Create

a%%'ication IDoc

IDoc Settings for 1ecei$ing Data

R/3CommunicationIDocs

+ranch 2+ranch 1

Inbound processing includes transferring the IDoc data from the external system through the inbound

port! creating the inbound IDoc! finding the correct application processing using the partner profiles

and posting the application document.

If there are errors! error handling "more general exception handling# starts. Exception handling is a

separate process and is not part of inbound processing. $here is also exception handling for outbound

processing! but this is less important. In outbound processing you can assume that the data being sent

is consistent.

In the example branch 2has to define its IDoc interface:

$he name of the port must be defined in the port description! so that IDocs can be accepted by

the ()* System. In the partner profilesbranch 2specifies branch 1as the partner for the inbound processing and

specifies message ,ID--0. $he names of the processors "in your own company# responsible for

the partner and the message are also specified.

SAP AG BC420 10-18


19/56

0.56

SAP AG 1999

Error 9and'ing for IDocs

hat can yo! do i# an IDoc has not *een processed

&hese steps are carried o!t *y the %S

IDoc (it! error

Set de'ete indicator

&rc!i$e de'ete

1e%air IDoc

1esubmit

Co%"

If the data of an IDoc cannot be posted! the IDoc can be repaired and resubmitted. $he repaired IDoc

is assigned a new status "IDoc status 8#. $he original IDoc is assigned a new number and the newly

copied IDoc is assigned the old number.

@ou can delete IDocs only in archi%ing. After setting the deletion flag! IDocs can be archi%ed and

then deleted from the system. $his is only possible from the integrated inbox or from &usiness

'or+place.

IDocs can only be processed in the foreground for certain messages "internally transactions are

called using 5-all $ransaction#. $his depends on the process code that usually points to a function

module.

SAP AG BC420 10-19


20/56

0.20

SAP AG 1999

EDI / IDoc asicsEDI / IDoc asics

LSMW and IDocsLSMW and IDocs

IDoc &dministrationIDoc &dministration


SAP AG BC420 10-20


21/56

0.25

SAP AG 1999

Maintain ob*ect attributes

Maintain structures and source fie'ds

Maintain structure re'ations

Maintain fie'd ma%%ing and con$ersion ru'es

1ead data

Con$ert data

Start IDoc creation

Start IDoc %rocessing

Create IDoc o$er$ie(

Start IDoc %ost%rocessing

S IDoc

str!ct!re

IDoc

Maintain Ste%s for Data Transfer (it! IDocs

$o transfer an IDoc with the 3S'! the wor+ steps shown abo%e are re2uired.

SAP AG BC420 10-21


22/56

0.22

SAP AG 1999

Maintain )b*ect &ttributes IDoc

Standard atc!/Direct In%ut

atc! In%ut 1ecording

&I

IDoc

./e"t t#$e and im$!rt

te"%niue

I!" intermediate d!"ument

essae t#$e

Basi" t#$e

,n%an"ement

'ICC1

'ICCP01

&I

Select the obBect type and the import techni2ue. If you select ,C help on the input field you can select

rele%ant obBects from the list displayed.

If you select the import techni2ueIDoc! when it is sa%ed! the system chec+s whether a partner profile

already exists for the default partner and selected message type. If a partner profile does not exist! the

system attempts to create one.

Port and partner profiles are explained later.

SAP AG BC420 10-22


23/56

0.2+

SAP AG 1999

Maintaining Source Structures and Source =ie'ds

Source Structures

E!D

P"SI

Document $eader

Document position

Source Fields

E!D

SET1 C#001$ Record ID

REF C#00%$ Reference num&er

P"SI

SET' C#001$ Record ID

KE( C#00)$ Ke*

:

:!CC"UNT C#00+$ !ccount

!,"UNT !,T1#01%$ !mount

So!rceStr!ct!res

So!rce $ields

In this step! you define the obBect structures including their names! descriptions! and hierarchical

relationships. @ou then create and maintain fields for these structures.

In the dialog box! choose Change. @ou can now choose to create new structures! or change!

rearrange! or remo%e these.


24/56

0.27

SAP AG 1999

Maintaining Structure 1e'ations

Structure Rel-tion

E1FIKPF FI.ID"C/ Document e-der#comlete document$2222 E!D

E1FISEG FI.ID"C/ Position d-t- 333of FI document 2222 P"SI

E1FINBU FI.ID"C/ FI.!P4 FI.!R d-t- 333 of FI document

E1FISEC FI.ID"C/ D-t- for one.time customer 5 6endor #coml3 document$

E1FISET FI.ID"C/ Control d-t- for coml3 FI document

&his is where so!rce str!ct!res are assigned to

target str!ct!res in the IDoc

S IDoc

Str!4t!r

$he structure relations define the relationships between the source and target structures.

$he possible target structures are set when the obBect type and import method are selected.


25/56

0.23

SAP AG 1999

S%ecia' IDoc C!aracteristics for =I Documents

T!ere must be a crosss"stem com%an" code ?&LE@

Determine t!e transaction t"%e

=i'' ;/L account number (it! 'eading eros

Set debit/credit indicator

=i'' transaction t"%e for genera' 'edger

S%ecif" ;/L account number

$ield mapping

hen !sing IDocs to trans#er doc!ments there are alwaysspecial characteristics to pay attention to,


26/56

0.28

SAP AG 1999

CrossS"stem Com%an" Code

Crosss"stem com%an" codes are used for &LE distribution

in financia' accounting.

In t!e distributed en$ironment t!ere is %recise'" one centra'

s"stem for eac! crosss"stem com%an" code.

& com%an" code must be assigned to t!is crosss"stem

com%an" code on eac! s"stem in t!e distributed

en$ironment.

Basis C!m$!nents

istri/uti!n A,

!de**in and Im$*ementin Business Pr!"esses

Cr!ss-A$$*i"ati!n Settins

G*!/a* .raniati!na* nits

Cross-System Company Codes

. . .. . .

$ield mapping

'hen a message with company code dependent data is dispatched "in an A3E scenario#! in all the

company code fields the company code is replaced with the crosssystem company code. 'hen the

message is recei%ed in the target system! the re%erse con%ersion ta+es place.

SAP AG BC420 10-26


27/56

0.2

SAP AG 2001

Setting U% CrossS"stem Com%an" Code

niue "r!ss-s#stem "!m$an#"!des

Assinment !) "r!ss-s#stem "!m$an# "!de

t! "%art !) a""!unts

Assinment !) "!m$an# "!de t! "r!ss-s#stem

"!m$an# "!de

1

2

3

CrossS"s CC

Com%C Com%an" Aame

SAP AG

Location

CrossS"s CC Target C!rt&cc

G0001

G1000

(a**d!r)

CrossS"s CC

0001 G0001

I:

I:

G0001

G1000

$ield mapping

Acti%ities:

0.# -reate the crosssystem company code.

1.# Assign the crosssystem company code to the chart of accounts that the crosssystem company

code is also assigned to on the central system "see definition of an A3E central system#. $his

setting is re2uired on the decentral system to determine the chart of accounts of the company

code on the central system.

*.# Assign the crosssystem company codes to the local company codes. Specify the names of the

associated crosssystem company code for the indi%idual company codes.

SAP recommends you choose the same names for the company code and the crosssystem company

code.

SAP AG BC420 10-27


28/56

0.24

SAP AG 1999

Con$erting ;/L &ccount Aumbers

e1fiseg.s-7nr 8 osi.-ccount3

C!99 FUNCTI"N :C"N;ERSI"N000500000 500000

Source &ccount Target &ccount

5eros added

$ield apping

-on%ersion exit A3P=A! external internal:

A3P=A con%ersion is used in particular for account numbers. During con%ersion from the external

to internal format! the system chec+s whether the input in the IPE(SI;JE/I$JA3P=AJ;


29/56

0.26

SAP AG 1999

S%ecif"ing rocess Code / DC Indicator

&ransaction type #or general ledger

;.


30/56

0.+0

SAP AG 1999

Document Currencies

Document currenc" ?E5=I>=W&E1S@

Loca' currenc" ?E5=I>=9W&E1@

&mount in 'oca' currenc" ?E5=I>=DMT1@

&mount in doc. currenc" ?E5=I>=W1T1@

...570.46... +750.30....

DEM

570.46

UAI

+750.30

$ield mapping

IDoc str!ct!re E2$ISE62

IDoc str!ct!re E2$I7$2

...DEM... UAI...

$o transfer a document using an IDoc! two currency fields and two amount fields must be filled.

SAP AG BC420 10-30


31/56

0.+5

SAP AG 1999

(A,


32/56

0.+2

SAP AG 1999

rocessing Times in LSMW


33/56

0.++

SAP AG 1999

osition Counter

FFG.BAFA:AFF G*!/a* data de)initi!n

C!de= A:A= $!sF"!unter *i&e

,1'IS,G-B,I Ha*ue 0

$ield apping

FFB,GIF.'F 0

FFB,GIF.'F $!sF"!unter 1

E1$I7$ Segment

E1$ISE6 Segment

C!ooseExtras -8 Display 'ariant,

S!o( tec!nica' fie'ds and %rocessing times.

B,I P!stin r!+ num/er +it%in d!"ument

C!de= ,1'IS,G-B,I > $!sF"!unter


34/56

0.+7

SAP AG 1999

Maintain ob*ect attributes

Maintain source fie'ds and structures

Maintain structure re'ations!i%s

Maintain fie'd ma%%ing and con$ersion ru'es

1ead data

Con$ert data

Start IDoc creation



Start IDoc %ost%rocessing

Continuing t!e rocess

$he highlighted steps must now be executed.

SAP AG BC420 10-34


35/56

0.+3

SAP AG 1999

1 D"CU,ENT BC10000011%%%0>?0 0> 1%%%0>?1 1%%%0>?0 D, ' P"SI P000)S100000 ?)103@0 1>)03A% Info 1 ? P"SI P000@11?100 ?00@3@0 1@?+3)1 Info ' ) P"SI P000@S110000 )0@ '0)3)A Info ? @ D"CU,ENT BC100000'1%%%0>?0 0> 1%%%0>?1 1%%%0>?0 D, + P"SI P000)S100000 ?)'03@0 1>)?3)@ Info 1 > P"SI P000@11?100 ?0103@0 1@?A3%> Info ' 333

1ead Data

Field N-me Field Tet 333

SET1 Record indic-torP"STING

1ead data

9S,BC)'0.TESTD"CU Document.' KP+ 101133

;nce the external data has been read! it can be displayed from the 3S'. Different colors are used

for the document header and the item entries.

SAP AG BC420 10-35


36/56

0.+8

SAP AG 1999

1 EDI


37/56

0.+

SAP AG 2001

Start creating IDoc

Start IDoc Creation

=i'e containing con$erted data

&LE inbound %rocessing

D

Create IDocs on D

1ead fi'e

$he data con%erted earlier is now transferred to the IDoc interface. IDocs are created in the database.

SAP AG BC420 10-37


38/56

0.+4

SAP AG 1999

Start IDoc rocessing


&LE inbound %rocessing

D

1eads IDoc

Ca''s

Inbound function modu'e

Creates

=I

document

5

+

2

$he created IDocs are read one by one and the associated inbound function module is called. $his

chec+s the data is correct and writes it to the application tables. $he data "e.g. ,I document# has then

been created.

SAP AG BC420 10-38


39/56

0.+6

SAP AG 1999

ist !) I!"s

1 Sg S5 Message t"%e Far =ct. Ao.

51 'ICC1 24 A$$*i"ati!n d!"ument n!t $!sted

65 'ICC1 10 ,rr!r in A, serHi"e

69 'ICC1 1 I!" %as /een edited

70 'ICC1 2 .riina* I!" t%at +as edited

Status Descri%tion

IDoc Aumber Segm Date Time Direct. artner St. S!ort Descri%tion

000002006 4 09081999 16=56=23 In/!und SD DP!rt-1 70 .riina* I!" t%at J

000002007 4 09081999 16=57=54 In/!und SD DP!rt-1 70 .riina* I!" t%at J


Do!*le clic4ing on an IDoc ta4es yo! to the IDoc

display

Create IDoc )$er$ie(

@ou can %iew the status confirmation messages in the IDoc o%er%iew.

$he list arranges the IDocs by status number.

&y doubleclic+ing on a status number you can %iew the details of indi%idual IDocs.

SAP AG BC420 10-39


40/56

0.70

SAP AG 2001

Dis%'a"ing IDocs

IDoc 000000000000200

Data records

Status records

E5=I>=

Contro' record

E5=ISE;

E5=ISE;

E5=ISE;

35

82

87

30

Current status 35

Basi" t#$e

ire"ti!n 2 In/!und

=IDCC05

...

Partner num/er ort 5

Partner t#$e US

P!rt artner 5

Content of se'ected segment

:e"%ni"a* s%!rt teKt

=ie'd Aame =ie'd Content

B


41/56

0.75

SAP AG 1999

Dis%'a"ing an IDoc 1ecord

=ie'd Aame =ie'd Contents

B


42/56

0.72

SAP AG 1999

Editing IDocs

IDoc c-nges -re ritten to ted-t-&-se

ata re"!rd

B


43/56

0.7+

SAP AG 2001

Try posting again:

L0: Application document not posted

esubmit after !"E#EDI error:

L8: IDoc with errors added

80: Processing despite syntax error "inbound#

8*: Error transferring IDoc to application

8L: Error in A3E ser%ice

Ignore synta$ error:

86: Syntax error in IDoc "inbound#

eset status:81: Pass IDoc to application

Post:

8C: IDoc ready to be transferred to application

88: IDoc is waiting for predecessor IDoc "serialisation#

esubmit edited IDoc:

8: IDoc has been edited

Processing step for IDoc status

hich IDocs with

which stat!s are to

*e processed

#!rther

Start IDoc ostrocessing

In the IDoc postprocessing IDocs with a particular status are processed further this means they are

passed to inbound processing again. So ! for example! the IDocs edited and corrected earlier "all with

status 8# can be reprocessed.

SAP AG BC420 10-43


44/56


45/56

0.73

SAP AG 2001

Settins

'i*e $!rt

IDoc inbound %rocessing

ort 5

t


46/56

0.78

SAP AG 2001

orts

=i'e

ort 5

aintain P!rts

P!rt ort 5

es"ri$ti!n LSMW Demo

;ersi!n

I!" re"!rd t#$es SAP


47/56

0.7

SAP AG 1999

aintain Partner :#$e

artner t"%e Message

B

BP

I

S

S


48/56

0.74

SAP AG 2001

Partner $r!)i*es

Partner t#$e B

aintain Partner um/ers Partner num/er artner 5

Partner t#$e US

Maint. %ermitted %rocessors :e*e$%!n#

...

artner t"%e US

artner 5

C*assi)i"ati!n

:#$e

Pr!"ess!r 1)E1TS

anuae DE

artner ro'e Message t"%e

Message $ariant

3

Input parameter detail screen

=IDCC5

Maintain artner Aumbers

If an error occurs! a message is sent to the processor listed under 'rocessors

$his allows you to designate! per partner profile! who is notified if an error occurs.

SAP AG BC420 10-48


49/56

0.76

SAP AG 1999

IDoc Inbound arameters

:rier /# /a"&r!und $r!ram

P!st-$r!"essin= a**!+ed Inbound o%tions :e*e$%!n#

rocess code

Trigger immediate'"

Pr!"essin /# )un"ti!n m!du*e

'ICC1= 'I +%!*e d!"uments

essae Hariant

essae )un"ti!n

essae t#$e =IDCC5 is$at"% !) +%!*e 'I d!"uments

Partner t#$e US

Partner r!*e

Partner num/er artner5

ser

Partner

In*o!nd IDocs are processed immediately

=ID5

&y choosingDetail screen -$ Inbound para(eters you get to a screen where you can set the

inbound option )rigger i((ediately. Inbound IDocs are then passed directly to the application.

'ith )rigger by bac*ground progra( the IDoc is not passed to the application. Select the post

processing function from the 3S' "status 8C select IDocs#.

$he message type ,ID--0 is assigned to the process code 5,ID0. &ehind the concept process code

is a function module or wor+flow that reads the IDocs. &y using a process code you can replace old

processing with new processing in one step for any number of partners.

In the initial node of the IDoc interface you can display the process code for a message type.

"$ransaction 'E8C!Docu -$ process code#.

SAP AG BC420 10-49


50/56

0.30

SAP AG 1999

&cti$ate IDoc Inbound rocessing

A"tiHate I!" in/!und $r!"essin;

!cti6-te IDoc in&ound rocessing

(es NoC-ncel

&he e'ent recei'er lin4age #or IDoc in*o!nd processing is acti'ated here

$his function can also be called in -ustomi4ing for the IDoc interface "Implementation 9uide#

Basis-$Basis er+ices-$IDoc Inter,ace&

Inbound IDocs are first sa%ed in the database and then transferred to the applicationspecific inbound

processing.

$his transfer is triggered by an e%ent! except for the port type t(,-. $he processing standard tas+

"the e%ent recei%er# must therefore be lin+ed to this e%ent and the lin+age must be acti%ated.

'rinciples o, e+ent recei+er lin*age

If IDocs are recei%ed! they are first sa%ed to the database and then processed further in a second!

separate step "e.g. for the port type file#. $hey may be processed by the wor+flow concept of the

e%ent: if the IDocs are sa%ed in the database! an e%ent is triggered that then waits for its recei%er inthe system. $he recei%er " a function module# finds the e%ent and triggers the e%ent processing. It has

now recei%ed the e%ent and the e%ent no longer exists in the system. 'or+flow determines when the

recei%er searches for e%ents. Sa%ing and further processing are carried out at different times

"asynchronous processing#.

SAP AG BC420 10-50


51/56

0.35

SAP AG 1999

(!r&)*!+ Cust!miin

> t-&les -6-il-&le

Ho& for monitoring eceeded de-dlines is sceduledHo& for monitoring or7 item errors is sceduledSending to o&ects -nd R o&ects -cti6-tedEntries -re missing from te PD control t-&les

or7flo De6eloment En6ironmentCustomiing incomlete

Aut!mati" Cust!miin

Worf'o( Customiing

$he following entries for wor+flow -ustomi4ing must ha%e a green chec+:

'or+flow administrator maintained

'or+flow (,- destination fully configured

9eneric decision tas+ fully classified

Sending to obBects and =( obBects acti%ated

@ou can also start automatic -ustomi4ing.

$he item Nobs for monitoring wor+ item errorsF should be deacti%ated "not selected# ;therwise! the

()* System would continually attempt to post problem IDocs created during data migration. See

SAP ote 0C*8O.

$o test whether the (,- destination for the SAP &usiness 'or+flow is fully configured! choose )est

RFC destination. $he success message'ing success,ul should appear.

SAP AG BC420 10-51


52/56

0.32

SAP AG 1999

Describe data ec!ange using IDocs

Transfer data in LSMW using IDocs

Carr" out t!e re#uired administrati$e ste%s for

IDoc transfer

Bou are no( ab'e to:

Data Transfer Using EDI: Unit Summar"

SAP AG BC420 10-52


53/56

E$ercises

%nit: EDI

Topic: Transfer of &I documents using EDI

&asics of the IDoc processing

$ransfer of ,I documents using EDI technology

$ransfer legacy ,I documents in ()* using IDocs. $he tool youuse is the 3S'.

"'() pro*ect: +C,-//

'ubpro*ect: D0C%-//

0b*ect: ID0C-//

&ile 1ith documents in e$ternal format:

+C,2D0C223E!D2P0'."EG

$he ,I documents are a%ailable in the file &-C16JD;-J1J=EADJP;S.3E9 on the transportdirectory. $his file contains fi%e documents with three items each. $ransfer these data to thecorresponding IDoc structure using the 3S'. $hen transfer this file to the A3E inbound

processing. It generates IDocs in the database and processes them.

$ip: @ou will find the rele%ant information in the training course slides

SAP AG BC420 10-53


54/56

0 $he mapping plan has been set up for you. @ou will find the necessary mapping rules inthe Excel sheet. $he following target fields in the IDoc must be completed:

-rosssystem company code with 936660!

Document type "-on%ersion: 6K H SA#!

Document date!

Posting date!

-on%ersion date!

;ld document number!

-urrency +ey "-on%ersion: D H DE! Q H


55/56

1 -reate the obBect ID;-RR for the document con%ersion in 3S' under the proBect&-C16RR and the subproBect D;-


56/56

C ,ield apping:

C0 Do the mapping according to your mapping plan. @ou should consider thespecial features of the document transfer using IDocs "see training coursematerial#

C1 $he document item needs a se2uential number! which is not pro%ided in the

legacy data. =ence the se2uential number must be generated in the 3S'. Eachnew document header must be initiali4ed with 6 and counted up for each item.Proceed as follows:

InE/tras -$ Display +ariantacti%ate the global data definition and the

processing time times.

A counter needs to be created for the items under 9lobal Data:DA7A: Poscounter I*( (1FIS(/"B28(I VA2( !

At the time of JJ&E9IJ;,J(E-;(DJJ of the header record! the counter

must be reset to 4ero.

Poscounter 9 ! At the time of JJ&E9IJ;,J(E-;(DJJ of the item record! the counter

must be increased by one.Poscounter 9 Poscounter 1

Assign the field PosJcounter to the field E0,ISE9&