SAP ABAP CODE REVIEW CHECKLIST BAPI

SAP ABAP CODE REVIEW CHECKLIST BAPI

1. Check List

A. When using SAP predefined BAPIs, check status of BAPI Release for use or Obsolete.

B. Option of simulation, test run or check BAPIs should be used when required.

C. COMMIT WORK command must not be executed by the BAPI itself; it must be executed by the calling program. If the BAPI is updating db tables then BAPI_TRANSACTION_COMMIT & BAPI_TRANSACTION_ROLLBACK should be used

D. BAPIs should not return any screen dialogs from the SAP server system to the calling application.

E. There should be no exception or messages passed through the bapi using statements like a. Message b. Raise exception, etc

F. Use return parameter to pass all information or messages to the other system. The various structures for return parameter are a) Bapireturn b) Bapiret1 c) Bapiret2

G. Following Statements should not be included in bapi a. Call transaction b. Call screen c. Submit report, etc.

H. BAPIs can be further enhanced to suit customer requirements in the following 2 ways : a. Customer Enhancement to the BAP as provided by a BADI or SMOD. b. Customer modification by creating a subtype of the underlying Business Object which then becomes the supertype

I. Extended Check done?

j. Code Inspector check done?