S39 Scen InstallGuide en De

SAP SCM 4.1

November 2004

English

ScenarioAdvanced Repetitive Manufacturing

SAP AGNeurottstr. 1669190 WalldorfGermany

Scenario Installation Guide

SAP Best Practices Scenario Advanced Repetitive Manufacturing: 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


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.

© SAP AG Page 3 of


Content

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

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

2.1 Essential Information...............................................................................................6

2.2 Installation Considerations and Options................................................................12

2.3 Prerequisites..........................................................................................................12

3 Installation.................................................................................................................... 14

3.1 Building Block Connectivity....................................................................................14

3.2 Building Block CMDS (Configuration Part 1).........................................................14

3.3 Building Block Replication.....................................................................................15

3.4 Building Block SCM Collaboration Settings...........................................................20

3.5 Building Block Production Planning.......................................................................21

3.6 Building Block CMDS (Configuration Part 2).........................................................22

3.7 Building Block Backorder Processing....................................................................23

3.8 Building Block SCM Monitoring.............................................................................25

4 Test and Use................................................................................................................26

© SAP AG Page 4 of


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.

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.

© SAP AG Page 5 of 26


2 Preparation

2.1 Essential InformationRead 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 Building Blocks: ConceptThe 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.2 Building Blocks: InstallationTo 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.3 Installation Options

UseYou 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 InstallationA 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 InstallationYou 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 ScenarioIf 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 InstallationIf 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.4 Documentation

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 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.4.1 Documentation Overview

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



2.1.5 Uploading Configuration and User Roles

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

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

ResultYou 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 Make-to-Order with Component Availability Check is made up of the following building blocks:

Connectivity

Replication

SCM Collaborative Settings

Demand Planning

Production Planning

Collaborative of Delivery Schedules

SCM Monitoring

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 in this scenario are produced in a repetitive manufacturing process. The production process should be kept as simple as possible; the focus is on capacity leveling between different production lines.

2.3 Prerequisites

2.3.1 SAP NotesAdditional 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.

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

2.3.1.1 SAP Notes Building Block Production PlanningIf you intend to work with the product planning table (relevant for Repetitive Manufacturing), following notes are required:

SAP Note # Component Description



2.3.2 Master DataSAP 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

Rating routings

Repetitive profiles

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

Purchase Info. Record for purchased material

Sales scheduling agreement for finished goods

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.

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

If no master data exists, we suggest that you use the following building blocks from SAP Best Practices for Automotive as a reference to set up the data and the necessary settings. Note that these SAP Best Practices versions will not be available before July 2004:

SAP Best Practices for Automotive : Building block A82



3 Installation

3.1 Building Block Connectivity

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

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

3.2 Building Block CMDS (Configuration Part 1)

UseThe configuration of the building block CMDS - Collaborative Management of Delivery Schedules is divided into two separate parts.

You need to complete the configuration of the first part of the Collaborative Management of Delivery Schedules building block before you carry out the data replication (building block Replication).

The second part of the Collaborative Management of Delivery Schedules building block needs to be configured after you have completed the data replication (building block Replication).

PrerequisitesYou have installed the building block Connectivity.

Procedure1. In the configuration guide of building block Collaborative Management of Delivery Schedules,

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

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

3. Carry out all activities as described in the section Configuration Part 1 – Before Data Replication.



3.3 Building Block Replication

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

PrerequisitesYou have correctly installed the building block Connectivity.

Procedure1. In the configuration guide of building block Replication, read the Preparation section and


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 (Configuration Guide Data Replication Creating Integration Model onwards).

4. Create integration models according to the following instructions. For this scenario, we recommend that you create at least 3 different integration models in the following sequence:

Integration Model for Customizing

Model Name REM-CUST

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

APO Application CUST

Material Independent Objects Values

ATP Customizing select



Integration Model for Master Data

Model Name REM-MAST

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

APO Application MASTERDATA

Material Dependent Objects Values

Materials Material AS82*, MRP type X0

Plants BP01

Purchase info. Records For Material AS82*

ATP Check select

SA Items For Material AS82-3000

Material Independent Objects Values

Customers

Vendors

Work Centers

Select the checkbox 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.



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

Field name User action and values

Model Name REM-PDS

Logical System Enter your target system name

APO Application PDS

Material Dependent Objects General Selection Optionsfor Materials

Values

PDS (R/3) Material AS82-3000

Plant BP01

PDS

PDS Type PP/DS

Prod. Version 0001

Routing Select. Detailed plng




Integration Model for Transaction Data:

Model Name REM-TD

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

APO Application TRANSDATA

Material Dependent Object

e.g. Material AS82*

Storage Loc. Stock

Sales Orders

Planned Orders

Prod. Order

POs and PReqs

Manual Reserv.

Material Independent Objects

Shipments


Activating Integration ModelsIn 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 DefinitionIn the configuration guide of the Replication building block, refer to the activity under Data Replication Additional Customizing for Replication Maintaining Distribution Definition and make following entries

