Mast er Gui de

SAP f or Oi l & Gas

SAP f or Mi ni ng
SAP Busi ness Sui t e 7
I nnovat i ons 2010
Doc ument Ver si on 1.00 J ul y 2010
2
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,
Tivoli, and Informix are trademarks or registered trademarks of IBM
Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered
trademarks of W3C

, World Wide Web Consortium, Massachusetts

Institute of Technology.
J ava is a registered trademark of Sun Microsystems, Inc.
J avaScript is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and
other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves
informational purposes only. National product specifications may
vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional
warranty.
SAP Library document classification: PUBLIC
Disclaimer
Some components of this product are based on Java. Any code
change in these components may cause unpredictable and severe
malfunctions and is therefore expressively prohibited, as is any
decompilation of these components.
Any J ava Source Code delivered with this product is only to be used
by SAPs Support Services and may not be modified or altered in any
way.
Documentation in the SAP Service Marketplace
You can find this documentation at the following Internet address:
service.sap.com/instguides
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.c om
3
Typographi c Convent i ons
Type Style Represents
Example Text Words or characters that appear
on the screen. These include
field names, screen titles,
pushbuttons as well as menu
names, paths and options.
Cross-references to other
documentation
Example text Emphasized words or phrases in
body text, titles of graphics and
tables
EXAMPLE TEXT Names of elements in the
system. These include report
names, program names,
transaction codes, table names,
and individual key words of a
programming language, when
surrounded by body text, for
example, SELECT and
INCLUDE.
Example text Screen output. This includes file
and directory names and their
paths, messages, names of
variables and parameters,
source code as well as names of
installation, upgrade and
database tools.
Exampl e t ext Exact user entry. These are
words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Exampl e t ext > Variable user entry. Pointed
brackets indicate that you
replace these words and
characters with appropriate
entries.
EXAMPLE TEXT
Keys on the keyboard, for
example, function keys (such as
F2) or the ENTER key.
I c ons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Contents
4
Contents
SAP for Oil & Gas / SAP for Mining ....................................................................................... 5
History of Changes ............................................................................................................ 6
Getting Started ...................................................................................................................... 7
Related Information ........................................................................................................... 8
Related Guides .................................................................................................................. 9
SAP Solution Manager ...................................................................................................... 9
Important SAP Notes ....................................................................................................... 10
Business Scenarios of SAP for Oil & Gas ............................................................................ 11
Production and Revenue Accounting ............................................................................... 11
Business Scenarios of SAP for Mining................................................................................. 14
Commodity Transport Management ................................................................................. 14
SAP Enhancement Package Concept ................................................................................. 17
Enhancement Package Key Concept ............................................................................... 17
Key Facts About Enhancement Packages ....................................................................... 18
Enhancement Package Implementation ........................................................................... 20
The Main SAP Documentation Types .................................................................................. 23
SAP for Oil & Gas / SAP for Mining
5
SAP for Oil & Gas / SAP for Mining
SAP for Oil & Gas meets the special demands and requirements of the oil and gas industry,
for example supports marketing and sales-oriented activities, sales and distribution and
storage. SAP for Oil & Gas can also be used in the areas of production (refineries).
SAP for Mining supports companies to run the following key business processes in the
mining industry:
Contract-to-cash (for example, commodity pricing, provisional/adjustment invoicing)
Bulk transportation (for example, scheduling, nominating and ticketing of transports,
inventory projection)
Operations management (for example, handling of mining operations and maintenance
costs, capture of all relevant data on mined and processed ore, keeping track of all the
equipment used during mining processes)
Secondary processing (for example, management of cost through the entire supply chain,
management of distribution processes)
This Master Guide provides a central starting point for the technical implementation of the
following business scenarios of SAP for Oil & Gas andSAP for Mining:
Production and Revenue Accounting (page 11)
Commodity Transport Management (page 14)
You can find an overview about the whole functionality of SAP for Oil & Gas and
SAP for Mining in the solution map: service.sap.com/bmet SAP
Business Maps Industry-Specific Maps Oil & Gas or Mining.
The business scenarios that are presented here serve as examples of how you
can use SAP software in your company. The business scenarios are only
intended as models and do not necessarily run the way they are described here
in your customer-specific system landscape. Make sure that you check your
requirements and systems to determine whether these scenarios can be used
productively at your site. Furthermore, we recommend that you test these
scenarios thoroughly in your test systems to ensure they are complete and free
of errors before going live.
This Master Guide provides just one way to implement each business scenario.
For other ways to implement business scenarios, see the Scenario Component
List Viewer in SAP Service Marketplace (service.sap.com/scl).
SAP for Oil & Gas / SAP for Mining
History of Changes
6
History of Changes
The Master Guide is updated on a regular basis in SAP Service Marketplace at:
service.sap.com/instguides
Make sure you have the latest version of the Master Guide by checking SAP
Service Marketplace right before the installation.
The following table provides an overview of the most important changes that were made to
the latest versions.
Master Guide Versi on Important Changes
1.00 (J uly 2010)
Getting Started
Further Scenario Informati on
7
Getting Started
This Master Guide provides information about the components and guides which are required
during the implementation of the business scenarios.
Getting Started (page 6) contains valuable information about using this document and
related information (documentation and SAP Notes) crucial to the installation and
upgrade.
The Business Scenarios of SAP for Oil & Gas (page 11) and Business Scenarios of SAP
for Mining (page 14) contain the following information for each business scenario:
A short overview about the business scenario
Minimal system landscape
A software component matrix for each business scenario that provides information
about which components the business scenario uses and if the corresponding
component is mandatory or optional.
References to further information about the business scenario
You can find the most current information about the technical implementation of
SAP for Oil & Gas and SAP for Mining and the latest installation and
configuration guides on the SAP Service Marketplace under
service.sap.com/instguides.
We strongly recommend that you use the documents available here. The guides
are regularly updated.
Further Scenario Information
In addition to the information provided in this Master Guide, you can find more information on
the SAP Service Marketplace:
Scenario Description
The scenario description is part of SAP Solution Manager implementation content.
For more information about SAP Solution Manager, see
service.sap.com/solutionmanager.
Configuration Documentation
The configuration documentation is part of SAP Solution Manager implementation
content. For more information about SAP Solution Manager, see
service.sap.com/solutionmanager.
Getting Started
Related Information
8
Related Information
The following table contains links to crucial information for implementing this solution.
List of Related Documentation
Content Location
Information about technical and release
planning issues on SAP components
service.sap.com/pam
Information about the latest version of
installation and upgrade guides for SAP
components
service.sap.com/instguides
Information about SAP Notes service.sap.com/notes
Information about released platforms service.sap.com/platforms
Information about sizing and calculation of
hardware requirements (such as CPU, disk,
and memory resource) with the Quick Sizer
tool
service.sap.com/sizing
Information about network security SAP
Security Guide
service.sap.com/securityguide
Information about high availability service.sap.com/ha
Information about creating error messages service.sap.com/message
Performance service.sap.com/performance
Documentation on SAP Help Portal help.sap.com/
Getting Started
Related Guides
9
Related Guides
This Master Guide is based on Component Master Guides. The documents listed below
contain detailed information about the relevant components:
List of Related Master Guides
Content Location
SAP NetWeaver 7.0 service.sap.com/installNW70
SAP ERP 6.0 service.sap.com/erp-inst SAP ERP
6.0 Planning
SAP Enhancement Packages for SAP ERP
6.0
service.sap.com/erp-inst SAP ERP
6.0 SAP enhancement packages for SAP
ERP 6.0
Consider that there are several documents available to support the installation
of your product and its enhancement packages:
Master Guide
Installation Guide
Installation Guide: SAP Enhancement Package Installation Using SAP
Enhancement Package Installer (SAPehpi) 7.02
Troubleshooting and Administration for Installations Using SAPehpi
(ABAP)
Troubleshooting for Installations Using SAPehpi (J ava)
Practical Guide for How to Install SAP Enhancement Packages
You can find all these guides on SAP Service Marketplace under
service.sap.com/instguides where the installation guides of your
products are located.
SAP Solution Manager
SAP provides the SAP Solution Manager as the highly recommended platform to efficiently
support the implementation of your solution. Using SAP Solution Manager significantly
accelerates the implementation process and helps you to achieve your business goals. At the
same time, SAP can deliver Support Services based on the business scenarios designed and
documented in SAP Solution Manager. Implementation content for your solution may further
accelerate the implementation process. For information about availability of content
specifically tailored to your solution, see SAP Service Marketplace under
service.sap.com/solutionmanager.
Getting Started
Important SAP Notes
10
Important SAP Notes
This section contains important SAP Notes for SAP for Oil & Gas and SAP for Mining.
Read the installation SAP Notes before beginning the installation. These contain
the most recent information regarding the installation, as well as changes to the
installation documentation.
Make sure that you have the most recent version of each SAP Note. They are
located on SAP Service Marketplace (service.sap.com/notes).
Li st of Related SAP Notes
SAP Note Title Descripti on
417380 Release strategy IS-MIN
883774 Release strategy for IS-OIL/IS-
MIN as of SAP ECC 6.0
619057 QCI: External function calls
using the CALL System
Information about the quantity conversion
interface (QCI)
Business Scenarios of SAP for Oil & Gas
Production and Revenue Accounting
11
Business Scenarios of SAP for Oil & Gas
Production and Revenue Accounting
Overview
You can use this business scenario to create and process data for compliance reporting,
product balancing, and revenue accounting. This business scenario defines the required
setup for the following:
Use compliance reports
Perform product balancing
Accomplish various valuation tasks
Execute settlement statement value and posting
Process accounts receivable
Technical System Landscape
The following figure provides an overview of a possible system landscape for Production and
Revenue Accounting.
ERP Server
SAP Enhancement Package 5
for SAP ERP 6.0 SAP ECC
Server
XI Server (optional)
SAP NetWeaver 7.0
UsageType
ProcessIntegration
Portal Server (optional)
SAP NetWeaver 7.0
UsageType EP
The following software components are either mandatory or optional, as indicated below, for
the technical implementation of Production and Revenue Accounting.
Component Mandatory Optional
Business Scenarios of SAP for Oil & Gas
Production and Revenue Accounting
12
SAP Enhancement Package 5 for SAP ERP 6.0 SAP ECC Server
Technical Usage: Oil & Gas
X
SAP NetWeaver 7.0
UsageType Process Integration
X
SAP NetWeaver 7.0
Usage Type Enterprise Portal
X
Installation Sequence
The following table provides the installation sequence:
ERP Server
1 Installation of SAP ERP 6.0
SAP ECC Server
For detailed information, see
service.sap.com/erp-inst SAP ERP
SAP ERP 6.0 Planning.
2 Installation of SAP Enhancement
Package 5 for SAP ERP 6.0
SAP ECC Server
Technical Usage: Oil & Gas
For detailed information, see
service.sap.com/erp-inst SAP
ERP SAP ERP 6.0 SAP enhancement
packages for SAP ERP 6.0.
3 Activation of the SAP Oil & Gas
business function set
In Customizing for SAP Customizing
Implementation Guide, choose Activate SAP
ECC Extensions to activate the business
function set and the business function.
4 Activation of the Upstream
Production Management
(OIL_PRODUCTION) business
function
Activation of the Upstream
Revenue Accounting
(OIL_REVENUE_ACCOUNTING)
business function
Activation of the Production
Management and Revenue
Accounting Extended Features
(OIL_PRA_CI_1) business
function
5 Installation of External
Conversion Routines for the
Quanti ty Conversion Interface
(QCI)
For detailed information, see SAP Note
619057.
Business Scenarios of SAP for Oil & Gas
Production and Revenue Accounting
13
SAP NetWeaver XI Server (Optional)
1 Installation of SAP NetWeaver 7.0
Usage Type Process Integration
For detailed information, see
service.sap.com/instguidesNW70
SAP NetWeaver Portal Server (Optional)
1 Installation of SAP NetWeaver 7.0
Usage Type EP
For detailed information, see
service.sap.com/instguidesNW70
Business Scenarios of SAP for Mining
Commodity Transport Management
14
Business Scenarios of SAP for Mining
Commodity Transport Management
Overview
The purpose of this scenario is to schedule commodity bulk transports in dynamic scheduling
and publish the schedule as nomination within dynamic scheduling. You can complete the
information later by maintaining additional data in the nomination. Ticketing is executing the
transport as soon as the vehicle has been loaded.
Beforehand you can maintain a freight liner offer as a special type of a nomination. The
freight liner offer contains information about the stages and arrival and departure times of a
vehicle as well as the validity date.
This information is available for the transportation planner in dynamic scheduling.
Technical System Landscape
The following figure provides an overview of a possible system landscape for Commodity
Transport Management.
ERP Server
SAP Enhancement Package4
or5 for SAP ERP 6.0 SAP ECC
Server
Portal Server
Business Packagefor
Transportation Planner1.4
SAP NetWeaver 7.0
UsageType EP
The following software components are either mandatory or optional, as indicated below, for
the technical implementation of Commodity Transport Management.
Component Mandatory Optional
Business Scenarios of SAP for Mining
Commodity Transport Management
15
SAP Enhancement Package 4 for SAP ERP 6.0 SAP ECC Server
Technical Usage: Oil & Gas
Or
SAP Enhancement Package 5 for SAP ERP 6.0 SAP ECC Server
Technical Usage: Oil & Gas
X
X
SAP NetWeaver 7.0
Usage Type Enterprise Portal (EP)
X
Installation Sequence
The following table describes the installation sequence for Commodity Transport
Management.
ERP Server (Option 1)
1 Installation of SAP ERP 6.0 SAP ECC
Server
For detailed information, see
service.sap.com/erp-inst
SAP ERP SAP ERP 6.0
Planning.
2 Installation of SAP Enhancement Package 4
for SAP ERP 6.0 ECC Server
Technical Usage: Oil & Gas
Or
Installation of SAP Enhancement Package 5
for SAP ERP 6.0 SAP ECC Server
Technical Usage: Oil & Gas
For detailed information, see
service.sap.com/erp-inst
SAP ERP SAP ERP 6.0 SAP
enhancement packages for SAP
ERP 6.0.
3 Activation of the SAP Oil & Gas business
function set or SAP Mining business
function set
In Customizing for SAP Customizing
Implementation Guide, choose
Activate SAP ECC Extensions to
activate the business function set
and the business function.
4 Activation of the Commodi ty Management
and Bulk Transports 2
(LOG_COMMODITY_TRANSPORT_MGMT_4)
business function
Or
Activation of the Commodi ty Management
and Bulk Transports 3
(LOG_COMMODITY_TRANSPORT_MGMT_5)
business function (optional)
Business Scenarios of SAP for Mining
Commodity Transport Management
16
ERP Server (Option 2)
1 Installation of SAP ERP 6.0 SAP ECC
Server
For detailed information, see
service.sap.com/instguides
SAP ERP SAP ERP 6.0
Planning.
2 Installation of SAP Enhancement Package 5
for SAP ERP 6.0 SAP ECC Server
Technical Usage: Oil & Gas
For detailed information, see
service.sap.com/erp-inst
SAP ERP SAP ERP 6.0 SAP
enhancement packages for SAP ERP
6.0.
3 Activation of the Traders and Schedul ers
Workbench (LOG_TSW_ECC) business
function
SAP NetWeaver Portal Server
1 Installation of SAP NetWeaver 7.0 SP15 or
higher, Usage Type EP
For detailed information, see
service.sap.com/instguidesNW70
2 Installation of Business Package for
Transportation Pl anner 1.4
3 Assignment of the Transportation Planner
role to relevant users
SAP Enhancement Package Concept
Enhancement Package Key Concept
17
SAP Enhancement Package Concept
Enhancement Package Key Concept
We have adapted our major release strategy to better fit your adoption cycle. To ensure that
you benefit from new developments and innovations while minimizing the impact on your core
operational systems, SAP uses enhancement packages to speed up the delivery of new
functions.
With SAP enhancement packages, you can install and activate new functions depending on
your business needs without having to perform a system upgrade.
You can selectively implement the new functions and activate the software upon business
demand. As a result, you can isolate the impact of software updates and make new functions
available faster due to shortened test cycles.
Implementation
There are three different scenarios to implement an enhancement package:
Installation of an enhancement package on an existing SAP system
New installation of an SAP system including an enhancement package
Upgrade of an SAP system including an enhancement package
The installation process of enhancement packages consists of two different steps:
Technical installation of an enhancement package
Activation of new functions using the switch framework technology
You have a choice on both levels installation and activation. You do not need to install a full
enhancement package. Instead, you can update the software components that are related to
the functional enhancements you want to use.
From a business point of view, functional enhancements are grouped into business functions
(BFs). The technical installation of the business functions does not change the system
behavior. The new functions are available in the system, but are not active. After the
installation, no user interface or process change takes place. You must explicitly activate new
functions so that they become visible in the system. As a result, changes are predictable and
there are no side effects as only the activated areas change.
With the switch framework technology (transaction SFW5), it is possible to control the
activation of new SAP objects in ABAP-based SAP systems. The activation process triggers
a background job that automatically performs all changes in the SAP system.
You cannot reverse a business function once it is activated.
After you have activated a business function, you can see the changes and new
developments in the SAP system, for example:
Menu entries
New screens
New fields on the application user interfaces
IMG activities required for the implementation
SAP Enhancement Package Concept
Key Facts About Enhancement Packages
18
New table entries in Customizing tables and system tables
You can create a transport request with the current settings of the switch framework. You can
check functional changes and the impact of an activated business function in advance in the
business function documentation.
Test the installation and activation on a sandbox system.
Maintenance
SAP enhancement packages have Support Packages of their own that are equivalent to the
Support Package versions of the underlying SAP system. You must install the enhancement
package in combination with the latest available Support Package stack. This approach
reduces installation, modification adjustment, and testing effort. Using this strategy, you can
install SAP enhancement packages as a normal maintenance activity together with Support
Package stacks.
An enhancement package requires a specific Support Package stack level in the source
release SAP system. If the SAP system is on a lower Support Package stack level, all
relevant Support Package stacks are automatically included into the download queue, as well
as the latest available Support Packages for the enhancement package.
Tools
The enhancement package installation requires the following tools:
SAP Solution Manager Maintenance Optimizer
Installation or upgrade tools (depending on your scenario)
The SAP Solution Manager Maintenance Optimizer (accessible from the Change
Management work center) supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages. In addition, SAP Solution
Manager calculates a valid import queue for the selected SAP system and generates the
enhancement package stack configuration file that you require for the installation.
For the new installation of an SAP system including enhancement package as well as for the
upgrade of an SAP system to a higher release including an enhancement package, you use
the standard installation and upgrade tools (SAPinst, SAPup and SAPJ up). To install an
enhancement package on an existing SAP system, you use the SAP Enhancement Package
Installer (SAPehpi). It allows enhancement packages to be installed with reduced downtime.
SAPehpi uses the shadow system installation strategy, a well-known feature in the upgrade
technology.
Key Facts About Enhancement Packages
The following list summarizes important facts about the enhancement package concept and
recommended approaches:
Install only selected parts of the enhancement package. The selection is driven by
the functional need from a business point of view.
You cannot mix the installation of different enhancement package versions in your
ABAP-based SAP system. You can have just one enhancement package version in
the SAP system.
SAP Enhancement Package Concept
Key Facts About Enhancement Packages
19
SAP enhancement packages are cumulative, meaning that each new enhancement
package includes new innovations of its own as well as all innovations delivered with
prior packages.
We recommend installing the latest available enhancement package version.
Install enhancement packages and Support Packages in one single step (this
includes the preconditioned Support Packages).
SAP enhancement packages have Support Packages of their own that are equivalent
to the Support Package versions of the underlying SAP system.
SAP enhancement packages have the same maintenance period as the underlying
core application.
The installation of an enhancement package is irreversible.
As long as you do not activate a business function, the installation of an
enhancement package has no impact on existing business processes or user
interfaces.
You can only activate business functions in ABAP-based systems, not in J ava-based
SAP systems.
The activation of most business functions and extension sets is irreversible. Only a
small number of business functions is reversible.
Test the installation process and activation of new functions in advance on a sandbox
system. Ensure that you evaluate the runtime and the SAP system behavior, its
dependencies and impacts. Make sure that your SAP system is free of errors before
going live.
SAP Enhancement Package Concept
Enhancement Package Implementation
20
Enhancement Package Implementation
In the following, you will find an overview of the steps involved in the three different
enhancement package implementation scenarios.
Process
Enhancement Package Installation in an Exi sting SAP System
1. You find out, which of the new functions are interesting for your business.
2. You analyze the landscape dependencies.
3. You identify the relevant installable parts of the enhancement package.
4. You make sure that you have set up your SAP Solution Manager system for the
download of packages, and that you have configured the Maintenance Optimizer.
5. You download the installation queue.
6. You perform the installation.
7. You analyze the impact of the business function activation with the dependency
analyzer and the impact analyzer (transaction SWF5).
8. You activate the business functions.
9. You perform additional Customizing, if necessary.
10. You test the new functions.
Tools
SAP Solution Manager Maintenance Optimizer (mandatory)
SAP Enhancement Package Installer (SAPehpi)
Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution
Manager (transaction SWF5)
New Installation of an SAP System with Enhancement Packages
Process
1. You install the SAP system.
The installation of SAP ERP 6.0 including enhancement package 5 comprises the
technical usage Central Applications. The installation of the technical usage Central
Applications implies that the system is ready for use without installing any further
technical usages. Of course, you can optionally install additional technical usages.
2. If you want to install further technical usages:
a. You identify the relevant installable parts of the enhancement package.
b. You make sure that you have set up your SAP Solution Manager system for
the download of packages, and that you have configured the Maintenance
Optimizer.
c. You download the installation queue.
d. You perform the installation.
e. You activate the business functions using the switch framework (transaction
SWF5).
SAP Enhancement Package Concept
Enhancement Package Implementation
21
3. You perform the Customizing for the SAP system.
4. You test the SAP system.
Tools
Standard Installation tool SAPinst
SAPehpi or SAINT to install additional technical usages
In this scenario, you can use transaction SAINT for installing additional technical
usages, because software component SAP_APPL 6.05 is already present in your
system (part of technical usage Central Applications). This is a prerequisite for using
SAINT.
Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution
Manager (transaction SWF5)
Upgrade to an SAP System Including an Enhancement Package
Installation
Customers who are upgrading from a lower release to an SAP system for which
enhancement packages are available can include parts of enhancement packages into the
upgrade process.
The use of SAP Solution Manager Maintenance Optimizer is mandatory if you want
to include enhancement packages in your release upgrade.
Process
1. You plan the upgrade to the new release. Decide which parts of the enhancement
package you want to include into the upgrade procedure before you start with the
upgrade.
2. You identify the relevant installable parts of the enhancement package.
3. You make sure that you have set up your SAP Solution Manager system for the
download of packages, and that you have configured the Maintenance Optimizer.
4. You download the required parts of enhancement packages and Support Packages
as well as the enhancement package stack configuration file.
5. You perform the upgrade including parts of the enhancement package.
The upgrade program asks if you want to include parts of an enhancement package
into the upgrade process.
6. You activate the business functions using the switch framework (transaction SWF5).
7. You perform the delta Customizing for the SAP system.
8. You test the SAP system.
Tools
Standard upgrade tools (SAPup and SAPJ up)
SAP Enhancement Package Concept
22
SAP Solution Manager Maintenance Optimizer
The Main SAP Documentation Types
23
The Main SAP Documentation Types
Several documents have been created to assist you in installing, implementing, operating and
upgrading your SAP solutions. The Solution Master Guide is the first document you obtain.
Although strongly related to each other, the different documentation types help you solve
problems at different levels in different solution phases. The following figure shows an
overview of the most i mportant documentation types that you need in the various phases in
the life cycle of an SAP solution.
Documentation types in the software life cycle
Implementati on Implementati on
Master Gui de
Configuration
Documentation
Release Notes
Component
Installati on Guide
Component
Upgrade Gui de
Upgrade Master Guide
Operati on Operati on Upgrade Upgrade
Solution Management
Gui de
Implementati on Guide (IMG) Delta and Upgrade IMG
Security Guide
SAP Library
SAPterm
Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30
languages, as well as many definitions and glossary entries in English and German. The
current version is located in the SAP Help Portal at help.sap.com Additional Information
Glossary (direct access) or Terminology (as terminology CD). In the SAP system, use
Transaction STERM.
The SAP Library is a collection of function- and process-oriented documentation for SAP
components. It is located on SAP Help Portal at help.sap.com.
The Implementation Guide (IMG) is a tool used to configure the SAP system to meet
customer requirements. Its structure and documentation are component-oriented. It is located
in the SAP Easy Access menu of the SAP system under Tools Customizing IMG.
The Security Guide describes the settings for a medium security level and offers
suggestions for raising security levels. A collective security guide is available for SAP
NetWeaver. This document contains general guidelines and suggestions about system
security. Other technologies and individual applications have a Security Guide of their own.
The current version of the Security Guide is located on SAP Service Marketplace at
service.sap.com/securityguide.
The Main SAP Documentation Types
24
Implementation
The Component Installation Guide describes the technical implementation of an SAP
component, taking into account the combinations of operating systems and databases. It
does not describe any business-related configuration. You can find the Component
Installation Guides for the different components on SAP Service Marketplace at
service.sap.com/instguides.
The Configuration Documentation is contained in the SAP Solution Manager. SAP Solution
Manager is a tool with various functions, one of its main functions being the configuration of
SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as
well as documentation.
Production Operation
The Solution Operations Guide is the starting point for operating an SAP solution. The
guide refers users to the tools and documentation needed to carry out various tasks, such as
monitoring, backup/restore, master data maintenance, transports, and tests. It also refers
users to other documents, for example the SAP Library, the Master Guide, and the
Component Management Guides. The current version is located on SAP Service
Marketplace at service.sap.com/instguides.
Upgrade
The Upgrade Master Gui de is the starting point for upgrading the Business Scenarios of an
SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-
up of an upgrade. It also refers to other documents, such as the Component Upgrade Guides
and SAP Notes. Instead of an Upgrade Master Guide, there may be several Business
Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the Business
Scenarios of an SAP solution. The current version is located on SAP Service Marketplace at
service.sap.com/instguides.
The Component Upgrade Guide describes the technical upgrade of an SAP component,
taking into account the combinations of operating systems and databases. It does not
describe any business-related configuration. The current version is located in the SAP
Service Marketplace at service.sap.com/instguides.
Release notes are documents that contain short descriptions of new features or changes in
an SAP component since the previous release. Release notes about ABAP developments
enable the SAP system to generate delta and upgrade IMGs. The current version is located
on SAP Service Marketplace at service.sap.com/releasenotes or in the SAP Easy
Access menu of the SAP system under Help Release information.