FunctionImports in metadata documents

[knittedman007]

hi

Using oData Channel (minimal gateway) how do I expose FunctionImports in the metadata document?

My understanding is that a FunctionImport is used to support 'actions' or 'operations' that don't map to collections, and allow clients to use OData documents to be used to perform some (arbitrary) backend operation,

But I have no idea how to tie the backend BAPI/RFM to either the metadata description or the runtime behaviour.

I guess this is documented someplace, but I have not found out where.

Anyone point me in the right direction?

thanks

chris

[Former Member]

Hi Chris -

Chris Whealy provides an example of this in Part 2 of his HTG: [How to Write an OData Channel Gateway Service. Part 2 - The Runtime Data Provider Class|http://www.sdn.sap.com/irj/sdn/gateway?rid=/library/uuid/50ad7227-68a9-2e10-b191-905cb9b6c31a].

Regards,

Jin

[knittedman007]

Thanks !!

Yes - that helps understand things. Although the term 'action' seems to be used instead of 'functionimport' - if you search for functionimport you get nothing ... so you sort of need to know what you are looking for. But the details in the doc are very helpful.

Another question: are actions support via the generic channel approach (RFM or BOR browser)? I haven't seen any obvious info about exposing 'actions' as FunctionImports using this approach.

thanks again

- chris

[Former Member]

Regarding actions support via the generic channel approach, don't think so. However, as far as I know, the generic channel is supposed to move to the OData channel api in a future SP (don't know which one) so should be applicable then.

[knittedman007]

Yes - I just heard that too, although I don't entirely understand what it means ...

thanks

chris