As you can see, there isn’t much to do. You can rename the business data graph identifier, for example, to erp or v1, which you can use as a version indicator for your business data graph. If some of the destinations aren’t required in the use cases for this business data graph, you can comment these out. There’s only one locating rule: everything (sap.*) comes from the single SAP S/4HANA data source.
This is a common scenario with multiple systems, each having its own policy. The locating policy shows that SAP S/4HANA (erp), is the leading source of truth for all sap.s4 mirrored entities, and all unified entities, except for CustomerQuote (in namespace sap.graph), which comes from the SAP Sales Cloud system (c4c). In all cases, the locality-of-reference principle dictates that key-based references are handled locally.
The application uses one or the other data source.
In the second use case, the application user may require access to the data in both systems.
Therefore, there are two use cases to consider
Glasp is a social web highlighter that people can highlight and organize quotes and thoughts from the web, and access other like-minded people’s learning.