Professional Documents
Culture Documents
Trigger IDOC in Debug Mode
Trigger IDOC in Debug Mode
RSNAST00 RSNASTED RBDMIDOC RSEOUT00 RBDAPP01 RSECHK07 Program to process the IDOCs Can be found in the Processing Log of the document with the routine EDI_PROCESSING or LE_PROCESSING! Generates IDOC"s from change pointers #$ou can a%so use transaction &D'() Processes outbound IDOC"s with status *+, # IDOC"s mass processing) Processes inbound IDOC"s! Chec- if partner profi%er is .a%id
Useful transacti ns f r ID cs
&D/0 1 Status 2onitor for LE 2essages 3 Reprocess IDoc S LE 1 Disp%a4 LE Customi5ing
6E+' 1 Disp%a4 IDoc 6E+7 1 IDoc Lists 6E+8 1 Search for IDoc in Database 6E(8 1 9est too% 6E'+ 1 :ind :unction modu%es asscoaited with IDoc 6E*+ 1 9o chec- the segments in the basic t4pe 6E*( 1 9o chec- the fie%ds in the segment
Useful ta!les
9ab%e N S9 EDIDC EDID; EDIDS Discription 2essage Status Contro% information for an IDOC Data Records from ;!+ onwards Status of an IDOC
Ste"s t
tri##er ID c in $e!u# % $e
(!Go to transaction from which we generate IDoc #:or E<1 .f+' with the in.oice number) => goto => header => Output t4pe can be ta-en from here! '!C%ic- Processing Log, to get the IDOC number and to get the program #E<1 RSN S9ED) name with the routine #:or E<1 EDI_PROCESSING #Comm! 2edium = EDI) or LE_PROCESSING #2edium = LE))! *!Set the brea-=point#bp) in the routine got it from the Processing Log! ;!Goto we+' => gi.e IDOC number to co%%ect partner detai%s#partner no! ? t4pe)! 7!Goto we'+ => :ind the partner no! ? t4pe => C%ic- on message t4pe => message contro% #tab strip) => c%ic- on processing code to find the :unction modu%e associated with! @!Set the bp in the function modu%e 0!Go to the standard program "RSN S9++", gi.e the fo%%owing inputs and e<ecute!
9ips to find out Input Parameters1 Aere, ObBect -e4 is in.oice number, So output app%ication CD*E is se%ected! Output 94pe#FRD;) can be found in .f+' header or in message contro%#refer step 7)! 9he abo.e input .a%ues can be found in .f+' header or in N S9 tab%e!