SAP Knowledge Base Article - Preview

2656227 - Error: Bad Request : 400 : HTTP/1.1


  1. OData channel is used to send messages. The message processing for the integration flow has "Failed" with an error: Bad Request : 400 : HTTP/1.1
  2. In ljs trace, following details can be found.

2018 05 29<<<<iflow name>>>_Worker-1#na#avshcie#tenant name#web##na#na#na#na#Bad Request : 400 : HTTP/1.1 <?xml version="1.0" encoding="utf-8"?><error xmlns=""><code>XXX</code><message xml:lang="en">

The request URI is not valid. The segment 'XXX' refers to an entity set and not to a single entity

</message><innererror xmlns=""><transactionid>XXXX</transactionid><timestamp>20180529101100.5066840</timestamp><Error_Resolution><SAP_Transaction>For backend administrators: run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details</SAP_Transaction><SAP_Note>See SAP Note 1797736 for error analysis (</SAP_Note></Error_Resolution></innererror></error>

In ljs trace, find the request URI like GET http://host:port/sap/opu/odata/sap/.../<segment_name>/$metadata HTTP/1.1

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.



SAP Cloud Integration


SAP Integration Suite all versions

Keywords, Bad Request, 400 HTTP/1.1, Request URI, The request URI is not valid, PROCESSING DETAILS, Address, 400, HCI, CPI, Cloud Integration, , KBA , LOD-HCI-PI-CON-OD , OData Adapters , LOD-HCI-PI-OPS , Cloud Operations , 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.