Using tables parameters for RFC

Hi All
I am trying to use tables parameter for a Remote Function Call.
It says it is obsolete and not working, we are using ECC6.0 version of SAP.
Any help??

Instead, you should use a table type in a IMPORTING or EXPORTING parameter. Create the table type in SE11 and then reference this table type in your parameter in the IMPORTING/EXPORTING tab. The use of TABLES parameters section is obselete.
Regards,
Rich HEilman

Similar Messages

Table parameters for RFC FM.

hi,
Is it required to create table types in SE11 for populating TABLE parametes in RFC FMs.
I have got structures but when i mention T_RSPARAMS type RSPARAMS in tables tab its not accepting.
Do I need to create table type first for those structures and then declare in TABLES tab?

Hi,
If you are in ECC 6.0, use the foll declaration for tables :
IT_X LIKE abc.
where abc shud be a structure. It works perfectly fine. " LIKE " parameter is not present in the F4 help, but u manually enter it. It works alright.
Thanks
Nayan

Using Table types in RFC

Hi All,
I am trying to create one RFC. But in that RFC, I wish to use Table types as import and export parameters completly avoiding Tables tab. Will that effect the performance of RFC if I use Table types. If Yes, Please give clear clarification where it effects the performance.
Also please let me know how the performance of the RFC is effected if we use Tables tab.
Thanks,
Ravee..

"I wish to use Table types as import and export parameters completly avoiding Tables tab."
I'm not sure if Tables can be avoided, if just using regular ABAP. I know that the Importing tab would not work when I tried it (under vrs 4.6b).
Because you are launching separate processes, in separate memory areas: any parameter you use in RFC has to be known by the calling and the callee functions/programs. This means that you need a common reference. If you have more than one function module in a function group, you can use the TOP file and a 'Z' data dictionary structure.
I hope that this helps,
Dan Perecky

Sample JAVA code using Resource Adapter for RFC Connections

Hi Java Knowledgeable Ones.
I have successfully deployed the SAP Netweaver J2ee Engine "Resource Adapter for RFC Connections to ABAP Systems" to my Web Application Server. Now I need to develop a JAVA application that would utilize this deployed resource adapter. The resource adapter specifies the SAPClient, UserName, and password. I am thinking that the JAVA code to invoke this connection would therefore not need to provide this information as it should be available in the resource adapter.
Do you have sample code that you could send to me showing how to do this?
Thanks,
Kevin

Hi Kevin,
this is actually no good style! You should not open the connection with the adaptor knowing the password. Usually it should work via a connection that uses only basic rights and the user has already authenticated and is using his security ticket.
For security handling see:
http://help.sap.com/saphelp_nw04/helpdata/en/61/f8bc3d52f39d33e10000000a11405a/frameset.htm
Regards,
Benny

How to use different parameters for two tables(chart and Table) in one report in SSRS?

Hi,
Here is my requirement, i have 7 parameters in my report(Site,Account,LOB,year,Month,WeekDay and Date_Filter),
and in my report i have one table and one Chart,
my requirement is the table in the report has to show the data for 6 parameters only i.e(Site,Account,LOB,year,Month and WeekDay).so the table has to consider only 6 parameters, and it has ignore the 7th parameter, table should not consider Date_Filter parameter.
And Chart has to consider all 7 parameters.
so, when we preview the report table has to show the data for only 6 parameters and chart has to show the data for all 7 parameters.
if there is a way to get this Please reply me ASAP, it is an urgent requirement.
Thanks in Advance,
Naveen

Hi Naveen,
Refer below link to create multiple datasets as suggested by Gnanadurai
http://technet.microsoft.com/en-us/library/ff714047(v=sql.105).aspx
Thanks
Swapna

Using table rows for input

Hi,
Is it possible to use rows of table for input? Table binded to a RFC model table parameter. The rows of table is looking readonly.
Best regards,
Altug Bayram

Hi,
Did u check if the attributes set to read only. ?
What is the cardinality of the node.
And when it is a input for the RFC , i think you have missed the createElement part...!
P.S : It will be gain more attention when it is a seperate question.
Regards
Bharathwaj
Message was edited by: Bharathwaj R

More than 1 line items in bdc using table controls for BOM

