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.
More SAP tools
See allNew to SAP ECC 6.0? Start with the SAP ECC 6.0 guide and toolkit, or plan with SAP ECC to S/4HANA Conversion Planner, Training Path Builder, Upgrade Path Planner.
Keep exploring
Free tools
- SAP Role Design WorksheetAn editable worksheet for designing SAP single, derived and composite roles with transaction counts, critical objects and an exposure score per role.
- SAP PM Transaction Codes ReferenceA searchable list of the transaction codes SAP PM users and consultants reach for daily, grouped by process step.
- SAP PM Maintenance Order Types, Tables and Transactions ReferenceSearchable lookup of SAP plant maintenance order types, order transactions, order tables and system statuses.
ERP fixes and how-tos
- SAP PO Report by Creator: Transactions and EKKO-ERNAMWhich SAP transaction lists purchase orders by creator? Use ME2N or ME80FN with dynamic selection on Created By, or read EKKO-ERNAM in SE16N. Steps and variants.
- How to Use BAPI_TRANSACTION_COMMIT CorrectlyBAPIs never commit their own update. Here is when to call BAPI_TRANSACTION_COMMIT with WAIT, and why a BAPI can run fine and still save nothing.
- SAP S/4HANA upgrade steps: a runbook for manufacturersStep-by-step SAP S/4HANA upgrade and conversion runbook: readiness check, Maintenance Planner, custom code, SUM, testing and cutover for manufacturers.
Runs with your ERP
- Loftware with SAP ECC and S/4HANA: label design and printing from SAP transactionsHow Loftware and the NiceLabel ABAP package drive labels from SAP ECC and S/4HANA, including SAP GLM Plus, data flows, setup steps and pitfalls to avoid.
- SAP Ariba Invoicing with SAP S/4HANA and ECCHow SAP Ariba Invoicing captures invoices from email, PDF and images with AI OCR and routes them for matching and approval against SAP purchasing data.
- Esker Accounts Payable Automation with SAP S/4HANA and ECCHow Esker Accounts Payable Automation captures supplier invoices, matches them to POs and posts to SAP S/4HANA and ECC, plus setup steps, pitfalls and options.
AI on your ERP
- Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANASAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
- AI on SAP for Aerospace and Defense Manufacturers, Without the ITAR ExposureEvaluate SAP for aerospace and defense industrial AI: S/4HANA and ECC data access, serial genealogy, config control and quoting, with ITAR data kept in-house.
Integrations
- How to add Slack to SAP ECC 6.0Build a Slack app for SAP ECC 6.0: slash commands that read stock and orders via BAPIs, interactive approvals, alert channels and Socket Mode for on-prem.
- How to build a mobile app for SAP ECC 6.0Build a mobile or barcode app for SAP ECC 6.0 on the shop floor: goods movements, production confirmations, approvals and offline handling over RFC or OData.