Business Process Procedure 4423

8/3/2019 Business Process Procedure 4423

http://slidepdf.com/reader/full/business-process-procedure-4423 1/26

SAP ECC 6.00

June 2007

English

H03: SOP and Production

Planning

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Business Process Procedure



SAP Best Practices H03: SOP and Production Planning - BPP

Copyright

© Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9,z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP productsand 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 namesmentioned are the trademarks of their respective companies. Data contained in this document servesinformational 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 accompanying

such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 26




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 fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

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 keywords 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 asnames 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 thesystem exactly as they appear in the documentation.

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

© SAP AG of 26




Contents

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

1.1 General Information and Target User .........................................................................................5

1.2 Overview ....................................................................................................................................5

2 Prerequisites .....................................................................................................................................7

2.1 Organizational and Master Data .................................................................................................7

2.2 Installing Final Step ....................................................................................................................7

2.3 Uploading the User Role ............................................................................................................7

3 Basic Business Process ....................................................................................................................8

3.1 Creating Product Sales Planning ................................................................................... ............8

3.2 Displaying Product Sales Planning ............................................................................. ...............8

3.3 Displaying Plan before Transferring ...........................................................................................9

3.4 Transferring Planned Quantities to Sales Organization Planning (SOP) ..................................10

3.5 Confirmation of Transferred Plan .......................................................................................... ...11

3.6 Producing Legacy Data for Use as Examples ..........................................................................11

3.7 Calling up Standard Analyses Customer Applications ..............................................................12

3.8 Structure of Current Schedule Lines ........................................................................................14

3.9 Creating the Planning Hierarchy ................................................................................... ...........15

3.10 Changing the Planning Hierarchy ...........................................................................................17

3.11 Working and Navigating in the Planning Table of a Flexible Planning Structure ....................193.12 Creating Sales Plan ................................................................................................................21

3.13 Creating the Operations Plan .............................................................................................. ...23

3.14 Transferring Production Plan from SOP to Demand Management.........................................24

© SAP AG of 26




H03: SOP and Production Planning

1 Purpose

1.1 General Information and Target User

This documentation provides an instruction on how the scenario (H03: SOP and ProductionPlanning) is processed from a business point of view. It gives a step by step operation guide aswell, which the users can follow to finish the process of this scenario.

The target user of this documentation will possibly be:

Partners

Customers

1.2 OverviewThe process entitled SOP and Production Planning describes a scenario, which focuses on thefollowing:

Profitability Analysis

Analyze actual demand using historical data

Flexible planning.

Demand Management

1.2.1 Scenario with Flexible Planning

In addition to the procedure previously described using flexible planning (consistent planning), Salesand Operations Planning (SOP) is also carried out here. The result of Sales and OperationsPlanning is transferred to Demand Management (preplanning) as planned independentrequirements.

Attention must be paid to the following points:

Carry out a forecast using actual data

Create sales planning using this forecast

Derive operations planning from sales planning

Transfer Sales and Operations Planning to Demand Management/MRP

All the existing standard tools of flexible planning (for example, forecasts on the basis of actual

quantities, macros, and so on) can be used here. This section of the value chain explains only asmall selection of the available functions. For other functions, refer to the Online Documentation [LO

– Sales and Operations Planning (SOP)].

A standard information structure (S727) has been created for this scenario. This informationstructure contains the characteristics: Sold-to party , Material Group, Material , and Plant , as well asthe key figures Sales, Delivery quantity , and Production, as such. In Customizing, you can create auser-specific information structure containing any characteristics and key figures you require.Planning structure S727 is configured to carry out consistent planning. Consistent planning is a type

© SAP AG of 26




of planning in which a quantity change at a particular planning level affects all the other planninglevels (upwards and downwards).

In information structure S727, the key figure Order quantity is updated for scheduling agreementsand standard orders. The key figure Order quantity is important for carrying out planning of this type.

On the basis of this actual data (order quantity), a forecast is carried out. To create a sales plan, youcan change the result of this forecast (manually) as required.

The operations plan can be determined automatically from the sales plan by means of macros (via

specific procedures - for example, Target stock level Production or Target days' supply Production, and so on). The operations plan is subsequently transferred to Demand Management(preplanning) per plant for each material in the form of individual planned independent requirements.

This concludes the part of Scheduling Agreement Processing with Forecast Delivery Schedules,Invoice Processing and Flexible Planning.

1.2.2 Flow Chart for the Value Chain

Customer Vendor

(FlexiblePlanning)

Delivery

Goods IssueGoods Receipt

Billing Document

Accounting

Document1

ShippingNotification

Shipping Notification

Payment Notice (REMADV)

Payment run

Accounting

Document2

SchedulingAgreement

Schedule Line

MM-SchedulingAgreement Schedule

Line

Invoices

Accounting

Document1

Invoice (INVOIC)

Forecast Delivery Schedule

(DELFOR)

PaymentNotice

Incoming Payment

Payment

Bank

Accounting Document 1: Open itemAccounting Document 2: Payment

© SAP AG of 26




2 Prerequisites

2.1 Organizational and Master Data

The following organizational and master data is required in the scenario:

Field name Value

Plant BP01

Material H03-1000, H03-2000

Customer C0300

Scheduling agreement 35000000

PO number 5600000001

Purchasing org. BP01

2.2 Installing Final Step

Before you can begin performing the steps described in the Business Process Procedure, theinstallation of the following building block must have been completed:

Building Block Description

Final Steps Maintaining Material Posting Period, Costing Run, InitialStock Posting, etc.

2.3 Uploading the User Role

Use

Before you can begin performing the steps described in the Business Process Procedure, you needto upload the user role for this scenario and assign it to your user. A user role enables you tocomfortably access all transactions required for the business application testing.

You have to install a user role for each scenario. The following role is available:

Technical name Description File name for upload

/SMB62/H03_01U SOP and Production Planning SMB62_H03_01U

Procedure

For more information about uploading the user role to the system and working with roles, see to theEssential Information building block.

© SAP AG of 26




3 Basic Business Process

3.1 Creating Product Sales Planning

Use this business process step is used to create a product sales planning using planning level:YB100 , planning package: YB110 , and planning methods: YB100 .

Procedure

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

SAP role menu H03 BPP - SOP and Production Planning →Planning Framework ：Overview

SAP ECC menu Accounting →Controlling →Profitability Analysis→Planning →Edit Planning Data

Transaction code KEPM

2. On the Planning Framework; Overview screen, expand the structure in the Planning Levelsscreen area until you can see all entries.

3. Double-click on planning package YB110 .

Period/year of planning package needs to be adjusted according to your needs.

4. Expand enter planning data in the Planning methods screen area and display parameter setYB100 .

5. Double-click on parameter set YB100 .

6. Make the following entries:

Product Text Planning sales quantity Planning revenue

H03-1000 Connector A 1000 2500

H03-2000 Connector B 1500 3750

7. Choose Save and go back to the SAP Easy Access screen

3.2 Displaying Product Sales Planning

Use

This business process step is used to display the product sales planning data created at previousstep.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Planning Framework Overview

SAP ECC menu Accounting →Controlling →Profitability Analysis→Planning →Edit

© SAP AG of 26




Planning Data

Transaction code KEPM

2. Display planning package YB110 choosing planning levels YB100 at planning framework:Overview screen.

3. Display planning method on double clicking planning package YB110 .

4. Expand planning data display then display parameter set YB100 .

5. Double click on parameter set YB100 .

6. Planned values at previous step are displayed.

3.3 Displaying Plan before Transferring

Use

This business process step is used to display the product sales planning data created in profitability

analysis before transferred to SOP.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Display Plan inFlexible Planning

SAP ECC menu Logistics→Sales and Distribution→Sales Information System

→Planning →Display

Transaction code MC95

2. On the Display Plan in Flexible Planning: Initial screen, make the following entries:

Field name Description User action and values Comment

Planning type Z_SOPKAPAM

3. Select Enter .

4. On the Display Plan: Initial screen, make the following entries:


Prod.group/material H03-1000

Plant BP01

5. Choose Active version.

6. On the Display Rough-Cut Plan, confirm data.

Confirm nothing is filled in since transferring has not been done yet. Transferring will bedone at nest step.

7. Press Back three times and go to the SAP Easy Access screen.

© SAP AG of 26




3.4 Transferring Planned Quantities to Sales OrganizationPlanning (SOP)

Use

This business process step is used to transfer planned quantities to sales organization planning(SOP).

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Transfer PlanData to SOP

SAP ECC menu Accounting →Controlling →Profitability Analysis→Planning →

Integrated Planning →Transfer Quantities to SOP

Transaction code KE1E2. On transfer plan to SOP: Initial Screen, enter following entries.

Plan Data

From Period 2007.001

(the FirstPeriod of CurrentFiscalYear)

To 2007.012

(the LastPeriod of CurrentFiscalYear)

Version 001

Record Type FCharacteristic Product

Quantity Sales quantity

SOP

Version

Version text

Options

Transfer Changes Only

Test run

3. Select Selection criteria

4. At Transfer Plan to SOP: Selection Criteria screen, select characteristic values according to your needs.

5. Select Execute.

6. You can check logs for your reference on your needs.

7. Choose Back two times and go to the SAP Easy Access screen.

© SAP AG of 26




3.5 Confirmation of Transferred Plan

Use

This business process step is used to confirm the result of transferring product sales planning data

created in profitability analysis to SOP.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Display Plan inFlexible Planning


→Planning →Display


2. On the Display Plan in Flexible Planning: Initial screen, make the following entries:Field name Description User action and values Comment

Planning type Z_SOPKAPAM

3. Select Enter .

4. On the Display Plan: Initial screen, make the following entries:


Prod.group/material H03-1000

Plant BP01

5. Choose Active version.

6. On the Display Rough-Cut Plan, confirm data transferred.

7. Press Back three times and go to the SAP Easy Access screen.

3.6 Producing Legacy Data for Use as Examples

Use

This business process step is used to produce legacy data.

Newly imported scheduling/JIT delivery schedules and changes to existing sales

delivery schedules are updated in the information structure S727.

The process will be explained using the characteristic combination Customer C0300,Materials H03-1000 and H03-2000, and Plant BP01.

Legacy data for this characteristic combination is produced by an ABAP program for useas examples. This program has to be executed once. The advantage of this is that thesame legacy data for this characteristic combination exists in every system.

© SAP AG of 26




Procedure


SAP role menu H03 BPP - SOP and Production Planning →ABAP Editor

SAP ECC menuTools

→

ABAP Workbench→

Development →

ABAP Editor Transaction code SE38

2. On the ABAP Editor: Initial Screen , maintain in accordance with the following table.


Program YSOP_S727_HISTORY

3. On the ABAP Editor: Initial screen, choose Program→Execute→Direct processing.

4. The following message is displayed: Program run OK.

5. Choose Back to return to the SAP Easy Access screen.

The following table in the next step shows the results for materials H03-1000 and H03-2000, customer C0300 and plant BP01.You can view this imported historical data.

3.7 Calling up Standard Analyses Customer Applications

Use

This business process step is used to call up standard analyses customer applications.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Standard analysisfor info structure

SAP ECC menu Logistics→ Logistics Controlling → Logistics Information

System→ Standard Analyses→ User-Defined Application

Transaction code MCSH

2. On the Info structure screen all the info structures found are listed.

Choose InfoStrc S727 and choose Copy .

3. On the Standard analysis for info structure S727 Selection screen, make the following entries:


Characteristics

Plant BP01

Period to Analyze

Month 12 months in the past Example: 2006.03 ~2007.03

To Current date

© SAP AG of 26




4. Choose Execute.

5. On the Standard analysis for info structure S727: Basic List screen, a list of various materialsappear:

If this is your first time to call up standard analyses customer application, you maybe

cannot get the right list. So select from menu Edit Choose key figure. Then first

choose the figure Order quantity , second choose Sales, choose to put the Order quantity to Selection criteria and choose enter twice.

6. Place the cursor on the 得意先 C0300 and then choose Choose (F2).

7. Place the cursor on the Material group 1 and then choose Choose (F2).

8. Place the cursor on the material Connector A (H03-1000) and then choose Choose (F2).

9. Double click the line to drill down the information until you see the following data. On theStandard analysis for info structure S727: Drilldown screen, you can now view the importedhistorical data for this material, which is also displayed in the table below:

Month Actual order quantity

M-12 191

M-11 200

M-10 209

M-9 218

M-8 227

M-7 236

M-6 245

M-5 254

M-4 263

M-3 272

M-2 281

M-1 290

Current month M

M+1

M+2

M+3

10. Go back to the Standard analysis for info structure S727: Basic List screen and repeat steps 6and 9 for material H03-2000 (Connector B).

11. Choose Back to go back to the SAP Easy Access screen and do not save the analysis.

© SAP AG of 26




3.8 Structure of Current Schedule Lines

Use

This business process step is used to change schedule lines at the vendor side.

Forecasts refer to historical legacy data (basic data). Current data of standard orders(for example, open quantity for future months: M, M+1, M+2, and so on) as well as newforecast/JIT delivery schedules of a scheduling agreement can also be included as basicdata in forecasts.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →ChangeScheduling Agreement

SAP ECC menu Logistics→Sales and Distribution→Sales→Scheduling

Agreement →Change

Transaction code VA32

2. On the Change Scheduling Agreement: Initial screen, make the following entries:


Scheduling Agreement

35000000

3. Confirm your entries.

4. On the Change Sched. Agr.w/Rel. 35000000: Overview screen, the system displays the

scheduling agreement header and item data.

5. From the scheduling agreement, you can call up the forecast delivery schedule (select item):

Goto Item Forecast dlv. sched.

6. On the Change Sched. Agr.w/Rel. 35000000: Item Data screen, maintain the following schedulelines in accordance with the following table:


Dlv. schedule Delivery schedule no. 1

Dlv.sched.date Current date

7. On the Change Scheduling Agreement 35000000: Item Data screen, maintain the followingschedule lines

Date (External date type) Date (schedule line date) Order quantity

M (month) Current Month 299

M (month) Current Month + 1 month 308

M (month) Current Month +2 months 317

M (month) Current Month +3 months 326

© SAP AG of 26




8. Choose Save, confirm the message that the delivery date cannot be met and then go back to theSAP Easy Access screen.

This current delivery schedule data is not updated in info structure S727.

3.9 Creating the Planning Hierarchy

Use

This business process step is used to create the planning hierarchy at the vendor side.

To create a sales plan, you can forecast actual data from the past. The order quantitiesand scheduling agreement quantities updated in information structure S727 form thebasis of this forecast. You can change your result manually, as required. In this way, thesales plan is created.

Information structure S727 is used to carry out planning via the organizational levelsSold-to party , Material Group, Material , and Plant (the characteristics of the informationstructure). The business planning and information key figures include Order quantity andDelivery quantity for determining and evaluating position trends and, if necessary,planned production acquisitions.

To create flexible planning, you have to maintain the planning hierarchy.

The planning hierarchy displays the organizational levels and units of your company, for which sales planning is to be created. The particular combinations of sold-to party,material group, material, and plant that are relevant for planning are specified for information structure S727. For this reason, only characteristic combinations from theplanning hierarchy are used when flexible planning is created / changed. All the

combinations for planning must, therefore, be created in the planning hierarchy.The first time you do this; there is still no planning hierarchy in the system. You thereforehave to add at least one characteristic combination.

To create a planning hierarchy, for example:

Sold-to party: C0300

Material Group; 01

Material: H03-1000, Aggr. Factor 1, share (%) 60

Select Material H03-1000 choose Next Step

Plant: BP01. Aggr. Factor 1, Proportion (%) 100

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Create Planning Hierarchy


→Planning →Flexible planning →Master Data→Planning

© SAP AG of 26




Hierarchy →Create


2. On the Create Planning Hierarchy: Initial Screen, make the following entries:


Info structure S727


4. On the Characteristics screen, make the following entries:


Sold-To party Do not enter value

Material group Do not enter value

Material Do not enter value

Plant Do not enter value


6. On the Create Planning Hierarchy: Sold-to party screen, you can view with the aggregationfactor and proportion in %. Make the following entries:


Sold-to pt C0300

Aggr. fact. 1

Proportion 100

7. On the Create Planning Hierarchy: Material group screen, you can view with the aggregationfactor and proportion in %. Make the following entries:

Field name Description User action and values CommentMatl group 01

Aggr. fact. 1

Proportion 100

8. On the Create Planning Hierarchy: Material screen, you can view with the aggregation factor and proportion in %. Make the following entries:


Material H03-1000

Aggr. fact. 1

Proportion 60

9. On the Planning level screen, select OnlyHere.

10. On the Create Planning Hierarchy: Plant screen, you can view the highest planning stage (plant)with the aggregation factor and proportion in %. Make the following entries:


Plant BP01

© SAP AG of 26




Aggr. fact. 1

Proportion 100

11. Choose Save.

12. Choose Back to return to the SAP Easy Access screen.

3.10 Changing the Planning Hierarchy

Use

This business process step is used to maintain the planning hierarchy.

You want to include additional new material in sales planning, for example. This meansthat the new material also has to be included in the planning hierarchy (change planninghierarchy).

When you change the planning hierarchy, you can add or delete any characteristiccombination.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Change Planning Hierarchy


→Planning →Flexible planning →Master Data→Planning

Hierarchy →Change


2. On the Change Planning Hierarchy: Initial screen, Make the following entries:


Info structure S727


4. On the Characteristics screen, do not enter values:

If you do not enter any values on this screen, you can view the entire planning hierarchy

with all its members.


Sold-to party Do not enter value




© SAP AG of 26





The procedure for maintaining our planning hierarchy is the same as for building theInformation Structure S727 that forms the basis for the planning hierarchy. For this

reason, the sold-to party is the highest aggregation stage. The material is subordinate tothis stage. The plant is in turn subordinate to this material. You can enter several entriesfor each stage; for example, you can have various sold-to parties at the top stage. Youcan assign proportional factors to these entries that must result in 100% yield for eachstage.

6. On the Change Planning Hierarchy: Sold-to party screen, you can view the highest planningstage (sold-to party) with the aggregation factor and proportion in %. Make the following entries:


Sold-to pt C0300

Aggr. fact. 1

Proportion 100

7. Select the sold-to party already entered and choose Next level (you can also do this by double-clicking the row) to go to the next planning level (material group) for this sold-to party. This callsup the Change Planning Hierarchy: Material group screen. Make the following entries:


Matl group 01

Aggr. fact. 1

Proportion 100

8. Select the material group already entered and choose Next level (you can also do this bydouble-clicking the row) to go to the next planning level (material) for this sold-to party. This calls

up the Change Planning Hierarchy: Material screen. Make the following entries:Field name Description User action and values Comment

Material H03-1000

Aggr. fact. 1

Proportion 70

9. Now select material H03-1000 and choose Next level (you can also do this by double-clickingthe row) to go to the next planning level (plant) for this sold-to party. This calls up the ChangePlanning Hierarchy: Plant screen. Make the following entries:


Plant BP01

Aggr. fact. 1

Proportion 100

10. When you have changed the planning hierarchy, choose Save, and then choose Back to returnto the SAP Easy Access screen.

© SAP AG of 26




For characteristic combinations for which there is already actual data in the infostructure, the planning hierarchy can also be generated automatically. To do so, chooseMC9A. For more information about this topic, refer to the Online Documentation [LO –Sales and Operations Planning (SOP)].

The proportional factors for the members of a planning hierarchy can also be generated

automatically via the actual data in the info structure. To do so, choose MC8U.

With consistent planning, the proportional factors of the planning hierarchy are onlyrequired if quantities or values for an aggregate (for example, customer) have to bereplanned and distributed to the members. You can obtain further information regardingthis from the Online Documentation.

(LO – Sales and Operations Planning (SOP))

3.11 Working and Navigating in the Planning Table of aFlexible Planning Structure

UseThis business process step is used to work in the planning table of a flexible planning structure atthe vendor side.

Planning structure S727 is configured as consistent planning: changes on any planninglevel have a vertical effect on every other planning level. Aggregation is carried outupwards, and distribution according to the proportional factors is carried out downwards.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Change Plan inFlexible Planning


→Planning →Change


2. On the Change Plan in Flexible Planning: Initial screen, make the following entries:


Planning type Y_S727_SOP

To enable you to change flexible planning, a planning type (configuration) has to becreated in the system.

A planning type describes a user (group)-specific planning table. A planning type is aspecific planning and information screen based on the data of the information structure.


4. On the Planning for info structure S727 screen, do not enter any values. Delete the defaultvalues if necessary.

© SAP AG of 26






Material Group Do not enter value



If you do not enter any values on the initial screen, all the members of the planninghierarchy are displayed in the planning table and can be planned. If you enter values, anextract is displayed in accordance with the values selected from the planning hierarchy.

5. Choose Active version. The Change Plan (Consistent Planning) screen, which contains theplanning table, appears.

6. On the Change Plan (Consistent Planning) screen, you can see the values C0300 , 01, H03-1000, and BP01 in the sold-to party, material group, material, and plant fields respectively. Youare now at the highest level of the planning hierarchy.

In the planning table header, the characteristics Sold-to party , Material Group, Material ,Plant show you that you are at the lowest level of the planning hierarchy.

In the planning table, the key figure (order quantity) you require to create planning arearranged via a time stream (in info structure S727, months are displayed). With planningtype Y_S727_SOP, the rolling sales plan always begins with the current month. Byconfiguring the planning types, you can set other options.

In the rows, key figures are listed: a) key figures updated by the system (actual keyfigures), and b) key figures for planning, which can be entered or changed. The followingkey figures must be noted:

1. The first line as well as the header line, displays the current planning level.2. The key figure Order quantity is the sales quantity for planning.

3. The key figure Actual Order quantity is the order quantity updated from

orders and scheduling agreements.

4. The key figure Actual Net value represents the updated order and

scheduling agreement value. (For more information on this, see the comments on

the topic Updating.)

5. Production is the key figure to which the final result from production

planning is transferred.

6. By means of a macro (calculation of stock), the key figure Stock level can

be used to calculate the stock level per period on the basis of the key figures

Sales and Production.7. By means of a macro (calculation of days' supply), the key figure Days'

supply can be used to calculate the days' supplied per period on the basis of the

key figures Sales and Production.

8. If the key figure Target stock level is maintained per period instead of

Production , the key figure Production can be calculated via a macro (Target stock

level Production) and the key figures Sales and Target stock level .

© SAP AG of 26




9. If the key figure Target days' supply is maintained per period instead of

Production , the key figure Production can be calculated via a macro (Target stock

level Production) and the key figures Sales and Target days' supply .

When consistent planning is carried out, the data is stored on the bottom planning level.The system implements changes to and navigation between aggregates by aggregating

(cumulating or calculating the average of) detailed data, as well as correspondinglydisaggregating data into details.

7. Go back to the SAP Easy Access screen and do not save.

For other navigation options, refer to the Online Documentation [LO – Sales andOperations Planning (SOP)].

3.12 Creating Sales Plan

UseThis business process step is used to carry out a forecast on the basis of actual order quantity at thevendor side.

On the basis of the updated order quantities (order quantities and scheduling agreementquantities), you want to carry out a forecast for the key figure Order quantity.

Depending on the forecasting technique, the statistical forecast requires a minimum of historical data (which is imported via updating). With online forecast, you can correct thehistorical values manually.

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

SAP role menu H03 BPP - SOP and Production Planning →Change Plan inFlexible Planning




2. On the Change Plan in Flexible Planning screen, make the following entries:


Planning type Y_S727_SOP3. Confirm your entries.

4. On the Planning for info structure S727 screen, do not enter any values. Delete the defaultvalues as necessary.



Material group Do not ever value

© SAP AG of 26






5. Choose Active version. The Change Plan (Consistent Planning) screen, which contains theplanning table, appears.

6. On the Change Plan (Consistent Planning) screen, select the row containing the key figure

Order quantity and choose Edit →Forecast

7. On the Forecast: Model Selection screen, make the following entries:


Periods

Period intervals Period intervals radio button

(on)

Forecast from/to Enter, for example, 12 months in thefuture

Historical datafrom/to

Enter a historical period, for which dataalready exists in the system - for example, 12 months.

Forecastexecution

Aut. model selection

Aut. model selection radio button

(on)

Forecastparameters

Profile Profile SAP is defaulted by system

8. Choose Forecasting to carry out a forecast

9. In the Forecast: Parameters for Automatic Model Selection dialog box choose Forecasting againand confirm the information message that appears.

10. In the Forecast: Results dialog box, the system displays the results of the forecast you havecarried out. You can make changes here manually. If you want to save the final result, chooseCopy and Save (green checkmark). The result will then be transferred to the planning table.

A forecast takes the past into account. There are also market effects that cannot beforecast (for example, more or fewer competitors, and so on). To also take influences of this type into account, you can alter the results of the forecast manually, or work with the

Event functionality.Flexible planning provides a large number of options for mapping this process (manuallycreated forecast; forecast created in background; manual change of statistical default).In this case, the result yielded by the planning process is the sales plan.

You can carry out a forecast at every planning level. Since consistent planning is used,the historical data for the forecast is totaled for the aggregate in question.

For other options for carrying out forecasts, refer to the Online Documentation [LO –Sales and Operations Planning (SOP)].

© SAP AG of 26




11. Choose Save and Back to return to the SAP Easy Access screen. Confirm any systemmessages displayed.

You can forecast the expected order quantities (sales plan) for the future on the basis of

the historical values (order quantity).

3.13 Creating the Operations Plan

Use

This business process step is used to create the operations plan from the sales plan.

The operations plan can be derived from the sales plan. To do this, you have to takevarious influencing factors into consideration - for example, resource leveling via rough-cut planning, target stock level, or target days' supply, and so on.

There are various options/strategies for deriving the operations plan from the sales plan,such as:

1. Copy sales plan 1:1 as operations plan (macro: Sales -> Production)

2. Enter target stock level, and have system calculate operations plan (macro: Target

Stock Level Production)

3. Enter target days' supply, and have system calculate operations plan (macro: Target

Days Supply Production)

