BDLS vs BDLSS vs RBDLS2LS

Hi,
I have some query about BDLS, BDLSS and RBDLS2LS?
1) Apart from the fact that in BDLSS logical systems can also be convert remotely in all partner systems. What other features are provided in BDLSS and why one should go for BDLSS and not BDLS?
2) Why SAP does not provide the feature of scheduling BDLS parallel process using bdls tcode, why we need to run RBLS2LS report to schedule the multiple BDLS process when BDLS and RBDLS2LS are nearly same?
Thanks,
Ankit Mishra

Hi Ankit,
From my understanding
As of SAP Web Application Server 6.20, SAP provides the option to convert logical systems using a new transaction that is more transparent and easier to use. Transaction BDLS has been used for this purpose until now. This transaction remains unchanged, and is enhanced by the new transaction BDLSS. In contrast to BDLS, in BDLSS logical systems can also be converted remotely in all partner systems.
Program RBDLS2LS - Conversion of Logical System Names: Old Version of RBDLSMAP
This program converts a logical system name, which has already beendefined in the system, to a new name. This program converts a logicalsystem name, which has already been defined in the system, to a newname. The program determines all relevant tables for the conversion,and converts the corresponding entries.
Reference links
http://help.sap.com/saphelp_erp2004/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm
1826348 - RBDLS2LS does not convert BW specifc tables
http://www.stechno.net/sap-programs.html?view=sapprog&id=RBDLS2LS
Hope this helps.
Regards,
Deepak Kori

Similar Messages

BDLS or BDLSS after Client copy

Hi all,
I am currently working on two systems ..SRM and ECC 6.0.In SRM and ECC.We have 2 clients 100(Development) and 120(Customizing) in both the systems.We recently did a client copy of production to our development clients and I have one confusion regarding the LOGICLA SYSTEM UPDATE which is one of the madatory steps post client copy.
For the LOGICAL SYSTEM UPDATE,do we need to run the transaction BDLS or BDLSS??What is the difference between these 2 transactins?Also what are the advantages /disadvantages?
My BASIS guy told me that during our client copy,BDLS was automatically run.Surprisingly,although BDLS was run,the logical system entries are not yet updated!
Please advise.

Hello,
You need to run BDLSS, which has enhanced functionalities of BDLS. Check the following link out:
[Conversion of Logical Systems|http://help.sap.com/saphelp_NW04s/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
For your question related the difference between BDLS and BDLSS, from the above link:
As of NetWeaver 6.20, SAP provides the option to convert logical systems using a new transaction that is more transparent and easier to use. Transaction BDLS has been used for this purpose until now. This transaction remains unchanged, and is enhanced by the new transaction BDLSS. In contrast to BDLS, in BDLSS logical systems can also be converted remotely in all partner systems.
Regards,
Shival

BDLS vs BDLSS

I used BDLS many times but can any one explain what exactly BDLSS used for?
I read that BDLSS can be used to change logical sys names remotly.(Can any one explain me on this)
thank you

Hi
Please check the following link:
http://help.sap.com/saphelp_nw04/helpdata/EN/33/c823dbaea911d6b29500508b6b8a93/content.htm
Regards
Chen

Tcode BDLS and BDLSS problem with logical system names

Hello!
I have following problem.
During the SAP ECC 6.0 installation we have forgotten to give the clients the logical names.
Now, during the customizing it is necessary to have all the tables with logical names, so I have given for all the systems a logical name.
Now I have problem to convert all the tables that were customized without logical to such with one.
<b>Is there some (semi)-automatical mechanism to do this or should I go to the SE16 and do it there?</b>
Thank you very much indeed
regards
Thom

Hi,
You need to do it from SE16 or SM30
Regards
Sudheer

After system copy (ccm), how to change logsys in catalog items?

Hello all
We're still on ccm 2.0 sp03 and did a system copy of our production ccm system to our test ccm system. But the catalog items still refer to the production logical system being the production R/3 system.
How can we change the logical system of catalog items without having to delete / rebuild our catalogs from scratch in our test system?
Using transaction BDLS or BDLSS does not work.
TIA
Renaud

Hi All,
I have similar scenario. Can anybody suggest the solution.
Regards,
Avinash

Client change in R/3 for BW

Hi,
We have a unit test client as X and now it has to change to Y.
I have heard about BDLS and BDLSS tcodes which help but I need some more clarifications:
1 - Will running BDLS/BDLSS takes care of all the things like datasources, trabnsfer rules, infosource etc?
2 - If yes then what is the procedure/steps to run BDLS/BDLSS?
If No then what additional tasks we have to perform to ensure that BW points to Client Y and everything is working fine.
Please suggest.

Hi Martin,
Thanks for your reply.
So r u saying that running BDLS/BDLSS will take care of everything?
Do I just have to delete and reload the data without touching the datasource, transfer rules, transformations etc?

URGENT: SRM doubts

hi sir,
i have some doubts in srm5.0 back end settings as shown below...
1) what is VMC& how to activate VMC in SM52?
2) what happend if i change the LOGICAL System for my naming convention in RFC destination?
3) why should we maintain the local RFC within the SRM OWN server for what purpose? EVEN i having a SRM server.
4) is it RFC user is a dialog user?
5) I want to know the T.CODES for each &every menupath. pls tell me the path for that.
my kind request to all can anyone send me solutions as written above questions URGENTLY.my id is <b> [email protected]</b>
WITH REGARDS TO ALL

