Key Information

IDoc’s are a fundamental part of many customers SAP systems allowing data to be integrated to other systems in an asynchronous manner and in a commonly understood format. IDoc’s represent a significant portion of the global supply chain between various parties exchanging information automatically between systems.

When these IDoc’s are generated by the system (whether through a SAP GUI dialog transaction or typically a batch job), then the Testimony capture code will automatically record them and associate them as linkages with the various scripts/steps which created them.

In the screen-shot below, you can see the IDoc as a linkage for step 4 in the script. This is the step that generated the oubtound IDoc.

IDoc investigate screen

When the linkage in the lower left is selected, the right hand side appears with the recorded/expected IDoc shown on the left and the playback/actual IDoc on the right. You are able to see the IDoc control record (header) of each and the underlying segments and segment fields.

Recording inbound and outbound IDocs

To capture both inbound and oubtound IDoc’s in your source system, you need to activate the two IDoc related recording enhancements. This is detailed in the following earlier section on General Enhancements -> Enhancements.

Once captured in the recording, these linkages will be visible as either “Inbound IDoc” or “Outbound IDoc” linkages in the Business Transaction Linkage Explorer. After transferring to the Repository, these same linkages will be found within the Test Script Linkage Explorer.

Playing back and comparing IDocs

During the playback, the same IDocs will be captured and then compared to what happened in the recording. You must activate the playback enhancement to achieve this otherwise you will always have an “IDoc missing” failure reason since no IDoc’s will be captured at all.

Additional Notes

You can deactivate the comparison of the IDoc segment data if you expect to see differences between the IDoc data in the recording versus the playback. This would typically happen if such fields as time-stamps, unique identifiers or GUID’s are contained within the segment data. This parameter is explained in the earlier section on Configuration Parameters.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment