2025 Apr 14 1:33 PM - edited 2025 Apr 23 6:31 AM
(UPDATE - see below)
To access certain data, we have implemented a CDS Table Function in a Standard ABAP/Tier 2 package, which we would then need to be consumed by a Tier 1/Cloud for ABAP CDS View.
(We are following the recommendation here: Creating Tier 2 Cloud APIs).
However, in ADT the options to add a C1 or C2 release contract are greyed out / unavailable for the CDS Table Function:
Also, when trying to add a C0 release contract, it gives this message: "C0 release is not supported for entity type F.":
Trying to consume the CDS Table Function in a Tier 1 CDS View is impossible, and also results in an error (presumably until we can add a C1 release contract).
UPDATE 23.04.2025:
We created a case for this issue with SAP, referencing the above documentation. SAP came back with the following reply:
Dear customer, As Creating Tier 2 Cloud APIs says: Currently, the object types recommended by SAP to be wrapped are as follows:
Currently SAP does not support adding release contracts to CDS Table Functions which means they cannot be exposed as public APIs or consumed by Tier 1 CDS Views directly |
We pointed out to them that the documentation in fact goes on to say:
For mitigation scenarios, SAP recommends the following:
For the first option, a CDS view (which accesses the table function) would serve as the released object for tier 1 usage and for the latter option, a class (accessing the method) would suffice. |
What could potentially happen now, is that SAP changes the documentation to cover such a shortcoming. I hope not, because one of our project requirements depends on being able to use this functionality.
I've made a screenshot of the current doc:
Request clarification before answering.
| User | Count |
|---|---|
| 11 | |
| 6 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.