SAP ECO1

Master Guide

SAP for Engineering,Construction andOperationsSAP Business Suite 7Innovations 2010

Document Version 1.00 – July 2010

2

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks 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 IBMCorporation 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 theOpen Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder 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, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

SAP Library document classification: PUBLIC

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internet address:

service.sap.com/instguides

SAP AG

Dietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20

www.sap.com

3

Typographic ConventionsType Style Represents

Example Text Words or characters that appearon the screen. These includefield names, screen titles,pushbuttons as well as menunames, paths and options.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, titles of graphics andtables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, table names,and individual key words of aprogramming language, whensurrounded by body text, forexample, SELECT andINCLUDE.

Example text Screen output. This includes fileand directory names and theirpaths, messages, names ofvariables and parameters,source code as well as names ofinstallation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (such asF2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents

4

ContentsSAP for Engineering, Construction & Operations ................................................................... 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 Engineering, Construction and Operations .......................... 11

Contract Management ..................................................................................................... 11

Subcontractor Management ............................................................................................. 13

SAP Enhancement Package Concept ................................................................................. 15

Enhancement Package Key Concept ............................................................................... 15

Key Facts About Enhancement Packages ....................................................................... 16

Enhancement Package Implementation ........................................................................... 18

The Main SAP Documentation Types .................................................................................. 20

SAP for Engineering, Construction & Operations

5

SAP for Engineering, Construction &OperationsWith SAP for Engineering, Construction & Operations, you can support the full range ofbusiness processes, from specification and design to construction and operations, while yourealize exceptional collaboration with your partners.

This SAP for Engineering, Construction & Operations Master Guide provides a centralstarting point for the technical implementation of the following business scenarios of SAPfor Engineering, Construction & Operations:

Contract Management [page 11]

Subcontractor Management [page 13]

You can find an overview about the whole functionality of SAP for Engineering,Construction & Operations in the solution map: service.sap.com/bmetSAP Business Maps Industry-Specific Maps Engineering, Construction &Operations.

The business scenarios that are presented here serve as examples of how youcan use SAP software in your company. The business scenarios are onlyintended as models and do not necessarily run the way they are described herein your customer-specific system landscape. Make sure that you check yourrequirements and systems to determine whether these scenarios can be usedproductively at your site. Furthermore, we recommend that you test thesescenarios thoroughly in your test systems to ensure they are complete and freeof 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 ComponentList Viewer in SAP Service Marketplace (service.sap.com/scl).

SAP for Engineering, Construction & Operations

History of Changes

6

History of ChangesThe Master Guide is updated on a regular basis on SAP Service Marketplace at:service.sap.com/instguides

Make sure you have the latest version of the Master Guide by checking SAPService Marketplace right before the installation.

The following table provides an overview of the most important changes that were made tothe latest versions.

Master Guide Version Important Changes

1.00 (July 2010)

Getting Started

Further Scenario Information

7

Getting StartedThis Master Guide provides the information about which components and which guides arerequired during the implementation of the business scenarios.

Getting Started [page 6] contains valuable information about using this document andrelated information (documentation and SAP Notes) crucial to the installation andupgrade.

Business Scenarios of SAP for Engineering, Construction and Operations [page 11]contains the following information for each business scenario:

A short overview of the business scenario

Minimal system landscape

A software component matrix for each business scenario that provides theinformation about which components the business scenario uses and if thecorresponding component is mandatory or optional.

Where you can find further information about the business scenario.

You can find the most current information about the technical implementation ofSAP for Engineering, Construction and Operations and the latest installationand configuration guides on SAP Service Marketplace underservice.sap.com/instguides.

We strongly recommend that you use the documents available here. The guidesare regularly updated.

Further Scenario InformationIn addition to the information provided in this Master Guide, you will find more information onthe SAP Service Marketplace:

Scenario Description

The scenario description is part of SAP Solution Manager implementation content.For more information about SAP Solution Manager, seeservice.sap.com/solutionmanager.

Configuration Documentation

The configuration documentation is part of SAP Solution Manager implementationcontent. For more information about SAP Solution Manager, seeservice.sap.com/solutionmanager.

Getting Started

Related Information

8

Related InformationThe following list contains links to crucial information for implementing this solution.

List of Related Documentation

Content Location

Information about technical and release planningissues on SAP components

service.sap.com/pam

Information about the latest version of installationand 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 ofhardware requirements (such as CPU, disk, andmemory resource) with the Quick Sizer tool

service.sap.com/sizing

Information about network security – SAP SecurityGuide

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 GuidesThis Master Guide is based on Component Master Guides. You will find detailed informationabout the relevant components in the following documents:

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 ERP6.0 Planning

SAP Enhancement Packages for SAP ERP6.0

service.sap.com/erp-inst SAP ERP6.0 SAP enhancement package for SAPERP 6.0

Consider that there are several documents available to support the installationof your product and its enhancement packages:

Master Guide

Installation Guide

Installation Guide: SAP Enhancement Package Installation Using SAPEnhancement Package Installer (SAPehpi) 7.02

Troubleshooting and Administration for Installations Using SAPehpi(ABAP)

Troubleshooting for Installations Using SAPehpi (Java)

Practical Guide for How to Install SAP Enhancement Packages

You can find all these guides on SAP Service Marketplace underservice.sap.com/instguides where the installation guides of yourproducts are located.

SAP Solution ManagerSAP provides the SAP Solution Manager as the highly recommended platform to efficientlysupport the implementation of your solution. Using SAP Solution Manager significantlyaccelerates the implementation process and help you to achieve your business goals. At thesame time, SAP can deliver Support Services based on the business scenarios designed anddocumented in SAP Solution Manager. Implementation content for your solution can furtheraccelerate the implementation process. For information about availability of contentspecifically tailored to your solution, see SAP Service Marketplace underservice.sap.com/solutionmanager.

Getting Started

Important SAP Notes

10

Important SAP NotesThis section contains important SAP Notes for SAP for Engineering, Construction andOperations.

Read the installation SAP Notes before beginning the installation. These containthe most recent information regarding the installation, as well as corrections tothe installation documentation.

Make sure that you have the most recent version of each SAP Note. They arelocated on the SAP Service Marketplace (service.sap.com/notes).

List of Related SAP Notes

SAP NoteNumber

Title Description

Business Scenarios of SAP for Engineering, Construction and Operations

Contract Management

11

Business Scenarios of SAP for Engineering,Construction and Operations Contract ManagementOverview

You use this business scenario to sell and settle (bill) a project to customers for long runningprojects that are either based on a service structure (Bill of Services) or require for the billingprocess the handling of construction specific a like cumulative invoices, retention etc.. Typicaltasks performed take several month or week to complete. In this process it is typical that anumber of invoices are send to the customer instead of one depending on his progress.

A service specification (also called bill of service) is a quantitative and qualitative descriptionof the services to be performed e.g. to built a new building. It’s the communication structurefor all business partners involved in the process (owner, general contractor, subcontractors).

In Unit Price Contracts the owner and the general contractor agree on a price for one unit ofthe service to be performed. In order to measure the progress for the services to beperformed a service entry sheet is created. A service entry sheet is basically a quantitativeconfirmation for the services performed so far. The billing (down payment request or invoice)is based on the service entry sheet (quantities performed) and the bill of services (prices).

In Lump Sum Contracts owner and general contractor agree on a lump sum for the executionof the contract. In contrast to the unit price contract the settlement is done using a billing planand not with the service entry sheets. Service entry sheets are the internal measure tovaluate the constructions site and to determine its progress. Usually owner and generalcontractor agree on a billing plan with dates usually depending on the progress of the work.This means that e.g. 10% of the lump sum is paid when the contract is signed, 40% when thebuilding shell has been finished, and 40% when the interior fittings have finally beenperformed. The remaining 10% is paid once the entire work is done, that means after theacceptance procedure.

A huge part of the customer services is commonly performed by subcontractors(approximately 70%-80%). That means that parts of the customer service specification arecommunicated to different subcontractor. During the creation of a bid to the customertendering for some services in the procurement takes place.

The billing process can be integrated to debit-side down payment chains. Debit-side downpayment chains incorporate invoice and payment transactions between the sold-to party(debtor) and the main contractor. It is important to keep a cumulative view on the situation. Inaddition often various retentions (security retentions, special retentions or guaranteeretentions), additional cost e.g. for the consumption of electricity or water apply and thatverifications have been provided and have to be tracked have to be handled. The DownPayment Chains as a tool in SAP cover this scenario for Contract Management from theinitial contract and all its details, to the various partial invoices including specifics likeretentions and help to keep the entire process smooth and under control.

Technical System Landscape

The following figure provides an overview of a possible system landscape for ContractManagement.


Contract Management

12

ERP Server

SAP Enhancement Package 5 forSAP ERP 6.0 – SAP ECC Server

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Contract Management.

Component Mandatory Optional

SAP Enhancement Package 5 for SAP ERP 6.0 – SAP ECC ServerTechnical Usage: Financial Supply Chain Mgmt

X

Implementation Sequence

The following table provides the implementation sequence:

ERP Server

1 Installation of SAP ERP 6.0 –SAP ECC Server

For detailed information, seeservice.sap.com/erp-inst SAP ERP 6.0Planning.

2 Installation of SAPEnhancement Packet 5 forSAP ERP 6.0 – SAP ECCServerTechnical Usage: FinancialSupply Chain Mgmt

For detailed information, seeservice.sap.com/erp-inst SAP ERP 6.0SAP enhancement package for SAP ERP

3 Activation of the businessfunction LOG_FI_DPC_MM_1

In Customizing for SAP Customizing ImplementationGuide, choose Activate SAP ECC Extensions toactivate the business function set and the businessfunction.


Subcontractor Management

13

Subcontractor ManagementOverview

You use this business scenario to integrate externally performed service procurement withinvoice processing using credit-side down payment chains. It allows companies to managetheir relationships with subcontractors and suppliers.

You can use this scenario to:

Manage the external procurement of services with a detailed description of theservices.

Enter several service entry sheets (SES) in order to confirm the performed services. Process the invoicing with credit-side down payment chains which allows you:

o That various business transactions like advance payment, several partialinvoices, a final invoice, corrections to postings for the final invoice and offsetof advance payment can be handled.

o That invoices are based on progress and entered cumulativeo That the customer retains a certain amount of the invoice. In the contract of

the credit-side down payment chain the agreed retentions are entered (likeretentions for partial invoice and final invoice). The following kind of retentionare possible in the posting process:

Security retention amounts for partial invoices (which are canceledwhen the final invoice is created).

Security retention amounts for final invoices (which affect paymentwhen a defined time period has elapsed or through a bankguarantee).

Special retention amounts (quality defects or incorrect invoicing).o That additional costs like water and energy might deduced.o That various conditions are checked if the subcontractor has fulfilled his

obligations and can be paid.o Optional match against the quantity take of (also called service entry sheet).

Credit-side down payment chain allows you to monitor payables for subcontractors orvendors and to gain information on past and future outgoing payments

The subcontractor management process differs in various countries and also has legalrequirements. You have to check if the localization is available for the specific business case.


Subcontractor Management

14

Technical System Landscape

The following figure provides an overview of a possible system landscape for SubcontractorManagement.

ERP Server

SAP Enhancement Package 5 forSAP ERP 6.0 – SAP ECC Server

The following software components are either mandatory or optional, as indicated below, forthe technical implementation of Subcontractor Management.

Component Mandatory Optional

SAP Enhancement Package 5 for SAP ERP 6.0 – SAP ECC ServerTechnical Usage: Financial Supply Chain Mgmt

X

Implementation Sequence

The following table provides the implementation sequence:

ERP Server

1 Installation of SAP ERP 6.0 –SAP ECC Server

For detailed information, seeservice.sap.com/erp-inst SAP ERP 6.0Planning.

2 Installation of SAPEnhancement Packet 5 forSAP ERP 6.0 – SAP ECCServerTechnical Usage: FinancialSupply Chain Mgmt

For detailed information, seeservice.sap.com/erp-inst SAP ERP 6.0SAP enhancement package for SAP ERP

3 Activation of the businessfunction LOG_FI_DPC_MM_1

In Customizing for SAP Customizing ImplementationGuide, choose Activate SAP ECC Extensions toactivate the business function set and the businessfunction.

SAP Enhancement Package Concept

Enhancement Package Key Concept

15

SAP Enhancement Package ConceptEnhancement Package Key ConceptWe have adapted our major release strategy to better fit your adoption cycle. To ensure thatyou benefit from new developments and innovations while minimizing the impact on your coreoperational systems, SAP uses enhancement packages to speed up the delivery of newfunctions.

With SAP enhancement packages, you can install and activate new functions depending onyour business needs without having to perform a system upgrade. You can selectivelyimplement 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 dueto 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 fullenhancement package. Instead, you can update the software components that are related tothe 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 systembehavior. The new functions are available in the system, but are not active. After theinstallation, no user interface or process change takes place. You must explicitly activate newfunctions so that they become visible in the system. As a result, changes are predictable andthere are no side effects as only the activated areas change.

With the switch framework technology (transaction SFW5), it is possible to control theactivation of new SAP objects in ABAP-based SAP systems. The activation process triggersa 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 newdevelopments in the SAP system, for example:

Menu entries

New screens

New fields on the application user interfaces

IMG activities required for the implementation

New table entries in Customizing tables and system tables


Key Facts About Enhancement Packages

16

You can create a transport request with the current settings of the switch framework. You cancheck functional changes and the impact of an activated business function in advance in thebusiness 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 theSupport Package versions of the underlying SAP system. You must install the enhancementpackage in combination with the latest available Support Package stack. This approachreduces installation, modification adjustment, and testing effort. Using this strategy, you caninstall SAP enhancement packages as a normal maintenance activity together with SupportPackage stacks.

An enhancement package requires a specific Support Package stack level in the sourcerelease SAP system. If the SAP system is on a lower Support Package stack level, allrelevant Support Package stacks are automatically included into the download queue, as wellas 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 ChangeManagement work center) supports the download of a consistent queue that includes allnecessary Support Packages and enhancement packages. In addition, SAP SolutionManager calculates a valid import queue for the selected SAP system and generates theenhancement 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 theupgrade of an SAP system to a higher release including an enhancement package, you usethe standard installation and upgrade tools (SAPinst, SAPup and SAPJup). To install anenhancement package on an existing SAP system, you use the SAP Enhancement PackageInstaller (SAPehpi). It allows enhancement packages to be installed with reduced downtime.SAPehpi uses the shadow system installation strategy, a well-known feature in the upgradetechnology.

