Download docx - Snp Yp9 Scm702 Bpd en Xx

EHP2 for SAP SCM 7.0

January 2013

English

Supply Network Planning (YP9)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Document

SAP Best Practices Supply Network Planning (YP9): BPD

Copyright

© 2013 SAP AG or an SAP affiliate company. 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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP 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. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© SAP AG Page 2 of 46

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

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

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

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

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

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

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



Contents

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

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

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

2.2 Business Conditions........................................................................................................7

2.3 Roles and Authorization..................................................................................................7

2.4 Preparation Steps............................................................................................................7

3 Process Overview.................................................................................................................10

4 Process Overview Table.......................................................................................................11

5 Process Steps- Heuristics Run.............................................................................................13

5.1 Infinite Planning: Perfect World.....................................................................................14

5.2 Infinite Planning: Distribution Horizon Constraint Results in Late Demand Fulfillment. .20

5.3 Infinite Planning: Production Horizon Constraint Results in Late Demand Fulfillment...22

5.4 Infinite Planning: Capacity Overload.............................................................................25

6 Process Steps - Optimizer Run (Optional)............................................................................27

6.1 Finite Planning: Perfect World.......................................................................................28

6.2 Finite planning: Capacity Constraint (Production Rate).................................................35

6.3 Finite planning: Capacity Constraint (Product Priority)..................................................37

6.4 Finite planning: Capacity Constraint (Sales Order Priority)...........................................40

6.5 Finite planning: Raw Material Constraint.......................................................................43

6.6 Reverting the Setting Changes......................................................................................45

7 Appendix.............................................................................................................................. 45

7.1 Posting Initial Stock in ERP...........................................................................................45

7.2 Creating a Sales Order..................................................................................................46

7.3 Deleting a Sales Order..................................................................................................47

7.4 Maintaining the Vendor Location Material Master.........................................................47



Supply Network Planning

1 PurposeCreating a feasible supply plan according to your demand situation considering all production and distribution activities along the supply chain is the goal of the process.

This RDS will help you to reduce delivery times, optimize transports, plan the required supply just in time and keep needed safety-stocks

Starting from a demand plan, you use Mid-term Supply Planning to determine a permissible plan for fulfilling the estimated sales volumes. This plan covers both the quantities that must be transported between two locations (for example, distribution center to customer or production plant to distribution center), and the quantities to be produced and procured.

Mid-term Supply Planning is based on a model of the supply network. The model represents a specific supply network and consists of individual nodes, links, and other elements. The nodes represent different locations of the network, such as customer locations, distribution centers, plants, or suppliers. The links between the nodes are represented by the transportation lanes. Elements such as products, bills of materials, routings, and different kinds of resources are also essential parts of the supply network. The structure of the model and the detailed settings influence the results of the planning run.

Mid-term Supply Planning will help to:

create a supply plan that provides a clear picture on procurement, production and distribution activities in an end to end supply chain

consider significant capacity and material constraints to achieve a feasible plan

optimize the capacity utilization at the plants, distribution centers and at the suppliers

respect inventory levels

increase the visibility in the global supply chain

2 Prerequisites

2.1 Master Data and Organizational DataDefault Values

Essential master and organizational data was created in your ERP and APO system during the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example master data for materials, locations, and resources.

This business process is enabled with organization-specific master data, examples of which are provided in the next section.

Additional Default Values

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC and APO system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data.

SNP supply network:



Organization and master data:

Object Value Description Comment

Plant 1000 Plant 1000

1100 Plant 1100

Distribution Center

2300 DC 2300

2400 DC 2400

Sales Organization

1000 Sales Org 1000

Customer 100000

Purchase Organization

1000

Vendor 390001 Vendor 390001

390002 Vendor 390002

Finish Goods SCM-PROD01 PROD01 Created for all locations

SCM-PROD02 PROD02 For location: 1000, 1100, 2300

SCM-PROD03 PROD03 For location: 1000, 2300

Raw Materials

SCM-RAW01 RAW01 For location: 1000, 1100

SCM-RAW02 RAW02 For location: 1000, 1100, 390001, 390002

Purchase Info Record

1 390001 (SCM-RAW01)

2 390002 (SCM-RAW01)

3 390001 (SCM-RAW02)

4 390002 (SCM-RAW03)

Workcenter SCM-MFG1 Assembly For plant 1000, 1100 Heuristic

SCM-MFG2 Assembly For plant 1000, 1100 Optimizer



Production version

0001 Version 0001 Production version for each product.

BOM and Routing:

2.2 Business Conditions The business process described in this business process documentation is part of a larger chain of integrated business processes or scenarios.

Following scenarios can be executed before or after the SNP scenario for example,

Best practice baseline packages:

Sales Order Processing: Sale from stock (109)

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

Purchasing scenarios Procurement without QM (130)

Stock Transfer with Delivery (134)

SCM Rapid-deployment packages:

Demand Planning (Y98)

MRP Based Scheduling (S80)

ATP scenarios (S61,S62,S63)

In this scenario, we do not use the same master data using by above scenarios. If you implement the scenario by your own master data, above scenarios can be real integrated.

2.3 Roles and AuthorizationFor this SNP RDS package, the role APO Planner’s Home Page (SAP_SCM_PLN_HOME) needs to be assigned to the relevant users.

2.4 Preparation Steps



This chapter contains process steps that have to be done as prerequisite before you can start to work through the standard Business Process Documentation of the scenario for supply network planning.

2.4.1 Configuring Planner's Home PageThe planner’s home page is a Web application that you can call up in the SAP NetWeaver Business Client (NWBC). It is a start page that can be personalized easily and that you, as a supply chain planner, can use to display the information necessary to perform your daily tasks, and if necessary, navigate to the planning applications where you can change the data that you work on. Due to the user-specific nature of the information that the planner's home page contains, it can easily be personalized in both content and layout. To personalize your planner’s home page, please refer to document YP6 Configuring Planner's Home Page.

2.4.2 Deleting Transaction Data

UseTo go through all the test cases for both heuristics and optimization from scratch, it is strongly recommended to delete transaction data before start the process steps.

You use this function to delete transaction data that was planned in SAP APO from the SAP APO system and a connected SAP R/3 system. It is generally not recommended to use this function in the production system; instead, you should use it for testing and correction purposes.

You can also delete the data in SAP ERP by using the APO Core Interface (CIF) to transfer the deletion activities to SAP ERP.

Procedure1. Access the transaction choosing the following navigation option:

SAP SCM menu Advanced Planning Optimization ® Supply Network Planning ® Environment ® Delete Transaction Data

Transaction code /SAPAPO/RLCDEL

2. On the Delete Transaction Data Screen, enter the following data:

Field name User action and values Comment

Select Objects

By Categories Selected Can be selected after you have input data in field Planning Version

Selection By Categories

Category Choose for example, * Choose * to delete all transactional data.

Additional Selection Options

Manual Selection Checked

Planning Version 000

Supply Network Planner

Choose the planner, for example,, <A> to <B>

Fixed Orders Checked



Today + No. of Days Enter for example, <540> days You can enter a horizon during which you want data to be deleted. You specify the number of days that the system adds to or subtracts from the current date (system date) to calculate this horizon into the future or the past. If you are specifying a past horizon, enter a minus sign in front of the number of days.

Settings

Settings

In R/3 and APO Selected

Test Mode Unchecked

Log Availability The default value is 30 days. Enter the number of days over which the generated log is to be saved.

3. Choose Save to create a variant.

4. On the Variant Attributes screen, make the following entry:


Variant Name Enter the variant name, for example,, <YP_DEL >

Description Enter the description, for example, <Delete trans data>

5. Choose Save.

6. On the Delete Transaction Data screen, you could check the box Test Mode first and then choose Execute. If everything works fine, please uncheck the box Test Mode and choose Execute again to do the real deletion.

7. Choose Yes to confirm to delete from active version 000.

In this document, planning results in APO is not release to ERP immediately. Therefore, to ensure the data in ERP is also deleted, transaction /SAPAPO/C5 has to be triggered in addition, you can refer to the chapter 5.1.4for detail.

2.4.3 Deleting Demand Data

UseTo go through all the test cases for both heuristics and optimization from scratch, it is also recommended to delete demand data in SCM before start the process steps. The deletion of demand will also be transferred to ERP.

Procedure 1. Access the transaction choosing the following navigation option:

SAP SCM menu Advanced Planning and Optimization ® Supply Network Planning ® Environment ® Adjustment of Forecast

Transaction code /SAPAPO/MD74

2. On the Reorgnizaing Indep.Reqmts – Adjust Reguirements (PlndIndReq) Screen, enter the following data:




Selection

Manual Selection Selected

Version 000

Location Choose for example, * Choose * to delete all transactional data.

Options

Display Log Checked

Delete Orders Checked

Send deletion to ERP

Checked

All Planning segments

Checked

Settings

Test Mode Unchecked

Log Availability The default value is 30 days. Enter the number of days over which the generated log is to be saved.

3. On the Reorgnizing Indep.Reqmts – Adjusting Requirements (PlndIndReq) screen, you could check the box Test Mode first and then choose Execute. If everything works fine, please uncheck the box Test Mode and choose Execute again to do the real deletion.

3 Process Overview

Below is the process overview for SNP Process.



4 Process Overview TableProcess step /

Step of Scope item

Business condition

Business role

Transaction code Expected results

1. Loading Demand in the Background

Demand can be loaded in two ways: Demand loaded from SAP ERP via CIF or if APO Demand Planning is used: Demand loaded from SAP APO Demand Planning (transaction /n/ SAPAPO/MC90)

System Depending on scenarios listed in business conditions.

Primary Demand (i.e. Sales orders and Forecast) is loaded.

2. Executing the Supply Planning Run in the Background

System This can be done with either scenario a) or b) but not both.

Distribution, production and procurement proposals by the system.

a) Infinite Planning with SNP Heuristics

Prerequisite: Determine Low Level Code (transaction /n/SAPAPO/SNPLLC)

System /n/SAPAPO/SNP01

Distribution, production and procurement proposals planned by the system.

Capacity constraints are not respected.

b) Finite Planning with

System /n /SAPAPO/SNPOP

Distribution, production and



Process step /

Step of Scope item

Business condition

Business role


SNP Optimization

procurement proposals optimized by the system.

Capacity constraints are respected.

3. Checking Planning Results

Check favorite products and resource if there are problems that require immediate action.

The SNP run results in certain capacity utilization.

In this process step it can be checked whether there are overloaded or underutilized resources.

The need for manual planning can be determined.

Supply Planner APO

NWBC –> Main page, Product/Resource tab

Display of utilization for one special resource in one location as per personalized view.

Display KPIs for certain materials

4. Analyzing Alerts

Access through SAP APO Planner’s Homepage

Supply Planner APO

NWBC ® Alert View

The system displays all the alerts according to selected alert query.

5. Manual Planning in Quantity View at Product Location level

Access through SAP APO Planner’s Homepage

Supply Planner APO

NWBC ® Favorite selections

/n /SAPAPO/SDP94 ® Quantity view (Material)

Analyze system proposal and make adjustments if necessary.

Depending on the user it can result in changed order dates and quantities; or user creates new orders with different sources of supply; furthermore type of replenishment may change for example, from in-house to external.



Process step /

Step of Scope item

Business condition

Business role


6. Planning with the Capacity View at Resource level

Infinite planning run has produced capacity overloads.

Or changes in capacity offer require re-planning.

Access through SAP APO Planner’s Homepage.

Supply Planner APO

NWBC ® Favorite selections

/n/SAPAPO/SDP94 ® Capacity View (Resource)

Depending on resource and planning approach no capacity overloads, constant capacity usage. Manually planned capacity.

For example, planner might reduce capacity overloads by manually shifting orders. Automatic Capacity Leveling is not in scope.

7. Releasing the Supply Plan

Supply Planner APO

/n/SAPAPO/C5 APO Orders are published to ERP. Both systems have same view on demand and supply plan.

a) unattended mode

Mid-term supply plan should be visible in SAP ERP and APO without any delay.

System Change Pointers are released automatically. Orders are transferred in real-time to SAP ERP.

b) attended mode

Mid-term supply plan should be finished and planner(s) have decided to release plan to SAP ERP

Supply Planner APO

/n/SAPAPO/C5 Change Pointers are released. SAP ERP and APO are in sync.

5 Process Steps- Heuristics Run

Test Case OverviewIn this Heuristics planning scenario, we use 4 test cases to show the system planning logic, results and possible manual adjustments.

Test Case 1: Infinite planning: perfect world. The demand in DC2400 can be satisfied by stock-on-hand in PL1100, no alert is generated and manual adjustment is not needed.



Test Case 2: Infinite planning: distribution horizon constraint results in late demand fulfillment. There is a distribution horizon set in DC2400. Demands in this horizon cannot be fulfilled in time. They are fulfilled directly after the horizon automatically by the heuristic.

Test Case 3: Infinite planning: production horizon constraint results in late demand fulfillment. Due to the production horizon in PL1000, the near demand in DC2300 cannot be satisfied on time by the highest priority source of supply. The planner reviews the supply shortage in PL1000 alerts from the Alert Work list, and he creates orders with different source of supply (PL1100) in Quantity View of interactive planning.

Test Case 4: Infinite planning: capacity overload. The high demand in DC2300 lead to capacity overload in PL1000, the planner checks the alerts and reduces planned production KF to 100%, then finds the free capacity in earlier bucket to fulfill the left demand.

Prerequisites Make sure you have maintained the master data as instructed in the configuration guide.

For test purpose, in heuristics scenarios, we have created initial stock for SCM-PROD01, 60 pc in DC2300, 50 pc in PL1000 and 60pc in PL1100. In case there is not any stock in the system, please refer to the appendix to create above initial stocks accordingly.

5.1 Infinite Planning: Perfect World

5.1.1 Creating the Demand for Test Case 1

UseFor testing purpose, we prepare the demo data for each test case. Before you start testing for each test case, make sure the demand are created or maintained as described. Otherwise there will be some deviations in the results.



The forecast can be loaded in two ways, either transfer Planned Independent Requirement from ECC via CIF in real time or release from APO – DP if Demand Planning is implemented. Once the forecast is loaded, it is visible in the key figure of Forecast in SNP planning book.

In this RDS package, we transfer planned independent requirement from ECC to SCM. PIR is transferred in real time and it is displayed in the key figure Forecast of SNP planning book.

Sales order can be transferred from ECC to APO as demand as well. Forecast consumption is out of scope. In SNP RDS, total demand equals to forecasts plus sales orders.

Prerequisites System connectivity has been setup. All settings in SAP ERP system for CIF have been configured correctly. Finish goods demand is created either in DP or in ECC.


SAP ECC menu Logistics ® Production Planning ® Demand Management ® Planned Independent Requirements ® Create

Transaction code MD61

2. On the Create Planned Independent Requirements: Initial Screen, enter the following data:


Material Enter the material number, for example,, <SCM-PROD01>

Plant Enter the DC number where the forecast is created, for example,, <2400>

Version Enter 00

Planning Period Enter W

3. Choose Enter.

4. On the Plnd Ind. Reqmts Create: Planning Table screen, enter quantity 30 at <current week + 3 weeks>.

5. Choose Save.

The demand situation at SAP ERP is as following:

Product Plant Requirement on <Current week + 3 weeks>

SCM-PROD01 2400 30 pc

ResultForecast is transferred to SNP successfully. You can check the forecast in the SNP planning book.

5.1.2 Infinite Planning with SNP Heuristics

UseDistribution, procurement and production proposals are generated by the system. The SNP Heuristic performs requirements planning throughout the entire Supply Chain Network based on rules set up in configuration. SNP Heuristics takes neither capacity nor cost constraints into consideration.



Prerequisites Readiness of all master data


SAP SCM menu Advanced Planning and Optimization ® Supply Network Planning ® Environment ® Maintain Process Chains

Transaction code RSPC

2. On the Choose Display screen, choose Network.

3. On the Process Chain Display Planning View screen, choose the process chain YP_Heuristics

4. Choose Schedule.

5. In the Select Priority dialog box, choose Standard Priority C, then choose Continue. The process chain is scheduled to run immediately.

6. You could choose Logs to check the detail log.

Typically, automatic heuristic run is scheduled by process chain.

ResultThe log is displayed and the SNP Heuristic run finished successfully.

5.1.3 Checking the Planning Results with SAP APO Planner’s Homepage

UseCheck favorite products/location and resources if there are problems that require immediate action.

The planner can check the capacity utilization, whether there are overloaded or underutilized resources. The planner can decide whether manual interventions are needed to deal with the planning problems.

The KPIs relevant for this SNP RDS package are listed below:

Maximum Resource Utilization for the next 30 days. Average Days’ of Supply (SNP) for the next 30 days.

Prerequisites KPIs and KPI profiles are maintained and assigned to the role or planner.

APO planner’s homepage is customized to show the relevant KPIs.

Procedure1. Log on NWBC which is connected with SCM system

2. On APO Planner’s Home Page screen, in the section My objects, Choose the tab page Location Product.

3. Check KPI Average Days’ of Supply (SNP)

4. Choose the tab page Resource

5. Check KPI Maximum Resource Utilization

ResultPlanner has an overview at

The average days’ of supply for certain product location combination.



The maximum utilization for resources in one location as per personalized view.

There is a stock on hand 60 pc in PL1100 and it can cover the demand, so no alert generated.

5.1.4 Releasing the Supply Plan

UseThere are two kinds of release mode. In this document, we will only show the attended mode as the example,

Option 1: Unattended Mode

After SNP orders are saved at APO system, orders are transferred immediately to SAP ERP. Both systems then have same view on demand and supply plan.

Option 2: Attended Mode

After APO Order is saved at APO, it will not be transferred immediately to SAP ERP. The changes pointers are used to collect the changes. The planner can first check the planning result and then manually trigger the order transfer.

Prerequisites Active Integration models exist in order to transfer the SNP orders to ERP. For this package,

you need to include planned order and purchase requisition in the integration model. Distribution definition is customized correctly.

5.1.4.1Attended Mode

UseThe periodic publication of planning results can be chosen if data that has been generated or changed in SAP APO does not have to be transferred immediately to SAP R/3. This is often the case for Supply Network Planning (SNP). Periodic publication is the default setting in SNP Customizing.

Transferring the data at a later point in time (for example, using background processing that is scheduled to run at night) has performance benefits because it evens out the load on the CIF interface.

In comparison to the direct publication of planning results, periodic publication records and collects change pointers (see figure below). You can start the processing of change pointers manually or schedule this to take place as background processing. The change pointers are deleted when they have been processed.

Prerequisites Customize to periodic transfer SNP orders to OLTP system


SAP SCM menu Advanced Planning and Optimization ® APO Administration ® Integration ® Publication ® Publish Orders

Transaction Code /SAPAPO/C5

2. On the Select and Copy Orders screen, make the following entries:


Orders

Order number Leave it blank.




APO order type Enter the order type, for example,, from 021 to 031

021 External procurement 026 Confirmation for scheduling

agreement 031 In-house production 036 Project orders 053 Sales order

300 Production campaign

Order GUID Leave it blank.

Products

Product Identifier Name of the location product

Production Planner Planner who is responsible for the location product in Production Planning and Detailed Scheduling (PP/DS)

SNP Planner Enter the SNP planner, for example,, <B>

The customer can also choose other selection field for example, product number.

Demand Planner Planner who is responsible for the location product in Demand Planning

Transportation Planner

Planner who is responsible for the location product in Transportation Planning

Locations

Source location For stock transfer: issuing plant or vendor

Source location type Use the input help to choose the number of the required location type.

Destination location Recipient

Destination location type

Use the input help to choose the number of the required location type.

Other Criteria

Method N – Create new order [New]

Newly created orders often have the value C.

C – Change order [Change]

D – Delete or partially delete document [Delete]

R – Completely delete order [Remove]

Creation time stamp Time of event creation

User name Logon name of the user in the SAP ERP system

Flow Control




Maximum number of hits

The default value is 1000 Number of maximum selected change pointers

Block size Enter the number of change pointers you want to be processed in each block.

The block size is set to 1000 by default.

The system processes the change pointers selected for transfer on a block by block basis depending on the figure entered here. As the block size increases, so does the associated memory requirement. An application log is written for every block that is processed.

Processing Direction The system only evaluates this data if you have entered filter criteria in the Products screen section. Both processing directions have an effect on performance. Tests should be made to determine which processing direction results in higher performance in your system.

From Product Selected The system determines the associated change pointers depending on the product/planner entered

From Change Pointer

The system begins with the selected change pointers and filters out those that do not meet the filter criteria.

Background processing

This is only valid for background processing.

Delete Events If you set this indicator, the system deletes all selected change pointers without sending them first.

Detailed Job Log If you set this indicator, you receive detailed information in the job log.




Variant Name Enter the variant name, for example,, <YP_C5>

Description Enter the description, for example,, <Process change pointers>

5. Choose Save.

You can use the program variant when you schedule a background job.

6. On the Select and Copy Orders, choose Execute.

7. All orders with change pointers are listed on the Select and Copy Orders screen, select all rows, and choose Process Change Pointers.

8. Go to SAP ERP system, using MD04, the planner can see the planning result is transferred to ERP system correctly.



5.2 Infinite Planning: Distribution Horizon Constraint Results in Late Demand Fulfillment

UseIn this section, you can create a new demand in ERP, and the new demand is in the distribution horizon, so it cannot be fulfilled in time. The demand is fulfilled directly after the horizon automatically by the heuristic.

5.2.1 Demand for Test Case 2Repeat the procedure in the chapter 5.1.1 to maintain the demand for this test case, to maintain the demand in day you can enter “D” in the planning period field .

The demand situation at SAP ERP should be as following:

Product Plant Requirement on <Current day + 3 days>


5.2.2 Infinite Planning with SNP HeuristicsYou can refer to the chapter 5.1.2 for detail.


You can refer to the chapter 5.1.3 for detail.

5.2.4 Analyzing Alerts

UseThe planner can check the alerts in the Alert Worklist at APO planner’s homepage. The alerts listed below are relevant for this RDS package:

Supply Shortage



Shortfall below Target Stock Level Stock above Target Stock Level Shortfall below safety stock Resource overload

The planner can review the details of the supply shortage alert and access to the interactive planning to solve the issue.

Prerequisites Overall Alert Profile is created.

Create Alert Query for location product at APO planner’s homepage.

Procedure 1. On the APO Planner’s Home Page screen, choose Alert Worklist, choose Query for Location

Product alerts, if necessary choose refresh to get the updated alerts. Check database alerts.

supply shortage

Due to the 7 days distribution horizon set in DC2400, demands in this horizon cannot be

fulfilled in time. They are fulfilled directly after the horizon automatically by the heuristic.

Therefore, there is a supply shortage in DC2400.

2. Choose the line of alert Supply Shortage, Alert Details section is displayed at the bottom of the screen.

3. The planner can also choose Goto ® Supply and Demand Planning to go directly to interactive planning screen.

4. Do not leave the screen.

ResultThe planners reviewed the Alerts shown on the planner’s home pages, and will do manual

planning to solve the issue.

5.2.5 Manual Planning in Quantity View at Product Location level

UseAccess through location product alerts on SAP APO Planner’s Homepage, analyze system proposal and make adjustments if necessary.

Depending on the user it can result in changed order dates and quantities; or user creates new orders with different sources of supply; furthermore the type of replenishment may change for example, from in-house to external. In case of recent demand or supply updates, an interactive planning run is required to create a new proposal.

Procedure1. On the dialog box quantity view of planning book, the selection is SCM-PROD01/DC2400,

choose Change.

2. Double-click on Total Demand and Total Receipts.

3. The planners review the demand and supply situation, and communicate restriction to

demand planners/sales. And demand planners/sales agree to change the demand to

<current day+7 days>.



4. Repeat the procedure in the chapter 5.1.1 to change the demand to <current day+7 days> in ERP.

ResultConsequently, since the due date of the demand is changed, then it can be fulfilled in time.

5.2.6 Double-check Resource Utilization with the Capacity View

UseAfter manually adjustment of production or distribution schedule, the planner need to double check the resource utilization. In case of resource overload, the planner needs to go back to the quantity view to do reschedule.

Procedure1. On the planning book, choose data view 2_CAPACITY and choose the selection profile

01_RESOURCE

2. Double-check resource utilization of work centers in PL1100.

ResultCheck resource utilization and decide whether planned orders have to be rescheduled using

quantity view.

5.2.7 Releasing the Supply Plan You can refer to the chapter 5.1.4for detail.

5.3 Infinite Planning: Production Horizon Constraint Results in Late Demand Fulfillment



UseIn this section, you can create a new demand in the ERP, and the new demand will result in supply shortage in plant PL1000; then the planner will analyze the alert from planner’s home page and manually change certain order to other source of supply- plant PL1100.

5.3.1 Demand for Test Case 3Repeat the procedure in the chapter 5.1.1 to maintain the demand for this test case.


Product Plant Requirement on <Current day + 7 days>


5.3.2 Infinite Planning with SNP HeuristicsYou can refer to the chapter 5.1.2 for detail.


You can refer to the chapter 5.1.3 for detail.




Supply Shortage

The stock on-hand in DC 2300 is 60 pcs. The 60 pcs in stock are consumed by the

demand of 60 pcs. As a consequence the stock on hand falls to 0 which is below the

safety stock, as the target stock level in DC2300 is 60 pcs, 60 pcs is required to

meet the target stock. The demand for 60 pcs is transferred to the plant PL1000

because the transportation lane from PL1000 to DC 2300 has the highest priority.

The transfer of the demand creates a supply shortage of 10 pcs in the plant PL1000.

As there is a stock on-hand of 50 pcs in PL1000, the demand will consume the stock

first, and the remaining 10 pcs will require an in-house production. However, the

lead time from PL1000 to DC2300 is 7 days, then the stock transfer req. demand

due date is in next week which is within the production horizon, so the plant cannot

supply 10 pc on-time.




ResultThe planners reviewed the Alerts shown on the planner’s home pages, and can manually

plan the orders to solve the issue.



5.3.5 Manual Planning in Quantity View at Product Location level

