Virtual Elements in CDS Projection Views
Virtual elements are fields defined in CDS projection views that have no corresponding column in the database and are instead calculated at runtime. Developers use them to expose computed or transient data — such as values derived from application logic — as part of a CDS-based data model without persisting those values to the database.
Tutorials that teach this
Prerequisites
- Concept SAP BTP ABAP Environment Setup The provided sources do not contain sufficient information to define a specific concept, as the concept name is listed as "undefined." The sources cover topics such as [getting started in the ABAP Environment](https://help.sap.com/docs/btp/sap-business-technology-platform/2ffdd2412aff494dbf3de31089c965d4?locale=en-US&state=PRODUCTION&version=Cloud), subscribing to Web Access for ABAP, creating service keys, importing content from abapGit repositories, and configuring remote code analysis in ATC, but no single named concept is identified for definition.
- Concept ABAP CDS View Creation and Development The provided sources do not contain sufficient information to define a specific SAP developer concept, as the concept supplied is "undefined" and the source snippets offer only tutorial titles and brief fragments without substantive explanatory content. Based on the available context, these sources relate to ABAP development on [SAP Business Technology Platform](https://help.sap.com/docs/btp/sap-business-technology-platform/5de837488d6e431da008ae374a405919?locale=en-US&state=PRODUCTION&version=Cloud), covering topics such as building SAP Fiori apps, authorization fields, and extending data sources using the ABAP RESTful Application Programming Model. A developer working in this space uses these resources to guide tasks such as creating check tables for authorization fields, consuming queries on SAP Analytics Cloud, and extending Core Data Services in the ABAP Environment.
- Concept OData UI Service Development The concept name provided is "undefined," so no specific SAP developer concept can be identified or defined from the available sources. The sources reference topics such as OData UI services, CDS views, Business Object interfaces, and SAP Fiori apps, but without a defined concept to describe, a valid documentation entry cannot be produced. Please provide a valid concept name to generate an accurate definition.
- Concept ABAP RESTful Application Programming Model (RAP) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several broad SAP BTP and ABAP topics — such as the ABAP Environment, RAP development, authorization basics, and system workload analysis — without converging on a single, specific concept to define. There is insufficient information to produce an accurate, source-grounded definition.
- Concept RAP Business Object Code Generation The concept name was not provided, so a specific definition cannot be generated. Please supply the concept to be defined so it can be accurately described based on the available source material.
- Concept ABAP Object-Oriented Class Implementation The concept name was not provided and cannot be determined from the available source snippets, which cover unrelated topics such as change document objects, units of measurement, dimensions, and number range objects. No coherent single concept definition can be grounded solely in these sources.
- Concept SAP BTP ABAP Environment (Steampunk) The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as the [XCO Library](https://help.sap.com/docs/btp/sap-business-technology-platform/c154dffe892b4d9ea4566722f0bcd5f1?locale=en-US&state=PRODUCTION&version=Cloud), ATC configurations, abapGit, and the Cloud Connector — no grounded definition can be written for an "undefined" concept. Please provide a valid SAP developer concept name so an accurate, source-grounded definition can be produced.
- Concept ABAP Class Definition and Implementation The concept name is not defined in the provided sources, so a precise label cannot be confirmed. Based on the available snippets, **ADT Class Execution** is a capability that allows developers to [execute ABAP classes directly in ABAP Development Tools (ADT)](https://help.sap.com/docs/btp/sap-business-technology-platform/6f0e26492b854627ac19a9a34205a546?locale=en-US&state=PRODUCTION&version=Cloud) without additional setup steps. Separately, the XCO library provides APIs for [reading a class](https://help.sap.com/docs/btp/sap-business-technology-platform/bc23e26f236042c48171d850e82843b9?locale=en-US&state=PRODUCTION&version=Cloud) programmatically, enabling developers to inspect class definitions such as `zcl_xco_doc_cp_cs_class` at runtime.
- Concept SAP Fiori Elements UI with OData V4 The provided sources do not contain sufficient information to define the concept "undefined." The sources cover various SAP Fiori elements topics — such as OPA testing, navigation, quick views, and header field editability — but none of them describe or reference a concept explicitly identified as "undefined."
- Concept RAP Managed Business Object The concept provided is **undefined**, and the supplied sources do not describe or name a specific SAP developer concept that can be reliably identified and defined. The sources reference topics such as [modeling protection against unauthorized write activities](https://help.sap.com/docs/btp/sap-business-technology-platform/fb6a6213fced4fe8af8466e25fa73035?locale=en-US&state=PRODUCTION&version=Cloud) and the ABAP RESTful Application Programming Model, but without a named concept to define, no accurate and grounded definition can be produced.
- Concept Generate ABAP Repository Objects Wizard The concept name is not defined in the provided sources, and no clear single concept is described across the snippets beyond general references to ABAP and RAP development tasks on SAP BTP. A meaningful, source-grounded definition cannot be written without a valid concept name or supporting descriptive content in the sources.