A unique secondary key is implemented as a unique secondary index on the database. Its maintenance and creation have specific characteristics. The index must be kept current to ensure data integrity and performance, so it is updated synchronously whenever the table's data is modified (e.g., via INSERT, UPDATE, DELETE). This ensures that any subsequent read access using the index will find the correct data.

Furthermore, the ABAP Dictionary provides a flexible creation option. Instead of creating the index on the database immediately upon table activation, it can be defined for "lazy" creation. In this case, the physical index is only built on the database the first time a read access (e.g., a SELECT statement) attempts to use it.

A. It is created when a table is filled.

The index is created during table activation or upon first read access, a DDL-related event, not as a direct result of DML operations like filling the table.

B. It is updated when the modified table is read again.

Index maintenance is synchronous with data modification to ensure consistency; delaying updates until the next read would render the index inaccurate and unreliable.

1. SAP Help Portal

ABAP Keyword Documentation

ABAP Dictionary

Database Tables

Secondary Indexes:

"A secondary index is updated each time the table content is changed. This costs time." This statement supports option D.

"For this reason

you can also create secondary indexes in the ABAP Dictionary that are not created on the database immediately. The index is not created on the database until it is first accessed by a SELECT statement (or by a different read access)." This statement directly supports option C.

2. SAP Help Portal

ABAP Dictionary

Creating Secondary Indexes:

In the section on creating an index

the documentation describes the option for "Creation Type": "You can define whether the index must be created directly with the table in the database

or whether it can be created later when it is first used (that is

when the table is accessed for the first time using the index)." This confirms the "create on first access" feature (Option C). The entire purpose of an index necessitates it being updated upon modification (Option D)

which is a fundamental database principle also covered.

The recommended and standard approach for implementing row-level (instance-based) authorization for CDS views in the ABAP RESTful Application Programming Model (RAP) is to use Core Data Services (CDS) Access Control with Data Control Language (DCL). Creating a DEFINE ROLE artifact allows you to specify declarative authorization rules that are automatically enforced at the database level whenever the CDS view is accessed. This ensures that users only see the data (e.g., for specific company codes) they are authorized for, providing a secure, reusable, and performance-optimized solution that integrates with the standard SAP authorization concept (PFCG).

A. Add a WHERE sy-uname = ... filter in the projection view

This hardcodes authorization logic into the data model, making it inflexible and difficult to manage. It is not a role-based approach and violates the separation of concerns principle.

C. Put AUTHORITY-CHECK in the save method of the behavior implementation

This performs a check during the transactional save phase, not during data retrieval. It cannot prevent a user from viewing unauthorized data, which is the primary requirement.

D. Set @AccessControl.authorizationCheck: #NOTREQUIRED and filter at UI

This explicitly disables backend authorization checks and relies on insecure client-side filtering. All data would be sent from the server, creating a major security vulnerability and performance issue.

---

1. SAP Help Portal: ABAP RESTful Application Programming Model > Concepts > Authorization > Access Control.

This official documentation states

"Access control for the ABAP RESTful programming model is based on the data control language (DCL) of the ABAP Core Data Services (CDS)." It details the use of DEFINE ROLE to implement instance-based authorizations that are automatically evaluated during data access.

2. SAP Help Portal: ABAP Keyword Documentation > ABAP - Dictionary > ABAP CDS - DCL Statements > DEFINE ROLE.

Section: DEFINE ROLE describes the syntax for creating a CDS role. It explains that the WHERE condition in the access rule is "evaluated as an additional selection condition for every access to the CDS entity". This confirms that DCL provides the required row-level filtering at the database level.

3. openSAP Course: "Building Apps with the ABAP RESTful Application Programming Model"

Week 4

Unit 3: Adding Authorization Control. This unit explicitly teaches the creation of DCL files (DEFINE ROLE) as the standard method to add instance-based authorization to a RAP Business Object's data model

ensuring users can only see and edit data for which they have privileges.

The requirement is to add a new button to a Fiori elements UI that triggers a custom calculation. In the ABAP RESTful Application Programming Model (RAP), a UI button that executes logic is implemented as an "action". To add a new action to a standard, released RAP Business Object (BO), the correct extensibility mechanism is a Behavior Extension. This allows a developer to define the new action and implement its corresponding logic in an extension-specific behavior implementation class, without modifying the original SAP object.

