video1.0<iframe src="https://www.loom.com/embed/3d55b8b7fd9b41e88454531266e38398" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/3d55b8b7fd9b41e88454531266e38398-a6519d8cffc5a50c.gif351.049This Loom explains how to validate generated IDOCs from SAP PO processing in an end-to-end PI GUID inbound middleware test. The author updates the automation object to select validate message output, noting that for standard SAP PO captions no message version is needed and the output will be the after mapping version. They create a new test case (10 messages, selecting the production PO environment and a document number) so the test stores both input payloads and output IDOC messages, then run it in QA and compare production vs current execution payloads to see differences as PO values change. They also use debug mode to create an exception for the expected differing Bellurn SAP PO number and describe why to ignore that field.