Welcome to this SAP enhancement packages: Technology Facts presentation.

Today I would like to give you an overview about the technology and
implementation procedure of SAP enhancement packages for SAP ERP.

1
Let„s have a look at the agenda: First I will explain the concept of SAP enhancement
packages, afterwards we will take a look at the architectural aspects. In chapter
three we will get an insight into the main steps of the implementation procedure
followed by customer experience and best practices.
At the end I will summarize what we have looked at and give an outlook.

2
Customers have the need to stabilize their core systems and yet to still deliver
ongoing innovation. With the SAP enhancement package concept SAP tackles
this challenge. SAP enhancement packages represent a new software delivery
strategy that allows you to get innovations on top of SAP ERP 6.0 without the
need for fully upgrading your current release. With SAP enhancement packages,
the methodology for implementing new functionality has significantly changed.
This E-Book outlines the basic ideas of the new concept and the implementation
procedure for SAP enhancement packages for SAP ERP. Furthermore, this E-
Book links to the guides and notes that SAP provides. Getting familiar with these
procedures will help you to minimize implementation efforts.

So what are the major changes?

First of all you can now install new functionality, without any change for end-
users right at the outset. Therefore the SAP enhancement packages installation
should be performed in a normal maintenance window as part of your existing
regular Support Package Update with only minor additional effort.
Afterwards you can activate new functionality when you want to, and you know
exactly which functional changes will occur and what you have to test after the
activation of the new functionality. SAP‟s aim is to provide new functionality for
well-defined user groups without side effects for the rest.
Secondly Support Packages contain only corrections and legal changes, in case
you only want to maintain your current state SAP assures that your system will
stay stable and compliant.

3
SAP enhancement packages for SAP ERP include functional enhancements,
industry-specific enhancements and simplifications. To discover and evaluate which
innovations are shipped in which SAP enhancement package, visit the SAP
Service Marketplace.
In addition, enterprise service (ES) bundles are delivered with SAP enhancement
packages. Each ES bundle comprises a set of enterprise services to support an
end-to-end business process (for example Order to Cash) across the SAP
Business Suite. To learn which ES bundles are available and to understand the
details of the services, please refer to the Enterprise Service Wiki Pages in SDN.
From a functional perspective SAP enhancement packages are built on top of each
other: By installing the current SAP enhancement package the entire content of
earlier packages is incorporated.
SAP enhancement packages have the same maintenance duration as the
underlying core application, SAP ERP 6.0. As before, all legal changes and
corrections will be available via Support Packages. SAP provides Support
Packages for SAP ERP 6.0 on a regular basis during the defined maintenance
period and, in parallel, in the equivalent Support Packages for SAP enhancement
packages for SAP ERP. In the future, it is planned to deliver SAP enhancement
packages for other SAP applications (e.g. SAP CRM or SAP SCM) as well.

The first three generations of SAP enhancement packages for SAP ERP have
been delivered and adopted in the market. This is proven by high number of live
customers.
4
SAP enhancement packages allow you to update a subset of the software
components that are part of your SAP ERP 6.0 implementation. For example, you
are now able to update parts of your SAP ECC Server. The selection of software
components is driven by the functional enhancements that you plan to
implement. In the picture you can see how new HCM functionality is installed by
updating only EA-HR (version 602) on the SAP ECC Server. The Solution
Manager - Maintenance Optimizer automatically identifies the relevant installation
packages (potentially also including Support Packages) according to the current
system status and the chosen Technical Usage(s). As the whole procedure is
highly automated, the Maintenance Optimizer also provides a configuration file
for the installation tools.
As SAP leverages the Enhancement and Switch Framework to deliver new
functionality, the installation of an SAP enhancement package has no impact on
existing business processes or user interfaces, as long as no business function
has been activated. However SAP enhancement packages require a defined SAP
ERP Support Package Stack, including a certain level of SAP ERP and SAP
NetWeaver Support Packages. Please note: There is a SAP enhancement
package SP equivalence level. Furthermore you potentially need to perform a
modification adjustment (SPDD/SPAU). If you have modifications to the SAP
code in your system and you separate the installation of the Support Package
Stack and the installation of the SAP enhancement package into two steps, you
need to perform the modification adjustment twice (and in part for the same
objects), since SAP enhancement packages also contain corrections from the
equivalent Support Package Stacks.
5
The key difference between SAP enhancement packages for SAP ERP and
other, older technologies is the improved software lifecycle.
This is given through the selective character and the capability that no UI or
process changes take place after the installation as new functionality must be
explicitly switched on to become active in the system.
As a result the continuous provisioning of new functionality is possible with SAP
enhancement packages for SAP ERP .
Thereby companies can permanently decrease the functional gap.