HI,
ad 1) VMC is Virtual Machine Container for more information - look at link:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/a1/854ab9451048539e9131f19d3f9ab8/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/df8a715afb1631e10000000a1553f7/frameset.htm
ad 2) Every document created in SRM have a logical system attached to it. If You change it You must populate the changes. (e.g. in transaction BDLS or BDLSS )
ad 3) logical RFC (loopback) must be maintained. This RFC is used to communicate SRM itself.
ad 4) RFC user is a system user.
ad 5) I'm affraid I don't understand the question
Regards,
Marcin Gajewski

Runtime error while executing transaction BDLS

Hello,
While executing BDLS transaction for converting logical system names I am getting following error
Runtime Errors         CONVT_NO_NUMBER
Except.                CX_SY_CONVERSION_NO_NUMBER
Short text
     Unable to interpret "7,160 " as a number.
How to resolve the above problem?

Hi Rachel,
BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly
lives in runtime only and is checked by syntax checker.
Now, sometimes tables have inconsistencies associated with them and you
will get this dump when a syntax check is performed on them.
So please check this and regenerate the culprit tables.
So please redo the steps for BDLS and check. There are
probably some tables which could be determined by you (syntax
check - in case program has already been saved only)
An easy way to check this is to run RBDLS2LS program (old BDLS) and
afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>
<<)>(>
<<(><<)>)>ClientName>) program.
Known tables which caused such dumps in the past are:
DFKKCOLFILE_P_W
DFKKKO
DFKKMKO
DFKKREP06
DFKKREP06_S
DFKKREP07
DFKKREV06
DFKKREV07
Simply reactivate the tables you find out in SE11.
Another thing which has lead to this dump in the past is
in your R/3-System the value ' x ' is
additionally added to the value of your current release in the basis
release table SVERS.
The table RSBASIDOC takes the release value from the table SVERS.
If you change value 'x' to your release in both tables (SVERS and
RSBASIDOC) and
and activate again your source system connection. This could solve the
dump too.
I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)
b.rgds, Bernhard

BDLS failing with ASSERTION_FAILED dump

Dear Experts,
We have replaced the existing quality system DF0 with RC0.These both system are quality systems and RC0 has been refreshed from production.
So in BW qulaity system we need to replace the DF0 with RC0 as source system. I have created logical system name LSRC0310 for RC0 in BW qulaity system and ran a BDLS to convert DF0 to RC0. But it is giving a dump ASSERTION_FAILED.
Earlier it failed with error that logical system LSRC0310 name alreday exists.So i deleted the logical system name and ran BDLS but it again failed with same error.I have checked the logs and it just makes an entry in table TBDLS, TBDLST. The logs in BDLSS also says that the conversion went in error with "Error in field of table . Manual correction required."
Thus the source system DF0 is not replaced in RSA1 also i can still see cubes pointing to DF0.
I have referred to Modify source system link but it is failing in the BDLS step so cannot proceed ahead.
Please can you guide and help is solving this issue.
Regards,
KUldeep.