B. SAP HANA database table extension: This is used for adding new persistent fields to the underlying data model, not for adding UI actions or business logic.

C. RAP BO Node Extension: This is used to add a completely new entity (a node), such as a child entity, to the business object's structure, not for adding behavior to an existing entity.

D. Business Service Extension: This term is too general. While the service binding will ultimately expose the new action, the specific development artifact used to define the action on the BO is the Behavior Extension.

1. SAP Help Portal - ABAP RESTful Application Programming Model: Behavior Extension. This document explicitly states

"You can use a behavior extension to add a new action

a new determination

or a new validation to a business object node." This directly maps to the question's requirement of adding a button (action) with calculation logic. (Found under SAP Business Technology Platform > ABAP Environment > Development > ABAP RESTful Application Programming Model > Concepts > Extensibility > Behavior Extension).

2. SAP Help Portal - ABAP RESTful Application Programming Model: Node Extension. This document clarifies that a node extension is used to "add a new node to the business object's composition tree." This is for structural changes (adding new entities)

which is different from the functional requirement in the question. (Found under SAP Business Technology Platform > ABAP Environment > Development > ABAP RESTful Application Programming Model > Concepts > Extensibility > Node Extension).

In ABAP Objects, when a subclass constructor is implemented, it must adhere to specific rules related to the inheritance chain. Firstly, the subclass constructor must explicitly call the constructor of its direct superclass using super->constructor. This call is mandatory and must be the first action that affects the instance; no instance components (attributes or methods accessed via the me reference) can be used before this call. This ensures the inherited part of the object is properly initialized. Secondly, the signature of the subclass constructor is independent of the superclass's constructor. This allows the subclass to define its own specific parameters required for its instantiation, which can then be used to provide the necessary values to the superclass constructor.

B. Import parameters must be evaluated before calling the superclass constructor, as their values are often required to be passed to the super->constructor call.

D. Raising an event is an action on an instance. Like accessing any other instance component, it is forbidden before the super->constructor call has completed and fully initialized the object.

1. SAP Help Portal - ABAP Keyword Documentation - CONSTRUCTOR:

Section: Instance Constructor: "In a subclass

the instance constructor must explicitly call the instance constructor of the direct superclass using the pseudo reference super->constructor

before it can access the components of its own class. ... Before the superclass constructor is called

no components of the instance can be accessed using the self-reference me." This directly supports option C and explains why D is incorrect.

Section: Instance Constructor: "The interface of the instance constructor of the subclass can be defined in any way

as long as it provides the parameters of the superclass constructor with values." This directly supports option A.

Section: Instance Constructor: "The public and protected parameters of the superclass constructor's interface are filled in the statement super->constructor." This implies that the values must be ready before the call

which contradicts option B.

The ABAP program executes a SELECT statement, which retrieves all columns for every row in the spfli table. This access pattern, where entire records are processed, is the primary use case for the Row Store in SAP HANA. The Row Store organizes data for a single record in a contiguous memory location, making the retrieval of full rows highly efficient.

The "Load Unit" setting is directly related to the storage type. For Row Store tables, the corresponding load unit is "Page Loadable." This means data is loaded from persistent storage into memory in units of pages (blocks of rows) on demand when the table is first accessed. Since the program runs rarely, this on-demand loading mechanism is suitable and avoids consuming memory unnecessarily.

A. "Storage Type" to "Column Store": This is inefficient for SELECT queries, as it requires the database to reconstruct each row from separate, non-contiguous column vectors, which is a costly operation.

B. "Load Unit to "Column Loadable": This setting is the default for Column Store tables, where individual columns are loaded into memory as needed. It is not the appropriate load unit for the Row Store.

1. SAP HANA Administration Guide for SAP HANA Platform: In the section "Row Store and Column Store

" the documentation states

"The row store is the preferred storage layout for tables that are typically accessed using SELECT (that is

all columns are requested)... Row store tables are loaded into memory page by page on demand." This directly supports the selection of "Row Store" (C) and its associated "Page Loadable" (D) characteristic. (See SAP HANA Platform 2.0 SPS 07 > SAP HANA Administration Guide for SAP HANA Platform > Chapter 10: Managing Tables > Row Store and Column Store).

2. SAP HANA SQL Reference Guide for SAP HANA Platform: The CREATE TABLE statement syntax definition specifies the table type options. It clarifies that PAGE LOADABLE is the default and standard load behavior for tables created with the ROW storage type. (See SAP HANA Platform 2.0 SPS 07 > SAP HANA SQL and System Views Reference > SQL Reference > Data Definition Language (DDL) > CREATE TABLE Statement (Data Definition)).

3. Plattner

H. (2009). A Common Database Approach for OLTP and OLAP Using an In-Memory Column Database. This foundational paper on in-memory databases explains that row-oriented storage is optimal for OLTP-style "point queries" or transactions that access an entire record at once

which is analogous to a SELECT operation. In contrast

column-oriented storage is designed for OLAP queries that aggregate data over a small subset of columns. (See Section 2

"Row vs. Column Store"). DOI: https://doi.org/10.1145/1559845.1559846

The ABAP demo view entity DEMOSALESCDSSOIVE exposes element MAT (material number) and is the object SAP’s documentation uses in the example on line 17:

“SELECT mat FROM demosalescdssoive …”.

Because the question explicitly asks for “ABAP SQL” and the code sample is working with a CDS view entity, the only statement that can retrieve field MAT exactly as shown is option B.

Option C refers to the legacy transparent table/SQL view; options A and D reference objects that do not exist or are syntactically invalid in the SAP demo model.

A. “Material” is neither a table nor a CDS entity in the SAP demo model; statement would raise a syntax error.

C. DEMOSALESSOI is a table; the sample in line 17 targets the CDS view entity, not the table.

D. Name contains blanks and is not a valid ABAP dictionary or CDS identifier; would not compile.

1. SAP Help Portal

ABAP Keyword Documentation 7.57 – Example “SELECT – From a CDS View Entity”

code lines 14-18 show: SELECT mat FROM demosalescdssoive ... (Section path: ABAP – ABAP Keyword Documentation – ABAP SQL – SELECT

Example ID: abapselectfromcdsviewentity).

2. SAP Help Portal

ABAP Platform 2022 – Demo Data Model “Sales” → CDS View Entity DEMOSALESCDSSOIVE

Element list entry “mat type matnr” (Table “Elements of the view entity”).

3. SAP Help Portal

ABAP Platform 2022 – Transparent Table DEMOSALESSOI description (note presence of MAT field and distinction between table and CDS view entity).

In the ABAP RESTful Application Programming (RAP) model, a CDS Projection View is specifically designed to expose a subset of the underlying data model for a particular business scenario or application. It acts as a consumption-specific layer, selecting only the required fields, associations, and actions from the more comprehensive base (or interface) CDS view. This ensures that the OData service for a Fiori app is lean and only contains the data and functions relevant to that specific use case, improving performance and security.

A. Database view: This is a general ABAP Dictionary object for combining tables. It is not the specific RAP artifact designed for creating an app-specific data consumption layer.

B. Metadata extension: This object is used to add or override UI-specific annotations for a CDS view. It does not define or filter the data fields of the model itself.

D. Data model view: This term typically refers to the base or interface CDS view in RAP, which defines the complete, reusable data model, not the app-specific, filtered subset.

1. SAP Help Portal

ABAP RESTful Application Programming Model > Core Data Services (CDS) > CDS Projection Views: "A CDS projection view is defined on top of a CDS data model view to serve a specific business purpose. It exposes a subset of the elements of the underlying data model view and adds consumer-specific annotations."

2. SAP Help Portal

ABAP RESTful Application Programming Model > Getting Started > Steampunk Core > Develop a Fiori App > Create the CDS Data Model > Create a CDS Projection View: "You create a CDS projection view to expose the data from the underlying data model view for a specific use case. In a projection view

you can decide which elements and associations of the underlying view you want to expose."

3. SAP Help Portal

ABAP RESTful Application Programming Model > Business Object Projection: "A business object projection is a consumption-specific view on a business object. It is used to expose a subset of the business object's functionality for a particular scenario." The CDS Projection View is the data modeling artifact for this concept.

When the clabapunitassert=>assertequals method is called and the actual (act) and expected (exp) values are not equal, the method raises an exception of type cxaunitassertfailed. The ABAP Unit framework catches this exception, marks the specific test method as 'failed', and records the failure in the test results log. The optional msg parameter is used to provide a custom, descriptive message in this log, which helps in diagnosing the reason for the failure. The execution of other test methods in the test run continues.

