Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Authorization rules decide which users may call a service or act on records. CAP’s requires and restrict annotations express different permission conditions for those operations.

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 authorization: Why hiding a button does not protect the API
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 declarative authorization and custom instance-bound operations; supported annotations and Java behavior require version-specific review.

Primary documentation reviewed on 14 November 2026 using readable full text and official indexed excerpts. Relevant full-text CAP authorization sections and indexed authentication guidance reviewed. Model and policy matrix were not compiled or penetration-tested; deployed claims, Java differences and custom handler behavior need runtime verification.

A MANUFACTURING EXAMPLE

Enforce manufacturing request approval responsibility

Separate reading and approving

User role: Order viewer. READ operation: Permitted by relevant rule. Approve action: Requires additional permission. Review: Service and entity rules
What to notice: Opening the same application does not make every operation equally authorized.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
User role
Order viewer
READ operation
Permitted by relevant rule
Approve action
Requires additional permission
Review
Service and entity rules
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.
API
A defined interface through which programs exchange data or request actions.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

User permissions → Service restrictions → Allowed operation. Conceptual diagram for CAP authorization: Why hiding a button does not protect the API.
Apply the idea: A factory request application needs a reviewer to act only within the assigned business responsibility, including the intended self-approval restriction.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. Enforce manufacturing request approval responsibility

    A factory request application needs a reviewer to act only within the assigned business responsibility, including the intended self-approval restriction.

  2. Protect the service endpoint, then make the interface reflect that policy

    A hidden or disabled button changes what one UI presents.

  3. Scope and prerequisites

    The worked model targets CAP Node.js instance-bound actions and generic service authorization.

  4. Separate authentication, role access and instance policy

    Authentication establishes a verified caller identity and claims.

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.