All of the SAP Intelligent Enterprises run their core business process using Electronic Data Interchange (EDI) with their business partners. SAP S/4HANA programs depending on the flavor (Brownfield, Greenfield or Selective Data Transition) would cause the need to retest all EDI relevant business processes. What if you have 500 or 1000 B2B partners? Which ones to select for testing and how to make sure organizing the testing will not slow down the whole SAP S/4HANA program? Service virtualization and testing (SVT) solutions like Int4 IFTT (Certified ABAP addon for SAP Solution Manager – SAP Solman) provide the developers and functional consultants with ways to quickly simulate all B2B/EDI partners. It allows not only to quickly run test scenarios during the development (DEV) and integration (SIT) phases of the project but also run the regression testing on any non-productive environment. Not having to ask EDI partners each time for test messages or to validate the ones produced by the new SAP S/4HANA installation allows the SAP S/4HANA transformation projects to be more sustainable as projects use less resources and can be done much faster.
SVT solution like Int4 IFTT allows SAP Developers’s and SAP Function Consultants’s to decouple from EDI partners
One of the most typical questions from SAP developers and SAP Functional Consultants is can I get a few test messages from my EDI partner to validate my development? Who can help me with my testing, who can coordinate it? With Int4 IFTT you can just open Int4 IFTT SAP transaction and simulate any any EDI partner in no time. It removes the delays caused by dependency on those your B2B partners from SAP applications and continue with your SAP S/4HANA projects to deliver it on time.
Being compliant means your EDI business partners need to be able to understand you and you must be a reliable partner. Let’s work on a few examples of being non-compliant:
- Wrong data – if you send to your partners wrong data in the EDI file, your EDI partner will not understand you and it will need to correct it what takes time and money. If you do that your EDI partner will also make you familiar with EDI chargebacks – financial penalties for non-compliance. Each time you will send a wrong electronic message you may pay a penalty which may be not be large (2-6% of product cost) if you send one wrong message but if you send 10.000 or 100.000 of wrong electronic messages it will immediately become a few hundred thousand dollars.
- Messages are late – again anything between 5-150$ per one late message but if we have an issue and all messages from one day are delayed again a few hundred thousand dollars.
These are just a few examples of penalties from your EDI partner but what about the cost to reschedule the shipping, transport, delivery if the EDI business processes are not working?
According to the EDI customer survey from Figure 1 almost 20% of companies lose more than 500.000 USD per year due to poor EDI integrations and another 26% lose at least 100.000 USD. This is all without having a big impact project like SAP S/4HANA…
Figure 1 – Sources: https://www.cleo.com/blog/knowledge-base-edi-compliant
Imagine now that an SAP S/4HANA project introduces a few new business processes, the company is doing a consolidation or a carve-out or maybe even want to implement a clean core SAP S/4HANA systems. Does it mean the EDI related business processes like Order to Cash (OTC), Purchase to Pay (PTP), Logistics of any other need to be retested? No but only if you can make sure your SAP S/4HANA program budget can accommodate the EDI chargebacks and all financial penalties and basically the company does not need to sell or buy anything. In any other case testing EDI business processes will be a huge part of the program.
Int4 IFTT being an SAP native Service Virtualization and Testing solution will simulate EDI partners to test the functional and not functional behaviour of those systems as shown in Figure 2. It will also allow capturing the electronic messages running on any kind of supported Enterprise Service Bus (SAP Process Orchestration, SAP Integration Suite, Boomi, Webmethods, Azure Integration Services) and those electronic messages can be reused for testing.
Figure 2 – EDI partner simulation
Int4 IFTT SVT was designed to support complex SAP S/4HANA transformation and technically it runs on SAP Solution Manager (SAP Solman) as a certified ABAP addon. Int4 IFTT SVT is the only enterprise level solution which can fetch messages directly from any EDI message processing engine /Enterprise Service Bus (SAP Process Orchestration, SAP Integration Suite, Boomi, Webmethods, Azure Integration Services) connected to SAP S/4HANA out of the box. Later on those messages can be reused by development and SAP functional teams to simulate the behaviour of any EDI partner as shown in Figure 3. We can take electronic messages from one landscape (production) and rerun them on any other landscape (DEV, TST).
Figure 3 – repeating existing EDI messages for SAP S/4HANA transformation programs