S44 Scen InstallGuide en De

SAP SCM 4.1

November 2004

English

Scenario Engineer-to-Order: Project Planning and Scheduling

SAP AGNeurottstr. 1669190 WalldorfGermany

Scenario Installation Guide

SAP Best Practices Engineer-to-Order: Project Planning & Scheduling: 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 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, mySAP.com, 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.

© SAP AG Page 2 of 23


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 field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

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

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

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names 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 the system exactly as they appear in the documentation.

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



Contents

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

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

2.2 Prerequisites..............................................................................................................12

3 Installation............................................................................................................................ 15

3.1 Building Block: Connectivity.......................................................................................15

3.2 Building Block: Production Planning Part I.................................................................16

3.3 Building Block: PS Integration....................................................................................16

3.4 Building Block: Replication.........................................................................................17

3.5 Building Block: Production Planning Part II................................................................20

3.6 Building Block: SCM Monitoring.................................................................................21

3.7 Building Block: Detailed Scheduling...........................................................................22

4 Test and Use........................................................................................................................ 23



Engineer-to-Order: Project Planning and Scheduling - Installation Guide

1 PurposeThis 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 RequirementsTo 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:

Connectivity

Replication SCM

PS Integration

Production Planning

Detailed Scheduling

This 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 PreparationThe 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.

2.1.1.1Building 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.

2.1.1.2Building 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.

2.1.1.3Installation Options

Use

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 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 SAP Notes 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 Installation

You may consider installing individual building blocks and not an entire scenario if one of the following 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 scenarios with specific functions.

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



Configuration of Non-Standard Scenario

If you want to configure a scenario that is not in the scope of SAP Best Practices proceed as 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 the recommended 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 building block 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 guide for your existing scenario, or choose a scenario that is very similar to check the installation 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.



2.1.1.4Documentation

Document Types and Content

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

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

Document Type

Purpose File Format

Scenario Overview

Provides a graphical overview of a scenario. MS PowerPoint

Scenario/Building Block Description

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

HTML

Scenario Installation Guide

The Scenario Installation Guide tells you which building blocks you need to install for a specific scenario and prescribes their installation sequence. It is the documentation backbone for installing a business scenario. It does not give you detailed instructions on how to install a specific building block but may contain scenario-specific configuration data. Always refer to the Scenario Installation Guide before you start installing a building block and when you have finished installing a building block.

MS Word

Building Block Configuration Guide

Each building block has a configuration guide, which describes:

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 the logical order of the installation process.

MS Word

Business Process Procedure

End-user documentation providing detailed, application-focused descriptions of business processes. Used for testing scenarios.

MS Word



2.1.1.4.1 Documentation Overview

Use

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



2.1.1.5Uploading Configuration and User Roles

Use

For each building block you want to install, there is a user menu comprising all configuration activities, 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 processes covered by this scenario

To set up the user menu for the person who is going to use this menu, you need to upload the user role file that contains this menu and assign it to the relevant user. Should there be more than 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 SAP Best Practices for SCM Documentation CD, 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 at the 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 to the 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 Installation Considerations and OptionsThe scenario ‘Engineer-to-Order: Project Planning and Scheduling’ is made up of the following building blocks:

Connectivity

Replication SCM

PS Integration

Production Planning

Detailed Scheduling

This 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.3 Prerequisites

2.3.1 SAP Notes

Additional information regarding this Best Practice scenario and all errors that became known after the delivery of the SAP Best Practices for SCM CD are documented in the SAP Note 772396

In addition, the following SAP Notes are required to run the respective sections of this scenario:



2.3.1.1 SAP Notes Building Block PS Integration

If you intend to work with the enhanced PS integration functions, you need the following SAP Notes:

SAP Note # Component Description

161028 SCM-APO-INT-RP MOD: Planned Order scheduling via APO interface

730363PS Integration

SCM-APO-PPS

Use BAdi to change the initial transferred network activities status to “deallocated”. Meanwhile, change the standard planning run logic in such a way that the components of “deallocated” activities are not considered.

693105

PS Integration

SCM-APO-INT-POR

In R/3, if the network activity is transferred to SCM, the status of this activity is changed to “Scheduled Externally” which means that it cannot be changed in R/3. This note is used to enhance the standard function so that you can unlock the activity and do data maintenance work in R/3.

711104

Heuristics

SCM-APO-INT-POR

Create new algorithm so that you can run the “Bottom up” and “Top down” heuristic for network operations.

713089

Heuristics

SCM-APO-INT-POR

Create new algorithm so that you can run the “Remove Backlog” heuristic for operations.

711105

Scheduling

SCM-APO-INT-POR

For the capacity consumption between rough-cut project planning and detailed scheduling capacity planning, order operations are planned on pool capacity resources and on work center capacities at the same time. As a consequence the order operations are displayed twice in the operations chart of the SAP APO DS planning board. This note is used to eliminate the double display.

711107SCM-APO-INT-POR

If your material uses strategy type 70, this notes can allows you to transfer type 70 to SCM without manual maintenance.

713088

Scheduling

SCM-APO-INT-POR

