SAP BAPIs
BAPIs are SAP’s stable, released, remote-enabled interfaces to business objects, the reference set of safe operations for reading and changing SAP data. This page explains finding and using them.
A BAPI such as BAPI_SALESORDER_CREATEFROMDAT2 is a released, remote-enabled function module that performs one operation on a business object while enforcing SAP's business logic, stable across releases. Browse them in the BAPI Explorer, transaction BAPI, read the function module in SE37, always check the RETURN structure, and call BAPI_TRANSACTION_COMMIT. They are the safe alternative to direct table writes.
- Watch out: a BAPI does not commit by itself, so the caller has to issue the commit.
What it is
A BAPI (e.g. BAPI_SALESORDER_CREATEFROMDAT2) is a released function module representing an operation on a business object, enforcing SAP’s business logic. BAPIs are documented, stable across releases and callable remotely, the safe programmatic API for classic integration.
How to find/use it
- Use the BAPI Explorer (transaction BAPI) to browse by business object.
- View the underlying function module in SE37.
- Check parameters and the RETURN structure.
- Remember: check RETURN and call BAPI_TRANSACTION_COMMIT.
Why it matters
BAPIs are the reference catalogue of safe, supported operations on SAP objects, essential for integration and data loads. Knowing the right BAPI (and its commit/return rules) avoids risky direct table writes.
Common pitfalls
- Guessing instead of using the reference tools.
- Editing/using without understanding the object.
- Relying on memory for details you can look up.