6
But - How is this possible?
Since the installation process is decoupled from activation, you can now
continuously provide the newest functionality to the system along with your
regular maintenance activities. In order to use synergy effects and to minimize
effort (especially regarding potentially needed modification adjustments – see
above), SAP ERP enhancement packages should be applied within one queue,
together with the required Support Packages.
Using this strategy, SAP enhancement packages can be installed without causing
disruption as a normal maintenance activity together with Support Packages.

7
For the first time an enhancement package for SAP Netweaver will be delivered with
SAP enhancement package 4 for SAP ERP.
SAP enhancement package 4 for SAP ERP components for the SAP ECC Server 6.0
always require SAP enhancement package 1 for SAP NetWeaver 7.0. However the
deployment of SAP enhancement package 1 for SAP NetWeaver 7.0 usage types, e.g.
Portal, is in general optional.
By that customers can fully separate the new functionality in enhancement packages
and corrections in support packages. This leads to reduced efforts for testing and no
end-user training required when applying support packages.
By that adding new functionality becomes even more predictable and controllable.

8
So where is the difference between SAP enhancement packages for SAP ERP
and for SAP NetWeaver?
All in all there are a lot of similarities. The installation procedure is in both cases
efficient and fast. The installation is performed with the EHP installer based on
proven SAP software lifecycle management tools.
In both cases there is no UI or process change for end users after installation of
an enhancement package and by that the impact of Installation is limited.
Furthermore new functions are switched on selectively, either with the switch
framework or other, alternative procedure.

9
So what do live customers think about the new concept?
Firstly, they are now able to Innovate on demand, as SAP enhancement
packages provide stability and access to Innovation.
Secondly, customers are able to reduce their costs and efforts, as they were able
install functional enhancements, unnoticeably as part of existing system
maintenance. Furthermore they were able to simplify their testing with standard
SAP test case templates.

10
Let us now take a look at the architectural aspects.

11
Here you can see a brief overview about the evolution of the SAP ERP
architecture. In short:
With SAP R/3 4.6 and 4.7 (“Enterprise”) the SAP Web Application
Server (or “Basis”) based on ABAP was the foundation of the ERP
application. There was no SAP Netweaver, also the SAP industry
solutions were at that time Add-Ons on top of the application. SAP
started to support Unicode with SAP R/3 4.7.
With SAP ERP 6.0 SAP provides a solution which is built on top of SAP
Netweaver, e.g the SAP Enterprise Portal can be leveraged as a
unified UI for all applications, also the SAP Business Intelligence and
SAP Process Integration are integral parts of SAP‟s ERP solution. The
application was also enhanced tremendously, with SAP ERP nearly all
industry solutions became part of the application core plus tons of new
functionality is ready to use. You can explore the new functionality
easily with the SAP Solution Browser.

By the way, in case you plan to upgrade to ERP 6.0 you can directly
bind in SAP enhancement packages into the upgrade procedure, this is
possible since Support Release 3.

12
Now I want to sketch the architectural details of the enhancement package
concept:
[Animation 1]
Now a selective exchange of one component is possible: With SAP EHPs you
can selectively update software components. Please note that matching
combinations of software components, as well as PI/EP/BI-content and Java
software components are grouped by Technical Usages. As the number of
software components are limited, e.g. a separate installation of logistics and
financials (both are located in the core software component SAP/EA_APPL) is
not possible.
[Animation 2]
Strict separation of technical installation and the implementation of the new
functionality: Explicit activation separately for each Business Function (with EHP3
we have approximately 150 Business Functions). However only Backend
functionality (ABAP) is switchable.

