How to implement Multi Origin Composition when not every user has a SAP user on the metadata system?

Former Member — Thu, 11 Apr 2019 13:06:51 GMT

Hello,

we have an OData service with two destinations. The OData service is provisioned in the SAP Cloud Platform.The OData service is error tolerant.

The service is referenced in our manifest.json as follows:

"Srv": {
  "uri": "/sap/opu/odata/sap/ZTEST_SRV;mo",
  "type": "OData",
  "settings": {
    "odataVersion": "2.0"
  }
}

Our problem is that not every user has a SAP user in in both systems. Some users even have only a SAP user in Destination B. These users cannot access the OData service in any way. They cannot access $metadata and they also cannot access entity sets. It seems like error tolerance only works if you have at least a SAP user on the metadata default system.

Does anyone else have this problem? Any solutions on how to fix this?

Re: How to implement Multi Origin Composition when not every user has a SAP user on the metadata system?

Former Member — Wed, 08 May 2019 06:51:55 GMT

We found a solution:

Go to OData Provisioning Administration page
Make OData service error tolerant
Open burger menu and go to "Metadata"
Activate metadata caching
Remove checkbox from "Destination-based metadata caching"

Now the metadata will be fetched from the first available system 🙂

Question Re: How to implement Multi Origin Composition when not every user has a SAP user on the metadata system? in Technology Q&A

How to implement Multi Origin Composition when not every user has a SAP user on the metadata system?

Re: How to implement Multi Origin Composition when not every user has a SAP user on the metadata system?