Error when creating rfc function module

Hi,
now i am creating one rfc functionmodule (ZSUSR_USER_AGR_ACTIVITYGR_GET) by copying existing general standard functionmodule. problem is, in tables i have one parameter called USER_ACTIVITYGROUPS i referred this one with TYPE-POOLS TYPE ZUSTY_T_AGR, when i am trying to save this function module it is giving this message <i><b>Type zusty_t_agr is unknown.</b></i>
it is very urgent
Please help me

Hi,
Check this link. It has got all the information about RFC.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards

Similar Messages

Error when call RFC Function module in R/3

Dear All,
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
we are facing the error "Error while lookup Exception during processing the payload. Error when calling an adapter by using the communication channel CC_PPPI_MES_RFC_Rcvr (Party: , Service: WCD_320, Object ID: 16563889b449328eac76caa6a3bc592e) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'."
This is the first time we are doing this configuration.
Could you please let me know what woulbe the reason.

read the original message
We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
I am talking about the above Receiver RFC channel which you guys are using to call R/3 from XI. That where you need to change the commit parameter

I need to create RFC function module which creates the IDOC

Hi-
Any idea how to create RFC function module which creates the outbound IDOC. If you have any sample code please forward to me.
Thanks,
Sony

My Problem is
Whenever they create Invoice using T-code's like FV65(Parked Document), automatically should create IDOC's...
I have used message type FIDCC1 but this message type is usefull only for Posting documents.
1. Whenever they create parked document, entries will be stored in BKPF(Parked Document-Filed-BKPF-BSTAT = 'V') and Bseg....
2. I have to read entries from those tables and should create IDOC...
3. I checked FM's(FI_IDOC_CREATE_FIDCC1, FI_IDOC_PREPARE) but are not useful...
4. Now I need to write one RFC function module and that FM should create the IDOC's....
Can anyone please help me out?
Thanks,
Sony

How to create RFC function module and how to call this function module

Hi,
i want to know step for creating RFC function module and then How to use this function module from some other sap system.
Thnaks,
jigar

Jigar,
To implement a remote function module in ABAP, perform the following steps:
Register the module as remotely callable in the RFC server system.
In the function module Administration screen (transaction code SE37), set the field Can be called via REMOTE CALL. Registering a module as remote causes an RFC stub to be generated for it.
Write the code for the function module.
Create the destinations.....................
Displaying, Maintaining and Testing Destinations
To display, create or modify destinations, choose Tools ® Administration ® Administration ® Network ® RFC destinations or enter transaction code SM59.
Remote Destinations are stored in table RFCDES. The RFCDES table describes logical destinations for remote function calls.
It is not possible to maintain the RFCDES table directly.
You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® AcceleratedSAP ® Customizing ® Execute Project ® SAP Reference IMG.
In the Implementation Guide, expand the following hierarchy structure:
Basis
Application Link Enabling (ALE)
Sending and Receiving Systems
Systems in Network
Define Target Systems for RFC Calls
Displaying Destinations
The initial screen for this transaction displays a tree:
Different connection types (i.e. partner systems or programs) are possible. For further information, see Types of Destinations.
To display all information for a given destination, double-click it, or place the cursor on it and press F2 .
To search for a destination, press the Find button and specify your selection. You get a list of all entries matching your selection. Place the cursor on the one you want, and press F2 or simply double-click the destination. All information for the given entry appears.
Creating Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
All available connection types are explained in Types of Destinations.
To create a new RFC destination, press the Create button. A new screen is displayed with empty fields for you to fill in.
If you want to create a new destination
As you create a remote destination, you can specify a particular application server or a group of servers for a balanced distribution of system load.
For details of the destination parameters, see Entering Destination Parameters.
Changing Existing Destinations
On the destinations overview screen (transaction code SM59), the connection types and all existing destinations are displayed in a tree structure.
You can display all information for a given destination by double-clicking it or pressing F2 on it.
To change an existing destination, double-click it, or place the cursor on it and press the Change button.
For details of the destination parameters, see Entering Destination Parameters.
Testing Destinations
To test a destination, choose the appropriate function from the Test menu.
Connection (also available via the Test connection pushbutton)
Authorization (checks logon data)
Local network (provides a list of application servers)
You can use the CALL FUNCTION statement to call remote functions, just as you would call local function modules. However, you must include an additional DESTINATION clause to define where the function should run:
CALL FUNCTION RemoteFunction
DESTINATION Dest
EXPORTING
f1 =...
f2 =...
IMPORTING
f3 =...
TABLES
t1 =...
EXCEPTIONS......
The field Dest can be either a literal or a variable: its value is a logical destination (for example, "hw1071_53") known to the local SAP System. Logical destinations are defined in the RFCDES table (or the TRFCD table in R/2 Systems) via transaction sm59 or the following menu path: Tools ® Administration, Administration ® Network ® RFC destinations. You can also access logical destinations via the Implementation Guide (IMG) by choosing Tools ® Customizing ® Enterprise IMG. In the Implementation Guide, you can then choose Cross-application components ® ALE ® Communication ® Define RFC destination.
The remote function call concept, for example, allows you to access a function module in an R/2 System from an ABAP program in an R/3 System. If you want to read a customer record from your R/2 Systems database, create a remotely callable function module in the R/2 environment which retrieves customer records. Call this function from your R/3 System using a remote function call and listing the destination for the target R/2 System:
Pls. reward if useful

