SAP Knowledge Base Article - Preview

3760937 - Odata v4 receiver adapter routes to wrong client when sap-client is missing in metadata request

Symptom

  • An integration flow using the OData V4 Receiver Adapter in SAP Cloud Integration (CPI) routes requests only to the default SAP client, for example `100`, even when a different target client such as `110` or `120` is intended. 
     
    You may observe the following symptoms: - 
    1. The iFlow fails during the metadata call with the error `HTTP/1.1 404 Not Found`.  
    2. Backend response headers such as `SAP_SESSIONID_QS4_100` indicate session creation in client `100`.
    3. The required `sap-client` parameter is missing from the actual call and/or metadata call. 


Read more...

Environment

  • Cloud Integration
  • SAP Integration Suite

Product

Cloud Integration all versions ; SAP Integration Suite all versions

Keywords

odata v4, receiver adapter, sap-client, metadata request, custom query parameters, query options, wrong client, client routing, 404 not found, default client, multi-client backend, metadata details, $metadata, integration suite , KBA , LOD-HCI-PI-CON-OD , OData Adapters , 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.