Use and impact of the logical system (SCC4)

An error has been made in our SAP system (production environment), transaction SCC4. The field «Logicial system» has been changed from «PRD460» to «QAS460». It has been left this way for few weeks and when we realized the mistake, we changed it back from «QAS460» to «PRD460».
For few hours, the document numbers in MM (t-code MIGO) were generated, but were not found in t-code MB03. We were able to generate them manually in t-code SM13 and the problem was solved.
What is the use of the «Logicial system» ? What could have been the impact on our database and on the integrity of our system of having the wrong logical system set to our production environment for few weeks ?
Thanks.

Hi,
Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.                               
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Anil

Similar Messages

  • I there, my question is quite simple, I would like to know if the "apple remote control" can be used with a mac mini and , if so, it can be used to control also the "logic pro" functions (e.g. record, start, stop etc). Thks a lot, Danilo

    I there, my question is quite simple, I would like to know if the "apple remote control" can be used with a mac mini and , if so, it can be used to control also the "logic pro" functions (e.g. record, start, stop etc). Thks a lot, Danilo

    Good work, thanks for the report.

  • What is the logical system name used for in R/3?

    We have a R/3 server. The production client has a logical system name. What is the logical system name used for?
    Tony Tam

    Hi Tony
    Following Links will help you in understanding the concept
    http://benstudycenter.blogspot.com/2008/02/logical-system.html
    http://help.sap.com/saphelp_sm32/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    thanks
    Bhudev

  • 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

  • Error in the logical system (BW - R3 connection)

    Hey guys, i need help, actually i created a connection between BW and R3 system, but i think i wrongly assigned the details to another BW system and now whenever i tried to load the data, it's not being processed.
    And i checked and it shows me that the connecetion is between source system (538) and BW (B3T800), though my BW client is BW (BW TEST). so how do you think i can change my background users i assigned while creating the source systems, because i think, while creating the source system, i used wrong background users. So instead of connecting via logical system (BW test), its connecting via (B3T800) to SAP R3 (538).
    --> Also i tried changing the Logical system name, as i checked and showed that for my BW client now it has a entry of the BW system (B3T800) and when i tried chnging it, it let me change that, but when i went to the RSA1, SAP doesn't let me access that, saying a message "your logical system has been changed", so can i change the logical system, do you guys think my problem will be solved?
    Regards,
    Amit Jaidka

    I have checked in SM37 taking that request number and when i checked the job log , its showing
    5 LUWs confirmed and 5 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    Lock table overflow
    Job cancelled after system exception ERROR_MESSAGE
    what is the reason for this termination in R/3.
    Thanks

  • Message determination and Partner function LS (Logical system) for PO

    Hi,
    I have worked in the past with vendors (VN) as partner roles in a PO, with the message to create an EDI outpout to Partner Type: LI (Vendor), and this works succesfully.
    Now, the idea was to use in EDI, a Partner Type: LS (Logical system) as a receiver of EDI messages (message types: ORDERS) for inbound Purchase Orders to the Partner.
    So, we have set up a respective message condition, with Partner Function: LS  (Logical System), in transaction: MN04 (Create Output-condition records).
    A. When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent to partner.
    B. When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
    Company code is assigned to purchase organization, and so is purchase organization to plant.
    Any idea why there is no automatic message determination in the case of the transaction: ME21N?
    There is a single message condition that is to be read for both cases (trans: ME59N and ME21N).
    Note: If I try ME21N, and enter the output type and partner (=Logical System), manually, I receive a warning message :
    VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent.
    However you can not assign a partner function LS to a vendor, in vendor master data, because of message CZ 327 (Can not use this partner role).
    Anyone with similar experience? Thank you for your advice.

    Hi,
    I well understand that the receiving partner can be a partner: Vendor (LI).
    I have seen that working.
    However, in the Partner Profiles (trans: WE20), the receiver was created as a Logical System (LS).
    We want the partner Logical system (LS) to receive the idoc for purchase order (ORDERS).
    After that, I think that the idea is that the LS can generate an idoc for a sales order creation that will then outbound to another partner.  I think that this is the concept.
    The issue is that I have seen that the POs created with transaction: ME59N, have received from message determination (trans: MN04) the message with partner LS (automatically), and the idoc of the purchase order (ORDERS) have reached the partner LS.
    The question is why the message determination fails when creating the PO from trans: ME21N or ME21, with reference to the PR. Message condition is the same and message determination procedure is the same for both cases.
    There is no issue with customizing for the LS in trans: WE20
    (Port processing agent is Active for LS and ORDERS have the proper processing code for application EF).
    I hope I am helping more with this.

  • This is not the logical system of controlling area 2000

    Hi,
      While creating Activity type / price planning in kp26....i am getting the the information like...
    "This is not the logical system of controlling area 2000"..
      but i am using the company code 3000 which is assigned to the controlling area 2000....
    so...kindly tell me how to come out of this....
    Thanks in advance..

    Hi,
    I assume the error is either KC028 or  COCORE081. In any case: please check if you have activated an ALE scenario for the relevant controlling area in TA OKKP1. Then check if the logical system differs from the system defined for you client in TA SCC4. If this is the case, then that is the reason for the error.
    Regards
    Karl

  • Not converting the logical system through BDLS

    Hi Experts,
    I did the system copy of BI system from production to developemnt
    To change the logical system  in RSA1 --> Source systems
    I have choose client role as test in scc4 and in tcode BDLS i have given the old logical system name new  logical system name
    after completing the job RBDLSMAP i checked in the RSA1 there is no change in logical sytem
    i got the following message
    SM37 log
    Job started
    Step 001 started (program RBDLSMAP, variant &0000000000005, user ID ABCD)
    Logical system name ABC500-1 does not match SAP's recommendation
    Job RBDLSMAP no longer exists
    Converted table: 'RSSTATMANSTATUS'; number of changes: ''
    Converted table: 'RSSTATMANSTATDEL'; number of changes: ''
    Converted table: 'RSSTATMANREQMAP'; number of changes: ''
    Converted table: 'RSSTATMANREQMDEL'; number of changes: ''
    Converted table: 'RSSTATMANPSA'; number of changes: ''
    Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
    Job finished
    Spool log
    Table Name                Field Name       Number of Relevant Entries    Number of Converted Entries
    /BI0/ABP_CUST00*          LOGSYS                              0                              0
    /BI0/ABP_CUST40*          LOGSYS                              0                              0
    /BI0/ABP_VEND00*          LOGSYS                              0                              0
    /BI0/ABP_VEND40*          LOGSYS                              0                              0
    /BI0/ACDS_DS0400*         LOGSYS                              0                              0
    /BI0/ACDS_DS0440*         LOGSYS                              0                              0
    /BI0/ACDS_DS0500*         LOGSYS                              0                              0
    /BI0/ACDS_DS0540*         LOGSYS                              0                              0
    /BI0/ACLM_DS0300*         CLM_FISY                            0                              0
                              LOGSYS                              0                              0
    /BI0/ACLM_DS0340*         CLM_FISY                            0                              0
                              LOGSYS                              0                              0
    /BI0/ACLM_DS0600*         CLM_FISY                            0                              0
                              LOGSYS                              0                              0
    /BI0/ACLM_DS0640*         CLM_FISY                            0                              0
                              LOGSYS                              0                              0
    /BI0/ACRM_CMGL00*         LOGSYS                              0                              0
    /BI0/ACRM_CMGL40*         LOGSYS                              0                              0
    /BI0/ACSM_LINK00*         LOGSYS                              0                              0
    /BI0/ACSM_LINK40*         LOGSYS                              0                              0
    /BI0/AGN_BP00*            GN_PAR_LSY                          0                              0
    /BI0/AGN_BP40*            GN_PAR_LSY                          0                              0
    /BI0/AGN_CONV00*          LOGSYS                              0                              0
    /BI0/AGN_CONV40*          LOGSYS                              0                              0
    Could any body help me in this
    Thanks & Regards,
    Arun

    Hi experts,
    I have done the system copy form Production to Developement.
    Transfermations and DTP(Data transfer process) are still connected from Produciton R3 which  should be from developemnt R3.
    I have tryied to change the logical sytem name through BDLS. But the logical system name is not changed
    i got the job log which is in above conversation in my thread.
    Please let me know how to change the logical system name in Transfermations and DTP in RSA1
    Thanks & Regards,
    Arun

  • How to change or rename the logical system name T90CLNT090 IN BI 7

    HI Expert's,
    i am really digging for the solution of changing or renaming the logical system name technical name T90CLNT090.
    in our company we are using ecc5.0 with bi 3.5 and ecc6 with bi 7. In BW 3.5 having a connection with R/3 and the technical name of the myself bw source system(logical system) is T90CLNT090.
    In bi 7 also the logical system name is same as T90CLNT090. Because of the same system name(Logical name) it is not active in BI7 and also it's giving error when i am activating the DSO Object as Transfer structure prefix for source system T90CLNT090 is not defined.
    because of this i am not able to create the source system between r/3 also.
    so how to change this source system name for T90CLNT090.
    regards
    harikrishna N

    Hi,
    Pls follow this OSS note : 325525.
    Note 325525 - Copying and renaming systems in a BW environment
    Summary
    Symptom WARNING: THIS NOTE HAS BEEN REPLACED.  FOR MORE CURRENT AND MORE COMPREHENSIVE INFORMATION SEE NEW NOTE 886102.
    You want to copy and or rename one or more systems (database or client copy). One or more of the systems is a BW system or is connected to a BW system.
    Caution: This note only deals with problems that occur in the BW source system connections. Other problems that occur in the BW environment (indexes) are NOT dealt with. See URL http://www.service.sap.com/bw --> Services & Implementation --> System copy & Migration.
    Other terms BW, source system, OLTP, database copy, client copy, system infrastructure, transport system, connections, RFC connection, trfc, transfer structure, IDoc, ALE customizing, logical system name, system changeability, renaming systems, system copy
    Solution Several scenarios are possible in this environment. Find the scenario relevant to your situation below and execute the steps listed or read the note(s) specified:
    Scenario 1) You do not want to copy a system but only want to rename one (changing a logical system name).
               Solution scenario 1): Execute Transaction BDLS both in the client to be renamed and in the connected BWs or BW source systems. To do this, see Notes 121163 and 369758.
               Check the RFC destinations in all connected BWs/BW source systems as described in Note 524554.
               Reactivate all partner agreements that carry the new logical system name after renaming.
    Scenario 2) You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group) by a database copy. SAP recommends this procedure for copying systems.
               Solution scenario 2):
    If you want to rename one or more of the copied systems, then execute Transaction BDLS both in the client you wish to rename and in all the connected BW and BW source systems. See Note 121163.
                        Make sure that an RFC destination exists with the new logical name in every connected BW or BW source system.
                        Reactivate all partner agreements that carry the new logical system name after renaming.
    Change the hosts in the appropriate RFC destinations so that they refer to the correct computer. For this, see Note 524554.
    Scenario 3) You want to copy a single BW system of the group by database copy.
    Scenario 3)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 3)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 3)b) You want to keep the original system of the copy so that you have two systems after copying.
                         Solution scenario 3)b): See Note 184754.
    Scenario 4) You want to copy a single source system of the group by database copy.
    Scenario 4)a) You only want to exchange the hardware of your system but do not want to rename the system.
                         Solution scenario 4)a): You do not need to execute follow-up work regarding the system connections, except for adjusting the IP address in the RFC destinations of the connected system.
    Scenario 4)b) You want to keep the original system of the copy so that you have two systems after copying.
               Solution scenario 4)b): See Note 184322.
    Scenario 5) You want to import a client copy in a source system.
               Solution scenario 5): See Note 325470.
    Thanks & Regards,
    Suchitra.V

  • In CIF customer exit there is no information about the logical system

    Dear All,
    we have a SAP R3 system (ver 4.7) connected to 2 SAP APO systems.
    we need to differentiate the UE code in R3 by APO TARGET SYSTEM.
    In the CIF userexit used:
    EXIT_SAPLCLOC_001
    EXIT_SAPLCSRS_003
    EXIT_SAPLPGS1_001
    EXIT_SAPLCSTK_001
    EXIT_SAPLMEAP_001
    there is no information about the logical system (source, destination
    etc.) The control parameters are not provided to the user exit.
    I found a note 1060634 where the parameter have been added to
    EXIT_SAPLCSLS_002 , but not to all other exits.... do you have any clue on how we can proceed?
    Thank you !!
    Best Regards , Barbara

    Found the answer, to bad i cannot give points to myself :-P
    In the ABAP i use the E_T_RANGE output structure.
    That structure has several fields (sign, opt, low, high).
    In my ABAP i stored the same value in the low and high field.
    This should work fine for normal (flat) characteristic values.
    However, because i use a hierachy i should enter the 0HIER_NODE value in the high field.
    For details see: SAP NOTE: 912473
    Regards

  • Getting the logical system from where RFC is being called

    Hi All,
    How can we get the logical system name from where RFC is being called?
    Regards,
    Akshay

    Hi Akshay,
    If your company follows the SAP recommendations on naming [logical systems|http://help.sap.com/SAPHELP_NW70/helpdata/EN/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm] <b>&lt;SystemID&gt;"CLNT"&lt;Client&gt;</b> then you should get away with a simple call to RFC_GET_ATTRIBUTES (and even if they don't, the function module might possibly provide other clues required to build the logical system name).
    There might be other ways, but I'm kind of suspecting that the logical system name of the calling system might not be part of the communication data (like other readily available data as IP address etc.). So if this solution doesn't work, it might be helpful to understand how the naming conventions for logical systems used by your company.
    Cheers, harald

  • 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

  • How do you identify the Logical system in start routine of a transformation

    My scenario is this.  I have five r3 systems that I am extracting from.   In the start routine of the transformation from the r3 data source to my data store I  am going to delete data and I need to know the source system id.    How do I identify the logical system or source system id in the transformation.  Is there a system field that contains this information.    I do not want to hard code the source system id in the routine.

    hi
    have a lool at tables rsreqdone and rsbkrequest with a join you should be able to determine the source.
    regards
    Boujema
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).
    Edited by: Boujema Bouhazama on May 9, 2008 12:04 AM

  • 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

  • Configuring tomcat and apache on the same system

    i need to configure tomcat and apache on the same system.
    first i have configured apache and it is working well.
    Next is have configured tomcat and it is working well.
    i need to interlink tomcat and apache. so i downloaded jk connector and i have configured it.
    i gave an entry in the httpd.conf as
    Include /tomcat/conf/auto/mod_jk.conf
    i have copied the file mod_jk.so to /usr/local/apache/libexec/
    went i start apache after the entry is given it gives the error like this
    cannot load /usr/local/apache/libexec/mod_jk.so into server: ld_so.1. /usr/local/apache/bin/httpd: fatal : libgcc_s.so.1 : openfailed : no such file or directory in linux
    please help to configure this.
    i have done every thing as it is in apache.org documentation. please give the complete configuration. some say that tomcat is not compiled according to apache1.3. but i configure jk connector as --with-apxs=/usr/local/apache/bin/apxs
    send me the reply
    thankqs in advance

    Hi,
    I'm working in a linux machine and choose to use also two different users. Of course I'm using two different ORACLE_HOME directories.I think that the best approach.Just a question ,are you keeping the "GROUP" same or different?
    Anand

Maybe you are looking for