The parallel process for mrp.

hi exports
we plan to do the scope of planning for the total planning as a background job.
while doing that system ask for the parallal processing for mrp
what is customize step and procedure to do the parallel process for mrp.

Dear Raj,
With the help of parallel processing procedures, you can significantly improve the runtime of the total planning run.
To process in parallel, you can either select various sessions on the application server or various servers.
Parallel processing runs according to packages using the low-level code logic:
The work package, with a fixed number of materials that are internally defined in the program, is distributed over the individual servers/sessions. Once a server/session has finished processing a package, it starts processing the next package.
If a low-level code is being planned, the servers/sessions that have finished must wait until the last server/session has finished its package to avoid inconsistencies. Then the next low-level code is processed per packages.
The parallel processing procedure is switched on in the initial screen of total planning.
Activities
Define the application server with the number of sessions that can be used:
If you want to define various servers for parallel processing, enter the server with the number of sessions.
If you only want to use one server, but several sessions, enter the application server and the appropriate number of sessions.
Further notes
Parallel processing shortens the time required for calculation, however, it cannot shorten the database time as the system still only operates using one database.
The Customizing Transaction is   OMIQ
Regards
PSV

Similar Messages

  • Parallel processing in MRP

    CAn anybody tell me  the use of parallel processing in MD01 screen...
    SAP help tells the following..
    But I cant understand that..
    PLease help me get a clarification.
    Karthick P

    Dear
    The parallel processing use in total planning run in MD01 or MD40 thats meas planning run for number of plant at atime. By using parallel processing procedures, you can significantly improve the total planning run. The parallel processing procedures can either run on several servers or in several sessions. So we define this setting in OMIQ.
    Scope of planning in OMIZ here we combine the number of plant/ MRP are for total palnning run which use in MD01 to run MRP for all plant at same time.
    So if you want to run the MRP for all palnt or MRP Area as total planning run then you need to define scope of planning and parallel processing to improve the system performance and if you don't define it then also you can excetue the MRP.
    Summery is :
    1) If you want to run MRP viw MD 01 online you require scope of planning.
    Reason:- With scope of planning only you can combine no of plant / MRP area.etc.,
    If you want to run MRP in back ground this is not required.
    2) Always parallel processing will improve the system speed by acessing data base layer with multiple application layer.
    setup : go to SPRO>material management>Consumption based planning-->Define parallel processing in MRP.
    Refer : the parallel process for mrp.
    Hope this will be useful
    Regards
    JH

  • Duplicate IR through parallel processing for automated ERS

    Hi,
    We got duplicate IR issue in production when running the parallel processing for automated ERS job. This issue is not happening in every time. Once in a while the issue happeing. That means the issue has happened in June month as twice. What could be the reasons to got this issue. On those days the job took more time comaredt o general. We are unable to replicate the same scenareo. When i am testing the job is creating IRs successfully. Provide me the reasons for this.

    Wow - long post to say "can I use hardware boxes as inserts?" and the answer is yes, and you have been able to for a long time.
    I don't know why you're doing some odd "duplicated track" thing... weird...
    So, for inserts of regular channels, just stick Logic's I/O plug on the channel. Tell it which audio output you want it to send to, and which audio input to receive from. Patch up the appropriate ins and outs on your interface to your hardware box/patchbay/mixer/whatever and bob's your uncle.
    You can also do this on aux channels, so if you want to send a bunch of tracks to a hardware reverb, you'd put the I/O plug on the aux channel you're using in the same way as described above. Now simply use the sends on each channel you want to send to that aux (and therefore hardware reverb).
    Note you'll need to have software monitoring turned on.
    Another way is to just set the output of a channel or aux to the extra audio outputs on your interface, and bring the outputs of your processing hardware back into spare inputs and feed them into the Logic mix using input objects.
    Lots of ways to do it in Logic.
    And no duplicate recordings needed...
    I still don't understand why the Apple-developers didn't think of including such a plug-in, because it could allow amazing routing possibilities, like in this case, you could send the audio track to the main output(1-2 or whatever) BUT also to alternate hardware outputs, so you can use a hardware reverb unit, + a hardware delay unit etc...to which the audio track is being sent , and then you could blend the results back in Logic more easily.
    You can just do this already with mixer routing alone, no plugins necessary.

  • Parallel processing for increaing the performance

    various ways of parallel processing in oracle especially using hints
    Please let me knw if there exists any online documentation in understanding the concept

    First of all: As a rule of thumb don't use hints. Hints make programs too unflexible. A hint may be good today, but might make things worse in future.
    There are lots of documents available concerning parallel processing:
    Just go to http://www.oracle.com/pls/db102/homepage?remark=tahiti and search for parallel (processing)
    Due to my experience in 10g, enabling parallel processing might slow down processing extremely for regular tables. The reason are lots of waits in the coordination of the parallel processes.
    If, however, you are using parallel processing for partitioned tables, parallel processing works excellent. In this case, take care to choose the partitioning criterion properly to be able to distribute processing.
    If, for example, your queries / DMLs work on data corresponding to a certain time range, don't use the date field as partitioning criterion, since in this case parallel processing might work on just a single partition. Which again would result in massive waits for process coordination.
    Choose another criterion to distribute the data to be accessed to at least <number of CPUs -1> partitions (one CPU is needed for the coordination process). Additionally consider to use parallel processing only in cases where large tables are involved. Compare this situation with writing a book: If you are planning to have some people writing a (technical) book consisting of just 10 pages, it wouldn't make any sense at all concerning time reduction. If, however, the book is planned to have 10 chapters, each chapter could be written by a different author. Reducing the resulting time to about 1/10 compared to a single author writing all chapters.
    To enable parallel processing for a table use the following statement:
    alter table <table name> parallel [<integer>];If you don't use the <integer> argument, the DB will choose the degree of parallelism, otherwise it is controlled by your <integer> value. Remember that you allways need a coordinator process, so don't choose integer to be larger than <number of CPUs minus 1>.
    You can check the degree of parallelism by the degree column of user_/all_/dba_tables.
    To do some timing tests, you also can force parallel dml/ddl/query for your current session.
    ALTER SESSION FORCE PARALLEL DML/DDL/QUERY [<PARALLEL DEGREE>];

  • Parallel processing for ABAP prorams in Process chain.

    Hi All,
    In one of the process chain, we have added the ABAP program. In Backend,the job is running as "BI_PROCESS_ABAP".
    I just want to know, same like DTP, can we keep parallel processing for the ABAP programs also. Please suggest.
    Thanks.

    Hello Jalina
    Also check with BASIS if the memory allocated to run this program has not overflowed and the selections you have in your ABAP program is in small chunks and use variants to run them in parallel OR series
    Thanks
    Abhishek Shanbhogue

  • Parallel processing for information broadcasting

    Hi SDN,
    How can we control parallel processing for information broadcasting in BI background management?
    Early answer is appreciated.
    Thanks in Advance.
    Namrata

    Hi,
    agree with the above postings
    you can find more details regarding this in below given link
    http://help.sap.com/saphelp_nw70/helpdata/en/ef/4c0b40c6c01961e10000000a155106/frameset.htm
    hope this helps
    Regards,
    rik

  • Job fail with Timeout for parallel process (for SID Gener.): 006000

    Hello all,
    Im getting below error and not able to find any issue with Basis side. Please anyone help on this!
    Job started
    Data package has already been activated successfully (will be skipped)
    Process started
    Process started
    Process started
    Process started
    Process started
    Import from cluster of the data package to be activated () failed
    Process 000001 returned with errors
    Process 000002 returned with errors
    Process 000003 returned with errors
    Process 000004 returned with errors
    Background process BCTL_4XU7J1JPLOHYI3Y5RYKD420UL terminated due to missing confirmation
    Process 000006 returned with errors
    Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
    Log for activation request ODSR_4XUG2LVXX3DH4L1WT3LUFN125 data package 000001...000001
    Errors occured when carrying out activation
    Analyze errors and activate again, if necessary
    Activation of M records from DataStore object CRACO20A terminated
    Activation is running: Data target CRACO20A, from 1,732,955 to 1,732,955
    Overlapping check with archived data areas for InfoProvider CRACO20A
    Data to be activated successfully checked against archiving objects
    Parallel processes (for Activation); 000005
    Timeout for parallel process (for Activation): 006000
    Package size (for Activation): 100000
    Task handling (for Activation): Backgr Process
    Server group (for Activation): No Server Group Configured
    Parallel processes (for SID Gener.); 000002
    Timeout for parallel process (for SID Gener.): 006000
    Package size (for SID Gener.): 100000
    Task handling (for SID Gener.): Backgr Process
    Server group (for SID Gener.): No Server Group Configured
    Activation started (process is running under user *****)
    Not all data fields were updated in mode "overwrite"
    Data package has already been activated successfully (will be skipped)
    Process started
    Process started
    Process started
    Process started
    Process started
    Import from cluster of the data package to be activated () failed
    Process 000001 returned with errors
    Process 000002 returned with errors
    Process 000003 returned with errors
    Process 000004 returned with errors
    Errors occured when carrying out activation
    Analyze errors and activate again, if necessary
    Activation of M records from DataStore object CRACO20A terminated
    Report RSODSACT1 ended with errors
    Job cancelled after system exception ERROR_MESSAGE

    Thanks for the link TSharma I will try that today.
    UPDATE:
    I ran a non-parallel Data Pump and just let it run overnight. This time it finished after 9 hours.  In this run I set the STATUS=300 parameter in the PARFILE which basically echos STATUS updates to standard out every 300 seconds (5 minutes).
    And as before after 2 hours it finished 99% of the export and just spit out WAITING status for the last 7 hours until it finished.  The remaining TABLES it exported (a few hundred) were all very small or ZERO rows.  There clearly is something going on that is not normal.  I've done this expdp before on clones of this database and it usually takes about 2-2.5 hours to finish.
    The database is about 415 Gigabytes in size.
    I will update what the TRACE finds and I'm also opening a case with MOS.

  • Parallel processing for one large message

    I have some troubles from messaging performance perspective.
    Sender:ABAP Proxy
    Receiver:File Adapter
    I'd like use parallel processing for one large message.
    And the file for receiver is needed to be one file.
    Could you let me know how to set them ?
    Best regards,
    Koji Nagai

    Hi
    Can you elaborate your requirement more?
    How are you trying to achieve parallel processing in XI.
    Since you mentioned that the source is Proxy, there should be some trigger mechanism say selection screen, you restrict the values here and use append strategy in File and can execute the same.
    REgards
    Krish

  • 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

  • I am trying to upgrade my macbook pro to os x mavericks, but it has been on the reboot process for more than 2 hours. There is only the apple logo with the spinning ball thing. What should I do?

    I am trying to upgrade my macbook pro to os x mavericks, but it has been on the reboot process for more than 2 hours. There is only the apple logo with the spinning ball thing. What should I do?

    Hi there Candyleehoiman,
    I would recommend taking a look at the troubleshooting steps found in the article below.
    Mac OS X: Gray screen appears during startup
    http://support.apple.com/kb/ts2570
    -Griff W.

  • Guidelines required to analyze the extraction process for 2LIS_02_SCL.

    Hi All,
    I have a problem here regarding the extraction process for the DataSource 2LIS_02_SCL. The values posted by date fields like
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date  (0STAT_DATE)
    In BW are suspected to be wrong values.
    So I am supposed to check the extraction process for PO Schedule Line (2LIS_02_SCL).
    So how can I proceed with this analysis in BW side as well as in SAP R/3.
    Can anyone please help with the process.
    Thanks in advance.

    Hi,
    In Bw thre is always confusion about following Dates.
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date (0STAT_DATE)
    So ask Functional Consultants and Business USers and Identify the corretc Date in ECC and then Change the Mapping In UPdate Rules in BW. i.e. What date USer is wanting and accordingly we nee dtgo change the mapping in UPdate Rules in Time Char Tab in UpdateRules.
    Thanks
    Reddy

  • How to analyze the extraction process for 2LIS_02_SCL both in R/3 & BW.

    Hi All,
    I have a problem here regarding the extraction process for the DataSource 2LIS_02_SCL. The values posted by date fields like
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date (0STAT_DATE)
    In BW are suspected to be wrong values.
    So I am supposed to check the extraction process for PO Schedule Line (2LIS_02_SCL).
    So how can I proceed with this analysis in BW side as well as in SAP R/3.
    Can anyone please help with the process.
    Thanks in advance.

    Hi,
    In Bw thre is always confusion about following Dates.
    Posting Date (0PSTNG_DATE)
    Schedule Line Delivery Date (0SCL_DELDAT)
    Statistics Date (0STAT_DATE)
    So ask Functional Consultants and Business USers and Identify the corretc Date in ECC and then Change the Mapping In UPdate Rules in BW. i.e. What date USer is wanting and accordingly we nee dtgo change the mapping in UPdate Rules in Time Char Tab in UpdateRules.
    Thanks
    Reddy

  • What is the Learning Process for SAP Business ByDesign

    Hi Experts,
    What is the Learning Process for SAP Business ByDesign
    Prashant Kapoor

    HI prasanth,
    SAP-ByD always updated day to day. you can find here:
    https://my020062.sapbydesign.com/sap/ap/ui/repository/SAP_BYD_WEKTRA/CP/sapLSUIContentPlayerTestPage.html?manifest=067D03A7602B1D490899DF46B5082089&COMPONENT=A1S_PDI&RELEASE=260&LANGUAGE=en&REGION=&INDUSTRY=&TASK=CR_VIEW&sap-language=EN
    Note: do u want open the above link u might have a  .net framework4.0 bcz this one silverlight application.
    Best Regards,
    Harish.y

  • Using Parallel Processing for Collection worklist Generation

    We are scheduling the program UDM_GEN_WORKLIST in Background mode with the below mentioned values in the variant
    Collection Segment - USCOLL1
    Program Control:
    Worklist valid from - Current date
    Ditribution Method - Even Distribution to Collection Specialists
    Prallel Processing:
    Number of jobs - 1
    Package Size - 500.
    Problem:
    The worklist gets generated but it drops lot of customers items from the worklist when the program is schduled in background using above parameters.
    Analysis:
    - When I run the program UDM_GEN_WORKLIST  in online mode all customers come through correctly on the worklist.
    - When I simulate strategy with the missing customers it evaluates them high so there is nothing wrong with the strategy and evaluation.
    - I increased the Pacakge size to its maximum size but still doesnt work.
    - Nothing looks different in terms of Collection Profile on the BP master.
    - There are always a fixed set of BP's that are missing fromt the worklist.
    It looks like there is something that I dont know about the running these jobs correctly using the parallel processing parameters, any help or insight provided in this matter would be highly appreaciated.
    Thanks,
    Mehul.

    Hi Mehul,
    I have a similar issue now; since a couple of days, the WL generation fails in background mode. Although when I'm running it in foreground processing it's completed w/o any problem.
    My question is that would you confirm that you did reduce the package size to 1?
    so, your parameters are: nr of jobs: 1  and package size: 1
    Is that right? Did it completely solve your issue?

  • The worker process for application pool 'MSExchangeAutodiscoverAppPool' encountered an error

    Hello Guys,
    I am getting an event ID 2297 with the description given below.
    The worker process for application pool 'MSExchangeAutodiscoverAppPool' encountered an error 'Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'WSMan'
    ' trying to read global module configuration data from file '\\?\C:\inetpub\temp\apppools\MSExchangeAutodiscoverAppPool\MSExchangeAutodiscoverAppPool.config', line number '275'.  Worker process startup aborted.
    Could someone help me please to resolve this.
    Thanks in Advance. :)
    Regards Rishi Aggarwal

    Hi,
    Based on the error message, it seems the issue is related to that there is a duplicate entry in the file it mentioned.
    I recommend you follow Amit’s suggestions to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for