Procedure1. On the popup quantity view of planning book, the selection is SCM-PROD01/PL1000,

choose Change.

2. Double-click on Total Demand and Total Receipts.

3. The planner reviews the demand and supply situation and tries to find other source of

supply. The supply planner checks with other Plant PL1100 to know whether PL1100 can

also distribute SCM-PROD01 to DC2300 and it still has stock on hand 10 pc. Then the

planners decide to supply 10 pc from PL1100 to DC2300.

4. Choose product SCM-PROD01 at location DC2300 in Selected Object.

5. Right-click on the cell with 60 pc for the third week in row Stock Transfer Req. Receipt.

6. Choose Display detail.

7. In the Display Details screen, for the order from PL1000 to DC2300, reduce the quantity from

60 pc to 50 pc

8. Choose Create.

9. Enter 10 in the cell Receipt Quantity, and press enter.

10. On the dialog box screen Source of Supply Determination, choose PL1100 as source of

supply.

11. Choose Adopt.

12. Save the data in the planning book.

13. Choose product SCM-PROD01 at location PL1000 in Selected Object.

14. Delete 10 pc production order (planned) outside production horizon.

15. Save the data in the planning book.


ResultConsequently, the demand to DC2300 is fulfilled by other source of supply PL1100. In this

example, new production is not required. After the planner changes production or distribution

schedule, he need to double check resource utilization.

5.3.6 Double-check Resource Utilization with the Capacity View


01_RESOURCE

2. Double check resource utilization of work centers in both PL1000 and PL1100.

ResultCheck resource utilization and decide whether need reschedule on quantity view.




5.4 Infinite Planning: Capacity Overload

UseIn this section, you can create new demand in ERP, and the new demand will result in resource overload in plant PL1000; then the planner will change the schedule and produce in advance in plant PL1000.

5.4.1 Demand for Test Case 4Repeat the procedure in the chapter 5.1.1 to maintain the demand for this test case.




5.4.2 Infinite Planning with SNP HeuristicsYou can refer to the chapter 5.1.2for detail.


You can refer to the chapter 5.1.3for detail.






Resource overloadThere is a resource overload in the fifth week for resource WSCM-MFG_1000_001 at PL1000.The production (Planned) in the fifth week for PL1000 is 90 pc; however, the capacity in PL1000 is 80 pc. Therefore, there is a resource overload in PL1000.

2. Choose the line of alert resource overload, Alert Details section is displayed at the bottom of the screen.



ResultThe planners reviewed the resource overload Alerts shown on the planner’s home pages, and

will do manual planning to solve the resource overload in PL1000.

5.4.5 Planning with the Capacity View at Resource Level


02_RESOURCE

2. Check resource utilization of work centers in both PL1000, for the fifth week the key figure

Resource Capacity Level show 112.5%, there is resource overload.

3. Choose Display dependent objects.

4. Choose Product.

5. Choose Change.

6. In the Quantity View section, Shift 10 pc to <Current week + 4 weeks>and reduce 90 pc to

80 pc for <Current week + 5 weeks>.

7. Check the resource utilization again, there is no overload

ResultNo resource overload.


6 Process Steps - Optimizer Run (Optional)

Test Case OverviewIn this optimizer planning scenario, we use the following five test cases to show the system planning logic and the results.

Test Case 1: Finite Planning: Perfect World.

Automatic multi-sourcing by the system based on the capacity constraints, and the priority (defined in the transportation lane). The requirements can be satisfied, so no alert generated.



Test Case 2: Finite Planning: Capacity Constraint (Considering the production rate)

Automatic multi-sourcing by the system based on the capacity constraints, and the priority (defined in the transportation lane).

In this test case, we use two products, SCM-PROD02 and SCM-PROD03, they can be all produced at the same work center, while SCM-PROD03 has higher output rate.

The total demand exceeds the capacity, so the demand can only be satisfied with some delay.

Supply shortage alert is generated. When check the optimizer log data, the late delivery penalty cost is also created. The planner then needs to review the supply shortage alerts from the Alert Worklist. The supply shortage is for the product SCM-PROD02 because of lower output rate.

Test Case 3: Finite Planning: Capacity Constraint (Considering the product priority)

From this test case, the planner can see during the optimizer run, the system will also consider the priority of the product, which will then lead to the different planning result.

Based on the test case 2, the planner changes the priority of the product SCM-PROD02 to 1, so it has higher priority than SCM-PROD03. After the optimizer run, the planner can see that the system tries to satisfy the demand for the product SCM-PROD02, and the supply shortage alert is generated for the product SCM-PROD03.

Test Case 4: Finite Planning: Capacity Constraint (Considering the sales order priority)

From this test case, the planner can see during the optimizer run, the sales order has higher priority than the forecast.

Originally there has forecast demand for the product SCM-PROD02, the resource is almost fully loaded. Now create a sales order for the product SCM-PROD03 at SAP ERP. After the Optimizer run, the planner can see the system tries to first satisfy the sales order, the supply shortage alert is generated for the product SCM-PROD02.

Test Case 5: Finite Planning: Raw Material Constraint

From this test case, the planner can see the supply shortage alert generated for the demand because of the raw material constraint.

There has a fixed receipt order from the vendor, the quantity is less than the requirement. Now you change the planned delivery time to 999 days for the vendor location material master. After the optimizer run, the planner can see the supply shortage alert generated because of the raw material constraint.

Prerequisites Make sure you have maintained the master data as instructed in the configuration guide. For test purpose, we have created initial stock for SCM-PROD02, 20 pc in DC2300. In case

there is no stock in system, please refer to the appendix to create above initial stocks accordingly.

Check and make sure the planned delivery time for vendor location material master is set to 0. Refer to Appendix for detail.

Check and make sure the product priority SCM-PROD02 in DC2300 is set to 0. Refer to the step 1 in the prerequisite part in the chapter 6.3 for detail.

6.1 Finite Planning: Perfect World



6.1.1 Maintaining the Demand Data

UseFor testing purpose, we prepare the demo data for each test case. Before you start test for each test case, make sure the demand are created or maintained as described here. Otherwise the result will have some deviations.

The forecast can be loaded in two ways, either transfer Planned Independent Requirement from ECC via CIF in real time or release from APO – DP if Demand Planning is implemented. Once the forecast is loaded, it is visible in the key figure of Forecast in SNP planning book.

In this RDS package, we transfer planned independent requirement from ECC to SCM. PIR is transferred in real time and it is displayed in the key figure Forecast of SNP planning book.

Sales order can be transferred from ECC to APO as demand as well. Forecast consumption is out of scope. In SNP RDS, total demand equals to forecast plus sales order.

