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

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

0.+
SAP AG 1999
Course )$er$ie( Diagram
Daten,berna!me
D- Wor.benc!
LSM Wor.benc!
/rinci%'es of Standard
Data Tansfer
D
i
r
e
c
t

I
n
%
u
t
0&/I
T
&

1
e
c
o
r
d
e
r
Course )$er$ie(
0
a
t
c
!

I
n
%
u
t
C
a
'
'

T
r
a
n
s
a
c
t
i
o
n
+
EDI
0asics
2
3
4 50
6
6
55
57
5+
52
55
52
5
2
5050
55
7
SAP AG BC420 10-3

0.7
SAP AG 1999
Data Transfer Using EDI
EDI / IDoc 0asics
EDI / IDoc 0asics
LSMW and IDocs
LSMW and IDocs
IDoc &dministration
IDoc &dministration
SAP AG BC420 10-4

0.3
SAP AG 1999
E'ectronic Data Interc!ange
Company 2
Company 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

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-1
Com%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

0.2
SAP AG 1999
R/3
S&/
documents
External
system
Intermediate
Documents
EDI subs"stem Eterna'
documents Converter
R/3 System
EDI
EDI 0asics
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 A.SI /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

0.4
SAP AG 2001
R/3
"andelsgesellscha#t
$I%I%E-1
Electronic Data
Interchange
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 1 wants to exchange ,I documents using IDocs with branch 2. Also
branch 0 wants to send ,I documents %ia EDI to an external system.
SAP AG BC420 10-8

0.6
SAP AG 2001
IDoc
&he control record contains
administrati'e in#ormation -
sender( recei'er and
message)
Contro' record
IDoc 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 record is 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 control
record 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

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 specific IDoc type that 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 choose Display tree.
$he example shows a part "simplified# of the basic type ,ID--P60 ",I document#.
SAP AG BC420 10-10

0.55
SAP AG 1999
FIDCCP01

E1FIKPF
Segment fields

E1FISEG
E1FISEC
IDoc: Complete FI document
Basic 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 code
Internal len't$ !!!!!+ (.ternal len't$ !!!!!+ #ffset !!!!+3
Data typeC1AR Data element B2*RS3/4#B
Company codes t$at
...
...
$ield descriptions o# segment #ields
optional min-ma. !!!!!!!!!1-!!!!!!!555
.ptional segment
-ossi*le n!m*er o#
these segments
optional min-ma. !!!!!!!!!1-!!!!!!!555
T!e IDoc 0asic T"%e
$he example shows an extract of the basic type 5,ID--P605 ",I document#. " $ransaction: 'E8*#.
SAP AG BC420 10-11

0.52
SAP AG 2001
IDoc : ;ra%!ic Dis%'a"
"eader record always has the same str!ct!re
pplication data,
maxim!m 1/// *yte records
EDI<DC70 ...........=IDCC/05.......
E2=I>/=002
E2=I>/=002
E2=ISE;00+
E2=ISE;00+
E2=ISE;00+
E2=ISE;00+
E2=ISE;00+
E2=ISE;00+
IDoc *asic type
Str!ct!re name that determines
the str!ct!re o# the application
data
An IDoc always contains a header segment.
Each record contains six fields:
SE9.A: Segment
:A.D$ -lient
D;-.<: IDoc number
SE9.<: Segment number
PS9.<: Parent segment number
=3E>E3 =ierarchy le%el
In field SE9.A: the structure of the application data is described for each record.
IDoc principles:
$he fields in IDoc segments are of type -=A(.
.aming con%entions: a segment consists of an SAP releaseindependent segment type and at least
one releasedependent segment name. Segment types are structures in the A&AP Dictionary. $hey
begin with E0. Segment names begin with 5E15. An external system can recogni4e the segment
%ersion from the segment name.
SAP AG BC420 10-12

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 EM/IA=05
Message t"%e
EM/&DD
Message t"%e
EM/SBS
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 E:PI., contains all the
information about an employee.
:essage types are %iews of an IDoc type.
:essage type E:PADD is a %iew of the employee?s address data.
:essage type E:PS@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

0.57
SAP AG 1999
IDoc and Message T"%e ?2@
IDoc t"%e EM/IA=05
IDoc t"%e EM/IA=02
&ype
1e'ease 7.0
1e'ease 7.8
R/3 R/3
1e'ease 7.0
1e'ease 7.8
IDoc t"%e EM/IA=05
Message t"%e EM/SBS
IDoc t"%e EM/IA=02
Message t"%e EM/SBS
/artner & /artner 0
/artner %rofi'e for & /artner %rofi'e for 0
%ast name $irst name
Stra0e Stadt Region
User ID System -ro#ile
Street City Region
%ast name $irst name
Stra0e Stadt Region
User ID System -ro#ile
Street City Region
Message t"%e
EM/SBS
In different releases a message type can refer to different IDoc basic types.
SAP AG BC420 10-14

0.53
SAP AG 1999
/artner /rofi'e: )utbound
/ort 5
/tm%/fi'e<--.tt
/artner &
IDoc t"%e
Message t"%e
t1=C
R/3
FIXEDASSET_CREATEINCLVALUES
FIXEDASSET_CREATEINCLVALUES01
/ort 2
/artner 0
IDoc t"%e
Message t"%e



DEBMAS
DEBMAS02
Partners that communicate using IDocs must be defined in the partner profiles. =ere you choose
which message in which way is sent to the partner and how the inbound messages are processed.
&y assigning a logical message! you assign a business function to the IDoc type.
SAP AG BC420 10-15

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 example Branch 1 has 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 specifies branch 2 as the partner for the message ,ID--0and
enters the defined port. "In the ()* System created outbound IDocs! also called communication
IDocs can be archi%ed in the company and then deleted from the system.#
SAP AG BC420 10-16

0.52
SAP AG 1999
+ranch 2 +ranch 1
IDoc interface C &LE ser$ices
Business (!r&)*!+
S&/ a%%'ication
2 1
&%%'ication IDoc
Communication
IDocs
/rinci%'es of Inbound /rocessing
R/3
Document
'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 way using 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

0.54
SAP AG 1999
!"ument
C%e"& $artner
C%e"& $!rt
,rr!r %and*in-
Aot ).D
Create
a%%'ication IDoc
IDoc Settings for 1ecei$ing Data
R/3
Communication
IDocs
+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 2 has 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 profiles branch 2 specifies branch 1 as 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

0.56
SAP AG 1999
Error 9and'ing for IDocs
1hat can yo! do i# an IDoc has not *een processed2
&hese steps are carried o!t *y the %S31
IDoc (it! error
Set de'ete indicator
&rc!i$e C 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 8A#. $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

0.20
SAP AG 1999
EDI / IDoc 0asics
EDI / IDoc 0asics
LSMW and IDocs
LSMW and IDocs
IDoc &dministration
IDoc &dministration
Data Transfer Using EDI
SAP AG BC420 10-20

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

0.22
SAP AG 1999
Maintain )b*ect &ttributes : IDoc
Standard 0atc!/Direct In%ut
0atc! In%ut 1ecording
0&/I
IDoc
./0e"t t#$e and im$!rt
te"%ni1ue
I!" 2intermediate d!"ument3
4essa-e t#$e
Basi" t#$e
,n%an"ement
'ICC1
'ICCP01
0&/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 techni2ue IDoc! 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

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!rce
Str!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. <se the rele%ant pushbuttons to execute these functions.
If you are creating more than one structure! a dialog box appears which as+s you to define the
relationship between the structuresD are they e2ual "flat structure# or une2ual "hierarchical#E
Caution: @ou can only create one structure per recording for migration obBects created through a
recording of a transaction as there is only one flat target structure a%ailable per recording.
SAP AG BC420 10-23

0.27
SAP AG 1999
Maintaining Structure 1e'ations
Structure Rel-tion
E1FIKPF FI.ID"C/ Document 0e-der#com1lete 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 #com1l3 document$
E1FISET FI.ID"C/ Control d-t- for com1l3 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.
<sually there are target structures that must be selected "re2uired segmentsF#. $he system informs
you of this with the message $his structure must be selectedF.F
$o set structure relations! place the cursor on a field in the ()* structure or target structure. -hoose
Relationship. A dialog box appears with a list of the source structures you ha%e created. Select a
structure from this list.
If you want to change the relation! you must first delete the existing relation using the rele%ant
pushbutton.
A chec+ function is a%ailable to chec+ the structure relationships for errors. :essages for this chec+
are displayed in the status bar "error message or .o structure relations errors foundF#
SAP AG BC420 10-24

0.23
SAP AG 1999
S%ecia' IDoc C!aracteristics for =I Documents
T!ere must be a cross:s"stem com%an" code ?&LE@
Determine t!e transaction t"%e
=i'' ;/L account number (it! 'eading Eeros
Set debit/credit indicator
=i'' transaction t"%e for genera' 'edger
S%ecif" ;/L account number
$ield mapping
1hen !sing IDocs to trans#er doc!ments there are always
special characteristics to pay attention to,
<nli+e data transfer using batch input! when using IDocs other special fields ha%e to be included.
'hat fields these are depends on the IDoc type and the application.
SAP AG BC420 10-25

0.28
SAP AG 1999
Cross:S"stem Com%an" Code
Cross:s"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! cross:s"stem com%an" code.
& com%an" code must be assigned to t!is cross:s"stem
com%an" code on eac! s"stem in t!e distributed
en$ironment.
Basis C!m$!nents
istri/uti!n A5,
4!de**in- and Im$*ementin- Business Pr!"esses
Cr!ss-A$$*i"ati!n Settin-s
G*!/a* .r-ani6ati!na* 7nits
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

0.22
SAP AG 2001
Setting U% Cross:S"stem Com%an" Code
7ni1ue "r!ss-s#stem "!m$an#
"!des
Assi-nment !) "r!ss-s#stem "!m$an# "!de
t! "%art !) a""!unts
Assi-nment !) "!m$an# "!de t! "r!ss-s#stem
"!m$an# "!de
1
2
3
Cross:S"s CC
888
Com%C Com%an" Aame
888

