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

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

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

Conversion of logical system

Hi,all,
I have 3 BI box - BWD, BWQ, BWP, and 3 R3 box - R3D, R3Q, R3P, before I transport datasource, infopackage from BWD to BWQ, I configured the conversion of logical system in BWQ as: BWD -> BWQ, R3D -> R3Q, that works fine, So before I transport to P, how should I configure this mapping in BWP: BWD -> BWP, R3D -> R3P or BWQ ->BWP, R3Q -> R3P?
Thanks a lot.

Hi,
You can input all four or you can input the combinations going from your Q to your P system. Both will work...
-Jacob

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

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.

TDMS - conversion of logical systems

Hello,
during execution of activity "Assign Logical system names in receiver systems" I got empty list. Normally I was getting whole list of logical systems for both sender and receiver system. And now I have nothing...with message "No logical system name maintained for Receiver Systems".
Of course I checked BD54 and all entries are there, both systems are open, both on SP15.
Any suggestions from anyone?
cheers
Michal

You can also cross-check in table TBDLS or txn BDLS.

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.

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

Logical system with business service

hi,
can we have a logical system with business service just like we have with business system?? If yes,how can we create logical system for business service??
Ratna.

Hi,
If you intend to use it with IDoc adapter it might be also necessary to set up corresponding Logical System (tcode: BD54) in adequate backed system.
Refer conversion routine (logical system vs. service) in this presentation [Using the IDoc-Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd] - page no 6.
Regards,
Jakub

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?

Conversion of source system while transport

Dear Experts,
We have following landscape:
BID (BI dev)
BIQ (BI QA)
BIP (BI Prod)
and
R3D (R3 dev)
R3Q (R3 QA)
R3P (R3 Prod)
For transport we have made following settings for
"conversion of source system name after transport":
In BID system (BI dev)
BID->BIQ
R3D->R3Q
Question-
-Where do I mention settings for production?
-Can I make folowing settings in Dev so that it works for all the transport?
BID->BIQ
R3D->R3Q
BID->BIP
R3D->R3P and no settings in BIQ and BIP environment.
-Do I need to mention below settings in BIP (BI prod)
BID->BIP
R3D->R3P
Thanks

Hello,
Please log into the system in which you are trying to import the transport in and go into transaction code RSA11 and then ino "Tools --> Conversion of Logical System Names".
In order to change the values the system needs to be modifiable and the person having the change access should be doing this (which would be the BASIS team if the security is set properly).
So, in BIP system in your case please go into the above path and maintain the entry for BID --> BIP and also R3D --> R3P.
The whole purpose of doing this is to make sure that the datasources which have the source system property get converted into the appropriate source system names when transported over multiple environments.
Please assign the points if this answers your question.
Let me know if you need additional information in this regards. If you don't have the access you can check if these parameters are set or not by accessing the view "V_RSLOGSYSMAP" in the system.
Thanks
Dharma.

Logical System Conversion after system refresh failed

Hello,
Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
02/18/2009 16:09:33 Job started                                                                     00           516          S
02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
02/18/2009 16:10:19 Job finished                                                                    00           517          S
When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
Any suggestions on this?
Thanks,
Mahesh

Hi ,
Rerun the BDLS again as this took very little time.
When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
Thanks.

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.

Conversion of Logical systems

Similar Messages

Maybe you are looking for