Help reg RFC Destination

Hi Folks,
    I have send send IDoc from XI system to R3 system. For this I am creating RFC Destination in XI system using txn SM59. Also the name of RFC Destination in XI is same as Logical System Name in R3 system for that client.
  After creating RFC Destination I did 'Test Connection' , which was successful. But on doing 'Remote Logon' it in neither giving any error nor opening Remote Session.
  Can anybody tell me why remote session is not opening?
Thanks in Advance.
Swamy

Hi swamy,
if it does not open the remote session the reason is that the user you are using is a non dialog (correct) user so it cannot logon in dialog mode but is used for communications.
To check if the logon parameters (user/pwd) are correct use from the menu  of SM59 test->authorization.
Regards,
Sergio

Similar Messages

  • Service desk RFC destination in the Satellite system

    HI All,
          can any body tell me the RFC destination that is to be maintianed in the satellite system so that the message reaches the solution manager service desk.
    I am creating messages they are being send to the service desk successfully but are not visible when I go into the service desk of the solution.
    But they are visible through the transaction code CRM_DNO_MONITOR .Can any body help the RFC destination to be maintaned in the BCOS_CUST table so that the message reaches the Service Desk.]
    Currently I am using the RFC destination to the service desk client in the solution manager ie SIDCLNT200
    Thanks in advance
    Regards
    Amit

    Hi Amit,
    I think your expectation is not correct. I understood, you can create a message in a satellite system and you can see the ticket in SolMan service desk. Then everything is configured correct. What you are now looking for is to see the ticket in a solution when the sat. system is part of the solution. This is not working. If you create out of a solution a service desk ticket, these ticket get a special attribute that they belong to this solution, all other tickets can not be selected by a solution.
    Sorry but I am quite sure that it is working like this.
    There is only one option, that you define special variants so you can see only tickets from special systems, but these variants can not be assigned to a solution.
    Regards,
    uDo

  • Help with RFC sender, Program And RFC Destination

    Hi!!
    my scenary is asynchronous
         RFC Sender -> SAP-XI -> Oracle reciever
    I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI  receive the message but the message is empty.
    1. In my program on the line
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
    2. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
    3. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
    What is my Error?
    Where am i making a mistake?
    RFC
    FUNCTION zbapi_sd_ped_ord_servic.
    *"Interfase local
    *"  TABLES
    *"      PED_ORDEN STRUCTURE  ZSD_RFC_T04
    *"      RETURN STRUCTURE  ZSD_RFC_R06
      TABLES: zsd_ped_orden, zsd_rfc_r01.
      DATA: tb_ped_orden LIKE zsd_ped_orden  OCCURS 0 WITH HEADER LINE,
                     tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
    *Get Pedido by Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
              FROM zsd_ped_orden
              WHERE estatus  EQ  space.
      LOOP AT tb_ped_orden.
        MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
        APPEND ped_orden.
        tb_ped_orden-estatus = 'X'.
        tb_ped_orden-fecha_actualiz = sy-datum.
        tb_ped_orden-hora_actualiz = sy-uzeit.
        MODIFY tb_ped_orden.
      ENDLOOP. 
      MODIFY  zsd_ped_orden FROM TABLE tb_ped_orden.
      COMMIT WORK.
    *Errors in Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
              FROM zsd_rfc_r01
              WHERE estatus  EQ  space.
      LOOP AT tb_rfc_orden_error.
        MOVE-CORRESPONDING tb_rfc_orden_error TO return.
        APPEND  return.
        tb_rfc_orden_error-estatus = 'X'.
        tb_rfc_orden_error-fecha_actualiz = sy-datum.
        tb_rfc_orden_error-hora_actualiz = sy-uzeit.
        MODIFY tb_rfc_orden_error.
      ENDLOOP.
      MODIFY  zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
      COMMIT WORK.
    ENDFUNCTION.
    PROGRAM
    REPORT  ZBAPI_SD_PED_ORD_SERVIC.
    DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
          return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
         TABLES
              ped_orden             = ped_orden
              return                = return
      EXCEPTIONS
        communication_failure = 1
        system_failure        = 2
        OTHERS                = 3.
    IF sy-subrc <> 0.
      MESSAGE 'error' type 'I'.
    ENDIF.
    COMMIT WORK.
    RFC DESTINATION
    RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
    Connection TYpe: TCP/IP Connection
    Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
    Gateway host: host00
    Gateway service: sapgw00

    hi
    For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
    a) RFC destination
    b) RFC channel in the XI directory
    This weblog is a response to a few question about the basic configuration of the RFC sender adapter
    that were posted on the XI forum (and also on my e-mail)
    So here we go, basically we have to configure 2 things:
    a) RFC destination
    b) RFC channel in the XI directory
    RFC destination:
    1. To create the RFC go to TCODE: SM59
    2. Create new destination of type T (TCP/IP)
    3. Make sure you select Registered Server Program option before writing your program ID
    4. Write you program ID (remember it's case-sensitive)
    5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
    7. No configuration in the J2EE administrator nessecary
    Now we can proceed to RFC channel configuration:
    1. Enter your Application Server
    2. Your Application Server Service
    3. Enter your Program ID from the RFC destination
    And we're done:)
    Now you can test the RFC destination in SM59 to see if it works.
    Please chk this following link.
    1. RFC Processing with the RFC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
    2. Configuring the Sender RFC Adapter -
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    3.  /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    regards
    Manas

  • RFC Receiver Adapter and RFC Destination -- Help

    Hi,
    I would like to configure the RFC Receiver Adapter for the invokation of a RFC on SAP System (Name: ALPHA) using a RFC destination provided by another system named BETA.
    I have set External Server as server type.
    My first question is: I have to quote an application server gateway and a gateway service. Is this information related to a service on ALPHA or BETA?
    My second question is:
    It is also necessary to provide a Programm-ID. The destination on BETA is a R/3 connection and doesn't have a programm id. Where do I get this from?
    And my last question is:
    Is at all possible to use the RFC destination on BETA?
    Any help is really appreciated...
    Kind regards,
    Heiko

    Hi Heiko,
    I don't fully understand your need but:)
    since both of your systems are SAP systems
    why are you trying to use external server?
    can't you just call RFC on BETA
    and inside this RFC on beta call RFC on ALPHA?
    in a sync or async way?
    can you tell a little more about your requirement ?
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • RFC Destination with other Environments and Execute. Please help

    Hi GURU,
    I have a problem and I would like your help.
    I'm new at Abap and I'm trying to develop an application from ABAP to connect to an environment of java.
    I watched how to do this in various forums and the help of SAP, but just as I have found make the connection.
    In java I have already developed the server side and I have developed a ABAP function. But is not exactly how it works.
    Can you give me an example of how to send data from the sap application to java? Or give me any manual please.
    Another problem is,
    As I record the RFC destination?
    When I run a BAPI ABAP occurs to me the following error:
    RfcExecProgram'#Win32 error 2
    Because it can be?
    Thank you very much in advance
    RAFA

    The (Alesis Digital Audio Tape) ADAT optical I/O gives 8 channels up to 48Khz 24bit and 4 I/O at 88.2, 96 Khz... this are the technical specifications for this connectors!
    http://www.nationmaster.com/encyclopedia/ADAT
    If you need to use 8 ADAT I/O at 88.2/96 you need to buy device such as
    Yamaha MY16at (for Yamaha Digital Mixer) http://www.studiocare.com/store/index.php?mainpage=product_info&productsid=62346
    and similar devices
    ... or Motu 828MK3 that comes with 2X ADAT I/O....
    Motu 828MK3 is able to work with up to 8 ADAT channels at 88.2/96 and up to 16 ADAT I/O at 44.1/48.
    BUT... Apogee Ensemble comes with only 1X ADAT I/O... so you can use up to 4X 88.2 I/O channels and you need a second Ensemble unit for reach 8 ADAT I/O.
    Optical connectors can be used also for 2 I/O at 192Khz...
    in this case this kind of connection will be named as TosLink, even if it uses the same ADAT plug.
    cheers
    G

  • 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

  • Logical system and rfc destination

    hello all,
    what is the difference between logical system and RFC destination?
    thanks for ur help in advance.
    regards,
    vikas

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Regards

  • How to create a RFC destination for extracting data to HANA

    Hello All,
    Could someone help me in providing a document or note on how to create a RFC destination for extracting data from SAP data source to HANA using SAP LT replication server ?
    I am able to create a data base connection while transforming data from non SAP data source,but wasnt able to transform data which is from SAP abap tables .

    Hi Venkatesh,
    In SM59 t.code we create RFC destinations.
    Go thru the video link for creating RFC destinations step by step
    How to setup a trusted RFC connection between SAP systems: a step-by-step guide - YouTube

  • Unable to change RFC destination in IT Performance reporting wizard

    Hi Experts,
    I am setting up IT Performance Reporting in my Solman EHP1 system. In the first page of the PErformance reporting wizard, it asked me for RFC destination from BI to Solman(1st field) and Solman to BI (2nd field). I initially entered an existing RFC destination that we are already using in a separate application that has a user with very-limited authorization. Now, I am trying to change the RFC destination by running the same "Configure IT Performance Reporting" wizard but both fields are already GREYED out.
    I tried deleting the RFC destination previously defined in an attempt to reenable the fields but only the 2nd field was enabled. When I try to continue the setup, it results into a Shortdump because it is still looking for the initially defined RFC dest which is defined in the 1st field that cannot be edited.
    SAP has not yet provided us with a solution.Your help is greatly appreciated.
    Thank you very much.

    You canprovide the RFC destination in DOE administration portal. Goto Configurations link and search for "BACKEND DESTINATION" parameter in "BACKEND CONFIGURATION" link. Here you can provide RFC destination at SWCV level or at Data object level.
    After deleting RFC destination in SM59, it will never take you to backend system.

  • Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist

    Hi Experts,
    I have one standard ALV report in ABAP Webdynpro.
    When i try to print the ALV Report it gives Communication failure : RFC Destination SALV_WD_EXPORT_PDF does not exist.
    Can you give solution for this one.
    Regards,
    Sri

    Hi Sri
    Please go through this..
    /people/bv.pillai/blog/2007/01/09/webdynpro-abap-alv-print-versionpdf
    also Have a look this note SAP NOTE 918236; you will need help from basis.
    Cheers,
    Kris.

  • Error in Local Message System: RFC destination MB3AP1039 does not exist.

    Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
    Message no. BCOS088
    Hi,
         When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
    Can anyone help me in resolving the above issue.
    Thanks & Regards,
    Mirza Kaleemulla Baig.

    Dear friend
    You have to of following option
    1.Define Service Desk destination in the R/3 systems:
    Note: for this you need to log in the R/3 system.
    Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
    2.a. Go to transaction SM30.
    b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
    c. Press the Continue button in the following screen:
    d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
    e. In the next screen, enter the following information:
    In the RFC Destination you should point to your Solution Manager destination RFC.
    0ss_msg   w   sm_bsmclnt_back    cust620     1.0
    shailesh

  • RFC destination BW could not be created in the source system R3073

    I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
    RFC destination BW could not be created in the source system message number R3073
    Why is this happening? The connection tests just fine.
    I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
    Any ideas?
    thanks

    Hi,
    I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
    Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
    Create your BWDEV RFCDEST manually in your BWQA .
    Perform test and authorization test within SM59 from both sys.
    When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
    hope this helps...
    Olivier.

  • 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

  • RFC destination error in posting 3rd party payment in 4.7 FI system

    Hi,
    We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
    The error says "An RFC destination could not be specified for the logical system HD1CLNT014
        Message no. B1550
    Diagnosis
        An RFC destination should be specified for the logical system
        HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
        local logical system and this system is not included in the relevant
        Customizing tables.
    Procedure
        Check:
            -   RFC destination
               -Port definition
             -oubound partner profile of message type SYNCH for this logical system
    We checked our configuration for all Logical system and RFC destination and everything seems fine.
    Any help in this regard is appreciated.
    Thanks
    Kesav

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

Maybe you are looking for