In what situation, I should define a logical system?

In our sap system, we do not define any logical system for a certain client.  I do not know is it necessary to define the logical system,   what is it used for?   In what sitution, I should have a logical system?     Could you give me some advices?
thanks

Hi,
'logical system' is used to identify an individual client in a system, for ALE
communication between SAP systems.
http://help.sap.com/saphelp_nw70/helpdata/en/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm
--Kishore

Similar Messages

  • Define one logical system for PI or multiple LS for 3rd-party system?

    Hi gurus,
    We are using IDOC2SOAP and SOAP2IDOC scenario in PI7.11. My question is regarding the logical system(or partner profile) on R3 side. We have two 3rd party system:A and B, so we have two choices.
    1. define one single logical system for PI integration server;
    2. define two logical systems for A and B.
    For choice 1, it seems we can only use one business sytem or business component (business service in 7.0) as the two 3rd party system, especially for SOAP2IDOC scenario.
    For choice 2, it seems we have no restrictions.
    Is it correct?Any help will be appreciated.

    technically you can use both options.
    The question is - do you want all the IDOCs in your R3 system to appear as though they were sent from the PI?
    What if a lot of 3rd party systems were sending the same IDOC (for example - ORDERS) and you want to investigate only those who were sent from system A?
    I like it configured that every system will be identified by a name I give it.
    I just use the IDOC communication channel checkbox of "Take Sender from Payload"
    or use a different service in the IBC that has a different logical system configured in its Adapter specific identifiers.
    Hope it helps,
    Imanuel Rahamim.

  • Defining a Logical System

    I'm trying to follow the Best Practices note, "B84: BI Connectivity" for SAP BW 7.0 dated August, 2007.
    On the second step, 1.2, "Defining a Logical System", I reach the second sub-step, clicking "Define Logical System". After the harmless warning, "Caution: The table is cross-client", then I get an error.
    If I'm logged in as SAP* (client 000), I get the error, "No changes for user SAP* allowed".
    If I'm logged in as ddic (client 000), I get the error, "User DDIC may not make changes in customer systems".
    I'm still very new to SAP and don't understand these kinds of permissions issues at all. Two questions:
    1) How can I resolve this issue?
    2) Is there a good book that I can read to understand these kinds of administrative issues better?

    Hi,
    you to login as a development user or administration user into your BI client (100 e.g) but not as SAP oder ddic which are reserved users with special authorizations. Client 000 is a special client used for installation and creating the working or devleoping client where you set up /customize your BI later.
    With htis development user you can then change the logical systems table, which is valid for all clients in te system!
    Hope you got an idea
    Juergen

  • How to define a logical system in BD21 (RBDMIDOC)

    Hi,
    We have several logical systems in our distribution model (BD64/WE20) liked to CREMAS message. One other them is the X server, for instance.
    When run BD14, it´s ok, because we can set the target system (X server in this case).
    However, when we work with change pointers, the BD21 doesn´t have a target system field and it´s based on distribution model. So, it sends IDOCs to
    all logical system. But we want to send to only X server.  
    Does anybody know how to define a target system in this case?
    Best regards,
    André Avilla
    Brazil

    Hi
    Check the below wiki.
    https://wiki.sdn.sap.com/wiki/display/EP/SystemCreationin+portal
    https://wiki.sdn.sap.com/wiki/display/EP/HowtoConnecttoBWSystemthroughEnterprisePortal7.0UsinganIView.
    Regards
    Basheer
    Edited by: Basheer on Jul 13, 2009 5:13 PM

  • Maintenance Optimizer "local logical system is not defined"

    hello, i would like to create a new maintenance transaction to upgrade from SAP ERP 6.0 to SAP ERP 6.0 Enhanced Package 4 i follow the steps in the "maintenance optimizer configuration guide" BUT when i click to create a new maintenance transaction i faced an error told me "local logical system is not defined"!!! so how i can define Local logical system?
    thanks in advance
    Amr M. Abdelazeez
    Mobile: 002 011 40 85 200
    Linked In: http://eg.linkedin.com/in/amrabdelazeez/
    Alexandria, Egypt

    This should be configuration issue, please check the description in the Implementation Guide (tr: SPRO) at following point:
    SAP Solution Manager
    - Basic Settings
       SAP Solution Manager System
        General Settings
         Maintain Logical Systems
    After having maintained the logical systems, the error should not be displayed any longer.

  • Error : Logical System is not defined

    Hi Experts,
    I have installed SAP CRM 7.0 IDES . But when i am trying to exectute Transaction Code /nbp ( Business Partner Creation) system is giving an error 'Logical System is not defined ' and i am not able to execute the transaction.
    Kindly explain how to define the logical system.
    Regards,
    Rohit Tripathi

    Hello Rohit,
    To solve the problem you should proceed as described in the long text of the error message B2 001 and maintain the logical system for the current client via transaction SCC4.
    The reason for this error is that the ALE outbound of business partner is activated. If you don't want the ALE messages to be generated when business partner is changed then you can disable the ALE outbound. To do that, go the maintenance view CRMC_BUT_CALL_FU and disable the following function modules if active:
    BUPA_OUTBOUND_REL
    BUPA_OUTBOUND_ALE_REL
    I hope this could be helpful.
    Best regards,
    Maggie

  • What is logical system in ALE

    Dear all
    I still confuse with Logical System in ALE where we already have Client.
    And I see that relationship between Client and Logical System is 1:1
    So why we need Logical System instead just use Client ?
    Regards,
    Halomoan

    I think this is what you want to read:
    A logical system is an unique identifier of a system/client combination.
    That is why SAP recommends to use the notation <SID>CLNT<CLT> to set the logical system. For example, assume you have client 400 for system QA1 and you have client 400 for system DV1. Then the logical system name would be:
    for QA1/400: QA1CLNT400
    for DV1/400: DV1CLNT400
    The logical system is used in the IDOCS that you transmit from one system to the other. So with this, you know the source system of the IDOC, and this tells you where the business document was created.
    Using only the client as identifier is not enough, because you can have the same client number in several systems.
    Nevertheless, you should read the documentation!!
    Regards,
    Juan

  • Local logical system is not defined

    Hello
    We are trying to setup a logical system  - created or defined the logical system
    when we try the BD64 it gives out the error "Local Logical system not defined"
    I am using ECC 6 version
    IS there any way to bypass  and do the setup ?

    HI Anil,
    Best Methodology for creating a RFC Destination that also includes setting up <b>Logical System</b> is:
    <b>Use Transaction -> SALE /b]
    1) <b>Define Logical system :</b>
    Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Define Logical System
    <b>
    2) Assign Client to Logical system:</b>
    Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Assign Logical System to Client
    <b>3) Create RFC Destination: T-CODE (SM59)</b>
    Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Communication -> Create Rfc Connection
    Follow steps in sequence. Hope it answers every thing.
    Cheers,
    *RAJ*
    *POINTS IF FOUND HELPFULL*

  • Where to define third party logical system name in file to idoc scenario

    Hi Friends,
      I am shalini shah.
    I have one doubt, where I can define the logical system name in File to Idoc scenario.
    I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
    In SALE or any where.
    Please give me solution.
    Warm Regards,
    Shalini Shah

    Hi Shalini,
    You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
    Just refer the below link for configurations with step by step solution.
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Thnx
    Chirag

  • Runtime error (syntax error) when defining a new logical system

    Hi!
    I get a short dump when trying to define a logical system, the field <b>clidep</b> does is not defined in function module <b>SCPR_BCSET_PROT_GET_TABKEYS</b>:
    CALL FUNCTION 'SCPR_HI_DB_SCPRACTR_READ'
        EXPORTING
          TABLENAME     = wa_tabnames-low
          VIEWNAME      = viewname
          CLIDEP        = clidep
        IMPORTING
          ACTKEYS       = actkeys
        EXCEPTIONS
          NO_DATA_FOUND = 1
          OTHERS        = 2.
    I have searched for notes, but I haven't fiund anything to correct the error. Does anyone one how to correct this?
    - Mari Virik

    Hi!
    I get a short dump when trying to define a logical system, the field <b>clidep</b> does is not defined in function module <b>SCPR_BCSET_PROT_GET_TABKEYS</b>:
    CALL FUNCTION 'SCPR_HI_DB_SCPRACTR_READ'
        EXPORTING
          TABLENAME     = wa_tabnames-low
          VIEWNAME      = viewname
          CLIDEP        = clidep
        IMPORTING
          ACTKEYS       = actkeys
        EXCEPTIONS
          NO_DATA_FOUND = 1
          OTHERS        = 2.
    I have searched for notes, but I haven't fiund anything to correct the error. Does anyone one how to correct this?
    - Mari Virik

  • Confusion on Logical System (Idoc)

    Hi Guru's
    Please help me out
    I have two SAP System  : ex SAP A client 100 and SAP B clint 200.
    My Sender system is SAP A(100) and Reciver SAP B(200)
    I have to do ALE configuration. I got stuck in SALE Transaction is Client assignment.
    As i have to define Logical system for Both SAP A and SAP B.
    But in Assignement part what should i do
    Should i assign Logical system of SAP A( 100) to client 100 or 200?and what should i do for Logical System of B?
    I hope i need to assign the Logical system of both system in SAP A to some client.
    Regards
    RJ

    Hi,
    Find the steps below.
    1.Go to SALE transaction
    2.Define Logical system (Use only the existing Logical systems).
    3.Assign client to the logical system. (Never change the existing assignments).
    4.Define target systems for RFC calls. (We can do this using SM59 also).(Always maintain same names and descriptions for RFC destinations like Logical system.)
    Example:
           Logical system in 100: LS_100
           RFC destination in client 200 should also be LS_100
           Logical system in 200:  LS_200
           RFC destination in CLIENT 100 should also be LS_200
           For a better practice always maintain both RFC destinations  in both sending and receiving systems.
    Hope this helps.
    Regards,
    SuryaD.
    Edited by: SuryaD on Dec 23, 2009 11:51 PM
    Edited by: SuryaD on Dec 23, 2009 11:52 PM

  • Logical systems in ALE iDoc

    Hi,
    For exchanging data between two systems(not between two clients of the same system) using ALE iDoc , logical systems should be maintained in both the systems?
    For eg: there are two systems, system A and system B.
    i have maintained the logical systems as SYSA (for system A)  and SYSB ( for system B) in the system A using the transaction 'SALE'. Should this need to be maintained in system B also?
    Thanks & Regards,
    Soumya.

    Hi,
    In both the systems you have to Define the Logical systems,
    but in you assign only one to the client,
    i.e. in system A you assign the Logical Sytem of of A to the Client in SALE
    transaction the same goes for B.
    and you don't need to create a distribution model for both the systems,
    you can create it in one system and send it to the other system.
    Regards,
    Samson Rodrigues.

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

  • Difference between the Logical System n Client

    Hi Guys,
      i need a some information plz help me.
    what r the differences between the logical system n the client.
    plz give me the detail explanation
    appreciated with points
    regards
    kk

    Hi there,
    'logical system' is used to identify an individual client in a system, for ALE
    communication between SAP systems. That's why you see a field for 'logical
    system' in the client master data in SCC4 (table T000).
    Client can be defined as commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.
    Hope it helps
    Cheers
    Deepanshu

  • Mapped logical system

    Hi Experts,
    I have a confusion to use the type of RFC connection like when
    to use ABAP connection and TCP/IP connections etc...
    I have defined one logical system and define one RFC destination and when  i am trying connect this two it is asking me to give Standard RFC destination for BAPI and dialog calls to connect to the logical system. i would like to know what is this ? why we need to give this?.
    and we assign this logical system to the Mapped logical system. i d like to know what is this mapped logical system and when we need to assign the logical system to this mapped system.
    Can anybody please clarify all my doubts.
    Thanks, Izaz.

    Hi Izaz,
    ABAP connections are given between 2 SAP systems and TCP/IP is used between ABAP and JAVA.
    Regards,
    Suman

Maybe you are looking for