Prerequisites System connectivity has been setup. All settings in SAP ERP system for CIF have been configured correctly. Finish good demand is created either in DP or in ECC.


SAP ECC menu Logistics ® Production Planning ® Demand Management ® Planned Independent Requirements ® Create

Transaction code MD61

2. On the Create Planned Independent Requirements: Initial Screen, enter the following data:




Material Enter the material number, for example,, <SCM-PROD02>

Plant Enter the DC number where the forecast is created, for example,, <2300>

Version Enter 00

Planning Period Enter W

3. Choose Enter.

4. On the Plnd Ind. Reqmts Create: Planning Table screen, enter quantity 100 at <current week + 3 weeks>.

5. Choose Save.

The demand situation at SAP ERP is as following:


SCM-PROD02 2300 100 pcs

ResultForecast is transferred to SNP successfully. You can check the forecast in the SNP planning book.

6.1.2 Finite Planning with SNP Optimizer

UseThe SNP optimizer offers cost-based planning. System searches through all feasible plans in an attempt to find the most cost-effective plan. A feasible plan means it satisfies all the supply chain model constraints that you set in the SNP optimizer profile, for example, production capacity.

Optimization uses exact method (linear programming) to deliver an optimal solution based on costs and priority. In this solution, we provide the automatic cost generation method to get control cost as per the business goal.

A process chain is created for periodic background job. The planning can also be run interactively. After the planning run, the optimal distribution, procurement and production proposals are generated by the system. Capacity constraints are respected.

Prerequisites Customization like SNP optimization profile and required master data are correctly maintained.


SAP SCM menu Advanced Planning and Optimization ® Demand Planning ® Environment ® Maintain Process Chains

Transaction code RSPC

2. On the Process Chain Display Planning View screen, double click the process chain YP_Optimizer , then choose Schedule.

3. On the Select Priority dialog box, choose Standard Priority C, then choose Continue.



For the testing purpose, the process chain is scheduled to run immediately. In real customer project, the Optimizer is scheduled to run periodically at background.

This step can also run within the interactive planning screen, make sure you load all relevant products locations to the work area.

4. You could choose Logs to check the detail log.

ResultThe log is displayed and the SNP Optimizer planning run finished successfully.

6.1.3 Checking the KPIs with SAP APO Planner’s Homepage

UseUsing SAP APO Planner’s Homepage, the planner can have a quick overview on the KPIs for his or her favourite product/location combinations and resources.

The KPIs relevant for this SNP RDS package are listed below:

Maximum Resource Utilization for the next 30 days. Average Days’ of Supply (SNP) for the next 30 days.

Prerequisites KPIs and KPI profiles are maintained and assigned to the role or planner.

APO planner’s homepage is customized to show the relevant KPIs.

Procedure1. Log on NWBC client which is connected with SCM system

2. On APO Planner’s Home Page screen, in the section My objects, Choose the tab page Location Product.

3. Check KPI Average Days’ of Supply (SNP)

4. Choose the tab page Resource

5. Check KPI Maximum Resource Utilization.

ResultThe planner has an overview at

The average days’ of supply for certain product location combination. The maximum utilization for resources in one location as per personalized view.

6.1.4 Checking and Analyzing Alerts

UseIdeally, after the optimization run, you can get a feasible plan that meet all the demands, and at the same time satisfies all the supply chain model constraints. But sometimes, a feasible solution might involve due date or safety stock constraint violations, because the due dates and safety stocks are defined as soft constraints (the violation will incur penalty costs). The optimizer only proposes a plan that will violate soft constraints if it is the most cost-effective plan.

The planner can know these violations by alerts. After the Optimizer run, the planner can check the alerts information in the Alert Worklist at APO planner’s homepage. He or she can get a quick overview on for which product/location, at which time buckets, which kinds of alert type exists.

The alerts listed below are relevant for this SNP RDS package:

Supply Shortage (Due date violation)



Shortfall below safety stock (safety stock violation)

These violations are normally caused by the capacity and lead time constraints.


Create Alert Query at APO planner’s homepage.

Two query categories are created, one for location product alerts, the other for resource alerts.

Create 2 queries to display the alerts.


Product alerts, if necessary choose Refresh to get the updated alerts. Check below database alerts.

Supply Shortage

Shortfall below safety stock

In Optimizer scenario, you can only focus on Location Product alerts because Optimizer is constraints based planning, so there should have no resource overload alerts.

2. There should have no alert generated. That means the demand is satisfied with no delay or non-fulfillment.

3. You can check the planning result using the Interactive Planning screen with the following steps.

4. On the Interactive Planning screen, select your Selection Profile, for example,, <02_PLANNER_B>, load the location product <SCM-PROD02/DC2300> to the work area.

5. On the work area, the planner can see quantity 100 is created for Stock Transfer Req. Receipt key figure on the same time bucket as the requirement. Right-click this cell, choose Display the details from the context menu, the detailed receipt information is displayed at the bottom of the screen. 80 pc is supplied from PL1000 first, and the left 20 is supplied from PL1100.

Net requirement at DC = 100(forecast) – 20(stock on hand) + 20(safety stock).

The transportation lane PL1000 ® DC2300 has higher priority than PL1100®DC2300, so requirement is supplied from PL1000 first with 80pcs (max capacity), the left 20 is supplied from PL1100. This is the optimal solution.

The result can be a little bit different because of workdays in the buckets, or master data setting difference. For example, 4 days workdays in <current week + 2 weeks>, then the result will be different.

6.1.5 Releasing the Supply Plan

UseThere are two kinds of release mode. In this document, we will only show the attended mode as the example,

Option 1: Unattended Mode

After SNP orders are saved at APO system, orders are transferred immediately to SAP ERP. Both systems then have same view on demand and supply plan.

Option 2: Attended Mode



After APO Order is saved at APO, it will not be transferred immediately to SAP ERP. The changes pointers are used to collect the changes. The planner can first check the planning result and then manually trigger the order transfer.

Prerequisites Active Integration models exist in order to transfer the SNP orders to ERP. For this package,

you need to include planned order and purchase requisition in the integration model. Distribution definition is customized correctly.

6.1.5.1Attended Mode

UseThe periodic publication of planning results can be chosen if data that has been generated or changed in SAP APO does not have to be transferred immediately to SAP R/3. This is often the case for Supply Network Planning (SNP). Periodic publication is the default setting in SNP Customizing.

Transferring the data at a later point in time (for example, using background processing that is scheduled to run at night) has performance benefits because it evens out the load on the CIF interface.

In comparison to the direct publication of planning results, periodic publication records and collects change pointers (see figure below). You can start the processing of change pointers manually or schedule this to take place as background processing. The change pointers are deleted when they have been processed.

