Resolve syntax errors and obsolete references in ABAP Development Tools using automated single and mass quick fixes in the ATC Problems view.
Once you run the ABAP Test Cockpit (ATC) with the check variant S4HANA_READINESS across your custom codebase for SAP S/4HANA, you receive a detailed list of findings. At Harbor Supply Co., running this check against 4,000 custom objects returns hundreds of issues ranging from syntax incompatibilities to obsolete transaction calls. Remediating these findings does not mean rewriting every program by hand. By combining manual fixes with automated quick fixes in ABAP Development Tools (ADT), you can clear standard findings systematically.
Previous lesson: Running S/4HANA Readiness Checks with ABAP Test Cockpit | Next lesson: S/4HANA Data Model Changes: MATNR, KONV, VBUK and MATDOC
Remediation begins with sorting findings by priority. ATC categorizes findings into priority 1, priority 2, and priority 3. As covered in the previous lesson, priority 1 findings are blockers such as syntax errors and missing objects that stop a program from compiling. Priority 2 findings compile but fail at runtime or return wrong data, such as reads on VBUK or KONV. Priority 3 findings are performance and modernization warnings that do not break the program.
When planning your sprint, focus on priority 1 issues first. If a custom program cannot compile, you cannot run functional tests. Group your findings by check title and error message rather than tackling them object by object. When you see forty occurrences of the same obsolete function module, fixing them as a batch takes a fraction of the time needed when jumping between unrelated issues.
Common Mistake: Do not start modifying code before verifying whether the object is still used in production. Check your usage data from transaction SUSG before fixing any finding. Fixing an obsolete call in a program that has had zero executions over the past twelve months wastes development and testing capacity.
A frequent finding in classic custom code is the direct invocation of obsolete transactions. In SAP ECC, custom batch reports and dialog programs often call classic inventory or sales transactions using the CALL TRANSACTION statement. Many of these classic transactions are discontinued in SAP S/4HANA.
At Harbor Supply Co., the custom report ZMM_STOCK_MOVES contains a call to transaction MB11 for goods movements. In SAP S/4HANA, transaction MB11 is unavailable, and transaction MIGO serves as the single transaction for goods movements.
abapCopy
If your code triggers obsolete transactions via batch input or CALL TRANSACTION, you cannot simply substitute the transaction code because the screen flow and parameter IDs differ. For automated processing, replace transaction calls with supported APIs such as standard function modules or object-oriented classes. When interactive navigation is required, update the call to target the modern transaction:
abapCopy
Review the specific simplification item linked in the ATC message before applying your fix. The Simplification Database provides notes explaining whether an API replacement exists or if the calling logic requires redesign.
Remediating code line by line is slow when many findings follow standard patterns. ABAP Development Tools (ADT), the Eclipse based Integrated Development Environment (IDE), provides automated corrections called Quick Fixes.
Think of a quick fix like a spellchecker for ABAP: it suggests the correct replacement for an outdated word and leaves the rest of your sentence alone.
When you open an object with an ATC finding in the ADT editor, the problem appears with a warning or error marker in the left margin. Position your cursor on the underlined code and press Ctrl+1 (or Cmd+1 on macOS) to bring up the Quick Fix menu. ADT displays the available automated remediation options based on the check message.
Quick fixes apply standard transformations reliably. Typical areas where automated quick fixes apply include:
Pro Tip: Always check the preview of a quick fix before you apply it, and confirm that the change keeps your business logic intact.
Applying individual quick fixes inside the source editor is practical for a single program. However, when Harbor Supply Co. faces several hundred instances of identical field length issues across dozens of packages, individual fixes become repetitive. ADT offers mass quick fixes directly from the ATC Problems view.
To perform a mass fix, run ATC with check variant S4HANA_READINESS on your custom package. Group the results in the ATC Problems view by Check Title. Expand the category containing findings with available quick fixes. A light bulb icon next to the finding indicates that an automated fix exists.
Select multiple findings in the list using Shift+Click or Ctrl+Click. Right-click the selection and choose Recommended Quick Fixes.
textCopy
The wizard prompts you for a transport request and modifies all selected programs simultaneously. Because the changes apply automatically across multiple objects, keep the scope of each mass fix execution limited to related objects within the same development package.
Applying quick fixes changes the source code on the server, but the ATC Problems view does not update automatically. You must run a recheck to verify that the errors are resolved and that no secondary syntax issues were introduced.
In the ATC Problems view, right-click the package or the specific findings you remediated and select Recheck. ATC sends the updated source code back through the check engine. If the fix satisfied the check rules, the finding disappears from the active list.
Quick Challenge: After resolving syntax errors and obsolete statements, run an extended syntax check in ADT. Verify that inline declarations and host variables added during remediation follow modern ABAP standards.
Once your priority 1 and priority 2 findings are resolved, your code compiles against the SAP S/4HANA dictionary and reads data from the right places. You are now prepared to address underlying database schema shifts where automated quick fixes cannot rewrite complex custom SQL queries.
Review this legacy routine from Harbor Supply Co. that processes material numbers and calls an obsolete transaction:
abapCopy
Perform the following tasks:
Ctrl+1 to observe the proposed quick fixes.In the next lesson, S/4HANA Data Model Changes: MATNR, KONV, VBUK and MATDOC, you will explore the major database table transformations and adapt your custom queries accordingly.
Was this lesson helpful?