Get Example source ABAP code based on a different SAP table
VX_EXA_ONLY
ABAP_CDS_V1_VIEWS , Obsolete Client Handling This example demonstrates how obsolete client-independent> ABAP_CDS_V1_VIEWS > are handled.
ABAP_SOURCE_CODE ABAP_EXEC >
ABAP_DESCRIPTION The program accesses the following ABAP_CDS_V1_VIEWS >: DDLS DEMO_CDS_SPFLI_CLIENT_2 DDLS DEMO_CDS_SPFLI_CLIENT_3 They are used to demonstrate the behavior in rare cases where ABAP_CDS_V1_VIEWS with the obsolete notation ClientDependent:false>> are made into client-independent views even though they contain client-dependent data sources:
DEMO_CDS_SPFLI_CLIENT_2> is a client-independent CDS view in which the client column is not specified in the SELECT> list.
DEMO_CDS_SPFLI_CLIENT_3> is a client-independent CDS view in which the client column is specified in the SELECT> list. RTTI is used to read the components of the associated data types:
The structure of the client-independent CDS entity without client column in the SELECT> list does not have a client column.
The ABAP_CDS_MNG_VIEW of the client-independent CDS view without client column in the SELECT> list has a client column.
The structure of the client-independent CDS entity without client column in the SELECT> list does not have a client column.
The ABAP_CDS_MNG_VIEW of the client-independent CDS view with client column in the SELECT> list has a client column, which makes it client-dependent. The statement SELECT> is used to make the following accesses:
Regular access to a client-independent CDS entity without client column in the SELECT> list. The data is read from all clients. No conditions can be specified for the client. The result set does not have a client column.
Regular access to a ABAP_CDS_MNG_VIEW of the client-independent CDS entity without client column in the SELECT > list. The data is read from all clients. No conditions can be specified for the client. The result set does not have a client column.
Regular access to a client-independent CDS entity with client column in the SELECT> list. The data of the client specified in the WHERE> condition is read. It is not possible to specify the obsolete addition CLIENT SPECIFIED >> here. The result set has a client column.