Dear Friends,
This is regarding the $filter behaviour in Netweaver Gateway.
I wish to explain a simple use-case in order to get to the question.
(A)
My Entity , namely, SOPartner has the following fields
SOID (key)
PartnerID (key)
PartnerFunction (key)
PartnerFunctionText
(B)
In my Query function module, the query would be similar to "Get Me all Partners for a Given SalesOrder" (~/SalesOrders('X3')/SOPartners)
(C)
Signature of the FM is as follows
CALL FUNCTION lv_rfc_name
EXPORTING
iv_sohdr_guid
iv_partnerfct
IMPORTING
et_sopartners
Question:
1. I believe, the query with $filter similar to this -> ~/SalesOrders('X3')/SOPartners?$filter=PartnerFunction eq '14' ...can be catered by implementing the filter in the DPC_EXT class.
2. Ideally, PartnerFunction should be range-table in order to support queries like ...?
~/SalesOrders('X3')/SOPartners?$filter=PartnerFunction eq '14' and PartnerFunction eq '15'
3a. What happens to requirements where the $filter needs to be done on NON-INPUT fields? ( say, PartnerID? ).
3b. What is the idea behind "Requires Filter" flag for the EntitySet and "Filterable" flag for the property at the Entity Level?
4. Would there be an XSLT transformation available for filtering the result-set in the case of (3a)?
Many thanks for your time and patience
Cheers,
Suresh