Error in calling the Remote Function Module

Hi all,
I am trying to call the Remote function Module which is in CRM from ECC .
But we are not able to detect the function module as it is showing the error as Function Module not found.
Can anybody help us in calling the Remote Function Module .
Regards,
Madhavi

Please check the foll 2 things :
RFC radio button clicked in se37 for that FM
RFC connection established with the remote server in SM59
Thanks

Similar Messages

Error while calling the Mapping function module for BW Extraction

Hi
iam getting runtime error while calling the BW mapping function
The error description is as shown below.
Runtime Errors CALL_FUNCTION_UC_STRUCT
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Short text
 Type conflict during structure parameter transfer at CALL FUNCTION.
What happened?
 Error in the ABAP Application Program
 The current ABAP program "GP466CV1Y7W2VML1PJ3VB80KDOP" had to be terminated
 because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
 not caught in
 procedure "CALL_MAPPING_FUNCTION" "(FORM)", nor was it propagated by a RAISING
 clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 In the function "CMS_CB_BW_MAP", the STRUCTURE parameter "EXTRACT_DATA" is
 typed in such a way
 that only actual parameters are allowed, which are compatible in Unicode
 with respect to the fragment view. However, the specified actual
 parameter " " has an incompatible fragment view.
I am passing the EXTRACT_DATA parameter as specification LIKE with the associated type - corresponding structure
Please let me know how can i resolve this issue
Regards
Leon

Dear benarji ,
I'm having the same problem help me to correct . I have mentioned below as what error i got.
Runtime Errors CALL_FUNCTION_UC_STRUCT
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Short text
 Type conflict during structure parameter transfer at CALL FUNCTION.
What happened?
 Error in the ABAP Application Program
 The current ABAP program "ZDLROUTSTANDING_COPY" had to be terminated because it
 has
 come across a statement that unfortunately cannot be executed.
Error analysis
 An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was
 not caught in
 procedure "PDF" "(FORM)", nor was it propagated by a RAISING clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 In the function "/1BCDWB/SF00000080", the STRUCTURE parameter "IT_WORKS_SF" is
 typed in such a way
 that only actual parameters are allowed, which are compatible in Unicode
 with respect to the fragment view. However, the specified actual
 parameter "SFTWORKS" has an incompatible fragment view.
Missing RAISING Clause in Interface
 Program ZDLROUTSTANDING_COPY
 Include ZDLROUTSTANDING_COPY
 Row 876
 Module type (FORM)
 Module Name PDF
Trigger Location of Exception
 Program ZDLROUTSTANDING_COPY
 Include ZDLROUTSTANDING_COPY
 Row 894
 Module type (FORM)
 Module Name PDF
Source Code Extract
Line SourceCde
864 ** i_logo = 'ENJOYSAP_LOGO'
865 * IT_LIST_COMMENTARY = I_LIST_COMMENTS1.
866
867 ENDFORM. "alv_top_of_page1
868 *&---------------------------------------------------------------------*
869 *& Form PDF
870 *&---------------------------------------------------------------------*
871 * text
872 *----------------------------------------------------------------------*
873 * --> p1 text
874 * <-- p2 text
875 *----------------------------------------------------------------------*
876 FORM pdf .
877
878 * *** Smartforms & PDF ***
879
880 ssfctrlop-no_dialog = 'X'.
881 ssfctrlop-preview = 'X'.
882 ssfctrlop-getotf = 'X'.
883 ssfcompop-tddest = 'ERP7'.
884 DATA : mcheck LIKE sy-subrc.
885 CLEAR : fm_name.
886
887 "Get Function module name for given smartform
888 CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
889 EXPORTING
890 formname = 'ZSFDLOS1'
891 IMPORTING
892 fm_name = fm_name.
893
>>>> CALL FUNCTION fm_name
895 EXPORTING
896 control_parameters = ssfctrlop
897 output_options = ssfcompop
898 mrefno = mrefno
899 * P_TITLE = MTITLE
900 IMPORTING
901 document_output_info = st_document_output_info
902 job_output_info = st_job_output_info " IT_OTF_DATA
903 job_output_options = st_job_output_options
904 TABLES
905 it_works_sf = sftworks
906 EXCEPTIONS
907 formatting_error = 1
908 internal_error = 2
909 send_error = 3
910 user_canceled = 4
911 OTHERS = 5.
912
913 IF sy-subrc NE 0.
Advance Thanks