Key Facts About Enhancement PackagesThe following list summarizes important facts about the enhancement package concept andrecommended approaches:

Install only selected parts of the enhancement package. The selection is driven bythe functional need from a business point of view.

You cannot mix the installation of different enhancement package versions in yourABAP-based SAP system. You can have just one enhancement package version inthe SAP system.

SAP enhancement packages are cumulative, meaning that each new enhancementpackage includes new innovations of its own as well as all innovations delivered withprior packages.

We recommend installing the latest available enhancement package version.


Key Facts About Enhancement Packages

17

Install enhancement packages and Support Packages in one single step (thisincludes the preconditioned Support Packages).

SAP enhancement packages have Support Packages of their own that are equivalentto the Support Package versions of the underlying SAP system.

SAP enhancement packages have the same maintenance period as the underlyingcore application.

The installation of an enhancement package is irreversible.

As long as you do not activate a business function, the installation of anenhancement package has no impact on existing business processes or userinterfaces.

You can only activate business functions in ABAP-based systems, not in Java-basedSAP systems.

The activation of most business functions and extension sets is irreversible. Only asmall number of business functions is reversible.

Test the installation process and activation of new functions in advance on a sandboxsystem. Ensure that you evaluate the runtime and the SAP system behavior, itsdependencies and impacts. Make sure that your SAP system is free of errors beforegoing live.


