The Ultimate C_C_SAC_2102 - SAP Certified

Application Associate - SAP Analytics Cloud

C_SAC_2102 - SAP Certified Application Associate - SAP Analytics Cloud Certification Exam
Credential. The following features that are highlighted with '*' are client-specific and are therefore
available for all supported ABAP systems.

ABAP Development Tool provides features that are client-specific or require a specific back-end version.
Consequently, this overview covers all client-specific and back-end-specific dependencies. To highlight
and contrast back-end-specific help content in the relevant context, the following icons are used:
for on-premise releases

for SAP Cloud Platform ABAP Environment shipments

This topic contains release information about:

ABAP Development Tools

Displaying ATC Check Failures

Working with Data Preview

ABAP RESTful Programming Model

Automatically Drawing Primary Key Values for Managed Business Objects

New Options for Action and Function Results

Reporting Messages in ADJUST_NUMBERS and SAVE

Documenting Behavior Definitions

ABAP Development Tools
Working with Data Preview
Copying Rows as ABAP Value Statement

You can now copy all the rows to the clipboard as an ABAP value statement in Data Preview. This
enables you to copy the rows as ABAP value statement and use it in the ABAP code to work with internal
tables.
ABAP RESTful Programming Model
Automatically Drawing Primary Key Values for Managed Business Objects
The managed runtime framework can now automatically generate key values in scenarios with UUID
keys if managed numbering is defined in the behavior definition.

Syntax for defining managed numbering in the behavior definition:

[implementation] managed [implementation in class ABAP_CLASS [unique]];
define behavior for Entity [alias AliasedName]
lock (master|dependent() )
field ( [read only,] numbering:managed ) KeyField1, [KeyField2];
For more information, see Automatically Drawing Primary Key Values in Managed BOs.

New Options for Action and Function Results

The BO runtime framework now supports results for actions and functions other than $self. The results
can be entities of the same BO the action is defined for, entities of other BOs, or result structures. To
differentiate between result entities and result structures the syntax element entity has been introduced.
In addition, you can now create actions, for which the action consumer can decide whether the result shall
be returned completely or only parts of it, for example the keys only. Such an action must be marked with
the keyword selective in the behavior definition.

define behavior for CDSEntity

Action with result entity
action ActionName result [cardinality] entity OutputEntity
Action with result structure