Click here to load reader

S44 Scen InstallGuide en De

  • View

  • Download

Embed Size (px)



Text of S44 Scen InstallGuide en De

Scenario Installation Guide


November 2004


REF DokSprache \* MERGEFORMAT English

Scenario Engineer-to-Order: Project Planning and Scheduling

SAP AGNeurottstr. 1669190 WalldorfGermanyScenario Installation Guide


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 the express permission of SAP AG. The information contained herein may be changed without prior notice.

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

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

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

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

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

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








Typographic Conventions

Type StyleDescription

Example textWords or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example textScreen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.






153.1Building Block: Connectivity

163.2Building Block: Production Planning Part I

163.3Building Block: PS Integration

173.4Building Block: Replication

203.5Building Block: Production Planning Part II

213.6Building Block: SCM Monitoring

223.7Building Block: Detailed Scheduling

234Test and Use

Engineer-to-Order: Project Planning and Scheduling - 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 which building 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 you move to the next.

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 a detailed description of the various software components (SAP_BASIS, ), their releases and support package levels, refer to the System Requirements for the document SAP Best Practices for SCM 4.1 Scenarios, which you can find on the SAP Best Practices for SCM CD.

Installation Considerations and Options

The scenario Engineer-to-Order: Project Planning and Scheduling is made up of the following building blocks:


Replication SCM

PS Integration Production Planning

Detailed SchedulingThis scenario demonstrates one way of using the building blocks listed above. You can also use these building blocks in different combinations for other scenarios or scenario variants, using this scenario as a reference.

Furthermore, we assume that the products used here are produced in a project driven manufacturing process, which has been defined by the SAP in production module. The major focus is on the capacity leveling. 2 Preparation

The following chapter provides a general description of the building block concept and tells you how to work with the Best Practices documentation.

The Prerequisites section contains important scenario-specific information and lists the SAP Notes that you have to implement in your system. In this section, you can also find some master data considerations.

2.1.1 Essential Information

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

The following section 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 successful installation of a scenario. Building Blocks: Concept

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

Building blocks:

Are reusable, business process-oriented, preconfiguration units, which you simply have to assemble 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 that can 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. Building Blocks: Installation

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

The number and sequence of the building blocks depends 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 is available on the documentation CD.

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 steps in 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 the documentation CD. Installation Options


You can implement an entire SAP Best Practices scenario or install individual building blocks to 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 and describes

which building blocks are required for the scenario

the installation sequence for these building blocks

the scope of the implementation activities for each b