During SAP S/4HANA Cloud Public Edition implementations, partners occasionally encounter a scenario where a required Public API simply does not exist in the standard API catalogue. This gap can become a project blocker — particularly when third-party integrations or BTP side-by-side extensions depend on data objects that have no released API endpoint.
This blog post consolidates the recommended guidance for SAP partners on how to handle such situations. It covers the permanent resolution path via the SAP Customer Influence Programme (CIP), interim workaround options using Custom APIs, current known limitations, and the product improvements on SAP's roadmap.
Whether you are an implementation consultant, solution architect, or partner enablement lead, this guide provides the end-to-end picture.
Source link