Quantcast
Channel: SCN : All Content - SAP Gateway
Viewing all articles
Browse latest Browse all 2823

oData service development based RFC

$
0
0

Hi Firends,

 

I am developing a oData service based on RFC. Our setup is central hub deployment. We have Gateway server and ERP in separate boxes.

 

Question 1: In which server I have to develop the oData service? is it in SAP DEV box or SAP Gateway box?

 

I tried initially developing oData service in Gateway Server but I did not find any data elements or references ,  data types in Gateway server so I had to switch my oData service development to ERP DEV system, then I can run the service in SAP Gateway client via System Alias usign RFC connection.

 

is it best practice?

 

2. As part of the oData service development.  I have created custom z RFC wrapper with two import parameters likeIM_MODUS , IM_BEGDA and EX_ACCOUNTS as Export parameter. Now I am calling the below FM in my custom wrapper as ZAccounts_GET.

 

 

CALL FUNCTION 'PT_ARQ_ACCOUNTS_GET'

       EXPORTING

         im_pernr     = '1234'

         im_begda     = '20141111'

         im_modus     = 'R'

 

       IMPORTING

         ex_accounts  = ex_accounts

       TABLES

         ex_messages  = l_messages

         ex_commands  = lx_commands.

   ENDIF.


3. In Data Model imported RFC which created Entity Types.


4. Now in the service implementation , I have selected GetEntitySet(Query)--> Map to data source, here I am not seeing input parameters, why are they not showing up ? attached screen doesn't have imPernr, im_begda, im_modus.  Some reason these are created in separate Entity type.  Screens attached.


Viewing all articles
Browse latest Browse all 2823

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>