Professional Documents
Culture Documents
IDOC Testing: You Can Test The Idoc Using Idoc Test Tool. Just Follow The Steps Above
IDOC Testing: You Can Test The Idoc Using Idoc Test Tool. Just Follow The Steps Above
T-Codes.
WE19 Test tool
WE12 IDoc test: Inb. Proc of Outb. File
WE16 IDoc test: Inbound File
WE17 IDoc test: Inbound status report
WE02
WE05
WE19
Debugging an IDOC
You can test the Idoc using idoc test tool.
Just follow the steps above.
1. Go to transaction WE19.
2. Enter the idoc number you want to test.
3. Go to menu IDOC -> test inbound idoc -> standard inbound
4. One popup screen comes get the "FUCTION NAME" to test the idoc.
5. Click on "INBOUND FUNCTION MODULE" button.
6. Enter function module name.
7. Click on CALL IN DEBUGGING MODE check box and choose foreground mode.
And choose yes to run it.
EDIT IDOC
Go to transaction WE19.
Enter the idoc number you want to test.
Double click on each segments and u can edit the values.
Then click start inbound
Basically WE02 and WE05 are same in terms of Functionality. Displays the IDocs.
But there is one diff. One of these transactions is for Administration purpose.
And WE07 is for Error statistics. It displays the IDocs which went into errors. It classifies
the IDocs in there error types.
Use transaction WE05 or WE02 to add missing data for your inbound Idoc, If you use
transaction WE19, system will generate new IDoc. However, system will not generate new IDoc
if you use WE05 or WE02.
3. Double click on the segment (page Icon) where you want to add missing data.
4. In the screen "Display Data Record for IDoc", go to menu "Data Record" and click on
"Display - > Change". Then system will display a popup information "Changes to the IDoc are
written to the database", then press enter .
In order to process the edited inbound IDoc, please execute standard program RBDAGAIE by
providing the above IDoc number.
You can call the inbound process using the normal path by clicking the Standard
Inbound button, in which case the process goes through the checks as if it had been sent
in by the subsystem.
Alternatively, you can pass the process to a function module directly, by clicking the
Inbound Function Module button. In this case, the system bypasses the checks for
partner profile and hands the IDoc data to your inbound function module directly. This
approach is useful for testing an inbound process without having to maintain any
inbound configuration.
You can also start the function module in debug mode and select the processing option
for your posting module.
Finally, you can choose to save the IDoc in a file.