Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

ABAP is SAP’s programming language. ATC and Code Inspector inspect programs for possible problems without running the business task; a check variant is the chosen set of rules.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

ABAP is SAP’s programming language for business applications. A program reads data, applies rules and produces a result. Start with the objects involved before investigating code.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP ATC versus Code Inspector: Read static-check findings in context
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

ABAP ATC and Code Inspector in classic ABAP/ADT landscapes; central, remote and target-release workflows vary by installed version.

Primary documentation reviewed on 14 November 2026 using readable full text and official indexed excerpts. Documentation review only; authored examples were not compiled or executed in an SAP system.

A MANUFACTURING EXAMPLE

Check a plant purchasing extension before release

Compare the check setup

Object: Z_ORDER_REPORT. Team A variant: Local checks. Team B variant: Project checks. Finding sets: May differ
What to notice: The rule set matters: no findings in one variant does not prove that every other check passed.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Object
Z_ORDER_REPORT
Team A variant
Local checks
Team B variant
Project checks
Finding sets
May differ
Words you’ll meet in this guide
Program
A set of instructions executed by a computer.
Class
A reusable unit that groups data with operations called methods.
Database
Organized information kept beyond one program execution.
Internal table
A list of rows held temporarily in an ABAP program’s memory.
Key
One or more fields used to identify or find a record.
ABAP
SAP’s programming language for business applications.
API
A defined interface through which programs exchange data or request actions.
ADT
ABAP Development Tools: SAP tools for ABAP development in Eclipse and, on supported systems, Visual Studio Code.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Program → Check variant → Findings. Conceptual diagram for SAP ATC versus Code Inspector: Read static-check findings in context.
Apply the idea: A manufacturer's ABAP team checks a component purchasing report before deployment and must explain why two static-check runs return different findings.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Check a plant purchasing extension before release

    A manufacturer's ABAP team checks a component purchasing report before deployment and must explain why two static-check runs return different findings.

  2. A clean result is meaningful only with its check context

    Use Code Inspector to understand and run a selected collection of static checks; use ABAP Test Cockpit, or ATC, to work with quality-check runs and their findings in the workflow supported by your landscape.

  3. Audience, access and release boundaries

    This guide is for developers and reviewers who can display repository objects and run permitted local quality checks.

  4. Separate objects, rules and result records

    An object set answers what is inspected: a particular class, program, package or supported selection.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.