Based on Community Project and SAP enhancement package forum here are the frequently asked questions:
1. What distinguishes an enhancement package from a standard upgrade?
With an enhancement package, you have the option to update only specific subsets of software components of your system related to specific business functions. Afterward, you select and activate business functions; the system behavior will change only where a business function has been activated. This targeted update and activation process is key within the delivery methodology of enhancement packages.
2. When is the best time to install an enhancement package?
SAP strongly recommends installing the enhancement package for SAP ERP when performing a regular SP stack implementation. The installation of enhancement packages and the application of the SP stack should be done together in one queue in the SAP add-on installation tool (known as transaction SAINT) or the SAP enhancement package installer. This reduces the downtime and manual effort for the whole installation procedure. In addition, you can leverage synergies concerning modification adjustment as well as regression testing for all software components at that time.
3. How much end-user training is needed after installing an enhancement package?
No end-user training is required for a pure installation (in other words, the loading of the enhancement package). End-user training for activation is required only for changes that are not intuitive. The changes are documented in the corresponding documentation for each business function.
4. Which tests are necessary when implementing an enhancement package?
Installing an enhancement package requires a regression test (the same as the test required when implementing support packages). Activation of a business function within an enhancement package requires an acceptance test of the business function. A proposal for the scope is documented in the test catalog that SAP delivers with each enhancement package. The test catalog can be reviewed in SAP Service Marketplace or (after installing an enhance ment package) in the switch transaction (/sfw5).
5. Is there a direct upgrade path available from e.g. SAP R/3 4.6c to an SAP enhancement packages?
SAP delivered this feature with support release 3 for SAP ERP 6.0. When upgrading to SAP ERP 6.0, the new upgrade tools included in this support release allow you to optionally include parts of an enhancement package. Thus, you can upgrade in one step - for example, from SAP R/3 4.6C to SAP ERP Central Component (SAP ECC) 6.0, including SAP enhancement package 3 for SAP ERP 6.0.
6. Are enhancement packages cumulative?
Yes. Each enhancement package includes all the functionality and technology enhancements of previous packages as well as all the new enhancements contained in the current package.
7. When component X is upgraded with enhancement package 2 and component Y is upgraded with enhancement package 3, does SAP still guarantee compatibility between these components?
Enhancement packages are cumulative, so when component Y is upgraded with enhancement package 3, component X is also upgraded to the same version. This ensures compatibility of all components. The maintenance optimizer function of the SAP Solution Manager application management solution identifies the installation packages automatically according to this rule.
8. Once activated, can a business function be deactivated?
No. It is not possible to deactivate a business function.
9. Why is the SPAU transaction necessary before any switch activation, even though the software is supposedly not yet changing its behavior?
Updating software components means that new versions of development objects are brought into your software. If you have changed those objects in your software as well, you must adjust your modifications in the newly applied development object so as not to lose your changes. This is independent of any switch activation.
10. How long will SAP maintain a particular enhancement package?
SAP will maintain an enhancement package for as long as SAP maintains the release upon which the enhancement package is based.