SAP Gateway Client – Tips and Tricks
Purpose of this blogpost: List little tricks while using the SAP Gateway Client.
Who should read it: Anyone and everyone who uses SAP Gateway Client and wants to extract more from it.
Relevant SAP Transaction: /IWFND/GW_CLIENT
Format of this blogpost: Q&A
Here we go.
Que 1: I am not able to launch transaction /IWFND/GW_CLIENT. What should I do?
Ans 1: Try /n/IWFND/
Que 2: I have entered the Service URI. When I want to check Service Metadata, and I click on “Service Administration” or “Service Implementation” button, I get the following message: “Function not available for remote gateway system”.
How should I check the service metadata?
Ans 2: You are probably using an external URI. The SAP Gateway Client works only with local links.
In order to know the internal link, from the external URI, remove the domain and host name.
For example, if your external URI is: <https://erpxxxxx.hana.ondemand.com/sap/opu/odata/sap/SERVICE_NAME>,
replace it with this: </sap/opu/odata/sap/FCO_PI_COST_CENTER/>,
and then click on “Service Implementation” or “Service Administration” button.
It should work now.
Note: The shortened URI is filled with the local domain and host name by the Gateway Client itself, before it serves your request.
Que 3: I am using filters in my URI. Filter on Attribute A works, but on Attribute B does not. Why?
Ans 2: Seemingly the concerned OData Service has not implemented the Filter for Attribute B. Check the OData Service logic in GET_ENTITYSET method of the corresponding implementation Class.
For example, filter on CompanyCode works: <https://hostname.corporate.com:PORTNUMBER/sap/opu/odata/sap/SERVICE_NAME/EntitySetName?$format=json&$filter=CompanyCode%20eq%20%271110%27>,
But, filter on CostCenterID does not work:<https://hostname.corporate.com:PORTNUMBER/sap/opu/odata/sap/SERVICE_NAME/EntitySetName?$format=json&$filter=CostCenterID%20eq%20%270000000001%27>,
Then, most likely a filter on CostCenterID has not been implemented in the Service Logic.
Note: You may view the Service Implementation Class by clicking on the button “Service Implementation” on Application toolbar. (Refer to Que 2).