Symptom
When updating the OMSA service instance with default plan by inputting JSON in BTP, encounters error: "Custom authorities are not supported for non-default plan."
Meanwhile, in the log, there were errors with the same Instance Id.
{"authority":"api.sourcing-availability.cloud.sap","bytes_received":1902,"bytes_sent":104,"connection_termination_details":null,"downstream_local_address":"xx.xx.xx.xx:8080","downstream_remote_address":"xx.xx.xx.xx:0","duration":22,"mdc":{"BTPTenantId":"","dt":{"trace_id":"d1xxxxxxxxxxxxxxxdcb"}},"method":"PATCH","path":"/sbf/v2/service_instances/5021xxxx-xxxx-xxxx-xxxx-xxxx5511401?accepts_incomplete=true","protocol":"HTTP/1.1","request_headers":{"accept":"application/json","accept_encoding":"gzip","x_test_run_id":null},......
Read more...
Environment
SAP Commerce Cloud with OMSA Integration
Product
Keywords
custom authorities are not supported for non-default plan, omsa, default plan error, btp service instance update, service plan, json configuration, service broker, order management for sourcing and availability , KBA , CEC-SCC-INT-OMSA , OMSA Integration , IS-DFO , SAP Order Management for sourcing and availability , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview