Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

CDS defines reusable views of business data. DCL adds rules that restrict which rows a user may read, so different users can legitimately see different results.

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.

Security separates verifying an identity from granting permission to perform business actions. A role groups relevant access, while restrictions define the allowed data and activities.

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 CDS returns fewer rows for a user: Check DCL without removing security
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 CDS/DCL read protection using classic7.52 and current documented concepts. Entity type, SQL/framework access path, projection inheritance and authorization provisioning differ by installed release; sample custom objects require local creation and syntax checks.

Reviewed relevant official SAP indexed documentation excerpts on 14 November 2026. Examples, identifiers, amounts and expected observations are illustrative; no customer SAP execution was performed. Transaction availability, labels and results depend on the installed release, deployment and local configuration.

A MANUFACTURING EXAMPLE

Explain purchasing visibility across plants

Same view, different access

CDS entity: Purchase order view. Buyer scope: Purchasing org 1000. Administrator scope: Broader permitted scope. Comparison: Same filters and identity?
What to notice: Fewer rows can be an intended authorization result. Compare context before changing a data-access rule.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
CDS entity
Purchase order view
Buyer scope
Purchasing org 1000
Administrator scope
Broader permitted scope
Comparison
Same filters and identity?
Words you’ll meet in this guide
Authentication
Checking who an identity belongs to.
Authorization
Permission for an action on particular data.
PFCG
The classic ABAP Role Maintenance transaction for organizing roles.
Role
A grouping of intended tasks and associated permissions.
Authorization object
A grouping of related permission fields checked by relevant SAP application logic.
ABAP
SAP’s programming language for business applications.
CDS
Core Data Services: reusable definitions of business data and relationships.
SQL
A language used to read and work with database data.
DCL
Data Control Language: definitions that restrict access to relevant CDS data.
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.

Same CDS view → User access rules → Permitted rows. Conceptual diagram for ABAP CDS returns fewer rows for a user: Check DCL without removing security.
Apply the idea: A manufacturing buyer sees fewer operational rows than a broad-access support user because their authorized organizational scope can differ.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. Explain purchasing visibility across plants

    A manufacturing buyer sees fewer operational rows than a broad-access support user because their authorized organizational scope can differ.

  2. Fewer CDS rows can be the intended authorization result

    ABAP CDS access control can restrict a read according to Data Control Language rules, including conditions based on the current user’s authorizations.

  3. Make the two reads comparable first

    Record the exact CDS entity accessed, SQL/service path, filters, parameters, client, business date and runtime identity.

  4. Understand implicit row conditions and PFCG aspects

    SAP describes CDS access checks during supported entity reads through ABAP SQL/Open SQL and relevant framework paths.

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.