Implementing a custom BAPI

To implement the second scenario, which is described in Extending the SAP call out to a synchronous system sample, you require information from your SAP administrator or developer to access an external system from SAP.

The steps for creating your adapter and message set are the same as when you implement a predefined BAPI, which is described in Building the SAP call out to a synchronous system sample. The equivalent of the shared variable in the sample (for example, IMS or DB2) requires nodes that are specific to your external system, which have their own samples (for example, a Database node for DB2 or an IMSRequest node for IMS).

Information that is required to build the adapter and message set:

  1. SAP system information: Host name, System number, Client number, User name, and Password.
  2. The custom BAPI names.
  3. Which parameters of the BAPI are import parameters (parameters that are passed into the BAPI, and therefore, into an SAPInput node) and which are export parameters (return parameters, therefore, the parameters that must be put into the message tree for the SAPReply node). This information is not discovered by the Adapter Connection wizard.
  4. Information on message codes for errors, warnings, and informational messages that must be sent back in the return object.

Additionally, you must give the SAP administrator and SAP developer the RFC program identifier that you are using.

Back to Extending the sample

Back to sample home