3662936 - OData V2 Receiver, $batch payload with encoded <uri>

The batch request payload consists of a <uri> which specifies the resource on which that batch operation is performed. This <uri> does not have URL encoding, causing an error at runtime.

Example of <uri> without encoding:
<uri>ProductSet('HT=1000')?sap-client=100</uri>

According to the RFC specification, the character = is a reserved character with special meaning in URLs. In this case, the = inside the single quotes ('HT=1000') is unencoded, which is incorrect. However, the = in the query option (sap-client=100) must remain unencoded.
The expected encoded value in <uri>: ProductSet('HT%3D1000')?sap-client=100

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

• SAP Integration Suite
• Cloud Integration

CPI, Cloud Integration, iflow, deployment, odata, script, batch, payload, encoded, rfc, uri, encoding , KBA , LOD-HCI-PI-CON-OD , OData Adapters , Problem