Title

CAPM - SAP Datasphere

Description

A CAP application consuming data from SAP Datasphere.

When business data and models are available in SAP Datasphere, they can be exposed as OData Services.
When a CAP app needs to connect to SAP Datasphere (DS), do not connect to the HDI container underneath DS, use the OData Services provided by DS.
Using DS OData Services simplifies consumption and maintenance as there is no need to configure HDI cross-container accesses, roles and synonyms.

Side-by-Side extensions to keep the Core Clean.
An application that extends standard Purchase Orders with custom data.
An application that gives access to employee information mixing data from SAP S/4HANA and SuccessFactors.
An application using data from Google BigQuery and SAP S/4HANA.

HTML5 Application Repository Service can host any web app such as SAP Fiori, Angular, React, Vue, etc.
CAPM (Cloud Application Programming Model) apps could be developed in Node.js or Java.
Communication between the services should go through the Destination Service, not added to the diagram to simplify it.
On-premise solutions could be both SAP and non-SAP.
Cloud solutions could be both SAP and non-SAP.
SAP Cloud Identity Services is not required to connect to On-premise or Cloud solutions.

CAP, CAPM, Node.js, Java, SAP Datasphere, OData