Logical System Conversion issue

Hi All,
BW (DW100) is connected to two clients say DE100 and DE200. Some of the objects in BW are pointing to DE100 and some of the objects are pointing to DE200.
Now we planned to make all the objects pointing/connect to source system DE200 not to DE100. The objects pointing to DE100 are created in DW100 in Release 1 and objects ( Release 2 ) pointing to DE200 are moved from another system development system.
What is the best approach to make it more stable because some of the objects are used in DE100 and some of the objects are used in DE200 . In process chain, we have infopackage and DTP connected to DE100 and for some objects connected to DE200.
What we planned means first run the BDLS from DE100 ( old Logical system ) to DE200 ( New Logical system ) and re-traanspotr the TR ( Release 2 ) to DE200.
COuld you please advise here what should be the best approach?
TIA

Completely depends on the way the production system exists - if it exists with a single client, then life is easy.
You might have connections to a BW system from source system with two clients. But if the target system has only one client, then you can just transport the Transport requests from both of these clients to the target system.
Meanwhile you can transport the TR's from BW system which connects to 2 clients to a target system with one client. But you need to maintain the proper details in source system conversion table in the target BW system, else the transports will fail at the import step.
Regards,
Thejas K

Similar Messages

Help for Job BDLS - Logical System Conversion aftrer System Refresh

