RFC destination getting created

Hi All,
I am creating scripts using SAPGUI command in the target system. The source system is WAS6.20 and the target system is 6.40. Whenever i create a recording using SAPGUI, an extra RFC destination is created with following naming convention:
ECATT_SAPAPO_<client no>_<logon language>_<session ID>.
Why is it so, even when i have a system data container with the target system RFC.
Kindly clarify.
Thanks in advance.

>
srinivas_1984 rao wrote:
> Hi All,
>
> I am creating scripts using SAPGUI command in the target system. The source system is WAS6.20 and the target system is 6.40. Whenever i create a recording using SAPGUI, an extra RFC destination is created with following naming convention:
> ECATT_SAPAPO_<client no>_<logon language>_<session ID>.
> Why is it so, even when i have a system data container with the target system RFC.
>
> Kindly clarify.
>
> Thanks in advance.
Hi Srinivas,
After recording using SAPGUI method in the target system,are you getting the automated script in this format?
SAPGUI ( va01,va01_1).
If you are gettign the second half part as shown in bolded above,then please do the following.
1)Make a copy of the existing script for backup reason.
2)Do the below changes after backup.
   a) Delete the second half part---which is shown as bolded.then your script would be looking like
      SAPGUI ( va01).
   b)Double click on the remaining part and parameterize.
   c)Maintaing the required system information in System data contianer.
   d)In the script mention on the attributes tab,mention the target system on which script needs to be executed.
Hope this info helps.
Regards,
SSN.

Similar Messages

  • RFC destination of receiver system

    Hi Guys,
    I am trying to do the shell creation from scracth, and now i have found on the RFC destination creation there are three RFC connection which needs to be define. But my question is in this step we dont have any receiver system becasue export files has not been generated yet that will come after this step, so how can i proceed.
    Regards,
    Subhash

    Hello Subhash,
    In the step 'Define RFC Destinations' you create the RFC destinations for the SAP systems that participate in your project (or subproject).
    Yes, you are correct, since the target/receiver system is not yet created, you cannot establish a RFC for the same.
    Please proceed by maintaining the following:
    Server name, System number , Language, Client, Username and Password  for the control and the sender system.
    Best Regards,
    Mridu.

  • ** End-to-End Monitoring - RFC destination error while save config in RWB

    Hi Friends,
    We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
    We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
    Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
    I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
    For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
    There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
    There is no PIRWBUSER in the Sender/Receiver System.
    In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
    So, what could be the problem for the above error?
    Could you kindly clarifiy friends.
    Thanking you
    Kind Regards,
    Jeg P.

    Hi friends,
    I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for  XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
    In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
    Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
    When we save configuration, an one more destination is automatically created in the name as below.
    PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207. 
    When we test  newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
    The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
    Name or Password is incorrect (repeat logon) - PMIPID00120080207
    But, still remote login is possible in the old RFC destination using the PIRWBUSER.
    So, What could be the problem ...?
    Kindly reply, friends.

  • NO RFC Destination for BAPI

    Hi,
    I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
    BUS6010 Method POST & CHECK
    BUS2072 Method FINDDETAILS
    I am using the Program RHINLV00_LSO to transfer data.
    When i execute this report it's throwing an error
    " NO RFC Destination for 2 BAPI's".
    An RFC Destination is created in SM59 to link the  two systems and i have distributed the distribution model to R/3 4.7.
    The Function modules are marked as Remote enabled function modules.
    Regards,
    Ramesh K.

    Hello,
    Did you test RFC destination whether the definition is working fine or not?
    You can test the destination,if it's working fine,then Bapis' should be able to execute.
    Thanks.
    Mark points if helpful.

  • NO RFC Destination for BAPI's

    Hi,
    I am working on ALE for Activity allocation. I am using 3 methods in my distribution model. I need to transfer data from ECC 6.0 source system to R/3 4.7.
    BUS6010 Method POST & CHECK
    BUS2072 Method FINDDETAILS
    I am using the Program RHINLV00_LSO to transfer data.
    When i execute this report it's throwing an error
    " NO RFC Destination for 2 BAPI's".
    An RFC Destination is created in SM59 to link the two systems and i have distributed the distribution model to R/3 4.7.
    The Function modules are marked as Remote enabled function modules.
    Regards,
    Ramesh K.

    Hi,
    After creating the distribution model with 3 methods in ECC 6.0 (source system). Generated Partner profile automatically from BD64. Then distributed the distribution model to the other system i.e., SAP R/3 4.7 successfully. Then created partner profile from that system automatically.
    Port, partner profiles,outbound parameters, inbound parameters were created successfully.
    Thanks
    Ramesh

  • PI System Copy (JCO RFC destinations missing)

    Hi,
    We are doing a Homogeneous System Copy of a PI 7.0 system:
    - Source system --> PI 7.0 Production system ("PIP")
    - Destination system --> PI 7.0 Development system ("PID")
    We are executing the specific POST activities for a PI system (point 5.2.3.2.4 in the "System Copy for NW2004s SR2 Abap+Java" guide). In point 5.2.3.2.4.2, PI RFC destinations must be adapted in both Abap (SM59) and Java (Visual Administrator, JCO RFC Provider). The problem is that in all PI abap RFC destinations (AI_RUNTIME_JCOSERVER etc) the program_id is pointing to our PI
    Production system ("AI_RUNTIME_PIP"), is it OK?
    Besides, in Visual Administrator (JCO RFC Provider service), all the required RFC listeners for PI ("AI_DIRECTORY_PIP", "AI_RUNTIME_PIP", etc.) are missing after the system copy (???). Must these RFC listeners be manually created? How can we do it? Must we create them with the development SID ("AI_RUNTIME_PID") or with the production SID ("AI_RUNTIME_PIP")? Perhaps PI configuration wizard must be executed after the system copy of a PI system so that these JCO RFC destinations are created, but we are afraid executing the wizard could harm the PI configuration...
    Thanks in advance.
    Jon Larrucea

    Hi Jon
    Probably the best thing to do is just create these destinations manually. You will need to do this in SM59 and the Visual Administrator. See the link below:
    Creating RFC Destinations in the ABAP and Java Environments 
    http://help.sap.com/saphelp_nw70/helpdata/en/be/6e0f41218ff023e10000000a155106/content.htm
    Regards
    Mark

  • 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...

  • 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.

  • 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

  • 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.

  • 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

  • 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......

  • Session created by RFC Destination don't close.

    Hi Experts
    I create an RFC Destination in NetWeaver 7.2, and i use this destination to access some RFC from CAF project.
    The problem is when i access the RFC, the ECC create a session to the user and don't close this session.
    After some time i have a lot of session created in ECC. The session in ECC should be closed, because i get some error when there are a lot of session with the same user opened in ECC.
    I create the destination in NWA - Destination.
    Could someone help to solve this?
    Regards
    Marcos Brandã

    Not anwsered.

  • 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

  • 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

Maybe you are looking for