BDLS on BW Q/A

Hello all,
We have a situation where the client did a system refresh in our BW Q/A from BW Prod. They didn't change the logical system name back to LSYST01300 (R/3 Q/A) from LSYSP01300 (R/3 Prod.). This has been like that since Dec. 04 until recently, when a system refresh was done again, BASIS changed the logical system name back to LSYST01300 without running BDLS. Now, BW doesn't connect to R/3 and fails on transfer IDOCs. Can the IDOC error issue be fixed without running BDLS now or if BDLS is run, will it change all the InfoSources in BW that carry LSYSP01300 back to LSYST01300? Please advise. Thank you.
Praveen Punnam

hi Praveen,
you need to run the BDLS to change the logical system names in order to esatblish the communication between R/3 and BW.
after running the BDLS you need to replicate the source system in BW. Change the contents of the target host fields for all R/3 and Data Mart           Note 184754
source systems RFC connections to a nonexistent address.               (also 184971)
Update the target BW system name in table T000 using SM30.
Change logical system name in all BW tables using BDLS.Note 325525
SAPPRD600 -> SAPQAS100                        121163)
(Note: logical system name may be displayed using SCC4).
hope this might help
thanks
qandeel

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

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

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

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

Post System Refresh Activity - BDLS run

Hi,
We have finished system refresh of a QA system from Production. We need to run BDLS now to convert the original Production logical systems to QA relevant logical systems.
I am short of understanding of this process. Can anyone please help me with the concept and process?
Thanks in advance,
Abdul

Hi Abdul Rahim Shaik,
BDLS will convert the logical system name for your PROD to QAS.
For eg:
Your source - PRDCLNT100
Your target - QASCLNT100
If you go to SCC4 in your QAS, u will see Prod logical system name for the client.
Once you run BDLS after system copy, logical system name exist in every table for PRDCLNT 100 will change to QASCLNT100.
Refer to below link for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm
Cheers,
Nicholas Chang

Source systems vanishes from RSA1 after renaming of the LSN after BDLS

Dear BW/BI Experts,
           We are doing BW3.1 upgarde to BI7.0........After system copy there is need of rename of logical system for BP1 to BD1 (Prod. to Dev. and Dev. is our new Target BW system ) and From RP1 to RQ1. Before renaming I checked that all source systems were there in RSA1 i.e. Myself BW system , RP1 source system and Flat file source system as per SAP HOW TO ....System Copy in SAP Business Intelligence Systems Landscapes document. (almost 16 steps)
        But after running renaming program by BDLS , I saw source systems are vanished from RSA1..........and now I am trying to create source systems manually.........system is not allowing the same...........pl suggest...........waiting for your experts opinion......pl help urgently as I am in problem fromn last many days and did system copy more than 2 times considering that there may be system copy problem.......
While RQ1CLNT100 creation i.e.Source system ....I am getting follwoing error.........
Entry in outbound table already exists
Message no. E0404
Diagnosis
A partner profile (outbound paramters) could be found using the following key:
/RQ1CLNT100/LS//RSRQST////
This relates to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST    Test indicator
Procedure
Please check the EDI partner profiles.
and also following error after activation..........
Entry in inbound table not found     E0
Entry in inbound table not found     E0
The BW IDoc type ZSBA014 is not the same as the source system IDoc type ZSBC044     RSAR
The following errors occurred in the source system:     RSAR
Incorrect IDoc type ZSBA005 in the ALE definition of the source system     RSAR
Best Regards,
Sharad

Hi Sharad,
This is a very Basis-oriented task,
can your BD1 system can communicate with your peer ECC/R3 deveopment? you might need to run sm59 to ensure your RFC connection with ECC/R3 deveopment is communicating without problem.
once the RFC is ok, if you are familiar with WE20 and WE21 transactions, these transaction will configure IDoc setting (basis level) where you BI system will talk to, i believe IDoc are using old information copied from BP1 is still pointing to your ECC/R3 productive system at IDoc level. you will need to have Basis guy to help you out. please let me know if you need help on WE20 and 21, if you do, you need to provide me your current settings in BD1 and the peer ECC/R3 development setting as well.
cheers

BDLS Question?

Hello
I am using SRM 5.5 extended Classic and ECC 6.0.
We have recently re-pointed our test systems to a different R/3 test client and have changed some of the logical system names manually before running BDLS.
Please can you advise what will happen if I now run BDLS to change all of the other Logical system names that we did not change manually? Will there be any errors caused by this and will BDLS ignore those we have changed already or do you advise we revert them all back and then run BDLS? Or is there a way we can just exclude those before running BDLS?
Please can someone advise as this is the first time I have done this and I dont want to get it wrong?
Many thanks in advance.

