BAPI Overview
SAP ERP integration makes use of several BAPIs from the ERP system. These need to be whitelisted in the SAP Cloud Connector (SCC). The list of such BAPI's along with their needs are as follows:
|
BAPI Name |
Order Creation/ Simulation |
Data Sync |
Product Sync |
Account Sync |
Custom Table Sync |
Material/BOM/ |
SSC |
Equipment Sync |
|---|---|---|---|---|---|---|---|---|
|
BAPI_INQUIRY_CREATEFROMDATA2 |
X |
|
|
|||||
|
BAPI_QUOTATION_CREATEFROMDATA2 |
X |
|
|
|||||
|
BAPI_SALESORDER_CREATEFROMDAT2 |
X |
|
|
|||||
|
BAPI_SALESORDER_SIMULATE |
X |
|
|
|||||
|
COD_SALESORDER_SIMULATE |
X |
|
|
|||||
|
BAPI_TRANSACTION_COMMIT |
X |
|
X |
|
||||
|
BAPI_MATERIAL_AVAILABILITY |
|
|
||||||
|
RFC_READ_TABLE |
X |
|
X |
|
||||
|
BAPI_CHARACT_GETDETAIL |
X |
X |
|
|
||||
|
BAPI_CLASS_READ |
X |
X |
|
|
||||
|
BAPI_MATERIAL_GETALL |
X |
|
|
|||||
|
BAPI_MATERIAL_GET_PRODUCTHIER |
X |
|
|
|||||
|
CLAF_CLASSIFICATION_OF_OBJECTS |
X |
|
|
|||||
|
COM_CFG_READ_PRODUCT_VARIANT |
X |
|
|
|||||
|
COM_CFG_READ_ALL_PROD_VARIANTS |
|
|
X |
|
|
|
|
|
|
RFC_READ_TEXT |
|
|
X |
|
|
|
|
|
|
ZBDS_GOS_CONNECTIONS_GET |
|
|
X |
|
|
|
|
X |
|
SO_DOCUMENT_READ_API1 |
|
|
X |
|
|
|
|
X |
|
COM_CFG_READ_VARCOND_DESCR |
|
|
||||||
|
EXTRACT_DATA |
|
X |
|
|||||
|
SELECT_COUNT |
|
X |
|
|||||
|
BAPI_MATERIAL_EXISTENCECHECK |
|
X |
|
|||||
|
BAPI_ROUTING_EXISTENCE_CHECK |
|
X |
|
|||||
|
BAPI_MAT_BOM_EXISTENCE_CHECK |
|
X |
|
|||||
|
BAPI_MATERIAL_SAVEDATA |
|
X |
|
|||||
|
BAPI_MATERIAL_GETINTNUMBER |
|
X |
|
|||||
|
BAPI_MATINSPCTRL_SAVEREPLICA |
|
X |
|
|||||
|
BAPI_MATERIAL_BOM_GROUP_CREATE |
|
X |
|
|||||
|
BAPI_ROUTING_CREATE |
|
X |
|
|||||
|
BAPI_CUSTOMER_GETDETAIL2 |
|
|
|
X |
|
|
|
|
|
BAPI_CUSTOMER_GETSALESAREAS |
|
|
|
X |
|
|
|
|
|
ISA_CUSTOMER_SALES_READ |
|
|
|
X |
|
|
|
|
|
ITOB_EQUIPMENT_ENHANCED_READ |
|
|
|
|
|
|
|
X |
|
CIDEON/BAPI_EQUI_BOM_READ1 |
|
|
|
|
|
|
|
X |
| RFC_METADATA_GET |
x |
x |
x |
x |
x |
x |
x |
x |
| RFC_PING |
x |
x |
x |
x |
x |
x |
x |
x |
ERP RFC User
The ERP Central Component (ECC) integration is conducted via Remote Function Calls (RFC) that are recommended to be executed by a distinct ERP user. This user needs some permissions in order to execute RFC modules.
A new user can be created using (Transaction SU01) and subsequently, the permissions should be assigned.
Create new single role e.g. ‘Z_ISS_RFC’ (Transaction PFCG)
Depending on document types used:
- BAPI SD_SALES_DOCU_MAINTAIN needs to be patched in current SAP releases to enable transfer of manually entered pricing conditions
- See SAP Note 177
- Depending on installed add-ons this could also be /SLCC/EXTRACT_DATA or /SLCE/EXTRACT_DATA
- Doesn't work by default in SAP_AP releases >=23
- Doesn't work by default if support package SAPKNA7032 is installed (SAP Note 1995783)
Change Authorization Data (without template)
Manually add Authorization Objects:
- for SSC product configuration
- C_TCLA_BKA (configuration)
- C_TCLS_BER (configuration)
- C_TCLS_MNT (configuration)
- K_KEKO (variant prices)
- S_RFC (KB export)
- S_TABU_DIS (KB export)
- for sales order/quote creation or simulation
- V_VBAK_AAT (sales doc)
- V_VBAK_VKO (sales doc)
- for replication of ERP non-configurable material master
- M_MATE_STA (to pull material master, display C, K, V for STATM)
Select Edit – Insert authorizations – from profile: S_A.SCON
Grant full authorization of each object or restrict to generate and save single role.
E.g. company code, sales doc type, division….
Edit RFC-User and ‘Z_ISS_RFC’ to Roles (SU01)
For debugging of e.g. a specific BAPI call switch RFC user to ‘Dialog’-Mode and add role SAP_BC_DWB_ABAPDEVELOPER to access SE37 with RFC user.
For changed authorizations, refer to SAP system trace to record authorization checks (ST01), cf. http://help.sap.com/saphelp_nw73ehp1/helpdata/en/92/7ac87d293a47d8a17368c9f45661f4/content.htm.