Unknown error calling a RFC Function Module in BODI

Hi all,
I am having an issue identifying the error that my batch job in BODI is giving with regards to a RFC function module call in my query. The value returned by the standard parameter 'AL_RFC_RETCODE' are square characters ( ).
At the completion of the job, the error message 'RFC CallReceive error <Function ZCT_INDSLS_SLS_TRN_INSERT: Invalid request.. Invalid request.>.' is being output.
Correct me if I'm wrong but the parameter 'AL_RFC_RETCODE' should return standard values as per the techical manual provided to undertand any errors that might occur during a RFC FM call.
Can anyone help me on this?
Best regards,
Andrew Wong

Hi Senthil,
I think you answered your query in your question itself
The user ID and password need to be maintained in RFC destination in SM59.
Go to SM59 and then click on test connection..if it does not ask for ID and passwoed that means correct ID and password is maintained in SM59 otherwise maintain it.
Regards,
Atish

Creating RFC Function Module

I am trying to use PHP and SAPRFC to pull out some information from our SAP database. I've been reading documentation and I've stumbled across this in the SAP documentation:
There are two restrictions on writing remote functions that are to be called transactionally:
                + Transactional calls cannot return parameter values. As a result, the interface for these functions should not specify any EXPORT parameters.
                + Functions that run transactionally may not perform call-backs: the caller's context does not necessarily still exist when the call-back is relayed back to the original system.
If this is true then how am I suppose to receive any data back from the RFC? I am trying to pull a couple of variables out of a few tables using basic select statements like this:
FUNCTION Z_RFC_COMMISSION_INDIVIDUAL.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(COMM_ACCOUNT) TYPE LIFNR DEFAULT 000000
*" EXPORTING
*"     VALUE(NAME) TYPE LFA1-NAME1
SELECT SINGLE name1 FROM lfa1 INTO name
WHERE lifnr = comm_account.
ENDFUNCTION.
I can connect to the SAP database but I am still not clear on the best way to pull out single values instead of a whole table from SAP using PHP. Does anyone have any example function module source code they could share?

Hi Mark,
I used this code (copy of you)
DATA: comm_info_output TYPE TABLE OF bdi_entry.
DATA: comm_info TYPE TABLE OF lfa1.
DATA: nametab TYPE TABLE OF bdi_mfgrp.
DATA: sel_tab TYPE TABLE OF bdsel_stat.
CALL FUNCTION 'TABLE_ENTRIES_GET_VIA_RFC'
    EXPORTING
      tabname               = 'LFA1'
    TABLES
      tabentry              = comm_info_output
      nametab               = nametab
      sel_tab               = sel_tab
    EXCEPTIONS
      system_failure        = 1 MESSAGE l_mes
      communication_failure = 2
      OTHERS                = 3.
