Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

Testing of Idoc

Former Member
0 Kudos


Iam new to idoc's plz tell me how to test an idoc.

idoc type : WPUFIB01

message type : WPUFIB




Former Member
0 Kudos


There are 2 types of IDocs.


USe Tcode " WE14 " to process all idocs

2. Inbound

Tcode is "WE16"

Give the Idoc Type and Message type and run it it will process all idocs.Check the unprocessed idocs and analyse it.

Don't forget to reward if useful.

Active Contributor
0 Kudos

Use Transaction WE19 to test idocs.



Former Member
0 Kudos

Hi Eswar,

Yes, as per ravi solution i am agreeing with that. Execute WE19 and enter u r IDOC number press F8. Then type /h in command box press inbound Functionmodule push button then it will take u into debug mode. But u should set breakpoint in that function module.

Hope this helps you, reply for queries, Shall post you the updates.


Kumar. .

Active Participant
0 Kudos

Hi Eswar,

The best way to test the inbound process in to find an old IDoc (search in WE02 by extending the date range) of the same message type which have been posted.

The using this Idoc number go to WE19 transaction and test this by using the "Inbound Function module" tab. Select the "Call in debugging mode" checkbox and "In foreground" radio button.

If you have put the break point in the inbound function module or the user-exit, the code will stop at that point.

For testing the outbound process, the Idocs are generated from the application it depends upon how you are generating the Idocs (change pointer or message control or a custom program to generate the idocs).

Hope this helps.