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

Similar Messages

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

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>

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

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!

Getting metadata for RFCs using RFC SDK (with position of parameters)

Hi!
I'm currently using the RFC SDK Function "RfcGetFunctionInfoAsTable" to retrieve metadata for RFCs from SAP. What i see is that the "Position" field in the RFC_FIELDS_U structure contains arbitrary values, and so I am not able to determine what is the actual ordering of the parameters.
What can I do to determine the exact ordering of the parameters of an RFC? (ordering as in - I want to obtain the parameters in the same order as they appear in SAP GUI).
Thanks,
Mustansir

Hi,
I think you can use the code similar to the one below...
some of the things not covered in this are
1. all types for which   CALL FUNCTION 'RFC_GET_NAMETAB' is not returning result, you can call CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION' directly. I have not covered that in this code. Hope this is helps in resolving your issue.
Also, the code is not optimized. So there is some scope for optimization of this code.
REPORT ZTEST_GET_SREUCTURE.
DATA : PARAMS     type table of     RFC_FUNINT,
      ls_params like line of params.
data: NAMETAB     type table of     X031L,
      ls_NAMETAB like line of NAMETAB.
data: FIELDS type table of RFC_FIELDS,
      ls_fields like line of fields.
CALL FUNCTION 'RFC_GET_FUNCTION_INTERFACE'
EXPORTING
    FUNCNAME                      = 'fm_test_fm'
TABLES
    PARAMS                        = PARAMS
IF SY-SUBRC <> 0.
ENDIF.
loop at params into ls_params.
CALL FUNCTION 'RFC_GET_NAMETAB'
    EXPORTING
      TABNAME                     = LS_PARAMS-TABNAME
    TABLES
      NAMETAB                     = NAMETAB
IF SY-SUBRC <> 0.
ENDIF.
loop at NAMETAB into ls_NAMETAB.
    CALL FUNCTION 'RFC_GET_STRUCTURE_DEFINITION'
EXPORTING
    TABNAME                     = LS_NAMETAB-ROLLNAME
TABLES
    FIELDS                      = FIELDS
    loop at fields into ls_fields.
      write: ls_fields-FIELDNAME.
    endloop.
endloop.
endloop.

RFC Lookup - BAPI-TABLE Parameters problem

Hello All,
I had a scenario where i need to export parameters and am supposed to get import parameters from BAPI between source and target structures.
like -
source --> BAPI execution = result --> target
We had succeeded in getting those but the only problem is with TABLE parameters in that BAPI.
How can we achieve it.
Faster reply would be appreciated.
Thanks & regards
Reddy

Hi VJ,
Its not a simple source-target mapping .
For Ex :
Source-Bapi-Idoc
Source will send some parameters to BAPI and bapi will execute it and respond with values in table parameter of the bapi and result would be assigned to idoc-field.
For this i am using RFC Look up with sample code as :
String rfcxml ="<ns0:Z_BAPI xmlns:ns0=\"urn:sap-com:document:sap:rfc:functions\">" +
"     <A>" + A + "</A>" +       --- Export parameters
"     <B>" + B + "</B>" +       --- Export parameters
//"                       <TABLE><FIELD1>" + FIELD2 + "</FIELD1></TABLE>" +
//"                       <TABLE><FIELD2>" + FIELD2 + "</FIELD2></TABLE>" +
//"                       <TABLE><FIELD3>" + KDMAT+ "</FIELD3></TABLE>" +
//          "<FIELD1>" + FIELD1 + "</FIELD1>" +
"</ns0:Z_BAPI> " ;
Passing A & B as export parameters and getting TABLE-FIELD1&2&3 as response.
I hope some problem in the syntax.
Regards,
HP

RFC Tables Parameters

Hello all
I am having performance issues relating to an RFC call between CRM and ECC. I have been asked to get an RFC call between the two working as quickly as possible.
The code is as optimised as possible, I have replaced onerous FM calls with bespoke code and optimised select statements.
But for some reason I have a niggling thought in the back of my mind that no tables should be passed to the RFC FM in the IMPORTING parameters section and should be passed as TABLES parameters only.
Does anyone know if this is true or not. I have found OSS note 888777 which says that this is true in relation to ABAP-JAVA comms but it doesn't say whether this is the case in ABAP-ABAP.
Any advice/comments most welcome.