Enhancement Package Implementation

18

Enhancement Package ImplementationIn the following, you will find an overview of the steps involved in the three differentenhancement package implementation scenarios.

Process

Enhancement Package Installation in an Existing 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 thedownload 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 dependencyanalyzer 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 SolutionManager (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 thetechnical usage Central Applications. The installation of the technical usage CentralApplications implies that the system is ready for use without installing any furthertechnical 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 forthe download of packages, and that you have configured the MaintenanceOptimizer.

c. You download the installation queue.

d. You perform the installation.

e. You activate the business functions using the switch framework (transactionSWF5).


Enhancement Package Implementation

19

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 technicalusages, because software component SAP_APPL 6.05 is already present in yoursystem (part of technical usage Central Applications). This is a prerequisite for usingSAINT.

Switch framework with Dependency Analyzer and Impact Analyzer in SAP SolutionManager (transaction SWF5)

Upgrade to an SAP System Including an Enhancement PackageInstallation

Customers who are upgrading from a lower release to an SAP system for whichenhancement packages are available can include parts of enhancement packages into theupgrade process.

The use of SAP Solution Manager Maintenance Optimizer is mandatory if you wantto include enhancement packages in your release upgrade.

Process

1. You plan the upgrade to the new release. Decide which parts of the enhancementpackage you want to include into the upgrade procedure before you start with theupgrade.

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 thedownload of packages, and that you have configured the Maintenance Optimizer.

4. You download the required parts of enhancement packages and Support Packagesas 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 packageinto 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 SAPJup)

