Since the move from SAP ERP 6.0 (ECC) to S/4HANA, many classic transactions have been deprecated or replaced. In fact, S/4HANA contains a significant number of obsolete transaction codes—yet SAP does not provide a straightforward, built-in method to identify them.
In this blog, we’ll explore how to locate these obsolete transactions and compare your ECC 6.0 system with S/4HANA. You’ll also see that while many transactions are formally marked as obsolete in S/4HANA, some remain technically available for use.
Obsolete transactions in S/4HANA typically fall into four main functional areas:
- General Settings
- Finance
- Materials Management
- Order-to-Cash
We’ll walk through each area and then discuss practical ways to generate a list of deprecated transactions using your ERP 6.0 and S/4HANA systems.
- General Settings
In S/4HANA, the most notable changes in the general settings area involve customer, vendor, and partner master data management. These legacy transactions have been replaced by the SAP Business Partner concept, with the universal transaction BP now serving as the single point of entry.
As a result, many customer/vendor-related transactions are now obsolete and redirect to BP. Examples of obsolete transactions (alphabetical order):
FD01, FD02, FD03, FD05, FD06, FD32, FD33, FK01, FK02, FK03, FK05, FK06, FK08, MAP1, MAP2, MAP3, MK01, MK02, MK03, MK05, MK06, MK12, MK18, MK19, V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23, VAP1,
VAP2, VAP3, VD01, VD02, VD03, VD05, VD06, XD01, XD02, XD03, XD05, XD06, XD07, XK01, XK02, XK03, XK05, XK06, XK07
- Finance
Finance in S/4HANA has undergone a complete redesign, with many classic ECC transactions removed or merged into streamlined “central” transactions.
Key changes include:
- FS00 now serves as the single access point for G/L account management, replacing FS01, FS02, FS03, OKB2, KA01–KA06.
- Many CK and KB transactions have been replaced by “Enjoy” transactions (add an N to the original code, e.g., CK11 → CK11N, KB11 → KB11N).
- FBL1N, FBL3N, and FBL5N are replaced by their “H” variants (e.g., FBL5H), with FAGLL03H offering enhanced, flexible reporting capabilities.
- Legacy financial transaction sets (F.2A, F.2B, F.2C, F.4A, F.4B, F.4C, F.24, F.47, FA39) are replaced by FINT and FINTAP.
- Materials Management
In MM, MIGO has become the universal transaction for goods movement. Virtually all classic MB-prefixed transactions have been retired in favour of MIGO, simplifying process execution.
- Order-to-Cash
Credit management in S/4HANA has been re-engineered. The well-known VKM1 transaction has been replaced with UKM_MY_DCDS, reflecting the updated credit management framework.
How to Identify Obsolete or Changed Transactions in Your S/4HANA Migration
When moving from ERP 6.0 to SAP S/4HANA, one of the most reliable ways to spot obsolete or modified transaction codes is to start with the source — your original ECC 6.0 system.
Retrieve the complete list of transaction codes from ECC 6.0, then compare it directly with the transaction codes in your S/4HANA environment.
Your SAP Basis team can generate these lists or assist in extracting them for side-by-side analysis. This comparison will clearly highlight which transactions have been:
- Obsoleted and no longer in use
- Replaced with new equivalents
- Still available in S/4HANA
By performing this check, you’ll not only pinpoint changes but also streamline user training, process documentation, and day-to-day operations in your new S/4HANA landscape.
Step 1 – Identify your ERP 6.0 SAP_BASIS release
- In the SAP GUI, go to System → Status.
- Click the Details button.
- Locate the SAP_BASIS component — the Release number will be shown next to it.
Example: In my case, the release number is 755.
Step 2 – Compare in S/4HANA
- Log into your S/4HANA system via the SAP GUI.
- Go to transaction SE16N and open table PRGN_CORR2.
- In the SAP Release field, enter greater than or equal to the release number you found in your ERP 6.0 system.
Step 3 – Review the results. The resulting list will display both:
- Your existing transaction codes from ERP 6.0
- The new transaction codes that replace them in S/4HANA
For instance, in the SAP system referenced for this blog, post-migration analysis revealed that 233 transactions from ERP 6.0 were rendered obsolete in S/4HANA.
Note: “Obsolete” here doesn’t always mean removed, some transactions may still work, so it’s best to test them directly in your SAP system.
Alternative Approach: You can also run the SAP Readiness Check on your ERP 6.0 system. This will map the new transactions for each process area. However, it won’t give you a complete, definitive list like the above method.