144_BPP_EN_US

7/29/2019 144_BPP_EN_US

http://slidepdf.com/reader/full/144bppenus 1/25

EHP4 for SAP ERP6.0

June 2010

English

Logistics Planning (144)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Documentation

7/29/2019 144_BPP_EN_US


SAP Best Practices Logistics Planning (144): BPD

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 expresspermission 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, Systemz10, 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 WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand 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, WebIntelligence, 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 inother countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 25

7/29/2019 144_BPP_EN_US



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

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.

EXAMPLETEXT

Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example, SELECTand 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 namesof installation, upgrade and database tools.

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

Exampletext

Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

<Exampletext>

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


7/29/2019 144_BPP_EN_US



Contents

Logistics Planning............................................................................................................................... 5

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

2 Prerequisites.....................................................................................................................................5

2.1 Master Data and Organizational Data........................................................................................ 5

2.2 Business Conditions ..................................................................................................................6

2.3 Preliminary Steps....................................................................................................................... 6

2.4 Roles.......................................................................................................................................... 7

3 Process Overview Table...................................................................................................................8

4 Process Steps.................................................................................................................................10

4.1 Sales and Operation Planning..................................................................................................10

4.2 Long Term Planning.................................................................................................................13

5 Follow-Up Processes...................................................................................................................... 235.1 Operational Production Planning and Control........................................................................ ..23

6 Appendix......................................................................................................................................... 24

6.1 Reversal of Process Steps.......................................................................................................24

6.2 SAP ERP Reports ..................................................................................................................24


7/29/2019 144_BPP_EN_US



Logistics Planning

1 PurposeThe purpose of logistics planning is to make sure that future demand can be satisfied by your company’s available resources and to point out situations where demand cannot be met in time or inthe desired quantities.

This process sometimes is called Sales and Operations Planning . The process usually takes placein a simulative mode and at an aggregated (usually product group) level. Once a feasible productionplan 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 Prerequisites2.1 Master Data and Organizational Data

A range of indispensable master and organizational data was created in your ERP system in theimplementation 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 enablesyou to go through the process steps of this scenario.

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

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


7/29/2019 144_BPP_EN_US



Master data

Value Other Master Data

Bus. Condition Comments

ProductGroup

Level 1

00001B001 You have completed all steps described in theBusiness ProcessDocumentation Sales Qty Budget and Transfer toSOP (with CO-PA),Revenue Planning (172).

The productgroupscorresponds tothe producthierarchiesProduct

Group

Level 2

00001B000100000001

ProductGroup

Level 2

00001B000100000002

ProductGroup

Level 2

00001B000100000003

Plant 1000(1100)

SOPversion

001 Use theseversions in thedemo script

LTPVersion

001 Use theseversions in thedemo 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 thefollowing processes and fulfilled the following business conditions before you can start going throughthis scenario:

Business condition Scenario

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

Prerequisite ProcessSteps (154)

You have completed all steps described in the Business ProcessDocumentation Sales Qty Budget and Transfer to SOP (with CO-PA), Revenue Planning (172). In this scenario, you performrevenue 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 ProcessDocumentation Sales Quantity forecast (179).

Sales Quantity forecast (179)

2.3 Preliminary Steps

No preliminary steps are required to test this scenario.


7/29/2019 144_BPP_EN_US



2.4 Roles

Use

