Installation of SAP Enhancement Enhancement Package 4 for SAP ERP 6.0
Technical FAQ
This document summarizes the answers to some of the most frequently asked questions about the technical installation of SAP enhancement package 4 for SAP ERP 6.0 that have have been answered by the EHP Technology Backoffice. Backoffice.
Version 1.11 08/31/2009
Page 1
TABLE OF CONTENTS 1
Informatio Information n Sources Sources ................................ ................................................. ................................. ................................. .................................. .....................3 ....3
2
Enhanceme Enhancement nt package package Concept Concepts......................... s.......................................... .................................. ................................. ..........................5 ..........5
3
Product Product Version Versionss ................................ ................................................. .................................. .................................. ................................. ..........................8 ..........8
4
Technical Technical Usages Usages and and Softwar Softwaree Components Components............... ............................... ................................. .................................10 ................10
5
Software Software Calcula Calculation tion and Download... Download................... ................................. .................................. .................................. ........................12 .......12
6
Install Installatio ation n of EHP4 EHP4 on the the ECC ECC Server Server ................................ ................................................ ................................. ......................16 .....16
7
Install Installatio ation n of EHP4 EHP4 package packagess on other other syste systems ms ...................... ....................................... .................................. ...................18 ..18
8
Impact Impact of the install installatio ation n on the the transpo transport rt environ environment......................... ment.......................................... ......................19 .....19
9
Activat Activation ion of of busines businesss functi functions...... ons....................... ................................. ................................. .................................. ............................20 ...........20
10
Page 2
Feedbac Feedback k and Disclai Disclaimer........... mer............................ .................................. ................................. ................................. ..............................23 .............23
1 INFORMATION SOURCES 1.1 What are the central locations for EHP4 related documentation?
The two most important locations for EHP4 related documentation are:
– https://service.sap.com/erp-ehp – https://service.sap.com/ehp-inst: SAP enhancement package 4 for SAP ERP 6.0 1.2 What are the recommended text documents to be read before installing EHP4 for SAP ERP 6.0?
The SAP Technology Backoffice recommends reading the following text documents: 1. First Steps: Installation of SAP enhancement package 4 for SAP ERP 6.0 The first steps document provides a comprehensive compilation of all important information sources regarding EHP4 for SAP ERP 6.0. 2. Master Guide SAP Enhancement Package 4 for SAP ERP 6.0 The Master Guide is the central starting point for the technical installation of EHP4 for SAP ERP 6.0. It contains EHP4-specific information on cross-scenario level. Use the Master Guide to gain an overview of the enhancement package, its software units, its scenarios, processes, and role-based work centers from a technical perspective. 3. What IT Professionals Need To Know about SAP Enhancement Packages This document summarizes the basic enhancement package concepts. It will help you to quickly become familiar with enhancement packages for SAP ERP 6.0. 4. SAP Enhancement Package Installer (SAPehpi) Guide This document describes the installation of enhancement package components on an SAP system using the SAP Enhancement Package Installer. In particular, it is the only document that contains a detailed list of all the technical preparations and follow-up activities that are necessary when enhancement packages are installed using the SAP Enhancement Package Installer. 5. How to Install SAP Enhancement Package 4 for SAP ERP 6.0 This document provides an overview of the end-to-end process that is required to download and install EHP4 for SAP ERP 6.0. In particular, it describes the preparations that have to be performed on the SAP Solution Manager. Furthermore, it specifies how to calculate and download the EHP4 software packages using the SAP Solution Manager Maintenance Optimizer. 1.3 Which presentations should you view before installing EHP4 for SAP ERP 6.0?
The SAP Technology Backoffice recommends viewing the following presentations: 1. SAP Enhancement Packages for SAP ERP: Technology Facts This presentation provides a comprehensive compilation of the concepts, tools and best practices regarding the installation of EHP4 for SAP ERP 6.0. In contrast to the text documents about enhancement packages, most of the subjects are illustrated with graphical figures and examples. 2. Lifecycle of an Enhancement Package This presentation describes the installation procedure for enhancement packages from
Page 3
a business function perspective. It explains how to det ermine relevant business functions, how to select the corresponding technical usages, and how to plan the acceptance tests that have to be performed after the activation of a business function. 1.4 Is there a central document that describes all the business functions of EHP4 for SAP ERP 6.0?
Yes, the textbook SAP Enhancement Package 4 for SAP ERP 6.0: Details contains descriptions of all the business functions that are new with EHP4 for SAP ERP 6.0. 1.5 Is there a place to discuss enhancement package related questions with other SAP professionals?
Yes. There is a forum for discussion of enhancement package related questions on the SDN. 1.6 Does SAP Consulting offer workshops on enhancement packages for SAP ERP 6.0?
Yes. SAP Consulting offers the service Enhancement package planning for SAP ERP 6.0 which has the following objectives:
– Establish a time frame, identify the dependencies, and define the required resources to start the technical implementation of an enhancement package
– Understand the relation between business functions, technical usages and software components of an enhancement package.
– Learn the new strategy to apply SAP enhancement packages continuously as a normal maintenance activity
– Address issues related to technology, project risks, testing, and get behind the concept of switchable business functions
– Minimize the effort and downtime of an SAP enhancement package implementation project You can find additional information about this service on the SAP Service Marketplace. Apart from this service offering, we can also offer a customer individual EHP workshop or technical review & optimization sessions. If you would like to order any kind of technical EHP workshop or review sessions, please contact us via e-mail.
Page 4
2 ENHANCEMENT PACKAGE CONCEPTS 2.1 Are enhancement packages cumulative?
We would like to clarify this without using the term "cumulative", as this term could potentially be ambiguous:
– You can install EHP4 for SAP ERP 6.0 in one step on 64-bit platforms without having installed EHP3 before.
– Every EHP version includes the content of any previous EHP versions. For example, you cannot install EHP4 without getting the content of EHP3 and EHP2 as well.
– Technically, SAP has started to deliver EHP software packages as delta packages with EHP4 for SAP ERP 6.0. Thus, your EHP4 installation queue will contain EHP4 and EHP3 packages if you have not already installed EHP3. However, all these packages should be installed in one step on 64-bit platforms. 2.2 Is it necessary to install Support Packages prior to an EHP installation?
As a rule, it is neither necessary nor recommended to install Support Package prior to the EHP4 installation. Do not install new Support Packages prior to an EHP installation unless you are sure that t he equivalent EHP Support Packages have already been released. Please check SAP Note 832594 for additional information. Currently, there is only one known exception to this rule: If software component IS-OIL will be updated to version 604, SAP_BASIS 700 Support Package 13 has to be installed prior to the EHP4 installation. 2.3 Is it possible to install EHP4 for SAP ERP 6.0 without installing Support Packages?
No, as a general rule it is not possible to install enhancement packages for SAP ERP 6.0 without installing equivalent SAP ERP 6.0 Support Packages. An EHP4 installation will include at least EHP4 SP Stack 01 which is equivalent to SAP ERP 6.0 SP Stack 14. SAP recommends the inclusion of the latest available EHP SP Stack. 2.4 Is it possible to uninstall enhancement packages?
No, it is not possible to uninstall enhancement packages. 2.5 Is it possible to undo the activation of a business function?
Currently, it is not possible to undo the activation of business functions. However, future EHP versions will differentiate between reversible and non-reversible business functions. 2.6 Is it necessary to perform a regression test after an EHP installation?
SAP strongly recommends a full regression test after each EHP installation (which is also recommended for SP Stack installations).
Page 5
2.7 Is it necessary to perform delta customizing, user acceptance tests, and end user training after an EHP installation?
On ABAP-based systems, installation of EHP software component versions does not change the system behavior unless you activate business functions. Consequently, delta Customizing, user acceptance tests and end user training are only necessary if you activate business functions. On Java-based systems, the deployment of EHP software component versions can change the system behavior immediately. Consequently, delta Customizing, user acceptance tests, and end user training might be necessary after the deployment of EHP software component versions. Check SAP Note 1160106. 2.8 Is it possible to install EHP4 for SAP ERP 6.0 on non-unicode systems?
Yes, it is possible to install EHP4 for SAP ERP 6.0 on non-unicode systems. However, it is not possible to build up a non-unicode installation of SAP ERP 6.0 EH P4 from scratch. 2.9 What is the general procedure for the installation of EHP4 for SAP ERP 6.0?
The general procedure for the installation of EHP4 for SAP E RP 6.0 is as follows: 1. Determine the technical usages EHP4 for SAP ERP 6.0 that you want to install. After the installation of EHP4 for SAP ERP 6.0, a business function will only be available if it is part of the selected technical usages. 2. Create a maintenance transaction in the SAP Solution Manager and select the appropriate technical usages in order to calculate the corresponding software packages. 3. Install the calculated software packages with the appropriate installation tool for your hardware platform: a. On 64-bit systems, the SAP EHP Installer is the only supported installation tool. b. On 32-bit systems, SAINT and JSPM are the only supported installation tools. Further information can be found in t he document How to Install SAP Enhancement Package 4 for SAP ERP 6.0. 2.10 How can I install SAP ERP 6.0 EHP4 from scratch?
If you want to install SAP ERP 6.0 EHP4 from scratch, you must proceed in two steps: 1. First install SAP ERP 6.0 from a special media set ("SAP ERP 6.0 EHP4 ready") which can be downloaded at the SAP Software Distribution Center ( Download Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Application Components SAP ERP SAP ERP ENHANCE PACKAGE ).
2. In a second step, use the SAP EHP Installer to install the technical usages of EHP4 that your business requires. This second step is mandatory for using the system productively. Please note that you are not allowed to use the installation of only SAP ERP 6.0 EHP4 ready for a productive system without applying further EHP4 technical usages in a second step.
Page 6
2.11 What is contained in an "SAP ERP 6.0 EHP4 ready" installation?
SAP ERP 6.0 EHP4 supports the selective installation of new software component versions. SAP's customers install different technical usages depending on their business and on the role of the system. It is not possible to provide an "installation export" for all of the possible combinations of technical usages. The media set "SAP ERP 6.0 EHP4 ready" only contains those EHP software component versions that have to be installed in every EHP4 installation. Basically, this means SAP NetWeaver 7.0 EHP1 and a few other EHP4-specific software components. Please note that you are not allowed to use the installation of only SAP ERP 6.0 EHP4 ready for a productive system without applying further EHP4 technical usages in a second step. 2.12 Does the maintenance (Support Package installation) of an EHP4 system differ from the maintenance of an SAP ERP 6.0 system?
Typically, an SAP ERP 6.0 EHP4 system contains a combination of application software components with version 600 and version 604. These two types of software component versions need different Support Packages: 1. Software components with version 600 need SAP ERP 6.0 Support Packages 2. Software components with version 604 equivalent EHP4 Support Packages SAP Note 1297231 describes the relationship between SAP ERP 6.0 Support Packages and EHP4 Support Packages. However, it is not necessary to compile the correct combination of Support Packages manually. If the software component versions of the target system are correctly maintained in transaction SMSY, the SAP Solution Manager Maintenance Optimizer automatically calculates the correct combination of Support Packages. If you want to install EHP4 SP Stack 03 on an existing EHP4 system, see also the section Download of Support Package Stack 03 in SAP Note 1297231.
Page 7
3 PRODUCT VERSIONS 3.1 What is the difference between the two product versions “EHP4 for SAP ERP 6.0” and “EHP4 for SAP ERP 6.0 / NW 7.01”?
EHP4 for SAP ERP 6.0 is based on EHP1 for SAP NetWeaver 7.0. Consequently, two kinds of software component versions are delivered with EHP4 for SAP ERP 6.0:
– EHP4 application software components (typically version 604 *) – SAP NetWeaver 7.0 EHP1 software components (typically version 701 *) SAP offers you two landscape options for running EHP4 applications in your SAP ERP 6.0 landscape: "EHP4 for SAP ERP 6.0" and "EHP4 for SAP ERP 6.0 / NW 7.01". In both product versions, all ABAP-based product instances must be installed on SAP NetWeaver 7.0 EHP1. For SAP NetWeaver 7.0 systems with usage types “Enterprise Portal”, “Business Intelligence” or “Process Integration” that are part of your SAP ERP 6.0 landscape, you can choose between the following two options:
– Installation of the EHP4 application software components only (product version “EHP4 for SAP ERP 6.0”)
– Installation of the EHP4 application software components and the SAP NetWeaver 7.0 EHP1 software components (product version “EHP4 for SAP ERP 6.0 / NW701”). If product version “EHP4 for SAP ERP 6.0” is used, EHP1 for SAP NetWeaver 7.0 is installed only on the system that contains the ECC Server, and on other systems that contain ABAP-based product instances of SAP ERP 6.0. If product version “EHP4 for SAP ERP 6.0 / NW 7.01” is used, EHP1 for SAP NetWeaver 7.0 is also installed on systems with usage types “Enterprise Portal”, “Business Intelligence” or “Process Integration” that are part of your SAP ERP 6.0 landscape. 3.2 When should product version “EHP4 for SAP ERP 6.0” be used?
Product version “EHP4 for SAP ERP 6.0” must be used if some of your S AP ERP 6.0 product instances (for example, XSS Self Services) run on a Java-based system that must not be updated to SAP NetWeaver 7.0 EHP1. For example, a Java-based system must not be updated to SAP NetWeaver 7.0 EHP1 if you have deployed additional Java software components on it that are incompatible with SAP Net Weaver 7.0 EHP1. 3.3 When should product version “EHP4 for SAP ERP 6.0 / NW 7.01” be used?
Product version “EHP4 for SAP ERP 6.0 / NW 7.01” should be used if all Java-based systems that contain SAP ERP 6.0 product instances (for example, XSS Self Services) can be updated to SAP NetWeaver 7.0 EHP1. A Java-based system can be updated to SAP NetWeaver 7.0 EHP1 if all Java software components that are deployed on it are compatible with SAP NetWeaver 7.0 EHP1.
*
If no new version had been part of the very product version development, then the old version had been taken over into the new product version.
Page 8
3.4 Is it possible to install EHP1 for SAP NetWeaver 7.0 only for usage type “AS ABAP” of a dual-stack system?
No, all usage types in your system are updated by EHP1 for SAP NetWeaver 7.0. In dual-stack systems, the usage types “AS ABAP” and “AS Java” must always be updated together. It is not possible to update only parts of your system. Please also check the section about enhancement packages in the Master Guide SAP NetWeaver 7.0. 3.5 Is it possible to install EHP1 for SAP NetWeaver 7.0 only on SAP NetWeaver 7.0 systems with a specific usage type?
Yes, in principle it is possible to install EHP1 for SAP NetWeaver 7.0 only on SAP NetWeaver 7.0 systems with a specific usage type. For example, you could install EHP1 for SAP NetWeaver 7.0 on systems with usage type “Business Intelligence” while keeping the systems with usage type “Enterprise Portal” on SAP NetWeaver 7.0. In this case, you need two different maintenance transactions to calculate and download the software packages for your systems: One maintenance transaction with product version “EHP4 for SAP ERP 6.0” and another maintenance transaction with product version “EHP4 for SAP ERP 6.0 / NW 7.01”.
Page 9
4 TECHNICAL USAGES AND SOFTWARE COMPONENTS 4.1 What is the definition of a technical usage?
Technical usages contain combinations of software component versions that are required to use specific business functions of an enhancement package for S AP ERP 6.0. The relationship between business functions, technical usages, and software components is explained in detail in the Technology Facts presentation. When you calculate the software packages for EHP4 for SAP ERP 6.0, the Maintenance Optimizer requests you to select t he required technical usages. Depending on the selection of the technical usages, the Maintenance Optimizer includes the EHP4 software packages only for those software components that must be updated to use the desired business functions. After the installation of EHP4 for SAP ERP 6.0, business functions can only be activated if the corresponding technical usage had been selected in the Maintenance Optimizer. However, it is possible to install additional technical usages later with additional effort similar to the initial EHP installation. 4.2 How can I determine the technical usages for the installation of EHP4 for SAP ERP 6.0?
There are two different approaches to determine the technical usages for the installation of EHP4 for SAP ERP 6.0. These approaches are also known as the “selective installation” and the “broad installation”: 1. The selective installation is the recommended way to determine the technical usages for the installation of EHP4. It consists of two steps: a. Identify the business functions that you want to use. A complete description of all the EHP4 business functions can be found in the textbook on EHP4 Functionality. b. For each identified business function, the corresponding technical usage can be determined with the mapping table that is attached to SAP Note 1165438. 2. The broad installation can be used when it is not possible to determine the required business functions prior to the technical installation of EHP4 for SAP ERP 6.0. I n this case, you can try to select the technical usages from a technical point of view. T he corresponding procedure is described in the following blog on the SAP Developer Network: https://weblogs.sdn.sap.com/pub/wlg/9880. 4.3 Are there any technical usages that must be selected?
You are not allowed to mix different EHP versions within one system. The following examples illustrate the implications of this rule:
– Combination of application software component versions 600 and 602: supported – Combination of application software component versions 600 and 603: supported – Combination of application software component versions 600 and 604: supported – Combination of application software component versions 602 and 604: not supported – Combination of application software component versions 603 and 604: not supported
Page 10
Because of this rule, all software components with version 602 or 603 must be updated to version 604 during an EHP4 installation. For this reason, the selection of technical usages in the Maintenance Optimizer must cover at least the software components which are already on version 602 or 603. Check the attachments to SAP Note 1165438 to determine the appropriate technical usages. Furthermore, if the ECC Server contains active industry solutions, the corresponding technical usages must be selected as well. For example, if industry solution IS-OIL is active, the technical usage “Oil & Gas” must be selected. Check the attachments in SAP Note 1165438 to determine the corresponding technical usage for a particular industry solution. 4.4 What happens if a large number of technical usages are selected?
If you select a large number of technical usages, a correspondingly large number of software components are updated to version 604. When a newer EHP version (for example, EHP5 for SAP ERP 6.0) is installed later, you have to update all these software components to the new EHP version. Furthermore, the effort for modification adjustment (SPDD/SPAU) might be higher if a large number of technical usages are selected. 4.5 Is it possible to install additional technical usages after the initial installation of EHP4 for SAP ERP 6.0?
After the initial installation of EHP4 for SAP ERP 6.0, you can install additional technical usages. However, each installation of an additional technical usage requires an additional effort similar to the initial EHP installation (for example, testing). The standard tool for the installation of additional technical usages is the EHP Installer. Read section Disabling the Java Stack Handling in SAP Note 1245473 before installing additional technical usages on dual-stack systems. 4.6 Is it possible to use transaction SAINT for the installation of additional technical usages after the initial installation of EHP4 for SAP ERP 6.0?
Technically, it is possible to install additional technical usages with transaction SAINT if t he technical usage “Central Applications” has already been installed. However, this option requires a high level of expertise and is not recommended by SAP. In particular, the use of SAINT can result in a longer downtime compared to the EHP Installer. Make sure you import the newest SPAM/SAINT update before installing additional technical usages with transaction SAINT. If you do use SAINT, you still have to generate a stack configuration file with the SAP Solution Manager Maintenance Optimizer. If you want to use the parallel import feature of R3trans, follow the instructions of SAP Note 1309506.
Page 11
5 SOFTWARE CALCULATION AND DOWNLOAD 5.1 How can I obtain the software packages for the installation of EHP4 for SAP ERP 6.0?
All the software packages that are required for the installation of EHP4 for SAP ERP 6.0 have to be calculated by the Maintenance Optimizer of the SAP Solution Manager. The Maintenance Optimizer will calculate the software packages not only for the ECC Server, but also for the other systems that might belong to your SAP ERP 6.0 landscape (for example, an Enterprise Portal, SAP BW/BI system, or SAP PI/XI system). After the appropriate software packages have been calculated, they have to be downloaded via the SAP Download Manager or via the SAP Software Lifecycle Manager. If the download is too slow, some of the large software packages can be copied from the DVD “SAP Enh. Package 4 for SAP ERP 6.0” (material number 51033594) that can be ordered separately. 5.2 Is it possible to install EHP4 for SAP ERP 6.0 without using the SAP Solution Manager Maintenance Optimizer?
No. You are not allowed to install EHP4 for SAP ERP 6.0 without using the SAP Solution Manager Maintenance Optimizer. All supported installation tools (including current versions of SAINT) require a stack configuration file that can only be generated by the Maintenance Optimizer. It is not possible to install EHP4 for SAP ERP 6.0 without this stack configuration file. 5.3 What are the Support Package and SAP Note requirements for the SAP Solution Manager?
SAP recommends always using the latest SAP Solution Manager 7.0 SP Stack for EHP4 package calculation. As of July 2009, SAP Solution Manager 7.0 SP Stack 20 is recommended. When EHP4 for SAP ERP 6.0 entered the ramp-up, the minimum Support Package requirement for the Solution Manager was SP Stack 15. However, the EHP Technology Backoffice recommended using SP Stack 17 which requires less Note corrections. Depending on the SP Stack level of your SAP Solution Manager, multiple Note corrections must be implemented to ensure that the Maintenance Optimizer will generate a valid stack configuration file for EHP4 for SAP ERP 6.0. The current list of relevant Note corrections can be found in SAP Note 1122966. 5.4 What configuration is necessary in the SAP Solution Manager?
The Maintenance Optimizer calculates the required software packages based on the SAP Solution Manager system landscape (transaction SMSY). To ensure the correct calculation of the software packages, all systems that belong to your SAP ERP 6.0 solution, must be maintained correctly in transaction SMSY. Detailed information can be found in the document How to install EHP4: A practical guide. Caution: If the system landscape is not maintained correctly, this may result in invalid stack configuration files and severe installation problems.
Page 12
5.5 What are the most common mistakes regarding SMSY configuration for EHP4 for SAP ERP 6.0?
The three most common mistakes regarding the SMSY configuration are: 1. Assignment of wrong product versions 2. Incorrect modeling of Java-based systems and dual-stack systems 3. Incomplete maintenance of SAP ERP 6.0 product instances 1. The Maintenance Optimizer offers the option “EHP4 for SAP ERP 6.0” only for systems that have product version SAP ERP 6.0 assigned. If the Maintenance Optimizer does not of fer the option “EHP4 for SAP ERP 6.0” for a system, check whether product version SAP ERP 6.0 is assigned to the system. 2. If you have Java-based systems or dual-stack systems, you must use the SLD (system landscape directory) to create the SMSY entries for these systems. The Java stack must be registered in the SLD via the SLD data provider service of the V isual Administrator. After the system has been registered in the SLD, the SMSY must be synchronized with the SLD via transaction SMSY_SETUP. Finally, make sure that the product version is correct and that the correct Java software component versions are displayed in the Software Components tab. 3. In transaction SMSY, each system entry contains a Selection of Main Instances tab. All active product instances must be marked as relevant on this tab. If an SAP ERP 6.0 product instance runs on a different system than the ECC Server, the SID of this system must be registered for the corresponding product instance. 5.6 Where can I obtain the stack configuration file for the installation tools?
In order to calculate the EHP4 software packages, a maintenance transaction has to be created in the Maintenance Optimizer of the SAP Solution Manager. At the end of the maintenance transaction, the Maintenance Optimizer will generate an XML file that contains the stack configuration and save this file to directory “
/in” of the Solution Manager. The stack configuration file can be provided to the installation tools in two different ways: 1. The installation tools can read the stack configuration file from the SAP Solution Manager if table BCOS_CUST has been maintained correctly in the target system via transaction SM30. In this table, entry OSS_MSG must contain a working RFC connection to the Solution Manager. 2. If no working RFC connection is maintained in table BCOS_CUST, you can copy the stack configuration file to the target system manually. In this case, the stack configuration file should be placed in the same directory that contains the EHP4 software packages. 5.7 How can I calculate the EHP4 packages for Java-based product instances of SAP ERP 6.0, such as SAP XSS (Self Services)?
Before you can calculate the EHP4 packages for Java based product instances, you must assign the SID of the Java-based system to the appropriate instances of an SAP ERP 6.0 system in transaction SMSY. To do this, click on the SID of an SAP ERP 6.0 system (for example, the ECC Server system) and make the required entries in the Selection of Main Instances tab (below, NW7 is an example for the SID of your Java-based system):
Page 13
When a maintenance transaction is created for a system of product type “SAP ERP 6.0”, the Maintenance Optimizer will calculate the packages for all the systems that have been registered for at least one of the product instances. In the previous example, the Maintenance Optimizer also calculates the required software packages for the Java-based product instance SAP XSS (Self Services) on system NW7 . 5.8 How can I calculate the EHP4 packages for an Enterprise Portal that contains business Packages (content) of SAP ERP 6.0?
Before you can calculate the EHP4 packages for an SAP Enterprise Portal (EP) system that contains business packages (content) of SAP ERP 6.0, you must assign the SID of the EP system to the appropriate instances of an SAP ERP 6.0 system in transaction SMSY. To do this, click on the SID of an SAP ERP 6.0 system (for example, the ECC Server system) and make the required entries in the Selection of Main Instances tab (below, EP7 is an example for the SID of your EP system):
When a maintenance transaction is created for a system of product type “SAP ERP 6.0”, the Maintenance Optimizer calculates the packages for all the systems that have been registered for at least one of the product instances. In the previous example, the Maintenance Optimizer also calculates the required software packages for EP system EP7 . 5.9 How can I calculate the EHP4 packages for a BI (Business Intelligence) system that is part of my SAP ERP 6.0 landscape?
If product version “EHP4 for SAP ERP 6.0” is used, BI_CONTENT 704 has to be downloaded manually at the Software Distribution Center on SAP Service Marketplace. If product version “EHP4 for SAP ERP 6.0 / NW 7.01” is used, you must change the product version of your SAP BI system to “SAP ERP 6.0” in transaction SMSY and assign the appropriate products instances on the Selection of Main Instances tab (below, BI7 is an example for the SID of your BI system): Page 14
After you have made the changes specified above, you can calculate the EHP4 packages via a separate maintenance transaction for system BI7 (replace BI7 with the SID of your BI system). 5.10 How can I calculate the EHP4 packages for a PI (Process Integration) system that is part of my SAP ERP 6.0 landscape?
Before you can calculate EHP4 packages for an SAP Process Integration (PI) system, you must change the product version of that system to “SAP ERP 6.0” in transaction SMSY and assign the appropriate product instances on the Selection of Main Instances tab (below, PI7 is an example for the SID of your PI system):
Once you have made the changes specified above, you can calculate the E HP4 packages via a separate maintenance transaction for system PI7 (replace PI7 with the SID of your PI system).
Page 15
6 INSTALLATION OF EHP4 ON THE ECC SERVER 6.1 What tool must be used to install EHP4 on the ECC Server?
If the ECC Server runs on a 64-bit platform, the initial installation of EHP4 must be performed with the EHP Installer. If the ECC Server runs on a 32-bit platform, transaction SAINT is the only supported installation tool. You should note that EHP4 for SAP ERP 6.0 must be installed in two steps in this case. The exact procedure is described in SAP Note 1275873. Make sure you import the latest SPAM/SAINT update before installing EHP4 for SAP ERP 6.0 on a 32-bit platform. If you want to use the parallel import feature of R3trans, follow the instructions of SAP Note 1309506. 6.2 Is it possible to update separately the ABAP and Java stacks of a dual-stack system?
If you are running a dual-stack system, you always have to update the ABAP stack and Java stack in parallel. The EHP Installer always updates both parts of the system. 6.3 What can you do to optimize the runtime and downtime of the EHP Installer?
The runtime and downtime of the EHP Installer depends on many different criteria. However, the following preparations can help to reduce runtime and downtime:
– Perform all the database specific preparations that are recommended in the SAP Enhancement Package Installer (SAPehpi) Guide (database parameters, update of database statistics, and so on.)
– Install current versions of R3trans and tp before you start the EHP installation on the development system. Current versions of R3trans can be obtained at https://service.sap.com/patches (Support Packages and Patches - Entry by Application Group Additional Components SAP Kernel).
– Download the current version of the EHP Installer before you start the EHP installation on the development system. The current version of the EHP Installer can be obtained at https://service.sap.com/patches (Support Packages and Patches - Entry by Application Group Additional Components Upgrade Tools SAP EHP INSTALLER SAP EHP INSTALLER 7.00 )
6.4 Is it possible to reset a running EHP installation, and if so, what is the correct way to reset the installation?
The correct way to reset a running installation depends on the current roadmap step of the installation. A detailed description can be found in the SAP Enhancement Package Installer (SAPehpi) Guide. The EHP Installer allows you to reset a running installation up to the DOWNCONF_TRANS phase. Once the roadmap step Downtime has been started, it is no longer possible to reset the installation. 6.5 Does the EHP Installer allow repeating certain roadmap steps or phases of the installation?
The EHP Installer divides the installation process into different roadmap steps and phases, where each roadmap step consists of several phases. Page 16
Once an installation phase has been finished successfully, the EHP Installer does not allow going back and repeating that specific phase. However, you can use the back button to undo a complete roadmap step and run it again afterwards. Further information can be found in the SAP Enhancement Package Installer (SAPehpi) Guide. 6.6 Installation phase EHP_INCLUSION fails with message "ERROR: Unable to generate add-on queue". What could be the reason?
At the beginning of the installation, you must specify a download directory. In phase SCANDIR_EPS, the EHP Installer extracts all the software packages in that download directory to “/in”. From there, the packages are uploaded into the SAP system. After a stack configuration file has been chosen in phase EHP_INCLUSION, the EHP Installer tries to calculate a consistent installation queue. If t he queue calculation fails, you can try the following: 1. Make sure that the software packages in the download directory are identical to the software packages that are specified in the stack configuration file. 2. Using transaction SEPS, choose Inbox from Goto menu. Here, you can check if a particular package has been uploaded into the SAP system successfully. 6.7 What is meant by the term “equivalent Support Packages” in installation phase BIND_PATCH?
There are separate Support Packages for SAP ERP 6.0 software components and for EHP4 software components. Each EHP4 Support Package is equivalent to a certain SAP ERP 6. 0 Support Package. After an EHP4 installation, the Support Package levels of all EHP4 software components must be equivalent to the SAP ERP 6.0 Support Package levels of the original system. The EHP Installer checks whether the stack definition contains all the EHP4 Support Packages that are required to maintain the Support Package equivalence. The results of this check will be displayed in phase BIND_PATCH. If some equivalent EHP4 Support Packages are missing, you must add them manually in this phase. Note that a violation of the Support Package equivalence may result in severe system inconsistencies.
Page 17
7 INSTALLATION OF EHP4 PACKAGES ON OTHER SYSTEMS 7.1 How can EHP4 be installed for ABAP-based product instances of SAP ERP 6.0 that are installed on a different system from the ECC Server?
There are three ABAP-based product instances of SAP ERP 6.0 that can be installed on a different system from the ECC Server:
– E-Recruiting (software component ERECRUIT) – Learning Solution Front End (software component LSOFE) – Strategic Enterprise Mgmt. (software components SEM-BW + FINBASIS). If you have one of the previously mentioned product instances installed on a system different from the ECC Server, and you want to update this product instance to EHP4 for SAP ERP 6.0, follow the instructions in SAP Note 1326576. Currently, it is not possible, to install version 604 of these product instances directly on a system of product version SAP NetWeaver 7.0 EHP1. If you want to install a system with version 604 of these product instances from scratch, you must proceed in two steps: 1. Install a system with product version NetWeaver 7.0 and add version 600 of the appropriate product instance. 2. Follow the instructions in SAP Note 1326576. 7.2 What tool should be used to deploy EHP4 specific portal content on the SAP Enterprise Portal?
If product version “EHP4 for SAP ERP 6.0” is used, EHP1 for NetWeaver 7.0 is not installed on the SAP Enterprise Portal. In this case, the EHP4 specific portal content for the SAP Enterprise Portal should be deployed with the JSPM tool. If product version “EHP4 for SAP ERP 6.0 / NW 7.01” is used, EHP1 for NetWeaver 7.0 will be installed on the SAP Enterprise Portal. In this case, the E HP Installer will also deploy the EHP4 specific portal content if it is part of the stack configuration file. 7.3 What tool should be used to deploy EHP4 specific BI content on SAP BI/BW systems?
If product version “EHP4 for SAP ERP 6.0” is used, EHP1 for NetWeaver 7.0 is not installed on SAP BI/BW systems. In this case, BI_CONTENT 704 must be installed via transaction SAINT. If product version “EHP4 for SAP ERP 6.0 / NW 7.01” is used, EHP1 for NetWeaver 7.0 is installed on SAP BI/BW systems. In this case, the EHP I nstaller also installs the EHP4 specific BI content if it is part of the stack configuration file. 7.4 What tool should be used to deploy EHP4 specific XI content on SAP PI/XI systems?
XI content is always deployed using the Integration Builder tool of the SAP PI/XI system.
Page 18
8 IMPACT OF THE INSTALLATION ON THE TRANSPORT ENVIRONMENT 8.1 Is it possible to transport from an EHP4 system into an SAP ERP 6.0 system if no EHP4 business functions have been activated in the EHP4 system?
No. As a rule, transports are only supported between systems with identical software component versions and Support Package level. SAP ERP 6.0 EHP4 has different software component versions and Support Package levels from SAP ERP 6.0. Consequently, transports between such systems are not supported. However, there are some exceptions to the above rule. Check SAP Note 1090842 for additional information on this topic. 8.2 Is it possible to transport between two EHP4 systems that have different business functions activated?
As a general rule, transports are only supported between systems that share the same activation states in transaction SFW5. However, there are some situations where certain kinds of transports might still work. Individual recommendations about the transport strategy for systems with differing activation states are considered a consulting service. Please contact [email protected] for additional information. 8.3 How can corrections for the production system be transported after EHP4 has already been installed on the DEV system?
Individual recommendations on the transport strategy that should be used during your EHP installation project are considered a consulting service. Please contact [email protected] for additional information. 8.4 How can corrections for the production system be transported after EHP4 has already been installed on the DEV and the QAS system?
Individual recommendations on the transport strategy that should be used during your EHP installation project are considered a consulting service. Please contact [email protected] for additional information. 8.5 Is there any way to import transport requests into a system after the EHP Installer has locked the development environment in phase REPACHK2?
No. The EHP Installer locks the development environment in phase REPACHK2, because there is no safe way to change or import repository objects after that phase. If you disregard the development lock this may lead to data loss and inconsistencies. SAP will not provide support for issues that result from the unauthorized disregard of t he development lock.
Page 19
9 ACTIVATION OF BUSINESS FUNCTIONS 9.1 Will the technical installation of EHP4 for SAP ERP 6.0 activate any business functions automatically?
No. The technical installation of EHP4 for SAP ERP 6.0 will not activate any business functions automatically. After installation of EHP4 for SAP ERP 6.0, all the new business functions are inactive in the ABAP-based ECC Server system. On Java-based systems, new functions become active immediately after the deployment of the corresponding Java software component versions. 9.2 What happens to business functions previously activated when EHP4 for SAP ERP 6.0 is installed?
The technical installation of EHP4 for SAP ERP 6.0 does not change the state of business functions that have already been activated. If your system already contains active business functions (for example, EHP3 business functions), these business functions remain active after the installation of EHP4 for SAP ERP 6.0. You cannot reactivate business functions that have already been activated before the installation of EHP4 for SAP ERP 6.0, nor is this necessary. 9.3 Is it possible to undo the activation of a business function?
Currently, it is not possible to undo the activation of business functions. However, future EHP versions will differentiate between reversible and non-reversible business functions. 9.4 In which system should a business function be activated for the first time?
SAP recommends activating business functions in a test environment (meaning a sandbox system) for the first time. This allows you to explore the new functions and to test the system without being put under pressure. 9.5 How are business functions activated in a sandbox or development system?
In a sandbox or development system, business functions are activated directly in transaction SFW5. Transaction SFW5 displays a list w ith the business functions sets of all technical usages that have already been installed on the system. For each business function the following information is displayed:
– Activation state of the business function set (color of the lamp icon) – Link to test case templates (notepad icon) You activate business functions in transaction SFW5 by sett ing the flags for t he corresponding business sets and choosing Activate Changes. A background job is then scheduled that carries out the changes. Note that the SAP user needs appropriate authorizations to activate business functions in transaction SFW5. 9.6 How should business functions be activated in a quality assurance or production system?
Due to the system change options, it is usually not possible to activate business functions directly in a quality assurance or production system. Instead, the business function settings
Page 20
should be transported from the development system into the quality assurance and production system (in that order). A transport request that contains the business function settings of the development system can be generated in transaction SFW5. To generate the transport request, call transaction SFW5 in the development system and choose Transport from menu System Settings. After the transport has been generated, it can be imported to the quality assurance system. The import o f the transport request automatically activates the same business functions that were in the development system when the transport request was generated. 9.7 What are the impacts of activating a business function? Which acceptance tests are necessary?
To gauge the impacts resulting from the activation of a business function, transaction SFW5 provides the impact analyzer tool. The impact analysis for a specific business function can be triggered by choosing Impact Analyzer from the context menu of the corresponding business function set. The impact analysis returns a list of all transactions that are affected by the activation of the business function. Additionally, SAP provides a test case template for each business function. These documents contain detailed descriptions of all the acceptance tests that are recommended after the corresponding business function has been activated. After the installation of EHP4 for SAP ERP 6.0, the test case templates can be accessed via the links (notepad icon) in transaction SFW5. Prior to the installation of EHP4 for SAP ERP 6.0, the test case template can be accessed on SAP Service Marketplace ( https://service.sap.com/erp-ehp):
First, select the appropriate link from section (1), then search for the required business function and click on link (2).
Page 21
9.8 Are there any dependencies between the activation of business functions and the deployment of Java software component versions?
Yes, there can be dependencies between the activation of business functions in the ECC Server and the deployment of Java software component versions. As specified in SAP Note 1160106, some business functions require the deployment of a particular Java software component version. For example, the activation of the business function “Learning Solution 02” (HCM_LSO_CI_2) requires the deployment of the Java software component versions LSOCP 604, LSOOP 604, LSOAE 604. Additional information on the dependencies of product instance “SAP Learning Solution” can be found in SAP Note 1170324. In general, such dependencies are also documented in the detailed descriptions of t he business functions on SAP Service Marketplace (https://service.sap.com/erp-ehp):
First, select the appropriate link from section (1), then search for the required business function and click on link (2).
9.9 Do I have to activate business functions in a specific client of the SAP system?
In principle, the activation of a business function is client-independent, i.e. the new functionality will be available in all clients of the SAP system. However, the activation of a business function via transaction SFW5 will also trigger the extraction of template customizing for t he new business function. The template customizing will be extracted into a specific client of the SAP system. In order to avoid overwriting existing customizing, you should activate business function in client 000 and follow the instructions of SAP Note 337623 carefully.
Page 22
10 FEEDBACK AND DISCLAIMER 10.1 Feedback
SAP is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, you can send feedback directly to [email protected]. Please provide the document title in your e-mail. 10.2 Disclaimer
This documentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, t he implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
Page 23
