Skip to Content
0

Best practices to handle standard content like C4C in sap pi?

Mar 23, 2017 at 02:51 PM

45

avatar image

Hi All,

I am trying to understand best approaches in configuring the standard content interfaces in SAP PI, i have the following queries

1) Can i directly refer the standard content namespace and operation mapping directly in Integration directory or do i need to create a new software component and add standard SWCV as dependent objects underneath?

2) If there is any enhancement needed for the standard interface do i need to create a different namespace and configure my custom mapping?

3) If in later release i am getting a new mapping version where there are additional fields added in the target XSD then i assume that this would break fix the additional functionality at target end if the fields are not populating which are required, so for every new release do i need to take new mapping version from standard content and apply previous custom logic and migrate to other environments?

Appreciate if anybody can help me to understand the best practices or provide any docs related to them. Thanks!!

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Harish Mistri Mar 23, 2017 at 10:48 PM
0

Hi Vikram,

Please find my inputs

1) Can i directly refer the standard content namespace and operation mapping directly in Integration directory or do i need to create a new software component and add standard SWCV as dependent objects underneath?

--->> It is better to create custom SWCV and create the dependency. you can enhance the content in custom swcv.

2) If there is any enhancement needed for the standard interface do i need to create a different namespace and configure my custom mapping?

-->> It is a good practice to enhance any standard content in custom swcv.

3) If in later release i am getting a new mapping version where there are additional fields added in the target XSD then i assume that this would break fix the additional functionality at target end if the fields are not populating which are required, so for every new release do i need to take new mapping version from standard content and apply previous custom logic and migrate to other environments?

-->> you need to perform the custom rules after the upgrade. the Data type enhancement will not be impacted. Please refer the below blog

https://blogs.sap.com/2015/02/12/sap-standard-interface-sap-esr-content-package-enhancement-in-pi/

regards,

Harish

Share
10 |10000 characters needed characters left characters exceeded