Problem while filling the Setup Table for the DS 2LIS_02_SCL.

Hi All,
When I am trying to fill the Setup table for the DataSource 2LIS_02_SCL and only for one specific Purchase Order, it is showing me a message like
u201CDataSource 2LIS_02_ITM contains data still to be transferredu201D
I have deleted the Setup Table and I want to delete the entries from SM13, but I do not have Authorization.
Also, here I am trying to fill the Setup Table for 2LIS_02_SCL and not for 2LIS_02_ITM, but the message displayed above is showing as 2LIS_02_ITM DataSource. I think the Setup Table will be same for both the DataSources.
Waiting for your valuable inputs.
Thanks in Advance.

Hi,
When you want to fill the setup tables first you need to delete setup tables to avoid the duplicate entires in setup tables ( you can delete the setup tables by using t.code LBWG with application no is 02)
In your case, the data souce is 2LIS_02_SCL for purchasing.
when you want to delete the setup tables by using t.code LBWG with 02 application no it will delete all the purchasing related data from all the data sources like
2LIS_02_SCL
2LIS_02_ITM
Before the deletion of setup tables you need to clear the delta Queues and stop the V3 jobs, which loads the data to Delta Queues (RSA7) and Update tables(LBWQ).
you need to run the V3  jobs manually by using LBWE > Job control > and schedule the jobs until the delta queues will get 0 records. that means no data will be available in RSA7 and LBWQ
go to SM37 to see the jobs LIS-BW-VB_APPLICATION_02,
once the delta queues gets 0 records by running V3 Jobs manullay.
Then remove the released state jobs > remove from schedule means delete the jobs in LBWE > Go to job control > you can delete the released jobs.
Becuase No postings to be done in application tables, while running setuptable filling you should take some down time to fill the setup tables.( OLI*BW)  *=Application number.
Once you clear the Queues and delete the v3 jobs, then you need to fill the setup tables after deletion of setup tables.
once you fill the setup tables , by running intialization to BW side the delta Queue is formed for the data source in R3 side
Now the postings can be done in R3 side, so you need schedule back the V3 jobs, which you already delted from LBWE to load the data from application tables to RSA7 or LBWQ.
I hope this may help yoou.
Regards.
Rambabu
Edited by: Rambabu velanati on Jun 9, 2010 4:41 PM
Edited by: Rambabu velanati on Jun 9, 2010 4:52 PM

