C4C. new Solution oder patch solution , this is a dilemma

[siwei_yang]

Hi there,

this is a question that I have been thinking about but got no idea how to deal with it.

Assuming, that you created three original solutions A , B and C.

A has a customer BO called BO_a

B has a customer BO called BO_b

As I known there is no possibility to use both BO_a and BO_b within the Solution C, Am I right?

To avoid this problem, we should create from verfy first the two customer BO within one solution called X , instead of putting those in different solutions. And if this solution X has been assembled and deployed then we have to create a patch solution on it, and do some new things there, for example create another customer BO e.g. BO_x. So it actually means that we should put always all enhancements in the patches of that original solution X, because we will never know for our future enhancements, when we will run into the case where we have to use BO_a , BO_b or BO_x ... .

However, on the other sides, there is a drawback to create a patch solution . As we know creating a patch solution will delete or disable all your scoping and fine-tuning and configuration about formular templates and workflow rules ... etc. It indicates that we actually should not open patch solution too often, because nobody likes to reconstruct all those things each time.

So this is the dilemma what I mean. I hope I have explained it clearly.

Someone adviced me to create a webservice for each BO. But this will increase cost and effort significantly.

Now I would like to know how the other people do to deal with this problem.

Thanks a lot

Peter

[former_member206060]

Hi Peter,

First of all as you have mentioned, it is not possible to access a custom BO created in solution A to be consumed in solution B. For this you need to use webservices functionality, this can increase the effort but this is how you can use cross solution BO's.

Now coming to the point where you have to create a patch solution if there are any changes after the solution assembly, which is a regular process. The patch version keeps adding up as and when changes arise. However it doesn't mean that you always have to keep uploading the patch version to the original solution, you will have all the patch versions ZIP file saved in your computer, in case any such situation occurs you can just upload the zip file of the latest version directly to the orginal solution.

Also as you mentioned, it is not true that after all patch version creation you have to reconstruct/ reconfigure everything. This is true only after the first patch creation from the orginal solution. This is because the namespace changes for patch and you will have to create data and scoping again for this patch namespace. For subsequent patch version of the same solution these are not necessary and also this scenario exists only in test tenants and will not happen in production tenants.

Hope this clarifies your concerns.

Thanks,

Dhanya

[Former Member]

Hi Dhanya,

Thank you for the information.

I am majorly looking for these two areas:

1. Is there any Specific documentation available for C4C support and enhancement.

2. Any sample technical specifications and process flowsheets for enhancement.

Best regards,

Veeru

[former_member206060]

Hi Veera,

If you are looking for PDI documentation specifically, then you can refer to the SAP Cloud Application Studio Help document , which has all the details. And topic specific documents will be available as blogs in community as well.

https://help.sap.com/viewer/cbcebe3cfb1647a8b0322c18dbb0b481/2019.11/en-US

Hope this helps!

Thanks,

Dhanya