"Logical System"  &  "Assign Logical System to Client"

Hi Experts,
I'm new to Basis, I have the following systems installed:
1. EBP and SUS are installed in same server with different client:
    EBP:  E01 with client 100
    SUS: E01 with client 200
2. ECC system is installed at a separate setver
    ECC:  D01 with client 100
My question is, in EBP client  which logical systems and client assigments need to be done?
What I confused is,  for the EBP and ECC they have same client number 100,  in EBP client , the client number 100
should be assigned to EBP or to ECC?
Kindly please guide.
Thanks and best regards
Jack

Hello Jacky,
                   You can assign the client number 100 to EBP and ECC systems, it doesn't create any problem. Because when you logical system in EBP, you need to create two logical systems one for EBP and ECC, but you need to assign client 100 to EBP only, same goes to the other side also.
Regards,
Prasanna

Similar Messages

  • Assign business system

    I have created a business system in SLD.  When I want to assign this business system to the scenario, I can not find it in the wizard and also not show on Object tab. It is a new business system, I dont assign it to the other scenarios. How to find it?

    Hi
    You need to first import this business system from SLD into Integration Directory.
    Go to objects tab -> right click on "Business System" -> Assign Business System.
    In the new window choose your newly created business system and its ready to use now
    If your Business system does not show in da new window, refresh the cache,
    how to refresh the cache?
    Goto ID -
    > Environment -
    > Clear SLD Cache,  try the step of importing it again.
    Hope this clears your doubts
    Thanks
    Saiyog

  • SOLMAN 7.1 Assigning Hana database Technical system to product system

    Hi All,
    I am trying to assign a HANA database technical system to Product system.
    I am trying to do it in conventional way (i.e in LMDB TCODE--> Selected Product system-->Assign Technical system--> ).
    But I am getting below error.
    No local proposals; search remotely in SAP SMP (time-consuming).
    So wanted to know whether there is any other way for assigning Prodcut system to HANA DB Technical system.
    Please find the screen shot for the error message.
    Thanks & Regards,
    Solman Starter

    You can either use a product system that already exists for the ABAP system (if the ABAP system was already connected to Solution Manager) or create a new one. After all you should use the same product system for ABAP and HANA.
    Check this for further reference -
    Managed System Setup of HANA in Solution Manager 7.1 - SAP Solution Manager Setup - SCN Wiki

  • Error while assigning Logical System to Client

    Hi,
    I am trying to perfomr data transfer suing Idoc from SAP R/3 to PI.
    For this, I have created a logical system PD1CLNT100.
    But when I try to assign the client 100 to this Logical system through SALE, I ge the following error
    "An entry already exists with the same key SALE"
    but I am unable to see this entry in the client list in SALE.
    Please tell me where is it picking the entry from?
    regards,
    Piyush

    Hi  Piyush Mathur SAP   
    Check once again for Client 100 ... there willl be entry  (Assign the Logical System to Client)
    Check in table  V_TBDLS  for Logical Systems..
                             T000         for Clients
    Log out from the system and log in once again and check it....
    i hope Above info helps you
    Thanks
    Ramesh

  • Assign Logical System to client 000

    I need to install Bw at SAP ECC 6.0, in doing so on the client 000 with the transaction RSA1, present the message that should be assigned System logical customer 000, it does not bring inconvenience to any future activity,
    Thanks

    Hi Victor,
    If you're installing BW you shouldn't use cleint 000, create a new client...
    Once you create the client go to transaction SALE and You'll see Create logical system ans assign logical system in the list.
    First create a new logical system for the client to use... then assign the logical system to the client.
    Regards
    Juan
    Please reward with points if helpful

  • Assign a Logical System Name of a production client

    Hi everybody,
    We have an ERP system (now upgraded to ECC 6.0) that is in productive use since 7 years. Until now, no Logical System Name have been assigned to the production client - the field in transaction SCC4 is empty/blank.
    Now we plan to implement a BW, so a test and a productive BW systems have been installed. According to the attached file and content of note 184447 we choose to use "Option 1: Uniform Logical System names clients by system type" for naming convention for LSN's.
    All the systems/clients (BW test and productive, ERP test only) now are assigned with corresponding LSN's, except the production ERP client. It is still without LSN and the client is not defined as Source System for productive BW system.
    So, my question is:
    Should I expect any problems if the LSN of the production client is set up now, after long time, effective productive use?
    I would mention that this is infact initial setup, not a change of LSN. Therefore transaction BDLS is not relevant, I think.
    Thanks in advance

    Hi DB49,
    I already did an initial setup of LSN in the test ERP client (that client is copy of the productive ERP client, i.e. the LSN has not been set). And everything seems to be OK.
    But the documentation says that ".... In a production system, the logical system must not be changed ...".
    "Changed" is not "ïnitial setup" of course, so there will not be any problems I hope, but ...
    SCC4 --> LSN field --> F1 -->
    "System in which applications run integrated on a shared data basis.
    The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
    In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
    The logical system is relevant in the following SAP areas:
    ALE  general: two or more logical systems communicate with one another.
    ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
    Workflow objects: the logical system in which the object is located is always included in an object's key.
    When maintaining the logical system, note the following:
    The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system."

  • How to Assign Logical System to a Client in SALE Transaction

    Hi ABAP/EDI Specialists,
    1How to Assign Logical System to a Client. In the SALE transaction window.
    I didn't see any Receiving and Sending Systems(Tree). But I can see Logical Systems. In the Definition and Assign Subtree are there. I created two Logical Systems STUD_S and STUD_R. When I executed Assign Logical Systems. I got a window, Where I can see a list of Clients. I got confused, how to Assign those Two Logical Systems to Client 800 and 810. Finally I double Clicked on each client and in the next window. I changed the Logical System to STUD_S for Client 800 and Logical System STUD_R for client 810. and saved them.
    Is this procedure correct???
    Why I need this is, While generating partner profiles in ALE Model (BD64), I am getting no list at all. When I executed I got no list.
    "No messages have been defined for the selection conditions in the Model"
    I got struck at this point.
    Please help me to come out of it.
    Thanks,
    Chinna

    Hi Chinna,
    Thanks for such a valuable information. I am able to move further. But i got struck while generating parntner profiles from ALE distribution model.
    Log For Partner Profile Generation:
    Partner:
    Partner ZVK_SS_800 as partner has been Created ( Sending System)
    Partner ZVK_SS_820 as partner has been Created (Receiving System)
    Port:
    Port Cloud not be Created
    RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
    Enter the RFC destination and Restart the generation
    It is not recognizing the RFC port, even though i followed all the steps correctly.
    While creating RFC destination, can someone tell me How to fix the above error and what is the Client No, Username and Pasword i have to give.
    Thanks
    Chinna
    Edited by: Chinna on Jun 6, 2008 7:43 PM

  • 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

  • About  assigning logical system name to client

    Hi:
        the SAP landscape is:
        CRM DEV CR0 (CLIENT 200)        -
    >    CRM PRD CR1 (CLIENT 800)
                      \|/                                                                        \|/
          ERP DEV MZ0 (CLIENT 200)      -
    >   ERP PRD MZ1 (CLIENT 800)
       the crm dev is connected the erp dev and the crm prd is connected the erp prd.
       the CRM version is CRM2007 and the ERP version is ECC 6.
        My question is :
       Can the logical system name of the prd client 800 be same with the dev 200?
       Could you give me any advice?
    THANKS.
    Edited by: Xiaofeng Qiu on Jun 5, 2009 11:27 AM

    Hi,
    The logical system must be unique company-wide. In a production system, the logical system must not be changed.
    Goto SCC4-->Double click on any client number. You will see logical system text. Select it & press f1 you will below information about logical system.
    "The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
    In the SAP System the client corresponds to a logical system.
    When you maintain the logical system, note the following:
    The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed."
    Thanks
    Sushil

  • 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

  • Logical system on QAS after remote client copy from PRD to QAS

    I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
    Thank you in advance

    Hi Branko,
    After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
    Other activities, check Jobs, RFC's, etc...
    Regards
    Juan
    Please reward with points if helpful

  • Assign Logical System both in GTS and R3

    Hello all,
    We are using Two different system for R3 and GTS , and defined logical system both systems ( for R3 QR1CLNT100 and for GTS QG1CLNT100 , now do I need to assign logical system both system for clients in R3 and GTS ( I mean at the time of assignment both clients QR1CLNT100 & QG1CLNT100 i have to assign in both systems  or only one.   For Feeder system only I need to assign GTS system logical system as QG1CLNT100 vice versa ( for GTS system need to only Feeder system logical client QR1CLNT100)
    Thanks in advance for valuable inputs.
    Thanks & Regards
    Tarun

    There are following steps  for doing connection between R/3 and GTS
    1. Define Logical System
      Here you have to define both R/3 logical system as well as  
      GTS logical system.
    2. Assign Logical System.
    Here actually when u get in you will see the physical system
    detail on which you are logged in , suppose you are on R/3 you will find detail of R/3 system with different clients. Some clinet willcome as default like 00 which is waldrof client the SAP client and other are are those which are created at the time of installation.
    Here you have to assign the logical system of R/3 to the physical system client combination on which you looged in.
    you will find a field  of logical system on the top once you get in detail of the client system combination.
    Now here we have assigned the Logical system of R/3 this is required as when GTS will communicate wiht R/3 it willtry to look for  R/3 logical system as for RFC connection we always define logical system to which the system will talk.
    this configuration we do under Maintain RFC connection for RFC call Tcode SM59
    3.  Maintain RFC connection for RFC call Tcode SM59.
       Here we define the Target host, and logon detail like 
       language , client, user passwaord.
       We need to define the detail for GTS for RFC connection and   so we need here the logical system of GTS.
    4. Maintain RF destination for method call
      Here again you will require GTS logical system .
    5. Maintain ALE distribution here you will require both R/3 and GTS logical system.
    Hope it helps
    Kind Regards,
    Sameer

  • Difference between client system and logical system

    Hi all
    Can any one explain about the client system and logical system??
    When this message type will comes in to picture at the time idoc processing??
    Thanks and Regards
    Arun Joseph

    hi Arun,
    I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
    and to know the diffrence between client and logical system very keenly go thru this link
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
    IDOC Administration
    Step 1: Tcode: WE 46
    Setting the Global Parameter for IDOC Interface
    Step 2: Maintaing a Logical System
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Define Logical systems
    Go to Spro transaction
    Step 3: Allocating Logical systems to the Client
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Assign Client to Logical systems
    Go to Spro transaction
    Step 4: Setting up an RFC destination
    Tcode: SM 59
    Path: From the ALE Customizing in IMG, choose Communication, Define RFC
    Destination
    You can also do the Advanced Settings in the RFC Destination
    Step 5: The PORT definition
    TCode: WE 21
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Systems in Network, Asynchronous Processing, Assign Ports, Define Port
    Step 6: Generating Partner Profiles
    TCode: BD 82
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
    Step 7: Distributing the Model
    TCode: BD 64
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, Maintain Distribution Model and Distribute Views
    Technques for Distributing the Master Data:
    Technique 1: The Push Approach
    Executing the Process:
    TCode: BD 10
    Path: from the ALE Main Menu, choose Material Data Distribution, Cross
    Application, Material, Send
    Technique 2: The Change Pointer Technique
    Enable Change Pointers Globally
    TCode: BD 61
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers
    Enable Change Pointers Globally
    TCode: BD 50
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers for Message Type
    Specify the Fields for which Change Pointers are to be written
    TCode: BD 52
    Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
    Change-Relevant Fields
    How the Classification system works:
    Creating a Class Type
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Status for the Class Types:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classification Status:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classes:
    TCode: CL 01 (it is zero)
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
    Allocating classes to the Logical Syatems
    TCode: BD 68
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Assign classes
    to Logical systems
    Filering at the IDOC level:
    Identify the Filter Object:
    TCode: BD 59
    Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
    Type to IDOC Field
    Modify the Distribution model
    How Segment Filtering Works:
    Configuration:
    Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
    TCode: BD 56
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
    The Reduced IDOC Type:
    The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
    The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
    represented by a forward slash(/) in the field.
    TCode: BD 53
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
    Create Reduced Message Type
    IDOC:
    Complete Documentaion on any IDOC using TCode: WE 60
    IDOC Display Tool: TCode: WE 02 or WE 05
    IDOC DEfinition components:
    Segment Components:
    1. Segment Type (E1, Z1)
    2. Segment Definition(E2, Z2)
    3. Segment Documentation(E3, Z3)
    E- SAP Defined
    z- Custom Defined
    IDOC runtime componets:
    control Record:
    Data Record:
    Staus Record:
    First Create the Segments using TCode: WE 31
    and then create the IDOC using TCode: We3 30
    first release the segments and then IDOC.
    Creating a new Basic IDOC Type:
    STEP 1: Analyze the Data:
    STEP 2: Create Data Elements:
    STEP 3: Create Segments:
    STEP 4: Create Basic IDOC Type:
    1. Execute TCode: WE 30
    2. Select the Create new option and enter a description for your basic IDOC type
    3. click the IDOC name, and click the create icon.
    Enter the segment type and its attributes.
    4. Keep on adding the segments as in step 3.
    5. Save the basic IDOC type
    Step 5: Release the Segment Type and Basic IDOC Type
    STEP 6: Transport the Segments and Basic IDOC Type
    Extending a Basic IDOC type:
    STEP 1: Analyze the Data:
    STEP 2: Create Custom Segments:
    STEP 3: Create the IDOC Type:
    STEP 4: Release the custom Segment and IDOC Extension
    Develop the function module for fteching the Data and then inserting the data into IDOC using
    EDIDD(for control Record) and EDIDC table(for DATA Record)
    Configuring the Systen for IDOCs
    Configure an Outboubd Process that uses Message Control
    Step 1: Create a new Message Type
    TCode: We 81
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 2: link the IDOC type to the Message Type
    TCode: We 82
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 3: Create a new Process Code
    TCode: We 41
    Path: From the Area menu of EDI, choose Control,Outbound Process COde
    Step 4: Create or Change a Partner Profile
    TCode: We 41
    Path: From the Area menu of EDI, choose IDOC,Partner Profile
    Configure an Outboubd Process for Stand-Alone Programs
    1. Create a new message type
    2. Link the IDOC type to the Message Type
    3. Add the message to the ALE Distribution Model(use BD 64)
    4. Create or change the Partner Profile
    go through the following site to have screen shots.
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    thanks
    karthik
    reward me points if usefull

  • Regarding problem while assigning logical system

    Hi Friends,
    I had a problem while assigning logical system to the client where in both of my systems are having same client number which belong to 2 different systems.
    while assigning the sender and receiver logical system to the same client i am facing problem stating that an entry has already been made for the same key.
    could any one plz give me a clear idea...while assigning logical systems (cross clients) for 2 different systems having same client number.
    Regards,
    Madhu

    Hello Madhusree,
    I'm running with same problem. I've created two logical systems and assigned them to two different clients. But here pops up the issue while generating partner profiles, throwing error "No active plan version exists". Later when I researched about the issue, I came to know that T77S0 table doesn't have any entries regarding plan versions. Basically, I created two clients by doing "client copy" from source client (800 & 100). And I could see plan version entries in the T77S0 of client 800. So, I thought of assigning just defined logical system to the source client 800 itself. But it throws error saying "entry already exists"; as client (800) is already assigned with other logical system.
    By coming across your post, gives me leap of hope that two logical systems can be assigned to same client. Could you please share me those troubleshooting steps concerning this issue. Points will be awarded.
    Regards, Anil. 

  • Creating and Assigning logical system after executng RSA1 transaction

    Hello guys, i am stuck since many days for running the transaction RSA1 for BW but message comes you can work only in client 001 only. when i try to log in with bcuser i cannot but i am able to log in with DDIC user but it says there is no logcal system assigned. I tryied to create a new logical system but it says user ddic may not change objects something like that. please help in this case that how i can be able to use bw in NW04s trial. i created a user in the client 001 but this user fails to create logical system and mssage states that you do not have authorization to do this actine. i hope i will get the answer very soon. Hafiz Anis

    For BI7.0(sap netweaver 2004s) help docs pls check the below links
    Check these links:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    NW2004s help:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm -> SELECT key capability
    http://help.sap.com/saphelp_nw2004s/helpdata/en/30/c4461ff69d5a438f1286e344b545fa/frameset.htm then select
    -> information integration -> business intelligence.
    For Modeling in Netweaver BI:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
    To know the New Features in BI:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4487dd91-0b01-0010-eba1-bcd64196ec6b
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
    Also check these links as well:
    https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e
    BI Data Modeling and Frontend Design
    For Netweaver Security & Authorizations:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8c/2ec59131d7f84ea514a67d628925a9/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/39f29890-0201-0010-1197-f0ed3a0d279f
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fda2a990-0201-0010-5497-b81b1556df24
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/adeac294-0501-0010-5a97-9ac5d562b1be
    Also check for documents in SDN .You can find the screen shots,Demonstrations and lot of documents:
    https://www.sdn.sap.com/irj/sdn/developerareas/bi
    Hope it helps

Maybe you are looking for