Custom code can use standard SAP code and SAP objects. Some of these objects might technically exist, but are in an unreleased status. This might mean SAP will not give support on them, or might remove them in a future upgrade.
Also when you want to move to the BTP ABAP cloud, you cannot use the unreleased code.
Questions that will be answered in this blog are:
- How can I scan my custom code for use of unreleased standard SAP objects?
Tool preparation
First install the program SYCM_UPLOAD_RELEASED_OBJECTS by applying OSS notes 2989803 – Check Usage of Released Objects with the Latest List of Released Objects and 3143521 – Check for Released Objects: Introduce Finding “Usage of API that will not be released”.
And download the attached file in the same note in the attachments section;
Now run program SYCM_UPLOAD_RELEASED_OBJECTS and upload the file to a new SCI variant:
After the upload, you will find this new variant SAP_CP_READINESS_REMOTE in SCI:
ATC run for unreleased code
Now you can start new ATC run with this newly created variant SAP_CP_READINESS_REMOTE:
Run the variant for you custom code (can take few hours).
Result can be shown as special whitelist item:
