s45 scen installguide en de

7/30/2019 S45 Scen InstallGuide en De

http://slidepdf.com/reader/full/s45-scen-installguide-en-de 1/17

SAP SCM 4.1

November 2004

English

ScenarioFulfillment Visibility

SAP AGNeurottstr. 1669190 Walldorf Germany

Scenario Installation Guide



SAP Best Practices Scenario Fulfillment Visibility: Installation Guide

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 softwarecomponents 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 trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript 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, and other SAP products and services mentioned hereinas well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warrantyof any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. Theonly warranties for SAP Group 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 additional warranty.

© SAP AG of 17




Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

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 keywords 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, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG of 17




Contents

Fulfillment Visibility: Installation Guide.....................................................................................5

1 Purpose.................................................................................................................................. 5

1.1 System Requirements ....................................................................................................5

2 Preparation............................................................................................................................ 6

2.3 Installation Considerations and Options........................................................................14

2.4 Prerequisites..................................................................................................................14

3 Installation............................................................................................................................16

3.1 Building Block Connectivity...........................................................................................16

3.2 Building Block SCM Collaboration Settings...................................................................16

3.3 Building Block Supply Chain Event Management .........................................................17

4 Test and Use........................................................................................................................ 17

© SAP AG of 17




Fulfillment Visibility: Installation Guide

1 Purpose

This document provides you with the information you need to set up your business scenario.It forms the backbone of the installation documentation, because it summarizes whichbuilding blocks you need to implement for this scenario, and in what sequence.

Always use the scenario installation guide (this document) as the starting point for all your configuration activities.

For a successful installation of the entire scenario, it is important that:

• You follow the building block sequence in the scenario installation guide

•

You carry out all required configuration activities for one building block before youmove to the next.

• That you refer to the relevant section in this document after you have finished

installing a building block before you start installing the next building block.

1.1 System Requirements

To implement this scenario, the following systems are required and must be installed:

• SAP R/3 4.7

• SAP SCM 4.1 Full Version

For this scenario, the Event Management (EM) Component of the SCM 4.1 system isused. Alternatively, you can install the EM as a standalone solution. This option has notbeen tested by the SAP Best Practices for SCM.

An additional component, the Web Communication Layer (WCL) must be installed onyour Event Management System. The installation guide for the Web Communication

Layer can be found on the Service Marketplace http://service.sap.com/InstGuides →

mySAP Business Suite Solutions→ mySAP SCM → Using SAP SCM 4.1 Server →

Installation Guide – WCL 4.1.

For a detailed description of the various software components (SAP_BASIS, …), their releases and support package levels, refer to the document System Requirements for theSAP Best Practices for SCM 4.1 Scenarios, which you can find on the SAP Best Practices for SCM documentation CD

© SAP AG of 17

http://service.sap.com/InstGuides

http://service.sap.com/InstGuides




2 Preparation

2.1.1 Essential Information

Read the section Essential Information in full to learn how to install an SAP Best Practices for SCM scenario. It describes

• the building block concept

• how to use the SAP Best Practices documentation

• how to upload user roles required for the installation or testing purposes

We recommend that you read the entire section to ensure the successfulinstallation of a scenario.

2.1.1.1Building Blocks: Concept

The building block concept offers substantial benefits to SAP business partners with respectto the development, distribution, and sale of solutions.

Building blocks:

• Are reusable, business process-oriented, preconfiguration units, which you simply have toassemble to obtain your desired installation.

• Can be used flexibly as the basis for many vertical solutions.

• Vary in size and content. Some building blocks cover only a small range of very specific,

scenario pre-configuration, whereas others cover complex, generic pre-configuration thatcan be used in many solutions. These generic building blocks help to reduce redundancy.

• Enable SAP business partners to focus on the development of the specific vertical

configuration requirements of each customer.

2.1.1.2Building Blocks: Installation

To install SAP Best Practices using building blocks, you install a number of building blocks ina predefined sequence using the various tools and documentation provided.

• The number and sequence of the building blocks depend on what you are installing.

• The configuration guides and configuration roles guide you through the installation.

• Each building block has its own configuration role and configuration guide. The role has

to be uploaded into the system from the documentation CD. The configuration guide isavailable on the documentation CD.

© SAP AG of 17




• To perform the configuration activities for a building block in the system, you follow the

configuration role you have uploaded reading the description of the corresponding stepsin the configuration guide.

• After installation, you can test the whole scenario using the document known as the

business process procedure (BPP). This document is also available on thedocumentation CD.

2.1.1.3Installation Options

Use

You can implement an entire SAP Best Practices scenario or install individual building blocksto configure your own scenario or to enhance an existing installation.