The following roles must have been installed to test this scenario in the SAP NetWeaver BusinessClient (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, butthe standard SAP GUI.

Prerequisites

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

Business role Technical name Process step

Employee(Professional User)

SAP_NBPR_EMPLOYEE-S Assignment of this role isnecessary for basic functionality.

Strategic Planner SAP_NBPR_STRATPLANNER-S

All process steps


7/29/2019 144_BPP_EN_US



3 Process Overview TableProcess step External

processreference

Businesscondition

Businessrole

Trans-actioncode

Expectedresults

Sales Qty Budget and Transfer toSOP (with CO-PA), RevenuePlanning

See scenario

Sales Qty Budget and Transfer toSOP (withCO-PA),RevenuePlanning (172)

Seescenario

(172)

Seescenario

(172)

The sales planis created.

Sales Quantity forecast (179)

See scenario

SalesQuantity

forecast (179)

Seescenario

(179)

Seescenario

(179)

The sales planis created.

DemandVerification(Check SalesPlan)

After salesfigures havebeentransferredto SOP

StrategicPlanner

MC76 Sales Plan hasbeen verified

Create Rough-Cut ProductionPlan

After Salesplan hasbeenchecked

StrategicPlanner

MC76 ProductionPlan created

Transfer Rough CutProductionplan to InactiveDemandManagement

ProductionPlan hasbeenchecked

StrategicPlanner MC75 The ProductionPlan from SOPhas beentransferred toinactivedemandmanagement

Create LongTerm PlanningScenario

BeforerunningsimulatedLTP MRP

StrategicPlanner

MS31 LTP Planningscenario iscreated

Execute LTPMRP Run

StrategicPlanner

MS01 The LTP MRPrun issimulated.

EvaluateCapacityRequirements

StrategicPlanner

CM38 Capacityconsumptionupdated oncost center

Activate aplannedindependent

You haveevaluatedand

StrategicPlanner

MS32 Plannedindependentrequirements


7/29/2019 144_BPP_EN_US



Process step Externalprocessreference

Businesscondition

Businessrole

Trans-actioncode

Expectedresults

requirementsversion

adjusted thesimulativeplanningresult

version isactivated for planningscenario

Copy toDemandManagement(active version)

StrategicPlanner

MS64 Active versioncreated inDemandManagement

Operational ProductionPlanning and Control

See allproductionscenarios

See allproductionscenarios

See all productionscenarios

See all productionscenarios


7/29/2019 144_BPP_EN_US



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 bereached based on historical, existing, and estimated future data. In the process described below weuse SOP to:

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

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

o 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 aggregatedlevel.

Also the opposite direction is possible (but not shown in this scenario): If your sales plan has beencreated at product group level you can disaggregate the plan according to predefined proportionalfactors to the material level. In this case it is useful to define the proportional factors according tohistorical 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.

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

Option 1: SAP Graphical User Interface (SAP GUI)

SAP menu Logistics Production SOP Disaggregation Break Down

PG Plan

Transactioncode

MC76


7/29/2019 144_BPP_EN_US



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

Business role Strategic Planner

(SAP_NBPR_STRATPLANNER-S)

Business rolemenu

Production→ SOP → Disaggregation→ Disaggregation:

Planning

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

Fieldname

Description User actionand values

Comment

Product group

00001B000100000001 Product group ID defined incentral master data BB in layer 2.

Plant 1000 Production Plant

Inactiveversion

Select thebutton.

Version 001 Check which version must beused

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 andchoose 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 materiallevel 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 youhave several options (see below).

Procedure

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


SAP menu Logistics Production SOP Disaggregation Break Down

PG Plan

Transactioncode

MC76




7/29/2019 144_BPP_EN_US




Business rolemenu

Production→ SOP → Disaggregation→ Disaggregation:

Planning

You are still in the transaction for Demand verification (see previous chapter) andcontinue without leaving it. If you have left the transaction run through step 1 - 5 of thisprocess 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 beactivated from the following menu path:

Edit → Create production plan → <create production plan option>

a. Production quantities are the same as sales quantities in each period ("synchronous tosales")

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

4.1.3 Transfer Rough-Cut Production Plan to Inactive DemandManagement

UseIn this activity, you transfer the inactive version of the production plan from SOP to DemandManagement 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 menu Logistics Production SOP Planning For Product Group

Transfer Product Group to Planning

Transactioncode

MC75


7/29/2019 144_BPP_EN_US






Business rolemenu

Production→ SOP → Product Group → Transfer PG to Demand

Management

2. Make the following entries:

Field name Description User action and values Comment

Product group 00001B000100000001


Version 001 Selectable fromdropdown.

Depends on versionused in scenario:Quarterly Plan - SalesQuantity Forecast withCO-PA (179)

Production planfor material or PGmember

Selected

From date <earliest date of change> Typically first day of current month

To date <earliest date of changePLUS 18 months>

Eighteen months in thefuture

Requirementstype

Leave blank

Version 01

Active Deselected

Make sure that you deselect Active on the initial screen to make sure it is inactive indemand 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 youto calculate capacity requirements, activity type requirement of the cost centers, and of therequirement of purchased parts.


7/29/2019 144_BPP_EN_US



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, capacityplanning, order volumes, purchasing budget, cost center planning, and inventory controlling.Following the evaluation of the simulative planning results, you can replace the current demandprogram 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 aspecial report and evaluate it there.

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

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

Long-term planning can also be executed based on operative master data: BoMs, routings, workcenters, 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 canuse 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 menu Logistics Production Production Planning Long-Term

Planning scenario Create

Transactioncode

MS31




Business role

menu

Production→ 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.


7/29/2019 144_BPP_EN_US




Field name Description User actionand values

Comment

Planning

scenario

001 <enter a new number and description>

Always use planning scenario 001. If thescenario already exists skip this processstep.

Long-term planning

Selected

3. Choose Enter .


Field name Description User action andvalues

Comment

From date <current date>

To date <current date PLUS18 months>

Eighteen months inthe future

Dep.reqmts for reorder point materials

Selected

Consider sales orders Selected

Include firm receipts Selected

Include firm purchaserequisitions

Selected

Include firm planned

orders

Selected

5. Choose Planned Independent Requirements.

6. In the dialog box, choose New entry .


Fieldname

Description User action and values Comment

Version 01 Inactive version from demandmanagement

From date <current date>

To date <current date PLUS 18

months>

Eighteen months in the future

8. Choose Confirm.

9. Choose Plants.

10. In the dialog box, choose New entry .


Field name Description User action and Comment


7/29/2019 144_BPP_EN_US



values

Planning plant

1000 You can repeat the steps for allplanning 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.

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


SAP menu Logistics Production Production Planning Long-term Planning

Long-term planning Planning run Online

Transactioncode

MS01

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


Comment

Planning Scenario

<from previousstep>


Display material list

Selected

Scheduling 2 Lead time scheduling andcapacity 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 .


7/29/2019 144_BPP_EN_US



Use transaction MS04 to check the planning results for planning scenario 001, materialFinished 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 Role



Business rolemenu

Production→ 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.


Comment

Planning Scenario

<from previousstep>


Display material list

Selected

Scheduling 2 Lead time scheduling andcapacity 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, materialFinished 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

Result

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


7/29/2019 144_BPP_EN_US



Procedure


SAP menu Logistics Production Production Planning ® Long-Term Planning

Evaluations Capacity requirements Work centers

Transactioncode CM38

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 Planning

From previous steps

Work Center Select a work center such as Assembly

Plant Plant 1 (1000)

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

Field name User action and values

Cumulation of requirements X

Hierarchy TOT_PLANT

Plant 1000

Entry type D

Start ( ) <Start of budget period>

Int.finish (mm/yyyy) <End of budget period>

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




Business rolemenu

Production→ Production Planning → Long-Term Planning →

Capacity Leveling L-T Planning


7/29/2019 144_BPP_EN_US



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 Planning

From previous steps

Work Center Select a work center for example Assembly

Plant Plant 1 (1000)

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


Cumulation of requirements X

Hierarchy TOT_PLANT

Plant 1000

Entry type D

Start ( ) <Start of budget period>

Int.finish (mm/yyyy) <End of budget period>

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.3Activate a planned independent requirements version

Use

Once you have evaluated and adjusted the simulative planning result, you can activate a plannedindependent requirements version in the planning scenario and, if necessary, you can give it a newversion number. As the validity period of the new version, the system either enters the periodrecorded when maintaining the simulative planned independent requirements version, or, if no


7/29/2019 144_BPP_EN_US



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

Procedure


SAP menu Logistics Production Production planning Long-Term

Planning scenario > Change

Transactioncode

MS32



Planning scenario Enter a new number and description.

3. Choose Activate ind.req.



Version Selected

Target version 00 Active version

Test mode Deselected

Create list Selected

5. Choose Activate.




Business rolemenu

Production→ Production Planning → Long-Term Planning → Change

Planning Scenario

1. Make the following entries and choose Enter :


Planning scenario Choose an existing scenario (001).

2. Choose Activate Independent Requirements.



Version Selected

Target version 00 Active version

Test mode Deselected

Create list Selected


7/29/2019 144_BPP_EN_US



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 as00). 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 menu Logistics Production Production Planning Long-Term Planning

