You performed a custom code check for an SAP S/4HANA conversion. In which transactions can you review the results? Note: There are 2 correct answe rs to this question.

Question

Options

• ASYCM (Simplification Database Content)
• BATC (ABAP Test Cockpit)
• CSE80 (Object Navigator)
• DSAT (Runtime Analysis)

• B
  93% (13)
• D
  7% (1)

Explanation

During an S/4HANA conversion, custom code checks run through the ABAP Test Cockpit (ATC), which aggregates all findings - compatibility violations, deprecated API usage, changed data model references - into a structured results list. From those ATC findings, developers drill into the flagged objects using SE80 (Object Navigator) to inspect and remediate the actual source code directly, making both tools essential parts of the review workflow.

Distractors:

• A (SYCM) shows the Simplification Database catalog - it lists what simplification items exist in S/4HANA, not where your custom code check results are stored.
• D (SAT) is a Runtime Analysis (profiler) tool used for performance measurement, completely unrelated to code compatibility checks.

Memory tip: Think "AC/DC power" - ATC Collects the findings, then you Drill into Code via SE80. ATC is the inbox, SE80 is the workbench.

No community discussion yet for this question.