masterguide cwm bs2010 a

Master Guide

SAP Catch WeightManagementSAP Business Suite 7

Innovations 2010

Document Version 1.00 – December 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 AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.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 Catch Weight Management Overview ...................................... 5

History of Changes ................................................................................ 7Getting Started .................................................................................... 8

Related Information ............................................................................... 9Related Guides ..................................................................................... 10SAP Solution Manager ......................................................................... 11Important SAP Notes ........................................................................... 11

Business Scenarios of SAP Catch Weight Management ............. 12Catch Weight Management ................................................................. 12

Upgrade of SAP Catch Weight Management ................................. 15SAP Enhancement Package Concept ............................................ 16

Enhancement Package Key Concept ................................................. 16Key Facts About Enhancement Packages......................................... 18Enhancement Package Implementation ............................................ 19

The Main SAP Documentation Types............................................. 22

SAP Catch Weight Management

5

SAP Catch Weight ManagementSAP Catch Weight Management (SAP CWM) provides basic functionality required in variousindustries, like for example in consumer products industry required by the food segment

One of the basic requirements of these industries is that many materials used have to bemanaged throughout the logistics chain in two independent units of measure, for example, inpieces and kilograms.

Catch weight materials, in the true sense of the term, are materials for which there is avariable relationship between the base unit and another parallel unit of measure. As therelationship between the units is not known in advance, or can vary every time goodsmovements are entered, it is necessary to “catch” the weight. This means that a quantity hasto be entered for both the parallel unit and for the base unit. This requires some form ofweighing or measuring before entry. You must also take into account the fact that thematerial could undergo natural shrinkage, such as weight loss during storage.

As there are no fixed conversion factors between the base unit and the parallel unit ofmeasure, both units have to be updated separately in inventory management. Therelationships between other alternative units have to be fixed to either the base unit or theparallel unit (for example, pallets to cases). The parallel unit can be any unit of measure anddoes not have to be a weight unit (for example, volume or length).

Complementary to the flow in logistics the valuation and the controlling aspects are adopted.Valuation takes place in one unit of measure which isin the food industry usually ameasurable unit. In most cases the weight unit of measure (e.g. KG) .

For this reason, SAP CWM allows materials to be carried in two independent units ofmeasure throughout the entire logistics chain (sales and distribution, purchasing, materialsmanagement, production, quality management and logistics execution). SAP CWM providesthe integration with standard costing and inventory valuation by usage of a so-calledvaluation unit of measure, which can be either the base unit or the parallel unit.

This Master Guide provides a central starting point for the technical implementation of theCatch Weight Management business scenario of SAP for Consumer Products:

Catch Weight Management [page 12]

You can find an overview about the whole functionality of SAP for ConsumerProducts in the solution map: service.sap.com/bmet SAP BusinessMaps Industry-Specific Maps Consumer Products -> ConsumerProducts – Food -> Demand Fulfillment & Execution.

The business scenarios that are presented here serve as examples of howyou can use SAP software in your company. The business scenarios are onlyintended as models and do not necessarily run the way they are describedhere in your customer-specific system landscape. Make sure that you checkyour requirements and systems to determine whether these scenarios can beused productively at your site. Furthermore, we recommend that you testthese scenarios thoroughly in your test systems to ensure they are completeand free of errors before going live.

This Master Guide provides just one way to implement each businessscenario. For other ways to implement business scenarios, see the Scenario


6

Component List Viewer in SAP Service Marketplace(service.sap.com/scl).


History of Changes

7

History of ChangesThe 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 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 (December 2010)

Getting Started

Further Scenario Information

8

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

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

Business Scenarios of SAP Catch Weight Management [page 12] contains the followinginformation for each business scenario:

A short overview about the business scenario

Minimal system landscape

A software component matrix for each business scenario that provides informationabout which components the business scenario uses and if the correspondingcomponent is mandatory or optional

References to further information about the business scenario

You can find the most current information about the technical implementationof SAP Catch Weight Management and the latest installation andconfiguration guides on the SAP Service Marketplace underservice.sap.com/instguides.We strongly recommend that you use the documents available here. Theguides are regularly updated.

Further Scenario InformationIn addition to the information provided in this Master Guide, you can 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

9

Related Information

The following table contains links to crucial information for implementing this solution.

List of Related Documentation

Content Location

Information about technical and releaseplanning issues on SAP components

service.sap.com/pam

