Creating Development Objects and Documentation
Purpose
After you have defined your BAPI, identified the relevant programming objects and given them names, you can create the programming objects in the R/3 System.
Process Flow
Task |
Tools / Further Information |
|
For SAP internal development, you have to complete a business object request form in the BAPI Explorer. For general information about creating business object types refer to the documentation on
SAP Business Workflow. |
|
For further information see the ABAP Dictionary. | |
|
For further information see the
BC - ABAP Workbench: Tools | |
Documentation on the BAPI and its parameters is essential because it is very difficult to use a BAPI that has not been well documented. |
For internal BAPI documentation you must follow the current BAPI documentation guidelines which you can get from your contact person in the BAPI Development group. See the general Documentation Guidelines. |
|
For details on how to do this see
Converting Between Internal and External Data Formats. | |
Note that the COMMIT WORK command must not be used in the function module. |
For further information see General Programming Guidelines for BAPIsand
Programming Standardized BAPIsFor an example of a function module that implements a BAPI see
BAPI Interface and Function Module. |
Finally, make sure that the parameters and parameter types of the method in the BOR match the parameters of the underlying function module in the Function Builder. |
For more information see
Defining Methods in the BOR Using the BOR/BAPI Wizard.
For an example of a function module that implements a BAPI see
BAPI Interface and Function Module. |