Week 7 of 12
Interfaces and integrations
The SAP system is rarely what fails at go-live. The bank rejects the payment file, the EDI partner cannot read the new invoice, the warehouse system misses deliveries. Interfaces need owners, partner contacts and a test result in every SIT cycle and every mock.
S/4HANA adds its own twists: 40-character material numbers in IDocs and partner maps, and Business Partner replacing customer and vendor master replication.
This week: inventory every interface and book the partners
- List every interface and direction: message or IDoc type, middleware, trigger, volume, monitoring transaction and the SAP connectivity objects.
- Name an SAP owner and a partner contact for each, and book partner test windows for SIT 1 now.
- Plan positive, negative and volume tests for each, including the cutover action (stop, drain, restart).
- An interface is ready only when it passed in SIT 2 and the final mock cutover. Track that, not "tested once".
Number of the week
2 per year
Public Edition upgrades that cannot be deferred: every interface needs a regression plan after go-live too.
Source: SAP release informationUse this week
- Interface Inventory & Test Tracker →
18 interfaces with message types, monitoring, cutover action and a Ready flag.
- SIT Cycle Plan & Entry/Exit Criteria →
16 end-to-end scenarios that cross interfaces, with a daily burn-down chart.
Next week: SIT and UAT. How to run cycles that prove something, and get a signature at the end.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.