Hi....
how do u update more than one line item for BOM using BDC table control.......
is there any specific command for doing that.......
hav tried d following code bt it takes the flatfile i/p FOR 2 LINE ITEMS as 2 different BOM'S.....
would appreciate ur help....plz provide code.............
REPORT zbdc4_cs01
       NO STANDARD PAGE HEADING LINE-SIZE 255.
INCLUDE bdcrecx1.
DATA : a TYPE i,
       b type i,
       c type i.
DATA : BEGIN OF it_rec OCCURS 0,
       rec(200) TYPE c,
       END OF it_rec.
DATA : BEGIN OF ctab OCCURS 0,
       matnr(18),
       werks(4),
       stlan(1),
       END OF ctab.
DATA : BEGIN OF xtab OCCURS 0,
       idnrk(18),
       menge(13),
       postp(1),
       END OF xtab.
DATA : BEGIN OF itab OCCURS 0,
       matnr(18),
       werks(4),
       stlan(1),
       idnrk(18),
       menge(13),
       postp(1),
       END OF itab.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = 'C:/TEST4.TXT'
      filetype            = 'ASC'
      has_field_separator = 'X'
    TABLES
      data_tab            = it_rec.
LOOP AT it_rec.
    a = strlen( it_rec-rec ).
    if a = 55.
    itab-matnr = it_rec-rec+0(18).
    itab-werks = it_rec-rec+18(4).
    itab-stlan = it_rec-rec+22(1).
    itab-idnrk = it_rec-rec+23(18).
    itab-menge = it_rec-rec+41(13).
    itab-postp = it_rec-rec+54(1).
    APPEND itab.
    elseif a > 55.
    itab-matnr = it_rec-rec+0(18).
    itab-werks = it_rec-rec+18(4).
    itab-stlan = it_rec-rec+22(1).
    itab-idnrk = it_rec-rec+23(18).
    itab-menge = it_rec-rec+41(13).
    itab-postp = it_rec-rec+54(1).
    APPEND itab.
    itab-idnrk = it_rec-rec+55(18).
    itab-menge = it_rec-rec+73(13).
    itab-postp = it_rec-rec+86(1).
    APPEND itab.
    endif.