13
SAP enhancement packages contain also a certain level of corrections therefore
require an equivalent Support Package Level for the Software Components which
remain on version 600.
Therefore EHPs should always be installed together with the required Support
Package Stack. As a consequence customers have to adjust possible
modifications and test the application, however this was the same with the pure
Support Package Stack installation. Efforts should be expected to be comparable
or slightly higher.

14
The Switch Framework Enables Optional Activation Of Business Functions:
With the Switch Framework, it is possible to control the activation of SAP ERP
objects. Activating a business function triggers switches, which then “influence”
the execution of the code enhancements. These switches ensure that you only
see the new functions if you have activated them. All functional changes and the
impact of an activated business function are made transparent in advance by the
documentation. Bear in mind that once a business function is activated you
cannot reverse it. Please note: The activation process starts a job in your SAP
system which automatically performs all changes in the system.

The Switch Framework is a proven concept as it was already used to retrofit

Industry Solutions in ERP 6.0.

15
Now I will give you an insight into the main steps of the implementation procedure
followed by customer experience and best practices.

16
So now we will walk through the overall procedure from a technical perspective:
1. Get information on which "Business Function" (this is the switchable unit which
is well described from a functional perspective) should be used.
2. Map the business function(s) to the corresponding Technical Usage(s) then
Check that all prerequisites are met. Then identify and download SAP
enhancement packages using SAP Solution Manager Maintenance Optimizer:
3. Activate the new functionality via the Switch Framework.

17
First of all the business expert has to select the required business functions.

The Enhancement Package Information Center is the single point of access to all
information related to a business function for the business expert.

Here you can find Presentations, Documentation, Release notes, test catalogues
and Learning Maps. The Business Function Documentation allows the user to get
to know the capabilities behind a business function and how to use them; learn
about options the business function provides; and notes which software
components are needed. Please note that each Business Function has a
technical name. This identifier is important to determine which parts of the system
needs to be updated.

18
Now you have to map the selected Business Functions to the required Technical
Usages.
If someone tells you to install the whole SAP enhancement package, please ask
which Business Function(s) he or she wants to use, as it is not reasonable to
install the "complete" SAP enhancement package (For example: The complete
bill of material includes ABAP and Java software components as well as SAP
BI/EP/PI content..).
You can find the complete list of Business Functions as well as the mapping to
processes and scenarios in the Service Marketplace.
Please remember: SAP enhancement packages are a delta shipment for SAP
ERP 6.0, so please check if additional technical components (e.g. Trex) are
required. You find more information about this in the release notes,
documentation and the Master Guide.

19
Once you have the names of the required Business Functions, you have to find
out the software components you need. Besides ABAP software components,
you might need to update Java components, portal content, or XI content as well.
To help you ensure consistency, we have bundled ABAP components, Java
components, portal content, and XI content as "Technical Usages.“

Now it is time to introduce some new technical terms.

 A Technical Usage bundles a number of Business Functions and instances
and components that are needed to make a particular Business Function work. It
synchronizes the changes over the different stacks and components. For
example some change in an ECC core component may need additional Portal
and XI content. New Business Functions are mapped to technical usages by a
note or documentation A technical usage contains all components that have to
be installed in the instances so that you can use a Business Function. This TU (at
the top) needs only new portal content and EA HR_602. There are other technical
usages needing Java components, XI- or BI content.
 The mapping is done with the help of a SAP note. You will find all specific
information in the SAP enhancement package master guide.

20
 Let's assume the customer wants to install the Business Function: HCM,
Administrative Services.
 We can easily see in the mapping note (step 2) that the Technical Usage:
HCM - Administrative Services must be installed.
The Technical Usage "HCM, Administrative Services" contains EA-HR
602 and Portal Content: BP for HR Admin.
For this the correct target stack (equivalence) would be the following:
SAP ERP 6.0 - Support Package Stack 14 is equivalent to SAP
enhancement package 3 –Support Package Stack 3. Both are based on
SAP Netweaver 7.0 - Support Package Stack 17.

21 21
First you have to bring your SAP Solution Manager up-to-date.
In order to use the Maintenance Optimizer application, you need SAP Solution
Manager 4.0 with the highest support package level in your system landscape.
Your system landscape has to be maintained in the Solution Manager system.
You can find more information about the SAP Solution Manager at help.sap.com
> SAP Solutions > SAP Solution Manager.
Please make also sure that you have installed the latest SPAM/SAINT update in
your system.
Secondly, as you need a certain Support Package level in your system let the
Solution Manager Maintenance Optimizer calculate the needed (and equivalent)
Support Packages for you. They can be included in the installation queue - the
details are explained in the next step.

