BDLS failed in new system

Question

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

Answer 1

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