2025 Oct 08 9:07 AM - edited 2025 Oct 08 11:21 AM
Hi Experts,
We have the non-released CDS I_RERENTALOBJECT which we need to use for our custom development.
MohanKumar5_0-1759910435397.png
We can create custom rapper on top of standard CDS as per the suggestion based on SAP documentation
Extend SAP S_4HANA in the cloud and on premise with ABAP based extensions
Page no- 42
MohanKumar5_1-1759910435400.png
After we create the Custom CDS, if we are not set the API state to released
Package – Default ABAP Language version – standard ABAP
Base CDS View
MohanKumar5_2-1759910435407.png
We are using the ATC check Variant ABAP_CLOUD_READINESS are getting the error
MohanKumar5_3-1759910435416.png
On top of the base CDS ZI_RERENTALOBJECT_POC which is API state is not set to release.
MohanKumar5_4-1759910435422.png
We are creating the new CDS on top of ZI_RERENTALOBJECT_POC under the package where the default ABAP Language Version to ABAP for Cloud Development.
When are executing with the ATC variant ABAP_CLOUD_READINESS there are no error found
MohanKumar5_5-1759910435429.png
Query is in case if the custom CDS or custom objects which are not released how we can be able to raise the Error in ATC check. We have created the custom ATC variant below are the screen shots.
Is there any options to capture error for above use case via ATC check with the screen shots are much appreciated
MohanKumar5_6-1759910435434.png
We are getting the same result
MohanKumar5_7-1759910435441.png
2025 Oct 09 2:46 PM
Hi @MohanKumar5 ,
ABAP_CLOUD_READINESS ATC variant and clean core checks based ATC variant support two different ATC checks procedure: the first one checks ABAP Cloud readiness and the second one clean core readiness. You need to decide which check procedure you want to apply and don't mix the checks as on your screenshot.
Now to your case. Your not-released custom wrapper CDS view ZI_RERENTALOBJECT_POC is in the package with "Standard ABAP" language version. If then your ZI_RERENTALOBJECT_POC_CLD CDS view is located in the ABAP package with ABAP for Cloud Development language version and using the ZI_RERENTALOBJECT_POC, then you should get the syntax error, because it is using the not-released CDS view. If it does not happen, then please open a ticket to SAP to process this issue. If your ZI_RERENTALOBJECT_POC_CLD CDS view is located in the ABAP package with "Standard ABAP" language version and is using the ZI_RERENTALOBJECT_POC, you will not get any ATC error with clean core ATC checks.
Kind Regards,
Olga.
2025 Oct 09 2:46 PM
Hi @MohanKumar5 ,
ABAP_CLOUD_READINESS ATC variant and clean core checks based ATC variant support two different ATC checks procedure: the first one checks ABAP Cloud readiness and the second one clean core readiness. You need to decide which check procedure you want to apply and don't mix the checks as on your screenshot.
Now to your case. Your not-released custom wrapper CDS view ZI_RERENTALOBJECT_POC is in the package with "Standard ABAP" language version. If then your ZI_RERENTALOBJECT_POC_CLD CDS view is located in the ABAP package with ABAP for Cloud Development language version and using the ZI_RERENTALOBJECT_POC, then you should get the syntax error, because it is using the not-released CDS view. If it does not happen, then please open a ticket to SAP to process this issue. If your ZI_RERENTALOBJECT_POC_CLD CDS view is located in the ABAP package with "Standard ABAP" language version and is using the ZI_RERENTALOBJECT_POC, you will not get any ATC error with clean core ATC checks.
Kind Regards,
Olga.
2025 Oct 10 10:54 AM
Hi Olga,
Thanks for your feedback,
CDS Views ZI_RERENTALOBJECT_POC_CLD CDS is under the ABAP for Cloud development package, i will raise the ticket with SAP for the above issues.