SAP AG

Location
Cross:S"s CC Target C!rt&cc
G50001
G51000
888

(a**d!r)
Cross:S"s CC
0001 G50001
I9:
I9:
G50001
G51000
$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

0.24
SAP AG 1999
Con$erting ;/L &ccount Aumbers
e1fiseg.s-7nr 8 1osi.-ccount3
C!99 FUNCTI"N :C"N;ERSI"N<E=IT<!9P!<INPUT:
E=P"RTING
in1ut 8 e1fiseg.s-7nr
I,P"RTING
out1ut 8 e1fiseg.s-7nr 3
000500000 500000
Source &ccount Target &ccount
5eros added
$ield 3apping
-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 I.P<$ field is purely numeric!
possibly with space characters before or after the numbers. If yes! the character string is transferred
rightBustified into the output field ;<$P<$ and then filled in with 4eros "6# to the left of the
numbers. ;therwise! the character string is transferred leftBustified to the output field and filled with
4eros "6# to the right.
Examples: "Input and output fields each hold eight characters#
0. G01*C ? H G666601*C?
1. GA&-D ? H IA&-D ?
*. G 01*C ? H G666601*C?
$he process for con%erting from internal to external format "function module
-;.>E(SI;.JE/I$JA3P=AJ;<$P<$# is exactly the re%erse.
SAP AG BC420 10-28

0.26
SAP AG 1999
S%ecif"ing /rocess Code / D:C Indicator
&ransaction type #or general ledger
;.<G9 :ransa"ti!n t#$e )!r -enera* *ed-er
<u*e= C!nstant
C!de= ,1'IS,G-;.<G9 > ?<'B7@8
SABCG e/it D Credit indi"at!r
C!de= E:ar-et )ie*d ,1'IS,G-SABCG e/itDCredit ind8
I' e1)ise--/s"%* > ?50@8
e1)ise--s%&6- > ?A@8
,5S,8
e1)ise--s%&6- > ?S@8
,9I'8
Con'ersion r!le #or de*it / credit indicator
depends on posting 4ey
$ield 3apping
$o allow a document transfer through IDoc! the process code and debit)credit indicator must be
specified.
SAP AG BC420 10-29

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>/=:DM0T1@
&mount in doc. currenc" ?E5=I>/=:W10T1@
...5270.46... +750.30....
DEM
5270.46
UAI
+750.30
$ield mapping
IDoc str!ct!re E2$ISE6//2
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

