Logical system BDLS

Hi,
We have done QA refresh from Production database to QA.After that I have done BDLS to change logical client name.This all was happned almost six months.Everything seems to be fine.
Just few days before we found that there are some tablems in QA which still shows production logical system and GUID.
Can we rerun BDLS now, is there any risk for to do redo this, because we have been doing many customization since 6 months after the refresh.Also can we find what tables are not converted and and change specific tables.
Appriciate if you can respond immdiately...
- Kristene

you can reset the BDLS settings and then run BDLS again or you can simply correct selected tables. for more information look here:
http://www.sapfans.com/forums/viewtopic.php?t=286945&highlight=bdls
also take a look at recent notes in service.sap.com/notes - 962674 might be an issue, 885343 points to the document.

Similar Messages

BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

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

BI 7.0, BDLS is not converting all logical systems for datasources

Hello all,
We have refreshed an ECC system, and during the post steps in BI, we were running into issues.
We've ran BDLS to convert the logical system from ECCCLNTXXX to ECCCLNTYYY, but it's was not converting for several datasources.
One in particular was causing several problems, and terminating the conversion.
0FC_CI_01. It is still hanging on to the old logical system. BDLS terminates with the following information:
Short text:
Active version of emulated 3.x DataSource 0FC_CI_01 cannot...
Basically, the exact symptom of Note 936644.
Eventually, through a series of trials, we discovered we could assign non-active sourcesystem/logical system combinations to the objects. As a result, we deleted the source systems entirely, ran BDLS to the ECCCLNTYYY, then recreated the sources.
This finally worked. What I need now is a root cause. Why would BI refuse to change the logical system of an object to an active one, but have no problem with an inactive?

Mike,
After running BDLS, you need to replicate the source system in BW, change the contents of the target host and fields for all R/3 and Data Mart(note 184754). Update the target BW system name in table T000 using SM30. Change logical system name in all BW tables using BDLS (note 325525)
Refer to the below doc for detail. Also refer to note 886102.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true]
Below note talks about similar issue.
How to change all infosources to the new source system automatically
Hope this helps.

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.

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 name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

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.

Could not determine BW release of logical system 'BWPCLNT100

after a BI systemcopy (production to development) we get the following
error when we run load jobs of type "delta load". full loads work fine
"Could not determine BW release of logical system 'BWPCLNT100'"
even if i start the deltaload from the R/3 system with transaction RSA3
with update mode "C" i get the same error . when i use update mode "F"
it works fine , but that's not the thing we want.
BWPCLNT100 is the logical system of the productive system .
we have changed all the logical system setting to BWDCLNT100 using
transaction BDLS and we have also changed all entries in RSBASIDOC,
RSISOSMAP, RSOSFIELDMAP,.... .
we have done several systemcopies in the past , they all worked fine
and without this error. this is the first copy in BI 7.00 .
are there any loadmodules which have to be regenerated with the new logical system name?
thank you for your help and kind regards hannes toefferl

Hi,
As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
This mainly happens due to init disturbance in the source system.
I would suggest you to delete the init and rerun the Init from BW once again.
This should solve your problem.
Thanks
Mayank

Is it possible to chenage logical system and how after a system is beeing u

Hello
I wander is it possible to chenage logical system and how after a system is beeing used for a while and how?

Hello Tina,
If the system is NOT a production system transaction BDLS can be used to change the logical system. This would be necessary after refreshing a dev system from a production system, for example.
If the system is a production system, I would agree that this is NOT advisable.
Regards
Greg Kern

Change of logical system name

Dear Experts,
I have following situation in ECC 6 EHP4 system:
a system copy of PRD system was peformed on QAS. POst system copy BDLS was NOT run, and logical system of QAS client was maintained manually.
Now client 300 in QAS has logical system as QASCLNT300 (after copy it was PRDCLNT300). The problem is that many accounting documents still point to PRDCLNT300 and hence can not be viewed now since log sys is QASCLNT300 now.
I can not run bdls now bcoz for BDLS target logical system should be new. Also for last few months new accounting docs has been generated for QASCLNT300.
Is there any way around? pls suggest
-Thanks,
Richa

This is a situation , where you cannot run BDLS now and you face issues with accounting docs .
As far as I feel , you will have have to redo the system copy and run BDLS again. The logical system name should never be maintained manually in SCC4.
Edited by: Ratnajit Dey on Jan 2, 2012 12:16 PM

Wrong logical system for prod categories

We had made a client copy and now the logical system name of R3MATCLASS in t.code COMM_HIERARCHY is still pointing to the old client; How can change we change this to the New client ?

Hello Rahul,
In case of client copy, you have to run transaction BDLS in order to convert old logical system name to new logical system name.
In this way, all tables containing reference to old logical system are updated with new value.
This should be true for logical system assigned to your product categories (table COMM_CATEGORY ).
Regards.
Laurent.

Logical System Change for Production System

Hi experts
We have new CRM and BI project. Logical System name of our ERP production system is not in naming standart. So we want to change logical system name and run BDLS in production system.
Is there any risk about this prosedure?
Best Regards...

Hi,
It is not advisable to change the logical system in production client once its assigned.
Regards,
Nisit

Logical system entry for table entry

Hi,
After system copy from one system name to another , I am facing some inconsistenices in various tables.
The table entry can be seen in se16.But when I try to select entries from the same table using SELECT statement, table are not getting populated.
I ran the BDLS also . How do I check the logical system entried for table where I have inconsistent entries?
Thanks,
Chitta

Hello Chitta,
But when I try to select entries from the same table using SELECT statement, table are not getting populated.
what are you trying to populate?
If your question is, its not showing anything... what error message you're getting? are you trying to run in the DB level?
If you're getting error, that this object doesn't exist in the database then you might not be logging with correct user. its an SAP table, then its owner is the SAP schema user. If you login with the schema user, it should show in a normal select statement. But if you login with <sid>adm then you have to give the correct schema id before tablename.
select * from <SchemaID>.<tablename>
SchemaID may be sapr3, sapsr3, or sap<SID> depending on your release.
Regards,
Debasis.

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 BDLS

Similar Messages

Maybe you are looking for