← All features

Testing

B2B agreement testing

You run hundreds of TPM agreements, and you have no test case that tells you a change did not break one of your trading partners.

You cannot build a good EDI (X12 or EDIFACT) infrastructure without a complete testing setup for it. B2B agreement testing in Figaf builds test cases around the TPM agreement in SAP Integration Suite, so every trading partner can be regression tested with real messages. It is used by B2B teams operating TPM and by teams migrating B2B scenarios from SAP PI/PO.

How it works

• Tied to the agreement. Test cases are connected with the data from TPM agreements, so you can search across all their parameters and find the test cases you want to run. On a test case you can switch to show the TPM objects.
• No trace mode needed. You select an agreement and create test cases from the next messages processed on it. Because this does not require trace mode, you can test at the scale of the whole landscape.
• MIGs, MAGs or iFlows. Testing supports agreements that use MIGs and MAGs, and agreements that use iFlows with ProcessDirect, which suits migrated scenarios.
• Acknowledgements. Messages that require CONTRL or 997 in the flow are supported (release 2505).
• TPM content of your choice. You can specify whether B2B test cases run with SAP Standard TPM V2 content or the SAP Community Factory TPM content (release 2510).
• Mass test cases from archives. Since release 2511 you upload a zip file of input and output messages with a correlation in the file names, for example in_002.xml and out_002.edi, and specify a default agreement. Figaf parses the agreements, assigns each message pair to the agreement it matches, and shows a validation log of what was assigned and what is still open, so you can keep uploading until all messages have a scenario.
• From SAP PI/PO. You can record EDI messages on SAP PI/PO and migrate the test cases to the relevant TPM agreements. When you migrate a B2B scenario, Figaf lists all test cases for the ICOs that use the operation mapping, so regression testing is available right away (release 2508).

Business value

• Every partner covered. Each agreement has a test case tied to it, instead of relying on a one-time manual check of the last partner someone touched.
• Less coordination with partners. Changes and migrations can be verified internally, before partners are asked to send test files.
• Reuse of history. Archived messages, also from platforms other than SAP PI, become a large regression test repository with little effort.
• Faster, safer migrations. Test cases carried over from SAP PI/PO show the gaps in a migrated scenario early, for example old partner identification logic that needs review.
• Lower operating cost. A B2B setup where all transactions can be tested with ease reduces the cost of building and maintaining it.

Good to know

• B2B testing with TPM was introduced in release 2504. It is part of Figaf B2B Management and builds on regression testing.
• Other B2B platforms are not supported for migration, but you can import their B2B messages into Figaf testing and add them to agreements automatically.

Learn more

• Figaf B2B Management