comm_info[] = comm_info_output[].
and I get no error message. Where exactly do you get error message. Resp. is it going to short dump? (if so please attach list from st22).
I think the problem is not in function module but in setting of unicode / non unicode systems. Probably with FM you get some not allowed characters.
I found following thread:
RFC Lookup after unicode conversion of target R/3
Is it suitable for you?
Sorry I am not expert for this. Maybe if you identify exact problem and you don't know solution create a new thread with good description in the title and you will find unicode issues experts.
Regards,
Karol
Edited by: Karol Seman on Jul 30, 2008 2:18 PM

Error while creating a function module

Hii Experts
I am adding a table name to the tables parameter in a already created function module, But it is giving a error : TABLES parameter is obselete
the table which I am adding is
IT_GRAPH TYPE ZTY_GRAPH ( zty_graph is a structure which i made in se11 comprising of 2 fields)
Thanx in advance

Hi,
Give table parameters as:
IT_GRAPH LIKE ZTY_GRAPH,
It will give a warning, just press enter and proceed.
Thanks & Regards,
Navneeth K.

Error when using CONVERT_OTF function module

Dear Friends,
In many of our reports we are using the function module CONVERT_OTF to send the output as a mail the users.
But after the latest patch update we have came across a new problem. Mail is getting triggered and we can also see the icon or
the file in mail. But when we are opening the file we are getting the message that "THERE WAS AN ERROR OPENING THIS
DOCUMENT. THE FILE IS DAMAGED AND COULD NOT BE REPAIRED.
Earlier this program has been working fine from last 2 years but after updating the patch in the of August 2009. This problem we are
facing. All our mails are not working.
Thanks
Vamshi
Edited by: Rob Burbank on Sep 7, 2009 3:12 PM

Dear Clemens,
Thank you for the immediate response. I have checked the program in Debug Mode. When we are passing the data to the CONVERT_OTF the output table of the function module is showing the data in some Unicode format in the tables OTF and LINES.
Out of the FM is in completely special characters and this is after updating the latest patch.
We are using Release 700 Level 19 and Service Package SAPKA70019.
Thanks and Regards
Vamshi Sreerangam
Edited by: vamshi sreerangam on Sep 8, 2009 5:54 AM

Error when creating rfc

Error Details     Error when opening an RFC connection
Error Details     ERROR: partner 'wc40-alt.medialogik.com:sapgw01' not reached
Error Details     LOCATION: SAP-Gateway on host sapdev / sapgw03
Error Details     ERROR TEXT: WSAECONNREFUSED: Connection refused
Error Details     RELEASE: 700
i am getting these type of errors what was the problem.. can u help me..

Hi Singam,
try to check with the basis team managing the system, to which you like to connect, if the sapgwXX service is running. I had a similar problem a few weeks ago.
Alternatively you can switch on the load balance and connect through a message server. You need to enter the hostname (from SLD), the Message Server-Service, which should be 36 + System Number, SystemId and a login group (try SystemId + _all, might work).
Regards
Sven

Time Constraint Error when calling a Function module from Webdynpro ABAP

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
    Termination occurred in the ABAP program "SAPUP50R" - in
     "CHECK_TIME_CONSTRAINT_S1".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 1069
    of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are inverted time periods.
    IF l_prelp_line-begda > l_prelp_line-endda.
      l_is_inconsistent = 'X'.
    ENDIF.
Check if there are overlaps or gaps.
    IF NOT l_prelp_before IS INITIAL.
      l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
      IF l_date_difference <> 1.
        l_is_inconsistent = 'X'.
      ENDIF.
    ENDIF.
    l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda <> '99991231'.
    l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
    IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
      MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
    ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
    ENDIF.
ENDIF.
ENDFORM.                    " CHECK_TIME_CONSTRAINT_S1     "XYVN0352581
*&      Form clear_no_adapter_needed              new     "XREN844998
      text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM.                    " clear_no_adapter_needed
*&      Form set_no_adapter_needed              new     "XREN844998
      text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM.                    " clear_no_adapter_needed

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

