RFC Destination (Remote Logon)is not Success

Hi All,
I have created one RFC Destination in SAP R/3 towards XI.
I have given the IP of XI and System Number
And also provided all the details like User, Pass, client Language.
After this i saved and clicked on Connect Test, it is Success.
Then now i clicked on Remote Logon. It is not going to another page, it is still showing the same SM59 page, No change......
What could be the problem
Regards
Suman

Hi Chandu,
R u getting any error in while doing the scenario?
The scenario works even it is not login into the XI Remotely.
Provide the valide username and password in the SM59 tr.code.
User need authorization to login to XI remotely. Ask the Basis guys.
If you want to remotely login ask the basis guy to create the new user and provide the user detailsin the SM59 and test it.
If you are getting any errors let me know.
Regards
Goli Sridhar

Similar Messages

  • Trusted RFC and Remote logon not possible due to Nat'd IP addresses

    Hi,
    We are trying to connect our SolMan 4 to our cusotmers ECC 6 and BI7 systems, the systems are off site and the IP addresses for the customers systems are nat'd when they come in and go out from our Network.
    The problem we get is that we cannot set up Trusted systems or Remote Logon to these systems due to issues with the Nating of the IP adresses. We can set up all standard RFC's after adding the the appropriate addresses into the hosts file and they work fine. But the trusted RFC does not set up properly and the BACK rfc from the satelite system does not get set up properly. What appears to happen is that when you try to start a remote session SAP goes to the satelite system and finds the Instance Name and the local IP address rather than the NAT'd IP address and try's to open a session from there. I found this by going into the trusted RFC in SM59 and then going to Extra's, System Information, Target System, this then tells me the Target System information, where it shows the System ID and IP address (which is the incorrect IP address).
    Anyone know how we can get the system to try to have the correct IP adress in the target system information so that we can get Remote Logon's to work??
    Cheers

    Hi Carl,
    Based on your explanation about Nating,, how will the RFC determine to connect to Solmans internal IP after it has been directed to the IP for the Router connection.
    I feel it is like configuring a jump of RFCs from one IP to another in a single chain.
    Can this be done ?? I mean we have to specify an IP in the RFC connection right.. so how will the automatic jumping of IPs be done.
    Sorry not answering the question but its very interesting and wanted to know.
    Also went trough note # 148832, might help.
    Regards,
    Kaustubh.
    Edited by: Kaustubh Krishna on Aug 13, 2009 12:17 PM

  • Live Auction's jCO RFC connection to SRM is NOT successful.

    hi to all,
    can any one help me about the configuration of RFC of live auction cockpit?
    i have followed the inst guide, but i always keep getting this message.
    RFC Error using locale en
    RFC Error using locale ja
    RFC Error using locale de
    Your RFC connection between Live Auction and SRM has failed. Please verify the following:
    Did you configure your SRM jCO setting (eg: jco.client.ashost, jco.client.sysnr etc) in Live Auction's properties?
    Is the user specified in jco.client.user property exist in SRM with the correct role and password ? Please change the user to type dialog and try to logon via SAPGUI before changing it to communication user to ensure the user is NOT locked.
    Did your SRM R3 has the code page installed that are specified in jco.client.lang ?
    Please check the J2EE engine's log file to see more details of the error. Please refer to J2EE's documentation on how to view the log files.
    thanks in advance

    Hi Ranin,
    Have you checked the note 1593439 where it mentions:
    If you are using Live Auction JAVA, you would additionally be required
    to assign the Authority object S_RFC to the RFC user being used for
    establishing a JCO connection between LACWPS JAVA Server and the SRM
    ABAP backend system with the following values. This authority is not
    needed in case you are using Live Auction on ABAP in SRM 7.0 Enhancement
    Pack 1 (SAP SRM 7.01) or higher release.
           Object            Field                Value
           S_RFC             ACTVT                16
                             RFC_NAME             BBP_LA_BIZAPI
                             RFC_TYPE             FUGR
    Perhaps this is the problem?
    Regards,
    Jason

  • RFC destination P11TPMREPL does not exist.

    Hi All,
    We are having inbound qRFC from CRM system to ECC R/3 Quality system .  The problem which I am facing is all the qRFC from CRM to ECC R/3 going into 'CPICERR' error. The error message say 'RFC destination P11TPMREPL does not exist.' .
    We are receiving this error in our Quality system and the 'P11TPMREPL' is the production RFC destination.
    I am not getting why the inbound qRFC from CRM to our Quality system is looking for production 'P11TPMREPL ' destination.
    Is anyone having idea; what is going wrong and where do I need to for RFC settings.
    Thanks.
    Shilpa

    Sorry,
    In my system IDOC got the same problem.
    I thought yours also same problem.
    There is no queue configuration, since this is a logical queue. There are no separate tables for the individual queues. For an R/3 system, there is only one table for the send queues. All entries for queues of all participating LUWs are stored in the queue table TRFCQOUT.
    and also check this table QSENDDEST.
    Thanks
    Naresh

  • Communication User Is Enough In RFC Destination Userid-Parameter

    Hi Guys,
       I Have The Rquirement Like,i have to call the remote function module which is in quality server from the development system,so for that i have created rfc destination in development system in the logon&security,i have given the userid,which was created by the basis team,this user is a communication user,not a dialog user,with this communication user, iam unable to connect to the system through program
             call function fm1 destination des.
    i would like to know whther we can conncet to the system through the communication user,or dialog user is must.please give ur valuble suggestion on this query..
                             thanks in advance...
    thanks&regards
       srinivasulu.j

    Hi Ranganath,
        Thanks For u r valuble suggestion,with the communication user given in rfc destination ,the connection is not establishing,when i click on test connection button in sm59,it is not showing any error,but when iam trying to execute form the program by calling the remote function module by giving the rfc destination,i checked in debugging,it is not connecting to the other sytem,pls provide some solution for this..
    thanks&regards
      srinivasulu.j

  • Check RFC Destination without access to SM59

    Hi,
    Typically SM59 is reserved for BASIS teams in our organization.
    Assuming there is no access( even read only) for SM59, is there a way (another tool) to test a RFC destination and check whether its functioning correctly ?
    Regards,
    Jon

    Or with SE37 test RFC_PING and input the target RFC destination (and of course not NONE as in my screen)
    Regards,
    Raymond

  • To check RFC destination

    hello All,
    Is there any function module available to check RFC destination is active or not?
    Thanks,
    Johnny

    Hi Johnny,
    You can use this FM <b>RFC_VERIFY_DESTINATION</b> if your release is greater than 4.6C.
    Check this sample code from Craig Cmehil's weblog.
    CALL FUNCTION 'RFC_VERIFY_DESTINATION'
      EXPORTING
        DESTINATION = TMP
            TIMEOUT = 10
      EXCEPTIONS
        INTERNAL_FAILURE           = 1
        TIMEOUT                    = 2
        DEST_COMMUNICATION_FAILURE = 3
        DEST_SYSTEM_FAILURE        = 4
        UPDATE_FAILURE             = 5
        NO_UPDATE_AUTHORITY        = 6
        OTHERS                     = 7.
      IF SY-SUBRC EQ '0'.
        "* Do code here
      ENDIF.
    or you can also use this FM <b>RFCPING</b> and check this sample code from other thread.
    DATA : IT_RFCSI LIKE RFCSI OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'RFC_PING' 
      DESTINATION IT_SLS-SYST
      EXCEPTIONS
        SYSTEM_FAILURE = 1
        MESSAGE RFC_MESS1
        COMMUNICATION_FAILURE = 2
        MESSAGE RFC_MESS1.
    IF NOT RFC_MESS1 IS INITIAL.
      MESSAGE I000(YHPA0K) WITH RFC_MESS1.
    ELSE.
      CALL FUNCTION 'RFC_SYSTEM_INFO'
         DESTINATION IT_SLS-SYST
         IMPORTING
           RFCSI_EXPORT = IT_RFCSI
         EXCEPTIONS
           COMMUNICATION_FAILURE = 1
           MESSAGE MSG_TEXT
           SYSTEM_FAILURE        = 2
           MESSAGE MSG_TEXT.
      MESSAGE I001 WITH 'Connection to '(029)
                        IT_SLS-SYST
                        'Succeeded'(030).
      ENDIF.
    ENDIF.
    Hope this will help.
    Regards,
    Ferry Lianto

  • RFC Destination not getting connected - IDoc to XI scenario

    Hi Everybody,
    I want send an IDoc from R/3 System to Xi, I have created Two logical systems (Sender and Receiver correspondingly) and i have assigned the clients to them.
    Once i create RFC destination, i have specified all my technical settings as well as Login/Security settings, once i click, "Remote Log On" it takes me directly to Login page of XI. Please guide me how to solve the problem. If i click Test---> Authorization, it prompts out with an error "Name and Password is incorrect (repeat Logon)", but i have given exact username and password.
    I am a fresher to XI.... please give me some documents related to IDoc to XI scenario step by step to [email protected] I would be grateful and appreciate you if u would help me to sort out this problem....
    Please give me step by step solutions.... Thanks in Advance...
    Regards/Guru

    Requirements in R3 system:
    1. Create RFC destination pointing to XI in SM59
    2. Create port for XI using we21
    3. create Outbound Entry in partner Profile for XI in we20.
    Requirements in XI system:
    1. Create Technical System pointing to the R3 system.
    2. create Business System pointing to the R3 system.
    If you want to send IIDOC out of XI,
    1. SM59 - Create RFC destination
    2. IDX1 - Create port
    3. IDX2 - Import Metadata.
    Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
    Check dis link for more info:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    please refer to michel book on IDCO usage in XI
    Message was edited by:
            Sreeram Reddy

  • Calling Remote enabled Function module in java using RFC Destination

    Hi
    We are on Portal 7.3 ehp1 sp9.
    Steps followed are :
    RFC Destination called “SAP_RFC” has been created as below :
    Configuration -> Destinations -> RFC Destinations
    Connection and Transport:
    Load balancing :Yes
    Provided : SystemID / MS Server / MS Server Service / Logon Group / Gateway Host / Gateway Service
    SNC : Inactive
    Logon Data:
    Authentication : Current User (Assertion Ticket)
    Language : EN
    Client : XXX
    Repository Connection:
    Destination Name : This Destination
    Specific Data:
    pooled Connection Mode : Yes
    Max : 5
    Size : 10
    Max. wait time : 10,000
    Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.
    JAVA Code as Follows:
    JCoDestination destination = JCoDestinationManager.getDestination("SAP_RFC");
    //destination.ping();
    JCoRepository repository = destination.getRepository();
    JCoFunction function = repository.getFunction("FM_NAME");
    function.execute(destination);
    Lines highlighted in RED color throwing an error as below :
    {"ERROR":"Initialization of destination JCO_RFC failed: Incomplete logon data. on <SID> mshost <MS_HOST>/ com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Incomplete logon data. on SID mshost MS_HOST"}
    And found that no COOKIE with the name “SAP_SESSIONID_<system>_<client>” was not found, I am afraid that “Assertion Ticket” was not created in above scenario.
    To confirm SSO configuration working, i have followed below steps:
    1) Created System Object pointing to R/3 and tests were successful for authentication type "SSOLOGONTICKET / ASSERTIONTICKET"
    It's J2EE application, no references or any other additional configuration been made part from above.
    Any help ?
    Thanks

    Here is log ..Assertion ticket could not be retrieved. Error was null
    Log Record Details
    Message:
    Assertion ticket could not be retrieved. Error was null
    Severity:
    Error
    Date:
    2014-04-23
    Time:
    20:28:26:056
    Category:
    /System/Security/destinations
    Location:
    com.sap.security.core.server.destinations.service.AssertionTicketRetriever
    Application:
    Thread:
    System [2]
    Data Source:
    j2ee/cluster/server0/log/system/security_00.log
    Arguments:
    Passport User Activity ID:
    3a7af5ddca8b11e384bd8adb6f484d33
    Message ID:
    Session:
    Transaction:
    User:
    Time Zone:
    +0800
    Customer Message Component:
    BC-JAS-SEC
    Runtime Component:
    tc~sec~destinations~service
    Correlation ID:
    3643650000002747
    Passport Session:
    3A7AF5DDCA8B11E384BD8ADB6F484D33
    Passport Connection:
    3a7af5ddca8b11e384bd8adb6f484d33
    Passport Connection Counter:
    0
    Log ID:
    C0000AD01D7B002200000EA5009800B2
    Host:
    host
    System:
    XXX
    Instance:
    J00
    Node:
    server0

  • RFC destination not working

    Hi,
    I have created a RFC destination in my XI system to connect to another system. But when i try Remote logon, it is not working. I have specified all the required details. Can anybody tell me what is the problem?
    Regards,
    Divija.

    Hi Divija,
    If your RFC user is not a dialog user, then you will not be able to log on to the system in the dialog mode. The remote log on will fail in the dialog mode. However, when you use an RFC call, there will not be any problems.
    Have u given the user id and client details...
    Press System Information->Target information and check if it is giving u information of ur destination system only.
    Also see if u have mentioned the host/port number correctly in SM59
    I hope u have connection type set to 3 in technical settings, SAVE AS IP address and enter IP address in the Target host.
    Load distribution should be set to NO.
    Another option go to ST05 and select RFC trace and execute the RFC and then disply the trace.
    Also go through these links...
    http://help.sap.com/saphelp_nw2004s/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
    I hope it helps.....
    Regards,
    Abhy

  • RFC- Remote Logon

    Hi,
    I am trying to create an RFC destination to XI in SAP 4.7 I entered the host correctly and other logon details.But when I press Remote Logon system is not executing the RFC Destination.Can any one put some ideas why the system is not executing the RFC Destination.
    ---Sudheer

    Sudheer,
    "But when I press Remote Logon system is not executing the RFC Destination"
    .....Means its working fine.
    Also if you just want to make sure...try to logon to XI system using same userid / pwd.
    Hope this will help.
    Thanks,
    Nilesh

  • An RFC destination could not be specified for the logical system

    Hello Experts,
    I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
    An RFC destination could not be specified for the logical system
    SB3CLNT011
    Message No. B1550
    Diagnosis
    An RFC destination should be specified for the logical system SB3CLNT011.
    This could not be done in this case. SB3CLNT011 is not your local logical system
    and this system is not included in the relevant Customizing tables.
    Procedure
    Check:
    RFC
    destination
    Port
    definitions
    oubound partner profile of
    message type SYNCH for this logical system
    Regards,
    Khushboo

    Hi Oritra and Suraj,
    I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
    Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
    System SB3CLNT011 as a partner type already exists
    System SB3CLNT012 as a partner type already exists
    Port A000000018 with RFC destination SB3CLNT011 already exists
    Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
    Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
    Outbound parameters for message type SYNCH SYNCHRON already exist
    Am I missing something in WE20?
    Regards,
    Khushboo

  • Remote Logon Tab does not work

    Hello All,
    We have a standard ABAP RFC Connection from our Dev system to our Prod system. We have maintained the connection with a Dialog user and the connection tests and authorization tests works fine. However when i test the 'Remote Logon' tab , nothing happens. We do not have an error message as well. So I turned on the RFC trace and the entries in the dev_rfc and dev_rd are as below;
    Dev_RFC:
    **** Trace file opened at 20140708 115142 AUS Eastern Standard Time, SAP-REL 640,0,414 RFC-VER 3 1368070 MT-SL
    >>>> [1] SID          : R/3  <ac: 844> K 10.200.1.31 >>> CLOSE abrfcio.c 2679 (86262062)
      -{E3128536-7394-41B0-9DD0-FDE742DFD323}
    ==== Delta HO 0,  0 LOG DROPPED
    DEV_RD:
    *** trace for connection 6 enabled ***
    GwIHandleRq: own_index: 0
    GwIHandleRq: set act rq type DEALLOCATE
    R3DEAL(86262062, cpic_vector=0, ..)
    I am the client (0)
    R3DEAL: state of conn/index 6/0: RESET
    R3DEAL: send return code to cpic partner
    GwISendRc: send appc_rc/sap_rc/status 18/0/0 to conn/target/client 6/1/20
    GwGetMemory: allocated 000000000BCE6000 (len=192)
    GwGetMemory: act_overflow_size = 460 (+ 192)
    GwSetCPICState: state of conn/index 6/1: RESET
    GwSendToClient: send data to conn/target/client 6/1/20
    OUT:
    ReqType     : CPIC         SysIdx  : 20     ReqLen  : 80     ReqId   : 0
    CommIdx     : 13           ConnIdx : 6      ReqVer  : 6      Trace   : 0
    conn        : 6            wp_no   : -1     ReqBlk  : -1
    RqType      : SAP_SEND     Prot    : INT    UID     : 31769  Mode    : 0
    User        :              SapRc   : 0      AppcRc  : 18     ConvId  : 86262062
    Vector      :
    Info        : SYNC_CPIC_FUNCTION
    Info3       : GW_WITH_CODE_PAGE
    NiIWrite: write 80, 1 packs, MESG_IO, hdl 23, data complete
    GwFreeMemory: free 000000000BCE6000 (len=192)
    GwFreeMemory: act_overflow_size = 268 (- 192)
    GwSendToClient: 80 bytes send to conn/target/client 6/1/20
    GwSendToClient: decrement conv_no of client 20: 0
    GwFreeMemory: free 000000000BCE4000 (len=268)
    GwFreeMemory: act_overflow_size = 0 (- 268)
    GwIDelR3Conn: idx/conv = ((0/0) | (-1/0)), delete conv 6 from conv-table
    GwClearConn: conv_no/tcp_conv_no/sna_conv_no: 3/3/0
    GwClearConn: free r3 conv info
    GwClearConn: free buffer info
    GwFiSearchConvId: deleted 86262062 local, conn=6
    GwListInsert: insert elem 6 into conn_free_list (at begin)
    GwListInsert: 497 elems in conn_free_list
    GwListRemove: elem 6 not in conn_search_list
    GwListRemove: elem 6 not in conn_write_list
    GwListRemove: remove elem 6 from conn_inuse_list
    GwListRemove: 3 elems in conn_inuse_list
    *** trace switched off ***
    There are no error messages in ST22 and SM21. After reading a couple of posts in SDN; I changed the password of the dialog user to a password consisting only of alphabets and upper case only but that did not help either.
    I did go through the SAP Notes ; 704206 and 189077 , however we are not using a saprouter string for the connection. We are using the local gateway connection.
    Point to note is that the same RFC connection which we have also set up in our Quality system gives us the remote log in prompt.
    I also checked the hosts and services files on both the servers and both seem to have the same entries.
    System Details:
    Release - 620
    Kernel Patch - 640 Patch 414
    Please do share if you have any ideas on how to resolve the issue. Do let me know if you need additional information.
    Thanks
    Surajit

    Hello Adil,
    Appreciate your feedback on this.
    Our network team confirms that the set up between Dev and Prod is exactly same as the set up bw QA and Prod. As the connection bw QA and Prod works , they are suspecting some other area to be the cause of this issue.
    Thanks
    Surajit

  • RFC Destination could not be created  in TREX administration tool

    Hi All,
       Recently i installed the TREX server, I am trying to connect the ABAP system with the RFC connection. I entered all necessary data for the RFC connection it giving error as
    RFC Destination could not be created.
    To solve the above problem i created one RFC connection of type TCP/IP in ABAP server eventhough it is not solved.
    Can i have the solution  for the above problem?
    Regards,
    Vivek.

    Hi Michale,
        Thanks for your quick response; I tried all the mentioned possibilities in that help document, still i am facing the same problem.
    It is giving the below error
    Connect to SAP System failed.Possible reasons:
    -Logon data incorrect
    -Password is not uppercase(must also be uppercase)
    -SAP system user locked
    -SAP user not in specified client
    -SAP User rights are insufficient
    -SAP system not reachable
    -saprfc.ini unavailable or entries incorrect
    -TREXTcpipClient.ini section[communication],parameters rfcdestination, sapsystem not set
    -SAP system Basis component below 6.20 or SP too low
    -->check also latest TREXTcpiplient trace file entries.*
    The above all are check by me everything is fine.
    The below information from the saprfc.ini file
    DEST=NPI
      TYPE=B
      MSHOST=server1
      GROUP=server1_group*.
    Is there any mistake, please let me know.
    Regards,
    Vivek.

  • RFC destination Could not be SPecified for Logical System

    Hello there
    i am traying to costomize Transaction Luancher for some of the report which is been devloped in ECC (wich is ARD 100)
    when  on Transaction launcher Wizard--> techincal
    i am  having a  logical system as ARD100(my r.3 system where report is devloped and which is connected to CRM )
    while chosing the OBJ.TYpe :   and Method:
    it says shows three erroe :
    1) RFC destination could not be specified  for the logical system ARD100
    2) Object type and Method is not available
    i have checked RFC  , in  SM59 entriesu2026u2026 There is an RFC named ARD100 and the connection test works. I also did an authorization test and it also works. I also checked to make sure the logical system name ARD100 exists
    could you please help me to resolved the same
    Regards
    Rajiv

    Hi Rajeev,
    In a system landscape it's important and necessary to use the logical system names consistently throughout all systems!
    Therefore please make sure, that you always use the same name for a logical system in all systems (CRM and R/3 systems).
    The following steps are required before a RFC call is made from the CRM system to the R/3 system :
        o  Use transaction SM59 to create an RFC destinations for the remote
           system.
        o  Use transaction BD54 to create the logical system.
        o  Use transaction BD97 to link the RFC destination created in SM59
           with the logical system created in BD54.
    I hope this helps.
    Best Regards
    Gavin

Maybe you are looking for