This page is not a part of an official Int4 documentation.
Knowledge Articles
Knowledge Articles
Breadcrumbs

1. SAP Backend Validation Approach 1- Automation Object and Test Case creation for the purpose of the Simulation based on SAP PO message

How to Create an Automation Object and Test Cases for a Purchase Order Interface

Hands-on tutorial - Part 1 of 5: SAP Backend Validation Series

This guide walks you through creating your first end-to-end simulation scenario in Int4 Suite. You will build an Automation Object pointing to an SAP PO interface, then generate test cases by pulling real production messages directly from middleware


Overview

In this scenario, an external system sends a Purchase Order to SAP PO. The middleware converts the Purchase Order XML into IDoc XML, and the SAP backend posts a Sales Order based on that IDoc.

This first guide focuses only on the Int4 Suite simulation capabilities - you will collect input messages directly from SAP PO using the interface PurchaseOrder_Outand turn them into reusable test cases.

At the end of this guide you will have:

  • A configured Automation Object linked to your SAP PO interface

  • Test cases populated with real input payloads taken from production

  • A working baseline that the next three guides in this series will extend



Step-by-step instructions

fdbf03aedf394361803b779abc1e3af9?workflows_screenshot=true

The scenario simulates an external system sending a Purchase Order. The Purchase Order XML is processed in middleware, converted into IDoc XML and ultimately results in a Sales Order being posted.

This walkthrough focuses only on the Int4 Suite simulation capabilities.

1. Review the interface before creating the Automation Object


61a951e7839b4e2db7a84d575261bb4a?workflows_screenshot=true

Before creating anything in Int4 Suite, first inspect the target interface in SAP PO:

  • The interface uses standard logging and staging, so the default Int4 Suite parameters can be used.

💡 Tip: If the interface uses adapter modules that change the message content and you want to fetch it - add a custom message caption in the Message version before processing

More info: https://help.int4.com/int4-suite-knowledge-center-library/3.15/creating-the-configuration-object-for-testing-adap


2. Create Automation Object

  1. Open the Fiori Launchpad and click the Automation Object tile.

  2. Click Create.

  3. Enter a descriptive Automation Object name.

  4. Set the Automation Object type to: PI GUID E2E Inbound

  5. Add a description.

  6. Click Create to save.

3. Import interface details from SAP PO

Inside the new Automation Object, use the Import from PI function to pull interface metadata directly from SAP PO:

image-20260512-093727.png

  1. Select the source environment - for example, Production PO.

  2. Choose the relevant interface name and interface namespace.

  3. Click Go and wait for Int4 Suite to fetch the available interface data.

  4. If multiple sender systems reuse the same interface, select the specific sender/interface instance you want to use.

  5. Click Save.

⚠️ Note: It is common for one interface to be reused by several senders.

4. Create test cases for the Automation Object

  1. Go to Int4 APITester Cockpit.

  2. Open (or create) the folder where you want to store the test cases.

  3. Click Edit, then add a new item using the + button.

  4. Choose Create test cases.

  5. Provide a description.

  6. Ensure the test case type matches the Automation Object type.

  7. Select the Automation Object you created in step 3.

  8. Set the environment. If the folder environment is empty, choose the origin environment - for example, Production PO

  9. Use the search help in the Document Number field.

    image-20260512-094051.png


  1. Click Search to fetch available messages from SAP PO.

  2. Review the list of messages Int4 Suite retrieved from the production environment.

  3. Select one or more messages.

  4. Click OK, then Save.

Int4 Suite will now download the input messages needed for the simulation.

image-20260512-094141.png

5. Verify the saved input payload

  1. Open the test case details.

    image-20260512-094242.png

  2. Navigate to Payloads.

  3. Click Input Message.

  4. Confirm that the input message was saved correctly and contains for example the expected Purchase Order XML.

    image-20260512-094303.png

8. Understand when to set a custom message version

In this example, no extra parameter was needed for message version before processing because the standard MS version was used.

If SAP PO uses a different message version - for example, one produced by a message logger or an adapter module such as EDI - you must enter that version in the Automation Object:

  • Open the Automation Object

  • Set Message version before processing to the appropriate value (e.g. EDI)

Int4 Suite uses this value to determine which version of the message to download into the test case.

Troubleshooting

Issue

Likely cause

Resolution

No messages returned in the search

Wrong environment selected, or no recent traffic on the interface

Verify the environment in the search popup and the interface name/namespace in the Automation Object

Payload is empty after save

Wrong message version configured

Check whether the interface uses a custom message version

Multiple sender systems appear

Interface is shared across senders

Pick the specific sender/interface instance you want to test

What's next

This guide established the foundation. Continue with the rest of the series:

Video reference

🎥 Full walkthrough on Loom: https://loom.com/share/5db000c422074732bf68a54a68a432f7