Thirdly please note that if you have an add-on installed in your system, ask your
add-on provider whether it is compatible with the SAP enhancement package for
SAP ERP 6.0. See SAP note 1117309 for details of add-ons delivered by SAP.
Fourthly read the documentation and the referenced notes to check that all other
prerequisites are met.

22
Now we identify and download SAP enhancement packages using SAP Solution
Manager Maintenance Optimizer.

23
If you use the SAP Solution Manager Maintenance Optimizer - as strongly
recommended and already required for downloading Support Packages in general -
you only need the name of the Technical Usage to install all needed software
components. Based on that information, the SAP Solution Manager Maintenance
Optimizer calculates the needed software components and Support Packages
automatically. Create a new maintenance transaction for updating your system with
SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you
through the preparation process for updating your systems. Select all systems that
are affected by the application of the SAP enhancement package. In the next step
of the guided procedure, you select the Technical Usages you want to apply to your
systems. The Solution Manager Maintenance Optimizer automatically calculates all
needed Support Packages and new software component versions needed for
installing the previously selected Technical Usages. As a result, the Solution
Manager Maintenance Optimizer creates the Stack-XML file that can be read by
the installation tools to create a valid import queue. You can find further information
about the Solution Manager Maintenance Optimizer at service.sap.com/solman-
mopz, detailed documentation at help.sap.com > SAP Solution Manager > (select
your preferred language) in the "Change Management" section.
Please remember: The software components of SAP enhancement packages for
SAP ERP 6.0 contain new developments (as we partially replace existing software
components). Therefore, if you take a look at your system after applying the SAP
enhancement package software components, you will find software components in
version 600 (e.g. with Support Package level 10) as well as software components
in version 602 (e.g. SAP enhancement package 2 with Support Package level 0
which contains equivalent corrections to SP level 10 of the same component in
version 600).
24
Here I have illustrated the use of the stack XML to feed the actual installation
tools. The SAP Solution Manager creates a customer specific stack XML which
contains the information about the queue of selected support and enhancement
packages.
Now the installation tools use this information to bring the specific system to a
well-definied and consistent system state.

25
In the next step I will introduce the actual installation tools.

26
Install the required Support Package Stack and include all selected parts of the
SAP enhancement package. The tool to use for installation depends on the type
of software component:
 ABAP and Java software components are installed using the SAP
enhancement packages installer with minimal downtime as of SAP enhancement
package 4.
 Portal Content is installed using the JSPM tool
 XI Content is usually uploaded from within the Integration Repository, which is
part of usage type Process Integration (PI) of SAP NetWeaver.
 BI Content is applied as common Support Packages.

Alternatively ABAP components can be installed using the SAINT tool and Java
software components can be are installed using the JSPM tool.
Please note that there might be limitations.

27
Here you can see how the installation of a SAP enhancement package is
performed using transation SAINT.

28
Here you can see how the installation of a SAP enhancement package is
performed using JSPM.

29
As of SAP enhancement package 4 ABAP and Java software components are
installed using the SAP enhancement packages installer with minimal downtime.

30
Here the basic principle of the SAP enhancement package installer is explained.
The SAP Enhancement Package Installer uses a system cloning and switch
procedure. This procedure installs a copy of the system, the shadow system, in
parallel to the original system. The shadow system is used to update the affected
software components and to install the additional components, while the original
system is still in production operation.
For further information please read the EHP Installer documentation.

31
SAP TechEd 08

The installation of an enhancement packages with SAPehpi is performed with

minimized downtime. The point of no-return is reached significantly later in the
installation process and not before checks have been run successfully
by the tool. This means you get a smooth and safe update.
As you can see in the graphic the expected downtime is reduced by 77 %, further
information will be published soon via the EHP experience database.

