Possibility to delegate processing of PDI/SDK actions & validations to BTP synchronously ?

[christiaens]

Hello

Context

We assume that it is possible to already on C4C V1 implement a clean core approach in preparation of C4C V2. We acknowledge that a more event driven (notification) using for example the event mesh and BTP Build Apps or BTP CAP/RAP is a possibility. Nonetheless, we also want to have more complex "in-app" possibilities externalized. These "in-app" extensions are typically done using PDI/SDK. This is however not manageable for complex in-app developments. There is no possibility to correctly modularize coding using a scripting language like ABSL. Therefore the below questions:

Questions:

1/ Is it possible to use the PDI/SDK actions as extension points (such as "ROOT/AfterModify, Item/BeforeSave) ? We want to use the PDI/SDK as a sort of BADI extension point ? Can we from there delegate in a performance optimal way to for example to a KYMA container where using CAP the logic is implemented ? Even CAP or RAP (we have quite a number of ABAP-ers) on Cloud Foundry would be perfect.

2/ We were thinking about microservices where that logic would be implemented since we assume that this would be most performant. Correct ?

3/ Is there a framework somewhere that could be leveraged to implement this delegation to a real enterprise quality development platform ?  Indeed, PDI collections would have to be "converted" into a format that can be understood by the separate platform (e.g.. CAP or RAP or  ...). Ideally this also has a signature allowing to bring back the changes that need to be done ... 

4/ If this would exist, can that effort then be salvaged when we would go to C4C V2 ? This although I am aware that V1 is ODATA based whilst V2 is REST based it seems.

More context: 

Correct management of a very large extension logic on multiple objects (ticket, quotes, ...) on multiple levels (Root, item, partners, ...) at multiple points (ON_CHANGE, VALIDATE, ON_SAVE, ...) in PDI/SDK is not really possible. Modularization is hell in PDI/SDK. Managing versions is hell in PDI/SDK. Indeed, this can even be deemed as normal. SAP C4C V1 is NOT a full fledged development platform....You can do simple scripting. That's it.  It is not made to make enterprise quality developments like CAP or RAP. 

For example the ticket is a golden bullet object. As such used for multiple use cases. Each case has it's own "custom logic". Managing the code is becoming really unmanageable. Quotes are also quite extended if they are to be used by all countries over the world.... 

[Simon1982 · Accepted solution]

Hi,

From my experience in the past 1,5 year I'll try to answer you questions from my perspective:

1/ Is it possible to use the PDI/SDK actions as extension points (such as "ROOT/AfterModify, Item/BeforeSave) ? We want to use the PDI/SDK as a sort of BADI extension point ? Can we from there delegate in a performance optimal way to for example to a KYMA container where using CAP the logic is implemented ? Even CAP or RAP (we have quite a number of ABAP-ers) on Cloud Foundry would be perfect.

Answer: There are two option for this; if it is simple logic the possibilities in the Key User Tool can be used (simple determinations / validations / autoflows).

The second is to use side-by-side extensions. For BADI like / Before save / After modify etc. we use microservices in Mendix but this can be any development tool/container (e.g. Kyma). I know SAP uses Node.js deployed on Cloud foundry for demo's.  

2/ We were thinking about microservices where that logic would be implemented since we assume that this would be most performant. Correct ?

Answer; Yes, that is correct.

3/ Is there a framework somewhere that could be leveraged to implement this delegation to a real enterprise quality development platform ?  Indeed, PDI collections would have to be "converted" into a format that can be understood by the separate platform (e.g.. CAP or RAP or  ...). Ideally this also has a signature allowing to bring back the changes that need to be done ... 

Answer: Don't think there is a dedicated framework for this. You should choose your preferred platform/container/language and basically rebuild your PDI code I guess.

4/ If this would exist, can that effort then be salvaged when we would go to C4C V2 ? This although I am aware that V1 is ODATA based whilst V2 is REST based it seems.

Answer: see previous but reach out to your SAP v2 account rep. would be best to get this answered.

Also follow the posts of @Kinsbrunner about development in a Sales and Service Cloud environment.

Simon