Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Issues in Netweaver Gateway concepts.

Hello Gateway Gurus,

      I had been carrying out OData service activities in Netweaver Gateway, Facing issues in understanding the functionalities and concepts in it.. I hope this post will be helpful for getting all basics understanding cleared.

NOTE: Please consider doubts mentioned below as Independent of each other also these images are not related to each other.

1. I am bit puzzled in the properties section of the data model... as in what is the relevance of the checkboxes as shown below picture..  I have noticed these reflected in $metadata of the service as well).

2. Regarding the other confusion its related to cardinality..

When we do we go for Cardinality as "N" and when for Cardinality as "M"

3. I have used the following lines of code many times...

sharing the snapshot for the same.

but yesterday I was in worry about what the IO_EXPAND-> Compare_to mean as I didn't know its working..

also the use of lv_compare_result ???

like for example, if I have to specify two children , but Even If I specify 'SOItems' here , I get 'SOSchedules' as well  ...

Thanking you in advance,

Hope to get many helpful hit on this..


Pavan Golesar.


Hi Pavan,

Can you please explain a bit more about the third point? Also please provide the URL that you are hitting, code of your GET_EXPANDED_ENTITY or GET_EXPANDED_ENTITYSET as a text file attachment. This can help in clarifying the things.

Let me try to explain from my side. Suppose there are 3 entitysets: SOHeaderSet, SOItemSet & SOSchdlineSet and there are two navigation properties defined: SOHeaderToItem, SOItemToSchdline. Now you try to hit these two URLs:

1. /sap/<MyService>/SOHeaderSet?$expand=SOHeaderToItem/SOItemToSchdline

2. /sap/<MyService>/SOHeaderSet?$expand=SOHeaderToItem

The 1st one would give you the complete list containing all 3 sets in response. But 2nd should give only SOHeaderSet and SOItemSet. Here comes the use of

io_expand->compare_to( '<navigationPropertyName>' ). By using this statement you can check which all navigation properties are asked in the request URL and then pass only those properties in the response.

Hope it clarifies the doubt at some extent.



0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question