Execution of RFC

Hi,
I have an RFC ZSM_USER_ALLOCATION where i need to pass certain input like userId,projectId, cadre,skillid and get output from
the same.When i pass userId,projectId, cadre output values are fetched in the perfect manner.But wenever i try to pass
skillid, i got get any data as output but executing the RFC at      R3 side with the same skillid fetches me output.Moreover ,
after trying with skillid when i try with userId,projectId, cadre i get no output at all!!!....
I cant figure out where i am going wrong ....Experts please do suggest .I am enclosing the same code for this :
CopyPSNumberNode: node for userId
CopyProjectDetailsNode : node for projectId
OutputDetailsNode : node where output after executing the RFC is set
IPublicTdc_DataCust.IZsm_Actual_Allocation_InputNode  AllocationInputNode = wdThis.wdGetTdc_DataCustController()
                                             .wdGetContext()
                                             .nodeZsm_Actual_Allocation_Input();
IPublicTdc_DataCust.IZsm_Actual_Allocation_InputElement AllocationInputElement = null;
AllocationInputNode.invalidate();
Zsm_Actual_Allocation_Input input = new Zsm_Actual_Allocation_Input();
Zsm_Cadre zsmcadre =  null;
Zsm_Skills o = null ;
if(CopyPSNumberNode.size()!=0)
for(int j=CopyPSNumberNode.size()-1;j>=0;--j)
  CopyPSNumberElement = CopyPSNumberNode.getCtx_vn_CopyPSNumberElementAt(j);
  Zsm_User_List userList = null ;
  userList = new Zsm_User_List();
  userList.setUser_Id(CopyPSNumberElement.getPSNumber());
  userList.setUser_Name(CopyPSNumberElement.getUserName());
  input.addT_User(userList);
if(cadNode.size()!=0)
   zsmcadre = new Zsm_Cadre();
   zsmcadre.setCadre(cadNode.currentCtx_vn_CadreElement().getCadre());
   input.addT_Cadre(zsmcadre);
if(CopyProjectDetailsNode.size()!=0)
  for(int k=0;k<CopyProjectDetailsNode.size();++k)
     CopyProjectDetailsElement = CopyProjectDetailsNode.getCtx_vn_CopyProjectDetailsElementAt(k);
     Zsm_Project zsm_proj = null;
     zsm_proj = new Zsm_Project();
     zsm_proj.setProject_Id(CopyProjectDetailsElement.getProjectId());
     zsm_proj.setProject_Name(CopyProjectDetailsElement.getProjectName());
     input.addT_Proj(zsm_proj);
        if(AllocationDetailsElement.getSkillId()!=null)
            o = new Zsm_Skills();
         o.setSkill_Id(AllocationDetailsElement.getSkillId());
          input.addT_Skill(o);
          wdComponentAPI.getMessageManager().reportSuccess(""o.getSkill_Id()""+o.getSkill_Name());
          wdComponentAPI.getMessageManager().reportSuccess(""+o.toString());
AllocationInputNode.bind(input);
OutputDetailsNode.invalidate();
wdThis.wdGetTdc_DataCustController().execute_zsm_actual_allocation_input();

Hi,
what is the data type of skillid in your wd code and backend? some time it may happen because of type mismatch. just check that.
also, If you didnt write  below code for skillid, is it working fine?
+if(AllocationDetailsElement.getSkillId()!=null)+
+{+
+o = new Zsm_Skills();+
+o.setSkill_Id(AllocationDetailsElement.getSkillId());+
+input.addT_Skill(o);+
+wdComponentAPI.getMessageManager().reportSuccess(""o.getSkill_Id()""+o.getSkill_Name());+
+wdComponentAPI.getMessageManager().reportSuccess(""+o.toString());+
+}+
Check the type of the skillid in R/3 and in your wd.
PradeeP

