{"ref":"content:recommendations-for-wrapper-interface-design","page":"/content/recommendations-for-wrapper-interface-design","json":"/content/recommendations-for-wrapper-interface-design.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"recommendations-for-wrapper-interface-design","title":"Recommendations for Wrapper Interface Design","url":"https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/recommendations-for-wrapper-interface-design/ba-p/14425678","content_type":"blog","explains":["capability:abap-cloud-readiness"],"summary":"Walks through designing a wrapper interface that encapsulates a classic BAPI (BAPI_USER_GET_DETAIL) behind a C1-released interface, so the code released for ABAP Cloud stays limited to types and structures ABAP Cloud can actually access. Covers when a non-released SAP structure can still be referenced safely, when it cannot, and how the API_CONSISTENCY and API_COMPATIBILITY ATC checks catch the difference before an upgrade breaks it.","short":"Wrapping a classic BAPI behind a C1-released interface for ABAP Cloud","author":"kaidehmann","published":"2026-06-25","provenance":{"discovered_via":[{"source":"source:sap-community","channel":"abap-development-tag"}],"first_seen":"2026-09-13"},"drafted_with_ai":true,"published_on":"source:sap-community"},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"unknown","evidence":"not crawled"},{"label":"Age","tier":"good","evidence":"published 4 months ago"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"good","evidence":"no recorded change after 2026-06-25"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":3528,"unit":"views"},{"value":1,"unit":"comments"},{"value":12,"unit":"likes"}]},"signals":{"views":3528,"likes":12,"comments":1,"metrics_at":"2026-10-25"},"series":null,"edges":{"authors":[]}}