Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

SAP CAP helps developers build business services. A bound action is an operation attached to an entity, so the request must identify which business record the action concerns.

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 CAP bound actions: Pass the entity context and test the service contract
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.

CAP Node.js custom instance-bound operations with illustrative OData V4 requests; Java, collection-bound and older runtime contracts differ.

Primary documentation reviewed on 14 November 2026 using readable full text and official indexed excerpts. Relevant full-text CAP action and authorization sections and indexed request-API text reviewed. CDL, requests and transition algorithm are original illustrative material and were not executed; installed runtime behavior must be validated.

A MANUFACTURING EXAMPLE

Approve the intended plant request

Approve which record?

Entity: Orders. Target key: 1001. Bound action: Approve. Required context: The intended order
What to notice: The operation must receive the correct entity context, not merely the action name.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Entity
Orders
Target key
1001
Bound action
Approve
Required context
The intended order
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.
CDS
Core Data Services: reusable definitions of business data and relationships.
OData
A standard for reading and updating data through a web API.
HTTP
The request-and-response protocol used by web applications and APIs.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Entity key → Bound action → Business operation. Conceptual diagram for CAP bound actions: Pass the entity context and test the service contract.
Apply the idea: A manufacturing approval application exposes a bound action, and its developer must establish which request instance the action targets.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. Approve the intended plant request

    A manufacturing approval application exposes a bound action, and its developer must establish which request instance the action targets.

  2. A bound action needs the entity identity as well as its own parameters

    For an instance-bound CAP action, the entity key comes from the binding context.

  3. Scope and prerequisites

    The worked example uses CAP Node.js with contemporary request APIs and OData V4-style invocation.

  4. Separate unbound, instance-bound and collection-bound operations

    An unbound operation belongs to the service rather than one entity instance.

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.