These calculations can be carried out with macros.

For other options as regards creating macros and an operations plan, refer to the onlinedocumentation [LO – Sales and Operations Planning (SOP)].

In this value chain, the operations plan is only copied 1:1 from the sales plan.

Taking into account integrated planning for materials requirement planning, checkcarefully whether you actually require the step described in this section. With theexception of the planning strategies for make to stock production that can be set in thematerial master, the planned independent requirement (the result of sales planningaggregated at plant level) represents a planned issue and not a planned receipt.

Procedure


SAP role menu H03 BPP - SOP and Production Planning →Change Plan in

Flexible Planning




2. On the Change Plan in Flexible Planning: Initial screen, make the following entries:


© SAP AG of 26




Planning type Y_S727_SOP


4. On the Planning for info structure S727 screen, do not enter any values. Delete the defaultvalues as necessary.






5. Choose Active version. The Change Plan (ConsistentPlanning) screen, which contains theplanning table, appears.

6. On the Change Plan (Consistent Planning) screen, choose Edit Macro.

7. On the Macro selection screen, select the following values:


Macro selection

Macros Switch Sales Production (on)

8. Note the quantities for the key figure Production. Confirm your entries and check whether thesales quantities have been copied to the key figure Production.

9. Save and Choose Back to return to the SAP Easy Access screen. Confirm any systemmessages displayed.

