SAP GUI and Fiori
The desktop engine recognizes SAP GUI-style controls by sight. Fiori apps run from the same steps in the browser.
Certify each S/4HANA upgrade in the test-tenant window
Public Edition upgrades arrive twice a year with about three weeks of test-tenant time. Key users prove their processes in plain English, on SAP GUI-style screens and Fiori.
- Fits the three-week window
- SAP GUI-style screens and Fiori
- Reuse tests for ECC exit
Run transaction 'MIGO'
Type '{{po.number}}' into 'Purchase order'
Tick the 'Item OK' checkbox on row 1
Press 'Ctrl+S'
Check that the 'Status bar' shows 'Material document' within 10 seconds
Key users own certification
Transaction-level steps
The SAP pack adds steps such as "Run transaction 'VA01'", in the words your key users already use.
Evidence and sign-off
Every check keeps what it expected and what it saw. A named person signs off in Quality View.
Certify each SAP release
The SAP release rhythm
Public cloud upgrades come to you. Private cloud and on-premise upgrades you schedule, but still certify.
| Release | Timing | Can you defer? |
|---|---|---|
| S/4HANA Cloud, Public Edition | February and August; test tenant about 3 weeks before production | No |
| S/4HANA Cloud, Private Edition | Base release every 2 years, feature packs every 6 months | Yes, you schedule it |
| SuccessFactors | 1H and 2H releases | Partly; some features switch on automatically |
| ECC to S/4HANA | ECC mainstream maintenance ends in 2027 | Your migration project |
Typical cadence. Dates vary by instance and region; check your vendor's release calendar.
Compare all vendor calendarsWhere SAP upgrades hurt
The upgrade changes objects your landscape depends on.
- ABAP enhancements and side-by-side extensions call changed objects
- Fiori apps are regrouped, and business roles lose a tile
- IDocs, APIs and middleware maps to banks and suppliers stop matching
- Invoices and delivery notes print or send differently
The processes auditors notice
Certify the end-to-end processes your auditors and customers notice first.
- Order to cash: sales order, delivery, billing and receivables
- Procure to pay: purchase order, goods receipt, invoice and payment run
- Record to report: journals, period close and statements
- Plan to produce: MRP run, production orders and confirmations
Certify customizing changes
Customizing changes every month. A new pricing condition needs the same proof as a vendor upgrade.
- Customizing settings and pricing conditions
- Purchase order release strategies and workflows
- Business roles and output determination
Procure-to-pay, end to end
Purchasing often starts outside SAP. Certify the whole chain as one test.
A requisition is approved in Coupa and becomes a purchase order.
The order, goods receipt and invoice post in SAP.
The payment run pays the supplier the matched amount.
Questions
How does this help an ECC to S/4HANA move?
Record your key processes on ECC as plain-English steps. Run them again on S/4HANA and compare outcomes with evidence.
We are on Private Edition. Do we still need this?
Yes. You choose when to upgrade, and the same processes still need proof before go-live.
Bring one process
Leave with a plan
Bring one process from your test tenant. We record it, run it and show the sign-off with you.