SAP Solution Manager Maintenance Optimizer


The Main SAP Documentation Types

20

The Main SAP Documentation TypesSeveral documents have been created to assist you in installing, implementing, operating,and upgrading your SAP solutions. The Solution Master Guide (this document) is the firstdocument you obtain. Although strongly related to each other, the different documentationtypes should help you solve problems at different levels on different solution phases. Thefollowing figure shows an overview of the most important documentation types that youneed in the various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German. Thecurrent 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, usetransaction STERM.

The SAP Library is a collection of function- and process-oriented documentation for SAPcomponents. It is located on SAP Help Portal at help.sap.com. SAP Library also containsBusiness Scenario Descriptions. These are found on SAP Service Marketplace atservice.sap.com/ibc.

The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customerrequirements. Its structure and documentation are component-oriented. It is located in theSAP Easy Access menu of the SAP system under Tools Customizing IMG.

The Security Guide describes the settings for a medium security level and offerssuggestions for raising security levels. A collective security guide is available for the SAPNetWeaver technologies such as SAP Web Application Server (SAP Web AS). Thisdocument contains general guidelines and suggestions about system security. Othertechnologies and individual applications have a Security Guide of their own.


The Main SAP Documentation Types

21

The current version of the Security Guide is located on SAP Service Marketplace atservice.sap.com/securityguide.