hi SAP Basis Gurus,
We have restored production data to test system. After that we are doing Logical System conversion - Renaming of Logical System Names. For that we are running BDLS job. The program used is IBDLS2LS.
Now one job is running for more than 200000 seconds. Job is doing "Sequential Read" on table ZARIXCO40. The following has been updated in the jobs log:
01.02.2008 10:20:06 Processing table ZARIXCO40
02.02.2008 01:59:56 Processing table ZARIXCO40
02.02.2008 22:26:44 Processing table ZARIXCO40
02.02.2008 23:04:05 Processing table ZARIXCO40
So as per above log, it looks like job got stuck in loop for table 01.02.2008 10:20:06 Processing table ZARIXCO40.
The oracle Session is showing following SQL Statement:
SELECT
/*+
FIRST_ROWS
FROM
"ZARIXCO40"
WHERE
"MANDT" = :A0 AND "LOGSYSTEM" = :A1 AND ROWNUM <= :A2#
~
Execution Plan is :
~
Execution Plan
Explain from v$sql_plan: Address: 00000003A2FD5728 Hash_value: 2772869435 Child_number: 0
SELECT STATEMENT ( Estimated Costs = 4.094.270 , Estimated #Rows = 0 )
 3 COUNT STOPKEY
 2 TABLE ACCESS BY INDEX ROWID ZARIXCO40
 ( Estim. Costs = 4.094.270 , Estim. #Rows = 32.799.695 )
 1 INDEX RANGE SCAN ZARIXCO40~0
 ( Estim. Costs = 418.502 , Estim. #Rows = 65.599.390 )
 Search Columns: 1
~
Table has been analyzed today. See the details below:
~
Table ZARIXCO40
Last statistics date 02.02.2008
Analyze Method mple 16.623.719 Rows
Number of rows 65.599.390
Number of blocks allocated 2.875.670
Number of empty blocks 7.912
Average space 934
Chain count 0
Average row length 313
Partitioned NO
UNIQUE Index ZARIXCO40~0
Column Name #Distinct
MANDT 1
KOKRS 14
BELNR 2.375.251
BUZEI 1.000
~
Index used for this table is also analyzed today:
~
UNIQUE Index ZARIXCO40~0
Column Name #Distinct
MANDT 1
KOKRS 14
BELNR 2.375.251
BUZEI 1.000
Last statistics date 02.02.2008
Analyze Method mple 24.510.815 Rows
Levels of B-Tree 3
Number of leaf blocks 418.499
Number of distinct keys 65.480.722
Average leaf blocks per key 1
Average data blocks per key 1
Clustering factor 40.524.190
~
Can you please let me know what could be the issue and how to resolve this issue so that job gets completed. Normally this job runs for 1,00,000 seconds. I can not afford to cancel this job and run again.
Any help is Highly appreciated,
Thanks
Best Regards,
Basis CK

Hi Markus,
The stastics of the table is already updated today. After that also it is not going faster. It is doing "Sequential Read" for more than 5 hours and then one update is issued. And in the job log, all other tables are preocess only once, only this table is selected to processed 4 times which is very abnormal.
01.02.2008 07:43:59 Processing table ZARIXCO11
01.02.2008 07:45:36 Processing table ZARIXCO16
01.02.2008 10:17:20 Processing table ZARIXCO21
01.02.2008 10:20:06 Processing table ZARIXCO26
01.02.2008 10:20:06 Processing table ZARIXCO29
01.02.2008 10:20:06 Processing table ZARIXCO33
01.02.2008 10:20:06 Processing table ZARIXCO37
01.02.2008 10:20:06 Processing table ZARIXCO40
02.02.2008 01:59:56 Processing table ZARIXCO40
02.02.2008 22:26:44 Processing table ZARIXCO40
02.02.2008 23:04:05 Processing table ZARIXCO40
~
I guess this will keep on going like this and not sure when it gets complete. Any other thing you can suggest which help to resolve the issue.
Thanks
Best Regards,
Basis CK

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.

Procedure to restart cancelled BDLS (logical system conversion) !! Urgent

Hello Experts,
I need immediate help. I started the BDLS (logical system name conversion) and it was running for about 3 days. It was about 70% complete. But because the users could not afford downtime, I cancelled the BDLS job. When I tried to restart BDLS later, it is giving an error "Logical system name already exists". Kindly note that we are on R3 4.6C environment with CRM 4.0. The BDLS conversion is on R3 4.6C QA which was refreshed from R3 4.6C prod.
My question is
1- Is there any way to restart BDLS on R3 4.6C? If so, what is the procedure?
2- The BDLS was 70% complete, before it was cancelled. So it created a new logical system name. Is it possible to delete this new logical system name without any problems?
3- Because BDLS converted 70% of the tables from old logical system name to new logical system name. There might be data inconsistency.
3a- Is there a way to reset all the converted tables to old logical system name?
3b- Is there a report or program or a procedure to reset the BDLS?
4- Will this state of having 70% of tables with new logical system name and 30% of tables having old logical system name create any problems for the data transfers and for the business?
Kindly help me in this regard as this is a very urgent issue. Points to be awarded for any kind of small help.

Thanks a ton Srikishan. I will do the same as you have said.
A couple of more questions.
1- Do I have to start this immediately now, in the morning hours, asking all the users to get disconnected or schedule it later, during the night time or on the weekend.
Will this current state of having 70% of tables with new logical system name and 30% of tables having old logical system name create any problems for the business?
2- If this there a way ( a program, a procedure) to reset changes done by BDLS?
Kindly note that due to the database being large, BDLS is taking 3 days. So I cannot do this during the week days (during business hours), I will have to reschedule this during the weekend.
Please let me know. Thanks.

How to change name of a logical system

Hi SDN,
I am trying to customizing intial download data transfer from ECC to CRM. But in outbound queue of ECC it is showing an error of SYSFAIL with description of logical system name changed. Given note 558701.
But I don't know old name of logical system.
1) Can you guys please help how to find the old logical system name there are many logical systems defined in my system.
2) and how to change it?

Hi Ravi,
Since logical system name is changed sombody in past must have ran BDLS to conver logical system name.
Check tcode SLG1, this tcode will tell you whether there were any logical system conversion done in Past, if it is done then it will tell you from which old logical system its converted to new one. So you can find out old logical system name.
Once you find out old logical system run BDLS again. It might possible BDLS ran unsuccessfully last time.

ATP Check Issue - No business system could be determined for logical system

Dear all
Got an issue while executing ATP check on a planned order in product view,
with a message: "No business system could be determined for logical system"
CIF setting wise:
regular business system group maintained and assigned in place,
master data wise:
business system group info fine in product master,
Is there anywhere suggested to check under ATP setting:
category, check mode, business event, check control/check instruction?
Your kindest enlighting is appreciated,
Thank you,
mandy

Dear Mandy,
usually this error is caused by a missing customizing entry:
spro:
Integration with SAP Components
   Integration via APO Core Interface (CIF)
     Basic Settings for Creating the System Landscape
       - Maintain Business System Group
       - Assign Logical System and Queue Type :
Please read the documentation for these two transactions and create the systems.
You need to specifiy there all systems that are in your BSG. The documentation for the customizing of 'name logical system' in APO says:
To enable the transfer of data between SAP R/3 and SAP APO, you need to name both the SAP APO system in which you are working and the SAP R/3 system to which you want to transfer data as logical systems.
I hope this helps.
Regards,
Tibor

SolMan / BW Logical System Issue

Hello all, I am having a SolMan/BW related issue and would really appreciate some advice. I realize some of this is for the BW forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1
I am embarrased I missed this section in the master guide the first time around.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.
I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.

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

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

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.

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

Need hlep! The issue about creating a logical system!

Hi all,
When I create a new logical system, and T-code is BD54. My user profile is SAP_ALL and SAP_NEW. The system pop-up the Warning message as follow:
You are not allowed to change cross-client customizing.
I have looked it into
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/b4/b0b13bb3acef3ce10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/b4/b0b13bb3acef3ce10000000a11402f/frameset.htm</a>
and the document explain the administrator role can create a logical system, but I do not know how to assign administrator role to a user.
Could anyone tell me how to do it or other solution.
Thanks in advance! Any help is appreciated!

Hi Feng, Welcome to SDN.....

SAP_BC_BASIS_ADMIN - Assign this Role to your User name in SU01 and then try creating Logical system, Also check the Client setting in SCC4(such as the client Role, Cross-client object changes...). Hope this Resolves your issue.
Cheers...
Santosh.
Reward Points if Answer is Usefull

Logical System Conversion issue

Similar Messages

Maybe you are looking for