Regarding the Remote Function Module

hi,
Can any body can provide the brief information regarding the Remote Function Module.
1)How to create the remote function module
2)how it differ from the normal function module
3)any special features about this.
Thanks in advance

Hi
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
Reward points for useful Answers
Regards
Anji

Formal error: Invalid calling sequence for function modules

Hi All,
I have developed a function module for FQEVENT 620 Payment: Transfer Line Items for Clearing.
The clearing works fine.
After clearing the open items i need to post an FI-CA Document(BAPI : BAPI_CTRACDOCUMENT_CREATE) for each open item(cleared item)
I have used the bapi : BAPI_CTRACDOCUMENT_CREATE in the same function module that i have developed for FQEVENT 620 Payment: Transfer Line Items for Clearing.Here i am getting an error "Formal error: Invalid calling sequence for function modules".
So please let me know where i can use this bapi to post fi-ca document.Is there a BAdi or Enhancement Spot where i can use this BAPI or tell me what should i do to overcome this error.
Regards
Venkat

Venkat:
While I am confused about your business process - creating an open item when clearing one seems strange. Look into event 0020 which is called after documents are posted - it may present the opportunity to post process additional documents.
regards,
bill.

Where should i call the rfc function module? in xi or in r/3

where should i call the rfc function module?
for the synch scenario: file < -- > xi <---> rfc
i know the type of rfc is tcp/ip; but i'm not sure with the followings,
and with some trials i can not even see any message via rwb even all the setting
can be activated without errors.
where should i create the rfc destination? in r/3 or xi
where should i call the rfc via abap program? in r/3 or xi
i guess the calling program should belong to the different server with the rfc itself....
so confused....
Thanks for your reply!!
Jun

if i create the destination in xi point to r/3, then i call the rfc use the destination in r/3 right ?
The call doesnt use the destination in R3. XI has the RFC destination which is just used to connect to the R3 system
but where i need to create the fm via se37? in xi or r/3 ?
In R3
Regards,
Prateek

Debuggin a Call to Remote Function Module

Hi
I have a scenario where i have a Remote Function Module in r3 which is being called synchronously by an external java application. The FM has a lot of input and output parameters and many tables. The output returned by the FM is not as expected.
Can anyone tell me how debug a Remote Function Module when a call has been made from an external application.
I am not able to get the test data sent by the external application . So when the external application gives a call to this Remote FM and if it is possibele to debug it would be great.
regards
Nilesh Taunk.

Hi Nilesh,
1) Login to SAP with the same ID with which you will calling the RFC function module from the outside system.
2) Goto transaction - se37/se38
3) Goto Utilities => Settings.
4) Select the ABAP Editor Tab.
5) Click on the Debugging tab.
6) Tick the Actv. button and give the user name with which you will be debugging the code. In this case the logged in user id.
7) Press Enter.
8) Now put an external break point inside the Function Module.
9) Load your external application (from where you want to debug the FM) once again.
The execution will stop in the FM.
Hope it helps..
Lokesh
PS: This was a simple question, but I guess the reason no one has answered your question is due to the fact that you havent rewarded points to members helping you. Also remember to close your post once it has been answered.

Error while determining the form function module

Hi everyone,
We are experiencing problems while displaying one adobe form in ESS. Its the Travel Expense form (PTRV_EXPENSE_FORM). When pressing the button to Display/Print the form we get an error message: "Error while determining the form function module", and no form I shown. The ADS server is configured correctly and there are other forms that are actually working, for example the Travel Request form. We are running WAS 7.0 with SP12.
Anyone has an idea what can cause the problem? Any help is greatly appreciated.
Thanks in advance!
Regards,
Sophie

Viktor,
Thank you for your answer, it solved our problem!
Regards,
Sophie

Travel Display Form: Error while determining the form function module

Hi,
In Travel Reqeust (ECC6/ESS) when i click the Display Form after raising the Travel Request it shows the error
"Error while determining the form function module"
Can anyone have idea on this?
Regards,
Boobalan

