SAP has prepared a first version of a SAP PO upgrade testing tool – PIT. It’s being shipped with SP14 to SAP PO which is currently released. The tool perfectly complements Int4 IFTT testing tool in one scenario the so please have a look how you can configure it to help you perform an SAP PO upgrade more easily.
SAP Test Tool primarily focuses:
In order to use SAP Test Tool you need to have SAP PO 7.5SP14 (where you can install it or run test scenarios) but if you just want tofeed the SAP Test Tool with data you can use a system from 7.31 SP17 or 7.5SP06 or higher.
For each message used as a source you need to enable loggingon BI, MS, AM.
Current limitations (this may be subject to change)
Terminology used in SAP Test Tool
Test system – SAPPO system in the landscape which is used for testing – either as source(feeding the Test tool with messages) , target (where sender’s messages areexecuted) – those are used in dual stack to single stack migrations or both(sender and target) which is a typical use case for regression testing on asingle system.
Test Case – SAPPO routing configuration which is being tested (ICO, etc.)
Test Data Set – aset of messages (successfully processed) which is a subject for testing.
Run configuration– specifies on which landscape should the test case be executed
In order to be able to create the configuration and run ityou’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.
Currently SAP Test Tool is using NWDS as a mainconfiguration tool. The scenario below will describe how to do regressiontesting on a single SAP PO system. We will find a successfully processedmessage, do a mapping change and see what will happen once we reprocess thesame message via the same ICO. Ideally it should display all of thedifferencies between the two runs.
Open NWDS and find the new perspective: SAP ProcessIntegration Test.
Open preferences and insert connection data to your SAP POwere the SAP Test Tool is installed.
In the next step you need to define the systems (source andtarget) where you need to run your tests. In this case it’s the same systemwhere SAP Test Tool is installed.
In the next step we can start creating Test Cases.
Select the type of the flow you want to test.
In the next step it’s time to select the routing objectitself (ICO).
In the next step the Test case is created so we can populateit with test data. In order to do that select the Test Data tab of the TestCase.
Then select the „Add“ button to add messages to the testdata where you can specify the source system from which you want to fetch thedata.
Next select the time range when the message was created and the message itself.
On the Verification tab of the Test case you can also definewhich parts of the message should not be checked (dates, etc.).
This step finishes the configuration/customizing part of theSAP Test Tool.
Run and validation.
In order to run the test you need to create a new runconfiguration.
Where you need to specify the Test Case and the landscape ofthe execution.
What you can also select here is the checkbox „Stop messagebefore delivering to Receiver“ which will automatically cancel the Test messageafter processing so it will not overload the receiver system.
Once you press Run the Test Case will get executed and theTestRun is executed you can send it for Verification which will compare the old(original) target message with the new one created by executing the Test Case.
As I’ve changed the mapping before running the Test Casewhat we can see is that there are some differences found.
In the Error Overview section we can see a more detaileddescription talling us the what is different between the original message andthe one from the Test Run.
SAP Test Tool is a free test tool provided by SAP which can help in some SAP PO Use types mentioned in this article. In case you’d need to Test some other use cases like the ones mentioned below fell free to contact us about a demo of the Int4 IFTT (the only SAP certified tool for testing all SAP middleware scenarios).
SAP Test Tool – PIT and Int4 IFTT scenario coverage
|Use Case Support|
|SAP PO dual stack to single stack migrations||Yes||Yes|
|3rd party middleware to SAP PO migrations||No||Yes|
|SAP PO to 3rd party middleware migrations||No||Yes|
|SAP EDI migrations (B2B add on)||No||Yes|
|SAP Cloud Platform Integration (CPI) testing||No||Yes|
|S4/HANA conversions testing||No||Yes|
|SAP Backend validations (document field level)||No||Yes|
|SAP Backend (IDOC, Proxy) testing, SAP eCATT |
|SAP AIF Testing||No||Yes|
|Test Driven Development||No||Yes|
|Integration test documentation||No||Yes|
|SAP PO Features|
|Use of successful messages as reference messages||Yes||Yes|
|XML comparison (including exceptions)||Yes||Yes|
|EDIFACT/ flat files comparison (incl. exceptions)||No||Yes|
|Exchanging test cases between environments||Yes||Yes|
|SAP PO adapter module testing||No||Yes|
|SAP PO multimappings||No||Yes|
|Background (scheduled) validations||No||Yes|
|Solman integration, incident management||No||Yes|
|SAP PO only (after 7.31 SP17)||Yes||No|
|SAP PO (also versions prior to 7.31 SP17) , SAP CPI, |
SAP Backend interface implementation,
More videos on the SAP PO upgrades topic – How to upgrade you SAP PO landscape
Write to us