BAPI Wrapper Pattern (Interface, Class, Factory)
A wrapper is a custom ABAP object that encapsulates a non-released SAP function module or API, exposing its functionality through a stable, released interface that developers can safely consume. Developers use wrappers to mitigate the absence of a released SAP API — for example, wrapping the BAPI_PR_CREATE function module to enable the creation of purchase requisitions from custom business objects such as a Shopping Cart. This pattern allows a business object to integrate indirectly with core SAP functionality while maintaining upgrade stability and clean API boundaries.
Tutorials that teach this
Prerequisites
- Concept RAP (Restful ABAP Programming) Model The provided sources do not contain enough grounded information to write a reliable 2–4 sentence definition for an **undefined** concept. Please supply a valid concept name and ensure the source snippets contain substantive descriptions of that concept so the definition can be accurately grounded.
- Concept ABAP Release Contracts The concept name was not provided, so a precise definition cannot be produced. Please supply the concept name so that an accurate, source-grounded definition can be written.
- Concept Clean Core Extensibility Principles The concept name was not provided (`undefined`), and the supplied source snippets do not contain enough descriptive content to identify or define a specific SAP developer concept. Please provide a valid concept name and relevant source snippets so an accurate, grounded definition can be written.
- Concept ABAP Object-Oriented Programming The provided sources do not contain enough information to write a grounded definition for an undefined concept. The snippets reference retrieving subclasses of a given class, the [ABAP Keyword Documentation](https://help.sap.com/docs/btp/sap-business-technology-platform/1632c79dd98f4bc2a314fd5009238fce?locale=en-US&state=PRODUCTION&version=Cloud), and exploring the ABAP Repository, but no specific concept is identified or described in sufficient detail to produce an accurate, source-grounded definition.
- Concept ABAP Class Definition and Implementation The concept name is not defined in the provided sources, so a precise label cannot be confirmed. Based on the available snippets, **ADT Class Execution** is a capability that allows developers to [execute ABAP classes directly in ABAP Development Tools (ADT)](https://help.sap.com/docs/btp/sap-business-technology-platform/6f0e26492b854627ac19a9a34205a546?locale=en-US&state=PRODUCTION&version=Cloud) without additional setup steps. Separately, the XCO library provides APIs for [reading a class](https://help.sap.com/docs/btp/sap-business-technology-platform/bc23e26f236042c48171d850e82843b9?locale=en-US&state=PRODUCTION&version=Cloud) programmatically, enabling developers to inspect class definitions such as `zcl_xco_doc_cp_cs_class` at runtime.
- Concept ABAP Cloud Development The concept name was not provided (marked as "undefined"), and the supplied source snippets cover a broad range of distinct SAP topics — including ABAP data models, metric providers, programming models, Git integration, background processing, ABAP Development Tools for Eclipse, generative AI, and BAdI implementations — without a shared or identifiable single concept to define. A focused, accurate definition cannot be written without knowing which specific concept is intended. Please provide the concept name so a grounded definition can be produced.