Hi,
This error was due to Not supported platforms of ADS (Adobe Document services)
It was not supported on itanium64 bit processors.
Please check where the ADS is supported in service.sap.com/pam
You can use the ADS in the Non-Supported Server by linking it to Supported Platform Server using the SM59 link. This will make the ADS files to work.
Please refer the ADS Config Doc for details.
Hope you also solve this problem.
Regards,
Boobalan

RFC Error While Invoking A Remote Function Module.

I am invoking A remote function module while invoking it get an exception when i see the error logs
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Screen output without connection to user. , error key: RFC_ERROR_SYSTEM_FAILURE at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101) at... [see details]
can anyone pls tell me what the error is..
regards
Nilesh Taunk.

Hi Nilesh Taunk,
You can go through the following steps
-o JCO Exceptions 1. http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
-o JCO Exceptions 2. http://help.sap.com/saphelp_nw04/helpdata/en/f6/e002416225f023e10000000a155106/frameset.htm
-o Restart of the J2EE instance and try re-importing the RFC model. Sometimes it helps.
-o Logon into WebDynpro Content Administrator as a J2EE Admin and check if the JCO Connections and User /pwd of your application is correct. You can ping or test your JCO connections. if something is wrong, enter the values again for JCO n retest them.
-o Try undeploying or removing the complete application and redeploy it.
Tu undeploy please go to
Go to Visual Admin -> Server -> Services -> Deploy ->

Under Runtime Tab
select the server, open the tree , you would find the webdypro list there.
Now select an application, first stop it, remove it and redeploy if necessary.
Let us know if you could solve the problem or not, gud luck!
Rgds,
Sreenivas.

Error while Testing the Inbound Function Module

Hi,
I have created a Z Function Module (Posting Program) for Testing the EDI Shipment Tender Status. When I try to process the IDoc with the Transaction WE19 and when I enter the name of the Z function Module , it gives me an error saying that "Interface for Function Zxxxx is incorrect". Can somebody give me a solution for this? Answer would attract reward points.
Thanks,
Venkat.

Hi,
You need to register this Function Module against Message Type.
Transaction code is : WE57.
Nilesh

'Control parameters' when call the smartform function module

Hi all,
I want to know what we have to export as value to control papameter while calling the fm of smartform.
Plz also let me know the various parameters in CONVERT_OTF.
Thanks in advance.

WA_CONTROL_PARAMETERS-GETOTF    = 'X'.
the above is needed if you want OTF data, to convert it to PDF
    WA_CONTROL_PARAMETERS-LANGU = 'E'.
Language of smartform
    WA_CONTROL_PARAMETERS-DEVICE = 'PRINTER'.
*default o/p device
    WA_CONTROL_PARAMETERS-NO_DIALOG = 'X'.
if you dont want the pop up screen , that asks you for printing make the value as 'X' .
other wise make it as space or clear it.
    WA_CONTROL_PARAMETERS-PREVIEW = SPACE.
if u want the print preview , make it as 'X' , otherwise SPACE
Below code shows how you can convert the OTF data to PDF data.
calling the smartform.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      FORMNAME           = 'Z_SMARTFORM'
    IMPORTING
      FM_NAME            = WF_FUNCMODULENAME
    EXCEPTIONS
      NO_FORM            = 1
      NO_FUNCTION_MODULE = 2
      OTHERS             = 3.
CALL FUNCTION WF_FUNCMODULENAME
      EXPORTING
        CONTROL_PARAMETERS   = WA_CONTROL_PARAMETERS "Control Params
        OUTPUT_OPTIONS       = WA_OUTPUT_OPT "Output Options
        WF_CARRID            = WF_CARRID
        WF_CONNID            = WF_CONNID
        WF_FLDATE            = WF_FLDATE
      IMPORTING
        DOCUMENT_OUTPUT_INFO = WA_DOCUMENT_OUTPUT_INFO
        JOB_OUTPUT_INFO      = WA_JOB_OUTPUT_INFO
        JOB_OUTPUT_OPTIONS   = WA_JOB_OUTPUT_OPTIONS
      EXCEPTIONS
        FORMATTING_ERROR     = 1
        INTERNAL_ERROR       = 2
        SEND_ERROR           = 3
        USER_CANCELED        = 4
        OTHERS               = 5.
      CALL FUNCTION 'CONVERT_OTF_2_PDF'
        EXPORTING
          ARCHIVE_INDEX          = WA_ARC_IDX
        IMPORTING
          BIN_FILESIZE           = WF_NUMBYTES
        TABLES
          OTF                    = WA_JOB_OUTPUT_INFO-OTFDATA[]
          DOCTAB_ARCHIVE         = TB_DOCTAB_ARCHIVE[]
          LINES                  = TB_LINES[]
        EXCEPTIONS
          ERR_CONV_NOT_POSSIBLE = 1
          ERR_OTF_MC_NOENDMARKER = 2
          OTHERS                 = 3.

