Error in Creating RFC Destination

Hi,
I am Going for RFC to File Scenario.
For Sender RFC it < I am trying to create RFC Destination in SAP r/3
I have Given
RFC Dest  : XI_CONNID
Conn type : Tcp/IP
Activation Type : Register Server Program
Program ID  :sap
gateway host : sap-server( Sap server)
gateway service : sapgw00.
I saved and I tested but it is showing errors.
Error : Error in Opening RFC Connection
    Whe i Click on this error message it i showing
     Error  Program sap not registered.
Points will be awarded.
regards,
Jayasimha

Dear Jaya,
create a RFC SENDER communication channel first and then activate the channel.
now go to sm59 there use the same program-id as u did at RFC SENDER COMMUNICATION CHANNEL.
note:program-id is registered by XI at R/3 level with details related to it's profile(XI profile).
step 1) create RFC COMMUNICATION CHANNEL with program-id as "any name" at XI first .
2)create TCP/IP connection with registered program-id created by XI at first step
so when you execute steps 2 then 1 you will get error ,coz by that time program-id is not yet registere by XI in R/3 domain.
after executing step 1 i.e creating porgram id at R/3 through XI.
got to ST22 at R/3 and check whether any dump is found against "XI creating porgram-id at R/3 level".
we failed at creating PROGRAM-ID itself at R/3 level because of missing authorizations against my R/3 user id,which we will be using at XI RFC channel.
generally problem will be at PROGRAM-ID creation itself,so just go to ST22 and check any authorizations missing for your userid which is being used at RFC channel configuring at XI.
Thanks & Regards,
Rama Krishna

