video1.0<iframe src="https://www.loom.com/embed/af9cccd8dc5049deb080652093559c75" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/af9cccd8dc5049deb080652093559c75-68aafb0a5a269148.gif364.407This Loom explains how to generate a unique PurchaseOrderNumber for each INT4 API test execution. The author creates a new variable PO in the assigned automation object using a read and replace approach, importing the test case payload and targeting the purchaser number field under attributes and purchaser number for replacement with a generated value. They then create a number range named PO_test with prefix workshop_one_test, set low value to 1 and a high value to another number, and enable add zeros for leading zeros. After saving, the cockpit shows the PO variable being updated from IND4_test_221 to workshop_10001 so each test run can be uniquely identified in the middleware or backend.