Information about the latest version ofinstallation and upgrade guides for SAPcomponents

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,and memory resource) with the Quick Sizertool

service.sap.com/sizing

Information about network security – SAPSecurity 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

10

Related Guides

This Master Guide is based on Component Master Guides. The documents listed belowcontain detailed information about the relevant components:

List of Related Master Guides

Content Location

SAP NetWeaver 7.02 service.sap.com/installNW70

SAP ERP 6.0 service.sap.com/erp-inst SAPERP 6.0 Planning

SAP Enhancemen Packages for SAP ERP6.0

service.sap.com/erp-inst SAPERP 6.0 SAP enhancement packages forSAP ERP 6.0

SAP EWM in conjunction with SAP SCM http://service.sap.com/instguides--> SAP Business SuiteApplications SAP SCM SAPSCM Server Using SAP SCM 7.0Server

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.

http://service.sap.com/instguides

Getting Started

SAP Solution Manager

11

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 helps 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 may furtheraccelerate the implementation process. For information about availability of contentspecifically tailored to your solution, see SAP Service Marketplace underservice.sap.com/solutionmanager.

Important SAP NotesThis section contains important SAP Notes for SAP Catch Weight Management.

Read the installation SAP Notes before beginning the installation. Thesecontain the most recent information regarding the installation, as well aschanges to the installation documentation.

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

List of Related SAP Notes

SAP Note Title Description

1274044 IS-CWM: Reactivating theSwitch BC Sets

1279313 IS-CWM: Activating CWM in anERP system

CWM - Migration

1399197 Functional restrictions in SAPCatch Weight Management withSAP Enhancement Package 5

1450225 SAP CWM: Data Migration fromOld to New Architecture

1402525 IS-CWM: Check for possibleinconsistencies between MMand QM

Business Scenarios of SAP Catch Weight Management

Catch Weight Management

12

Business Scenarios of SAP Catch WeightManagementCatch Weight ManagementOverviewYou can use this business scenario in the consumer products industry, particularly in the foodindustry, to manage materials in two independent units of measure (for example, piece andkilogram). You can enter a base unit of measure and a parallel unit of measure for a material.A material for which you have defined a parallel unit of measure is called catch weightmaterial (CW material).

You can use the CWM-specific functions throughout the entire logistics chain, in costing andinventory management and in the financial accounting area.

Technical System LandscapeThe following figure provides an overview of a possible system landscape for Catch WeightManagement.

ERP Server

SAP Enhancement Package 5for SAP ERP 6.0 – SAP ECC

Server

SCM Server

SAP SCM 7.0 – SAP SCMServer

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

Component Mandatory Optional

SAP Enhancement Package 5 for SAP ERP 6.0 – SAP ECC ServerTechnical Usage: Catch Weight Management

X

SAP SCM 7.0 – SAP SCM Server

Supply Chain Management (for integration with ExtendedWarehouse Management)

X

Installation Sequence

The following table describes the installation sequence for Catch Weight Management.



13

ERP Server

1 Installation of SAP ERP 6.0 – SAP ECCServer

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

2 Installation of SAP Enhancement Package5 for SAP ERP 6.0 – SAP ECC ServerTechnical Usage: Catch WeightManagement

It is mandatory to installEnhancement Package 5 beforeyou select the Catch WeightManagement business function set.

3 Selection of the Catch Weight Managementbusiness function set

Go to transaction “SwitchFramework Customizing“ (SFW5) toselect the business function set forCWM (CWM BFS)

You cannot select the CWM BFS, ifyou have already activated abusiness function of anotherBusiness Function Set.

4 Activation of the CWM Finalization ofArchitectural Change and New Processes(CWM/CM_2) business function You can only activate this business

function, if:

You have installed the softwarecomponent IS-CWM 605 andEA-APPL 605

You have activated thebusiness function NewArchitecture: Inv. Mgmt., Inv.Acctg in ERP (/CWM/CM_1) inadvance or in parallel

If you have activated one orboth Business Functions of theold CWM architecture(“/CWM/BF” and/or“/CWM/APPL_INTEGRATION_1”), you have to perform a datamigration first.

See SAP Note 1450225

5 Activation of the “CWM Flexible MaterialPrices” (/CWM/FMP) business function(optional).This is needed in order to define your ownprice types for your materials.

You can only activate this businessfunction, if:

You have installed the softwarecomponent IS-CWM 605