32
From a system landscape or project perspective please keep in mind that all
activities must be performed in the "normal" sequence, for example:
a) Setup sandbox, perform Installation/Update (enhancement packages/support
package stack) and get familiar with the new functionality
b) Setup temporary maintenance system for the EhP installation project (for
emergency corrections), as it is generally not recommended to transport
between systems with different structure (e.g. 600 -> 603, this is also true for
systems with different activated Business Functions)
c) Perform installation in DEV (development system), perform modification
adjustment, etc.
d) Perform installation in QAS (quality assurance system), perform integration
test, etc.
e) Perform installation in PRD (productive system) & Go-Live/Support
In general you should have most of the procedures already in place, as most
customers regularly implement Support Package Stacks.

33
In the next step we will activate parts of the newly installed functionality.

34
The switch transaction shows all the business functions that can now be
activated after the installation of the new software components.
In the switch framework transaction you can:
View the list of business functions available with the latest system setup
Access documentation, release notes, test catalogue, and possible
dependencies
Install the relevant documentation, refer to SAP note 1066110
Before the activation you get transparency of all system and UI changes that will
take place.
Afterwards you can activate the chosen business functions and perform the
configuration tasks.
By that the new coding becomes effective. All other parts of the system remain
stable.

35
Test case templates will be available for each business function that is new to an
enhancement package.
These templates can be called directly from the switch transaction. The link to the
corresponding test case is located right next to each business functions.
The SAP test case templates help you to plan and perform your acceptance test
and train your end users for the selected business functions.
By that you are also able to narrow down the test scope because functional
changes are documented for each business function.

So - where to find Test Case Templates?

Firstly before installing EHP in SAP Service Marketplace. All test cases are
available as documents in the enhancement package information center and can
be downloaded.
Secondly after installing EHP via the switch framework. Test cases are shipped
with the enhancement package and are part of the installation (SAP ECC). From
there, you will (by drilldown) enter the test workbench. Test cases can be
transported to SAP Solution Manager via workbench request.

36
So here are the recommendations on implementation procedure of SAP
enhancement packages.
1. Discovery
Use Sandbox System to explore new functions as Business Functions are not
reversible.
2. Installation tactics
Always combine the installation of enhancement package with the installation
of the latest Support Package Stack (ABAP). However there are exceptions:
Pay attention especially in mixed environments: ABAP/JAVA, e.g. LSO.
With new tool, the EhP Installer, the minimization of downtime is possible.
3. Preparation
Read the documentation: The principles and methods to install SAP
enhancement packages differ significantly from a traditional release upgrade.
Make sure your SAP Solution Manager 4.0 is at the latest patch level (SAP
Note 1122966).

37
I will now share with you some customer feedback from the last SAP
enhancement package ramp-up:
The Installation was perceived as smooth and straight forward. In general it took
less time than expected. The Implementation turned out to be much simpler than
customers expected. There were large effort savings if compared with upgrades,
e.g. one customer stated: „We were 3 times faster than in our upgrade project.‟
Finally the Business Function Concept was well received. The System behaviour
indeed only changed where a business function was activated and no side effects
noticed. Capsulation of business functions using the Switch Framework works
very well.

38
Finally I will summarize and give an outlook.

39
Here are the key take aways:
1. With SAP enhancement packages there is a clear separation of new
functionality in enhancement packages and patches in Support Packages.
2. Now a targeted update of existing software components is possible: Mixed
software component versions are allowed within one system. You have to
select the required parts of the chosen EHP.
3. Know your Scope - Architecture of SAP enhancement packages allow a
phased approach:
Install SAP enhancement packages combined with Support Packages as
a maintenance activity with minor additional effort (ABAP). In case you
implement Java components be aware of changes in the procedure.
Followed by the activation of Business Function(s) and the
implementation of new functionality
4. There is a direct upgrade path available from previous SAP R/3 releases to
SAP enhancement package 3 for ERP 6.0.

40
Outlook:
Deploying business innovation with SAP enhancement packages across the
entire SAP Business Suite and accelerated innovation.

41
The central starting to point to get further information about SAP enhancement
packages is the SAP enhancement package information center.
You can access it in the SAP Service Marketplace via the Quicklink: ERP-EHP.
There you will find for example the EHP FAQ document, the EHP Must Know
Guide and get direct access to the EHP forum and the Wiki pages.

42
Thank you for attending this presentation.
In case you have any questions just drop me a mail.

43
44