What is the significance of creating an implementation class for a Behavior projection in SAP RAP?

[SachinArtani]

Hi experts,

I noticed that for the behavior projection of manage sales order v2 RAP app i.e. C_SALESORDERMANAGE, there is an implementation class maintained and certain actions are defined below. If there are already actions defined in R_SALESORDERTP which are also visible in UI app, why do we need to define actions in projection view and also create another implementation class there?

Thanks in advance

[Ramjee_korada · Accepted solution]

Hi,

This allows specific functionality to be implemented at a specific projection layer but is not required for other projections. 

 Actions and Functions in Projection Behavior Definitions 

Best wishes,

Ramjee Korada

[SachinArtani · Accepted solution]

Hi @Ramjee_korada, Thank you for your answer. With that, I understand that for a single data model, we create multiple projections with multiple behavior projections where we could have projection specific actions and we can expose those projections to make multiple end applications serving different actions.

This approach would reduce the overhead of creating many actions in a single app and then hiding specific actions by creating variants of the main Fiori app.

Please correct me if I am wrong here. Also, don't we project the actions we create in Behavior Projection? Like "use action setMaterialText"?

[Ramjee_korada · Accepted solution]

Your understanding correct including the last point.