How to minimize upgrade downtime during SAP ERP 6. By submitting your personal information, you agree that Tech. Target and its partners may contact you regarding relevant content, products and special offers. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy. Managing SAP ERP 6. Upgrade Projects. Chapter 5 Executing an Upgrade Project. About 5. 4 of organizations using SAP say that minimizing downtime is an important part of planning and executing SAP ERP upgrade projects. But what factors influence downtime What can be done to minimize downtime in an upgrade project Downtime management means controlling the time the system is unavailable, so learn how to reduce downtime related costs, and find out how the total amount of downtime can affect other decisions in an upgrade project. Oracle-VM-Setup.jpg' alt='Sap Library Ecc 6.0' title='Sap Library Ecc 6.0' />Managing SAP ERP 6. Upgrade Projects, Ch. Table of contents Managing system landscapes during SAP ERP 6. How to minimize upgrade downtime during an SAP upgrade project. Downtime Minimization. This section discusses system downtime in the context of an SAP upgrade project. Downtime is probably the biggest challenge of an upgrade and a crucial topic because it is the time when the system cannot be used by the business. In an SAP customer feedback survey, 5. Managing downtime is not just about controlling the time the system is unavailable, but also about. Furthermore, costs are not linear for longer downtime costs can increase exponentially. Sap Library Ecc 6.0' title='Sap Library Ecc 6.0' />The total amount of downtime permitted by the business has an effect on many of the other decisions you make when planning an upgrade project. Therefore, you must carefully determine the maximum downtime that will be available and precisely detail the upgrade tasks that have to be performed during that time. In this section, we will look at the factors that influence downtime and what you can do to tackle the challenge of downtime within your upgrade project. You will learn how to decide on the upgrade strategy to use and also find details about SAP tools you can use to help minimize downtime. We will also provide you with recommendations for how to reduce downtime costs. Definitions Downtime, Uptime, Runtime. This section provides an overview of what the terms downtime, uptime, and runtime mean in the context of an upgrade project. Figure 5. 6 shows the business and technical perspectives of the downtime and uptime phases. Downtime both technical and business, uptime, and runtime are described in Table 5. Table 5. 1 Definitions of Downtime, Uptime and Runtime. Term. Definition. Technical Downtime. This is the time period during which the upgrade tools perform the upgrade process without the system being available for end users. It does not include the time for data backup and final testing. Business Downtime. Sap Library Ecc 6.0' title='Sap Library Ecc 6.0' />This is the total amount of time during which the system is not available for end users. It includes the technical downtime and the time necessary for data backup and final tests. Uptime. The time during which end users can use the systems applications in production while the upgrade process is running. Runtime. The overall time it will take to carry out the upgrade process. It is measured from the start of the upgrade process to the end when the system is available for productive use again, and consists of all upgrade uptime, technical downtime, and business downtime. Business Uptime Business Downtime In any system, you can further divide downtime into planned and unplanned downtime. Unplanned downtime concerns items over which you have little direct control such as hardware, or operating system failures, as well as human error. Planned downtime, on the other hand, is very much under your control, in particular in terms of when it takes place. You are required to plan downtime for system and infrastructure maintenance and for the implementation of patches, upgrades, and changes to transports. Planned downtime can be minimized through the following Scalable components that enable rolling maintenance. Improved upgrade and patch processes. Proven software lifecycle management and propagation engines e. Why is Downtime Necessary One of the advantages of SAPs technology is that it allows customers to adapt, extend, and modify SAP software, and these extensions will be kept and adjusted to the new release during the upgrade process. Furthermore, most of the required processing steps that are part of the upgrade can be performed during system uptime. Downtime is necessary whenever live, running transactions have to be replaced by new functionality and there is a potential risk for data inconsistency, for example due to a change in the processing logic, or a change to the data model or structure. You must prepare users for business downtime and make them aware of the need for both technical downtime and business downtime. Downtime Facts and Figures. SAP has analyzed the average downtime business downtime and technical downtime for customers upgrading to SAP ERP 6. The average business downtime was calculated separately, according to the SAP source release. The SAP Community is the quickest way for users to solve problems, learn more about SAP solutions, and invent new ways to get things done. Dr. Gaetano Altavilla describes the main steps to be done in the SAP system by the logistics, planning, quality, and financial departments to perform quality. SAP SE is a software company based in Germany. SAP offers business software, targeting small and mediumsized companies, just as whole software solutions for major. Get ahead of the game with an enterprise resource planning system ERP from SAP. Learn how to minimize upgrade downtime during an SAP ERP upgrade project and use downtime management methods to attain zero downtime in an upgrade. Results showed 3. SAP R3 Enterprise and 4. SAP R3 4. 6. C. For all upgrades to SAP ERP 6. The chart shown in Figure 5. SAP ERP 6. 0 SR3 where the downtime minimized strategy was used. Choosing an Upgrade Strategy. Svchost.Exe 100 Cpu Windows Xp Patch. With the system switch technology, most upgrade activities are moved into uptime. When upgrading with the system switch upgrade procedure, SAP provides you with two upgrade strategies the downtime minimized strategy and the resource minimized strategy. You must decide which strategy to use as determined by the requirements of your organization. Two factors are key to this decision Maximum downtime permitted by your organization. System resources available. The downtime and the consumption of system resources depend on the interaction of several parameters you can set for the upgrade. To optimize the duration of downtime and the consumption of system resources, parameter settings are grouped into preconfiguration modes. Instead of setting the parameters manually, you choose the preconfiguration mode that suits your system resource situation. You select the preconfiguration mode in the upgrade GUI during the upgrade procedure. By setting the preconfiguration mode, you can choose either a resource minimized or a downtime minimized upgrade strategy. For more details, see the SAP ERP 6. Table 5. 2 shows an overview of the three available preconfiguration modes. SAP recommends using the downtime minimized strategy for the majority of upgrades. The additional resources needed should be available because SAP ERP 6. Table 5. 2 Preconfiguration Modes for Setting the Upgrade Strategy. Preconfiguration Mode. Features. Low resource use. Low system resource consumption. Early start of downtime shadow system operation during downtime upgrade strategy parameter resource minimizedICNV tool cannot be used. Standard resource use. Late start of downtime import and shadow system operation while the system is still in production operation upgrade strategy parameter downtime minimizedDatabase archiving mode is off during downtime. Database backup required before downtime. ICNV tool can be used. High resource use. Late start of downtime import and shadow system operation while the system is still in production operation upgrade strategy parameter downtime minimizedFast import.