SAP ECC Obsolete Transactions and S/4HANA Replacements
After conversion, some familiar transaction codes stop working or are replaced. This table maps the most common ones to what users should run instead, so training and role design can start early.
| ECC T-code | What it did | Use in S/4HANA | Note |
|---|---|---|---|
XD01 | Create customer (central) | BP | Create a Business Partner with the customer role |
XD02 | Change customer (central) | BP | Maintain the customer role in BP |
XD03 | Display customer (central) | BP | Display via BP |
VD01 | Create customer (sales area) | BP | Sales area data sits in the BP customer role |
VD02 | Change customer (sales area) | BP | Sales area data sits in the BP customer role |
VD03 | Display customer (sales area) | BP | Sales area data sits in the BP customer role |
XK01 | Create vendor (central) | BP | Create a Business Partner with the supplier role |
XK02 | Change vendor (central) | BP | Maintain the supplier role in BP |
XK03 | Display vendor (central) | BP | Display via BP |
MK01 | Create vendor (purchasing) | BP | Purchasing data sits in the BP supplier role |
MK02 | Change vendor (purchasing) | BP | Purchasing data sits in the BP supplier role |
MK03 | Display vendor (purchasing) | BP | Purchasing data sits in the BP supplier role |
FD32 | Change customer credit management data | UKM_BP | SAP Credit Management master data |
FD33 | Display customer credit management data | UKM_BP | SAP Credit Management master data |
MB01 | Post goods receipt for purchase order | MIGO | Use movement type 101 with reference to PO |
MB1A | Goods issue | MIGO | Use the goods issue transaction type in MIGO |
MB1B | Transfer posting | MIGO | Use the transfer posting transaction type in MIGO |
MB1C | Other goods receipts | MIGO | Use the goods receipt, other transaction type in MIGO |
MB31 | Goods receipt for production order | MIGO | Use goods receipt with reference to order |
MD01 | MRP run, total planning | MD01N | MRP Live runs on the database |
ME21 | Create purchase order (old screen) | ME21N | Enjoy transaction, also available in ECC |
ME22 | Change purchase order (old screen) | ME22N | Enjoy transaction, also available in ECC |
ME23 | Display purchase order (old screen) | ME23N | Enjoy transaction, also available in ECC |
ME51 | Create purchase requisition (old screen) | ME51N | Enjoy transaction, also available in ECC |
ME52 | Change purchase requisition (old screen) | ME52N | Enjoy transaction, also available in ECC |
ME53 | Display purchase requisition (old screen) | ME53N | Enjoy transaction, also available in ECC |
VL01 | Create outbound delivery (old screen) | VL01N | Also available in ECC |
VL02 | Change outbound delivery (old screen) | VL02N | Also available in ECC |
VL03 | Display outbound delivery (old screen) | VL03N | Also available in ECC |
Check each entry in your target release with transaction SE93 or the SAP Fiori apps reference library. Fiori apps often exist for the same task and may suit key users better than SAP GUI.
Scan custom code for obsolete T-code calls
Want the list above turned into an automated scan of your Z programs and jobs? We can set up a read-only analysis.
Optional. The tool and every export work without this. No spam.
How to use this table
Search for the transaction code a user mentions, or filter by the replacement to see everything that now routes to BP or MIGO. Export the table and compare it with the transaction usage in your own system, using ST03N workload statistics or SCMON data, so you only train users on codes they actually run. Then update authorization roles in PFCG to reflect the new transactions.
- Pull ST03N usage for the last 12 months
- Intersect with this list to find affected users
- Update PFCG roles and the Fiori launchpad catalogs together
The three big groups
Customer and vendor transactions collapse into the Business Partner transaction BP, which changes how master data is created, who owns it and how approvals work. Goods movement transactions MB1A, MB1B, MB1C and MB31 are replaced by MIGO, which is already available in ECC and can be adopted before the project. Credit management moves from FD32 to UKM_BP. Moving users to BP and MIGO in ECC before cutover shortens training load at go-live.
Common mistakes
Teams often discover replaced transactions during user acceptance testing, when scripted test cases still reference ECC codes. Also check batch jobs, LSMW recordings, BDC sessions and ABAP code that CALL TRANSACTION an obsolete code, because these fail silently or with authorization errors rather than visible messages. Search custom code for the codes in this list before testing begins.
Frequently Asked Questions
Do obsolete transactions always fail after conversion?
Not always. Some codes remain with restrictions, others are blocked or redirect. Treat every entry as a decision to retest, because behavior depends on target release and settings.
Can I move users to MIGO before the project?
Yes. MIGO exists in ECC, so you can train users and adjust test scripts early. It reduces change load at go-live and removes one training item from the cutover period.
Is BP only a transaction change?
No. It also changes the data model, number ranges, account groups mapping, and approval workflows. CVI configuration is a core part of the work, not only a screen replacement.
How do I find which codes my users really run?
Use workload statistics in ST03N or usage recordings from SCMON, filtered by transaction code. That gives actual usage rather than assumptions and avoids training on unused functions.
If you want an automated scan of your custom code and background jobs for obsolete transaction calls, Netray can help set that up.
Related Tools
SAP S/4HANA Key Simplifications Reference
A searchable reference of the biggest ECC to S/4HANA data model and functional changes, with the action each one usually forces.
SAPSAP S/4HANA Conversion and Migration Tools Reference
A lookup of the SAP tools used at each phase of an S/4HANA conversion or migration, what each does and when to use it.
SAPSAP CVI Business Partner Gap Report ABAP Generator
Generates an ABAP report that finds customers and vendors without a Business Partner link, the first check before a CVI conversion.
SAPSAP Custom Code Inventory ABAP Query Generator (TADIR)
Generates ABAP SELECT statements against TADIR that count and list custom objects by type and package for S/4HANA remediation planning.