A. The ABAP Test Cockpit (ATC) is a tool for static code analysis, whereas ABAP Unit is for dynamic testing. A runtime test failure does not modify ATC configuration.

B. A failed unit test does not inherently block a transport. This behavior depends on the quality assurance settings configured in the transport management system.

C. The test method's execution is terminated, but the overall test run is not "aborted" in the sense of a system crash. The framework handles the failure gracefully and proceeds with other tests.

1. SAP Help Portal - ABAP Keyword Documentation

clabapunitassert:

"If the check is not successful

an exception of the type CXAUNITASSERTFAILED is triggered." This exception is handled by the ABAP Unit framework to log the failure. The msg parameter is described as an "optional commentary that is displayed if the assertion fails."

Source: SAP Help Portal

ABAP Platform

ABAP Keyword Documentation

System Classes and Interfaces -> CLABAPUNITASSERT.

2. SAP Help Portal - ABAP Unit Test Results:

"The ABAP Unit result display shows you the outcome of a test run... For each test that has run

the result display shows the outcome: Passed

Failed

or an error icon for a test that could not be run." This confirms that a failed assertion results in a logged outcome.

Source: SAP Help Portal

ABAP Platform

ABAP Development Tools (ADT) -> Testing ABAP Code -> ABAP Unit -> Running and Evaluating ABAP Unit Tests.

In C#, when creating an instance of a derived class (subl), the Class constructor (static constructor) of that derived class executes first. The runtime then proceeds to initialize the instance. The subl instance constructor calls the base class constructor, which triggers the Class constructor of superl (if not already run) to initialize the base type. Once type initialization is complete, the Instance constructor of superl runs to initialize the base object, followed finally by the Instance constructor of subl to complete the derived object's initialization.

Microsoft Learn. (2023). Static Constructors (C# Programming Guide). Retrieved from learn.microsoft.com. (Confirming static constructors are called before the first instance is created and the order of execution for derived types).ECMA International. (2017). Standard ECMA-334: C# Language Specification, 5th Edition. Section 15.12 (Static Constructors) and Section 15.11 (Instance Constructors). (Defines the exact triggering rules for static constructors and the chaining of instance constructors).Albahari, J., & Albahari, B. (2021). C# 10 in a Nutshell. O'Reilly Media. Chapter 3: Classes and Structs. (Explicitly details the initialization order: Subclass static $\rightarrow$ Base class static $\rightarrow$ Base class instance $\rightarrow$ Subclass instance).

The annotation @Environment.systemField: #SYSTEMLANGUAGE links the CDS view parameter plangu to the ABAP system field sy-langu. This creates an implicit default value. When the CDS view is consumed, either directly in an ABAP SQL statement or as a data source in another CDS view (view-on-view), the system automatically passes the value of sy-langu to the parameter if no explicit value is provided. However, this is only a default mechanism. The consumer of the CDS view can still explicitly pass a different value to the parameter, which will override the automatic system language value.

C. The value of sy-langu will be passed to the CDS view automatically when you use the CDS view in ABAP but not when you use it in another view entity

This is incorrect. The default value mechanism applies in all consumption scenarios, including when the view is used as a data source for another CDS view.

D. It is no longer possible to pass your own value to the parameter.

This is incorrect. The annotation provides a default value, not a restriction. It is always possible to override this default by explicitly passing a value to the parameter.

1. SAP Help Portal

ABAP Keyword Documentation: ABAP CDS - DEFINE VIEW ENTITY

parameterannot.

Section: @Environment.systemField

Content: This section explicitly states

"Specifies a system field of the ABAP environment whose value is passed implicitly to the parameter in an Open SQL read." It further clarifies

"If an explicit actual parameter is specified for an input parameter p... this value is used. Otherwise

the value of the system field specified in the annotation is used." This directly supports that the value is passed automatically (supporting A) and can be overridden (supporting B and refuting D).

2. SAP Help Portal

ABAP Keyword Documentation: ABAP CDS - Parameter Passing.

Section: Parameter Passing from a CDS View

Content: This documentation explains how parameters are handled in view-on-view scenarios. If a consuming view uses a parameterized view

it must handle the parameter. If it doesn't explicitly pass a value

the default mechanism of the underlying view (in this case

the @Environment.systemField annotation) is triggered. This supports option A and refutes option C.