In the activity Maintaining Distribution Definition (Replication configuration guide

Publication Type

Location No. Logical System SAP Rel.

External Procurement

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

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

AS7CLNT001

e.g. 470

In-house Production

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

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

AS7CLNT001

e.g. 470

ResultYou 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.4 Building Block SCM Collaboration Settings

UseThis building block contains the configuration steps that are required to use collaborative supply and demand planning in your APO system.

PrerequisitesYour system landscape must be set up to enable the exchange of messages via EDI.

Procedure1. In the configuration guide of building block SCM Collaboration Settings, read the Preparation

section and upload the configuration roles for this building block.

2. Carry out the following activities described in the configuration guide of building block SCM Collaboration Settings:

EDI Settings for Collaborative Management of Delivery Schedules

ResultYou have set up the configuration for collaborative settings in your SAP system and can start with the configuration of the next building block.



3.5 Building Block Production Planning

UseThis building block contains the configuration steps that are required if you want to use Production Planning functions in your APO system.

Procedure1. In the configuration guide of building block Production Planning, read the Preparation section

and upload the configuration role for this building block.

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

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

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

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.

4. In the Configuration section, perform all activities of the chapter Settings for Advanced Repetitive Manufacturing

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

ResultYou have set up the configuration for production planning in your SAP system and can proceed with the configuration of the next building block.



3.6 Building Block CMDS (Configuration Part 2)

UseThis building block contains the configuration steps that are required to use Collaborative Management Delivery Schedules in your APO system. Some steps you should already finished the installation in the above installation steps.

Procedure1. In the configuration guide of building block Collaborative Management of Delivery Schedules,

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 Checking Master Data in APO after Replication Configuration Setting Parameters for Backorder Processing Configuration Planning Table Setting for CMDS

ResultYou have set up the configuration for Collaborative Management of Delivery Schedules in your SAP system and can start with the configuration of the next building block.



3.7 Building Block Backorder Processing

UseThis building block contains the configuration steps that are required to use backorder processing functions in Collaborative Management of Delivery Schedules.

Procedure1. In the configuration guide of building block Backorder Processing, read the Preparation

section and upload the configuration roles for this building block.

2. In the Backorder configuration guide, go to the section Configuration Setting for Backorder Processing and carry out the following activities:

Activating Backorder Processing Define Filter Type

For step 2, use the following table content


Filter Type Enter the filter type name, e.g. ZCMDS

For step 4. use the content in the following table


Category Enter the ATP category, e.g.

BM for sale order

HC for release of scheduling agreement

For step 6, use the following informationField name User action and ValuesMATNR Product

PLANT Plant location

Define Sorting ProfileFor step 2, use following table contentField name User action and values

Sort profile Specify the sort profile, e.g. ZCMDS.

For step 4. use the content in the following tableField name Sequence

MATNR 1

3. In the section Configuration Creating Variants, carry out the following activities:

Creating Filter VariantFor step 2, use the following content:




Filter type Enter the filter type name, e.g. ZCMDS

For step 3, use the information in this table then save as variant as ZCMDS:


Product Enter the product, e.g. AS82-3000.

Plant location Enter the plant if you want to select orders with the plant as the source location e.g. PLBP01/KD6416.

Creating Variant for BOP Background ProcessingFor step 2, use the following information and save the variant as ZCMDS:


Name Enter the job name, e.g. ZCMDS.

Filter type Enter the filter type, e.g. ZCMDS.

Variant name Enter the filter variant created in the previous step, e.g. ZCMDS.

Sort profile Enter the sort profile name, e.g. ZCMDS.

For step 3, use the information in the following table:


Product Check Select

Enhd. Confirm Logic

Select

Product Allocation

Deselect

Forecast Deselect

Customization Deselect

Execution Mode Choose the option Update Change

For step 6, save the variant name as ZCMDS.

ResultYou have set up the configuration for Backorder Processing in your SAP system and can start with the configuration of the next building block.



3.8 Building Block SCM Monitoring

UseThe building block SCM Monitoring contains the necessary configuration data in order to be able to perform monitoring in the APO System.

Procedure1. In the configuration guide of building block SCM Monitoring, read the Preparation section and


2. Carry out all activities from the SCM Monitoring configuration guide:

ResultAll relevant settings for implementing the scenario-specific functions of SCM Monitoring in the SAP APO system are processed.



4 Test and UseYou have successfully installed the scenario Advanced Repetitive Manufacturing. To test the business application of this scenario, refer to the business process procedure Advanced Repetitive Manufacturing, which gives you detailed step by step instructions on how to use the different functions in SAP R/3 and SAP APO. To test the business scenario simply work through the business process procedure.


Date post:	20-Feb-2016
Category:	Documents
Upload:	mahendra-pande
View:	234 times
Download:	0 times

S39 Scen InstallGuide en De

Documents