3.14 Transferring Production Plan from SOP to DemandManagement

Use

This business process step is used to Transfer Production Plan from Sales and Operations Planning(SOP) to Demand Management at the vendor side.

Until now, sales and production plans have been created in the info structure S727, thatis, the values were not MRP-relevant. These production plans can now be transferred toDemand Management as planned independent requirements.

There are two options for transferring production plans for materials to DemandManagement:

1 Automatic (background job) and simultaneous transfer of selected characteristiccombinations from the planning hierarchy.

2 Transfer of individual materials per plant online.

© SAP AG of 26




Procedure


SAP role menu H03 BPP - SOP and Production Planning →Create Planned Indep. Requirements

SAP ECC menu Logistics→Production→Production Planning →Demand

Management →Planned Independent Requirements→Create

Transaction code MD61

If you are creating planned independent requirements for the first time, chooseScheduling Agreement Processing with: Shipping Notifications, Invoices & Flexible

Planning→Processes at Supplier →Add Preplanning.

2. On the Change Planned Independent Requirements: Initial screen, make the following entries:


Planned independentrequirements for

Material

Product group

Reqmts plan

Material (on)

Material H03-1000

MRP area

Plant BP01

Define version

Version 00

Planning horizon

From Current date

To Current date + 1 year

Planning period M (month)