Similar Messages

  • Creat RFC destination for portal

    Hello,
    when i am doing RSPOR_SETUP , i am getting java and abap support package versions are different error message for step 2, i.e creating RFC destination for portal.
    Please send me suggestion regarding this issue.
    regards
    Sreesudha

    is ur BI and Portal SP versions different ?? ....if true ?? make sure they have the same SP
    use this link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00bed70a-7501-2a10-ec9e-9a04485ab477
    for guidance......

  • Create RFC destination

    HI,
    I want to build RFC destination between 2 ABAP system ,
    i need step by step solution ?
    Regards

    Hi,
    1)Log on to ABAP system.
    2) Goto T-code SM59.(For Creating RFc destination)
    3)Different connection types will appear select for ABAP CONNECTION
    4)Click on Create button from top.
    5)Give the name of RFC destination------ex:ZR/3TOBW
    6)Connection type -
    3
    7)Short Description
    8)Click on Technical Settings Tab and maintain the Host name and system number of another ABAP System.
    9)Click on Logon&Security Tab Provide the log on Credentials of  another ABAP system
    10)click on save.
    11)Click on Connection Test Button.
    12)Click on Remote logon.
    after that you will be connecting to the another ABAP system Remotely.(If and only if the Technical Settings which you provide are correct We can connect to other ABAP system)
    If any error occur's please check your Technical settings and also Logon&Secirity which you provide.
    Thanks.

  • Getting error in creating JCo destination for WebDynpro

    Hi Guys,
    I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
    When I am seeing the details:
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
    Web Dynpro code generators of DC sap.com/tcwdtools:
    No information available
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87289.311
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Please help me guys.
    Paritosh

    You should post your question to the Webdynpro forum:
    Web Dynpro Java

  • Best practice for creating RFC destination entries for 3rd parties(Biztalk)

    Hi,
    We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
    The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP. 
    We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
    We also wanted to know if there are any best practices to optimise on number of RFC destinations.
    Here were a few suggestions we had in mind to tackle the same.
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
    I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
    I would appreciate if you can suggest the best architecture or practice to achieve  RFC destinations in an optimized manner.
    Thanks in advance
    Sam

    Not easy to give a perfect answer
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    -> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    -> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    -> consider this option 2.
    We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

  • How to create RFC Destination without using SM59?

    Hello all:
    We are troubleshooting an issue.   An user created a RFC destination.   He claims that he did not use SM59.   We checked his access and do not have SM59 in his roles.
    He configured VIRSA FireFighter.   During the configuration, he created RFC destination.   Document says use SM59 or contact BASIS Admin.     He claims that he used a config table and he don't remember the config table name.   RFC screen shows his ID as creator of the RFC.
    We are trying to understand how an RFC can be created (outside of SM59) and plug the security hole in the environment.
    Any insights would be appreciated.
    --Anand

    The FireFighter solution changes the RFC destination of the service user "on the fly" without S_TCODE checks for 'SM59'. But if I can remember correctly when looking into this, it does not create the RFC destination (in SM59) "on the fly".
    > He claims that he used a config table and he don't remember the config table name.
    Theoretically this is possible - a config table to define the name of the destination, and then create it if it does not exist yet (when used).
    Otherwise, see SAP note 587410 and restrict (remove) his authority for the test environment (concentrate on S_DEVELOP, not S_TCODE - as you have also experienced).
    Cheers,
    Julius

  • RFC - XI - WEBSERVICES scenario - Where to create RFC Destination

    Hi  Experts
    For my RFC - XI - WEBSERVICES scenario, I have to create one TCP/IP RFC destination on R/3 system with the following details
    RFC Destination Name    : XXXX
    Connection Type            : T (TCP/IP)
    Activation Type              : u201CRegistered Server Programu201D
    Program ID                      : YYYY
    Gateway Host                : R/3 Details ..??
    Gateway Service           : R/3 Details ..??
    My Function Module (Remote-Enabled) - u201CZZZZu201D is defined in R/3 System.
    This Function Module should be communicated with the target system i.e. NW XI system 
    As per the Note from SAP Help: To be able to communicate using RFC, you need to define the target systems as RFC destinations in the sending system(R/3)
    Target system u2013 XI Server
    Sending system u2013 R/3 System
    Are my details provided are good enough as per my explanation? Please guide me in this regard.
    QUESTION : Where exactly do I need to create the RFC Destination(SM59)? on R/3 side or on XI side?

    Refer the following link-
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414700)ID1636235450DB01012070359836134304End?blog=/pub/wlg/1438
    what are the inputs should be given to Gateway Host and Gateway Service while creating RFC Destination??
    Open transaction SMGW on the R/3 system and choose
    Goto -> Parameters -> Display. Beneath Attributes there will be the
    entries 'gateway hostname' and 'gateway service'.#

  • Getting problem when creating RFC Destination on XI system

    hi,
    I m trying to create RFC Destination on XI system using sm59 tcode. In technical setting tab at  Target Host field, i gave SAP  ECC server IP address. and in Logon Tab I gave Login parameters for SAP ECC server  (Client 400, User : 05 & Password for user 05). Current user and Unencrypted Password fields are unchecked. also Logon Scree is also unchecked in Security Option.
    Problem is, when i click on Remote logon tab, It shows me Logon screen with client 000, User : 04 (which is XI system's user name) and Password. so it doesn't take given login setting for ECC system and if i tried this thing more than 3 times, ECC server block my pwd.
    Please suggest me the required solution
    Thanks & Regards
    Ritesh

    Hi ritesh
    First check if the user exists in ths system. Check the password especially. Because the password space (Number of characters)in SM59 screen is more than password character in SU01 screen.Check the password.
    Secondly, Check if you have given the proper client in the destination box of SM59.
    Check for the unicode test also.
    If possible change the user type as service user.
    When everything is perfect am sure the rfc connection should be fine...

  • Steps to create  rfc destination

    hi,
    what are the steps to create rfc destination

    Follow the following steps :
    1. Create RFC destination for both the systems on CRM and R/3 in SM59.
    2. Create the logical systems and assign clients to logical system in SALE transaction both on CRM and R/3.
    3. Create a user in the R/3 table CRMCONSUM with the name CRM.
    4. Maintain the Middlware Parameter tables on CRM : Table SMOFPARSFA:
    Create an entry for following parameter entry:
    Key - R3A_COMMON
    Para name - CRM_DEFAULT_DESTINATION
    Value - R/3 logical system
    5. Maintain the parameter tables on R/3 system : CRMRFCPAR, CRMPAROLTP
    CRMRFCPAR :
    Create new entry with following data:
    User - CRM
    Object name - *
    RFC Destination - RFC destination for CRM
    Load types - All Load Types
    In Queue flag - X
    Send XML – No XML
    CRMPAROLTP :
    Create the following parameter entry:
    Para name - CRM_DEFAULT_DESTINATION
    User - CRM
    Value - Name of the CRM logical system
    6. Create Sites and attach subscriptions in Admin Console : Tcode SMOEAC
    Create a Site as CRM and another as R/3. Attach the required subscriptions to the R/3 site.
    7. Register the queues in SMQR and SMQS transactions.
    PS : For detailed steps refer the Middlware Base Customizings(CR500 and CR100)
    Regards.

  • Creating RFC Destination For UNICODE system From NON-UNICODE system

    hi
    how can i create RFC Destination For UNICODE system( XI ) From NON-UNICODE (R/3) system.
    thanks and regards
    Mithlesh Kumar Jha

    Hi,
    Check these blogs , Hope u would be getting some idea
    <b>/people/thomas.jung3/blog/2004/06/24/bsp-150-a-developer146s-journal-part-v-xml-for-rfcs
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
    /people/sap.user72/blog/2004/06/19/how-i-started-with-sap-web-development</b>
    Regards,
    Sridhar Reddy

  • Creating RFC destination in Visual Administrator results in error

    Hi.
    I am trying to set up ESS and MSS on a EP 6.0 with SP15.
    According to a Post-installation guide for SLD i have to create a RFC destination, but when i save the settings i get the following error: Error changing bundel's properties, see LOG for details!.
    And when i try to start the RFC destination i get the following error: Error starting bundle, see LOG for details!
    Have anybody encountered this problem, and if so, can you give me a hint to what the problem might be?
    Regards Liselotte

    hi
    I am also running into this error, and this is preventing me from completing my xi configuration as after i create the bundle..and select start..i get a msg "error starting bundle see log for details.."
    what log do i see...?
    and a test connection from sm59 also fails..
    any help on this is appreciated.
    Regards
    Ravi

  • CPIC-CALL Transaction program not registered Error while creating RFC Desti

    Hi All,
    I am trying to create a new RFC Destination.
    Details I have provided are..
    1.RFC Destination Name
    2.Connection Type - TCP/IP
    3.Description
    4. Activation Type - Registered Server Program.
    5.Program Id.
    6. Gateway Host and Gateway Service.
    But When I Test the connection, I am getting the following error.
    <b>" program xyz not registered / CPIC-CALL: 'ThSAPECMINIT'# Transaction program not registered"</b>
    However I was able to create and connect RFC Destinations successfully previously.
    I am not SAP guy. Could someone help resolve this issue.
    Thanks,
    Phani

    hi Sekhar,
    I request you to please help me out in this issue. I am getting similar kind of problem. I am trying to replicate the customer from CRM to R/3 and i get a bdoc message in SMW01 that "RFC connection failed please press the save button again". When the basis team further investigated they came up with the below error..
    User: CRREMOTE (Client: 071)
    Destination: OCR (handle: 1, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1462
    CPIC-CALL: 'ThSAPECMINIT'
    Transaction program not registered
    DEST =OCR
    HOST =%%RFCSERVER%%
    PROG =dpssrfc
    Trace file opened at 20061121 140451 EST SAP-REL 640,0,109 RFC-VER
    3 804778
    resize I/O buffer to 28000 bytes
    >>>> [2] MQ_LINK      : TCP  <ac: 3> K %%RFCSERVER%% >>> OPEN
      {45632F14-288E-0046-0000-0000A888A7AA}-
    ======> CPIC-CALL: 'ThSAPECMINIT'
    can you please tell me where can be probelm. Regarding your message, where can i get the communication channel to assign the program id.
    Awaiting your reply,
    Thanks & Regards,
    Yogesh

  • Creating RFC Destination in SAP R/3

    Trying to create an RFC destination in SAP R/3.  Looked at few articles in creating them, but I am getting error while testing.  It says that the "Program" couldn't not be found.  I tried with all options, "Registered in Server Program", "Start on Application Server" etc.,
    Is there a place to register a "Program"?  Is this program specific to my XI server?  How should this program be created or registered.
    Any help is greatly appreciated!
    Thanks
    Satya

    one more hit:
    http://server:port/rwb/index.jsp
    message monitoring
    BTW
    you have created everything in XI repository & configured everything in xi directory haven't you?
    if not you can try this document:
    "Validating a Connection Between R/3 and SAP XI with RFC"
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/validating a connection between sap r3 and sap xi with rfc.pdf
    by Sridhar Rajan Natarajan
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • Error in SPM (RFC Destination not been Maintained)

    Hello,
    I have created a request for Super user access of a Fire fighter ID: FF_Goods Receipt and it has been assigned to a fire fighter and when he tries to login it is giving me the error as "The Destiantion XXXX has not been maintained.
    I have done the configuration related to SPM and assigned a RFC Destination in SPM Config.
    Where we have to maintain the RFC destination in SPM?
    Regards,
    Kumar Rayudu

    Hi Kumar.
    Yes we need to create RFC connection for SPM (backend System)
    Check for Post installation document
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90280209-1e57-2b10-009c-d8d800f626c5
    Regards
    Gangadhar
    Edited by: gangadhar hm on Sep 4, 2009 12:04 PM

  • Error in creating JCO Destination

    Hi All
    I want to create Adaptive RFC model and after creating JCO destinations when i am trying to execute my application I am getting this error
    Can anyone guide...
       com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 ERROR service 'sapmsB07' unknown TIME Mon Apr 23 16:01:08 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsB07' not
    found SYSTEM CALL getservbyname_r COUNTER 3
    Thanks,Arch

    Hi
    I made entries in host as well as service files .
    192.168.8.42 B0001001      # added by me R/3 System
    192.168.9.24           # Portal host
    sapmsB07     3610/tcp      # added by me R/3 Msg Server Sevice
    I changed the status to PUBLIC in r/3. it was space there.
    Now the error I got is.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:3310' not reached TIME        Tue Apr 24 11:06:51 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2764 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     1
    Thanks

Maybe you are looking for