Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An API is an interface another program can use. A released SAP API has an explicit permitted use; merely finding an object in a system does not make it a supported extension point.

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 ABAP Cloud released APIs: Check the release contract before using an object
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 Cloud released-object consumption; exact contracts, visibility and component-access capabilities depend on product and backend release.

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

A MANUFACTURING EXAMPLE

Choose a supported contract for a plant extension

Existence versus supported use

Object: An internal SAP class. Object visible: Yes. Release contract: Not yet confirmed. Extension decision: Check permitted usage
What to notice: An object being visible is different from its being released for your language version and purpose.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Object
An internal SAP class
Object visible
Yes
Release contract
Not yet confirmed
Extension decision
Check permitted usage
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.
CDS
Core Data Services: reusable definitions of business data and relationships.
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.

Available object → Release contract → Supported use. Conceptual diagram for ABAP Cloud released APIs: Check the release contract before using an object.
Apply the idea: A manufacturer builds an order-summary extension and must distinguish a technically visible SAP object from an interface released for its development model.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. Choose a supported contract for a plant extension

    A manufacturer builds an order-summary extension and must distinguish a technically visible SAP object from an interface released for its development model.

  2. Visibility is the start of discovery, not permission to depend on an object

    For ABAP Cloud development, inspect an object's API state, release contract and applicable visibility before using it as a dependency.

  3. Scope: ABAP Cloud, language versions and software components

    This guide is for developers planning an ABAP extension or reviewing a legacy dependency.

  4. Read release contract and visibility together

    C0 identifies dedicated extension use, C1 system-internal consumption and C2 remote API use in the reviewed documentation.

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.