Use
Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
Features
The following standardized BAPIs are provided:
Reading instances of SAP business objects
Programming GetList() BAPIs.
Programming GetDetail() BAPIs.
BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Programming Create() BAPIs.
Programming Change() BAPIs.
Programming Delete() BAPIs.
Programming Cancel() BAPIs.
Programming Methods for Sub-Objects.
BAPIs for Mass Data Processing
The BAPIs listed above for creating and changing data can also be used for mass processing. For more information see
BAPIs for Mass Data TransferBAPIs for Replicating Business Object Instances
Programming Replicate()/SaveReplica() BAPIs.
Other Less Used Standardized BAPIs
Programming GetStatus() BAPIs
Programming ExistenceCheck() BAPIs