BDLS errors

Question

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

Answer 1

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