This note describes how a rough capacity planning in project networks and a detailed planning with planned and production orders with automated consumption can be applied for the project manufacturing with SAP SCM 4.1

723374

Scheduling

SCM-APO-PPS-DST

In the detail scheduling planning board you cannot hide unselected objects (orders or operations). This note can solve the problem.

722751

Scheduling

SCM-APO-PPS-DST

This note allows you to sort operations via their account assignment object in the table section of the Operations chart in the detailed scheduling planning board.



2.3.2 Master Data

SAP Best Practices for SCM does not provide master data in SAP R/3, as customers usually have their own master data in SAP R/3. However, the existence of master data is an essential prerequisite if you want to test this scenario.

The following list indicates which types of master data types are usually required:

Material master data

BOM

Work centers

Class and Characteristics for alternative resources (optional)

Routings

Production version in the material master data of the finished or semi-finished goods.

Purchase Info. Record for purchased material

The SD settings such as the order type, item category, and schedule line category and relevant assignment, pricing, and so on, so that you can create the sales order in the R/3 system

Standard Project Work Break Down Structure

Standard Project Network

Material assignment with standard project

Make sure that all data and settings required have been created and maintained correctly.

If no master data is available, we suggest that you use the following building blocks from SAP Best Practices for IMC as a reference to set up the data and the necessary settings.

SAP Best Practices for IMC : Building block E62

You hereby focus on the project planning and scheduling function, if you want to achieve other sales and project relevant functions, such as billing, accounting etc., you need to install the following required building blocks or scenarios from SAP Best Practices for IMC:

E33 ETO Sales Order Processing

E73 ETO Order Processing



3 Installation

Purpose

The following section tells you which building blocks you need to install for this scenario and specifies the predefined configuration sequence you have to follow for all building blocks.

For the installation of each individual building block, refer to the corresponding Building Block Configuration Guide (for manual configuration), which provide detailed instructions on how to set up the building block.

3.1 Building Block: Connectivity

Use

Connectivity refers to the interface and transfer of data and configuration settings between the 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. Implement the activities of the following sections of building block Connectivity:

Configuration Guide à Local Settings à SAP R/3

Configuration Guide à Local Settings à SAP SCM

Configuration Guide à Cross Connectivity à SAP R/3 with SAP SCM

Result

Building Block Connectivity is installed properly, you can go on to the next building block.



3.2 Building Block: Production Planning Part I

Use

Some settings of the Production Planning Building Block must be finished before the initial transfer of master data from the SAP R/3 to SAP SCM. The remaining settings of this Building Block will be performed at a later stage, after data replication

Procedure

1. In the configuration guide of building block Production Planning, read the Preparation section and upload the configuration roles for this building block.

2. Carry out the following activitiy as described in the Production Planning configuration guide:

Configuration → Settings for Project Manufacturing Defining Requirements Strategies

The remaining steps of this building block will be installed later on.

Result

The first configuration part of Production Planning is installed, and you can proceed with the next building block.

3.3 Building Block: PS Integration

Use

This building block contains the configuration steps that are required to use PS Integration in your SCM system.

Procedure

1. In the configuration guide of building block PS Integration, read the Preparation section and upload the configuration roles for this building block.

2. Carry out all activities as described in the PS Integration configuration guide.

Result

Building block PS Integration is installed, you can proceed with the installation of the next building block.



3.4 Building Block: Replication

Use

Replication refers to uploading and downloading customizing data, master data and transaction data from SAP R/3 to the SAP APO system.

Prerequisites

You have correctly installed the building block Connectivity.

Procedure

1. In the configuration guide of building block Replication, read the Preparation section and upload the configuration roles for this building block.

2. Perform all activities of the section Preliminary Steps.

3. Refer to the section Data Replication and read carefully how to create integration models, save the results and create variants (Replication configuration guide Data Replication Creating Integration Model).

4. For this scenario, we recommend that you create at least four different integration models in the following sequence:

Integration Model for Customizing

Model Name E.g. PS_CUST

Logical System Enter your target system name, e.g. APOCLNT001

APO Application E.g. CUST

Material Independent Objects Values

ATP Customizing select

Integration Model for Master Data:

Model Name E.g. PS_MAST

Logical System Enter your target system name E.g. AS7CLNT001

APO Application E.g. Masterdata

Material Dependent Object

Materials e.g. Material SE62*, MRP type X0

Plants e.g. BP01



Purchase info. Records Select and specify

Material Independent Objects

Work Centers Select and specify

Vendors Select and specify

Customers Select and specify

Integration Model for the Production Data Structure (PP/DS)

Model Name E.g. PS_PDS

Logical System Enter your target system name, e.g. APOCLNT001

APO Application E.g. PDS

Material Dependent Objects General Selection Optionsfor Materials

Values

PDS (R/3) Material

Plant BP01

PDS

PDS Type PP/DS

Prod. Version 0001

Routing Select. Detailed plng

Integration Model for Transaction Data:

Model Name E.g. S44_PS

Logical System Enter your target system name, e.g. AS7CLNT001

APO Application E.g. Transac

Material Dependent Object e.g. Material SE62*

Storage Loc. Stock select

Project Stock select

Sales Orders select