Planned indep.reqmts Copy version

Transactioncode

MS64


Business role SAP_AIO_STRATEGICPLANNER-S(Strategic Planner-Professional User)

Business rolemenu

Production→ Production Planning → Demand Management ( DM) →

Create Simulation Version



Comment

Plant Enter all plants.

Material Leave blank

From date <first day of currentmonth>

To date <From date PLUS18 months>

Eighteen months in thefuture

Source version 01 Inactive version fromdemand management

Target version 00

Target version active Selected

No database changes(Simulation)

Deselected

3. Choose Execute.

Result


7/29/2019 144_BPP_EN_US



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


7/29/2019 144_BPP_EN_US



5 Follow-Up ProcessesYou 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)

.


7/29/2019 144_BPP_EN_US



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 reversesome 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 role SAP_BPR_STRATEGICPLANNER-S

Business role menu Strategic Planning → Long-Term Planning (LTP) → Change

Planning Scenario

Comment You 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 informationon this business process.

You can find detailed descriptions of the individual reports in the following BPDdocuments 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 locateddirectly in the section where they belong.

Reports

Report title Transactioncode (SAPGUI)

BusinessRole(NWBC)

Business Role Menu(NWBC) Comment

Long-TermCapacityPlanning

CM38 StrategicPlanner

Production→ Production

Planning → Long-Term

Planning → Capacity

Leveling L-T Planning

The capacityevaluation isdisplayed.

Change Plan MC82 Strategic Production→SOP → Display of


7/29/2019 144_BPP_EN_US



Planner Change Plan for Product Group

planningversion.

Evaluation of ProductGroupPlanning

MD47 ProductionPlanner

Production→

Evaluations→ Reports→

Product Group Planning

Evaluation

Planningsituation isdisplayed.

Long-TermPlanning:MRP-list

MS05 StrategicPlanner

Production→ Production



Planning: Display MRP List

Simulation of MRP-list

Date post:	14-Apr-2018
Category:	Documents
Upload:	omer-sanatna
View:	218 times
Download:	2 times

144_BPP_EN_US

Documents