BDLS problem

Hello,
i have created a BW 7 system copy - after finishing all post installations , i had to run the bdls for the source system since it was changed from the original copied BW system.
now whenever i try to run bdls with the old and new logical system name i get the following error -
The DataSource ZCORP_COST_HIST(LQACLNT320) does not exist in object version A.
LQACLNT320 is the new logical system name of the source system.
when i check in transaction RSDS i can see that the above datasource ZCORP_COST_HIST exists under the original source system logical system name but does not exist under the new one - as the error message tells
can anyone assist in solving this problem?
Regards,
Moshe

Hi Moshe,
With regards this error:
"The DataSource ............... does not exist in object
version A
Message no. 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.
Check for the entry in tbl RSLOGSYSMAP, which specifies the mapping details.
Also check in tbl ROOSOURCE for the Myself. There you should have the entry for the datasource. If you do not see entry there is some problem and this caused to generate error. So make sure that mapping of the system are correct in table
RSLOGSYSMAP.
If you have no issue with above, then check the following:
- make sure that the datasource is available in the source system.
- also check that the RFC connection to system is ok in SM59.
- make sure that the system must be open to changes.
Rgds,
Colum

Similar Messages

Is there any problem running again "bdls" after being disconnected while r

Hello
I have an emergecy question
Is there any problem running again "bdls" after being disconnected while running it (my network connecton to laptop got broken)
Thank you in advance

Hi,
Be sure that it does not continue to run. If it was really interrupted, yes, you must run it again. Otherwise you would have a lot of inconsistancies.
Regards,
Olivier

Problems in BDLS

When running BDLS I have error in fields of following tables:
EDPP1
VBAP
TBD06
USZBVLNDRC
USZBVSYS
USZBVPROT
USZBVPROTC
Is there manual correczion required and which?
Thank you in advance

Hi Jan
May be those tables are having duplicate entries. Suppose you want to change PRDCLNT100(your source logical system name) to QASCLNT100 ( your target logical system name). But EDP21, EDP13 and EDPP1 contain 2 or more entries of PRDCLNT100 before converting. Then you will get problem ( or error message) during conversion. What you need to check that whether those tables contain QASCLNT100 or not. Sometimes, extra entries show error message during BDLS but they are harmless. For above mentioned tables if you can restore all the source system connections successfully after system copy then its fine. Please ensure RSBASIDOC and RSLOGSYSDEST contain proper entries
Please check the log of BDLS from SLG1 ( Object CALE, Subobject LOGSYSNAME).
Hope this helps. Please get back to us if yu have further questions

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.
Is there some (semi)-automatical mechanism to do this or should I go to the SE16 and do it there?
Thank you very much indeed
regards
Thom

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

Problem With BDLS

We have done an intallation witch is based on an exported database system.
In the new system i have launch the BDLS transaction with PR2CLNT300 ( like old logical system name) and QA2CLNT300 ( like new logical system name )
We have for making some test for adapting the new link between BI and R3 and we have re-run the BDLS transaction: this time the old logical system name was QA2CLNT300 and the new one QA2CLNT210.
Like the error was always there we wanted to run again BDLS to come in the same state after the first BDLS ( with the new logical system name : QA2CNLT300)
But i have this message : The logical system name QA2CLNT300 already exist.
is there a way to return in this state ( QA2CLNT300)?
Regards.

Just hit enter and the message will go away and continue.
Thanks,
Naveed

Problem while creating a system copy

Hi guys,
I've created a copy of my original BW system with the database copy of SQL server procedure:
1. Copy DB from "old" system and perform "post" activities (SID change, BD54 and after - BDLS -"old" logical sys. Name to "new" one..).
2. Verify RFC to ECC source system and create new RFC in ECC source system to "new" BW system.
3. Make BW logical system known to ECC source system (BD54).
4. RFC names are the same as Logical system names (both BW and ECC sides).
When I try to restore the source system connection (The original one) on the "new" BW system I get the following message:
The Connection BA is used in the PRD300YPCC. Source System as a Connection BWPCLNT550 to BW.
Do You Want to Delete this Connection in the Source System? The Connection is Restored After It Has Been Deleted Successfully.
If I answer delete - than the source system is working on the new copied BW system. But the original source system on the original BW system will have the same problem I'm having with the copied systems. This means that only one system could be connected to the ECC production on the same time.
Is there a way to make it work - i.e have both BW systems connected to the same ECC system. We want to have it done so we could upgrade one system and check it against the productive system.
Thanks alot,
Tomer Steinberg.

Still not solved.

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

Problem with Business partner flow from R/3 to CRM

Hi,
We are setting up a process to flow of Business Partners from R/3 to CRM.
We have configured PIDE correctly but the problem is when I am creating any customer in R/3 we are getting DUMP.
Kindly help me in this regards.
Thanks

Hi,
Check out the following Middleware Configuration :
 CRM Middleware configurations
1. Source client for Client copy
 Using t-code SCC3 in both CRM and ISU to get the source client used for client copy. Get source client for profile SAP_ALL.
2. RFC Destinations
 Use t-code SM59 and check if the following RFC destinations have been created:
 CRM
o R/3 Destination for CRM e.g. CRTCLNT240
o R/3 Destination for ISU e.g. ISTCLNT240
o Logical Destination for Middleware R&R queues one for current client and one for client 000. e.g. SAPCRM_MW_RR_240, SAPCRM_MW_RR_000
o TCP/IP Destination for IPC dispatcher e.g. IPC_RFC_DISPATCHER
o TCP/IP Destination for IPC server e.g. IPC_RFC_SERVER
 ISU
o R/3 Destination for CRM e.g. CRTCLNT240
o R/3 Destination for ISU e.g. ISTCLNT240
3. Logical Systems
 Using t-code SALE check if the following logical systems have been created:
 CRM
o Own logical system e.g. CRTCLNT240
o Logical system for ISU e.g. ISTCLNT240
o Logical system for source client used in client copy e.g. CRTCLNT200
 ISU
o Own logical system e.g. ISTCLNT240
o Logical system for CRM e.g. CRTCLNT240
o Logical system for source client used in client copy e.g. ISTCLNT200
 Check if own logical system is assigned to the client.
 Path: Sending and Receiving systems -> Logical Systems -> Assign Client to Logical System.
 Convert Logical System name in application tables
 Use t-code BDLS to convert logical system names in the application system.
1. Enter old logical system name retrieved in step 1. e.g. CRTCLNT200
2. Enter new logical system name e.g. CRTCLNT240.
3. Select radio button Conversion of Client-Dependent Tables and execute the transaction.
This process needs to be carried out 4 times: twice in CRM and twice in ISU.
 CRM
o Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
 ISU
o Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
4. Middleware Parameter tables
 Use t-code SM30 to maintain middleware parameters in following tables
 CRM
o Table SMOFPARSFA:
 Change value for following parameter entry:
 Key - R3A_COMMON
 Para name - CRM_DEFAULT_DESTINATION
 Value - Old ISU logical system -> new ISU logical system
 E.g. ISTCLNT200 -> ISTCLNT240
 ISU
o Table CRMRFCPAR:
 Delete the previous entry for the following key:
 User - CRM
 Object name - *
 RFC Destination - Old RFC destination for CRM e.g. CRTCLNT200.
 Load types - All Load Types
 Create new entry with following data:
 User - CRM
 Object name - *
 RFC Destination - New RFC destination for CRM e.g. CRTCLNT240.
 Load types - All Load Types
 In Queue flag - X
 Send XML No XML
o Table CRMPAROLTP:
 Change value for following parameter entry:
 Para name - CRM_DEFAULT_DESTINATION
 User - CRM
 Value - Old CRM logical system -> new CRM logical system
 E.g. CRTCLNT200 -> CRTCLNT240
5. Admin Console (Sites and subscriptions)
 Using t-code SMOEAC in CRM change attributes for the following sites.
 CRM site
o Name: Change name from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o Description: Change description from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o Site attributes: Change RFC destination from old CRM RFC destination to new CRM RFC destination e.g. CRTCLNT200 -> CRTCLNT240
o Click on get values button to refresh logical system details.
 ISU site
o Name: Change name from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o Description: Change description from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o Site attributes: Change RFC destination from old ISU RFC destination to new ISU RFC destination e.g. ISTCLNT200 -> ISTCLNT240
o Click on get values button to refresh logical system details.
 Check if ISU site is assigned to following subscriptions.
 All Business Agreements (MESG)
 All Business Partner Relationship (MESG)
 All Business Partners (MESG)
 All Business Transactions
 IS-U Connection Objects (MESG)
 IS-U Contracts (MESG)
 IS-U Points of Delivery (MESG)
 Product Materials (MESG)
6. CRM Middleware Queues
 Inbound Queues:
I. Execute transaction SMQR.
II. Change AS group from DEFAULT to parallel generators. Path: Edit -> Change AS Group
III. Register following queues:
 CRM
o CSA*
o R3A*
 ISU
o R3A*
Outbound Queues:
I. Execute transaction SMQS.
II. Change AS group from DEFAULT to parallel generators. Path: Edit -> Change AS Group
III. Register following queues:
 CRM
o CSA*
o R3A*
 ISU
o R3A*
R&R Queues:
I. Execute transaction SMOHQUEUE in CRM.
II. Check if all queues have status Released.
III. Start Queue Demon by clicking on Start Queue Demon.
Please reward points if it helps.
Regards,
Amit Mishra

Product problem in CRM after system copy

Hi,
W made CRM system copy - created test system from production system.
after this we have problems with replication of sales orders from test R/3 to test CRM.
Product IDs were not replicated, but the rest of order yes.
I think this is problem with logical systems on products due to system copy.
What should I do to correct it?
run BDLS for all product tables , to change logical system production R/3 to test R/3 ?
Regards
Radek

Hi Radek,
Check the values for Logical System in COMM_PRODUCT CRM table. If its still pointing to your production system, just run the BDLS again. You need to run BDLS for two times. First one to change CRM Old Logical System to CRM New logical system and second one for ECC Old Logical System to ECC new logical system.
You need to run two times, because for some products ECC is the source system and for some CRM is source system.
//Bhanu

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

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.

Problem in communication b/w MB90 and spool request

Hi Experts,
I am trying to print the Goods Movements in MB90. I am choosing print preview and number copies more than 1, But when I went to SP02 and trying to look at the request it only displaying one copy of the request, Please guide me how to encounter this problem at the earliest...
Thanks and regards,
B.Homeswara Prasad.

Hi
I did the convert the source system in BDLS...but still the problem persists.
I posted this issue in SAP.
I got the following reply.
Check if table RSADMIN table has correct logical system in BW
If incorrect
Run program SAP_RSADMIN_MAINTAIN and correct it.
In RSADMIN table i couldnt locate which field and in program SAP_RSADMIN_MAINTAIN i didnt understood what is value and object.
Did anyone come across this situation.
Regards
Rak

/BDL/TASK_PROCESSOR not getting triggered in satellite system from Solman

Hi,
We have scheduled EWA report in Solution Manager for one of the satellite system.
Solution Manager has sudddenly stopped creating of job /BDL/TASK_PROCESSOR0000002218 (ie job which is created immediately as EWA is scheduled in Solution Manager)
/BDL/TASK_PROCESSOR is running correctly and on hourly basis in satellite.
The EWA report is getting generated in Solution Manager after long time and without job /BDL/TASK_PROCESSOR0000002218 (is sessin specific job) being triggered.
Kindly help.
Regards,
Trupti M

Hi Paul,
My problem is solved.
Actually the Task: EarlyWatch Alert for Solution Manager under 'To Do' view of sdccn of satellite system was somehow getting scheduled as Back dated(ie instead of 30.04.2020 it was getting scheduled at 28.04.2010)
Due to this when we would do 'Start now' for the Task 'EarlyWatch Alert for Solution Manage' it was not getting triggered.
So I manually did refresh session which was mentioned under steps for manully sending data to SolMan under solution_mamanger tcode.
Due to this job BDL/TASK_PROCESSOR0000002237 got created.After this job got completed Task ''EarlyWatch Alert for Solution Manager ' got automatically generated.
I back dated the date for Task ''EarlyWatch Alert for Solution Manager" and started it.
Due to this the job /BDL/TASK_PROCESSOR0000002238 got created in satellite system for sending data to SolMan (This was not happening earlier.)
Extract from Solution_Manager tcode when scheduling:
When the Session Refresh task has been processed, a new task with the appropriate session type and session number appears in the To do view. This task collects and sends the data for your session. If a new task does not appear, search in the task-specific log for errors that ocurred during the Session Refresh task and make any necessary corrections.
To start the task immediately, select it and right-click to call up the context menu.
Choose Start Now. When the task has been processed successfully, it appears in the Done view. The data has been sent to your SAP Solution Manager system. You can check this in the task-specific log.
Thanks for all your help. Hoping my post will also be helpful for others.
Regards,
Trupti M

Dump during BDLS (Refresh BW)

Hello,
We are currently working on a BW refresh and during the BDLS we get the following dump:
Category                       ABAP Programming Error
Runtime Errors              OBJECTS_OBJREF_NOT_ASSIGNED
ABAP Program              SAPLRSBK_AFTER_IMPORT
Application Component   BW-WHM-DST
Date and Time               10.04.2014 01:47:55
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRSBK_AFTER_IMPORT" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: " ").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED" " "
"SAPLRSBK_AFTER_IMPORT" or "LRSBK_AFTER_IMPORTF02"
"DTP_CONVERT_AFTER_LS_CHANGE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
    SAP Release..... 702
    SAP Basis Level. 0009
    Application server... " "
    Network address...... " "
    Operating system..... "Windows NT"
    Release.............. "6.1"
    Hardware type........ "2x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... " "
    Database type..... "MSSQL"
    Database name..... "WV1"
    Database user ID.. "wv1"
    Terminal.......... " "
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "May 7 2010 02:47:09"
    create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
    Database version. "SQL_Server_9.00 "
    Patch level. 46
    Patch text.. " "
    Database............. "MSSQL 9.00.2047 or higher"
    SAP database version. 720
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows NT 6.1"
    Memory consumption
    Roll.... 0
    EM...... 125693760
    Heap.... 0
    Page.... 204800
    MM Used. 21725312
    MM Free. 3409648
User and Transaction
    Client.............. 200
    User................
    Language key........ "E"
    Transaction......... "BDLS "
    Transaction ID...... "FFFABFE3FA43F128BEA5005056B349F8"
    EPP Whole Context ID.... "005056B349F81EE3AFFF1C89DB1E7EA5"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPLRSBK_AFTER_IMPORT"
    Screen.............. "SAPMSSY0 1000"
    Screen Line......... 6
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSBK_AFTER_IMPORT" - in
     "DTP_CONVERT_AFTER_LS_CHANGE".
    The main program was "RBDLSMAP ".
    In the source code you have the termination point in line 74
    of the (Include) program "LRSBK_AFTER_IMPORTF02".
We found some SAP Notes but they are specific for different SAP versions or SP level.
Any help will be really appreciated.

Kindly check notes
1887227 - P31:DTP:Dump in After Import:RS_DTPA_AFTER_IMPORT
1684050 - Converting the logical system name for DTPs - Changes1642327 - RSBKDTP_BDLS: dump with error OBJECTS_OBJREF_NOT_ASSIGNED
BR,
K.

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.

BDLS problem

Similar Messages

Maybe you are looking for