4. On the Plnd ind. reqmts Create: Planning Table screen, the system displays the independentrequirement quantities per plant (BP01) for a particular point in time or over a particular period.

You can now change the quantities stored in the planning table by adding your ownvalues, supplementing the values, or copying a version from flexible planning structureS727.

5. To copy from flexible planning structure S727 select the item and choose Edit →Copy

requirements→Copy flex. plng.

6. In the fields on the Copy Flexible Planning screen, make the following entries:

© SAP AG of 26





Selection

Material H03-1000

Plant BP01

Info structure mat S727

Version A00

Period for copy andkey figure

Key figure PRODU

Reqmts date from Current Month

Reqmts date to Current Month +12 months

Month M (month)

Change referencevalues

Planned qty Leave blank

Postpone by Leave blank

Percent Leave blank

7. Choose the Select Sched. line.

8. On the Create plnd ind. reqmts: Copy Data Change screen, the Active version of the preplanningis displayed. On the right of the screen, you can see the defaulted schedule lines from flexibleplanning structure S727. In the header, you can see material , plant , MRP area, and total plnnd qty .

9. In the area on the right of the screen, select the schedule lines (requirements date and plannedquantity) that you want to copy to preplanning as the planned independent requirement.

10. To copy the selected schedule lines, choose Edit Select Copy

11. If requirements dates already exist, the message Requirements dates already exist is

displayed with the question "Do you want to overwrite the current schedule lines?" Choose Yes.

12. Choose Save. This takes you back to the Change Plnd ind. rqmts screen. You can check herewhether the production quantities from the flexible planning structure have been copied.

13. Choose Save and Back to return to the SAP Easy Access screen.

Forecasting, macros, copying to Demand Management, as well as other activities can

be carried out automatically in the background. For a detailed description of theprocedure, refer to the online documentation (LO – Sales and Operations Planning(SOP) - section Mass Processing ).

Business Process Procedure 4423

Documents

Transcript of Business Process Procedure 4423