Option A: Scenario Installation

The installation of an entire business scenario is the standard installation procedure.

The scenario installation guide is the central document for installing a business scenario anddescribes

• which building blocks are required for the scenario

• the installation sequence for these building blocks

• the scope of the implementation activities for each building block

SAP Best Practices Installation

A scenario installation typically consists of the following steps:

1. Check the preparation steps and prerequisites, such as system requirements and SAPNotes that you have to fulfill before you can start with the installation.

2. Install all building blocks according to the sequence in the scenario installation guide.

3. Test the scenario using the business process procedure.

Option B: Building Block InstallationYou may consider installing individual building blocks and not an entire scenario if one of thefollowing applies:

• You have already installed a scenario delivered by SAP Best Practices for SCM .

• You want to configure a scenario that is not in the scope of SAP Best Practices.

• You have already configured scenarios that are in the SAP Best Practices scope, but

without using the SAP Best Practices methodology and want to enhance these scenarioswith specific functions.

In this case we recommend the installation of individual building blocks.

© SAP AG of 17




Configuration of Non-Standard Scenario

If you want to configure a scenario that is not in the scope of SAP Best Practices proceedas follows:

1. Compare the scenario you are going to install with similar SAP Best Practices for SCM scenarios.Note that some industry-specific scenarios can be used for other industries, too.

2. Check whether there are building blocks containing configuration that can be used for your scenarios.Note that for most SCM scenarios, the installation of the Connectivity and the Replication building blocks is a basic prerequisite.

3. Refer to the scenario installation guide of a scenario that is similar to yours to check therecommended installation process.

4. Check the installation prerequisites of the building block(s) you are going to install(scenario installation guide and building block configuration guides). When you have

installed the required SAP Notes or support packages (if necessary), install the buildingblock following the description in the configuration guide.

Enhancement of Existing Scenario Installation

If you want to enhance an existing scenario installation with additional functions:

1. Compare the scenario you are going to install with similar SAP Best Practices scenarios

2. Verify whether the building blocks contain configuration that can be used to enhance your scenario.

3. Check the requirements for the installation of the relevant building blocks and make sure

they are compatible with your existing installation. Refer to the scenario installation guidefor your existing scenario, or choose a scenario that is very similar to check theinstallation documentation.

4. When you have installed the required SAP Notes or support packages (if necessary),install the building block following the description in the configuration guide.

© SAP AG of 17




2.1.1.4Documentation

Document Types and ContentEach building block has various documents, which describe the business content, installation,and testing procedures. It is important that you read these documents carefully in theappropriate order, as illustrated in Using the Document Types.

The following table gives you an overview of the documentation delivered with SAP Best Practices.

DocumentType

Purpose FileFormat

Scenario

Overview

Provides a graphical overview of a scenario. MS

PowerPointScenario/Building Block Description

Briefly describes the content of a scenario or building blockand shows its benefits. This is not a document as such, butappears as HTML content on the documentation CD.

HTML

ScenarioInstallation Guide

The Scenario Installation Guide tells you which buildingblocks you need to install for a specific scenario andprescribes their installation sequence. It is thedocumentation backbone for installing a business scenario.It does not give you detailed instructions on how to install aspecific building block but may contain scenario-specificconfiguration data. Always refer to the Scenario Installation Guide before

you start installing a building block and when you havefinished installing a building block.

MS Word

Building Block ConfigurationGuide

Each building block has a configuration guide, whichdescribes:

• The manual configuration steps you have to perform to

set up a building block.

• Configuration details for reviewing the system settings.

The configuration guide describes the activities in thelogical order of the installation process.

MS Word

Business

ProcessProcedure

End-user documentation providing detailed, application-

focused descriptions of business processes. Used for testing scenarios.

MS Word

© SAP AG of 17




2.1.1.4.1 Documentation Overview

Use

For an SAP Best Practices installation, use the documentation as displayed in the followinggraphic:

Building Block

Configuration Guide 5

Building Block


Building Block


Using Best Practices Documentation

Building Block


e.g. Replication

Preparation

Installation

Business Process

Procedure

Test and Use

•Essential Information

•Scenario description

•Scenario Overview

•Building block description

Building Block


e.g. Connectivity

Scenario

Installation Guide

© SAP AG of 17




2.1.1.5Uploading Configuration and User Roles

Use

For each building block you want to install, there is a user menu comprising all configurationactivities, which helps you to install this building block in the correct sequence.

Likewise, there is a user menu comprising all activities that belong to the business processescovered by this scenario

