<?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/ab920936ef2844de99a622b07f6f9dc8&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/ab920936ef2844de99a622b07f6f9dc8-ccd290c40a16122b.gif</thumbnail_url><duration>536.481</duration><title>5. SAP Backend Validation Approach 3 - Creating Database Validation Rulesets</title><description>This Loom demonstrates how to set up backend database validation rulesets to compare tables across SAP systems like SAP ECC or SAP S/4HANA. The author creates a localized application and a ruleset with ID demo-sales-order-release-to-reset, defining comparisons between VB-AK and VB-AP and selecting fields such as BSTNK with selection equals using variable P0, plus comparison details including masking and distinct error versus warning behavior. The ruleset is then added to an automation object under DatabaseValidations, and an API test is executed in APITesterCockpit where the test fails due to a time difference. The results show the reference document versus the current execution, with differences highlighted in red and masked fields hidden, with an option to focus only on the creation time differences.</description></oembed>