Thanks Walter for your reply.
This note is already present in the system and still BDLS fails with this message.
I hope my approach is correct.
Currently source system is DF0 and we want to convert to RC0. So running a BDLS will convert all the logical source system names for all the transfer structure and DTPs and transformations.Then after BDLS step i can restore the source system in RSA1.
Please confim if my this is feasible.
Regards,
Kuldeep.

BDLS performance - how to speed up BDLS run?

Hi all,
Although my database is not huge (1.5Tb), BDLS run takes a lot of time - 26 hours
I found very nice blog - /people/hari.peruri/blog/2006/11/01/execute-conversion-of-logical-system-names-bdls-in-short-time-and-in-parallel--intermediate, but since I have Basis 6.40 - it is not suitable for me.
I tried anyway - got inconsistency, I had to implement note 962674
I guess my only workaround is to use the old program RBDLS2LS ..
Any ideas how else I can speed up bdls run?
Many thanks in advance,
Best regards, Elena

Hi Elena
What possibly can be done in such a case could either be a reorganisation of the tables that are accessed at the database while running the transaction BDLS or customizing the source code of the program RBDLSMAP (used while calling BDLS transaction) such that the no. of accesses to some not so important tables get reduced.
for e.g. say after a refresh ,if we Consider taking out some table such as the infamous PA2* tables (if using HR)
and send this in the background, it will go faster because the TEST phase is ignored. you might save about 2 hours just with that.
Regards
Chen
Edited by: Chetan Seth on Feb 19, 2009 4:36 PM
Edited by: Chetan Seth on Feb 19, 2009 4:37 PM

BDLS in BI 7.0 / NW04s

Hi Gurus,
Has anybody ran t-code BDLS against BI 7.0 datasources? Does BDLS operate the same changing the transformations as it did with transfer rules BW <= 3.5?
My scenario is I need to pull data from our R/3 test system (R3TClnt100), instead of our R/3 Dev (R3DClnt100) system. We've mapped all transformations already to extract from BI 7.0 datasource extracting from R3DClnt100. Will BDLS work for this scenario?
Kind Regards,
Alex

it seems there is now an enhanced tcode BDLSS..
see below link..
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm
also see below thread..where I had experienced same problem..though not in BI 7.0..
Fresh source system clients in production BW system
Vishvesh

BDLS finishing immediately without conversion

Hi all,
BDLS run is finishing immediately, job without failing, BDLSS logs below. Not showing tables and the check with 0 etc. Other runs for other logical systemname conversions for ECC/BW ran successfully. Pls help ASAP
    Log for conversion: CRPCLNT100 -> CRQCLNT100 in system QAS400 (initiator QAS 400)
                                                                                02/17/2015 14:45:04 KRAJAN
<    Table T000 was not relevant for conversion
Table Name                Field Name       Number of Relevant Entries    Number of Converted Entries
<    SAPoffice Object references that have to be converted: 366
<    SAPoffice Object references that have been converted: 0
<    SAPoffice Object references that contain another LogSystem: 60
<    SAPoffice Object references that do not contain a LogSystem: 306
     Table buffer in server synchronized after conversion
     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: 'RSSTATMANPSAT'; number of changes: ''
     Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
     Converted table: 'RSMDATASTATE_PSA'; number of changes: ''
     Converted table: 'RSMSTATMANPART'; number of changes: ''
<    The processs is executed in the background (RBDLSMAP 14450000) in system QAS400
Thanks,
Kavitha Rajan

