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

Similar Messages

  • Is it possible to change the Logical System name in ID

    Hi,
    I am doing a file to Idoc scenario. My requirement is to overwrite the logical system name, which is set in SLD for sender (system). Is it possible to overwrite it in ID or in mapping somewhere.
    Thanks,
    Dehra

    Hi Dehra,
           Go through the below help file of SLD. It will give you information regarding logical name as well:
    <a href="http://xiserver:50100/sld/doc/sld.pdf">http://xiserver:50100/sld/doc/sld.pdf</a>
    Regards,
    Subhasha

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

  • 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

  • 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

  • How to map IntegrationProcress to ALE Logical System Name

    Hy,
    i'm triying to send an Idoc from my IntegrationProcess MY_IP
    to out Backend SAP System XX1.
    Konfiguration has been done with an valid ReceiverAgreement.
    But neverless i got the following error:
    "Sender Service MY_IP cannot be mapped to an ALE Logical System"
    1. Where do i specify this Mapping? (I tried Header Mapping ReceiverAgreement
      without success)
    2. In my message mapping EDI_DC40 has mandatory fields like RCVPRN.
        But hardcoding the Receiver here cannot be the solution. Do the value
    i map there do have any effect at all?
    Thanks in advance.
    Gunnar

    Hello Nilesh,
    you're right - now it works. I just defined any LS and SID. No the IDoc runs into the system, but cannot be processed since the originator is unknown. But this can be solved now with SALE and we20.
    To be honest: there are so many blogs concernig this case. But i didn't find any which explains why the behavior is different when you send an IDoc from an Integration Process and what happens behind the scene. In the documentation
    i didn't find anything at all...
    Thank you very much.
    Gunnar

  • Clarification Regarding Logical System Names

    HI all,
    I read the blogs regarding Logical System Name, even I am having the some problems in my system.
    For PI system client is 100.
          R/3 System Client is 100 is created.
    IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
    I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
    In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
    When I checking in the R/3 system that logical system Name ('PICLNT100')  is not there  and for r/3 client 100 having the different logical system name.
    IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
    It is different from the SLD logical System Name.
    How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
    when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
    How I have to maintain the logical system names in this case?
    please help me in this.
    Regards,
    Sree

    hi.
    each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
    http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
    IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
    to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
    once you configure it all data from r3 system is exported to SLD.
    if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
    each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
    hope its helps
    Rodrigo
    PD: rewards points if useful

  • How to change logical system name

    hi,
    there is no logical system name for business system in sld on integration tab.
    this bus sys is based on tech sys which is configured as integration server.
    plz tell me how to give the logical sys name there.
    plz reply me it is urgent.
    vijender

    Jochen Gugel wrote:
    > Hi @ll;
    >
    > at the tab in technical system the logical system name was correct.
    > But it wasn´t shown at the integration tab of the business system.
    > I solved this problem by deselecting the integration server, save this settings and reselect it afterwards.
    >
    > Kind regards
    > Jochen
    hello all,
    I'm actually having the same issue.  This issue is NOT the popular adapter-specific identifier problem where the business system in the ID needs to be compared with the SLD.  This issue is that the within the SLD on PI 7.0 the Logical System Name of a given business system is not present although the logical system name of the specified technical system does appear.  You cannot change the LSN of the business system since it relies completely on the LSN of the associated technical system.
    I used Jochen's approach before and it worked, but i've tried this again since i'm having the same issue.  Only now it doesn't work.
      i solved this issue by deleting the old BS and recreating it
    Thanks,
    Edited by: Jason Ray on Jun 24, 2008 5:47 PM

  • JDBC to Idoc scenario - change of logical system name

    Hi,
    I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
    Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
    If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
    Did i miss something resp. how can i load the current configuration from SLD?
    Thanks in advance
    Michael

    Hi Michael,
    Again Import the changed logical system in the Integration directory of you PI system.
    And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
    If they are showing old system then you have to replace the business system in all the scenario.
    Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

  • 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

  • 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

  • RSA1 - Source system connection : Change in logical system name

    Dear friends,
    Can you please tell me how can i change the logical system name for a source system connection.
    There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
    Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
    thanks
    ashish

    HI Sunny,
    This is not the same problem, may be similar though..i am not getting a way.
    let me describe u in a bit more details.
    Currently, we have a working source system connection to a system SID_CLT.  there is no change in source system.
    now, can i change this system connection technical name from SID_CLT to SIDCLNT*** .. 
    thanks
    ashish

  • RSA1 error  Logical system name has been changed for this system

    Hello All,
    Earlier the RSA1 was activated for client 300 on our crm 5.2. after that we changed the client to 500 using SE16 -> Type table RSADMINA / Check Colum BWMANDT -> 500.
    But now when we login to client 500 and execute RSA1 it is showing
    Logical system name has been changed for this system"
    In scc4 we have not made any changes. Can you tell what should be done ? in the pop up it is showing following steps
    Change the name of the logical system (table T000) for client back to SIDCLNT300. This enables you to continue working with the system.
    If you really want to change the logical name, than you can, if and when you:
    change the system name back to SIDCLNT300,
    delete all existing connections between this system and other systems,
    delete all transfer structures that still exist, and
    do not use ALE or Workflow.
    Guys do you know how to fix this ? .
    Also do you know Assignment of Source System to Source System ID (table RSSOURSYSTEM) using RSA1 ?
    Edited by: Sahad K on Mar 17, 2008 10:55 AM

    Hello Hari,
    Both the options you said  cannot be used
    since the logical system SIDCLNT300 is used by client 300 and it cannot be given to client 500.  Also there already exist a logical system SIDCLNT500 which is assigned to client 500.
    I found out the issue. In the table RSBASIDOC  the logical system name that can use rsa1( bw  client )is set as  SIDCLNT300).  Only if we delete that entry and set it to SIDCLNT500 ( 500) we can use it on client 500.
    The solution is specified in /message/3284842#3284842 [original link is broken]
    Let me try the solution 2 and inform you.
    Solution 2:
    You cannot delete the source system. Two cases have to be distinguished:
    The source system still exists.
    Switch to Transaction SM59. Find the destination which has the same name as the logical system of the source system from field SLOGSYS in table RSBASIDOC (see above).
    Such a destination does not exist in Transaction SM59. In this case, you have to create the destination to the source system. Name the destination equal the entry in SLOGSYS from above. Then return to the Administrator Workbench and repeat the deletion.
    The entry exists but a remote login is not possible. Correct the communication parameters.
    Everything works. Change to Transaction SE37, function module RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS = <log. name of the source system>, I_FORCE_DELETE = 'X'.
    The source system no longer exists or was replaced with another source system with the same IP address.
    Proceed as described in the first case but make sure, that the field 'Target host' contains a not existing server in the maintenance screen of the destination (Transaction SM59). If necessary, change an existing entry. Later when you delete, the system asks you whether you want to delete, although the source system is not available. Select 'Ignore'.
    Incase you have any idea other than this please let me know how to edit the RSBASIDOC table  and change the entry to client 500.
    Edited by: Sahad K on Mar 18, 2008 5:07 AM

  • Logical System Name Not appearing in the Business System

    Hi,
    Initially we had created a Technical system with Client 700 without a "Logical System Name" in SLD. hence the 'logical system name' in 'business system' was also Blank.
    Now, since we are implementing the IDOC to file scenario; we need to maintain the "Logical System Name" in the client and which in turn should reflect in our Business System in SLD.
    Though we maintained the Logical System Name in the Technical System --> Client --> Logical System Name; we are unable to see the same(Logical System Name) in Business System ('Integration' tab)
    Please also note that Business System is of the ROLE: Integration server.
    When we go to business system in SLD ---Integrtaion tab ---Logical System Name -- is still blank.
    Can anyone please help us to update the 'Logical system name' in Business System in SLD?
    Regards,
    Rehan

    Hi Sunil,
    I followed your link till
    Bussiness System -> select your bussiness System -> in Below pane u will find Details of your bussiness system ->amongs the various tabs available select Integration Tab->U will See option for technical system beside that u will see option for change ->click this ->u will be taken to Logical system ->there u define u r logical syatem name and then save the entries.
    When I clicked the option chnage ---> "Change Associated Technical System" appeared, It didn't take me to Logical system.
    But in turn I clicked hyperlink corresponding to Technical systems, it took me to technical system --> clients tab --I have entered the Logical system name.
    When I go back to Business system again its not showing the Logical system name in Integration tab.
    regards,
    rehan

  • Logical system name in SLD for the R3 buss. system is not open for input.??

    Dear all,
    We are upgrading to PI 7.1  and have a problem in a scenarie  where PI is sending IDOC to R3.
    The problem is probably related to the fact that it is not possible to write a logical system  name in SLD for the R3 system. I can not read the logical system name for the R3 system into the Directory (adapter specific identifier), *because the logical system for  the R3 bussines system is not an input file??*. How can i enter the logcal system name so i avoid following error:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Regards Ugur

    There are two ways....
    Option 1 : Go to the BS of ur R3 system in Integration Direction. Go to edit mode mode and select Properties -> Adapter Specific attributes - > enter the LS name and save...
    Option2 : You can use it from the mapping.... U either hard code/use from source the EDIDC40 section of ur mapping and the in ur IDOC receiver config select the option user
    Option ! is the best soln...All the IDOC to that R3 system will go the specified LS...
    regards,
    Arvind R

Maybe you are looking for