Principles
The quality of your BAPI documentation depends on the following principle:
The documentation must be in sufficient detail so that an external developer familiar with the business background but not with the SAP System, can use the BAPI.
Features
The documentation for the BAPI covers four areas:
1. |
The SAP business object type documentation. | |
2. |
The method documentation should answer the following questions: | |
|
What is the business function of the BAPI and what is it used for? | |
What do the BAPI functions actually do? | ||
Are there any important limitations, that is, are there functions that this BAPI cannot perform? | ||
What must you pay particular attention to with this BAPI? (e.g. authorization checks) | ||
Are there any Customizing dependencies? | ||
What dependencies are there between this BAPI and other BAPIs, and between individual method parameters? | ||
Is it a BAPI with buffering? If it is, the BAPI must be explicitly identified as such. | ||
Does the BAPI contain a COMMIT WORK command? If it does, it must be documented. | ||
3. |
The BAPI parameter documentation answers the following questions: | |
|
What is the parameter used for? | |
Which fields of a parameter must be filled, that is, what are the mandatory fields? | ||
What are the dependencies between fields? | ||
Are there any fixed values and what do they do? | ||
What are the default values of the parameter? | ||
Does the documentation of the return parameter comply with the guidelines and does it contain all the relevant error messages? | ||
If there is a termination, is a database rollback executed as an exception within the BAPI? If it is, you must describe this process in the documentation for the return parameter. | ||
Are all the available BAPI table extensions listed in the documentation on the extension parameters (ExtensionIn, ExtensionOut)? | ||
4. |
Data element documentation underlying the fields in the BAPI parameters |
Finally, you must also make sure that the documentation about the function modules and parameters has been saved by the documentation developer as an active version so that it appears in the translator's worklist.
Refer to