Just the once.
The signature of the FM is:
*" IMPORTING
*"     VALUE(I_FIELD1) TYPE ANYFIELD OPTIONAL
*"     VALUE(IT_TAB1) TYPE ANYTABLE
*"     VALUE(I_FIELD2) TYPE ANYFIELD OPTIONAL
*"     VALUE(I_FIELD3) TYPE ANYFIELD OPTIONAL
*"     VALUE(IT_TAB2) TYPE ANYTABLE OPTIONAL
*" EXPORTING
*"     VALUE(EV_RETURN) TYPE BAPIRET2
*" TABLES
*"      IT_TAB3 STRUCTURE ANYTABLE
I'm just wondering whether removing the IT_TAB1 and IT_TAB2 parameters from the IMPORTING section and placing them in the TABLES section would have any performance improvements.

In BAPI's why the structures are used in table parameters?

Hello sir,
what is BAPI sir? In BAPI's why the structures are used in table parameters? table parameters they are using structures but not using any customized tables ?
regards
rachu.

Hello Rachu
BAPIs provide RFC-enabled interfaces to SAP business objects (e.g. like customer, sales order, purchase order, etc.).
A BAPI does basically the same like you would need to do calling the corresponding transaction (e.g. BAPI_SALESORDER_CREATE -> VA01).
Since they are RFC-enabled they can be called from external systems.
BAPIs represent an external interface for the outside world. Very often you will find within the BAPI that there is a mapping done to the (SAP-)internal structures at the beginning of the coding and vice versa at the end of the coding. Thus, you will (almost) never find any DB table name used as type of a BAPI TABLES parameter.
Regards
Uwe

RFC destination for RFC to File scenario

Hi,
I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
Step 1:
For this a Registered server program is created in Jco RFc Destinations with,
Program Id : pgm1
Gateway host : PI's host
Gateway service : PI's service
application server host: ECC's host
system numer     : ECC's number
client : ECC's client
logon user : ECC user
password : pwd
Step 2:
In SM59, TCP/IP connection the following parameters are given:
Program ID : pgm1
Gateway host : PI's host       -
> is this correct
Gateway service : PI's service      -
> is this correct
Step 3:
So i am calling the RFC in ABAP program (R/3 system) like:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
Step 4:
In PI side,
for RFC sender I am passing :
Application server : PI server
Application server service: PI host
program ID: pgm1 which was created in the previos step
For RFC Metadata Repository Parameter, i am passing all the values related to R/3
Please let me know whether the steps and values i given is correct.
B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
so i am confused as which is the correct method. pls clarify

Ok I will try to explain....
Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
    comp_detail = company_detail.
COMMIT WORK.
Regards,
Sarvesh

Problem passing a table parameter in rfc call using the function control

I try to pass a Table as parameter to a Function Module using the SAP.Functions library (part of SAP frontend controls) from a Visual Basic (VBA) program.
The function module has been verified to work when invoked from SAP FrontEnd Function Builder.
The SAP RFC Control is created with
Set sapFunctions=CreateObject("SAP.Functions")
Following code snippet shows how I attempt to set exports and add a table row before calling the function module:
sapFunctions.Connection = sapConnection
Set sapMaterialUpd = sapFunctions.Add("Z_SD_BAPI_SALES_DATA_UPD")
With sapMaterialUpd
<i>'set exports</i>
     .Exports("PA_GLPUPDLEVEL") = "S"
     .Exports("PA_VKORG") = "FI14"
<i>'append table row</i>
     .Tables("IT_SALES_DATA_UPD").AppendRow
     .Tables("IT_SALES_DATA_UPD")(1, "VKORG") = "FI14"
     .Tables("IT_SALES_DATA_UPD")(1, "MATNR") = "W_3100"
     .Tables("IT_SALES_DATA_UPD")(1, "DATBI") = "99991231"
     .Tables("IT_SALES_DATA_UPD")(1, "DATAB") = "20041231"
     .Tables("IT_SALES_DATA_UPD")(1, "KBETR") = "2222"
     .Tables("IT_SALES_DATA_UPD")(1, "KONWA") = "EUR"