Hello Pete
Thank you for coming back to me.
We had SRQCLNT300 pointing to ERQCLNT300 and now it has been changed to SRQCLNT300 pointing to ERQCLNT315 which is a copy of ERQCLNT300.
The RFC destinations were changed by the Basis Team and then we started to change the EBP and R/3 Logical system names manually as at the time were not aware of BDLS.
Therefore we do not know what the implications would be to now run BDLS if we have already changed some of the logical system names manually.
Hope this makes more sense.

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 errors

Hi,
We were connected to a R/3 source system before and ran BDLS to convert the logical system names for existing BW Dev system pointing to a new ECC 6.0 Dev system.
BDLS did convert some table entries but the cross-client tables with * did not create entries for the new source system in BW. We are on BI 7.0 SP16, could not understand why this transaction has failed. Carried out all checks on partner profile, RFCs etc.
I looked at RSBASIDOC table in both systems and BW, found entries for old and new systems. Is this cause of the issue?
How best could we complete this task?
Thanks,
Ramesh

The data sources have changed under the 'Datasources' tree of the AWB along with the infopackages. The datasources can also be seen under old source system, as both new and old source systems exist under the 'Source Systems' tree of AWB.
I have tried using the FM RSAP_BIW_DISCONNECT and delete RFC connection of old source system, but had a short dump with message type 'X'.    The entry in RSBASIDOC hence remains intact for the old source system and it would also not delete the source system from this tree.
DEVCLNT230 is the new ECC source system and DEVCLNT220 is old R/3.
The messages under the log after running BDLS is as below:
Identifies Cross-Client Tables
@AH@ Field in table already contains the name DEVCLNT230
@03@ Error in field of table . Manual correction required.
@0S@ SAPoffice No object reference exists -> No conversion
@0S@ SAPoffice Object references that have been converted: 0
@0S@ Partner profile for DEVCLNT230 / LS has been deactivated
@03@ Transformations already exist for DEVCLNT230
     Transformation 02BM1BCS3IN1LUIQ50J9EB2K2H583OSR deleted in version D of CNSLT_RAM_R
@0S@ Generate D versions from DTP_46ZBND1PVW8VB3Z90HHTKVQPQ (R/3700 -> DEVCLNT230)
     Table buffer in server synchronized after conversion
It seems there is an issue with the IDocs, can I revert all changes and start again?
Thanks,
Ramesh

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 Conversion

Hi All,
As far I remember in SAP 4.7 release after system refresh of QAS from PRD system, I used to run BDLS logical system conversion in all the QAS clients. But in the current project they do refresh in R/3, BW, APO on same day simultaneously, when they do BDLS on each system they run BDLS for all the systems(R/3, BW, SCM ).I am little confused why do we need to BW logical system conversion in R/3, I was thinking its enough to do BDLS in R/3, BW and APO systems individualy. Please advice me on this.
*Current system is NW2004
Regards
KVR

when you do system refresh with PRD
BDLS table has only PRD BW system and APO system details so to recognise BW qas and APO in QAS, R3 BDLS has to updated with BW and APO QAS system details similarly BW qas BDLS with r3 and APO and same with APO system
Samrat

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

BDLS in productive ERP system

I have an interesting requirement. A customer is currently running R/3 4.7 with multiple countries. They want to split the system so one country has it's own system. The approach has been to take the existing 3-system landscape and perform a homogeneous system copy to a new landscape. The catch is that they want to use the same corporate BI system for reporting, so BDLS must be run in the new landscape since these new systems will be connecting to the same BI system as the originals.
We know SAP doesn't officially support running BDLS in a productive system like this, but we don't see any other options. I've looked at the SAP Landscape Transformation documents, and while the Solution Map references "Split Systems" under the "Consolidate and Reduce IT Cost" Scenario, the guides don't include any documentation for this scenario.
I've split systems before, for example when a company sells off a subsidiary, but in those instances we left the old logical system intact.
Does anyone have any suggestions that would allow us to split the production system and have both resulting systems connect to the same BI system for reporting purposes?
Thanks,
Rich

My suggestion would be to run BDLS to change the logical system name of the ECC client only on the copied system.
Do not run the BDLS for changing the logical system name for BI client in the copied ECC system.
Before you do such a critical activity , make sure you simulate the steps on a temporary environment i.e building test systems for simulation. This would be quite a good approximation of the things to come .

BDLS in system refresh

HI all
I did a system refresh of BI .After running BDLS the logs in BDLS shows success. But logical systems are not getting converted.When I checked in SLG1it shows no coversion has taken place. Can any one help me to proceed further and change my logical system
Regards
-aj_

> Oh ok thanks but this was already done. what I mean to tell is If I run BDSL it is showing successful .When I check BDLS logs in SLG1 it is showing error. WHy this happens and what can be done?
Without knowing the error that you see how should we help you?
Markus

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.

BDLS on BW Q/A

Similar Messages

Maybe you are looking for