Conversion of logical system names

Hi
Must the Conversion of logical system names be set up in each client.
I.e in the BW production client do I have to go and setup what the conversion is between before the transport and after the transport.
Also if I then go into this view and want to add my conversion detail, and the system doesn't exist (in table) do I have to create the entries in Dev and Transport it through?
Corne

Hi Corne,
If the correct entries don't exist in the underlying tables, you have maintain it in SPRO.
The entry in the table is cross client. hence it has to be done in Dev.
Go to SPRO -> SAP Netweaver -> Business Intelligence -> Links to Other Source Systems -> General Connection Settings
-> Define Logical System
1. To create a logical system, choose Edit -> New Entries.
2. Enter a name for the logical system that you want to create.
3. Enter a description of the logical system.
If you want to cange this entry:
a) Select the appropriate line.
b) Choose Edit -> Change field contents.
c) Enter the new text.
d) Choose Replace.
4. Save your entries.
Roy

Similar Messages

  • Conversion of logical system name fails

    Hi,
    when trying to transport a transformation on BW7 the logical conversion name is failing. When i check the setup (on rsa1 menu "Conversion of logical system names") it seams to be ok on source and target system.
    Any tips to solve this ?
    thx in advance

    Hi,
    when you are not maiantained the logical systems properly , then you will get that error when you are transporting the objects
    in Bi production system ( to which server you are moving objects) in that  you should maiantain the all logical systems as below
    1) for examaple BI deve --- BI prd
    one logical systm should be bi Dev to BI prd
    2) ECC production connected to BOI production
    Then one more logical assignment  ECC prd to BI prd
    normally those two you are maintained i think so.
    but when you are moving the objects from the BI development to Bi production
    the daat sources are pertaining to the ECC developmet
    so that ECC deve to BI Dev ( here there is no problem)
    when those daat source s you are moving to production it shows error
    because that ECC deve Data source logical system should be changed to BI production
    so you main tain one more logical system ECC dev to ECC PRD
    in your BI system
    Then try reimport the same.
    Thansk & Regarsd,
    sathish

  • Conversion of logical System Name

    Hi,
    I have read somewhere that Conversion of logical System Name is part of BW System check Before go live. Can someone explain the purpose of it.
    Thanks in advance
    krish

    Hi,
    There are two different activities related to this, if you have done the system copy then for changing the logical system name we will run BDLS transaction. Check the below link for more information,
    [http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm]
    But if you want to move the source system dependent objects from one system to another system then we maintain the source system and target system mapping in target system.
    For transport method you can maintain the system names as suggested by Gaurav and you can check that in table RSLOGSYSMAP or you can directly maintain entries in this table.
    Regards,
    Durgesh.

  • Conversion of logical system names in queries

    hello,
    We have the following problem in our multisource model.
    Constant values have been assigned in queries in development : for instance, in line 1, the profit center is restricted to the constant value D3/9000/TTBC600
    D3 : development source system
    9000 : controlling area
    TTBC600 : Profit center code
    When we transport the query, we were expecting a conversion of the source system ID in this constant value but it is not the case.
    could you tell me if this is a normal behaviour??
    If yes, it means that we have to enter constant value in hard code without reference to the source system ID (indirect input, you cannot enter more than the length of the object i.e. TTBC600 in this case) and this can be at the origin of conflict if we have same code in different source system.
    Thanks in advance for any answer
    OD

    Did your transports move up ok to your target system?
    I am asking because your problem could be your mapping of source system to source system ID is not set up correctly or your "conversion of source system names after transport" is not set up correctly in your target system.

  • Conversion of Logical System name for "Error DTP" is not working

    Hi All,
    I have created a DTP and corresponding "Error DTP" for handling the Error records in development.
    But when i move the both the DTP's to Consilidation systems,
    DTP is getting converted to the consolidation R/3 systems (Example: TQS).
    But the "Error DTP" is not getting converted with the source systems as R/3 cosolidation systems (TQS) and remains as source systems as Development R/3 system(TDS).
    We are in BI 7.0 version with SP level of 13.Can anyone help how to resolve this issue? or any OSS note available to resolve this issue.
    Thanks,
    Muruganand.K

    Closing Thread.

  • Conversion of Logical systems

    Dear All,
                      we are in the process of coverting exsisting logical system name into new one thru BDLS.Please throw some suggestions on what are asll the areas should we take care, areas get modified like programs, rfc etc.Please reply asap
    Thanks in advance
    Umesh k

    after a system refresh, if your logical system is using a generic name such as BW-SYS instead of BWP-001, you can change the RFC connection hostname in SM59 and stop there.
    if you must change the logical system name because it it SID specific, then you must run BDLS. It can run in 2 hours... or 3 days. this depends on hardware specs and size of DB.
    to help you make it run faster and in parallel, read the interesting blog about BDLS at /people/hari.peruri/blog/2006/11/01/execute-conversion-of-logical-system-names-bdls-in-short-time-and-in-parallel--intermediate

  • BI:Logical system name has been changed for This System

    Hi, Gurus,
    I want to Use my IDES SAP ERP 7.0 as my BI system for training purposes,when iam executing the transaction RSA1 in the system it is giving message
    "Logical system name has been changed for
    system"
    I Have changed the entries in table "RSADMINA" and maintained the Client no as 100 (My base client for BI) which i have copied from 001.
    When iam executing the Transaction RSA1 in 100 it is giving above mentioned error ,whereas in 001 it is working fine.
    Please Help . ..
    I tried to change the system logical name by "bdls" but it doesnt worked........

    Hi Deepak,
    Check the entries in table RSLOGSYSMAP (this is meant for correct conversion of logical system names for tansports).
    You can easily maintain the entries using tcode RSLGMP.
    Hope it helps.
    Grtx
    Marco
    PS I'm not a basis guy but do you have a correct BI installation yet?

  • Table for conversion of logical system

    HI All
    please let me know the table name which will have all source system converion list.
    thanks in advance.
    thx
    vij

    Hi,
    Can also check at transaction RSA->Tools Menu->Conversion of logical system names(Displays all Source and Target Systems).
    Thanks,
    Rema

  • Logical system name conversion.

    We are performing a logical system name conversion of a client and its taking long time due to huge DB Tables like COEP.
    Is there any process to speed it up ? Also what will be the consequences if Consutants workin the Other clients of the same system.

    Hi Narendran,
    what problems would it create ? i am looking for some specific ones as i too would know that if a user works during the process the database tables which are getting updated with a new logical name would get corrupted and there is a possible chance that the table for eg VBRK woiuld be having a few entries with the old LS name. But my thoughts were in this direction. This report first converts the table T000 and then TBLST from where the MANDT and LOGSYS gets picked up many times. if they are converted every new entry which is entered will be having the new name and the old names are under the process. so how risk is it ? to allow a user to work is what i am looking for. This might be putting a test to SAP code but i am looking for this test as analysing this report would help us in many ways. you must be knowing that this report may run upto weeks, we had this experience in the last client copy and i am trying to check on this reports behaviour.

  • System Copy  and Logical system name conversion

    Hello All,
    Can any one let me know some inputs over these few queries.
    1. How much time would a 500+GB clients take for Export and reimport after the system copy.
    2. What would be run time of the BDLSS report ( Converting the logical system names) for a typical 1500 GB QTY system
    The requirement is my QTY has 3 clients, and i would like to refresh it with my PRD data. How do i safely perform thia activity with the least downtine possible and please note, the clients are around 500+ GB huge..
    Thanks in advance for your inputs.
    Rgds,
    Sri

    Hi Frank,
    the parameters of my installation are as folows.
    Appl Serv : OS - AIX (5.2 Version) and CPU's - 4 (Mem 20480) ::: DB serv : OS - AIX(5.2 Version) and CPU - 6 (Mem 22528)
    The DB version is Oracle 9.2
    We are on 4.7 enterprise version of SAP with SAPKA62055 patrch level.
    br
    Sri

  • Logical system name change

    Hi all,
    Now my BI development is pointing to R/3 development. R/3 logical sytem name is bbbclnt100. Now all my datasources are pointing to this logical system. Our basis people are going to change the logical system of R/3. Please tell me the repercussions? what will happen to my datasources?
    Thanks in advance

    Anni,
    Change logical system name and run BDLS job to adjust. Do not change souce system. If you change source system all transfer rules will get deactivated.
    Check: [Conversion of Logical Systems|http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
    Search forum for more links.
    Srini

  • Idoc Acknowledgements -  Logical System Name

    All,
    Stuck with a few issues with Idoc Acknowledgments which I hope SDN can help me with. For ease of understanding the problem, am splitting this into 2 Scenarios ,
    <u><b>Scenario 1</b></u>
    <b>SAP R3 (Idoc ) - XI - File ( Business Service)</b>
    R3 Triggers Idoc to XI and XI sends this as a File to the target Application. AleAdudits can be sent back to the R3 system as shown in <a href="/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc">this</a> blog by Saravana by adding the Logical System Name to the Business Service.
    <u><b>Issue :</b></u>
    R3 has configured Partner Profile with respect to XI and this cannot be changed. To send the Idoc Ack's back to R3 we need to add the Corresponding Logical System Name to the Business Service.
    The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.
    <u><b>Scenario 2: </b></u>
    <b>R3 - XI - BPM - Target</b>
    Idoc triggered from R3, are sent to a BPM and then from the BPM to a file. Everything works fine.
    But, the problem lies that when the Ack needs to be sent back to R3, The ack errors out because no Logical System Name is associated with the BPM.
    We do not want to add another logical system name to the BPM  and  thereby create another partner profile and the problem is similar to Scenario 1.
    <u><b>Solutions Explored</b></u>
    1. In the ACK_IDOCAdapter , I tried to select option Take Sender From Payload and Take Receiver from Payload.
    But this does not seem to help. I can see the trace in MONI saying the ACK_IDOC adapter is choosen  to send the ack back to R3 , but it does not take the Partner Names from the payload of the AleAdudit and errors out with  error <i>Unable to convert..</i>
    2. As this AleAduit is sent from XI back to R3 and is not a R3 (AleAduit) - XI - R3 (aleaduit) case, adding a entry as shown in Section 6 in
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb">this</a> document will not help.
    Has anyone tried something of this sort. Any known solutions?
    I hope the description of the problem made sense, if no, do let me know.
    Regards
    Bhavesh

    Bhavesh,
    Your problem as i understand -> <i>The problem is - what if the Idoc is to be sent to 2 Different Business Service / Systems. The R3 expects an Acknowledgment with XI as the sender partner but we cannot share the same logical system across different Business Systems / services . The easiest solution seems to be to create different partner profiles in R3, one for each Business System / Service. But this is not possible currently.
    </i>
    If the IDOC is sent to 2 different business services/systems/Integration Processes, then it is very logical that an ALEAUDIT be sent for each of these business systems/services. Ideally, you SHOULD NOT look at sending a common ALEAUDIT for different recievers in XI, the reason being, failures could happen only for one receiver and NOT for others. Failure could be in the mapping/content conversion. I am assuming here that you are configuring XI to send back "ALEAUDITs" only for System Error Acks(hoping it is possible, since i see 3 XXXs in the IDXNOALE table).
    So, it is logical that you configure a different LS in R/3 for each reciever system/service/IP, all these LS's will have one entry for ALEAUDIT in the Inbound params entered in WE20.
    If your intention is to send ALEAUDITs back only in case of errors, it makes sense to create an entry for each receiver in R/3. If not, then it is a limitation.
    Regards
    Saravana

  • Conversion of source system names after transport

    Hi gurus,
    Please someone can tell me how to configure the "conversion of source system names after transport"  in the BI system as my transport is not working on a new BI System  ?
    Thx in advance

    Hi Firmin,
    You can do this in RSA1 in tools under conversion of logical source system names.
    Here you maintain the development system or the system used for development as the source system.
    You will have to mention the logical name of the development system.
    In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
    Check the folllowing link for more informationn on this.
    [Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
    Hope it helps you ,
    Best regards,
    Sunmit.

  • Logical system name for acknowledgement in BPM

    Hi,
    I have a szenario:
    IDOC --> BPM --> MAIL
    Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
    When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
    "Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
    What can I do?
    Possible Solution 1:
    I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
    Possible Solution 2:
    I can enter an existing logical system name in the "adapter specific attributes".
    BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
    Is Solution 1) a common way?
    Thanx
    Regards
    Wolfgang Hummel

    Hi,
    there are many ways:
    some for aleaud are described in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    >>>>Is Solution 1) a common way?
    no this is not good a good idea
    BTW
    you can also supress aleaud raport IDX_NOALE
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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

Maybe you are looking for