Ansicht
Dokumentation

ABENCDS_INTERSECT_V2 - CDS INTERSECT V2

CPI1466 during Backup CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

- CDS View Entity, SELECT, INTERSECT

Effect

The set operator INTERSECT returns all distinct rows that are included in all result sets of multiple SELECT statements of . As a prerequisite, the result sets must have the same number of elements and the element pairs that occur in the same position of the result set must have a compatible data type. All data types are supported except for STRING, RAWSTRING, LCHR, LRAW, and GEOM_EWKB. A view using INTERSECT can itself be the left side of a further view using INTERSECT.

As a prerequisite for using the statement INTERSECT in a CDS view entity, the CDS view entity annotation Metadata.ignorePropagatedAnnotations: true must be specified.

Rules for the Elements of a View Using INTERSECT

The first SELECT statement defines the signature of the INTERSECT view. The elements of the result set of the INTERSECT view have the following properties:

Element names

The direct element names or the alternative element names defined using AS must match for each column in the SELECT lists of all SELECT statements and are used.

Key elements

They key elements of all SELECT lists must match. Otherwise, a syntax check error occurs.

Element annotations

Only the SELECT list of the first SELECT statement can define element annotations. In all subsequent branches, element annotations are forbidden.

Data type

The SELECT list of the first SELECT statement determines the DDIC data type of each element of the CDS entity.

The data type used to create the result set on the database is a data type whose value range covers the data types of the associated columns of all result sets involved.

The following table shows which data types can be combined with each other in a view using INTERSECT. On the left side, the data types of the SELECT list of the first SELECT statement are listed and the other columns specify with which data types of the following SELECT lists they can be combined.

First/following

INT1

INT2

INT4

INT8

DEC

DF16_...

DF34_...

CURR

QUAN

FLTP

CHAR

SSTRING

STRING

NUMC

DATS

DATN

TIMS

TIMN

UTCL

ACCP

CLNT

LANG

UNIT

CUKY

RAW

GEOM_EWKB

INT1

INT2

INT4

INT8

DEC

DF16_...

DF34_...

CURR

QUAN

FLTP

CHAR

SSTRING

STRING

NUMC

DATS

DATN

TIMS

TIMN

UTCL

ACCP

CLNT

LANG

UNIT

CUKY

RAW

GEOM_EWKB

There are no further restrictions to note in combinations using "x". The following rules apply to the other combinations:

In combinations with "w", the length or the value range of the data type in the first SELECT must be long enough for all following SELECT lists. If this is not the case, a syntax check warning is raised.

In combinations using "l", the lengths of the data types must match exactly.

In combinations using "d", the number of decimal places must match exactly.

If the length or value range of the first element does not cover the following elements in combinations with "w", the value returned by the database can be too great for the data type of the element of the CDS entity. It is still possible to activate the view here, but the content may be truncated or exceptions may be raised in queries if a type reference is applied to the entity. This is due to the assignment rules of the INTO clause. Assignments to ABAP data objects with a sufficiently large value range, on the other hand, do not cause problems.

Amounts and Quantities in INTERSECT Views

If the elements of a UNION view are CDS amount fields, CDS quantity fields, or CDS calculated quantities, the following rules apply:

Since the annotation Metadata.ignorePropagatedAnnotations: true is mandatory in UNION views, all reference annotations are lost and must be provided again within the first SELECT branch.

For elements of data type CURR or QUAN as well as for calculated quantities, the reference annotation is mandatory.

Elements of other data types lose their reference information and their characteristic as amount or quantity field. The respective reference annotation can be assigned anew to declare the field an amount or quantity field. This is optional.

Calculated quantity fields can be merged only with other calculated quantity fields. Amount fields and quantity fields can be merged with each other, as long as the data types match (see matrix above).

For amount fields of type CURR, the number of decimal places must match exactly in all UNION branches.

Elements of data type CURR are incompatible to any other data type. The function CURR_TO_DECFLOAT_AMOUNT can be used to convert an amount field of data type CURR into an amount field of data type DECFLOAT34.

Associations in Views Using INTERSECT

A CDS view entity in which result sets are formed with INTERSECT can define and expose CDS associations. Such an association must be defined and exposed in the same way in all SELECT statements combined with INTERSECT. That is, CDS associations that are exposed in the respective SELECT lists must appear in all SELECT statements combined with INTERSECT and the following requirements must be met:

They have the same cardinality.

They must be exposed at the same position in the SELECT list using a path expression.

They must have the same ON conditions, that is:

The conditions must relate to the same fields in the association source and association target and express the same logic for these fields.

The fields of the association source that are listed in an ON condition must be at identical positions in the SELECT list.

It is not required that the associations are defined with the same alias name.

These rules also apply if a CDS association is defined in a data source of a SELECT statement and is exposed by the current statement. From outside, the CDS associations with the same name that are exposed in the individual SELECT lists act like a CDS association exposed by the INTERSECT result set. There are no restrictions on CDS associations that are not exposed in the SELECT lists.

Nesting of INTERSECT Branches

In CDS view entities, nesting of INTERSECT clauses is possible. To nest an INTERSECT clause within another INTERSECT clause, use brackets ( ... ). A nested INTERSECT clause is merged first and its result set is then merged again with the result sets of the other INTERSECT branches.

Defining new CDS compositions and to-parent associations is not possible in a view using INTERSECT. Exposing CDS compositions and to-parent associations that were defined in the data source of the SELECT statement is possible.

Annotations are only allowed in the SELECT list of the first SELECT statement. In all following branches, annotations are not allowed.

Notes

If the length of the value range of an element from the SELECT list of the first SELECT statement does not cover the associated elements of the following SELECT statements, it is advisable to define an appropriate type with a suitable CAST expression.

The maximum number of different SELECT statements that can be merged using INTERSECT depends on the database system. If this number is exceeded, the CDS view entity cannot be activated.

The addition ALL is not available for the set operator INTERSECT.

Example

The following CDS view entity combines the result sets of two SELECT statements using INTERSECT. It returns only those rows returned by both queries.

The program DEMO_CDS_INTERSECT uses SELECT to access the view and it displays the result set.

PERFORM Short Reference CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.

Length: 41160 Date: 20240512 Time: 063544 sap01-206 ( 288 ms )

Ansicht Dokumentation

ABENCDS_INTERSECT_V2 - CDS INTERSECT V2

- CDS View Entity, SELECT, INTERSECT

Effect

Rules for the Elements of a View Using INTERSECT

Amounts and Quantities in INTERSECT Views

Associations in Views Using INTERSECT

Nesting of INTERSECT Branches

Notes

Example

Ansicht
Dokumentation