Integration workflow using custom BAPIs

BAPIs contain the list of attributes that can be provided by while using the BAPI. For example – fetch supplier standard SAP BAPI may have 40 attributes while the general usage across customers may-be much more like 60 attributes. So, usage of standard BAPIs will restrict the customers to use only 40 attributes.

In addition to the above there are also cases where there are complex objects like create purchase order which has multiple entities like purchase order header, purchase order line, along with some additional work like populating tax code for tax calculation, defaulting plant address and orchestrating all of that in a standard BAPI with limited attributes restricts the kind of functionality that can be provided to the customer.

In view of the above, this integration was built with Custom BAPIs which is a like a super set consisting of almost all the attributes (either in terms of getting the attributes or posting the transactions by populating those attribute values).

Using custom BAPIs will require some additional work on the customer side to do configure some transport files and load it on SAP Server. However, all this work will be done and provided by Bristlecone team on ServiceNow store which can be easily downloaded and leveraged by customer to do the necessary pre-requisite steps.