- 24 Sep 2024
- 3 Minutes to read
- Print
- DarkLight
Enable SAP ERP integration
- Updated on 24 Sep 2024
- 3 Minutes to read
- Print
- DarkLight
To enable SAP ERP integration, follow these steps:
- Install SAP Cloud Connector.
- Configure mutual authentication between SAP Cloud Connector and back-end system.
- Configure access control.
- Connect your web application to an on-premise system.
- Set up SAP Business Technology Platform (SAP BTP).
- Create a remote function call (RFC) destination.
- Configure BAPIs.
- Configure an ERP RFC user for SAP ECC integration.
Install SAP Cloud Connector
Download SAP Cloud Connector from the SAP Development Tools for Eclipse page.
For installation details, read the Installation documentation.
Configure authentication
Configure mutual authentication between SAP Cloud Connector and your back-end system.
For configuration details, read:
Configure access control
To allow your web application to access a back-end system on the intranet, indicate this system in the SAP Cloud Connector.
For configuration details, read:
Connect your web application to an on-premise system
To connect your web application to an on-premise system, read:
- Consume Backend Systems (Java Web or Java EE 6 Web Profile)
- Invoke ABAP Function Modules in On-Premise ABAP Systems
Set up SAP BTP
After installing SAP Cloud Connector, register the SAP Business Technology Platform (SAP BTP) account in it. SAP Cloud Connector creates a tunnel connection with the registered SAP BTP account as shown on the image below:
Create a remote function call destination
The next step is to create a remote function call (RFC) destination. You can create an RFC destination at the account level or application level. All account-level destinations are accessible to all applications in the account, but not conversely. We recommend creating application-level destinations to enable applications to connect to QA or PROD ERP systems as needed.
The image below shows destination configuration in SAP Cloud Connector:
Configure BAPIs
The SAP ERP integration is facilitated by the Business Application Programming Interfaces (BAPIs) that enable access to SAP functions. To enable the integration, add BAPIs to the allowlist in SAP Cloud Connector.
The following table shows the BAPIs you need to add to the allowlist depending on the integration purposes.
Integration purpose | BAPIs |
---|---|
Order creation and simulation |
|
Data synchronization |
|
Product synchronization |
|
Account synchronization |
|
Custom table synchronization |
|
Creation of materials, bills of material, and routings |
|
Solution Sales Configuration (SSC) |
|
Equipment synchronization |
|
Configure an ERP RFC user for SAP ECC integration
To integrate SAP ERP Central Component (SAP ECC) through Remote Function Calls (RFC), use a dedicated ERP user with permissions to execute RFC modules.
Create a user
Create a user using Transaction SU01. Assign the necessary permissions to this user.
Create a role
Create a role, such as Z_ISS_RFC, using Transaction PFCG. Use the following image as an example:
Depending on the document types used, you may need to patch BAPI SD_SALES_DOCU_MAINTAIN
in current SAP releases to enable the transfer of manually entered pricing conditions. For details, read Note 177 on the SAP Support Portal page.
For some installed add-ons, you may also need to patch /SLCC/EXTRACT_DATA
or /SLCE/EXTRACT_DATA
.
This functionality doesn't work by default in the following cases:
- In SAP_AP beginning with the 23 release.
- If you installed the support package SAPKNA7032. For details, read SAP Note 1995783 on the SAP Support Portal page.
Configure authorization data (without template)
Manually add needed authorization objects.
- For SSC product configuration:
- C_TCLA_BKA (configuration)
- C_TCLS_BER (configuration)
- C_TCLS_MNT (configuration)
- K_KEKO (variant prices)
- S_RFC (knowledge base export)
- S_TABU_DIS (knowledge base export)
- For sales order and quote creation or simulation:
- V_VBAK_AAT (sales document)
- V_VBAK_VKO (sales document)
- For replication of ERP non-configurable material master:
- M_MATE_STA (to pull material master, display C, K, V for STATM)
To add authorization objects, select Edit > Insert authorizations > From profile > S_A.SCON.
Grant full authorization for each object or restrict authorization as needed to create and save the single role (for example company code, sales document type, division).
Edit RFC user and assign role
Edit the RFC user and assign the Z_ISS_RFC role through Transaction SU01.
To debug a specific BAPI call, switch the RFC user to the Dialog mode and add the role SAP_BC_DWB_ABAPDEVELOPER to access SE37 with the RFC user.