Similar Messages

  • Problems with filling of Setup table for 2LIS_03_UM

    I am not able to fill up this table. I mean its not getting filled thorugh TCode OLIZBW.
    Setup table for 2LIS_03_BF is getting filled up though.
    Can anyone foresee what can be the reason.
    Thanks PB

    Nope I am not. But the problem I have posted in my last note that i was getting -ve stock values which was resolved when i loaded the data with infosource 2LIS_03_UM in development. when I am testing it in QA I am not getting dat in this extractor.
    I had a chat with MM Functional Consultant , he said I probably wont get this data.
    Now I am not sure how will I be able to resolve the problem.
    Regards
    PB

  • Error while filling set up table for Inventory

    Hi,
       While filling up setup table for Inventory, 2lis_03_bf, i get an error, Plant F041 doesnot exist. I am trying to fillup the table without any selections. Can anyone please suggest me a solution.
    Thanks,
    Praveen

    Please check the following link:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Hope it helps you.

  • Problem in filling up the setup tables for 2LIS_11_VAHDR (All SD Data sources)

    Hello All,
    I have been  trying to fillup the setup tables for SD datasources( Application-11 Ex:2LIS_11_VAHDR), but it was not allowing me to do that.
    Below are the steps i have followed,
    1.Deleted the setup tables using tcode-LBWG- Application-11
    2.Cleared the queues in RSA7 and found 0 queues for 2LIS_11_VAHDR D.S by triggereing the I.P till it get zeroes.
    3.Checked the data in RSA3-No data found.
    4.Filling the setup tables using OLI7BW t-code, got a popu(Data for 2LIS_11_VAHDR has to still transfered)
    Do i need clear all the queues for SD-Billings,Orders e.t.c  since i have 8 data sources to be cleared apart from 2LIS_11_VAHDR .
    Could you please suggest any other option to fillup the setup tables.
    Regards,
    Siva

    Did you run the infopackage twice pertaining to 2lis_11_vahdr.One for delta and another time for repeat delta.As delta queue will hold the records in repeat delta mode as well.
    Also in case of Direct Delta --Data is transferred to Base tables and delta queue (RSA7) at the same time.So extraction queue (LBWG )and update tables(SM13) does not come into the picture.
    Regards,
    AL

  • Taking long time filling the setup tables for sales and shipment

    Hi ,
    I am trying to fill the setup tables for sales and shipment and it is taking lot of time .
    It took 16 hours just to bring 6 months of  sales history  data in the test environment .
    Cn anybody help on this issue why it is taking that much of time ...
    I am trying to  load the sales data from R/3 into APO-BW from 2005 to 2007 .......
    It is taking 16 hours to fill the data for only 6 months .

    Hi,
    1. delete data and refill the setuptables again by spliting to several small pieces.
    2. compare the data. wht is the last Document numner in RSA3(Maximum one). Start from Maximum one. may be bit complex approch.
    you need to check with PSA and base tables.
    keep one thing in your mind you need to check againest MSEG and BSEG only. noy BKPF and MKPF.
    correct if i'm wrong.
    either refill or create a user exit to avoid duplicae records(you should have very good understanding of data, it will lead to inconsitent data for delta records).
    User exit not a good solution. it's one possibility.
    ****Assign Points If Helpful****
    Regards,
    Ravikanth

  • How to initialize the setup table for GTMuFF08Global Trade ManagementuFF09?

    hi experts,
    I can find the datasource of GTM like 2LIS_46_SCL, 2LIS_46_ITM with rsa6.
    But when I use rsa3 to do test it, nothing found. I try to initialize the setup table, but I can not find it under SBIW.
    Please help me, many thanks. 
    Brgds/steve

    Hi
    These Data Sources are from LOGISTICS Try at Tcode.LBWE --Logistics **** Pit.
    Here is LO Cockpit Step By Step
    LO EXTRACTION
    - Go to Transaction LBWE (LO Customizing Cockpit)
    1). Select Logistics Application
           SD Sales BW
                Extract Structures
    2). Select the desired Extract Structure and deactivate it first.
    3). Give the Transport Request number and continue
    4). Click on `Maintenance' to maintain such Extract Structure
           Select the fields of your choice and continue
                 Maintain DataSource if needed
    5). Activate the extract structure
    6). Give the Transport Request number and continue
    - Next step is to Delete the setup tables
    7). Go to T-Code SBIW
    8). Select Business Information Warehouse
    i. Setting for Application-Specific Datasources
    ii. Logistics
    iii. Managing Extract Structures
    iv. Initialization
    v. Delete the content of Setup tables (T-Code LBWG)
    vi. Select the application (01 u2013 Sales & Distribution) and Execute
    - Now, Fill the Setup tables
    9). Select Business Information Warehouse
    i. Setting for Application-Specific Datasources
    ii. Logistics
    iii. Managing Extract Structures
    iv. Initialization
    v. Filling the Setup tables
    vi. Application-Specific Setup of statistical data
    vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
            Specify a Run Name and time and Date (put future date)
                 Execute
    - Check the data in Setup tables at RSA3
    - Replicate the DataSource
    Use of setup tables:
    You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
    Full loads are always taken from the setup tables
    Hope it helps

  • Error while filling PM setup tables

    Hi All, I activated the PM datasource(2LIS_17_I3HDR) in LBWE and then deleted the setup tables for PM in LBWG and then replicated the datasources in BW. When I try to fill setup tables for PM(OLIIBW) then I get error:
    No extract structure for event I0: Messages active
    Message no. MCEX 106
    Diagnosis :You called the setup for the extractor structures of application '17' (Plant Maintenance). However no extractor structure is active for event I0 (messgaes).
    I checked LBWE and the datasource (2LIS_17_I3HDR) is active. I check the OSS note 914268, I am hesistant to apply this note as due to heavy customizations at my company there has been issue while applying support packs, is there a work around? Kindly advice.
    **we are on PI is 2004_1_46C and the support package is 5.

    Hi,
    Had the same problem, make sure that your R3 env. that your are working at, is defined as source system at the BW client
    Shai

  • Issue while filling Inventory setup tables.

    Hi,
    Here we are facing a critical issue, while filling Inventory setup tables, we have done BX setup successfully. Not able complete BF and UM because of performance issues.
    We filled 40% of BF and UM, since we dont have system downtime and stoped the setup at that movement. Shall we do BF & UM setup without R/3 system downtime. Is there any other way we can fill the BF, UM setup tables.
    Your help is really appreaciated.
    Thanks
    BK

    Hi BK,
    Ideally you need the downtime when doing the setup for current and previous period as these are the only open ones where you can expect changes to happen due to user postings. What selection did you give when doing the set up? One idea is to break up the set up job so that each job loads for a week and then run the jobs in parallel. This would work for BF and then for UM of course you need to run it per company code. Are you using on ODS in your data model?

  • Error while filling set up tables for 2LIS_11  data sources

    hello All ,
    I tried to fill setup tables for 2LIS_11 data sources in OLI7BW , but the job RMCVENUA is getting cancelled. below is the Job Log ,
    Job started
    Step 001 started (program RMCVNEUA, variant &0000000000005, )
    Start of order processing
    Error determining rate: foreign curr. local curr. INR date 10.09.2008 (doc. 1)
    Job cancelled
    Is there any setting required in R3 side before filling setup tables of SD ?
    I am able to fill the setup tables for 2LIS_05 ( Notifications) successfully.
    Regards ,
    Amol Kulkarni
    Edited by: Amol Kulkarni on Dec 4, 2008 3:59 AM
    Edited by: Amol Kulkarni on Dec 4, 2008 4:00 AM

    Hi,
    one of the sales document currencies is not maintained properly in the system and therefore its failing.
    you need to correct those documents before filling the set up tables.
    Either you can chose the option fault document toleration limit to 1000...so that 1000 records wrong records can be tolerated or you have to crrect it first before filling up the set up tables.
    This will generally happen in test systems.... but very rare in production...so try to maintain currrency again in the system.
    generally you will see the sales doc number in the error for which its failing.
    May be at the time of filling some óne was working on some sales document and tried it save it.
    correct that doc and fill the set up tables again.
    Thanks
    Ajeet

  • " No entry in the conversion table for the syntax group" error

    Hi,
    Iu2019m getting an error in the port setup when I try to run an Access Test on the logical directory.
    Definition of path
    TFTS02\INTF\RD1\OUTB\MM\RFC WINDOWS NT missing
    Message no. SG024
    Diagnosis
    There is no entry in the conversion table for the syntax group WINDOWS NT and the logical path
    TFTS02\INTF\RD1\OUTB\MM\RFC.
    System Response
    The system cannot generate a platform-specific path.
    Procedure
    Make an entry for the syntax group WINDOWS NT and the logical Pfad
    TFTS02\INTF\RD1\OUTB\MM\RFC in the conversion table using the FILE transaction.
    Regards,
    Rajiv

    Hi
    the error is simple. The path
    TFTS02\INTF\RD1\OUTB\MM\RFC you are trying to access is not there so create the path in the FILE transaction.
    In file tcode goto NEW ENTRIES and give the path and also make sure that in AL11 the path and the filename you are trying to open exists.
    Thanks & Regards
    Jyo

  • SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

    I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
    On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In  Installation Progress after some progress installation fails.
    Windows show the following components couldn't installed:
    Managment Tools Complete  Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
    Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
    In detail for failure of every component it provide these details:
    Action required:
    Use the following information to resolve the error, and then try the setup process again.
    Feature failure reason:
    An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    In summary log file it provide the following details:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068643839
      Start time:                    2012-07-31 16:23:37
      End time:                      2012-07-31 16:33:32
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
      Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
      Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
      Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
      Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
      Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
      Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
      Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
      Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  Haansi-PC
      Machine processor count:       4
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    Database Engine Services                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SQL Server Replication                   1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2005      SQLEXPRESS           MSSQL.1                       
    SharedTools                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.4.5000        No        
      SQL Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.4.5000        No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033                
    Express Edition      10.50.1617.0    No        
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Express Edition     
    10.50.1617.0    No        
      SQL Server 2012                                                         
    LocalDB                                  1033                
    Express Edition      11.0.2318.0     No        
      SQL Server 2012                                                         
    Reporting Services - SharePoint                                                   
    11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Developer
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  TABULAR
      ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Manual
      ASSYSADMINACCOUNTS:            PC\Haansi
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SS2012
      INSTANCENAME:                  SS2012
      ISSVCACCOUNT:                  NT Service\MsDtsServer110
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Manual
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Data Tools
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Feature:                       SQL Client Connectivity SDK
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

    Please help. 
    I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068037632
      Start time:                    2014-09-29 15:05:38
      End time:                      2014-09-29 15:15:55
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for SSDTBI_VS2012:   Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
      Machine name:                  MSBI
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2008                                                          Management Tools - Basic  
                  1033                 Express Edition      10.0.1600.22    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          SQL Server Data Tools    
                   1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Evaluation Edition 11.0.2100.60    No         Yes       
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:         C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
      Installation edition:          Express
      Slipstream:                    True
      SP Level                       1
      Patch Level:                   11.1.3128.0
    Product Update Status:
      Success: KB 2674319, KB 2793634
    Product Updates Selected for Installation:
      Title:                         Service Pack 1
      Knowledge Based Article:       KB 2674319
      Version:                       11.1.3000.0
      Architecture:                  x86
      Language:                      1033
      Title:                         SQL Server 2012 SP1 GDR Product Update
      Knowledge Based Article:       KB 2793634
      Version:                       11.1.3128.0
      Architecture:                  x86
      Language:                      All
      Update Source:                 MU
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SSDTBI_VS2012, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files (x86)\Microsoft SQL Server\
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  true
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
    Detailed results:
      Feature:                       SQL Server Data Tools - Business Intelligence for Visual Studio 2012
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio Tools for Applications 2012
      Component error code:          0x80044000
      Component log file:            C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
      Error description:             VS Shell 2012 installation has failed with exit code -2147205120.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
      Feature:                       SQL Client Connectivity
      Status:                        Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

  • HT2305 My iPod is not being read by iTunes. What do I do to be able to sync my iPod if iTunes is not starting the setup wizard for the iPod when it is connected to a Dell PC? I am new the iTunes and iPods.

    My iPod is not being read by iTunes. What do I do to be able to sync my iPod if iTunes is not starting the setup wizard for the iPod when it is connected to a Dell PC? I am new the iTunes and iPods.

    Hello, BAHannebaum.
    The article below should resolve any device not being recognized in iTunes issue that you are experiencing.  The most common issues are the Apple Mobile Device Support driver or iTunes is outdated.  Start with the first step and test the results after each step processed. 
    iOS: Device not recognized in iTunes for Windows
    http://support.apple.com/kb/TS1538
    Cheers,
    Jason H. 

  • What to know the master table for the following fields

    I want to know the master table for the following fields.
    Company code ( BUKRS )
    Chart of depreciation ( AFAPL)
    Main Asset Number  (ANLN1)
    Asset Sub Number ( ANLN2 )
    Asset Class ( ANLKL )

    hi,
    1) t001 (<b>for assets T093C</b>)
    2) t096
    3 and 4) anla
    5) anka
    rgds Andreas
    Message was edited by:
            Andreas Mann

  • How to Read the internal table for the data download from the spool

    HI all,
    I have one issue regarding the spool ,we are getting the correct output as per requirement of  user but when we send the same to the user in pdf format they did notget the same.
    they are telling that the due date is missing from the pdf.
    Please advice me how to track the internal  table for the spool data converted intopdf in a readable format.
    the FM used for the above task is : 
    call function 'CONVERT_OTFSPOOLJOB_2_PDF'
    Please reply if any one worked on the same.
    Thanks in advance.
    Gaurav,

    Hi Wang,
    Please let me know how you solved your question.
    Points will be rewarded.
    Thanks,
    Arun.

  • Need to know the base tables for the QM datasources

    Hello SAP Experts,
    I want to know the base tables for the below mentioned datasources which stores the transaction data.
    1. 2LIS_05_QE1:  Inspection Characterstics Results
    2. 2LIS_05_QE2: Inspection Characterstics Results (Quan)
    3. 2LIS_05_QVUDN: Usage decision for Inspection
    Need your inputs.
    Thanks,
    Lasya.
    Edited by: lasya john on Dec 10, 2008 8:28 PM

    Hi Lasya,
    You can use help.sap.com for this.
    If you do not find this data source there...then
    You can go to LBWE t-code in R/3 and then infront of the data source...you have maintenance option.
    Click on that ...and go inside it in the display mode.
    Here you can see a generic pool of fields on the left side which can be included in the data source........  field present in the data sources in the right side of the pool.
    For every field you have a tructure name infront of it like MCXXXX where XXXX is the table name.
    So the field is being from that particular table.
    Even I would the same thing to reply to your thread.
    You can follow the same procedure to find the table for any LO data source.
    This is accurate in 99% cases...only in very few cases like purchasing...we get one or two fields from different tables.
    Hope it helps.
    Thanks
    Ajeet

Maybe you are looking for

  • Questions RE: Using System Recovery Discs on HP G71-358NR (Options?)

    I bought my HP G71-358NR Notebook in Dec 2009. It has Windows 7 Home Premium x32/x64 ). I am on my second hard drive (had to replace in Feb 2012), and I do have the HP System Recovery DVDs (there are 2 of them), and the HP Driver Recovery CD (1 disc)

  • My Album Artwork doesn't display?

    I am not sure what's going on, but my iPod classic doesn't display album art any longer.  It always has in the past.  I am not sure how long it hasn't displayed.  I just noticed the issue.  Any ideas out there?

  • Nokia 6700 Memory Selection Problem

    Hi, Please help I am not able to find the option in Nokia 6700 how to select memory card for the messages memory also how I able to tranfer the old messages to Nokia 6700. From the pc suite software provided by nokia I already copoed oll my messages

  • Pinwheel Bug when trying to "Create"

    I've tested on two computers. An 08 Mac Pro and an early 08 MacBook Pro both running 10.6.4. I noticed that sometimes (not always) especially after using iPhoto, exiting, iPhoto does a DB upgrade, then relaunching iPhoto, that choosing Create | Book

  • Server Client comunication

    I have to send Document type attribute from server to client. I'm using code from sockets tutorial and it seems like they can only communicate with String type attributes. So the question is, how can I send Document type attribute (XML DOM) ?