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 required information for the integration.
This blog focuses on configuration required in SAP ERP for the integration. Other blogs in this series include:
Get ready to integrate
ERP configuration
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 cloud configuration.
There is a new SAP Cloud for Customer (C4C) release every 3 months. Each release will normallyinclude 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. In addition to the integration configuration guides on Service Marketplace, you also might want to review the C4C admin guide on help.sap.com. If you are an integration expert new to C4C, this admin guide describes everything an administrator would need to do, including high level information on the integration.
Be sure to review this demonstration. It walks through the key Cloud configuration steps.
When integration C4C with SAP ERP, the cloud configuration includes:
- Scoping for integration
- Create the communication systems
- Perform Code-List Mapping
- Create the communication arrangements
- Create ID mapping (employees and product categories)
- Number range for master data objects
- Maintain document types for quotes/orders
Let’s look at each one.
1. Scoping for Integration
C4C is delivered with many functions and capabilities. Scoping is used to activate which features you want to use. Integration with ERP has its own scoping. The scoping is done in the business configuration area and you will select the ERP scoping. The video walks through the exact items you need to pick.
2. Create the communication systems
Creating a communication system is analogous to creating a SM59 destination in ECC. You have to say who will we communicate with. If you are using HCI, then you will enter your HCI host name. If you are using PI, then you will enter the reverse proxy (e.g. SAP Web Dispatcher). The name you provide can be the ERP name since it represents ERP, but you need to enter the next physical connection for C4C.
3. Perform code list mapping
Code list mapping map values on-premise to values in Cloud for customer. The following table shows the common code-list mappings for ERP. The “Local Data Type” is the field in Cloud for Customer. The “Fine Tuning Location” is how you find the field in C4C. Notice that in some cases the mapping is not required since the standard values are equal. The next is the customizing location in ERP for the customizing object, and finally you see the table name used in ERP for this customizing object. For details on all code list mapping, use the integration configuration guides on SMP. This complete spreadsheet is in the appendix of the ERP integration configuration guides on SMP.
Local Data Type | Fine Tuning Location in Cloud for Customer | Customizing Location in ERP | Table in ERP |
AcademicTitleCode | General Business Partners -> Maintain Academic Title | Cross-Application Components -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Persons -> Name Components -> Maintain Academic Titles | TSAD2 |
AddressUsageCode | Specific Mapping not
required: Choose "Local and Remote Codes are equal" |
BusinessPartnerFunctionTypeCode | Contacts -> Functions | Sales and Distribution -> Master Data -> Business Partners -> Contact Person -> Define Contact Person Functions | TPFK |
BusinessPartnerFunctionalAreaCode | Contacts -> Departments | Sales and Distribution -> Master Data -> Business Partners -> Contact Person -> Define Standard Departments | TSAB |
BusinessPartnerRelationshipCategoryCode | Specific Mapping not
required: Choose "Local and Remote Codes are equal" |
BusinessPartnerRoleCode | <not available> | Logistics - General -> Business Partner -> Customers -> Control -> Define Account Groups and Field Selection for Customers | T077D |
BusinessTransactionDocumentItemProcessingTypeCode | <not available> | Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Define Item Categories | TVAP |
BusinessTransactionDocumentProcessingTypeCode | Opportunities -> Maintain Document Types | Sales and Distribution -> Sales -> Sales Documents -> Sales Document Header -> Define Sales Document Types | TVAK |
CancellationReasonCode | Reasons for Rejection | Sales and Distribution -> Sales -> Sales Documents -> Sales Document Item -> Define Reasons For Rejection | TVAG |
CashDiscountTermsCode | Accounts ® Payment terms | Sales and Distribution -> Master Data -> Business Partners -> Customers -> Billing Document -> Define Terms
Of Payment | T052 |
CommunicationMediumTypeCode | <not available> | | TSAC |
CompanyLegalFormCode | General Business Partners ->Maintain Legal Form | Sales and Distribution -> Master Data -> Business Partners -> Customers -> Marketing -> Define Legal Statuses | TVGF |
CustomerABCClassificationCode | Accounts -> Maintain ABC Classification | Sales and Distribution -> Master Data -> Business Partners -> Customers -> Marketing -> Define Customer Classifications | TKUKL |
4. Create Communication Arrangements
Communication arrangements build on the communication system by providing exactly which objects/scenarios are being used for the integration.
5. Create ID mapping
While the master data integration to ERP includes accounts, products, sales organizations, there is still some master data that
must be loaded via the migration workbench. One examples includes emloyees. Once this data is loaded, then you need to create the ID mapping where you map the employees.
6. Number range for master data objects
Just as there are number ranges for ECC, there are also number ranges that need to be configured in C4C. The details are in the video.
7. Maintain document types for quotes/orders
The final step in the video shows the processing types that must be configured in the cloud for the sales quotes/orders.
That's it for the cloud configuration!
Please check out the other blogs in our C4C integration blog series at http://scn.sap.com/community/cloud-for-customer. The blog series includes the following blogs:
General
SAP Cloud for Customer Prepackaged Integration Content
How-To Guides and E-learning
Using HCI or PI
ERP Integration
Get ready to integrate
ERP configuration
Cloud configuration (this blog)
Coming soon: PI Configuration, HCI Configuration
CRM Integration (coming soon)
