CAP app architecture

[michal_majer]

Hi community,

we are currently developing a CAP application and have encountered problems:

 

Initial Architecture

Data persistence on the S4HC system using Custom Business Objects (CBOs). Exposing the data as OData services via custom BOs.

CAP consumes the data (3-4 different OData services + additional Custom CDS Views exposed as OData services), associates these CBOs with each other, and exposes them as a new OData service for consumption by a Fiori Elements app. No data persistence within CAP.

Problem: We consistently encountered errors regarding the association of entities across the different OData services. 

→ Rethink/Pivot 

Current Architecture

Moving away from CBOs on the S4HC system. Persisting the Business Objects at the HANA DB level. Association of entities is possible directly and seamlessly within CAP.

Additionally, retrieving FI documents (Financial Documents) from the S4HC system, which are associated with the main entity.

Problem: High cost of persistence on the HANA DB.

 

Summary

Initial: S4HC CBOs → CAP for Association → Fiori App. Problem: Association errors.

Current: HANA DB Persistence → CAP for seamless Association + FI Docs from S4HC. Problem: High HANA DB costs.

Could you please advise us on the best way to go forward from here regarding the architecture?IS CAP meant to do associations between entities just for projection purposes or do the entities have to be persisted by the framework in order to correctly resolve the associations?

KR,

Oliver

[michal_majer]

Hey, can You share more details about association errors? What kind of errors are those?