Planned Ind. Reqs select

Planned Orders select

Prod. Order select

POs and PReqs select



Manual Reserv. select

Material Independent Objects

Shipments e.g. Trans. Plant BP01

Network e.g. order type ZS02

Select the checkboxes listed in the table, if necessary, you can choose to enter the material, plant, customer, and so on, as selection criteria in the right section of the screen.

Activating Integration Models

In the configuration guide of the Replication building block, refer to the activity under Data Replication Activating Integration Model to activate the integration models you have created. Activate the integration models in the sequence in which you created them.

Distribution Definition

In the configuration guide of the Replication building block, refer to the activity under Data Replication Additional Customizing for Replication Maintaining Distribution Definition and make the following entries:

Publication Type

Location No. Logical System SAP Rel.

External Procurement

Enter your location no. e.g. PLBP01/KD6137, where you are going to execute the external procurement

Name of the target R/3 logical system e.g.

KD6CLNT137

e.g. 470

In-house Production

Enter your location no. e.g. PLBP01/KD6137, where you are going to execute the production


KD6CLNT137

e.g. 470

Project Order Enter your location no. e.g. PLBP01/KD6137, where you are going to execute the production


KD6CLNT137

e.g. 470

Additional Setting in SAP APO

1. Access the activity using one of the following navigation options:

Transaction Code /N/SAPAPO/CP3

IMG Menu mySAP SCM – Implementation Guide à Integration with SAP Components Integration of SAP SCM and SAP R/3 Basic Settings for Data Transfer Publication Maintain Object-Specific Settings

2. On the Change View: Object Specific Settings for Publication – Overview screen, choose New Entries.

3. Make the following entries:



Field name Values

Publ. Type Project Order

Retransfer Always Retransfer

4. Choose Save and go back.

Result

You have completed all activities related to the initial data transfer from the SAP R/3 system to SAP APO. You can now proceed with the installation of the next building block

3.5 Building Block: Production Planning Part II

Use

After you have completed the data replication (building block Replication), you need to configure the remaining part of the building block Production Planning configuration guide.

PrerequisiteSAP Notes 711104 and 713089 must have been installed.

Procedure

1. In the Configuration section, perform all activities of the chapter Master Data General Settings

2. In the Configuration section, perform all activities of the chapter Planning Parameters General Settings.

We suggest that you use a name such as “PS001” to denominate your own

Planner Responsible

Time Profile

Propagation Range

Variant for Production Planning Run

This allows you to distinguish these profiles from those used in other scenarios. If you follow this naming convention, be careful to assign the correct profile names in the Creating Variant for Production Planning Run.

3. In the Configuration section, perform the remaining activities of the chapter Settings for Project Manufacturing

4. In the Configuration section, the Advanced Settings chapter is optional and should only be performed by experienced users

Result

You have installed the building block Production Planning and can proceed with the configuration of the next building block.



3.6 Building Block: SCM Monitoring

Use

This building block contains the configuration steps that are required to use alert functions in SCM.

Procedure

1. In the configuration guide of building block SCM Monitoring, read the Preparation section and upload the configuration roles for this building block.

2. Carry out the following activities from the building block configuration guide:

Configuration Setting up the Alert Profiles PP/DS Alert Profile

o For step 2, make the following entries:

Field Name User Action and Values

Overall Profile PS001

Description BP: PS alert profiles



Relative time interval Select

Months Select

Months 17

Offset -5



PP/DS alert profile PS0001

Description BP: PS Alert Profile



Order Alert: Product Independent

Select

PP/DS Resource Alerts Select

Result

You have installed the building block SCM Monitoring and can proceed with the configuration of the next building block.



3.7 Building Block: Detailed Scheduling

Use

This building block contains the configuration steps that are required to use Detailed Scheduling in your SCM system.

Procedure

1. In the configuration guide of building block Detailed Scheduling, read the Preparation section and upload the configuration roles for this building block.

1. In the Configuration section, perform all activities of the chapter Master Data General Settings

2. In the Configuration section, perform all activities of the chapter Setting up Detailed Scheduling - General Settings.

We suggest that you use a name such as “PS001” to denominate your own

Work Area

Propagation Range

Time Profile

Strategy Profile

Optimization Profile

DS Planning Board Profile

Overall Profile

This allows you to distinguish these profiles from those used in other scenarios. If you follow this naming convention, be careful to assign the correct profile names in the Overall Profile.

2. In the Configuration section, perform all activities of the chapter Settings for Project Manufacturing

3. In the Configuration section, the Advanced Settings chapter is optional and should only be performed by experienced users

Result

You have installed the building block Detailed Scheduling and completed the installation of the scenario Engineer-to-Order: Project Driven Production Planning and Scheduling.

4 Test and Use You have successfully installed the scenario Engineer-to-Order: Project Driven Production Planning and Scheduling. To test the business application of this scenario, refer to the business process procedure Engineer-to-Order: Project Driven Production Planning and Scheduling, which gives you detailed step-by-step instructions on how to use the different functions in SAP



R/3 and SAP SCM. To test the business scenario, simply work through the business process procedure.


Documents

S44 Scen InstallGuide en De