0.+5
SAP AG 1999
(A,<S Curren"# &e#
S!ur"e= B,5,G-C7<<FB,G 2d!"ument "urren"#3
C!din-= $er)!rm *sm+Ftrans*ate
usin- ?(A,<S@ B,5,G-C7<<FB,G
"%an-in- ,1'IBP'-(A,<S8
Currencies for IDoc
A(A,< 5!"a* "urren"#
C!din-= ,1'IBP'-A(A,< > ?79I@8
4B:< Am!unt in *!"a* "urren"#
S!ur"e= P.SI-5.CA5FA4.79: 2am!unt in *!"a* "urr83
C!din-= ,1'IS,G-4B:< > P.SI-5.CA5FA4.79:
ECauti!n= S!ur"e )ie*d is *!n-er t%an tar-et )ie*d
(<B:< Am!unt in d!"ument "urren"#
S!ur"e= P.SI-.CFA4.79: 2am!unt in d!"8 "urren"#3
C!din-= ,1'IS,G-(<B:< > P.SI-.CFA4.79:
$ield 3apping
SAP AG BC420 10-31

0.+2
SAP AG 1999
/rocessing Times in LSMW
<<G9"B!9<D!T!<<
<<BEGIN<"F<PR"CESSING<<
<<BEGIN<"F<TR!NS!CTI"N<<
<<BEGIN<"F<REC"RD<<
<<END<"F<REC"RD<<
/// ///
/// ///
<<END<"F<TR!NS!CTI"N<<
<<END<"F<PR"CESSING<<
/
r
o
c
e
s
s
0" data record
0" target structure
0" data record
0" target structure
Global data definitions: the label JJ93;&A3JDA$AJJ is displayed for global data definitions and
declarations. @ou can define %ariables! structures! tables etc. that you want to use in your own code
in the field mapping.
Processing times: @ou can add your own processing time code.
Processing time - meaning:
33B(/I63#F3PR#C(SSI6/33 %&efore start of data processing #
33B(/I63#F37RA6SAC7I#633 %&efore start of processing data of a transaction#
33B(/I63#F3R(C#RD33 %&efore using con%ersion rules for source structure#
33(6D3#F3R(C#RD33 %After using con%ersion rules for source structure#
33(6D3#F37RA6SAC7I#633 %After transaction has been processed3
33(6D3#F3PR#C(SSI6/33 %After data hads been processed#
SAP AG BC420 10-32

0.++
SAP AG 1999
/osition Counter
FFG5.BA5FA:AFF G*!/a* data de)initi!n 888
C!de= A:A= $!sF"!unter *i&e
,1'IS,G-B7C,I Ha*ue 08
$ield 3apping
FFB,GI9F.'F<,C.<FF Be)!re usin- "!nHersi!n ru*es
C!de= $!sF"!unter > 08
FFB,GI9F.'F<,C.<FF Be)!re usin- "!nHersi!n ru*es
C!de= $!sF"!unter > $!sF"!unter I 18
E1$I7-$ Segment
E1$ISE6 Segment
C!oose Extras -8 Display 'ariant,
S!o( tec!nica' fie'ds and %rocessing times.
B7C,I P!stin- r!+ num/er +it%in d!"ument
C!de= ,1'IS,G-B7C,I > $!sF"!unter
<se counter posJcounter to +eep trac+ of document position number. $his number must be
incrementally increased for each document position and assigned to the E1FIE!-B"#EI field.
SAP AG BC420 10-33

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 %rocessing
Create IDoc o$er$ie(
Start IDoc %ost:%rocessing
Continuing t!e /rocess
$he highlighted steps must now be executed.
SAP AG BC420 10-34

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 TeBt 333
SET1 Record indic-tor
P"STING<KE( Posting 7e*
!CC"UNT !ccount num&er
D"C<!,"UNT !mount in document currenc*
9"C!9<!,P"UNT !mount in loc-l currenc*
TE=T Descri1tion
Dis%'a" read data
1ead data
9S,CBC)'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

0.+8
SAP AG 1999
1 EDI<DC)0 EDI<DC)0 100 )3+! ' FIDCCP01
' E1FIKPF E'FIKPF00' 100 0000133 1G91000
? E1FISEG E'FISEG00? 100 0000'33 '
) E1FISEG E'FISEG00? 100 0000?33 '
@ E1FISEG E'FISEG00? 100 0000)33 '
+ EDI<DC)0 EDI<DC)0 100 )3+! ' FIDCCP01
> E1FIKPF E'FIKPF00' 100 0000133 1G91000
A E1FISEG E'FISEG00? 100 0000'33 '
% E1FISEG E'FISEG00? 100 0000?33 '
Con$erted Data
Field TeBt Field 6-lue
T!BN!, EDI<DC)0
,!NDT 100
D"CNU,
D"CRE9 )3+!
ST!TUS
333
ID"CT(P FIDCCP01
Con$ersion
/rogram
Dis%'a" con$erted data
Con$ert data
$he read data is now con%erted to the IDoc format. .ote: $his does not include the actual transfer
creation of an IDoc into the ()* database.
$he IDoc segments are indicated here in color.
SAP AG BC420 10-36

0.+2
SAP AG 2001
Start creating IDoc
Start IDoc Creation
=i'e containing con$erted data
&LE inbound %rocessing
D0
Create IDocs on D0
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

0.+4
SAP AG 1999
Start IDoc /rocessing
Start IDoc %rocessing
&LE inbound %rocessing
D0
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

0.+6
SAP AG 1999
5ist !) 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 A5, serHi"e
69 'ICC1 1 I!" %as /een edited
70 'ICC1 2 .ri-ina* I!" t%at +as edited
Status Descri%tion
IDoc Aumber Segm Date Time Direct. /artner St. S!ort Descri%tion
000088802006 4 0980881999 16=56=23 In/!und 7SD DP!rt-1 70 .ri-ina* I!" t%at J888
000088802007 4 0980881999 16=57=54 In/!und 7SD DP!rt-1 70 .ri-ina* I!" t%at J888
Create IDoc o$er$ie(
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

0.70
SAP AG 2001
Dis%'a"ing IDocs
IDoc 0000000000002002
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
=IDCC/05
...
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
B7B<S
B5A<:
B5A:
G50001
SA
19990730
B7A: 19990731
888
Content o# header segment
Do!*le
clic4
!"ument n!t 888
I!" $assed t! 888
I!" trans)er8888
I!" inserted
=ere the IDoc with the uni2ue number 166K and all the status messages created up to now are
displayed. $he status is arranged chronologically meaning that the last status created "in this case
number L0# was the last message reported.
;n the right hand side the contents of the selected segment E0,IMP, can be monitored.
&y doubleclic+ing on the segment icon a detailed list with the fields of E0,IMP, can be displayed.
SAP AG BC420 10-40

0.75
SAP AG 1999
Dis%'a"ing an IDoc 1ecord
=ie'd Aame =ie'd Contents
B7B<S
B5A<:
B5A:
B7A:
((,<:
LB59<

G50001
SA
19990730
19990731
19990730
BC1000002
S!ort Descri%tion

G*!/a* uni1ue "!m$an# "!de
!"ument t#$e
!"ument date in d!"ument
P!stin- date in d!"ument
C!nHersi!n date
<e)eren"e d!"ument num/er
I!" num/er
2002
Se-ment t#$e E5=I>/=
9um/er 5
Su$eri!r se-ment n!8 0
'I I!"= d!"ument %eader= 2"!m$*ete d!"ument3
Aierar"%# *eHe*
5
(A,<S ,4 Curren"# &e#
G5;.< <'B7 Business $r!"ess
A(A,< 79I 5!"a* "urren"#
888
#ter do!*le-clic4ing on the header segment icon( this detail display appears
3ist with the fields of segment E0,IMP,.
The IDoc data can be edited from this template.
SAP AG BC420 10-41

0.72
SAP AG 1999
Editing IDocs
IDoc c0-nges -re Dritten to t0e
d-t-&-se
ata re"!rd
B7B<S
B5A<:
B5A:
888

7ni1ue "r!ss-s#stem "!m$an# "!de
!"ument t#$e
!"ument date
=ie'd Aame
S!ort Descri%tion
;L0005
S&
566602+0
=ie'd Content
Data can now *e edited) new IDoc stat!s 9: is created)
888
C%an-e data re"!rd
@ou can change the data of the IDoc by choosing Data record -$ Display%change data record&
A copy of the old IDoc is created. $he old number is assigned to the new IDoc and a new number is
assigned to the old IDoc. $he IDoc with the number 166K is the newly copied IDoc.
SAP AG BC420 10-42

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:
8A: IDoc has been edited
Processing step for IDoc status
1hich IDocs with
which stat!s are to
*e processed
#!rther2
Start IDoc /ost:/rocessing
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 8A# can be reprocessed.
SAP AG BC420 10-43

0.77
SAP AG 1999
EDI / IDoc 0asics
EDI / IDoc 0asics
LSMW and IDocs
LSMW and IDocs
IDoc &dministration
IDoc &dministration
Data Transfer Using EDI
SAP AG BC420 10-44

0.73
SAP AG 2001
Settin-s
'i*e $!rt
IDoc inbound %rocessing
/ort 5
t<'C $!rt
I!" in/!und $r!"essin-
Partner t#$e US
Partner num/er /artner 5
4aintain $!rts
4aintain $artner t#$es
4aintain $artner num/ers
A"tiHate I!" in/!und $r!"essin-
(!r&)*!+ Cust!mi6in-
1
2
3
;
<
dministrati'e tas4s ha'e to *e carried o!t in IDoc
in*o!nd processing)
IDoc Inbound /rocessing from LSMW
&y choosing ettings -$ IDoc inbound processing you get to the 3S:' administration en%ironment
for IDocs. @ou can branch to the maintenance transactions for IDoc processing.
IDoc inbound processing settings are proBectdependent as of 3S:' %ersion 0.K. $his means that
the settings for the selected 3S:' proBect are maintained on the initial screen. In %ersions before
0.K the settings are %alid for all proBects.
SAP AG BC420 10-45

0.78
SAP AG 2001
/orts
=i'e
/ort 5
4aintain P!rts
P!rt /ort 5
es"ri$ti!n LSMW Demo
;ersi!n
I!" re"!rd t#$es SAP <e*ease 48K
8 8 8
P%#si"a* dire"t!r#
8 8 8
'un"ti!n m!du*e
,K$!rt )i*e
888 Im$!rt )i*e E%ort fi'e Status )i*e
D:GusrGsa%Gtrans
,K$!rt)i*e8tKt
CPI-C
Internet
L45
888
1
Maintain /orts
Ports are channels through which IDocs are exchanged. $he IDoc interface supports fi%e different
exchange methods "port types#: ,ile! transactional (,-! -PI-! Internet! and the programming
interface PPS.
,or port type ,ileF! IDocs are written to files at the operating system le%el! where the recei%ing
system can read the files. @ou can start the recei%ing system here using synchronous (,-. In
addition to IDocs! you can also use files to exchange status records.
$he port description of the file includes the file name and path: ;nly the export file is important as
the name and location of the file is determined by the recei%ing system when IDocs are imported or a
status is returned. If you enter parameters for the input IDocs and status file! test tools can generate
default %alues. $he port must exist! e%en if it is only used for the import file! as the IDoc interface
only accepts ports it recogni4es.
SAP AG BC420 10-46

0.72
SAP AG 1999
4aintain Partner :#$e
/artner t"%e Message
B
BP
B7
5I
5S
7S
888
888

<',:,S:P
<P7B,952
<S,:,S:P
<S,:,S:P
<B5SCA,CB
<S,:,S:P
=orm routine

<,AF:012
B,9P<.;
<,AFB9A1
<,AF5'A1
5.GSGS
<,AF7S,<
Descri%tion

Ban&
,m$*!#ee /ene)its $r!Hider
Cust!mer D de/t!r
;end!r D "redit!r
5!-i"a* s#stem
7ser
2
Maintain /artner T"%e
An SAP user should choose <SF "partner type <S 7 user#.$his allows you to distribute any and all
error messages that appear during data transfer using the 3S:'! to the correct processor. $he
processors are contained in the partner profile of this SAP user.
;riginally! only two partner types were created! 53I5 and 5M<F! in order to e2ually separate
customers and %endors. During IDoc de%elopment! other partner types were added! such as! 5&5 for
ban+ing and 5<S5 for user.
SAP AG BC420 10-47

0.74
SAP AG 2001
Partner $r!)i*es
Partner t#$e B
4aintain Partner 9um/ers
Partner num/er /artner 5
Partner t#$e US
8 8 8
Maint. %ermitted %rocessors :e*e$%!n#
...
/artner t"%e US
/artner 5
C*assi)i"ati!n
:#$e
Pr!"ess!r 1)0E1TS
5an-ua-e 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