You have activated thebusiness function NewArchitecture: Inv. Mgmt., Inv.Acctg in ERP (/CWM/CM_1) in



14

advance or in parallel

6 Activation of the “SAP Trader's andScheduler's Workbench” (LOG_TSW_ECC)enterprise business function (optional).

SAP TSW is the logistics planning andexecution platform for bulk commodities. If youwant to use the Catch Weight Management inBulk Scheduling and Execution businessscenario provided in the SAP SolutionManager, this business function must beactivated.


You have installed the softwarecomponent SAP_APPL 605and IS-OIL 605

7 Activation of the “Trade, CommodityManagement 4” (ISR_GLT_COMMODITY_4)enterprise business function (optional).

With this business function, you can use newand enhanced functions in the area ofCommodity Management. If you want to usethe Catch Weight Management and TradeExpenses business scenario provided in theSAP Solution Manager, this business functionmust be activated.


You have installed the softwarecomponent SAP_APPL 605and EA-GLTRADE 605

You have activated thebusiness function EA-GLT,ISR_RET_COMMODITY,ISR_RET_COMMODITY_2andISR_RET_COMMODITY_3

SCM Server

Installation of SAPEnhancement Package 1 forSAP SCM 7.0 – SAP SCM Server

For detailed information, seeservice.sap.com/instguides SAPBusiness Suite Applications SAP SCM SAPSCM Using SAP SCM 7.01.

Upgrade of SAP Catch Weight Management


15

Upgrade of SAP Catch Weight Management

New Customers with systems where SAP CWM has never been activatedbefore can activate and use the following business functions:

CWM: New Architecture: Inv. Mgmt., Inv. Acctg in ERP (/CWM/CM_1)CWM: Finalization of Architectural Change and New Processes(CWM/CM_2)CWM: Flexible Material Prices ((CWM/FMP)

After you have successfully activated CWM in such a system, you have to runa report which is provided with OSS note 1279313. This report copies thecontent of the field BUoM into the new CWM field VUoM and initializesnew CWM fields in stock tables.

Upgrade customers that had already selected the Catch WeightManagement business function set in a version prior to EHP4 and haveactivated any other business function of this business function set, need tomigrate to the changed architecture introduced with Enhancement Package 4for ERP 6.0 before the new business functions of EHP5 can be activated.Tools to support the migration to the new architecture are available withEnhancement Package 5 for ERP 6.0. For more information on the migration,please, contact CWM Solution Management. See SAP note 1450225.

SAP Enhancement Package Concept

Enhancement Package Key Concept

16



We 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 selectively implement the new functions and activate the software upon businessdemand. As a result, you can isolate the impact of software updates and make new functionsavailable 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 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



17

New screens

New fields on the application user interfaces

IMG activities required for the implementation

New table entries in Customizing tables and system tables

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.

MaintenanceSAP 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.

ToolsThe 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 Packages

18

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.For CWM, there is an important exception valid: As off EHP4 a new architecture forCWM is in place which is not compatible with earlier versions. Therefore, CWM EHP4and higher does not include CWM EHP3 and earlier!!

We recommend installing the latest available enhancement package version.

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

19

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 System1. 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

Process1. 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.



20

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).

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 PackageInstallationCustomers 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.



21

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

22

The Main SAP Documentation TypesSeveral documents have been created to assist you in installing, implementing, operating andupgrading 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 solveproblems at different levels in different solution phases. The following figure shows anoverview of the most important documentation types that you need in the various phases inthe 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 DocumentationSAPterm 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.

The Implementation Guide (IMG) is a tool used to configure the SAP system to meetcustomer requirements. Its structure and documentation are component-oriented. It is locatedin 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 offerssuggestions for raising security levels. A collective security guide is available for SAPNetWeaver. This document contains general guidelines and suggestions about systemsecurity. Other technologies and individual applications have a Security Guide of their own.


The Main SAP Documentation Types

23

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

ImplementationThe 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. You can find the ComponentInstallation Guides for the different components 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 OperationThe Solution Operations Guide is the starting point for operating an SAP solution. Theguide refers users to the tools and documentation needed to carry out various tasks, such asmonitoring, backup/restore, master data maintenance, transports, and tests. It also refersusers 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.

UpgradeThe 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 in the SAPService Marketplace 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 in the SAP EasyAccess menu of the SAP system under Help Release information.

masterguide cwm bs2010 a

Documents