SAP LO-Planning

Business Process Procedures

EHP4 for SAP ERP 6.0June 2010English

APOLogistics Planning (144)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBusiness Process Documentation

Copyright

Copyright 2010 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.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.Icons

IconMeaning

Caution

Example

Note

Recommendation

Syntax

External Process

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.

Contents

5Logistics Planning

51Purpose

52Prerequisites

52.1Master Data and Organizational Data

62.2Business Conditions

62.3Preliminary Steps

72.4Roles

83Process Overview Table

104Process Steps

104.1Sales and Operation Planning

134.2Long Term Planning

235Follow-Up Processes

235.1Operational Production Planning and Control

246Appendix

246.1Reversal of Process Steps

246.2SAP ERP Reports

Logistics Planning

1 Purpose

The purpose of logistics planning is to make sure that future demand can be satisfied by your companys available resources and to point out situations where demand cannot be met in time or in the desired quantities.

This process sometimes is called Sales and Operations Planning. The process usually takes place in a simulative mode and at an aggregated (usually product group) level. Once a feasible production plan is found that satisfies demand it can be used as the basis for operational production planning (MRP and Detailed Capacity Scheduling).

The Best Practices scenarios in this section cover the following planning workflow:

Planning/forecasting of future demand

Aggregated production planning including capacity check to check at product group level if demand can be satisfied (using the SOP functionality)

Transfer of results to Long Term Planning (using the LTP module) to enable simulation of material requirements, based on the production plans Planning takes place in separate (simulative) planning versions within LTP

Review and adjustments of planned requirements as needed

Once the simulated requirements are accepted, the demand (independent requirements) is then transferred to active demand management for detailed MRP and Production Planning / Scheduling in the active version.

2 Prerequisites

2.1 Master Data and Organizational Data

A range of indispensable master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company, and master data that suits its operational focus, such as master data for materials, vendors, customers, and so on.This master data usually consists of standardized SAP Best Practices default values and enables you to go through the process steps of this scenario.

You can test the scenario with other material, or organizational data for which you have created master data. To find out how to create master data, refer to the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Master dataValueOther Master DataBus. ConditionComments

Product Group

Level 100001B001

You have completed all steps described in the Business Process Documentation Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue Planning (172).

The product groups corresponds to the product hierarchies

Product Group

Level 200001B000100000001

Product Group

Level 200001B000100000002

Product Group

Level 200001B000100000003

Plant1000(1100)

SOP version 001Use these versions in the demo script

LTP Version 001Use these versions in the demo script

2.2 Business Conditions

The business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scenarios. As a consequence, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

Business conditionScenario

You have completed all steps described in the Business Process Documentation Prerequisite Process Steps (154).Prerequisite Process Steps (154)

You have completed all steps described in the Business Process Documentation Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue Planning (172). In this scenario, you perform revenue planning. The result is a sales plan in value and/or quantity. Usually the sales plan is based on the sales history and is in quarterly, monthly, or weekly buckets.Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue Planning (172)

You have completed all steps described in the Business Process Documentation Sales Quantity forecast (179).Sales Quantity forecast (179)

2.3 Preliminary Steps

No preliminary steps are required to test this scenario.

2.4 Roles

Use

The following roles must have been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You do not need these roles if you are not using the NWBC interface, but the standard SAP GUI.

Prerequisites

The business roles have been assigned to the user who is testing this scenario.

Business roleTechnical nameProcess step

Employee (Professional User)SAP_NBPR_EMPLOYEE-SAssignment of this role is necessary for basic functionality.

Strategic PlannerSAP_NBPR_STRATPLANNER-SAll process steps

3 Process Overview Table

Process stepExternal process referenceBusiness conditionBusiness roleTrans-action codeExpected results

Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue PlanningSee scenario Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue Planning (172)See scenario (172)See scenario (172)The sales plan is created.

Sales Quantity forecast (179)See scenario Sales Quantity forecast (179)See scenario (179)See scenario (179)The sales plan is created.

Demand Verification (Check Sales Plan)After sales figures have been transferred to SOP Strategic PlannerMC76Sales Plan has been verified

Create Rough-Cut Production PlanAfter Sales plan has been checkedStrategic PlannerMC76Production Plan created