End With
<i>'call the function module</i>
If sapMaterialUpd.Call() = True Then
    <i>'do something with the return tables here...</i>Else
    Debug.Print sapMaterialUpd.Exception
End If
The Call() returns <b>FALSE</b> and the exception is <b>"SYSTEM_FAILURE"</b>. The connection also resets.
The local logfile that the control generates shows that an exception occurs at the point of the call:
<i>10.02.2005 17:54:20.766 Packing Parameters for Z_SD_BAPI_SALES_DATA_UPD
Packing Parameter PA_GLPUPDLEVEL.
Packing Parameter PA_VKORG.
Packing Table 0.
Packing Table 1.
10.02.2005 17:54:20.766 *** Calling RFC Function 'Z_SD_BAPI_SALES_DATA_UPD'
10.02.2005 17:54:20.986 RFC CALL status = RFC_SYS_EXCEPTION
10.02.2005 17:54:20.986 RFC Error: RFC_IO27
-Status:CODE=CM_DEALLOCATED_NORMAL STATUS=CM_NO_STATUS_RECEIVED DATA=CM_COMPLETE_DATA_RECEIVED ID=69415076
-Message:connection closed
-Internal Status:IO HANDLE=23 DRV=EXT LINE=1420 CODE=27 : GET ID=ffff LINE=861 CODE=7
10.02.2005 17:54:20.986 Function call finished.</i>
Seen next code snippet. If the Table object is not touched, the function call goes through without any problems:
sapFunctions.Connection = sapConnection
Set sapMaterialUpd = sapFunctions.Add("Z_SD_BAPI_SALES_DATA_UPD")
With sapMaterialUpd
'set exports
    .Exports("PA_GLPUPDLEVEL") = "S"
    .Exports("PA_VKORG") = "FI14"
    'do <b>not</b> append a table row, for testing only ;-)</b>
End With
<i>'call the function module</i>
If sapMaterialUpd.Call() = True Then
<i>    'do something with the return tables here...</i>
Else
    Debug.Print sapMaterialUpd.Exception
End If
This code works perfectly when calling the function. It returns TRUE and behaves normally. The function module returns descriptive response text in a table telling that the table was empty, according to the BAPI implementation.
So is there something special needed here <i>after</i> appending the table row and <i>before</i> making the Call to properly attach the table as a parameter for the function module?
Can this be a bug in the SAP RFC Control? The version of the wdtfuncs.ocx is 6206.6.45.54.
Any hints are welcome!

hi All partner,
who solved this problem , I meet it too and
can't clear it.
SAPfunc := sapfunctions1.Add('z_get_sfcs_dn_mo');
SAPitab := sapfunc.tables.item ('I_DNMO');
SAPitab.appendrow;                                       SAPitab.value(1,'MANDT') := '220';
SAPitab.Value(1,'VBELN') := '2150000001';
SAPitab.Value(1,'POSNR') := '50';
SAPitab.value(1,'MATNR') := '19-99999-00';
SAPitab.value(1,'AUFNR') := '921241512001';
SAPitab.value(1,'DEDAT') := '2005/09/09';
SAPitab.value(1,'LFIMG') := '100';
IF SAPfunc.call = true then
begin
end
else
    begin
    showmessage('call fail!!') ;
    end;
end;
RFC source code as below
FUNCTION z_get_sfcs_dn_mo.
""Local interface:
*" TABLES
*"      I_DNMO STRUCTURE ZDN_MO
data: wa type zdn_mo.
LOOP AT i_dnmo.
    wa-mandt = i_dnmo-mandt.
    wa-vbeln = i_dnmo-vbeln.
    wa-posnr = i_dnmo-posnr.
    wa-matnr = i_dnmo-matnr.
    wa-aufnr = i_dnmo-aufnr.
    wa-dedat = i_dnmo-dedat.
    wa-lfimg = i_dnmo-lfimg.
   modify zdn_mo from wa.
    insert into zdn_mo values wa. --dump at here
    commit work.
ENDLOOP.
T/C: ST22 error message say at
insert into zdn_mo values wa. ---dump at here
the sapfunc.call returns fail.
Message was edited by: jorry wang

