Have you got SAP Cloud for Customer (C4C) in your landscape? Are you taking advantage of the standard integration offered by SAP? Having led the technical integration across many SAP C4C projects, we’ve found a key requirement on sales and service improvement programmes is often to integrate business processes between C4C and existing on-premise SAP ERP and/or SAP CRM systems.
Fortunately for us, integrating these systems has been made a lot simpler by using standard integration content provided by SAP for both key master data and transaction data.
This standard integration content is provided for both of SAP’s middleware platforms - SAP Process Orchestration (PO) and SAP HANA Cloud Integration (HCI). Providing the integration content for both platforms is of great benefit, because if you have already made an investment in PO, you can import the add-on, which is available to download from the SAP Service Marketplace.
On the other hand, if you don’t already have PO and have a SAP-centric landscape, then we suggest using HCI. HCI is SAP’s new cloud-based middleware platform, and it brings multiple benefits - including the fact that no time or cost is required for hardware and installation. SAP provides you with the HCI tenant details (Test and Production) from which you can download the standard integration content. Using standard integration content to integrate C4C with ERP/CRM of course provides a number of advantages, which are outlined below.
- Less time spent on development:
The standard integration content does the hard work for you and includes all the message types, interfaces, mappings, and adapters for a particular scenario. There is only a small amount of configuration needed to configure the adapter’s specific connection details. However, you still have to allow your landscape to support this integration, by opening up the necessary firewalls and configuring reverse proxies and proxies where necessary.
- Easy to extend standard integration content:
If you have added additional fields in C4C, it is easy to export the updated WSDL file from your C4C communication arrangement and import this into PO or your HCI Integration Flow (iFlow). If you have also extended a standard IDOC in ERP/CRM, it is simple to import the new IDOC into PO or import the extended IDOC WSDL into your HCI iFlow and update your message mappings accordingly. This avoids having to rebuild your interfaces from scratch.
- Standard integrations can be used as templates:
This can greatly reduce development time when you want to integrate a third-party system in your enterprise landscape with C4C (e.g. reporting tools, HR tools, and marketing tools).
- Content is updated in line with each release of C4C:
SAP provides new releases of C4C every three months, containing additional features, and bug fixes. In line with this, SAP also provides new releases for their standard integration content - for example, the 1511 release of C4C also saw the release of 1511 integration content for both PO and HCI. That said, if your integration content is on an older release than the current release of C4C, it’s not a problem - the integration will still work.
The above information focuses on the standard integration content between C4C and ERP/CRM, but SAP also provides standard integration content for a number of other areas as well as guides that walk you through the integration steps. New content is being released all the time and this is great for developers and consultants as it reduces workload and shortens project timelines. We hope to see more and more standard integration content being released, to speed up delivery of key SAP-to-SAP integrations.