0.76
SAP AG 1999
IDoc Inbound /arameters
:ri--er /# /a"&-r!und $r!-ram
8 8 8
P!st-$r!"essin-= a**!+ed 888 Inbound o%tions :e*e$%!n#
/rocess code
Trigger immediate'"
Pr!"essin- /# )un"ti!n m!du*e
'ICC1= 'I +%!*e d!"uments
4essa-e Hariant
4essa-e )un"ti!n
4essa-e t#$e =IDCC5 is$at"% !) +%!*e 'I d!"uments
Partner t#$e US
Partner r!*e
Partner num/er /artner:5
7ser
Partner
In*o!nd IDocs are processed immediately
=ID5
&y choosing Detail 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

0.30
SAP AG 1999
&cti$ate IDoc Inbound /rocessing
A"tiHate I!" in/!und $r!"essin-
;
!cti6-te IDoc in&ound 1rocessing E
(es No C-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 in
the 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

0.35
SAP AG 1999
(!r&)*!+ Cust!mi6in-
<
Cor7floD Runtime S*stem
CustomiFing incom1lete
!cti6e 1l-n 6-ri-nt eBists
Cor7floD -dministr-tor m-int-ined
Cor7floD RFC destin-tion full* configured
Generic decision t-s7 full* cl-ssified
T-s7s for document gener-tion full* cl-ssified
!ll T>>G t-&les -6-il-&le
Ho& for monitoring eBceeded de-dlines is sc0eduled
Ho& for monitoring Dor7 item errors is sc0eduled
Sending to o&Iects -nd R o&Iects -cti6-ted
Entries -re missing from t0e PD control t-&les
Cor7floD De6elo1ment En6ironment
CustomiFing incom1lete
Aut!mati" Cust!mi6in-
Wor.f'o( CustomiEing
$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 0CA*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

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

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 you
use is the 3S:'.
"'() pro*ect: +C,-.-//
'ubpro*ect: D0C%-//
0b*ect: ID0C-//
&ile 1ith documents in e$ternal format:
+C,-.2D0C2-23E!D2P0'."EG
$he ,I documents are a%ailable in the file &-C16JD;-J1J=EADJP;S.3E9 on the transport
directory. $his file contains fi%e documents with three items each. $ransfer these data to the
corresponding 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 slidesP
SAP AG BC420 10-53

0 $he mapping plan has been set up for you. @ou will find the necessary mapping rules in
the 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 <SD#!
(ecord type "(,&<#!
3ocal currency "<.I#!
.umber of the posting line within the document. "-reate an extra fieldP#
Posting +ey "-on%ersion: 666CHC6 and 666LHL6#!
Debit)credit indicator " if 7 L6 set to =! if not set to S#!
Amount in local currency!
Amount in document currency!
Document text!
(ecord type for general ledger "(,&<#!
9)3 account no. "pay attention to leading 4eros P#!
9eneral ledger account " see 9)3 account abo%e #.
SAP AG BC420 10-54

1 -reate the obBect ID;-RR for the document con%ersion in 3S:' under the proBect
&-C16RR and the subproBect D;-<RR.
10 :aintain the obBect attributes: IDoc with message type FIDCC1 and basic type
FIDCC'.1.
11 $he source structures should consist of the document header =EAD and the
document item P;SI.
1* Source fields:
1*0 $he source fields for the document header are:
SE$0"0# Set indicator for header: =!
(E,J.;"A# (eference number in legacy system!
D;-JDA$E"06# Document date! note: field type DD(45
$@PE"C# Document type!
P;S$I.9JDA$E"06# Posting date! note: field type DD(45
$(A.SJDA$E"06# $ransaction date! note: field type DD(45
-<((JME@"1# Document currency.
1*1 $he source fields for the document position are:
SE$1"0# Set indicator for items : P
P;S$I.9JME@"66C# Posting +ey!
A--;<.$"06# Account number!
D;-JA:;<.$"0L# Amount in document currency! note: field type !(T65
3;-A3JA:;<.$"0L# Amount in local currency! note: field type !(T65
$E/$"*6# Description of the items.
* Structure relationships:
E0,IMP, should be assigned to the document header. E0,ISE9 should be assigned to
the document items.
SAP AG BC420 10-55

C ,ield :apping:
C0 Do the mapping according to your mapping plan. @ou should consider the
special features of the document transfer using IDocs "see training course
material#
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:'. Each
new document header must be initiali4ed with 6 and counted up for each item.
Proceed as follows:
In E/tras -$ Display +ariant acti%ate the global data definition and the
processing time times.
A counter needs to be created for the items under 9lobal Data:
DA7A: Pos3counter 4I*( (1FIS(/"B28(I VA42( !
At the time of JJ&E9I.J;,J(E-;(DJJ of the header record! the counter
must be reset to 4ero.
Pos3counter 9 !
At the time of JJ&E9I.J;,J(E-;(DJJ of the item record! the counter
must be increased by one.
Pos3counter 9 Pos3counter : 1
Assign the field PosJcounter to the field E0,ISE9&<SEI.
(1FIS(/"B28(I 9 Pos3counter
L -arry out the wor+ step 'pecify files.
:aintain the path and file name5:
Source file: &-C16JD;-J1J=EADJP;S.3E9
8 -arry out the wor+ step !ssign files:
Document: &-C16JD;-J1J=EADJP;S.3E9
Items: &-C16JD;-J1J=EADJP;S.3E9
K -arry out the wor+ step ead data ta+e a loo+ at the results.
O -arry out the wor+ step Con7ert data and ta+e a loo+ at the results.
A -arry out the wor+ step 'tart IDoc creation.
06 -arry out the wor+ step 'tart IDoc processing
06.0 :a+e a note of the IDoc numbers:
JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ
00 In the IDoc display "double clic+# you can ta+e a loo+ at the status confirmations.
Select one of the IDocs. 'hat was the last status created for one of your IDocs E
JJJJJJJJ
01 If the IDocs should contain an error! correct the error in the rules of the 3S:'. $hen
perform the corresponding steps in the 3S:' again.
0* 'rite down the document numbers of the first fi%e documents.
JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ JJJJJJJJJJJ
0C @ou can loo+ at the documents using transaction ,&6*.
SAP AG BC420 10-56