Problem with passing table values to RFC

Hi all,
I am passing values in table in RFC. There are no import/export parameters in RFC. We are passing only tables.
There are two tables in the RFC I_Dept and I_Subdept. Initially RFC is executed for getting the Dept which works fine as for this there is no need to set in input table value. But to get sub department I need to set the dept in I_Dept and after executing RFC I should get values in table I_Subdept. The code is as below:
wdContext.nodeOutput_I_Dept().invalidate();
wdContext.nodeOutput_I_Subdept().invalidate();
Z_Bapi_Dept_Values_Input d_Input = new Z_Bapi_Dept_Values_Input();
wdContext.nodeZ_Bapi_Dept_Values_Input().bind(d_Input);
Zdept dept = new Zdept();
dept.setZname("Sales");
d_Input.addI_Dept(dept);
try
wdContext.nodeZ_Bapi_Dept_Values_Input().currentZ_Bapi_Dept_Values_InputElement().modelObject().execute();
wdContext.nodeZ_Bapi_Dept_Values_Input().nodeOutput().invalidate();
catch (WDDynamicRFCExecuteException e)
msgManager.reportException(e.toString(), true);
Is anything wrong in this code because even after executing the RFC the size of node I_Subdept() is zero. But the RFC works fine in the backend.
Regards,
Jaydeep

A typical misunderstanding when populating structured input data
via code is the following:
- You have bound a WD context node hierarchy to the model say
N1         >         M1
->N2       >         ->M2
                                                                                where N1, N2 are WD Context nodes (N2 is child of N1) and M1, M2 are
model classes bound to the context nodes. Important: M1 has a relation
to M2 on the model side, means there is some method M1.setMyM2(M2)
(assuming the target role of the relation is called "MyM2").
- You create context elements for N1 and N2 which are bound to a model
class instances of M1 and M2 respectively.
Assuming that M1 is the "executable" model class (*_Input) and M2
represents an input structure needed, the M2-input will - using the
above approach - not be available on execution. Why? The relation on the
model side (MyM2) is not available if just maintaining it via the
context, i.e. context and model are not "in sync". As RFC execution is
done via the model the M2 input will not be available.
You best create complex/nested input structures on the model
side and then bind the top-level model object to the resp context node.
In the above sample this would be:
M1 m1ModelObject = new M1();
M2 m2ModelObject = new M2();
m1ModelObject.setMyM2(m2ModelObject);
Hope it helps!
Regards,
Sangeeta

ABAP Table Type in RFC Callable Object in GP

Hi Experts,
I have created a RFC in ABAP that has as one of its export parameters a table type. I am trying to call this RFC in my GP process. So I created the external service callable object as required. However, when I look at the output parameters for the callable object, the table type is not shown as a list (the is list column is not checked for this parameter).
Do you know if ABAP table types is supported/recognized by GP as a list? or is this a limitation?
Any help is welcomed!
Thanks in advance.
Robert

Hi Aneel,
You can try the following:
e.g.
for j = 1 to ActiveCell.SpecialCells(11).Column
oParam4.Rows.Add
if j=1 then oParam4.Value(j, "NAME") = ActiveSheet.Cells(1,j).Value
if j=2 then oParam4.Value(j, "TYPE") = ActiveSheet.Cells(1,j).Value
if j=3 then oParam4.Value(j, "NUMB") = ActiveSheet.Cells(1,j).Value
next j
Regards,
ScriptMan

Passing parameters to RFC iview

Hi
Can anyone let me know how to pass parameters to RFC iview ?
i want to pass the parameter through URL to the RFC iview (funtion_params_name1)
thanks

Hi Thanks for your reply. I have a RFC function module that accepts two input parameters, queries R3 database and returns table output. Need to create a Portal page for the end users out of those returned data. Your help is much appreciated!.
Hi
Well it is possible
try this....
Create a abap webdynpro application, here you can call the RFC function module as a supply function
get the data from the function module and display it on the webdynpro view
convert this webdynpro to a iview and attach this iview to the portal page.( this is just a few steps process)
thanks

Table parameters for RFC FM.

Similar Messages

Maybe you are looking for