{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/e4f9ffe4eb5048a6b62a2f04641140af\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/e4f9ffe4eb5048a6b62a2f04641140af-27e74e0b7deca86f.gif","duration":272.64,"title":"SAP Backend Validation Approach 2 - Validate Sales Order via Database Rules","description":"This Loom demonstrates adding database validation to an automation object to verify the sales order created by a simulated purchase order message. The author reviews the existing database validation rule set for sales orders using generic underscore SO, focusing on required variables that identify the sales order via the BSTNK purchase order number from the VBAC table and a variable value set to PO. They then edit the automation object, select the same database validation rule set, and save. Finally, they re-run the test case in the INTC4API tester cockpit in the QAPO environment to ensure INT4Suite validates both the reference sales order from production and the newly created tested sales order."}