idoc debugging

[Former Member]

hi gurus,

1) PLZ tell me in what situation we go for creating customized IDOC i.e writing posting and selection programing???

2)how to do IDOC debugging?and how do we test weather our IDOC is functioning properly or not?

thanx.

[Former Member]

Hi,

We can Debug Idoc by using Tcode : We19

Thanks

Sunil

[gajendra_bhakuni]

Hi Pavan,

1) We generally go for customized IDocs if none of the SAP standard IDoc does not suit our need/business process. Creating is custom IDoc should be a very stringent process. The SAP standard IDocs should be rigorously checked (if any user exits can be of our help or IDoc extension will solve the purpose).

2) WE19 is the test tool by which we can create IDocs to see whether our functionality is working. It is mostly used to debug inbound function modules.

For outbound function module debugging you can use the following:

1) RBDMIDOC - for master IDocs configured via change pointers.

2) RSNASTED - for transaction IDocs with output/message control.

3) RSEOUT00 - For IDoc whose status is "to be processed".

Hope this helps.

Regards,

Gajendra.

[Former Member]

hi,

in order to get the status of your idoc you can go to TCODE - WE05,

in that give the date of the idoc created and the message type(if you know),once you give all these details and execute it will list all the idoc created under the conditions you have selected along with the status of the idoc

The two available process for IDOCs are

We can identify the process with the number of status record.

Outbound Process

Sending out the data from our system. The IDOC which is called as Outbound IDOC

01 - 49 for Outbound Process

Inbound Process

When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.

50 - 75 for Inbound Process