Hi Kavitha,
Hope you are doing good. Nice to hear from you again.
Not sure if note 1406273 helps:
a) no records for either the old or the new name -> table skipped
b) records with the old name exist -> conversion goes through
c) records with the new name exist -> table skipped with warning => no manual intervention needed, but doublecheck is recommended. In this case the conversion log shows '<<' at the affected tables
d) records with the old and the new name coexist -> records are skipped with warning or error (depending on the flag for existence check, which is always set except in test conversions) -> you have to analyze the records and to manually delete that records which hold the old logical name and have their identical counterparts holding the new name. In this case the conversion log shows '<<<<' at the affected tables.
Hope this helps.
Kind Regards,
Hemanth
SAP AGS

BDLS - How to monitor the process?

Dear All,
I am running the BDLS sessions in Background (excluding the known huge tables) now in my Testing System just after the system refresh activities from Production to the Testing.
The BDLS sessions run more than 22 hours (still in progress now ) , may I know where ( which tcode ) I can see the progress of the BDLS?
I've tried to check in Txcode SM50, the BGD process performing a sequential read on a table for more than 8 hours...Is it possible hang in somewhere ? May I know how to determine if the BDLS is 'hang' ?
FYI, the table size that the BDLS running on is around 140GB..
Best Regards,
Ken

Dear Raja,
the log i get from BDLSS shows the table processed until :s
CATSHR                    EXTSYSTEM                           0
LOGSYS                              0
CATS_BW_TIME              I_RLOGSYS                           0
CATS_GUID_KEY*            EXTSYSTEM                           0
CBPR                      LOGSYSTEM                           0
CC1ERP                    SRCSYS                              0
CCMCTIADMIN               LOGSYS                              0
Dear sekhar,
Do you meant the job log from SM37 ? :
22.02.2010 09:59:19 Job started                                                                         00
22.02.2010 09:59:19 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID BASISADM7)      00
22.02.2010 09:59:19 The new logical system name T00CLNT300 is assigned to the current client 300        B1
Edited by: Wei Jian Kwan on Feb 24, 2010 1:00 AM

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

BDLS failed in new system

Hi all,
We are experiencing an error when runing BDLS in SAP BW 7.0.
To give you an overview, I am working on a new production system called BWP (copy of an acceptance system).
Attached to this new BW system, we have a new source system called BRP.
In order to change the source system of the old system, I run BDLS (after a successfull test run) with the second option (following a client copy). I noticed that unfortunately, nothing was changed.
So, I decided to run BDLS again with the first option.
First, I did a successfull test run, and I noticed that much more table will be converted.
After the test run, I launched the real conversion...
Unfortunately, after a while, BDLS is stop and I have the following message:
"The datasource XX_XX_XXXX_XXXX(BRP100)" does not exist in object version A".
On my side I tried lot of things:
- I tried to activate the datasource, but it's not working.
- I tried to change value in the table RSDS (datasource) but one more time it didn't worked.
- I tried to reconnect the original system to replicate the datasource in order to activate it, but it didn't work.-
Do you have any ideas how to bypass this error?
If you have any experience to share about BDLS, do not hesitate

Hi,
This is error code RSDS062. It means that the datasource cannot be found in the tbl RSDS.
So search in RSDS for the datasource, & check what version it is.
If OBJVER is M, then it must be activated.
Did you follow SAP Note 886102 for the system copy?
You need to follow each step of the scenario pertaining to your copy.
When running BDLS, generally four scenarios can happen:
1) no records for either the old or the new name -> table skipped
2) records with the old name exist -> conversion goes through
3) records with the new name exist -> table skipped with warning =>
    manual intervention needed, but doublecheck is recommended. In th
    case the conversion log shows '<<' at the affected tables.
4) records with the old and the new name coexist -> records are skip
    with warning or error (depending on the flag for existence check,
    which is always set except test conversions) -> you have to analy
    the records and to manually delete that records which hold the ol
    logical name and have their identical counterparts which are hold
    the new name.
Also, implement these notes if missing from your BW system:
1224597 P19:BDLS:DataSource not converted
1142908 70SP19: BDLS does not convert DTPs
1149141 70SP18/19: BDLS: Improvements log
1148403 70SP18: BDLS after early replication
Rgds,
Colum

BDLS vs BDLSS vs RBDLS2LS

Similar Messages

Maybe you are looking for