<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/5db000c422074732bf68a54a68a432f7&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5db000c422074732bf68a54a68a432f7-5088ff062388074a.gif</thumbnail_url><duration>371.81</duration><title>SAP Backend Validation Approach 1- Automation Object and Test Case creation for the purpose of the Simulation based on SAP PO message</title><description>This Loom demonstrates how to use INT4 suite simulation to process purchase order messages and ultimately post the resulting sales order. It focuses on collecting the input message directly from the middleware platform via the ptrsOrder_out interface by creating an INT4 automation object in Fiori launchpad with type SAP and using the default MS message version. The author imports existing interfaces from production PO, selects the correct sender, and creates INT4api-tester.com cockpit test cases for the automation object using the origin environment production PO. They then download and verify saved input payloads under the test case details, noting that if a different message version is needed, such as EDI, it should be specified in the automation object message version before processing.</description></oembed>