To set up the user menu for the person who is going to use this menu, you need to upload theuser role file that contains this menu and assign it to the relevant user. Should there be morethan one user role per scenario, you have to repeat this procedure.

Procedure

1. In the SAP Easy Access (SAP APO) screen, choose Create role.

2. In the Role Maintenance screen, choose Role → Upload from the menu bar.

3. Read and confirm the Information message that appears.

4. In the Open dialog box, browse for the role file in the Misc directory of the DocumentationCD, select the required user role and choose Open.The List of roles to be imported dialog box is displayed.

5. Choose Transfer (Enter) to import the selected role.

If the upload was successful, the message One role was loaded from the file appears atthe bottom of the screen.

6. To assign the role to your user, choose Change Role.

7. In the Change Role screen, access the User tab page.8. Enter your system user ID, save and go back.

9. Repeat this procedure for the remaining roles, if necessary.

10. Log off and log on to the system again.

11. Choose User menu. One or more roles you have assigned to your user are displayed.

Result

You have imported the user roles for this scenario into the system and have assigned them tothe system user ID it was intended for. The user roles appear as the user’s personalized user menus. Depending on the role type (configuration role or user role) the user can use this

menu to install a building block or to test the business scenario.

2.2

•

© SAP AG of 17




2.3 Installation Considerations and Options

If you want to install the Fulfillment Visibility scenario in a system landscape with an empty,

non-configured SAP R/3 system, we recommend that you install the SAP Best PracticesBaseline Package for UK in SAP R/3 as a configuration prerequisite. In this case, thefollowing building blocks that form the Layer 0 of the Baseline Package UK in R/3 aremandatory for all Logistic Service Providers solutions. You have to make sure these buildingblocks are installed and set up correctly in your SAP R/3 system.

Building Blocks Notes

Baseline Building Blocks (Layer 0)

B32 - Best Practices R/3 Installation

J02 - Organizational Structure

J03 - Financial Accounting

J08 - Cost/Profit Center Accounting

J05 - Material Management

J04 - Sales and Distribution

2.4 Prerequisites

2.4.1 SAP Notes

Additional Information regarding this Best Practices scenario and all errors that becameknown after the delivery of the SAP Best Practices for SCM CD are documented in the SAPNote 772396.

Currently, the following SAP Notes are required to run the respective sections of thisscenario:

2.4.2 SAP Notes for Building Block - SCEM

SAP Note # System Component Description

757146 SCM SCM-EM-MGR System parameters as selection fields in WCL

© SAP AG of 17




773781 SCM SCM-EM-MGR

2.4.3 Master Data

Before you install this scenario, you must have created some master data such as thematerial and vendor in the SAP R/3 system. You can use your own master data for thispurpose. If no master data is available, there is a chapter in the SCEM configuration guidethat describes how you can create a minimum set of required master data, to enable you totest this scenario.

© SAP AG of 17




3 Installation

3.1 Building Block Connectivity

Use

Connectivity refers to the interface and transfer of data and configuration settings betweenthe SAP R/3 back-end system and other systems running SAP solutions such as SAP SCM.

Procedure

1. In the configuration guide of building block Connectivity , read the Preparation section and

upload the configuration roles for this building block.

2. Carry out all activities of the following sections of the Connectivity configuration guide:

• Local Settingsà SAP R/3

• Local Settingsà SAP SCM

• Cross Connectivity à SAP R/3 with SAP SCM

3.2 Building Block SCM Collaboration Settings

Use

This building block contains the required steps for setting up e-mail communication from your SAP SCM system.

Prerequisites

You have correctly installed the building block Connectivity .

Procedure

1. In the configuration guide of building block SCM Collaboration Settings, read thePreparation section and upload the configuration roles for this building block .

2. Implement all activities of the section Setting up e-mail Communication.

© SAP AG of 17




3.3 Building Block Supply Chain Event Management

UseThis building block contains all steps required to implement the functions that are specific tothe Fulfillment Visibility scenario in the SAP systems.

Procedure

• In the configuration guide of building block Supply Chain Event Management , read the

Preparation section and upload the configuration roles for this building block .

• Implement all activities from the Supply Chain Event Management configuration guide.

Result

All of the settings relevant for implementing the scenario-specific functions of Fulfillment Visibility in an SAP R/3 Enterprise and SAP SCM environment have been processed.

4 Test and Use

You have successfully installed the scenario Fulfillment Visibility .

The business processes of this scenario are described in the business process procedure(BPP) Fulfillment Visibility.

This document gives you detailed step-by-step instructions on how to carry out the businessprocesses in the business application of your SAP system.

© SAP AG of 17

s45 scen installguide en de

Documents