Prerequisites Customize to periodic transfer SNP orders to OLTP system


SAP SCM menu Advanced Planning and Optimization ® APO Administration ® Integration ® Publication ® Publish Orders

Transaction Code /SAPAPO/C5

2. On the Select and Copy Orders screen, make the following entries:


Orders

Order number Leave it blank.

APO order type Enter the order type, for example,, from 021 to 031

021 External procurement 026 Confirmation for scheduling

agreement 031 In-house production 036 Project orders 053 Sales order

300 Production campaign

Order GUID Leave it blank.

Products

Product Identifier Name of the location product




Production Planner Planner who is responsible for the location product in Production Planning and Detailed Scheduling (PP/DS)

SNP Planner Enter the SNP planner, for example,, <B>

The customer can also choose other selection field for example, product number.

Demand Planner Planner who is responsible for the location product in Demand Planning

Transportation Planner

Planner who is responsible for the location product in Transportation Planning

Locations

Source location For stock transfer: issuing plant or vendor

Source location type Use the input help to choose the number of the required location type.

Destination location Recipient

Destination location type

Use the input help to choose the number of the required location type.

Other Criteria

Method N – Create new order [New]

Newly created orders often have the value C.

C – Change order [Change]

D – Delete or partially delete document [Delete]

R – Completely delete order [Remove]

Creation time stamp Time of event creation

User name Logon name of the user in the SAP ERP system

Flow Control

Maximum number of hits

The default value is 1000 Number of maximum selected change pointers

Block size Enter the number of change pointers you want to be processed in each block.

The block size is set to 1000 by default.

The system processes the change pointers selected for transfer on a block by block basis depending on the figure entered here. As the block size increases, so does the associated memory requirement. An application log is written for every block that is processed.




Processing Direction The system only evaluates this data if you have entered filter criteria in the Products screen section. Both processing directions have an effect on performance. Tests should be made to determine which processing direction results in higher performance in your system.

From Product Selected The system determines the associated change pointers depending on the product/planner entered

From Change Pointer

The system begins with the selected change pointers and filters out those that do not meet the filter criteria.

Background processing

This is only valid for background processing.

Delete Events If you set this indicator, the system deletes all selected change pointers without sending them first.

Detailed Job Log If you set this indicator, you receive detailed information in the job log.




Variant Name Enter the variant name, for example,, <YP_C5>

Description Enter the description, for example,, <Process change pointers>

5. Choose Save.

You can use the program variant when you schedule a background job.

6. On the Select and Copy Orders, choose Execute.

7. All orders with change pointers are listed on the Select and Copy Orders screen, select all rows, and choose Process Change Pointers.

8. Go to SAP ERP system, using MD04, the planner can see the planning result is transferred to ERP system correctly.

6.2 Finite planning: Capacity Constraint (Production Rate)



6.2.1 Maintaining the Demand DataRepeat the procedure in the chapter 6.1.1 to maintain the demand for this test case.





6.2.2 Finite Planning with SNP OptimizerYou can refer to the chapter 6.1.2 for detail.

6.2.3 Checking the KPIs with SAP APO Planner’s HomepageYou can refer to the chapter 6.1.3 for detail.

6.2.4 Checking and Analyzing the Alerts

UseThe planner can check the alerts in the Alert Worklist at APO planner’s homepage. The alerts listed below are relevant for this Optimizer scenario:

Supply Shortage Shortfall below safety stock








Product alerts, if necessary choose Refresh to get the updated alerts. There is an alert with Alert Type Supply Shortage generated for SCM-PROD02/DC2300.

The alert is created at DC level.


3. The planner can also choose Goto ® Supply and Demand Planning, the Interactive Planning screen is pop-up, and the location/product for that alert is loaded automatically.

4. Check the Supply shortage key figure for SCM-PROD02/DC2300. The supply shortage happened at <current week + 3 weeks>.

Select the capacity data view, you can found the work center is fully loaded before <current week + 3 weeks>. So the demand can only be met with delay.

The alert is for product SCM-PROD02 because the production rate for SCM-PROD02 is lower than SCM-PROD03, so the system tries to produce SCM-PROD03 first. (In this example, we don’t maintain the product priority, so the system treats these two products with the same priority.)

You may get supply shortage alerts also for the product SCM-PROD03. This is probably because the workdays or the testing date, which reduces the available capacity. In case of supply shortage alerts for the product SCM-PROD03, this should be ignored or the demand lowered.

ResultThe planners reviewed the Alerts shown on the planner’s home pages.

6.2.5 Releasing the Supply Plan You can refer to the chapter 6.1.5 for detail.

6.3 Finite planning: Capacity Constraint (Product Priority)



Based on the test case 2, in this test case, the planner changes the priority for the product SCM-PROD02@DC2300. Then during Optimizer run, the system tries to satisfy the demand of the product SCM-PROD02.

Prerequisites

Step 1: Change the Product Priority Master Data1. Access the activity .using the following navigation options:

SAP SCM menu Advanced Planning and Optimization® Master Data ® Product ® Product

Transaction code /SAPAPO/MAT1

2. On the Product Master: Initial Screen, make the following entry, and choose Change.


Product Enter the product number, for example, SCM-PROD02

–

Location Enter the location, for example, DC2300 –

3. On the Change Product <your product number> for Location <your location> screen, make the following entry:

Tab page Field name User action and values Comment

SNP2 Priority Enter the priority 1 You can assign values from 0 to 255 for the priority. The value 1 represents the highest priority, whereas 255 is the lowest priority. If you enter the value 0 or no value, the system equates this with priority 255.



4. Choose Save.

Remember to change it back when you finish the optimizer scenario testing.

6.3.1 Maintaining the Demand DataFor the test case 3, you do not need to change the demand data.













In this example, there will have a supply shortage alert also for the product SCM-PROD02. Because we set 20 pc safety stock for this product, the safety stock demand is considered finally.

Also in the SNP Optimizer Profile, we leave the checkbox Loc. Prod. Prio. more important than Prio.of Prio.Classes unchecked.



The following figure shows exactly how the system proceeds if the demand priority is more important than the product priority


3. The planner can also choose Goto ® Supply and Demand Planning, the Interactive Planning screen is pop-up, the location/product for that alert is loaded automatically.


Select the capacity data view for the resource in plant 1000, you can see the work center is fully loaded before <current week + 3 weeks>. So the demand can only be met with delay.

The alert is for product SCM-PROD03 because it has a lower priority than the product SCM-PROD02, so the system tries to satisfy the SCM-PROD02 demand first.

In this example, there has also a supply shortage alert for the product SCM-PROD02. Because we set 20 pcs safety stock for this product, the safety stock priority is considered finally.



