Skip to Content
Author's profile photo Ankur Godre

Checks on QA system post Server Refresh: Validate & maintain integration with C4C

Hello Everyone,

In this blog, I want to share my experience around post server refresh activities specific to C4C integration with SAP ECC system.

This is purely a technical blog, however it may come handy to Customers/Partners/Consultants who plan to or have already integrated their SAP ECC systems to C4C aka Cloud for Customer using HCI as middleware.

In a general, SAP landscape where there is Dev -> QA -> Prod. systems connected, as part of server maintenance activities, Customers might perform server refresh activities on Productive systems. What this means essentially in a C4C – ECC integrated scenarios is that the Integrationrelated settings/configuration maintained on SAP ECC QA system would get refreshed post this activity, which would overwrite the configuration/settings on SAP QA system.

As part of best practices, following would be the key steps to restore the integration on SAP ECC QA system:


1. Check the STRUST  TCODE for SSL client standard PSE with required certificates added to the certificate list:


Step 1.png

2.Check for HTTPS parameter in RZ10 instance profile:


Step2.png

If it does not exist, add the parameter in RZ10 instance profile and restart the system (one time activity).


3. Check in SMICM port information for HTTPS service, it should be active.


4. Go to SA38 TCODE to run RCOD_CREATE_CONNECTIVITY_MW.


Step4.png


5. Give the target host iflmapg**************.intaas.us1.hana.ondemand.com and ‘S user id’ with password and select Default SSl Client standard.




Step5.png

6. Select all the relevant IDOC Message types per the original scope of integration:


Step6.png


7. Now execute this report. It will create the distribution model and partner profiles:


Step7.png


8. Check the Logon & Security tab & populate the correct S-User Id details:


Step8.png


9. Finally, do the connection test, it give a message as shown below:


Step9.png

The above steps will ensure that the Integration related configuration/settings which might get over post Production Server refresh is restored back to its its original state.


I hope this blog comes useful to all the  C4C Customers/Partners/Consultants & the ones who plan to integrate C4C with SAP OnPremise system.


Comments/feedback are welcome!


Thanks


BR

Ankur




Assigned tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Umamahesh Swaminathan
      Umamahesh Swaminathan

      Hi Ankur,

      There is a Rapid Deployment Solution(RDS) available for the C4C integration with ERP via PI and HCI. Please check the quick link: https://service.sap.com/public/rds-cfc-erp

      Regards,

      Umamahesh

      Author's profile photo Former Member
      Former Member

      I get the best solution for rapid deployment solution for c4c, it works for me but not for my friend he has some issue with his system so he contacts to the System Thread exception from this site he gets a solution for the exception of a system.

      Author's profile photo Former Member
      Former Member

      Thanks for the Sharing the very useful information that has been targeted May 2018 Calendar Printable