Ansicht
Dokumentation

ABENCDS_PV_PROVIDER_CONTRACT - CDS PV PROVIDER CONTRACT

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

INDEX @@TRANSACTIONAL_INTERFACE@@@@

- PROVIDER CONTRACT

... PROVIDER CONTRACT ${ TRANSACTIONAL_QUERY
                      $| TRANSACTIONAL_INTERFACE
                      $| ANALYTICAL_QUERY $} ...
  $| ${ $} ...

Alternatives:

1. ... PROVIDER CONTRACT

2. ... ${ $}

Effect

The provider contract specifies the scenario in which a CDS projection view is used. The scenario determines in which runtime a CDS projection view is executed and which features are available. It is recommended that the provider contract is always specified to ensure that the appropriate, runtime-specific syntax checks are applied.

It is also possible, but not recommended, to leave out the provider contract. Projection views without provider contract are handled similarly to transactional projection views, but there are some minor differences in the syntax checks applied.

Alternative 1

... PROVIDER CONTRACT ...

Additions

1. ... TRANSACTIONAL_QUERY

2. ... TRANSACTIONAL_INTERFACE

3. ... ANALYTICAL_QUERY

Effect

Currently, the following provider contracts are available:

• TRANSACTIONAL_QUERY

• TRANSACTIONAL_INTERFACE

• ANALYTICAL_QUERY

Child entities within a CDS composition tree inherit their parents' provider contract and it is not allowed to specify a provider contract for a child entity. As soon as a projection view contains a to-parent association or a redirection to a parent entity, a provider contract must not be set.

Note

Further provider contracts are planned to be released in the near future.

Addition 1

... TRANSACTIONAL_QUERY

Effect

Specifies a CDS projection view as transactional query. Transactional queries are intended for modelling the projection layer of a RAP business object. A transactional projection view must always be part of a business object. That means it must either be a root entity itself, or it must be part of a composition tree that contains a root entity.

The feature set focuses on specializing the RAP BO operations of the underlying business object.

The runtime for transactional queries is mainly the RAP query engine, but also the RAP transactional engine.

Example

The following CDS projection view defines the provider contract TRANSACTIONAL_QUERY.

Its child entity derives the provider contract from the parent entity. It doesn't specify an own provider contract:

Addition 2

... TRANSACTIONAL_INTERFACE

Effect

Specifies a CDS transactional interface. CDS transactional interfaces serve as stable public interface layer in a CDS data model. They are typically used in the context of the ABAP RESTful Application Programming Model to provide the basis for a RAP BO interface. CDS transactional interfaces have a restricted feature set. They only support projecting elements and associations from the projected entity. It is recommended that release contracts C1 and, optionally, also C0 are added.

Example

The following CDS transactional interface is based on the CDS view entity DEMO_CDS_PURCH_DOC_M. The composition is redirected to the CDS transactional interface of the child entity. Both parent and child entity are release for system-internal use (C1 Contract).

The following CDS transactional interface represents the child entity:

Addition 3

... ANALYTICAL_QUERY

Effect

CDS analytical projection views are intended for modelling analytical queries within a CDS data model. An analytical projection view must always be part of an analytical object and the projected entity must be an analytical cube view. The feature set is restricted to the capabilities of the runtime of the analytical engine. The runtime for analytical queries are analytical engines, such as ABAP Analytical Engine or Online Analytical Processing (OLAP).

See also: CDS projection view, Analytical Queries

Example

The following CDS projection view defines the provider contract ANALYTICAL_QUERY.

Alternative 2

... ${ $}

Effect

It is possible, but not recommended, to leave out the provider contract. The default provider contract, if no provider contract is set explicitly, is TRANSACTIONAL_QUERY. The same features are available as for transactional queries and a projection view without provider contract can be used in the same scenarios. However, there are some minor differences in the syntax checks applied. The differences are listed in topic CDS projection view, no contract.

General Data in Customer Master   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 9326 Date: 20240511 Time: 144349     sap01-206 ( 106 ms )