Symptom
A custom ABAP namespace has been registered with SAP for partner use, however the namespace and its objects do not appear in the ABAP Cloudification Repository Viewer.
Environment
SAP S/4HANA
Cause
The Cloudification Repository is not automatically populated based on SAP namespace registration. For a partner namespace to appear in the viewer, the partner must contribute the API classification JSON file directly to the public repository. This is documented in the "Partner Extensions" and "Contributing" sections of the repository README at https://github.com/SAP/abap-atc-cr-cv-s4hc.
Resolution
To make a registered partner namespace visible in the Cloudification Repository Viewer, the partner must generate and contribute the API classification JSON file, following below steps:
- Implement SAP Note 3630552 - Classic API Support in ATC Check "Usage of APIs" for Partners
- Run report SYCM_API_CLASSIFICATION_MANAGR to generate the JSON file. It must contain only objects belonging to the partner namespace and use the naming format objectClassifications_<NAMESPACE>.json.
- Submit the file via a pull request to the src/patrner folder of the public repository: https://github.com/SAP/abap-atc-cr-cv-s4hc/tree/main/src/partner.
See Also
- SAP Note 3630552 - Classic API Support in ATC Check "Usage of APIs" for Partners
- ABAP Cloudification Repository: https://github.com/SAP/abap-atc-cr-cv-s4hc
Keywords
cloudification repository, crv, usage of apis, partner namespace , KBA , BC-DWB-CEX , Customer Extensions , Problem
SAP Knowledge Base Article - Public