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

Similar Messages

  • ERROR DURING BDLS CONVERSION

    Hi Markus and Friends,
    We have done BDLS conversion on pre-production after system copy from the production, when we tried to BDLS conversion between the logical system say PRHCLNT200(which is Production ECC 5.0 System) to QRHCLNT200 (which is preprod ECC5.0 System) with Oracle 9.0.0.7 database and AIX 5.4.
    Some of the tables got error like :
    Table Name  Field Name       Number of Relevant Entries    Number of Converted Entries
    For the tables:
    TBD05,TBD06,TBD20,TBD30 ===>  Error in field  of table . Manual correction required.
    I checked those tables and related to distribution model settings (BD64)....
    Please let me know to solve the issue.
    Thanks in advance....
    Regards,
    SAM

    Hi Kenny,
    Thanks for your response..We ran it once again but the same issue , when i check the logs for the bdls it clearly shows that the above mentioed tables are with the icon of >>>> and it means we need to correct it manually.... but how to rectify it.
    Please let me know what changes i need to do.
    Cheers,
    SAN

  • BDLS Conversion error

    Hi All,
    BDLS conversion job completed successfully but spool shows below tables in red.
    Table Name                Field Name               Number of Relevant Entries        Number of Converted Entries
    TBD05                                  RCVSYSTEM                           1                              0 @03@
                                                SNDSYSTEM                           1                              _
    TBD06                                  RCVSYSTEM                           1                              0 @03@
                                                SNDSYSTEM                           0                              0
    TBD20                                  RCVPRN                                  0                              0
                                                SNDPRN                                  1                              0 @03@
    USZBVPROT                        SUBSYSTEM                           1                              0 @03@
    USZBVPROTC                      SUBSYSTEM                           1                              0 @03@
    USZBVSYS                          SUBSYSTEM                           1                              0 @03@
    @03@ Error in field of table . Manual correction required.
    for relevant entries number of converted entries is _, is something wrong? job took almost 25 hrs to complete. should I rerun BDLS? Please advice.
    Environment: ECC6, Oracle 10g
    Regards
    KVR

    I had the same problem and I avoided even correcting it as it did not impact anything in my system.It change the logical name completely and was sufficient for me.
    Hope this help.
    Amit

  • BDLS conversion require manual corrections

    Hi, I am currently running BDLS in a system that is copied from BI Quality system. After the copy, I have run BDLS conversion for few source system connections. For the source system conversion from URD030 -> DV2CLNT030, I found that few tables require manual correction and ran BDLS on these tables as below, but still requires manual correction.
    =======================================================================================
    Log for conversion: URD030 -> DV2CLNT030 in system CND900 (initiator CND 900)
    05/23/2008 16:05:32
    < Table T000 was not relevant for conversion
    Table Name Field Name Number of Relevant Entries Number of Converted Entries
    /BIC/SYPRODHIER* LOGSYS 1 0 <<<<
    RSISOSMAP* LOGSYS 1 0 <<<<
    RSOSFIELDMAP* LOGSYS 1 0 <<<<
    Identifies Cross-Client Tables
    <<<< Error in field of table . Manual correction required.
    < SAPoffice No object reference exists -> No conversion
    < SAPoffice Object references that have been converted: 0
    Table buffer in server synchronized after conversion
    =======================================================================================
    SQL Level Updation gives the following errors.
    I tried to update the table manually from database level, but couldn't. Can you give some suggestions.
    =======================================================================================
    SQL> select count(*) from SAPBIW."/BIC/SYPRODHIER" where LOGSYS='URD030';
    COUNT(*)
    4047
    SQL> update SAPBIW."/BIC/SYPRODHIER" set LOGSYS='DV2CLNT030' where LOGSYS='URD030';
    update SAPBIW."/BIC/SYPRODHIER" set LOGSYS='DV2CLNT030' where LOGSYS='URD030'
    ERROR at line 1:
    ORA-00001: unique constraint (SAPBIW./BIC/SYPRODHIER~0) violated
    =======================================================================================
    Can somebody give me some suggestions on this?
    Regards,
    Giridhara Tadikonda

    I am getting a similar error.  Please assit.

  • BDLS Conversion after System Copy fails

    Hi All,
    We are doing a Homogeneous System Copy on a AIX 5.3/Oracle 10.2.0.4/ SAP ERP 6.0 environment.
    After the system copy we had to run BDLS to convert logical system names in tables. Except for 3 tables namely EDPP1, TBD05 and TBD06 the BDLS run was successful.
    We tried to convert the logical system names in these tables by running BDLS for these tables individually however they failed again.
    The error was - "Error in field of table. Manual correction required"
    I checked SAP Note 121163 and it is mentioned in this note -
    "If the new logical system name already exists in the system, it can cause errors for tables in which the logical system is key field or
    unique index (for example, COFIO1). In this case the number of converted entries is smaller than the number of selected entries."
    And in this case a manual post-processing is required. How do I go about doing this manual post-processing?
    1. Should I maintain these directly at the table level - which is cumbersome as there are a lot of entries?
    2. Or using a small ABAP program?
    Please let me know if any other information is required frommy side.
    Thanks, Dibya

    Hi,
    Yes ofcourse, you need to check all settinfs, once you copy teh system you are going loose all RFC's and Source and Destinations ectc, so adject all that settings.
    See the following  SAP Notes:
    SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
    SAP Note 325470 - Activities after client copy in BW source systems
    SAP Note 325525 - Copying and renaming systems in a BW environment
    SAP Note 1333302 - Special procedure for BW system copy
    SAP Note 996238 - Dump 'RFC connection error' after BW system copy
    Search for PDF in SDN
    How Tou2026System Copy in SAP Business Intelligence System Landscapes
    Thanks
    Reddy

  • 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.

  • Distubution of BDLS  run  between work process

    Hi all,
    We have the R/3  4.6c with 4.2 TB and BW  7.0 with 7.4 TB , during the refresh from   prod to quality  the BDLS steps takes  nealry 24 to 40 hrs . We have break down the tables  and kicking off mutliple BDLS jobs  like Z * tables  in BDLS run and  other set of tables in another run  so that these jobs will run parallel . During this BDLS conversion  only one  background process
    is running  for one BDLS run  is there any way to make the load distubution among available background process to so that the conversion will complete sooner.
      For example : In  R/3 i have trigger one BDLS run for CATSDB  table  in background  this will  occupy only one background process, how can we make to use of available all background process to run  for CATSDB so that conversion will be completed soon .
    Please suggest..
    Thanks,
    Subhash.G

    There is nothing wrong is running BDLS jobs in parallel. We were facing a similar situation in a project a few years back and then I had devised a solution after taking inputs from various sources and usage of parallel processing was one of steps of achieving BDLS faster. Parallel processing is not an issue at all. However parallel processing needs to be done smartly. Bigger tables ought to be excluded and for them dedicated processes can be used. For the rest you can tables for bracket them like A* to D* ,E* to F* and so on  making sure you are exclusing the larger tables. However usage of temporary indexes for big tables where not all the fields need to be filled in can be helpful. The index needs to include the field for logical system .No point in creating temporary indexes for tables where the logical system field is always full since anyways a complete table scan would be performed. Create indexes for 6-7 largest tablest of this kind. Of course increase thnumber of background processes as well temporarily.
    Regards.
    Ruchit.

  • WE20, WE21 settings after SAP BW system copy

    Hi!
    I copied SAP BW system and have executed the following post installation settings:
    - BDLS (conversion of logical system names)
    - Program RS_BW_POST_MIGRATION
    When I go to tcode RSA1 on my new copied SAP BW system and try to reach source system I get the following error:
    BI unknown in source system
    BI IDoc type ZSBA004 is not the same as source system IDoc type
    The following errors occurred in the source system
    EDI: Partner profile not available
    +Entry in inbound table not found     +
    Entry in outbound table not found
    Question:
    Should I create new entries in tcode WE20, WE21?
    If yes, how (copy of existing one from SAP source BW system)
    Thank you!

    Hi!
    I face currently with the problem on my new SAP BW within RSA1 --> Source system --> Check:
    BI unknown in source system
    BI IDoc type ZSBA004 is not the same as source system IDoc type
    How can I solve this problem?
    The partner definition t-RFC as well are created...
    Thank you!

  • Cannot see entries in RSA1 sources system list

    Hi
    As part of the post processing of the system copy from PXX to Xxx I scheduled a test run for the BDLS conversion PxxCLNT100 to XxxCLNT100.But as this was running too long I aborted this by doing "Stop transaction".
    Then I started the actual BDLS run (PxxCLNT100 to XxxCLNT100), during which I got the error "The datasource ZBI_MT_xxx_xxxxx" (XxxCLNT100) does not exist in object version A.
    As per the threads on SDN I ran the RSA1 tCode. Getting an error immediately "Logical System has been changed for this system".
    Checked and changed WE20 partner profiles for XxxCLNT100 from I to A.
    Then deleted PxxCLNT100 entry from RSBASIDOC.
    Now in RSA1 I do not get the error but now the entire list of source system is no longer seen.   
    Regards,
    Rohan

    Hi,
    Thanks for your help .
    @Ashutosh :: RSBASIDOC table has list of all source systems from Pxx system and one entry of XxxCLNT100.
    @Arjun :: EDPP1 has list of all source system from Pxx system except PxxCLNT100 and one other system (I had deleted manually).
    Also EDPP1 has list of all source systems for Xxx system.
    Currently there is BDLS running in the system Xxx for other source system. So will check and update once the BDLS completes.
    As i have one more system Ixx in line for which i need to carry out the system copy. Would not prefer to land in the same situation of not finding source systems in RSA1.
    Was thinking if I am missing any table in the export step before system copy, which might have caused this mess.
    select * from rfcattrib
    select * from rfcdes
    select * from edpp1
    select * from edp13
    select * from edp21
    select * from rfccmc
    select * from rfcdessecu
    select * from rfctrust
    select * from rfcgo
    select * from rzllitab
    select * from tpfid
    select * from e070l
    select * from btcomset
    select * from tvarv
    select * from rfcdoc
    select * from rfcsysacl
    select * from rzllitab
    select * from rzlliclass
    select * from sxroute
    select * from rfccheck
    select * from tbd51
    select * from tbd52
    select * from tbd53
    select * from tbd54
    select * from tbd55
    select * from tbd56
    select * from bdrgin
    select * from bdrgout
    select * from tojtb
    select * from saplikey
    Thank you all,
    Rohan

  • We would like to test old deltas from the source system( copied to new)

    Hi Gurus,
    The scenario is
    They will make a DB copy of the Prod system onto a QA system, the Copied system will have
    its system ID changed(SID) to a new one.
    There will be deltas available in the RSA7, as this is a copy of the  3 weeks old prod
    system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
    We would like to test these delta's to BW Dev. why we would like to do the delta's to the
    BW dev system is to check whether we can do system copies without clearing the delta's on
    the source system.
    After the system copy we will do all the activities necessary to reflect the system changes
    a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
    reflect the changes of the BW Prod system to BW Dev system.
    b. Likewise, we will perform all the above activities on the BW dev system by changing the
    existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
    the new Source system with the new (SID).
    c. We will check the source system connection
    d. Replicate the datasources on the new source system
    e. Activate the Transfer rules for the new source system.
    Now for us to do delta's from the new source system to the Bw dev system we need to change
    underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
    We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
    destination to the BW dev system.
    What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
    and also  the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
    like to know if this is the case .
    Lastly, appreciate if anyone can say if this is possible to do without having to clear the
    BW delta queue on the source system.

    Hi Ramesh,
    Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source)  in the BW system on the copied source system
    tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
    After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
    response much appreciated.
    Kalyan

  • Changing current production SID to new SID.

    Hello there,
    I have a question on changing current SID name to new SID name. We are planning on moving our current production hardware to new better hardware and change the PRD(old) to PRD(new). Is anyone out there (customers) who had done this before, and what would be the ramifications? I  know we have to run BDLS in order to change current logical systems to new logical systems. Are there any issues in doing so in Production system? Any input is appreciated.
    Thanks,
    Santosh

    Santosh
    you can do that easily just by installing SAP system on new hardware and then restoring this backup to new system,that should not be an issue,it is just like doing system copy
    but
    SAP has strongly recommended not to run BDLS conversions on Production systems database,so I would suggest you to first approach SAP,raise a message with them and ask their recommendations
    Let me know of any questions
    Rohit

  • BDLS for conversion of logical source system name

    Hello All,
    I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
    But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
    How do I make sure that the reassignment happens correctly?
    And what precautions should be taken to avoid further consequences?
    Regards,
    NIKEKAB

    BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
    Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
    You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
    Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
    Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
    Good luck...

  • Help for Job BDLS - Logical System Conversion aftrer System Refresh

    hi SAP Basis Gurus,
    We have restored production data to test system. After that we are doing Logical System conversion - Renaming of Logical System Names. For that we are running BDLS job. The program used is IBDLS2LS.
    Now one job is running for more than 200000 seconds.  Job is doing "Sequential Read" on table ZARIXCO40.  The following has been updated in the jobs log:
    01.02.2008 10:20:06 Processing table ZARIXCO40
    02.02.2008 01:59:56 Processing table ZARIXCO40
    02.02.2008 22:26:44 Processing table ZARIXCO40
    02.02.2008 23:04:05 Processing table ZARIXCO40
    So as per above log, it looks like job got stuck in loop for table 01.02.2008 10:20:06 Processing table ZARIXCO40.
    The oracle Session is showing following SQL Statement:
    SELECT
    /*+
      FIRST_ROWS
    FROM
      "ZARIXCO40"
    WHERE
      "MANDT" = :A0 AND "LOGSYSTEM" = :A1 AND ROWNUM <= :A2#
    ~
    Execution Plan is :
    ~
    Execution Plan
    Explain from v$sql_plan: Address: 00000003A2FD5728 Hash_value:  2772869435 Child_number:  0
    SELECT STATEMENT ( Estimated Costs = 4.094.270 , Estimated #Rows = 0 )
            3 COUNT STOPKEY
                2 TABLE ACCESS BY INDEX ROWID ZARIXCO40
                  ( Estim. Costs = 4.094.270 , Estim. #Rows = 32.799.695 )
                    1 INDEX RANGE SCAN ZARIXCO40~0
                      ( Estim. Costs = 418.502 , Estim. #Rows = 65.599.390 )
                      Search Columns: 1
    ~
    Table has been analyzed today. See the details below:
    ~
    Table   ZARIXCO40
    Last statistics date                  02.02.2008
    Analyze Method              mple 16.623.719 Rows
    Number of rows                        65.599.390
    Number of blocks allocated             2.875.670
    Number of empty blocks                     7.912
    Average space                                934
    Chain count                                    0
    Average row length                           313
    Partitioned                                   NO
    UNIQUE     Index   ZARIXCO40~0
    Column Name                     #Distinct
    MANDT                                          1
    KOKRS                                         14
    BELNR                                  2.375.251
    BUZEI                                      1.000
    ~
    Index used for this table is also analyzed today:
    ~
    UNIQUE     Index   ZARIXCO40~0
    Column Name                     #Distinct
    MANDT                                          1
    KOKRS                                         14
    BELNR                                  2.375.251
    BUZEI                                      1.000
    Last statistics date                  02.02.2008
    Analyze Method              mple 24.510.815 Rows
    Levels of B-Tree                               3
    Number of leaf blocks                    418.499
    Number of distinct keys               65.480.722
    Average leaf blocks per key                    1
    Average data blocks per key                    1
    Clustering factor                     40.524.190
    ~
    Can you please let me know what could be the issue and how to resolve this issue so that job gets completed. Normally this job runs for 1,00,000 seconds. I can not afford to cancel this job and run again.
    Any help is Highly appreciated,
    Thanks
    Best Regards,
    Basis CK

    Hi Markus,
    The stastics of the table is already updated today. After that also it is not going faster. It is doing "Sequential Read" for more than 5 hours and then one update is issued. And in the job log, all other tables are preocess only once, only this table is selected to processed 4 times which is very abnormal.
    01.02.2008 07:43:59 Processing table ZARIXCO11
    01.02.2008 07:45:36 Processing table ZARIXCO16
    01.02.2008 10:17:20 Processing table ZARIXCO21
    01.02.2008 10:20:06 Processing table ZARIXCO26
    01.02.2008 10:20:06 Processing table ZARIXCO29
    01.02.2008 10:20:06 Processing table ZARIXCO33
    01.02.2008 10:20:06 Processing table ZARIXCO37
    01.02.2008 10:20:06 Processing table ZARIXCO40
    02.02.2008 01:59:56 Processing table ZARIXCO40
    02.02.2008 22:26:44 Processing table ZARIXCO40
    02.02.2008 23:04:05 Processing table ZARIXCO40
    ~
    I guess this will keep on going like this and not sure when it gets complete. Any other thing you can suggest which help to resolve the issue.
    Thanks
    Best Regards,
    Basis CK

  • Table T000 was not relevant for conversion in BDLS log

    Hi All,
    I am getting the below message in BDLS log  while doing logical system system conversion with BDLS.
    "Table T000 was not relevant for conversion"
    Due to this I could see old logical system entry in SCC4 instead of New converted logical entry.
    (I've gone through the forums ,but didn't find solution)
    Any Idea why I am getting this message and I triggered BDLS from client 000.
    Regards,
    Srinivas Chapa.

    Already SCC4  entry for the client has old Logical system name.
    Ex:
    Client 500
    Logical System : <PRD>CLNT500
    I need this to be change to <QAS>CLNT500 after BDLS,but it is not happening after BDLs.
    Regards,
    Srinivas Chapa.

  • BDLS : Table T000 was not relevant for conversion

    Hello,
    After a system refresh ( homogeneous system copy in ECC6), we performed the post copy procedure.
    I ran the BDLS transaction, all the tables were converted fine, exept the table 000.
    I still have in transaction SCC4 the former logical systeank you in dam defined.
    I checked the BDLS job log and found the message :
    "Table T000 was not relevant for conversion"
    I don't underdtand why ? Is it the normal behaviour ?
    Table T000 is not excluded in BDLSC ...
    Thank you in advance for your help.
    Best Regards.

    I just found out that I launched the BDLS from the client 000.

Maybe you are looking for

  • How to disable an iMessage phone number on selective devices?

    I am using an iPhone 5S along with family sharing and my other family members(with their multiple other Apple devices including iPhone 5c, iPad Air, and iPhone 6) have the option to receive and send messages using my phone number. So, I was wondering

  • HP officejet 6500 E709n problem with scanner

    Hi I buy HP officejet 6500 E709n i have problem with scanner when printer work wireless  (when work USB or cable RJ45 it's ok). When I try scanning windows give me problem "4,[2,7,80040007),(3,7,0)]", I change drivers and still not working. I have Vi

  • Integration Engine does not connect with SLD

    Hi all, We have an XI 3.0 system that acts as QUA system in our track. This XI 3.0 system is connected to a central SLD installed on a PI 7.1 system that acts as our DEV system. Everything seems to be OK in the Java part. We refresh the caches succes

  • RDF Report Output Got Displayed in Special Chars

    Team, RDF report output is getting displayed in special chars. when i query the data from SQL Developer, the data is displayed fine. But when the data is displayed in the report the characters(single quotes, double quotes) are not displayed properly,

  • How to export "Managed by" field of Distribution and Security groups and import with new values?

    My Active Directory environment is 2003 functional level and we have Exchange 2010. I am trying to find out the best way to do a mass edit for the "Managed by" values of our security and distribution groups. I know we can export the "managed by" fiel