Transfer Rough Cut Production plan to Inactive Demand Management Production Plan has been checkedStrategic PlannerMC75The Production Plan from SOP has been transferred to inactive demand management

Create Long Term Planning Scenario Before running simulated LTP MRPStrategic PlannerMS31LTP Planning scenario is created

Execute LTP MRP RunStrategic PlannerMS01The LTP MRP run is simulated.

Evaluate Capacity RequirementsStrategic PlannerCM38Capacity consumption updated on cost center

Activate a planned independent requirements versionYou have evaluated and adjusted the simulative planning result Strategic PlannerMS32Planned independent requirements version is activated for planning scenario

Copy to Demand Management (active version)Strategic PlannerMS64Active version created in Demand Management

Operational Production Planning and ControlSee all production scenariosSee all production scenarios See all production scenarios See all production scenarios

4 Process Steps

4.1 Sales and Operation Planning

Sales & Operation Planning (SOP) is the link between sales planning and manufacturing.

It is a forecasting and planning transaction to enable sales, production, inventory targets to be reached based on historical, existing, and estimated future data. In the process described below we use SOP to:

Verify the sales (demand) plan coming from COPA or other sources

Create a Rough-cut production plan aimed to satisfy demand and to meet inventory targets

Visualize capacity utilization of the critical resources (usually the bottleneck resources) to verify the feasibility of the plan at an aggregated level.

SOP is suitable for long- and medium-term planning.

In this process, you view the S&OP figures. This is done after sales figures have been transferred from CO-PA to SOP.

You can visualize the following key figures

Sales plan

Production plan

Projected Stock

4.1.1 Demand Verification (Check Sales Plan)

Use

In this activity, you check the sales plan at material level. In this scenario it is assumed that the sales plan has been created at product group level.

Therefore you can disaggregate your sales figures to a material to verify demand at an aggregated level.

Also the opposite direction is possible (but not shown in this scenario): If your sales plan has been created at product group level you can disaggregate the plan according to predefined proportional factors to the material level. In this case it is useful to define the proportional factors according to historical sales figures to come to realistic forecasts at material level.

Prerequisites