Implementation

The Component Installation Guide describes the technical implementation of an SAPcomponent, taking into account the combinations of operating systems and databases. Itdoes not describe any business-related configuration. The Component Installation Guides forthe different components can be found on SAP Service Marketplace atservice.sap.com/instguides.

The Configuration Documentation is contained in the SAP Solution Manager. SAP SolutionManager is a tool with various functions, one of its main functions being the configuration ofSAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, aswell as documentation.

Production Operation

The Solution Operations Guide is the starting point for operating an SAP solution. Theguide refers users to the tools and documentation that are needed to carry out various tasks,such as monitoring, backup/restore, master data maintenance, transports, and tests. It alsorefers users to other documents, for example the SAP Library, the Master Guide, and theComponent Management Guides. The current version is located on SAP ServiceMarketplace at service.sap.com/instguides.

Upgrade

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of anSAP 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 Guidesand SAP Notes. Instead of an Upgrade Master Guide, there may be several BusinessScenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the BusinessScenarios of an SAP solution. The current Version is located on SAP Service Marketplace atservice.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 notdescribe any business-related configuration. The current version is located on SAP ServiceMarketplace at service.sap.com/instguides.

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developmentsenable the SAP system to generate delta and upgrade IMGs. The current version is locatedon SAP Service Marketplace at service.sap.com/releasenotes or on the SAP EasyAccess menu of the SAP system under Help Release information.

Upon reviewing this description of the supplementary information sources at your disposal,you will be ready to get started.

Documents

SAP ECO1