Skip to Content
avatar image
Former Member

Different responses from OData service for upper-case and lower-case in the URL service name

Hello everybody,

we are currently facing an issue with the OData service of one of our Fiori apps:

We have recently added two fields and one navigation property to the service in the respective SEGW project.

This worked fine on the source system, so we transported the changes to the target system (Back-End).

On the target system however, the updated service behaved in a strange way.

If we access the "Approvals" entity by making a request to "/sap/opu/odata/FIS/monm_approval_srv/Approvals", the response data is still structured the way it was before the change.

If we change the request to instead use the upper-case name of the service as "/sap/opu/odata/FIS/MONM_APPROVAL_SRV/Approvals", the response data has the desired structure, as it is supposed to be after the changes.

What's more, it is enough if only one of the characters of the service name is written in upper-case, to produce the desired result. If all characters are lower-case, the response structure suddenly changes again.

What could be causing this disparity? To our knowledge, the service name should not be case-sensitive, especially in the context of an HTTP request.

About our system infrastructure:

Source system:

Here, the OData service resides on the frontend (gateway) system.

SAP_BASIS7500001SAPK-75001INSAPBASISSAP Basiskomponente
SAP_ABA7500001SAPK-75001INSAPABAAnwendungsübergreifende Komponente
SAP_GWFND7500001SAPK-75001INSAPGWFNDSAP Gateway Foundation
IW_PGW1000007SAPK-10007INIWPGWProcess Gateway

CONCEPT GATEWAY2.0sap.comSAP GATEWAY 2.0
SAP NETWEAVER7.5sap.comSAP NETWEAVER 7.5

Target system:

Here, the OData service resides on the backend system and was published to the frontend system, as is the standard procedure recommended by SAP.

Front-End components

SAP_BASIS7510001SAPK-75101INSAPBASISSAP Basis Component
SAP_ABA7510001SAPK-75101INSAPABACross-Application Component
SAP_GWFND7510001SAPK-75101INSAPGWFNDSAP Gateway Foundation

SAP FIORI FOR S4HANA1610Initial Shipment Stacksap.comSAP FIORI FOR SAP S/4HANA 1610
SAP FIORI FRONT-END SERVER3.0Initial Shipment Stacksap.comSAP FIORI FRONT-END SERVER 3.0
AS ABAP FOR S4HANA7.51Initial Shipment Stacksap.comAS ABAP 7.51 FOR S/4HANA 1610

Back-End components

SAP_BASIS7510001SAPK-75101INSAPBASISSAP Basis Component
SAP_ABA75B0001SAPK-75B01INSAPABACross-Application Component
SAP_GWFND7510001SAPK-75101INSAPGWFNDSAP Gateway Foundation 7.40

S4HANA ON PREMISE1610sap.comSAP S/4HANA 1610

Thanks in advance for your help!

Patrick Venus

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 31, 2017 at 12:15 PM

    Hello everybody,

    The problem got solved. It was a caching problem and you can clear the cache wie this TA /IWFND/CACHE_CLEANUP

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks a lot for this Patrick,

      had exactly the same issue...
      I was under the impression that clearing the cache from GW_CLIENT in the hub (Metadata > Cleanup Cache > On Both systems) would be enough but apparently not

      Much appreciated
      Br

      Johan