Similar Messages

  • Java.lang.LinkageError on execution of RFC

    Hi all,
    I am getting java.lang.LinkageError: loader constraints violated when linking com/sap/tc/cmi/model/ICMIModelClass class when trying to execute a RFC.
    Does anyone has any idea why thie error is thrown.
    Thanks and regards,
    Jaydeep

    Hi Jaydeep, 
    Check this:
    Re: Unable to access external jars in DC during run time!!
    Regards,
    Shyam.

  • Client non-modifiable Warning while execution of RFC

    Hi All,
    When we execute the RFC in our Test server, I am get following warning. This function module is trying to update the HR infotype data. As this is Test client, it is non-modifiable (from config point of view).
    But why its throwing warning, when we change masterdata? Same thing is working fine in Production Server which is also non-modifiable. Please suggest the solution - Regards, Vinod
    Message no. TK430
    Diagnosis
    The system administrator has set your logon client to the 'not modifiable' status.
    Client-specific objects can not be changed in this client.
    System Response
    The function terminates.
    Procedure
    Contact the system administrator.
    For more information, see the SAP Library under Change and Transport System.

    Hi Sandeep,
    Thanks for the reply, but I couldnt find any namespace properties for HR infotype objects.
    Can you please specify the exact path.
    Thanks- Vinod

  • Execution a RFC from Site (Please I need a help )

    Hi,
    Again with my questions... I have a RFC that is executed from another RFC, when I test it with a variant (in R/3) works but when I execute it from Web Test Environment doesn't work.
    Any idea or information I will appreciate it.
    Thanks in advance.
    Tokio

    Hmmmmmmmmmm
    I have a RFC that is executed from another RFC, when I test it with a variant (in R/3) works
    - You’re able to see the trace after that ..if you’re able to run it successfully in R/3 right ?
    But when I execute it from Web Test Environment doesn't work.
    -That’s means something is missing when you’re running from out side from SAP. Do you have RFC connection ? In TR.SM59 .. Moreover , when you execute it ..Are you able to see any connection establish in Tr.smgw?
    Thanks
    Saquib

  • Run the execution of RFC is background

    Hi
    I want to run the call of the rfc in my program in BACKGROUND.
    the requirement is that i want to call the rfc in infinitie loop which should process in background and depending on the next input the background job should stop.
    How to achieve it.

    You could do the following:
    report xxx. "to be scheduled in a background job
    DO.
      call function 'RFC' destination xxx......
    * based on the return value => exit
      IF return_value EQ 'the value you want'.
        EXIT.
      ENDIF.
    ENDDO.
    This code will call the RFC repeatetly until the desired value is returned. In that case the loop is left and the background job will end.
    However be careful with those infinite loops, because if there is a problem and you don't get the desired value back this background job will run forever.
    Regards,
    Michael

  • Dump on execution of RFC HRXSS_PER_READ_P0006_US in ECC

    Hi
    I am just trying to execute one of FM that is used in case of country specific self service application. But I get following dump in the  backend. Strangely standard wd java also calls this FM without any dump. I also did check though extenal debugging.
    I have also checked if I execute it for any other infotype instead 006 I do get the same error.
    Please suggest if I am missing something .
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
    "SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"
    "HRXSS_PER_CLEANUP"
    Source Code Extract
    Line  SourceCde
        1 FUNCTION hrxss_per_cleanup.
        2 *"----
        3 ""Local interface:
        4 *"  EXPORTING
        5 *"     VALUE(MESSAGES) TYPE  BAPIRETTAB
        6 *"----
        7
        8 *  CALL METHOD mac_adapter->cleanup
        9 *    IMPORTING
       10 *      messages = messages.
       11
       12 * TRY.
    >>>>>   CALL METHOD xss_adapter->cleanup
       14     .
       15 * CATCH CX_HRPA_VIOLATED_ASSERTION .
       16 * ENDTRY.
       17
       18 ENDFUNCTION.
    Thanks
    Abhay

    Hello Abhay,
    This could be related to incorrect use of usecase in this case, please check the table V_T7XSSPERSUBTYP for the same.
    Also please Support Pack should be in sync, Mismatch will lead to the same error. You can go through the link :
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES
    You can check if the BADI HRXSS_PER_BEGDA is active in your system or not ??
    Best Regards,
    Deepak...

  • How to close RFC connection in one script coding

    In one script, I am using the REF command to call another 2 scripts and these called scripts shd be run on same C36 ( test system). I shd close RFC connection between these 2 scripts.
    That is , once the 1s script over the RFC shd be closed and the user has to give usename and pwd  then  2nd script shd run.
    I have tried with the following code…. But it says RFC is not open……
    REF ( Y04S_FC_RM_CJ88_112 , Y04S_FC_RM_CJ88_1 , C36_999 ).   (when execute this script RFC to C36 will be created and after execution that RFC shd be closed so I included following ABAP code)
    ABAP.
      data : dest type RFCDEST.
      move 'S4_SAPC36999' to dest.                                       
      move dest to v_dest.
    *--Close the connection before opening it incase it is opened
              call function 'RFC_CONNECTION_CLOSE'
                   exporting
                        destination          = dest
                   exceptions
                        destination_not_open = 1
                        others               = 2.
              if sy-subrc <> 0.
              endif.
              move sy-subrc to v_subrc.
    ENDABAP.
    REF ( Y04S_FC_RM_CJ44_112 , Y04S_FC_RM_CJ44_1 , C36_999 ). (here agagin the RFC will be created and this script will be exectued.)

    In one script, I am using the REF command to call another 2 scripts and these called scripts shd be run on same C36 ( test system). I shd close RFC connection between these 2 scripts.
    That is , once the 1s script over the RFC shd be closed and the user has to give usename and pwd  then  2nd script shd run.
    I have tried with the following code…. But it says RFC is not open……
    REF ( Y04S_FC_RM_CJ88_112 , Y04S_FC_RM_CJ88_1 , C36_999 ).   (when execute this script RFC to C36 will be created and after execution that RFC shd be closed so I included following ABAP code)
    ABAP.
      data : dest type RFCDEST.
      move 'S4_SAPC36999' to dest.                                       
      move dest to v_dest.
    *--Close the connection before opening it incase it is opened
              call function 'RFC_CONNECTION_CLOSE'
                   exporting
                        destination          = dest
                   exceptions
                        destination_not_open = 1
                        others               = 2.
              if sy-subrc <> 0.
              endif.
              move sy-subrc to v_subrc.
    ENDABAP.
    REF ( Y04S_FC_RM_CJ44_112 , Y04S_FC_RM_CJ44_1 , C36_999 ). (here agagin the RFC will be created and this script will be exectued.)

  • 3rd party to sap using RFC adapter

    Hi Folks,
    I'm sending some IDOC to sap from the 3rd party. I have to use RFC (TRFC call) adapter as sender and IDOC as receiver adapter.
    Can you please suggest me how to configure teh sender side.
    Regards....

    >
    santosh nayak wrote:
    > Hi Folks,
    > I'm sending some IDOC to sap from the 3rd party. I have to use RFC (TRFC call) adapter as sender and IDOC as receiver adapter.
    > Can you please suggest me how to configure teh sender side.
    >
    > Regards....
    In order to use RFC as sender need to configure the below
    SAP Side
    RFC destination of type T using SM59 tcode
    PI side
    RFC destination of TYPE t type using same tcode
    Note the progid provided should be same in both RFC destionations
    Then during execution of RFC in SAP side need to provide the RFC destionation created there
    HTH
    Rajesh

  • Process Chain remote execution locks up (All Dialog Processes used up)

    Hi,
    We have the following task at hand. We kick in BW process chain execution via RFC from our R/3 system using the function described below. What happens is that the process chain does get kicked in the remote BW system, but it quickly locks up. System monitor  says that all dialog process have been utilized. So, basically it gets stuck in the beginning of the process chain. Is there anything I can do to prevent this from happening?
    Here is the function call:
    This function triggers execution of process chain
    (on the remote BW system)
      CALL FUNCTION 'RSPC_API_CHAIN_START' DESTINATION p_rdest
        EXPORTING
          i_chain             = p_pchain
      I_T_VARIABLES       =
          i_synchronous       = 'X'
      I_SIMULATE          =
      I_NOPLAN            =
        IMPORTING
          E_LOGID             = gv_pchain_logid
        EXCEPTIONS
         failed              = 1
         OTHERS              = 2
    Thank you,
    AG
    Message was edited by:
            AG

    How many work process did you configured in SOLMAN, what is the action that CSMUSER is busy with?
    I think CSMREG is a communicatino user to satellite agents and check the RZ21--> AGENT status.
    Regards
    SM

  • RFC,TRFC

    hi all,
    what are the different types of RFCs and difference between them(RFC,TRFC etc)
    Regards
    raj

    Dear Raj,
    what are the different types of RFCs and difference between them(RFC,TRFC etc)
    RFC Basics
    This section gives a brief overview of the Remote Function Call (RFC) within an SAP System, that is
    · How the RFC Interface works
    · The functionality that is provided by the RFC and
    · It explains the technical requirements for RFC on R/2, R/3 and external systems on all currently supported platforms.
    The following background topics are available:
    1. The RFC Interface
    2. RFC in SAP Systems
    The RFC Interface
    A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call), but usually caller and callee will be in different systems. In the SAP System, the ability to call remote functions is provided by the Remote Function Call interface system . RFC allows for remote calls between two SAP Systems (R/3 or R/2), or between an SAP System and a non-SAP System.
    RFC consists of the following interfaces:
    · A calling interface for ABAP programs
    Any ABAP program can call a remote function using the CALL FUNCTION...DESTINATION statement. The DESTINATION parameter tells the SAP System that the called function runs in a system other than the caller's. RFC communication with the remote system happens as part of the CALL FUNCTION statement. RFC functions running in an SAP System must be actual function modules, and must be registered in the SAP System as "remote”. When both caller and called program are ABAP programs, the RFC interface provides both partners to the communication. The caller may be any ABAP program, while the called program must be a function module registered as remote.
    o The topic Calling Remote Function Modules in ABAP provides details on calling function modules registered as remote.
    o The topic Writing Remote Function Modules in ABAP provides information on writing function modules that you want to call remotely.
    · Calling interfaces for non-SAP programs
    When either the caller or the called partner is a non-ABAP program, it must be programmed to play the other partner in an RFC communication. To help implement RFC partner programs in non-SAP Systems, SAP provides
    External Interfaces
    External programs to call function modules in SAP R/2 or R/3 systems and execute them in these systems can use rFC-based and GUI-based interfaces. Vice versa, ABAP programs in R/2 or R/3 can use the functions provided by external programs via these interfaces.
    RFC in SAP Systems RFC is an extension of CALL FUNCTION in a distributed environment. Existing function modules can be executed from within a remote system (R/2 or R/3) via an RFC call. Adding a DESTINATION clause to the CALL FUNCTION statement does this:
    The destination parameter displays an entry in the RFCDES table (which is defined with transaction SM59). This entry contains all necessary parameters to connect to and log in the destination system. The RFC API on OS/2, Windows, Windows NT and all R/3-based UNIX platforms makes it possible to use the RFC functionality between an SAP System (R/3 from Release 2.1 and R/2 from Release 5.0D onwards) and a C program on the above platforms. It is of no significance to the caller whether the remote function is provided in an SAP System or in a C program. RFC frees the ABAP programmer from having to program his own communications routines. When you make an RFC call, the RFC interface takes care of:
    ·     Converting all parameter data to the representation needed in the remote system. This includes character string conversions, and any hardware-dependent conversions needed (for example, integer, floating point). All ABAP data types are supported.
    ·     There is no support for Dictionary structures.
    ·     Calling the communication routines needed to talk to the remote system.
    ·     Handling communications errors, and notifying the caller, if desired. (The caller requests notification using the EXCEPTIONS parameter of the CALL FUNCTION statement.)
    The RFC interface is effectively invisible to the ABAP programmer. Processing for calling remote programs is built into the CALL FUNCTION statement. Processing for being called is generated automatically (in the form of an RFC stub) for every function module registered as remote. This stub serves as an interface between the calling program and the function module.
    A distinction is made between an RFC client and RFC server. RFC client is the instance that calls up the Remote Function Call to execute the function that is provided by an RFC server. In the following, the functions that can be executed remotely will be called RFC functions and the functions provided via RFC API will be called RFC calls.
    All RFC functions available in a remote RFC server system, which are called by an RFC client, are processed transactionally. This means that after execution of the first RFC function in the RFC server system the complete context (all globally defined variables in the RFC server program or in the main program of a function module) is available for further RFC functions. The RFC connection is closed only
    ·     When the context of the calling ABAP program has ended or
    ·     Explicitly by RfcAbort or RfcClose in the external program.
    Until Release 3.0 the connection to an R/3 System must be established to a previously defined application server. From Release 3.0 onwards, it is also possible to have an application server assigned by the message server on the basis of a load balancing procedure. This applies both for RFC between R/3 systems and between external systems and R/3 systems.
    To make the execution of RFC functions reliable, safe and independent from the availability of the RFC server or RFC server system, the transactional RFC (tRFC) was introduced for R/3 systems from Release 3.0 onwards. This ensures that the called function module is executed only once in the RFC server system. In transactional RFC calls, the data that belongs to an RFC function must first be stored temporarily on the SAP database in the RFC client system. When processing is completed, this must be reported back to the calling ABAP program. Everything else is handled by the tRFC component in the R/3 System. Since a database is not always available on external systems, the link to the tRFC interfaces is implemented such that the client or server programs based on RFC API must take on some administrative functions to ensure that the respective function module is executed "only once".
    Best Regards,
    Srikanth
    Reward the useful answers and you will get one point yourself<a href="/people/baris.buyuktanir2/blog/2007/04/04/point-for-points-reward-yourselfyourself

  • Question about destination parameter in RFC function module

    Greetings,
    For execution of RFC function module such as MD_STOCK_REQUIREMENTS_LIST_API  on local server, the destination parameter is not required or it can be DESTINATION 'NONE'. I observe that the second option is much slower than the first option. My question is why the second is much slower.
    Thanks,
    Hung

    I've tested it with se37 by leaving RFC target system blank or filling it with 'NONE' , I saw 53000 microseconds versus 45000 microseconds.
    Hung

  • Calling abap rfc FM from jsp programming

    hi friends,
        I am having a requirement to call abap function module from jsp page. can any one help me please?
    thanks
    Medoyi C

    Hi Medoyi,
    Please follow the below steps
    1. Are you using NWDS or any other IDE? Create your Web Project.
    2. In any of the case download JCO3.0 jar files and add to these librarries to you IDE.
    3. Create a connection class in write a code here and you should have host, port and userid/password of the ECC system from where you are calling your RFC.
    4. After making a connection then write a code to pass import parameters and execute.
    5. After execution of RFC you will get export parameter, table or structure.
    6. Display this data now as a respose.
    Please reply back if any more information is required.
    Thanks,
    Hamendra

  • How to calculate RFC table columns in to another table column.

    Hi,
    I am doing a scenario, where in my Wendynpro UI table has been populated with a Function module output.
    Now three of the output columns needs to processed on each row.
    For ex:
    1. I have to add two cloumn values on each row in to third column which is binded to a context attribute. This should happen before I show the table result. So, I cannot use calulated attribute here. Instead I am trying to find a custom solution that should process each row as soon it appears then bind to result column.
    2. Also One of the RFC column has list of values i.e ABAP Function module returns a list of values. How do we populate these list of values in to UI table then add them alltogether before we show the result to the user.
    I appreciate your help in this regard.
    thanks
    Praveen

    Hi
    You can add custom attributes in Modal node as well. After successful execution of RFC, loop through the modal node and do the necessary calculations for each row and put them in the custom attributes.
    Map the required attributes in the Table UI including the custom attributes.
    This should help !!!
    Regards,
    Sayan Ghosh

  • Momento de envio do XML

    Boa tarde,
    Estou em um projeto de implementação e com a seguinte dúvida:
    Requerimentos:
    Tenho que enviar o XML assim que a Invoice+NF é gerada (VF01/VF04, etc).
    Num segundo momento, após a aprovação do XML, eu poderei imprimir a DANFe.
    Envio XML:
    Sei que a função que mapeia o XML para a versão 2.0 é a J_1B_NF_MAP_TO_XML e a função que envia para o GRC ou outra mensageria (utilizaremos NeoGrid) é a J_1B_NFE_XML_OUT.
    A pergunta é: como faço a chamada destas funções? Qual programa devo chamar? Em qual momento? É por customizing ou por uma exit no faturamento?
    Obs.: entendo que estas funções já estão configuradas no monitor J1BNFE para solicitar o reenvio da nota, etc.
    Impressão DANFe:
    Em paralelo, na J1BJ vou ter que configurar somente o programa de impressão do DANFe (J_1BNFPR), correto? Pois assim quando eu gerar e processar o output da NAST ele irá fazer a impressão do documento, correto?
    Caso não entendam as perguntas por favor me contestem que eu explico melhor.
    Obrigado!
    Felipe Brasil Simioni

    Olá, Fernando.
    Por favor veja se pode nos ajudar.
    Estamos tendo o mesmo problema com o envio do XML para a mensageria (não GRC).
    Seguindo as parametrizações indicadas acima:
    SPRO
       Componentes válidos para várias aplicações
         Funções gerais de aplicação
           Nota Fiscal
             Saída
               Atribuir parametros de numeração e dxed impressão
    O local de negócios está configurado como RFC CALL vazio (segue descrição abaixo):
    "Execução RFC e atualização banco dados na mesma LUW (padrão)"
    Porém, ao tentar enviar a nota fiscal (ex: J1B1N), ocorre um erro na SM58 e o XML não é enviado para o sistema de mensageria.
    Analisando o programa SAPLJ_1B_NFE, no include LJ_1B_NFEF42, vemos que para mensagerias não GRC o programa chama a função J_1B_NFE_XML_OUT em background task, o que ocasiona o erro abaixo na SM58.
      IF sy-subrc IS INITIAL.
    non SAP messaging system                          "V1.10
        if lv_xnfeactive is initial.                    "V1.10
    Call function asych. when RFC connection available
    gv_callmode can be switched in debbuging to call the RFC synchronous
    do not reset gv_callmode direct after the RFC call
          if gv_callmode is initial.
            CALL FUNCTION 'J_1B_NFE_XML_OUT'
    IN BACKGROUND TASK
              DESTINATION lv_rfcdest
              EXPORTING
                xml_in                = xmlh
                xml_item_tab          = xmli_tab
                xml_batch             = xmlb_tab
                xml_ref               = xmlr_tab
                xml_dup               = xmld_tab
                xml_vol               = xmlv_tab
                xml_head_tab          = xmlh_tab          "V1.10
                xml_imp               = xml_import_tab    "V1.10
                xml_ext1              = xml_ext1_tab      "V1.10
                xml_ext2              = xml_ext2_tab      "V1.10
                xml_adi               = xml_adi_tab       "V2.00
                xml_reb               = xml_reb_tab       "V2.00
                xml_cane_dia          = xml_cane_dia_tab  "V2.00
                xml_cane_ded          = xml_cane_ded_tab. "V2.00
    Erro da SM58:
          RfcAbort: Cannot lock transaction
          Nº mensagem SR053
    Note que a chamada é feita de forma assincrona porque a variável gv_callmode está como initial, e que segundo o comentário da SAP, essa variável é usada somente para debug, sem qualquer parametrização que controle o modo de chamada.
    Obs: se comentarmos a linha IN BACKGROUND TASK, tudo funciona perfeitamente.
    Mas obviamente não é o que queremos fazer. Queremos manter o programa original da SAP.
    Já pesquisamos notas para esse problema, mas não encontramos nada que se refira a esse problema.
    Alguém mais se deparou com essa situação?
    Desde já agradeço pela ajuda.
    Rodrigo Ferreira

  • CALL_FUNCTION_OPEN_ERROR

    Hi experts,
    We are have an issue with the RFC connection. it gives a short dump with CALL_FUNCTION_OPEN_ERROR Error when opening an RFC connection when the number of users goes up. The RFC is link/gateway connection is not getting disconnected when the RFC is done with the execution. so the number of connections are going up and once the max is reached it starts dumping.
    Is there a way to stop/kill the RFC connection once the execution of RFC is complete.
    ST22 Error analysis
    An error occurred when executing a Remote Function Call.
    "CPIC-CALL: 'ThSAPOCMINIT' : cmRc=17 thRc=249#Active connection table is full.
    Please try again later "
    Status of connection.... "CODE=CM_DEALLOCATED_ABEND -1 -1 SAPCODE=249 CONV="
    Internal error code.... "RFC_IO5"
    Is there a SM59 RFC connection setting which says disconnect once the RFC execution is done ?
    Any inputs are welcome,
    Regards
    Diwakar

    Hi,
    Yes I was able to solve this,
    Whenever I call a RFC the connection was not being closed when the execution of the RFC is complete . So I have to write the code to close that instance of RFC connection. I used the Function module 'RFC_CONNECTION_CLOSE' to close the connection whenever I call a RFC.
    Thanks
    Divakar

Maybe you are looking for