Handling maximum number of Communication Scenarios in SAP C4C

[former_member732037]

Dear Experts,

Hope this finds each of you safe and in good health.

We are building an two way integration of SAP C4C with non-SAP Marketing system via HCI. The inbound integration to SAP C4C has been completed. We have 4 integration scenarios to develop for outbound integration scenarios. One each for Lead confirmation, Account Data, Contact Data and Marketing Permission Data. The deployment for the inbound interface has been completed as well.

Now, we realized that the maximum number of Communication Scenarios allowed to be created per Solution is 15 (which I think is less), has been reached in our case.

We were thinking of creating a new patch solution for the development of Account,Contact and Marketing Permission integration interfaces. But this poses another problem to us, as we will not be able to use the extension field from Lead BO the newly created solution, the extension field is obtained via standard Odata web service extension in old solution.

Any help in this regard would be much appreciated.

Warm Regards,

Manu

[anant_acharya · Accepted solution]

Dear Manu,

This is current limitation in the C4C.

You can refer the KBA & Blog for details.

For your scenario, the best practice is to build one communication scenario per system and use it for the multiple services being consumed from that external system. System allows you to assign more services to an existing CSD content in a patch solution.

OR

If there are use cases which requires definition of more number of Communication Scenario Definition, then there is a need to split the SDK Solution in to multiple smaller solutions logically (manual process). Such splitting of solutions to logical smaller solutions would improve the overall lifecycle experience of SDK solution during various life cycle process.

Regards
Anant

[former_member732037 · Accepted solution]

Dear Anant,

Thank you for the response and clarification.

Seems to me like splitting of the solution would be the best possible to go ahead as we have some .csd files in the solution which are unused but cannot be deleted as they are already downloaded.

Warm Regards,

Manu