Business Semantic Data Elements in ABAP CDS

As someone working on SAP S/4HANA Public Cloud or ABAP Cloud, one of the biggest improvements you can make to your CDS models is choosing the correct data type.

While generic built-in types such as abap.char(), abap.numc() and abap.dec() are available, SAP also provides hundreds of business semantic data elements that already represent real-world business concepts.

Using these semantic data elements makes your CDS View Entities easier to understand, improves consistency across applications, and aligns your development with SAP standards.

One of the easiest ways to distinguish an experienced SAP architect from a beginner is by looking at the data types used inside CDS View Entities.

Beginners often define almost every field using generic built-in data types.

cast( Product as abap.char(40) )
cast( CompanyCode as abap.char(4) )
cast( Currency as abap.char(5) )

Although technically correct, these definitions do not communicate the business meaning of the data.

Experienced SAP developers instead prefer semantic data elements that already exist within the SAP data dictionary.

cast( Product as MATNR )
cast( CompanyCode as BUKRS )
cast( Currency as WAERS )

Consider the following example.

cast( field1 as abap.char(4) )
cast( field2 as abap.char(4) )
cast( field3 as abap.char(4) )

Looking only at the code, there is no indication of what each field actually represents.

Each field could represent a Company Code, Plant, Currency, Sales Organization, Storage Location, or any other four-character business value.

Now compare the same code using SAP semantic data elements.

cast( CompanyCode as BUKRS )
cast( Plant as WERKS_D )
cast( Currency as WAERS )

The business meaning is immediately obvious without requiring comments or additional documentation.

Organizational data elements represent the enterprise structure of an SAP system. They define how a business is organized into company codes, plants, purchasing organizations, sales organizations, and other operational units.

These are among the most frequently used semantic data elements in almost every SAP implementation and appear extensively in CDS View Entities, RAP Business Objects, and standard SAP APIs.

If you work on Sales, Purchasing, Inventory, Manufacturing, or Finance projects, you will encounter these semantic data elements almost every day.

cast( CompanyCode          as BUKRS   ) as CompanyCode,
cast( Plant                as WERKS_D ) as Plant,
cast( StorageLocation      as LGORT_D ) as StorageLocation,
cast( PurchasingOrg        as EKORG   ) as PurchasingOrganization,
cast( SalesOrganization    as VKORG   ) as SalesOrganization

Notice how the CDS immediately communicates the business meaning of every field without requiring comments or additional documentation.

Master data represents the core business entities of an organization. These identifiers are reused throughout SAP business processes and are among the most important semantic data elements to remember.

Whether you build Procurement, Sales, Manufacturing, Finance, or RAP applications, these semantic types appear repeatedly across SAP business objects.

Financial applications require standardized semantic types for currencies, amounts, and exchange rates. SAP provides dedicated data elements for these concepts instead of relying on generic decimal fields.

These semantic types become especially important when working with currency conversion functions, analytical CDS Views, and financial reporting.

Quantity fields are almost always associated with a Unit of Measure. SAP provides dedicated semantic data elements for both quantities and units to ensure consistency across logistics, manufacturing, inventory, and procurement applications.

cast( BaseUnit        as MEINS   ) as BaseUnit,
cast( SalesUnit       as VRKME   ) as SalesUnit,
cast( PurchaseUnit    as BSTME   ) as PurchaseUnit,
cast( Quantity        as MENGE_D ) as Quantity

These semantic data elements are frequently used together with UNIT_CONVERSION() and quantity semantics in CDS View Entities.

Almost every business application stores dates, times, or timestamps. SAP provides dedicated semantic types that clearly indicate the type of temporal information being stored.

cast( CreationDate      as DATS ) as CreationDate,
cast( CreationTime      as TIMS ) as CreationTime,
cast( LastChangedUTC    as TZNTSTMPS ) as LastChangedTimestamp

These semantic types become particularly useful when working with CDS date functions, timestamp calculations, and RAP audit fields.

SAP Purchasing applications use standardized semantic data elements for Purchase Orders and Purchase Requisitions.

cast( PurchaseOrder      as EBELN ) as PurchaseOrder,
cast( PurchaseOrderItem  as EBELP ) as PurchaseOrderItem,
cast( PurchaseReq        as BANFN ) as PurchaseRequisition,
cast( PurchaseReqItem    as BNFPO ) as PurchaseRequisitionItem

Sales and Distribution applications rely on semantic data elements representing Sales Orders, Billing Documents, and related business objects.

cast( SalesOrder       as VBELN_VA ) as SalesOrder,
cast( SalesOrderItem   as POSNR_VA ) as SalesOrderItem,
cast( BillingDocument  as VBELN_VF ) as BillingDocument

Semantic data elements communicate business meaning immediately. Developers reading the CDS View Entity can understand the purpose of a field without referring to technical documentation.

Material Management applications frequently use semantic data elements representing batches, valuation areas, and valuation types. These fields are commonly found in Inventory Management, Material Ledger, and Warehouse Management scenarios.

cast( Batch           as CHARG_D ) as Batch,
cast( ValuationArea   as BWKEY   ) as ValuationArea,
cast( ValuationType   as BWTAR_D ) as ValuationType

SAP also provides semantic types representing user-related information. These appear frequently in audit fields, workflow, approvals, and administrative applications.

cast( CreatedBy as SYUNAME ) as CreatedBy,
cast( Client    as MANDT   ) as Client

Besides business-specific data elements, SAP provides several generic semantic types that are reused throughout almost every SAP application.

These semantic data elements are not tied to a specific business module but are shared across Finance, Sales, Purchasing, Logistics, and many other SAP applications.

One of the most common use cases for business semantic data elements is within CAST expressions.

Instead of casting to a generic built-in type, developers often cast directly to the corresponding SAP semantic type.

cast( Product              as MATNR   ) as Material,
cast( CompanyCode          as BUKRS   ) as CompanyCode,
cast( Plant                as WERKS_D ) as Plant,
cast( Customer             as KUNNR   ) as Customer,
cast( Supplier             as LIFNR   ) as Supplier,
cast( Currency             as WAERS   ) as Currency,
cast( BaseUnit             as MEINS   ) as BaseUnit

This approach improves readability while ensuring the CDS model uses SAP's standard business semantics.

Prefer learning by watching?

This lesson is accompanied by a complete step-by-step implementation in Eclipse ADT. The video uses the same examples, naming conventions, and CDS code demonstrated throughout this tutorial.