OData V4 URL Encoding Issue with SAP Web Dispatcher + Proxy (Sales Order Management App)

[Veeranna_Vyapari]

Hi SAP Community,

We are facing an issue with OData V4 URL encoding after activating the standard Sales Order Management application in S/4HANA.

Note: An SAP incident has already been created, and in parallel we are reaching out to the community to learn from experts who may have faced a similar issue.

---

Issue summary

The problem occurs because equal signs (=) in the OData V4 request URL are being URL-encoded (%3D) before the request reaches the S/4HANA ICM.

In the browser, the request URL is correct and the = signs are not encoded:

https://etgwdsp.etgworld.com/sap/opu/odata4/sap/c_salesordermanage_srv/srvd_f4/sap/c_orgdivisionvaluehelp/0001;ps='srvd-c_salesordermanage_sd-0001';va='com.sap.gateway.srvd.c_salesordermanage_sd.v0001.ae-c_salesordermanage.createwithsalesordertype.organizationdivision.SalesOrderManageType.X'/$metadata?sap-language=EN

However, when the request reaches the ICM, the raw HTTP request shows that:

• = is encoded as %3D

• %27 is converted back to '

Example from ICM level 3 trace:

GET /sap/opu/odata4/.../0001;ps%3D'srvd-c_salesordermanage_sd-0001';va%3D'com.sap.gateway.srvd.c_salesordermanage_sd.v0001.ae-c_salesordermanage.createwithsalesordertype.organizationdivision.SalesOrderManageType.X'/$metadata?sap-language=EN

The SAP Gateway expects the “=” characters to remain unencoded, and because of this encoding, the request fails.

---

Landscape and behavior

Middleware involved

• SAP Web Dispatcher

• Corporate HTTP Proxy

Observed behavior

1. All apps work when the proxy is bypassed (Web Dispatcher active)

2. All apps work when the Web Dispatcher is bypassed (proxy active)

3. The issue occurs only when both proxy and Web Dispatcher are active

This strongly indicates that the URL is being modified due to an interaction between the proxy and Web Dispatcher.

---

Troubleshooting performed

• All required roles, authorizations, services, and ICF nodes are active

• Web Dispatcher profile parameters adjusted to prevent URL encoding

• Web Dispatcher mod file changes attempted for OData V4 handling
  → Issue still persists

As per internal network team analysis:

• A change may be required in the Web Dispatcher index file

• Neither the network team nor BASIS team has access to modify it

• Only SAP can make changes at this level

---

Questions to the community

• Has anyone experienced a similar OData V4 URL encoding issue with Web Dispatcher + proxy?

• Is this a known limitation or defect in SAP Web Dispatcher for OData V4?

• Are there any supported parameters, SAP Notes, or workarounds to prevent encoding of = in the URL?

• Should this be handled via ICM settings, Web Dispatcher configuration, or proxy rules?

• Is there any recommended architectural workaround until SAP provides a fix?

Any guidance, experiences, or references would be greatly appreciated.

Thanks in advance for your support.

Varsha J S

---

#SAP #S4HANA #ODataV4 #SAPGateway #SAPWebDispatcher #ICM #SAPBasis #SAPFiori #SAPCommunity
@SAP @SAPCommunity @SAPSupport

---