Simulate and test

A mapping isn't done when the lines are drawn. It's done when you can show that known inputs produce the expected outputs. Cloud Integration gives you two design-time tools for that, and neither needs a deployment. Simulate tests the entire mapping. Display Queue tests one node or function. Both run in the mapping editor, even when the flow isn't in edit mode, and both can use the same uploaded input file.

Open the integration flow (or the mapping artifact) and select the mapping.
Choose Simulate and select an input XML file from your computer. The data appears in the source message table.
Choose Generate Test. The output appears in the target message table.
Choose Download Output to keep the output file as evidence.
Change a function or property, simulate again, and compare. You don't have to save the mapping to simulate.

A few rules from SAP's documentation are worth knowing. Simulating an incomplete mapping returns a validation error, so finish the structure first. Mapping simulation is supported only for the Cloud Integration runtime profile. Mappings that use scripts can be simulated too, which matters for lesson 6 and sap-pim-202.

Pick inputsAnonymized ORDERS05 and INVOIC02 files taken from XP1 traffic, plus hand-made edge cases
Write expected outputsFrom the partner's specification, or from the PO mapping's output for the same input
SimulateRun each input; download the output file
CompareDiff expected and actual; explain or fix every difference
File the evidenceInput, expected, actual and result, stored with the test case

A repeatable mapping test: inputs, expected outputs, simulation, comparison and evidence.

The Sign-Off Table · thesignofftable.com/academy/sap-pim-201

What to put in the sample set

Case	Why it matters	ORDERS05 example
Happy path	Proves the main structure	One PO, three items, all partners present
Many items	Proves contexts and useOneAsMany	PO with 40 items
Optional data missing	Proves createIf, exists and defaults	No ship-to E1EDKA1 segment
Bulk message	Proves removeContexts and splitting	Two IDocs in one message
Edge values	Proves formats and precision	Quantities with 3 decimals, long texts, special characters
Invalid input	Proves the failure is visible	No E1EDK01 header: the flow must fail, not send a half order

A minimal sample set for one mapping; keep the files with the test cases.

Migration regression: PO output as the oracle

For interfaces that move from XP1, the best expected output is often the one PO produces today. Run the same input through the ESR mapping's test function on PO and through Simulate in Cloud Integration, then compare the two outputs. Any difference must be explained: a deliberate improvement, a partner-agreed change, or a defect. sap-pim-301 builds this into a full migration regression approach. Here, learn to do it for one mapping.

Comparing PO and Cloud Integration output for the same input turns the existing interface into the test oracle.

The Sign-Off Table · thesignofftable.com/academy/sap-pim-201

Beyond the mapping, the integration flow simulation feature lets you test a whole flow or part of it before deployment. You can mock receiver responses on Request Reply steps, so calls to S/4HANA or Lakeside aren't needed. Use it when the mapping depends on headers or properties set by earlier steps.

Hands-on lab · ACCELQ

Test the mapping through an iFlow endpoint with REST calls

Simulation proves the mapping in the editor; a REST call proves the deployed flow. You'll post the lesson's ORDERS05 sample to an HTTPS endpoint with + API > Insert REST call and turn the mapped fields into assertions.

Practice on Your own SAP Integration Suite trial (SAP BTP trial, Cloud Integration capability) running an integration flow you build from this lesson. Never a company tenant.

If you haven't set up ACCELQ yet, do the setup lab first. In your trial tenant, build a flow: HTTPS sender with address /cmc/mm-orders and CSRF Protected cleared, then your Message Mapping (ORDERS05 to order lines), then an XML to JSON Converter. Deploy it and copy the endpoint from the deployed content in the Monitor.
Take clientid and clientsecret from a service key of the Process Integration Runtime instance with plan integration-flow. Base64-encode clientid:clientsecret locally, then encrypt Basic <encoded value> under Resources > Utilities > Encrypt Text.
Create a Library Action named Post ORDERS05 to mapping with an Action Parameter endpointUrl. Click + API > Insert REST call, set the Endpoint URL to that parameter, method POST, and headers Content-Type: application/xml and Authorization with value $encr: plus your encrypted string. Click NEXT.
Choose XML as the payload type and paste the three-item sample (PO 4500000187). Click SEND REQUEST.
On the Status tab confirm 200. On the Response tab click the third line's PO number and material to create assertions: 4500000187 and CMC-HSG-400 prove the useOneAsMany chain. Click SAVE.
Insert a second call with the E1EDK01 segment removed. Assert the error status you actually get (a mapping exception typically returns 500) so the invalid-input case is proven.
Build a Scenario with the Action, run it on your Local Agent and open the Test Report.

Done when Both calls pass: the valid file returns three lines with the PO number on each, and the invalid file fails with the status you recorded. Keep the Test Report link with your mapping test case as evidence of the deployed flow.

Learn more in ACCELQ’s docs: REST API Test Automation in ACCELQ · Verifying API Responses in ACCELQ · Securing Sensitive Information in API Calls with Encrypted Values

Start the free ACCELQ trial Matt Angerer, who runs The Sign-Off Table, works at ACCELQ. Disclosure

Key points

Simulate tests the whole mapping, Display Queue one node; neither needs deployment or saving.
Keep a sample set with happy path, many items, missing optional data, bulk, edge values and invalid input.
For migrated interfaces, compare against the PO output for the same input and explain every difference.
Store input, expected output, actual output and result as evidence.

What to put in the sample set

Migration regression: PO output as the oracle

Lesson check