RFC remote function module call from XI

hi
I am trying to call a remote function module directly from XI which is not a bespoke module.
And i am getting the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.
Please help me in this.
Thanks in advance.

Hi Naina,
Normally RFC are synchronous, they do have return parameter as export parameter.
If return parameter is missing then , you can create Wrapper RFC.
Wrapper RFC:
It is nothing but you just create BAPI in SE37 transaction with Return parameter as export parameter and make it remote enabled by clicking on Radio button.
Under source code, CALL BAPI which XI has to call.
Thats it!
I hope this helps.
Let me know if any help required.

How to debug a remote function module in calling system? Help!

Hi Experts,
 I have a ABAP report (in System A) from where I am calling a remote function module which exists in a different system B.
ABAP Program(System A)<----calls--
RFC(System B)
Can I debug the RFC funnction module in system A using ABAP debugger? In other words if i put a breakpoint on the "call function" statement then in debug mode I want to see that the control is going to system B and I should be able to process the FM code line by line. Is this possible?
Is there any special transaction or settings?
Is there any alternative?
Please help
Thanks
Gopal

hello,
Try this method.
first check whether RFC connection is working b/w 2 systems.
if connection is working, then do like this.
In System B , put endless loop in FM before some main select statement.
like
DATA : v_a TYPE c VALUE space
DO .
 IF v_a = 'X'.
 EXIT.
 ENDIF.
ENDDO.
the above code will be endleep loop.
In system A, when cursor goes to CALL FUNCTION DESTINATION 'XXXXX'.
u shud be logged in system B. the moment control comes to system B.goto tcode SM50 . check ur username . choose that particular checkbox then in menu bar --> program/session --> Program --> Debugging.
i hope it will help u.
try & let us know.
Thanks,
Manjunath MS

Remote function module to wait untill the response came from webmethods

hi all.
here i have got a situation that the remote function module created in SAP-R/3 to wait untill the response came from webmethods :
i have created the remote function module by assigning one structure in tables(tab) and 3 parameters in changing tab just to collect the messages return from webmethods
so this rfc will be called by webmethods and pick the structure data and then it wll return 3 variables back to rfc.
here the rfc need to wait untill the response came from webmethods.
so can any body suggest me on what source code do i need to write in RFC

Hi Naina,
Normally RFC are synchronous, they do have return parameter as export parameter.
If return parameter is missing then , you can create Wrapper RFC.
Wrapper RFC:
It is nothing but you just create BAPI in SE37 transaction with Return parameter as export parameter and make it remote enabled by clicking on Radio button.
Under source code, CALL BAPI which XI has to call.
Thats it!
I hope this helps.
Let me know if any help required.

Remote Function module to wait for the response.

Hi .
i just created the remote function module to call the webmethod by putting the parameters in tables (tab) for webmethods to pick the data from RFC and parameters in changing (tab) to collect the reponse from webmethods ,i just want to know if this is the right way of creating the RFC for webmethods and the RFC need to wait for certain time until it should get the response from webmethods.
can any body guide me in this on how i can make the rfc to wait untill it will get the response from webmethods.
waiting for your response.
regards.
Varma

Hi Jaswanth,
FM used to upload the data from the non sap system to the SAP sytem is the GUI_UPLOAD ans GUI_DOWLOAD is downloading the data from SAP to the presentation server .This file can be xls,tab or space deliminatior ettxt fiel.
I think this was your requirement.
Pooja

Error in calling the Remote Function Module

Similar Messages

Maybe you are looking for