Scribd
Upload
11 views1 page

Idoc Tcodes

Uploaded by

Jaya Sankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
11 views1 page

Idoc Tcodes

Uploaded by

Jaya Sankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

1.

we31 segment creation


2.we30 idoc type cration
3.we81 message type creation
4.we82 assign message type with idoctype
5.sm59 creating Logical Destination.
6.we21 create port
7. we20 check partner profile
8.we02/we05 check idoc
9.we42 create process code
10.bd64 Distribution Model view.
11.bd61 activate change pointer globally.
12 bd50 activate change pointer for idoc message type.
13.bd52 Assign Change Point Items for Message Type.
14.BDCP2 change log will be maintained in table BDCP2.
-------------------------
We are going to use transaction BD87 for Re-processing the failed IDOC�s.

Debugging an idoc failed with status 51

1. go to we02/05
get the idoc number ( of Status 51), partner name

Goto WE20
Partnername input -> click on inbound message type - process code � get the
function module

Goto WE19
Give the Idoc number as input click to execute
Click on inbound function module �give the func.module (from above step) � click on
check box for debugging
Execute � find the problem �.correct it�..if you execute you will receive a new
idoc with status 51 again.

After identifying correct it and execute with out debug it will flow to status 53
----------------------
TCODE: BD50 (Activate change pointer for message type)
TCODE: BD66 (Segment Field-Change Document field)
TCODE: BD61 (Activate change pointers generally)
We can create IDOCS from change pointers with the report RBDMIDOC

You might also like