6.4 Finite planning: Capacity Constraint (Sales Order Priority)



In this test case, the planner needs to create a sales order at SAP ERP system. Then during Optimizer run, the system will try to satisfy the sales order demand first.

6.4.1 Maintaining the Demand Data Repeat the procedure in the chapter 6.1.1 to maintain the demand for this test case.


Product Plant Requirement on

<Current week + 2 weeks>

Requirement on


SCM-PROD02 2300 100 pcs 200 pcs

Delete the demand for the product SCM-PROD03@DC2300.

For testing purpose, you need to create a sales order at SAP ERP with the following information. Please refer to the chapter 7.2 in Appendix for how to create sales order at SAP ERP.

Product Plant Requirement on



Remember to delete the sales order after you finish this test case. Refer to the chapter 7.3 for how to delete the sales order.
















3. The planner can also choose Goto ® Supply and Demand Planning, the Interactive Planning screen is pop-up, the location/product for that alert is loaded automatically.


Select the data view for capacity, you can see the work center is fully loaded before <current week + 3 weeks>. So the demand can only be met with delay.

The alert is for product SCM-PROD02 because the sales order has the higher priority than the forecast, so the system tries to satisfy SCM-PROD03 demand first.

The result can be a little bit different for example, the support shortage alerts happened at <current week + 2 weeks>. This is probably because of your testing date especially when you test at the later part of the week.

Check the setting in your SNP Optimizer Profile, on the Automatic Cost Generation tab page, make sure the checkbox for the Loc.Prod.Prio.more important than Prio.of Prio.Classes is unchecked.





6.5 Finite planning: Raw Material Constraint

Prerequisites

Step 1: Create Fixed Receipt1. Access the activity .using the following navigation options:

SAP SCM menu Advanced Planning and Optimization® Production Planning ® Interactive Production Planning ® Product View

Transaction code /SAPAPO/RRP3

2. On the Product View screen, make the following entry:


Plng Version Enter 000

Product Enter the product number, for example, SCM-RAW02 –

Location Enter the vendor location, for example, SU0000390001

–

3. Choose Create Order.

4. On the Create Order screen, make the following entry:


Rec./Reqmts Qty

Enter the order quantity, for example, 60 Make sure the order quantity is less than demand.




Avail/Reqmt Date

Enter the requirement date, for example, <current date + 2 weeks>

–

5. Choose Enter and Save.

A fixed receipt order is created.

Step 2: Change the Vendor Location Material Master Data1. Access the activity .using the following navigation options:

SAP SCM menu Advanced Planning and Optimization® Master Data ® Product ® Product




Product Enter the product number, for example, SCM-RAW02

–


–

3. On the Change Product <your product number> for Location <your location> screen, make the following entry:

Tab page Field name User action and values Comment

Procurement

Planned Deliv. Time

Enter value 999 You

4. Choose Save.

5. Repeat the step 2 to 4 to change the planned delivery time for vendor SU0000390002.

Remember to change it back when you finish this test case.

6.5.1 Maintaining the Demand DataFor this test case, delete the sales order at SAP ERP system, no need to change the other demand data.






Procedure



1. On the APO Planner’s Home Page screen, choose Alert Worklist, choose Query for Location Product alerts, if necessary choose Refresh to get the updated alerts. There is an alert with Alert Type Supply Shortage generated for SCM-PROD02/DC2300.



3. The planner can also choose Goto ® Supply and Demand Planning, the Interactive Planning screen is pop-up, and the location/product for that alert is loaded automatically.


The alert is generated because the planned delivery time for the raw materials has been set to 999 days, which cannot meet the requirement. The system considers this raw material constraint, so the finished goods demand at DC level cannot be satisfied.


6.6 Reverting the Setting ChangesAfter you finished the optimizer scenario testing, you need to revert the changes you have made to make sure other testers can start testing with no problem.

Step 1: Change back the Product Priority Revert the prerequisite step in test case 3 to change the product priority to 0.

Step 2: Change back the Planned Delivery TimeRevert the prerequisite step 2 in test case 5 to change the planned delivery time to 0.

7 Appendix

7.1 Posting Initial Stock in ERP

UseIn this activity, you create initial unrestricted stock for test purpose.


SAP ECC menu Logistics ® Materials Management ® Inventory Management ® Goods Receipt ® other

Transaction code MB1C

2. On the Enter Other Goods Receipts: Initial Screen, enter the following data, then choose Enter.




Movement Type 501

Plant 1000

Storage Location 1020

3. On the Enter Other Goods Receipts: New Items Screen, enter the following data.

Material Quantity Comment

SCM-PROD01 50

4. Choose Save. Confirm the warning message if any, to save the stock.

5. Repeat step 2-4 to create intial stock for other locations.

Plant Storage Location Material Quantity

2300 1020 SCM-PROD01 60

1100 1140 SCM-PROD01 60

7.2 Creating a Sales Order

Use Here we create a sales order, which has higher priority than the forecast. During Optimizer run, the system will satisfy the sales order first.


SAP ECC menu Logistics ® Sales and Distribution ® Sales ® Orders ® Create

Transaction code VA01

2. Use the following data to create the sales order:


Order Type Choose the order type, for example,, <OR>

Sales Organization Enter <1000>

Distribution Channel Enter <10>

Division Enter <10>

Sold-To Party Enter <100000>

Ship-To Party Enter <100000>

PO Number Enter <testing>

Sales tab page

Material SCM-PROD03

Order Quantity 100

Delivery Date <Current week + 3 weeks>

Plant 2300

Amount Enter e.g., <20>

3. Choose Save. Write down the sales order number.



7.3 Deleting a Sales Order


SAP ECC menu Logistics ® Sales and Distribution ® Sales ® Orders ® Change

Transaction code VA02

2. On the Change Sales Order: Initial Screen, enter the sales order number you created before, then choose Enter.

You can also get the sales order number using transaction code MD04.

3. On the Change Standard Order <your order number>: Overview screen, choose Sales document from the menu bar, then choose Delete.

7.4 Maintaining the Vendor Location Material Master

UseFor optimizer scenario, test case 5, you need to maintain the planned delivery time for vendor location material master manually.

Procedure1. To carry out the activity, choose one of the following navigation options:

SAP SCM menu Advanced Planning and Optimization ® Master Data ® Product ® Product




Product Enter the raw material, for example, SCM-RAW02

–


–

3. On the Change Product <your product number> for Location <your location> screen, choose Procurement. tab page, enter e.g., <999> in the Planned Deliv. Time field.

4. Choose Save.

5. Repeat the step 2 to step 4 to create the following product location master:

Products Location Planned Deliv. Time

SCM-RAW02 SU0000390002 999