Time Constraint Error when calling a Function Module

Any help will be greatly appreciated - Thanks RM
Time Constraint Error
Information on where terminated
Termination occurred in the ABAP program "SAPUP50R" - in
"CHECK_TIME_CONSTRAINT_S1".
The main program was "MP000000 ".
In the source code you have the termination point in line 1069
of the (Include) program "UP50RU01".
Error occurred during batch input processing
Source Code Extract
l_is_inconsistent = 'X'.
ENDIF.
Check if there are inverted time periods.
IF l_prelp_line-begda > l_prelp_line-endda.
l_is_inconsistent = 'X'.
ENDIF.
Check if there are overlaps or gaps.
IF NOT l_prelp_before IS INITIAL.
l_date_difference = l_prelp_line-begda - l_prelp_before-endda.
IF l_date_difference 1.
l_is_inconsistent = 'X'.
ENDIF.
ENDIF.
l_prelp_before = l_prelp_line.
ENDLOOP.
IF l_prelp_before-endda '99991231'.
l_is_inconsistent = 'X'.
ENDIF.
IF l_is_inconsistent = 'X'.
IF p_access_type = 'R'.
490 Datenbankschiefstand Personalnummer & Infotyp &
MESSAGE x490 WITH l_prelp_before-pernr l_prelp_before-infty.
ELSE.
491 Unzulässige Daten Personalnummer & Infotyp &
Line 1069 Error occcurs >>>> MESSAGE x491 WITH l_prelp_before-pernr l_prelp_before-infty.
ENDIF.
ENDIF.
ENDFORM. " CHECK_TIME_CONSTRAINT_S1 "XYVN0352581
*& Form clear_no_adapter_needed new "XREN844998
text
FORM clear_no_adapter_needed .
CLEAR no_adapter_needed.
ENDFORM. " clear_no_adapter_needed
*& Form set_no_adapter_needed new "XREN844998
text
FORM set_no_adapter_needed .
no_adapter_needed = 'X'.
ENDFORM. " clear_no_adapter_needed

Hi,
Well, are you trying to do a batch input on infotype 0000? If yes you need to check that the proposed values respects the time constraint, meaning no gap, no overlaps and no inversions. Also fields SUBTY, OBJPS, SPRPS and SEQNR must remain initial when processing IT0000...
Kr,
Manu.

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

What are the steps we have to follow to develop RFC function module

hi
what are the steps we have to follow to develop RFC function module

I will tell you simple example within r/3 systems..
source system - A (SAP R/3 )
Destination System B (SAP R/3).
First create RFC Destination in SM59 - in A System.
Createing RFC Destination - GOTO SM59 Transaction and click R/3 System .
it will go second screen and give ur RFC Name ,IP Address and log on details.
click on test concetion and remote logon.
now create RFC Function module in B System.
goto se37 - create fm with starting with Z* or Y*.
maintain all data like
attribute should be remote enabled
importing is v_matnr
exporting is v_maktx.
write the simple code - select single maktx from makt into v_maktx
where matnr = v_matnr.
Call this fm in report program in se38 in B sytem and copy the FM.
paste this code A System
use ur logic and destination 'RFC Name'.
Reward Points if it is helpful
Thanks
Seshu
Message was edited by:
Seshu Maramreddy

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

RFC function module without RETURN parameter thows error in XI. Please help

Hi Experts,
I have a File to RFC scenario in XI. The RFC function module that I am using at the receiving end does not have "RETURN" parameter. So when I test my scenario I get "RETURN" parameter not found error on SXMB_MONI.
So is it mandatory that RFC function module must have RETURN parameter when used in XI?
Is there any work around to avoid the error without changing the RFC function module?
Please help!
Thanks
Gopal

In my senario the QOS is best effort because it is a Sync.
But the function module is sync in nature as it is returning a parameter called SO_Docs and Ret_Msg. The Ret_Msg contains the error info but it not of BAPIRET2 type.
So is there any way to avoid this error when my QOS is best effort?
Please help!
Gopal

Error when creating rfc function module

Similar Messages

Maybe you are looking for