Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
rasjoshi
Active Contributor

Hi SAPiense,

SAP customers have made large investments in on-premise Sales and Distribution application capabilities. The SAP SD module continues to be viable in the corporate system landscape, but many customers want to enable a fresh and intuitive user experience, increased functionality, and faster delivery of new functionality. The hybrid integration scenario is a great enabler of application delivery via the cloud, because it allows the customer to preserve the investment already made in the on-premise SAP SD module. By the utilization of iFlow solution content delivered by SAP PI, a bridge between the on-premise SAP SD module and the SAP Cloud for Customer system is established, thus allowing the customer to take advantage of the strengths of both.

This document details the steps required to enable communication between an SAP Cloud for Customer(C4C) and the on-premise SAP ECC system, using SAP PI as the on-premise middleware layer.

Message Flow -

1. Pre-requisites –

System

Task

SAP ERP

>= ERP 6.0 EHP0 SP 15(SAP_APPL);
SAP BASIS 7.0 SP 18 (SAP_BASIS)

Install C4C add-on CODERINT 600 (COD_ERP_INT 6.00)

SAP PI

>= SAP PI 7.11

          Note - SAP has delivered standard contents for C4C integration which can be consumed via SAP Cloud Cust ERP Integr 2.0 SWC.

2. Background Configuration in ERP System

     a. Create Partner Profile WE20

          

     b. Create Port WE21

           

     c. RFC Destination to point PI System –

For Dual Stack, we need to create Type 3 RFC Destination –

For Single stack, we need to create Type T RFC Destination –

3. Background Configuration in SAP PI System

     a. Create Technical and Business System in SLD for ECC system

     b. RFC Destination to point to ECC System -

            

For single stack create it in NWA (http://<HOST>:<PORT>/nwa)

     c. Create port in IDX1 for type 3 RFC

                         


    d. Resource Adapter (InboundRA) Configuration for IDOC_AAE (http://<HOST>:<PORT>/nwa --> InboundRA)

Provide the below properties –

     e. Receiver Communication Channel -

                       

             


4. Configuration in SAP C4C System –


     a. Login to SAP C4C system and select Business configuration to activate SAP ERP Integration in Scoping

                      

               Click on All Projects, Edit Project Scope and click Next

                      

              Under Communication and Information Exchange à Integration with External Application and Solutions, select Integration with SAP ERP (and others that are necessary for particular project)

                           

Click Next and select the following scenarios:

  • Do you want to replicate accounts and contacts from your cloud solution to your SAP ERP solution?
  • Do you want to replicate accounts and contacts from your SAP ERP application to your cloud solution?
  • Do you use your SAP ERP system to calculate prices for opportunity items in your cloud solution?

     b. Setup Communication System


We need to create a communication system with details of PI host and business name of ECC system. Path --> Administrator tab --> Communication Systems tab and Create a new communication system.

                      

                         

 

          Enter the ERP details and then activate. Save and close.

                          

                        Once the communication system is active, we need to create a communication arrangement as per the requirements of the objects.

    c. Communication Arrangement Configuration

          Login to SAP C4C system and Select Administrator --> Communication Agreement


                

                         Fill all the required details and click next -

                   

               Select the appropriate communication agreement and click on next -

             

              Provide the credentials -

            

          We can provide the password and download the certificate after clicking the Edit Credentials Button

                 

5. Testing -


For testing purpose, we put the file in AL11 of PI system with dummy values.

SAP C4C Monitoring -

           

As we can see from the above screen shot PI was able to successfully ping the SAP C4C web service.

Important check points -

1. Make sure all the required objects certificates and root certificates are deployed on PI server

2. Take the necessary action with the help of networking team in case of firewall

3. After below two steps are been taken care, ping the communication channel to check the status in connectivity between PI and C4C

Thanks & Regards,

Rashmi Joshi

8 Comments
Labels in this area