ENDLOOP.
PERFORM open_group.
LOOP AT itab.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0100'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29N-STLAN'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RC29N-MATNR'
                                   itab-matnr.           "'3000000107'.
    PERFORM bdc_field       USING 'RC29N-WERKS'
                                   itab-werks.              "'UN02'.
    PERFORM bdc_field       USING 'RC29N-STLAN'
                                   itab-stlan.              "'1'.
    PERFORM bdc_field       USING 'RC29N-STLAL'
    PERFORM bdc_field       USING 'RC29N-DATUV'
                                  '11.08.2008'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0110'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RC29K-BMENG'
                                  '1'.
    PERFORM bdc_field       USING 'RC29K-STLST'
                                  '1'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29K-EXSTL'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0111'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29K-LABOR'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29P-POSTP(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RC29P-IDNRK(01)'
                                   itab-idnrk.             "'1000000232'.
    PERFORM bdc_field       USING 'RC29P-MENGE(01)'
                                   itab-menge.              "'100'.
    PERFORM bdc_field       USING 'RC29P-POSTP(01)'
                                   itab-postp.             "'L'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0130'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29P-POSNR'.
    PERFORM bdc_field       USING 'RC29P-POSNR'
                                  '0010'.
    PERFORM bdc_field       USING 'RC29P-IDNRK'
                                  '1000000232'.
    PERFORM bdc_field       USING 'RC29P-MENGE'
                                  '100'.
    PERFORM bdc_field       USING 'RC29P-MEINS'
                                  'KG'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0131'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29P-POTX1'.
    PERFORM bdc_field       USING 'RC29P-SANKA'
                                  'X'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29P-POSNR(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_dynpro      USING 'SAPLCSDI' '0140'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RC29P-POSNR(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=FCBU'.
    PERFORM bdc_transaction USING 'CS01'.
ENDLOOP.
PERFORM close_group.

Hi
Check this sample code for the Table Control in BDC:
data: fnam(20) type c.
move 1 to id.
    loop at TI_STAGING WHERE VENDOR = IT_STAGING-VENDOR AND DOCDATE = IT_STAGING-DOCDATE.
      concatenate 'RM06E-EPSTP(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-itmcategory.
      concatenate 'EKPO-KNTTP(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-accassignment.
      concatenate 'EKPO-EMATN(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-material.
      concatenate 'EKPO-TXZ01(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-shortxt.
      quan = ti_staging-poqty.
      concatenate 'EKPO-MENGE(0' id ')' into fnam.
      perform bdc_field       using fnam quan.
      concatenate 'RM06E-EEIND(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-deliverydate.
      netpr = ti_staging-netpr.
      concatenate 'EKPO-NETPR(0' id ')' into fnam.
      perform bdc_field       using fnam netpr.
      concatenate 'EKPO-MATKL(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-mategroup.
      concatenate 'EKPO-WERKS(0' id ')' into fnam.
      perform bdc_field       using fnam TI_STAGING-plant.
      ID = ID + 1.
    ENDLOOP.
Regards,
Vishwa.

Get parameters for rfc sender communication channel

Hello everybody,
does anybody know how to establish the values for the cc-parameters?
For example:
Where do I receive information about:
- the Application Server (Gateway) = Gateway host name of the sender system
- the Application Server Service (Gateway)
- the Program ID
etc.
Regards Mario

hi,
did you have a look at my weblog?
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
>>>- the Application Server (Gateway) = Gateway host name of the sender system
fomr SAPlogon
>>>>- the Application Server Service (Gateway)
SAPGW + system number from SAPlogon
>>>>- the Program ID
any name
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Using table data for control

Hello,
I would like to use data entered in a table to automate air flow volume/sequence to a test chamber. As shown in the table control screen grab, the first column specifies the number of iterations through table elements during a test run and second column data specifies duration for each row sequence. Entries in the other columns are specific to different flow valves and specify set point values required to meter flow.
I guess my question is how can I index/assign each column in the table such that data to operate respective valves are obtained at subsequent iterations whilst simultaneously acquiring data from other components sequentially? Whilst I acknowledge that the solution may be quite simple, I have trawled through various examples and posts on tables and arrays without hitting on a solution. The attached .vi allows me to do some part of the test run.
Best regards,
Callisto
Solved!
Go to Solution.
Attachments:
Chip Firing.vi ‏34 KB

Hi Callisto,
If I understand your question correctly then the solution is in fact fairly straightforward. The important point to bear in min is the fact that the Table control can effectively be dealt with as an array of string. You can then use all of the traditional array manipulation tools and techniques to manipulate your data as you want. For example, use the Index Array function to extract specific columns and then if you want to pass individual elements within a column into a loop, wire the array up to the loop and ensure that Indexing is enabled. If you then want to use these data elements to drive your test application, you may want to convert some of the resulting string into more useful numeric's.
All of these concepts are demonstrated in the attached VI. I hope this helps, but let me know if you have any further questions.
Best Regards,
Christian Hartshorne
NIUK
Attachments:
926242 - Table Control.vi ‏9 KB

Urgent help- table input for RFC

Dear all,i have this following codes
a = Long.parseLong(wdContext.currentContextElement().getMat_doc_frm());
    b = Long.parseLong(wdContext.currentContextElement().getMat_doc_to());
    c = b-a + 1;
     Zbapi_Goodsmvt_Getdetail_Input stockitem = new Zbapi_Goodsmvt_Getdetail_Input();
    Zdocnum docnum = new Zdocnum();
for(int x = 1; x <= c; x++){
          docnum.setMat_Doc(String.valueOf(a));
         docnum.setDoc_Year(wdContext.currentContextElement().getYear());
         stockitem.addZdocnum(docnum);
         wdComponentAPI.getMessageManager().reportSuccess(docnum.getMat_Doc());
         wdComponentAPI.getMessageManager().reportSuccess(docnum.getDoc_Year());
          a = a+1;
    wdContext.nodeZbapi_Goodsmvt_Getdetail_Input().bind(stockitem);
     IWDMessageManager manager = wdComponentAPI.getMessageManager();
          try {
                                     wdContext.currentZbapi_Goodsmvt_Getdetail_InputElement().modelObject().execute();
                                        } catch (WDDynamicRFCExecuteException ce) {
                                             manager.reportException(ce.getMessage(), false);
let said i key in the doc_num_frm as 5000002567 and doc_num_to as 5000002568,it seems that the stockitem.addZdocnum(docnum); only captur the last number which is 5000002568 for 2 times...it shd be 5000002567 and 5000002568..but now the data inside the stockitem for zdocnum is both oso 5000002568.. any idea why lead to this? thanks

Dear Joan,
Zdocnum docnum = new Zdocnum();
Write the above line of code within the for loop instead of outside as follows :
for(int x = 1; x <= c; x++){
Zdocnum docnum = new Zdocnum();
docnum.setMat_Doc(String.valueOf(a));
docnum.setDoc_Year(wdContext.currentContextElement().getYear());
stockitem.addZdocnum(docnum);
wdComponentAPI.getMessageManager().reportSuccess(docnum.getMat_Doc());
wdComponentAPI.getMessageManager().reportSuccess(docnum.getDoc_Year());
a = a+1;
What is going wrong is you are creating a reference of type ZDocnum, instantiating it, setting its values and adding it to the input list.
Next time when you set its values you are using the same reference without changing the instance it points to.
So a new element gets added no doubt but the values of the first element also get changed.
If you create a new instance every time you add an element to the list ,then this won't happen.
Try this and check.
Regards,
Mayuresh
PS : xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Edited by: Armin Reichert on Jan 1, 2008 3:50 PM

Using wildcard parameters for MDX and RSQL queries

Hi,
Passing parameters to MDX and RSQL queries works,but is there a way we can pass wildcard(%) parameters to MDX and RSQL
Thanks,
Hari Devarapalli

Hari -- Try this Instr function -
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.dwe.cubemdx.doc/mdx_instr.html
Thanks,
Venkat

RFC Lookup Table Parameters Reusability

Dear All
My Requirement is to Map fields in IDoc from the File data ,there are some fields in idoc for which i need to fetch data from SAP.
For this i am using RFC Look up. i am retrieving values from table parameters for RFC.
and this Table parameters are being used muliple times in Mapping.
Right now i have to execute the same RFC for set of input data atleast 5 r 6 times.
This is effective Performance of the Interface
Is there any concept of Reusuability in RFC Lookup while Mapping in PI.?
Can we use Java Initialization section in mapping for executing the RFC once and using the output data in table parameters while mapping various target fields.
Hoping for a Positive Reply
Regards
Bhasker

Hi,
1) If it is PI 7.1 there are mapping enhancements, such as
a) Variables for storing intermediate mapping value,
b) for RFC lookup etc.
you can find the 7.1 pdfs from SDN
2) you can have a two stage mapping, putting them sequentially in Interface mapping object.
First step : Source to Target (orignal target structure)
here you can do all the mapping and also One time RFC lookup, but leaving the other fields where you need the lookup values again
Second step : Target to Target
here already mapped target becomes your input & you know the fields which have the value & the fields that you need to map again and all other fields are one to one mapping.
Regards
Vishnu

New in NW04s: FL069 TABLES parameters are obsolete (in function modules)

Can somebody explain what is the fundamental reason for this behaviour in NW04s?
In Netweaver 2004s system (like ERP2005 ) you get a warning message in SE37:
FL069 TABLES parameters are obsolete! when defining quite ordinary tables parameter using LIKE and reference to a structure in ddic.
I now speak normal function modules, not RFC enabled.
This example of tables parameter definition will cause the warning message:
return LIKE BAPIRET2
I of course looked the additional help provided by this message FL069. I understood it as following:
you should stop using TABLES parameter and more often use CHANGING parameter by referring a TABLE TYPE defined in dictionary.
if using CHANGING parameter and still want to pass the header line of your internal table you should use a separate parameter (EXPORT or CHANGING parameter)
Developers have too much used TABLES parameters for passing internal tables for reading (by value) rather than to be modified (by reference). As a consequence, fm could have change the header line without caller to know it.
in my opinion the message help is missleadingly telling that header line is no longer passed to function module if TABLES parameter is used. I made a small test program and fm (with TABLES paramerer), and everything worked as before.
The warning message can be ignored by pressing Enter a few times and your fm with TABLES parameter works as it had in older versions of Netweaver.
SAP is still using a lot of TABLES parameters in their own function modules. For example SD_SALES_HEADER_MAINTAIN.
So what is the point of this warning message while everything still works as it used to be and SAP uses this same "OBSOLETE" feature itself? Is there anything more fundamental behind this message? Like TABLES paremeters will no longer work in future versions of ABAP (or header line passing will be ignored in future versions) and therefore developers should switch to CHANGING/EXPORT parameters with TABLE TYPES as soon as possible??
Please understand that I don't need any assistance how to avoid this message, just interested to share your opinions what is the purpose of this warning message.
That is why I did not marked this thread as a question.
Br: Kimmo

Hello,
This is the view under Tables tab in my function builder:
I_T_SELECT     TYPE     SRSC_S_IF_SIMPLE-T_SELECT
I_T_FIELDS     TYPE     SRSC_S_IF_SIMPLE-T_FIELDS
E_T_DATA     LIKE     SFLIGHT (which I change to YBWxxxx)
The moment I change to YBWxxxxx it gives me that error '"TABLES parameters are obsolete! "'
and unfortunately hitting enter several times is not helping either
Thanks!

How BAPI Tables parameters are passed by reference

Hi Gurus,
I have a genuine doubt regarding BAPI parameters. I would like to point out the genreal rules of bapi like,
1. BAPI parameters should be passed by value. (Because they are rfc fm's. So both systems will be in different servers. This is the normal scenario.)
2. But the tables parameters in BAPI can't be passed by value. Instead they are passed by reference.
3. I know they use some kind of delta mechanism to transfer tables parameters to remote servers.
So gurus I would like to know what exactly happens when a tables parameter is passed. And also I didn't understand the delta mechanism. Kindly guide me.
Thanks in advance,
Jerry Jerome

You'll see in [SAP Library - RFC - Parameter Handling in Remote Calls|http://help.sap.com/saphelp_nw04s/helpdata/en/22/042551488911d189490000e829fbbd/frameset.htm] that tables are not passed by reference when you use RFC. It also explains the delta.
When you make a remote function call, the system handles parameter transfer differently than it does with local calls.
TABLES parameters
The actual table is transferred, but not the table header. If a table parameter is not specified, an empty table is used in the called function.
The RFC uses a delta managing mechanism to minimize network load during parameter and result passing. Internal ABAP tables can be used as parameters for function module calls. When a function module is called locally, a parameter tables is transferred u201Cby reference". This means that you do not have to create a new local copy. RFC does not support transfer u201Cby referenceu201D. Therefore, the entire table must be transferred back and forth between the RFC client and the RFC server. When the RFC server receives the table entries, it creates a local copy of the internal table. Then only delta information is returned to the RFC client. This information is not returned to the RFC client every time a table operation occurs, however; instead, all collected delta information is passed on at once when the function returns to the client.
The first time a table is passed, it is given an object-ID and registered as a "virtual global table" in the calling system. This registration is kept alive as long as call-backs are possible between calling and called systems. Thus, if multiple call-backs occur, the change-log can be passed back and forth to update the local copy, but the table itself need only be copied once (the first time).

Regarding parameters in rfc

hi all,
can any one explain me why RFC does not support the u201Cby referenceu201D mechanism , as i want to pass table parameter to rfc how they wil be passed without u201Cby referenceu201D .
thanks in advance
dilip

When you make a remote function call, the system handles parameter transfer differently than it does with local calls.
TABLES parameters
The actual table is transferred, but not the table header. If a table parameter is not specified, an empty table is used in the called function. The RFC uses a delta managing mechanism to minimize network load during parameter and result passing. Internal ABAP tables can be used as parameters for function module calls. In a local function module call, a parameter table is passed on by reference, and no new local copy has to be created. RFC does not support the u201Cby referenceu201D mechanism, so the whole table has to be exchanged between the RFC client and the RFC server. When the RFC server receives the table entries, it creates a local copy of the internal table. Then only delta information is returned to the RFC client. This information is not returned to the RFC client every time a table operation occurs, however; instead, all collected delta information is passed on at once when the function
returns to the client.
The first time a table is passed, it is given an object-ID and registered as a "virtual global table" in the calling system. This registration is kept alive as long as call-backs are possible between calling and called systems. Thus, if multiple call-backs occur, the change-log can be passed back and forth to update the local copy, but the table itself need only be copied once (the first time).

Using tables parameters for RFC

Similar Messages

Maybe you are looking for