
Welcome to the blog series on integrating SAP Cloud for Customer with SAP ERP and SAP CRM. This series walks you through the integration guides; highlighting key considerations as well as where you should go to ensure you have all the information you need for the integration.
This blog focuses on configuration required in SAP ERP for the integration. Before reading this blog you should read the blog on getting ready, which walks through the guides you need and setup that should happen prior to the ERP configuration.
There is a new SAP Cloud for Customer release every 3 months. Each release will normally include new integration scenarios. This blog is not comprehensive of all scenarios and required configuration. Before doing the configuration, always ensure you have the latest version of the integration guide from Service Marketplace. The integration guide is kept updated with the most recent scenarios and required configuration.
Additionally, this demonstration walks through the key ERP configuration steps.
The ERP configuration includes:
1. Web Service Configuration
The integration with SAP ERP includes both IDOCs and Web Services. To do the Web Service configuration you need to use transaction codes SICF, SRTIDOC, and SOAMANAGER. In SICF you need to ensure the IDOC service is enabled. This might already be enabled on your ERP system. SRTIDOC ensures the IDOC service is registered.
Use transaction code SOAMANAGER to configure Web Services provided for the integration. These Web Services include:
2. Number Intervals
Number range is a standard ERP configuration. This number range will be used when contacts/accounts created in the Cloud are integrated with SAP ERP.
3. User
A service user is recommended for the integration work on ERP. The Add-On includes recommended roles for the user.
4. Program for IDOC configuration
The integration guide describes report RCOD_CREATE_CONNECTIVITY_MW that is used to create the IDOC settings including distribution model, partner profiles, etc. Once the report has done the configuration, the only remaining step is to schedule the IDOC reports such as RBDMIDOC.
5. Application configuration
A BC Set is provided that does most of the application configuration. This includes sales document types, output processing, etc. These settings are required to provide follow-up details on sales orders/quotes created in ERP back to SAP Cloud for Customer. In additional to the BC Set, there is one Output Control that must be configured. It is called “requirement routine” and ensures we have a Cloud for Customer opportunity referenced when we send back the confirmation. The configuration for this is detailed in the ERP configuration section of the integration guide. Activation of the BC set is optional but highly recommended!
As you can see, the major steps for the ERP configuration include the Web Service configuration; number ranges, user, and then programs and a BC set that do the majority of the technical and application configuration.
Happy integrating!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |