Logical system name vs. destination name - CUA -

Hey experts,
at the moment I´m thinking about using the CUA in our SAP environment for role distribution.
In this scenario I need destinations to the child systems (of course!). In all manuals I found it say, that i HAVE to create destinations which have the same name as the logical system. However, this is not possible cause this is against corporate name conventions.
So I tried to use different destination names, but when I use the function "text comparison" (SU01->Roles) it always fails and says that the destination to the child system is missing.
So here my question: How can I tell the CUA not to search for destinations named like the logical system????
Thx in advance, nice weekend
Oliver

Hey John,
piece of cake ;).. that's what I thought at first. Unfortunately it´s not that easy. This is because of  partially really strict restrictions within the SAP-Software.
At the one Module, you can choose the destination, is used for a particular group of functions. At the next, you simply can´t. SAP says "you need to have a destination, named as the logical system name". And there is no way around.
Maybe I´am the first guy being disturbed by this "feature"....
Of cause, I already placed several posts within the basis section... but still.. no way around. In one case I even opened a ticket at SAP... (I already posted the answer above) ....
Thx anyways!
Oliver

Similar Messages

  • 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

  • Logical system and rfc destination related Query?

    Hi Dudes
    Do we need to define logical system and RFC destination if they are in different clients in same server
    Regards
    Raj Kumar

    Hi
    Both are client independent setting, so even if you define in one client, it would be available in other clients also.
    Regards,
    Sanjeev

  • Assigning logical system to a client in CUA

    Hi All,
    I have got a doubt in the basic configuration in the setup of CUA.
    I have performed all the steps that is given in the CUA cook book.
    In, assiging the logical system to a client, whether this step shoud be done only in the central system alone.
    Or the assignment should be done in the child system also.
    When i created the all the steps in central system, logical system is created automatically in child system. but in the client assignment i didn't find information. in cookbook also they have do it in all the SAP system.
    kindly advice.
    Thanks and Regards,
    Subhashini.

    >
    > So creating clients in Central system is enough for the child system.
    The term you used "Creating Client" is technically wrong in this regard. You already have a client which is in use as Central system - right? You need to maintain the details of Logical system names of all the Child system in Central system to keep the central system updated with the knowledge of type and name of the Child systems it has. This definition can be done by using TCode BD54 which is table maintenance view ( V_TBDLS ) of the table TBDLS.
    There is nothing to do or even can be done like Creating Client within a client (here your central system).
    > Since there is noe transfer of user master from child to central system no need to create a client for the logical system.
    >
    Its true that there will no transfer of user master from child to central system. But of course the similarly here you are not creating any client within the child system. You are just creating the logical system name (tcode BD54) for this client (child system) and mapping it with the client in tcode SCC4.
    Let us know your question. Also as suggested by Barnherd, please go through the SAP Help documentation on CUA. Also try to get an overview of Client in SAP (from SAP Help or SAP course ADM100) and Logical Systems.
    Regards,
    Dipanjan

  • Confusion in Logical System, port & RFC Destination

    hi,
    I have still few doubts regarding Logical System, port and RFC destication
    My SAP ECC6.0 and XI configuration is:
    For ECC 6.0 : Logical system name : T03CLNT400
    Client : 400
    RFC Dest : XIDEST
    Port : XIPORT
    For XI 3.0 : Logical System name : WXI
    client : 400
    RFC Dest : ECCDEST
    Port : SAPEC3
    now my confusion is, in t-code WE19, when sending IDOC to XI (idoc - file scenario), which entry i've to use in prot and Partner No in Receiver side and which port and partner no i've to use in Sender Side.
    also in XI side when creating Technical sys for web as ABAP which logical system name i've to use and in File to Idoc Scenario which logical system i've to use as sender business system (third party file business system)
    If possible please give me detail idea to clarify my cofusion.
    thanks
    ritesh

    Ritesh,
    <b>now my confusion is, in t-code WE19, when sending IDOC to XI (idoc - file scenario), which entry i've to use in prot and Partner No in Receiver side and which port and partner no i've to use in Sender Side.</b>
    If you are sending from R3 then give the sender details as R3 and the receiver side as XI where you have created the port from R3 to XI etc.
    Check this help for clear understanding on all this settings:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
    Also can you check this weblogs on the same:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    ---Satish

  • Logical System and Logical System Name

    Hi,
       I would like to create the following  and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
    Creating a port(I suppose I need to do this on the R3. What are the steps involved)
    Create a Partner Profile

    Hi Sonia,
    For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
    just go through the following steps and Configure ALE :-
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    Regards,
    Ashwin M
    Reward If helpful

  • RFC destinations for CUA - clarification required.

    Greetings, Gurus!
    I'm in the planning-going-testing phase of CUA implementation for our landscape, and it appears I've run into something of a snag.
    According to everything I've read, including various SAPnotes and documentation available in SAP Library, I understand that it is not possible to configure the CUA to use specific RFC destinations. Instead, CUA will attempt to use an RFC destination that has the same name as the logical system it is calling. I.e. central system ADMCLNT070 is making an RFC call in context of CUA to PRDCLNT510, for this purpose, RFC destination named PRDCLNT510 will be used.
    Q1: Have I understood this correctly?
    Q2: Is there any way to specify an RFC destination I want to use?
    Thanks for your time!

    would like yiu to go through the below link too,
    As the complication of using diffrent name and etc has been mentioned, and fixing has been hit and trial method for me when i did it..
    logical system name vs. destination name - CUA -
    Thanks,
    Prasant K paichha
    Edited by: Prasant K Paichha on Mar 5, 2010 12:52 PM

  • Logical systems assignment when SRM and ECC are on 2 different servers

    Hi SRM guru's,
    What is the standard practice for Logical system creation and assignment when  ECC and SRM are on 2 different servers.
    I could not able to find which i created a logical system  in SRM server which i created in ECC
    Same for the ECC also.
    how do i assign logical system of SRM to ECC
    vice versa.
    your prompt response is appreciated.
    Regards

    Hi Sai,
    Logical System Naming/Creation procedure is not dependent on the servers but it is just a logical representation of a system.
    As you are trying to name logical systems for ECC & SRM, please follow the below procedure which is usually recommeded by SAP and followed.
    Logical System : <SID>CLNT<Client Number>
    For Example if you have a client 300 in system DE0 (also called SID), the logical system name will be DE0CLNT300. And it will be same for SRM system.
    You can refer the below document which eplains the creation of logical system and RFC destinations etc
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    Note: Only while configuring the RFC Destination, the servers will play a crucial role.
    Regards
    Kathirvel

  • How to get RFC Destination and Logical System name dynamically

    Hi all,
    I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
    There is a way to do so in CRM which is as follows:
    DATA:  lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
               ls_siteselect TYPE siteselect.
      CALL FUNCTION 'SMOF0_READ_SITESELECT'
        TABLES
          to_siteselect = lt_siteselect.
      READ TABLE lt_siteselect INTO ls_siteselect
             WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
    The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
    I want to achieve the functionality fulfilled by the above code in R/3.
    Kindly help.
    Useful answers will be rewarded.
    Thanks in advance,
    Karan Merwana
    I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
    Message was edited by:
            Karan Merwana

    For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
    If anyone does manage to get a workaround, please let me know.

  • To get the logical system names of all the child systems in a CUA envirnmnt

    Hi Gurus ,
    Is there any table where we can find the logical system names of all the child sytems in a CUA environment .
    This is for a requirement that i need to develop an automated process where we can reset the password of all the child system in a CUA environemt when requested by the user at once .
    I found some tables such as V_TBDLS , but they do not contain the exact information what i need .
    Thanks in advance ,
    Harshit Rungta

    Hi,
    You are in the right track. BD54 will show you the logical system name for all the existed systems in CUA.
    Else you can also go to your CUA system and execute t-code SALE --> Basic Setting --->Logical Systems  ---> Assign logical system to client -
    > Display details
    here you can see logical system names for all the clients assigned to CUA.
    Thanks,
    Deb

  • Reg: Table name where logical system name will store in R/3 and CRM..

    Hi
    We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
    Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
    Regards

    Hi,
    In CRM:  look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
    In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
    If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
    Hope this helps.
    Thanks,
    Karuna.

  • RFC and Logical System names

    Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

    Hi Gaurav,
    It is recommended, but not mandatory, right, Muthuraman?
    The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
    Regards,

  • Logical System Name Usages

    Hi,
    In Connector properties there is one property called "Logical System Name" what is the purpose of this.
    regards
    mmukesh

    Hi,
    Some of the purposes of Logical System Name are,
    1. Systems of the Central User Administration (CUA) are referred to using logical system IDs. In the SAP sense, a logical system is a client. Therefore you must first set up logical system names that you then assign to the clients in the SAP systems.
    2. System in which applications sharing a common data basis run. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems.
    Regards
    Srinivasan T

  • Logical System Name after System Copy

    Hello,
    I have three questions about the logical system name after system copy.
    Q1) When I change SID D22 to S11 during system copy,
    do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
    Q2)  If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
    1.Tr-CD:BD54
       Add new logical system name for all clients in the target system.
    2.Tr-CD:SCC4
       As for all clients, select new logical system name with F4 help.
    Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
    I refer to the guide "Homogeneous and Heterogeneous
    System Copy for SAP Systems Based
    on SAP Web Application Server
    ABAP 6.40 SR1".
    thanks,
    Keishi

    Hi Keishi,
    As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
    For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
    For Q3  the answer is agaain yes and you can have two approaches>
    1. manually recreate all the RFC destinations after sys. copy.
    2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
    Regards.
    Ruchit.

  • Logical System Name 'WD_RFC_METADATA_DEST' is not properly defined in SLD

    Hi,
    Im getting this error message:
    <h3>
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: 'WD_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)
    </h3>
    What action should I take to fix this error? is this a web dynpro side error or basis error?
    Thanks!

    Dear TJ Ronald Amorado
    Please test the JCO destination for the model data and meta data which you are using in the webdynpro model.
    As per the error message you are getting 'WD_RFC_METADATA_DEST' is not defined in the QA.
    Please create it in the QA manually and test it. Refer to document : - [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?QuickLink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?QuickLink=index&overridelayout=true]
    Copy the name of the modeldata and metadata and use the same name in logical destination during model creation in webdynpro.
    Hope it will helps.
    Best Regards
    Arun Jaiswal

Maybe you are looking for