This can be done after sales figures have been transferred to SOP from CO-PA.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP menuLogistics ( Production ( SOP ( Disaggregation ( Break Down PG Plan

Transaction codeMC76

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business roleStrategic Planner(SAP_NBPR_STRATPLANNER-S)

Business role menuProduction ( SOP ( Disaggregation ( Disaggregation: Planning

2. On the initial screen, make the following entries:

Field nameDescriptionUser action and valuesComment

Product group00001B000100000001Product group ID defined in central master data BB in layer 2.

Plant1000Production Plant

Inactive versionSelect the button.

Version001Check which version must be used

3. Choose Inactive version.

4. In the Product group members dialog box, select the materials.

5. In the Disaggregation dialog box, select Create sales plans and Disaggregate sales plan and choose Enter.

6. If the Check proportions dialog box displays, choose Yes.

7. Save your entries.Result

You have viewed the S&OP figures on product group level and created the sales plan on material level based on the sales plan on product group level.

4.1.2 Create Rough-Cut Production Plan

Use

In this activity, you generate the rough cut production plan based on your sales forecast. For this you have several options (see below).

Procedure



SAP menuLogistics ( Production ( SOP ( Disaggregation ( Break Down PG Plan



Business roleStrategic Planner(SAP_NBPR_STRATPLANNER-S)

Business role menuProduction ( SOP ( Disaggregation ( Disaggregation: Planning

You are still in the transaction for Demand verification (see previous chapter) and continue without leaving it. If you have left the transaction run through step 1 - 5 of this process before continuing with the next step.

2. From the menu, choose Edit ( Create production plan ( Synchronous to sales. This makes production figures equal to sales at product group and material levels.

3. In standard SOP, additional strategies for generating production plants exist. These can be activated from the following menu path:Edit ( Create production plan ( a. Production quantities are the same as sales quantities in each period ("synchronous to sales")

b. Production quantities are such that target stock levels are reached

c. Production quantities are such that target days supplies are reached

d. Production quantities are such that the stock level at the end of each period is zero.

Result

You have created the production plan on material level based on the sales plan on product group level.4.1.3 Transfer Rough-Cut Production Plan to Inactive Demand Management

Use

In this activity, you transfer the inactive version of the production plan from SOP to Demand Management where the quantities are posted as planned independent requirements.

For several purposes you can post the production plan at first in an inactive version.

In our scenario we use inactive versions for the following purposes:

Version 001 for simulation and long term procurement purposes (forecast)described in this document

Version 002: for supporting the annual budgeting process (see 173: SOP through Long Term Planning Transfer to LIS/PIS/Capacity)

Procedure


SAP menuLogistics ( Production ( SOP ( Planning ( For Product Group ( Transfer Product Group to Planning



Business roleStrategic Planner

(SAP_NBPR_STRATPLANNER-S)

Business role menuProduction ( SOP ( Product Group ( Transfer PG to Demand Management

2. Make the following entries:


Product group00001B000100000001


Version001 Selectable from dropdown.

Depends on version used in scenario: Quarterly Plan - Sales Quantity Forecast with CO-PA (179)

Production plan for material or PG memberSelected

From dateTypically first day of current month

To dateEighteen months in the future

Requirements typeLeave blank

Version01

ActiveDeselected

Make sure that you deselect Active on the initial screen to make sure it is inactive in demand management. To transfer a single material, use transaction MC74.

3. Choose Transfer now.

Result

The inactive version is transferred to demand management. To display the inactive version for a single material in Demand Management, use transaction MD63 (or menu path Logistics ( Production ( Production Planning ( Demand Management ( Planned Independent Requirements ( Display).

4.2 Long Term Planning

In long-term planning, future demand programs are simulated within a planning run. This allows you to calculate capacity requirements, activity type requirement of the cost centers, and of the requirement of purchased parts.

The demand programs that can be simulated may include planned independent requirements and/or sales orders.

You can evaluate and optimize the simulation regarding material requirements planning, capacity planning, order volumes, purchasing budget, cost center planning, and inventory controlling. Following the evaluation of the simulative planning results, you can replace the current demand program with the preferred version in long-term planning and can continue it there.

You can transfer the data for external procurement to the purchasing information system using a special report and evaluate it there.

The principle of long-term planning is to simulate different versions of the demand program. The simulation can take into account operative data (for example, master data, sales orders, purchase orders, production orders).

The simulation can be used to optimize the demand program and the production and procurement data regarding material requirements planning, capacity planning, order volumes, purchasing budget, cost center planning, and inventory controlling.

Long-term planning can also be executed based on operative master data: BoMs, routings, work centers, and material masters. This means you do not have to create any new operative data.

4.2.1 Create Long Term Planning Scenario

Use

For simulation purposes, you set up LTP-Planning scenarios that represent planning areas you can use independently from each other.

In this activity, you create the LTP Planning Scenario.

If the LTP planning scenario already exists, use transaction MS32 to make changes.

Procedure


SAP menuLogistics ( Production ( Production Planning ( Long-Term Planning ( scenario ( Create

Transaction codeMS31




Business role menuProduction ( Production Planning ( Long-Term Planning ( Create Planning Scenario

Always use scenario 001. If the scenario already exists, change the scenario according to the steps described below. Choose Planning Scenario ( Change or switch to change mode. Choose Edit ( Cancel Release to reset the released status to change the existing values.



Planning scenario001

Always use planning scenario 001. If the scenario already exists skip this process step.

Long-term planningSelected

3. Choose Enter.



From date


Dep.reqmts for reorder point materialsSelected

Consider sales ordersSelected

Include firm receiptsSelected

Include firm purchase requisitionsSelected

Include firm planned ordersSelected

5. Choose Planned Independent Requirements.

6. In the dialog box, choose New entry.



Version01Inactive version from demand management

From date


8. Choose Confirm.

9. Choose Plants.

10. In the dialog box, choose New entry.



Planning plant1000You can repeat the steps for all planning plants.

12. Choose Confirm.

13. Choose Release and Save.

Result

The LTP Planning scenario is created. Make a note of the Planning Scenario number here:

_________

4.2.1.1 Execute LTP MRP Run

Use

In this activity, you simulate the execution of the LTP MRP run.

Procedure



SAP menuLogistics ( Production ( Production Planning ( Long-term Planning ( Long-term planning ( Planning run ( Online


2. On the Long-Term Planning Run screen, enter the following entries:


Planning Scenario


Display material listSelected

Scheduling2Lead time scheduling and capacity planning

3. Choose Enter.

4. The system displays the message Please check input parameters.

5. Choose Enter.

6. The system displays the message To start the planning run, press enter. Choose Enter.

Use transaction MS04 to check the planning results for planning scenario 001, material Finished Good MTO (for example F1000-M1) in plant 1 (1000) or in the NWBC role menu Production ( Production Planning ( Long-Term Planning( Planning Scenario: Stock/Reqmts List Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business RoleBusiness roleStrategic Planner


Business role menuProduction ( Production Planning ( Long-Term Planning ( Long-Term Planning: Total Planning

1. Select the planning scenario you created one step before, choose button Long-Term Planning and select Long-Term Planning Run Online from the menu.

2. On the Long-Term Planning Run screen, check the following parameters and press enter.


Planning Scenario


Display material listSelected

Scheduling2Lead time scheduling and capacity planning

3. The system displays the message Please check input parameters.

4. Choose Enter.

5. The system displays the message To start the planning run, press enter. Choose Enter.

Use transaction MS04 to check the planning results for planning scenario 001, material Finished Good MTO (for example F1000-M1) in plant 1 (1000) or in the NWBC role menu Strategic Planning ( Long-Term Planning (LTP) ( Planning Scenario: Stock/Reqmts List ResultYou have run the simulated LTP MRP.

4.2.1.2 Evaluate Capacity Requirements

Use

In this activity, you perform capacity planning for all relevant work centers you want to check.

After you run this activity, you can assess if the plan is acceptable.

Procedure


SAP menuLogistics ( Production ( Production Planning ( Long-Term Planning ( Evaluations ( Capacity requirements ( Work centers

Transaction codeCM38

2. Enter Profile YBLTP01 - LTP: Capacity requirements for AOP.

Use transaction SU01 or SU3 (SAPGUI) to predefine the profile in your user parameter or in the role menu (NWBC) IT-Administration ( User Management ( User Maintenance (Role: SAP_NBPR_IT_ADMIN-S)

Parameter ID: CYX

Parameter Value: YBLTP01

3. Make the following entries


Planning Scenario Long-Term PlanningFrom previous steps

Work CenterSelect a work center such as Assembly

PlantPlant 1 (1000)

4. From the menu, choose Settings General and make / check the following entries:

Field nameUser action and values

Cumulation of requirements X

HierarchyTOT_PLANT

Plant1000

Entry typeD

Start ( )

Int.finish (mm/yyyy)

5. Choose Standard Overview.

6. Repeat this activity for each work center of your planning model (which is used in the routings of the materials that have been planned).

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role



Business role menuProduction ( Production Planning ( Long-Term Planning ( Capacity Leveling L-T Planning

1. Select the planning scenario you created before.

2. On the Capacity Planning: Selection screen, choose More ( Planning ( Profiles ( Overall profile.3. Select the profile YBLTP01 - LTP: Capacity requirements for AOP and choose Continue.

Use transaction SU01 or SU3 (SAPGUI) to predefine the profile in your user parameter or in the role menu (NWBC) Administration ( User Management ( User Maintenance (Role: SAP_NBPR_IT_ADMIN-S)

Parameter ID: CYX

Parameter Value: YBLTP01

4. Make the following entries


Planning Scenario Long-Term PlanningFrom previous steps

Work CenterSelect a work center for example Assembly

PlantPlant 1 (1000)

5. From the menu, choose More( Settings General and make / check the following entries:


Cumulation of requirements X

HierarchyTOT_PLANT

Plant1000

Entry typeD

Start ( )

Int.finish (mm/yyyy)

6. Choose Continue and Standard Overview.

7. Repeat this activity for each work center of your planning model (which is used in the routings of your planed materials).

Result

Capacity planning has been checked. If the plan is acceptable, you can execute the next step.

4.2.1.3 Activate a planned independent requirements version

Use

Once you have evaluated and adjusted the simulative planning result, you can activate a planned independent requirements version in the planning scenario and, if necessary, you can give it a new version number. As the validity period of the new version, the system either enters the period recorded when maintaining the simulative planned independent requirements version, or, if no period has been maintained here, the system records the planning period of the planning scenario. Once you have activated the planned independent requirements version, it is valid for operative planning.

Procedure


SAP menuLogistics ( Production ( Production planning ( Long-Term Planning ( scenario(> Change




Planning scenarioEnter a new number and description.

3. Choose Activate ind.req.



VersionSelected

Target version00Active version

Test modeDeselected

Create listSelected

5. Choose Activate.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business RoleBusiness roleStrategic Planner


Business role menuProduction ( Production Planning ( Long-Term Planning ( Change Planning Scenario

1. Make the following entries and choose Enter:


Planning scenarioChoose an existing scenario (001).

2. Choose Activate Independent Requirements.



VersionSelected

Target version00Active version

Test modeDeselected

Create listSelected

4. Choose Activate.

Result

You have activated your planned independent requirements version.

4.2.1.4 Copy to Active Demand Management

Use

Alternatively to the previous step you can copy the LTP Version 01 into an active version (such as 00). In this activity, you create an active version in Demand Management by the following procedure.

The advantage of this step is the activation in batch mode.

Procedure


SAP menuLogistics ( Production ( Production Planning ( Long-Term Planning ( Planned indep.reqmts ( Copy version



Business roleSAP_AIO_STRATEGICPLANNER-S(Strategic Planner-Professional User)

Business role menuProduction ( Production Planning ( Demand Management ( DM) ( Create Simulation Version



PlantEnter all plants.

MaterialLeave blank

From date


Source version01Inactive version from demand management

Target version00

Target version activeSelected

No database changes (Simulation)Deselected

3. Choose Execute.

Result

An active version is created in Demand Management. To display the active version for a single material in Demand Management, use transaction MD63 (or menu path Logistics ( Production ( Production Planning ( Demand Management ( Planned Independent Requirements ( Display).

5 Follow-Up Processes

You have finished all activities that are part of the business process described in this document.

To accomplish subsequent activities of this business process, carry out the process steps described in one or more of the following scenarios, using the master data from this document.

5.1 Operational Production Planning and Control

Use

In this activity, you may run the different production scenarios.

Procedure

To execute this activity, run the following scenarios

Make-to-Stock Production - Discrete Industry (145)

Make-to-Stock Production - Process Industry (146)

Make-to-Order Production with Variant Configuration (147)

Make-to-Order Production w/o Variant Configuration (148)

Repetitive Manufacturing (149).

6 Appendix

6.1 Reversal of Process Steps

In the following section, you can find the most common reversal steps that you can take to reverse some of the activities described in this document,

Create Long Term Planning Scenario

Transaction code ( SAP GUI)MS31

Reversal:Change Planning scenario

Transaction code ( SAP GUI)MC75

Business roleSAP_BPR_STRATEGICPLANNER-S

Business role menuStrategic Planning ( Long-Term Planning (LTP) ( Change Planning Scenario

CommentYou can change the planning scenario

6.2 SAP ERP Reports

Use

The table below lists the most frequently used reports that help you to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents that provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221) Logistics Processes: SAP ERP Reports for Logistics (222)The descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

Reports

Report titleTransaction code (SAP GUI)Business Role (NWBC)Business Role Menu (NWBC)Comment

Long-Term Capacity PlanningCM38Strategic PlannerProduction ( Production Planning ( Long-Term Planning ( Capacity Leveling L-T PlanningThe capacity evaluation is displayed.

Change PlanMC82Strategic PlannerProduction(SOP ( Change Plan for Product GroupDisplay of planning version.

Evaluation of Product Group PlanningMD47Production PlannerProduction ( Evaluations( Reports ( Product Group Planning Evaluation Planning situation is displayed.

Long-Term Planning: MRP-listMS05Strategic PlannerProduction ( Production Planning ( Long-Term Planning ( Long-Term Planning: Display MRP ListSimulation of MRP-list

SAP AG

Page 25 of 25

_1118216528.bin

SAP LO-Planning

Documents

Transcript of SAP LO-Planning