PeopleSoft 8.00.01 Production Planning PeopleBook

PeopleSoft 8.00.01Production Planning PeopleBook

PeopleSoft 8.00.01 Production Planning PeopleBook

SKU MAPLr8SP1B 1200

PeopleBooks Contributors: Teams from PeopleSoft Product Documentation and

Development.

Copyright © 2001 by PeopleSoft, Inc. All rights reserved.

Printed in the United States of America.

All material contained in this documentation is proprietary and confidential to PeopleSoft,

Inc. and is protected by copyright laws. No part of this documentation may be reproduced,

stored in a retrieval system, or transmitted in any form or by any means, including, but not

limited to, electronic, graphic, mechanical, photocopying, recording, or otherwise without theprior written permission of PeopleSoft, Inc.

This documentation is subject to change without notice, and PeopleSoft, Inc. does not warrant

that the material contained in this documentation is free of errors. Any errors found in this

document should be reported to PeopleSoft, Inc. in writing.

The copyrighted software that accompanies this documentation is licensed for use only in

strict accordance with the applicable license agreement which should be read carefully as it

governs the terms of use of the software and this documentation, including the disclosure

thereof.

PeopleSoft, the PeopleSoft logo, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, and

Vantive are registered trademarks, and PeopleTalk and "People power the internet." are

trademarks of PeopleSoft, Inc. All other company and product names may be trademarks of

their respective owners.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O N T E N T S i i i

C o n t e n t s

About This PeopleBookBefore You Begin .............................................................................................................. xi

PeopleSoft Application Fundamentals............................................................................... xi

Related Documentation .................................................................................................... xii

Documentation on the Internet ..................................................................................xiii

Documentation on CD-ROM ....................................................................................xiii

PeopleBooks Standard Field Definitions.......................................................................... xv

Typographical Conventions and Visual Cues................................................................. xvii

Page and Panel Introductory Table................................................................................xviii

Comments and Suggestions............................................................................................. xix

Chapter 1

Overview of PeopleSoft Production Planning

What Is PeopleSoft Production Planning?....................................................................... 1-1

Traditional MRP Approaches.................................................................................... 1-2

Material Requirements Planning....................................................................... 1-2

Manufacturing Resource Planning.................................................................... 1-2

Enterprise Resource Planning Using PeopleSoft Production Planning..................... 1-3

What PeopleSoft Production Planning Offers You ......................................................... 1-4

Managing Business Processes and Data Flow .......................................................... 1-5

Using Seamless Integration to Create Production Plans ........................................... 1-6

Moving and Balancing the Supply Chain ................................................................. 1-8

Using PeopleSoft Production Planning to Manage Your Shop Floor ....................... 1-8

Understanding Plans................................................................................................ 1-10

Working With Constraints ...................................................................................... 1-11

Understanding the Interactive Approach to Supply Chain Management ................ 1-11

Using an Integrated Model of Material and Capacity ............................................. 1-13

Consuming Inventory...................................................................................... 1-14

Using Resources.............................................................................................. 1-14

Supplying Inventory........................................................................................ 1-14

Linking PeopleSoft Production Planning to Your Enterprise ................................. 1-14

Using the System of Record.................................................................................... 1-15

Understanding the Production DataLink................................................................. 1-16

P E O P L E S O F T 8 . 0 0 . 0 1 P R O D U C T I O N P L A N N I N G P E O P L E B O O K J A N U A R Y 2 0 0 1

C O N T E N T S i v P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Resolving Plan Constraints in PeopleSoft Production Planning ............................. 1-17

Collaborating With PeopleSoft Production Planning.............................................. 1-18

Establishing Supply and Demand ........................................................................... 1-19

Analyzing Your Supply Chain Model ........................................................................... 1-20

Creating Flexible Reports .............................................................................................. 1-22

Maintaining Plan Data Using Workbenches, Graphical Charts, and Histograms.......... 1-22

Chapter 2

Setting Up Production Planning

Before You Begin ............................................................................................................ 2-1

Defining PeopleSoft Production Planning-Specific Installation, User, and

|General Options........................................................................................................ 2-1

Defining the Concatenation Code for Configured Items........................................... 2-2

Setting Up Business Units for Your Production Planning System.................................. 2-2

Establishing Inventory, Order Management, and Purchasing Options............................ 2-3

Defining Inventory Attributes ................................................................................... 2-3

Defining Item Attributes by Units..................................................................... 2-4

Defining Transfer Attributes ............................................................................. 2-4

Defining Forecast Items .................................................................................... 2-5

Setting Up Stocking Periods ............................................................................. 2-6

Setting Up Demand Priority Families ............................................................... 2-6

Defining Order Management Options....................................................................... 2-6

Defining Forecast Product Information............................................................. 2-6

Defining Purchasing Attributes................................................................................. 2-7

Defining Manufacturing Options..................................................................................... 2-8

Manufacturing Data Used by Production Planning................................................... 2-8

Defining Resource Changeover Penalties ................................................................. 2-9

Defining Planning Resource Attributes..................................................................... 2-9

Using Production Planning Resources in Aggregate or Detail ............................... 2-10

Defining Production Planning Attributes ...................................................................... 2-10

Maintaining Aggregate Items.................................................................................. 2-10

Defining Product Forecast Percentages................................................................... 2-11

Defining Master Plan Data...................................................................................... 2-12

Defining Promise and Request Dates...................................................................... 2-14

Defining Roll Forward Phases ................................................................................ 2-15

Overview of the Roll Forward Feature ........................................................... 2-15

Setting Up Roll Forward Parameters .............................................................. 2-16

Setting Up Roll Forward Phases ..................................................................... 2-18

Defining Planning Attributes .................................................................................. 2-21

Defining Work Center Attributes ............................................................................ 2-22

Prioritizing Demand....................................................................................................... 2-22

J A N U A R Y 2 0 0 1 P E O P L E S O F T 8 . 0 0 . 0 1 P R O D U C T I O N P L A N N I N G P E O P L E B O O K

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O N T E N T S v

Defining Demand Priority Rules............................................................................. 2-24

Defining Lateness Tolerances ................................................................................. 2-26

Sourcing Demand .......................................................................................................... 2-27

Overview of Sourcing Templates............................................................................ 2-27

Solver Processing of Sourcing Template Data........................................................ 2-28

Setting Up Sourcing Templates............................................................................... 2-28

Defining Sourcing Templates ......................................................................... 2-29

Loading Sourcing Options .............................................................................. 2-34

Generating Sourcing Templates (PLS5000)............................................................ 2-38

Verifying Sourcing Options .................................................................................... 2-41

Defining Sourcing Inquiry Selection Criteria ................................................. 2-41

Viewing Sourcing Template Details ............................................................... 2-42

Viewing Sourcing Template - Production Option Details .............................. 2-44

Viewing Sourcing Template - Purchase Options Details................................ 2-46

Viewing Sourcing Template - Transfer Options Details................................. 2-47

Defining the Line Schedule Editor Defaults.................................................................. 2-48

Setting Up Item Changeover Families .................................................................... 2-49

Defining the Line Schedule Editor Color Scheme .................................................. 2-49

Setting Up the Line Schedule Editor General Defaults, Colors, Dimensions,

and Time Periods..................................................................................................... 2-50

Defining LSE General Settings....................................................................... 2-50

Defining LSE Dimensions .............................................................................. 2-52

Defining LSE Color Settings .......................................................................... 2-53

Defining LSE Time Periods ............................................................................ 2-55

Setting Up Line Schedule Editor Resource Entries Defaults .................................. 2-57

Defining LSE Balancing Defaults........................................................................... 2-58

Defining LSE Bar Colors Defaults.......................................................................... 2-60

Defining LSE Filters Defaults................................................................................. 2-61

Setting Up Bar Item Filters ............................................................................. 2-61

Setting Up Bar Color Filters ........................................................................... 2-62

Viewing the LSE Chart ........................................................................................... 2-62

Verifying Production Planning Data.............................................................................. 2-63

Understanding the Data Verification Process ......................................................... 2-63

Generating the Planning Data Inconsistency Report (PLS3000) ............................ 2-63

Chapter 3

Setting Up the Production DataLink

Overview of the Production DataLink Process................................................................ 3-1

Setting Up Solvers Using the Production DataLink ........................................................ 3-3

Reviewing Time Fences Used by Solvers................................................................. 3-5


C O N T E N T S v i P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Pegged Chain Processing for Solvers........................................................................ 3-7

Using Solvers to Process a Plan ................................................................................ 3-8

Overview of the Material Planning Solver.............................................................. 3-11

Overview of the Feasible Planning Solver .............................................................. 3-12

Verifying Current Supply and Demand Quantities ......................................... 3-13

Satisfying Unmet Demand .............................................................................. 3-13

Verifying Demand Priority for Frozen Tasks ................................................. 3-13

Ensuring Positive On-Hand Quantity at the Early Fence................................ 3-14

Sourcing Allocations and Options to Reduce Lead Time ............................... 3-14

Reducing Excess Inventory............................................................................. 3-15

Making the Plan Capacity Feasible................................................................. 3-15

Determining Weighted Priorities for Capacity Planning ................................ 3-17

Improving Plan Quality................................................................................... 3-19

Checking Effectivities..................................................................................... 3-20

Overview of the LP Solver...................................................................................... 3-20

Enforcing Constraints...................................................................................... 3-21

Planning Features Processed by the LP Solver ............................................... 3-22

Overview of Iterative Repair/Optimizer.................................................................. 3-24

Using the Production DataLink to Create a Master or Material Plan ............................ 3-25

Setting Up Run Types, Plan Types, Time Fences, and WIP/Roll Forward Options ..... 3-26

Defining General Time Fence Information ............................................................. 3-27

Defining Frozen Fence Offsets ............................................................................... 3-33

Defining WIP/Roll Forward Details ....................................................................... 3-34

Including Demand and Supply in the Production DataLink Run .................................. 3-36

Defining Demand Options ...................................................................................... 3-36

Defining Supply Options......................................................................................... 3-40

Setting Planning Run and Solver Options ..................................................................... 3-42

Selecting a Solver for Plan Generation ................................................................... 3-42

Defining Material Planning Options ....................................................................... 3-44

Defining Feasible Planning Solver Options ............................................................ 3-47

Defining Linear Programming Options................................................................... 3-50

Defining Iterative Repair Settings........................................................................... 3-52

Setting Up Command File and Source File Information ............................................... 3-55

Verifying Planning Server Connection Settings ............................................................ 3-58

Chapter 4

Generating the Production Plan

Overview of the Production Plan Process........................................................................ 4-1

Before You Begin ............................................................................................................ 4-2

Generating the Production Plan ....................................................................................... 4-2


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O N T E N T S v i i

Running Planning Solvers......................................................................................... 4-3

Defining Global Preferences ..................................................................................... 4-3

Creating a Material Plan............................................................................................ 4-5

Creating a Feasible Plan............................................................................................ 4-8

Generating a Plan Using Linear Programming (LP) ............................................... 4-12

Chapter 5

Managing the Master and Material Plans

Overview of the Master and Material Planning Process.................................................. 5-1

Master Plan Process Flow ......................................................................................... 5-3

Material Plan Process Flow....................................................................................... 5-4

Before You Begin ............................................................................................................ 5-4

Maintaining Master and Material Plans........................................................................... 5-5

Defining the Master or Material Workbench Search Parameters.............................. 5-5

Using the Master or Material Plan Summary............................................................ 5-7

Changing Server Settings................................................................................ 5-11

Changing Row Types...................................................................................... 5-12

Drilling Down to Maintain Scheduled Receipts...................................................... 5-13

Showing Supply .............................................................................................. 5-15

Showing Demand ............................................................................................ 5-18

Drilling Down to Add or Change Planned Orders .................................................. 5-20

Adding Production Orders .............................................................................. 5-22

Adding Purchase Orders ................................................................................. 5-24

Adding Transfers............................................................................................. 5-25

Maintaining Production Orders....................................................................... 5-26

Maintaining Purchase Orders .......................................................................... 5-29

Maintaining Transfer Orders........................................................................... 5-30

Analyzing the Master or Material Plan.......................................................................... 5-31

Reviewing the Master or Material Plan Summary .................................................. 5-32

Viewing the Master or Material Plan Detail ........................................................... 5-33

Reviewing Master or Material Plan Exceptions...................................................... 5-36

Selecting Exceptions for Review .................................................................... 5-37

Defining Advanced Filters .............................................................................. 5-39

Reviewing the Results..................................................................................... 5-40

Using the Planning Scorecard to Review Your Master or Material Plan................ 5-43

Overview of the Planning Scorecard............................................................... 5-43

Using the Planning Scorecard Page ................................................................ 5-44

Reviewing Request Date Constraint Violations.............................................. 5-47

Reviewing Safety Stock Constraint Violations............................................... 5-50

Reviewing Promise Date Constraint Violations.............................................. 5-51


C O N T E N T S v i i i P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Reviewing Excess Stock Constraint Violations .............................................. 5-54

Reviewing BI Shortage Constraint Violations ................................................ 5-55

Reviewing RM Shortage Constraint Violations.............................................. 5-57

Reviewing Aggregate Capacity Constraint Violations ................................... 5-59

Reviewing Forecast Fulfillment Constraint Violations................................... 5-62

Reviewing Transfer Shipment Date Constraint Violations............................. 5-64

Filtering Material or Master Plan Scorecard Data .......................................... 5-66

Chapter 6

Managing the Capacity Plan

Overview of the Capacity Planning Process.................................................................... 6-1

Before You Begin ............................................................................................................ 6-1

Maintaining the Capacity Plan......................................................................................... 6-1

Defining the Resource Workbench Search Parameters............................................. 6-2

Using the Capacity Summary.................................................................................... 6-4

Viewing the Resource Load ...................................................................................... 6-6

Adding Production ............................................................................................ 6-9

Viewing the Production Details .............................................................................. 6-10

Viewing the Production Outputs ............................................................................. 6-11

Analyzing the Capacity Plan ......................................................................................... 6-12

Viewing the Capacity Plan Summary ..................................................................... 6-12

Using the Planning Scorecard to Review Your Capacity Plan................................ 6-14

Filtering Capacity Plan Scorecard Data .......................................................... 6-14

Viewing Capacity Violations .......................................................................... 6-15

Chapter 7

Committing the Production Plan

Overview of the Commit Plan Process ............................................................................ 7-1

Receiving Planning Messages (PLS2000) ....................................................................... 7-3

Identifying Planning Message Options ..................................................................... 7-3

Verifying Planning Server Settings........................................................................... 7-5

Using Unprocessed Messages From a Previous Plan ...................................................... 7-9

Using the Master Plan Data Page.............................................................................. 7-9

Creating Planning Reports ............................................................................................. 7-10

Understanding Planning Report Options................................................................. 7-10

Creating Your Own Layout............................................................................. 7-11

Generating Supply and Demand Detail........................................................... 7-12

Understanding Simulation and Master Plan Reporting................................... 7-13

Generating the Planning Report (PLS2001)............................................................ 7-13

Before You Begin ........................................................................................... 7-14


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O N T E N T S i x

Defining Selection Criteria ............................................................................. 7-14

Defining Report Options ................................................................................. 7-16

Specifying Row Types .................................................................................... 7-17

Using the Planning Messages Report (PLS4001).......................................................... 7-21

Defining Message Selection Criteria....................................................................... 7-21

Defining Production, Purchase Order, and Inventory Transfer Message

Reporting Options ................................................................................................... 7-23

Displaying Planning Item Use Up Information ............................................................. 7-25

Displaying Planning Use Up Information ............................................................... 7-25

Generating the Planning Use Up Report ................................................................. 7-26

Chapter 8

Processing Planning Messages in PeopleSoft Production Management

Overview of the Production Messages Review and Application Process ....................... 8-1

Before You Begin ............................................................................................................ 8-2

Reviewing Production Messages ..................................................................................... 8-2

Selecting Production Messages for Review .............................................................. 8-2

Reviewing the Production Message Summary.......................................................... 8-5

Reviewing the Production Message Summary Production Details................... 8-5

Reviewing Production and Operations Detail ........................................................... 8-7

Viewing Additional Production Details ............................................................ 8-8

Viewing Operation Details................................................................................ 8-9

Reviewing Production Exceptions................................................................................. 8-10

Reviewing Production Exception Details ............................................................... 8-10

Applying Production Messages ..................................................................................... 8-12

Applying Production Messages............................................................................... 8-13

Chapter 9

Processing Planning Recommendations in PeopleSoft Inventory

Overview of the Inventory Messages Review and Application Process ......................... 9-1

Before You Begin ............................................................................................................ 9-1

Reviewing Inventory Transfer Messages ........................................................................ 9-2

Selecting Inventory Transfer Messages for Review.................................................. 9-2

Reviewing the Inventory Transfer Message Summary Details................................. 9-4

Displaying Message Details.............................................................................. 9-6

Applying Inventory Transfer Messages........................................................................... 9-7

Reviewing Inventory Exceptions..................................................................................... 9-9

Reviewing Inventory Planning Exceptions ............................................................... 9-9

Viewing Inventory Exception Details ............................................................. 9-10

Reviewing Material Stock Request Messages ............................................................... 9-11


C O N T E N T S x P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Selecting Material Stock Request Messages ........................................................... 9-11

Reviewing the Material Stock Message Summary MSR Details............................ 9-12

Reviewing Material Stock Request Exceptions............................................................. 9-13

Viewing Material Stock Request Exception Details ............................................... 9-14

Chapter 10

Processing Planning Recommendations in PeopleSoft Purchasing

Overview of the Purchasing Planning Messages Review and Application Process ...... 10-1

Before You Begin .......................................................................................................... 10-1

Reviewing Purchasing Messages................................................................................... 10-2

Selecting Purchasing Messages for Review............................................................ 10-2

Reviewing the Purchasing Message Summary: PO Details .................................... 10-4

Reviewing Purchasing Exceptions................................................................................. 10-7

Reviewing Purchasing Exception Details ............................................................... 10-7

Applying Purchase Messages ........................................................................................ 10-8

Chapter 11

Processing Planning Recommendations in PeopleSoft Order Management

Overview of the Order Management Planning Messages Review Process ................... 11-1

Before You Begin .......................................................................................................... 11-1

Reviewing Sales Order Messages.................................................................................. 11-2

Selecting Sales Order Messages for Review........................................................... 11-2

Reviewing the Sales Order Message Summary....................................................... 11-3

Reviewing Message Summary: Sales Order Details....................................... 11-3

Reviewing Sales Order Exceptions................................................................................ 11-5

Reviewing the Sales Order Exception Details ........................................................ 11-5

Chapter 12

PeopleSoft Production Planning Report Descriptions

PeopleSoft Production Planning Standard Reports........................................................ 12-1

Standard Financial Reports............................................................................................ 12-2

Index

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R E F A C E x i

A B O U T T H I S P E O P L E B O O K

The book provides you with the information you will need for implementing and using

PeopleSoft Production Planning. You can order the online version by requesting SKU

FSCMB8SP1R0, or the hard-copy version by requesting SKU MAPLr8SP1B 1200.

This section describes information you should know before you begin working with PeopleSoft

products and documentation, including PeopleSoft-specific documentation conventions,

information specific to the PeopleSoft Supply Chain Management product line, how to order

additional copies of our documentation, and so on.

Before You Begin

To benefit fully from the information covered in this book, you need to have a basic

understanding of how to use PeopleSoft applications. We recommend that you complete at leastone PeopleSoft introductory training course.

You should be familiar with navigating around the system and adding, updating, and deleting

information using PeopleSoft windows, menus, and pages. You should also be comfortable using

the World Wide Web and the Microsoft® Windows or Windows NT graphical user interface.

Because we assume you already know how to navigate around the PeopleSoft system, much of

the information in this book is not procedural. That is, it does not typically provide step-by-step

instructions on using tables, pages, and menus. Instead, we provide you with all the information

you need to use the system most effectively and to implement your PeopleSoft application

according to your organizational or departmental needs. This book expands on the material

covered in PeopleSoft training classes.

PeopleSoft Application Fundamentals

The PeopleSoft Production Planning PeopleBook provides you with implementation and

processing information for your PeopleSoft Production Planning system. However, there is

additional, essential information describing the setup and design of your system that is contained

in a companion volume of documentation called PeopleSoft Application Fundamentals.

PeopleSoft Application Fundamentals consists of important topics that apply to many or all

PeopleSoft applications across the PeopleSoft Supply Chain Management product line. Whether

you are implementing only PeopleSoft Production Planning, some combination of products

within the product line (for example, PeopleSoft Enterprise Planning, Inventory, Purchasing, and

Manufacturing), or the entire PeopleSoft Supply Chain Management system, you should be

familiar with the contents of this central PeopleBook. It is the starting point for fundamentals

such as setting up control tables and administering security.

In the PeopleSoft Applications Fundamentals PeopleBook, we've included common information

pertinent to all applications in the PeopleSoft Supply Chain Management product line, such as


P R E F A C E x i i P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

defining general options. If you're upgrading from a previous PeopleSoft release, you may notice

that we've removed some topics or topic headings from the individual application PeopleBooks

and consolidated them in this single reference book. You’ll now find only application-specific

information in your individual application PeopleBooks. This makes the documentation as a

whole less redundant. Throughout each PeopleBook, we provide cross-references to PeopleSoftApplication Fundamentals and other PeopleBooks.

Below you’ll find a list of those PeopleSoft Application Fundamentals sections that apply

specifically to PeopleSoft Production Planning.

Defining Financial and Supply Chain Management General Options describes how to set up

your basic structure and processing rules for PeopleSoft Financials and Supply ChainManagement applications using pages in the Define General Options menu.

Securing Your System explains how to set up application security for your system. The chapter

provides you with an overview of the PeopleSoft approach to application security and explains

the choices you must make in deciding what level of security to put in place throughout yoursystem, what key fields to secure, and whether it will be done by user IDs or user classes.

Maintaining Vendor Information explains how vendor information is positioned in the control

hierarchy, and guides you through the process of setting up vendors in the system. It also

discusses how to search for, inquire on, approve, inactivate, delete and report on vendors.

Structuring Procurement Options explains how to and where to enter basic system and default

information that doesn’t change or is used repeatedly throughout the systems for many aspects of

your payables and purchasing systems.

Working With Items discusses how to search for and work with items in the PeopleSoft

components. The topics covered include setting up and using substitute items, managing item

status, and defining quantity precision rules for item transactions.

Defining Item Control Values discusses how to set up item attributes using the Define Item

Controls menu. These attributes become the defaults or selection options for new items.

Defining Items discusses how to define items for PeopleSoft setID and business unit levels.

Items must be defined before you can use them in any PeopleSoft application.

Finding Item Information discusses the Inquiry and Report pages under the Define Items and

Define Item Control Data menus.

Working with Warehouse Management Systems describes the implementation of a full

integration between PeopleSoft Purchasing, PeopleSoft Payables, PeopleSoft Order Management,

PeopleSoft Inventory and a third-party warehouse management system (WMS). Integrating

PeopleSoft with a WMS can help you streamline your order-to-cash and procure-to-pay business

processes, which in turn can help you reduce costs, improve service levels, and generate morerevenue.

Related Documentation

To add to your knowledge of PeopleSoft applications and tools, you may want to refer to the

documentation of other PeopleSoft applications. You can access additional documentation for


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R E F A C E x i i i

this release from PeopleSoft Customer Connection (www.peoplesoft.com). We post updates and

other items on Customer Connection, as well.

Important! Before upgrading, it is imperative that you check PeopleSoft Customer

Connection for updates to the upgrade instructions. We continually post updates as we

refine the upgrade process.

Documentation on the Internet

You can order additional copies of the PeopleBooks CDs through the Documentation section of

the PeopleSoft Customer Connection Web site: http://www.peoplesoft.com/

You’ll also find updates to the documentation for this and previous releases on Customer

Connection. Through the Documentation section of Customer Connection, you can download

files to add to your PeopleBook library. You'll find a variety of useful and timely materials,

including updates to the full PeopleSoft documentation delivered on your PeopleBooks CD.

Documentation on CD-ROM

Complete documentation for this release is provided on the CD-ROM PeopleSoft 8.00.01Financials/Supply Chain Management PeopleBooks, SKU CD-FSCMB8SP1R0.

Your access to PeopleSoft PeopleBooks depends on which PeopleSoft applications you've

licensed. You may not have access to some of the PeopleBooks listed here.

The CD includes the following PeopleBooks (presented in HTML format) that you can print in

whole or in part:

• PeopleSoft 8.00.01 Advanced Planning Client

• PeopleSoft 8.00.01 Application Fundamentals for Financials and Supply Chain Management

• PeopleSoft 8.00.01 Asset Management

• PeopleSoft 8.00.01 Billing

• PeopleSoft 8.00.01 Bills and Routings

• PeopleSoft 8.00.01 Budgets

• PeopleSoft 8.00.01 Contracts

• PeopleSoft 8.00.01 Cost Management

• PeopleSoft 8.00.01 Deduction Management


P R E F A C E x i v P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

• PeopleSoft 8.00.01 Demand Planning

• PeopleSoft 8.00.01 eBill Payment

• PeopleSoft 8.00.01 Engineering

• PeopleSoft 8.00.01 Enterprise Planning

• PeopleSoft 8.00.01 eProcurement

• PeopleSoft 8.00.01 eProduct Management

• PeopleSoft 8.00.01 eStore

• PeopleSoft 8.00.01 eSupplier Collaboration

• PeopleSoft 8.00.01 Flow Production

• PeopleSoft 8.00.01 General Ledger

• PeopleSoft 8.00.01 Inventory

• PeopleSoft 8.00.01 Inventory Planning

• PeopleSoft 8.00.01 Mobil Time and Expense

• PeopleSoft 8.00.01 Order Management

• PeopleSoft 8.00.01 Order Promising

• PeopleSoft 8.00.01 Payables

• PeopleSoft 8.00.01 Product Configurator

• PeopleSoft 8.00.01 Production Management

• PeopleSoft 8.00.01 Production Planning

• PeopleSoft 8.00.01 Projects

• PeopleSoft 8.00.01 Purchasing

• PeopleSoft 8.00.01 Quality

• PeopleSoft 8.00.01 Receivables

• PeopleSoft 8.00.01 Remote Order Entry

• PeopleSoft 8.00.01 Resource Management

• PeopleSoft 8.00.01 Treasury

• PeopleTools

• Setting Up Your Manufacturing System


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R E F A C E x v

• Using PeopleSoft Applications

• Using PeopleBooks

PeopleBooks Standard Field Definitions

Throughout our product documentation, you will encounter fields or page elements that are used

on many application pages or panels. This section lists the most common page elements andprovides standard definitions.

Field or Page Element Definition

As of Date The last date for which a report or process includes data.

Description Freeflow text up to 30 characters.

Effective Date Date on which a table row becomes effective; the date that

an action begins. For example, if you want to close out a

ledger on June 30, the effective date for the ledger closing

would be July 1. This date also determines when you can

view and change the information. Pages or panels and

batch processes that use the information use the current

row.

For more information about effective dates, see PeopleSoft

8.00.01 Using PeopleSoft Applications PeopleBook,

“Working With Pages”.

EmplID (employee ID) Unique identification code for an individual associated

with your organization.

Language or Language

Code

The language in which you want the field labels and report

headings of your reports to print. The field values appear

as you enter them.

Language also refers to the language spoken by an

employee, applicant, or non-employee.

Process Frequency group

box

Designates the appropriate frequency in the Process

Frequency group box:

Once executes the request the next time the batch process

runs. After the batch process runs, the process frequency

is automatically set to Don't Run.

Always executes the request every time the batch process

runs.

Don't Run ignores the request when the batch process

runs.

Report ID The report identifier.


P R E F A C E x v i P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Field or Page Element Definition

Report Manager This button takes you to the Report List page, where you

can view report content, check the status of a report, and

see content detail messages (which show you a description

of the report and the distribution list).

Process Monitor This button takes you to the Process List page, where you

can view the status of submitted process requests.

Run This button takes you to the Process Scheduler request

page, where you can specify the location where a process

or job runs and the process output format.

For more information about the Report List page, the

Process List page, and the Process Scheduler, see

PeopleTools 8.12 Process Scheduler PeopleBook,

“Process Scheduler Basic”.

Run Control ID A request identification that represents a set of selection

criteria for a report or process.

User ID The system identifier for the individual who generates a

transaction.

SetID An identification code that represents a set of control table

information or TableSets. A TableSet is a group of tables

(records) necessary to define your company’s structure

and processing options.

Short Description Freeflow text up to 15 characters.

Standard Unit of Measure

(UOM)

A type of unit used for quantifying in PeopleSoft systems,

and usually associated with items. Depending on the

application, units of measure might describe dimensions,

weights, volumes, or amounts of locations, containers, or

business activities. Examples include inches, pounds,

workhours, and standard cost dollars.

Unit (Business Unit) An identification code that represents a high-level

organization of business information. You can use a

business unit to define regional or departmental units

within a larger organization.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R E F A C E x v i i

Typographical Conventions and Visual Cues

To help you locate and interpret information, we use a number of standard conventions in ouronline documentation.

Please take a moment to review the following typographical cues:

monospace font Indicates PeopleCode.

Bold Indicates field names and other page elements, such as

buttons and group box labels, when these elements are

documented below the page on which they appear. When

we refer to these elements elsewhere in the

documentation, we set them in Normal style (not in bold).

We also use boldface when we refer to navigational paths,

menu names, or process actions (such as Save and Run).

Italics Indicates a PeopleSoft or other book-length publication.

We also use italics for emphasis and to indicate specific

field values. When we cite a field value under the page on

which it appears, we use this style: field value.

We also use italics when we refer to words as words or

letters as letters, as in the following: Enter the number 0,

not the letter O.

KEY+KEY Indicates a key combination action. For example, a plus

sign (+) between keys means that you must hold down the

first key while you press the second key. For ALT+W,

hold down the ALT key while you press W.

Cross-references The phrase "For more information" indicates where you

can find additional documentation on the topic at hand.

• Capitalized titles in italics indicate the title of another

PeopleBook. For example: For more information about

billing, see PeopleSoft 8.00.01 Billing PeopleBook.

• Capitalized titles in italics followed by chapter title in

quotes refer to a chapter in another PeopleBook. For

example: For more information about establishing rate

templates, see PeopleSoft 8.00.01 Projects PeopleBook,

“Integrating With PeopleSoft Billing and PeopleSoft

Contracts”.


P R E F A C E x v i i i P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

• Capitalized titles in quotes refer to another chapter

of this PeopleBook. For example: For more

information about contract status security, see

“Securing Your PeopleSoft Contracts System”.

• Capitalized titles refer to sections within this chapter of

this PeopleBook. For example: For more information

about Defining Contract Statuses, see Defining Your

Own Contract Statuses .

Text in this bar indicates information that you should pay particular attention to as you work

with your PeopleSoft system. If the note is preceded by Important!, the note is crucial and

includes information that concerns what you need to do for the system to function properly.

Text in this bar indicates cross-references to related or additional information.

Text within this bar indicates a crucial configuration consideration. Pay very close attention

to these warning messages.

Page and Panel Introductory Table

In the documentation, each page or panel description in the application will include an

introductory table with pertinent information about the page. Not all of the information will beavailable for all pages or panels.

Usage Describes how you would use the page or process.

Object Name Gives the system name of the panel or process as specified in the

PeopleTools Application Designer. For example, the Object Name of

the Detail Calendar panel is DETAIL_CALENDAR1.

Navigation Provides the path for accessing the page or process.

Prerequisites Specifies which objects must have been defined before you use the page

or process.

Access

Requirements

Specifies the keys and other information necessary to access the page.

For example, SetID and Calendar ID are required to open the Detail

Calendar page.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R E F A C E x i x

Comments and Suggestions

Your comments are important to us. We encourage you to tell us what you like, or what you

would like changed about our documentation, PeopleBooks, and other PeopleSoft reference and

training materials. Please send your suggestions to:

PeopleSoft Manufacturing Product Documentation Manager

PeopleSoft, Inc.

4460 Hacienda Drive

Pleasanton, CA 94588

Or send comments by email to the authors of the PeopleSoft documentation at:

[email protected]

While we cannot guarantee to answer every email message, we will pay careful attention to your

comments and suggestions. We are always improving our product communications for you.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L O V E R V I E W O F P E O P L E S O F T P R O D U C T I O N P L A N N I N G 1 - 1

C H A P T E R 1

Overview of PeopleSoft ProductionPlanning

PeopleSoft Production Planning offers an advanced planning system that uses Web-based access

to enable simultaneous optimization of plant-level procurement and production. Using a

powerful Planning engine, the application simultaneously solves material, capacity, inventory

targets, and customer request and promise dates to produce supply chain schedules.

Breaking the traditional mold of ERP systems, PeopleSoft built a planning application around the

concepts of constraint-based optimization. The decision to embed advanced planning and

scheduling technology, instead of building traditional MPS and MRP planning systems, has

resulted in a system that provides advanced planning solutions to help respond to today’s quick-changing business environment.

The application’s interface structure makes it easy for you to follow a logical business process

flow. PeopleSoft Production Planning focuses on a clearly defined business process that makes it

possible to work with a production plan at every stage of the planning cycle. For example, you

can look at demands and at constraints on meeting those demands throughout your supply chain.

Then you can efficiently create an optimal Master or Material Plan that highlights and resolves

exceptions within the supply chain.

What Is PeopleSoft Production Planning?

PeopleSoft Production Planning is an integrated suite of intelligent agent applications that helps

you plan and schedule your enterprise production plans. It gathers information from other

PeopleSoft applications using the Production DataLink and loads it into a memory-resident data

model so you can easily create and solve your production plan. After processing your data,

PeopleSoft Production Planning presents plans and schedules to you that you can review,

approve, and then apply back to your PeopleSoft database.

PeopleSoft Production Planning is an intelligent assistant, showing you potential problems with

the plan and schedule. It graphically depicts exceptions, enabling you to drill-down to find out

what could be keeping your operation from meeting its objectives. Working with the application,

you resolve these exceptions. You can make manual changes to the plan with an easy-to-use

graphical interface or you can let PeopleSoft Production Planning automatically resolve the

exceptions with its intelligent exception-based solvers.

The more successful an enterprise is in controlling its supply chain, the more responsive it can be

to the constantly changing demands placed on it by the marketplace. PeopleSoft Production

Planning makes it possible for you to interact in real time with the planning model. As you


1 - 2 O V E R V I E W O F P E O P L E S O F T P R O D U C T I O N P L A N N I N G P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

interact with the planning model, you can evaluate the impacts of changes to the plan and quickly

respond.

Traditional MRP Approaches

Traditional planning approaches, Material Requirements Planning (MRP) and Manufacturing

Resource Planning (MRP II), were used as early as the 1970s and were aimed at making the

production environment more predictable and, ideally, increasing bottom-line profits.

Material Requirements Planning

MRP was the first major breakthrough in attempting to control the supply chain. The advent of

computing technology enabled companies to be more effective at demand management. It was

easier for manufacturers using MRP to view a production facility’s bills of material, inventory

data, product lead times, and master production schedule.

MRP consists of three major components used to organize information:

• The current finished goods demand, represented by the Master Production Schedule (MPS).

• The required items and their order of assembly, represented by the bill of material (BOM).

• Inventory item files that track current allocations and storage location.

The information from these three sources enabled manufacturers to become more productive byreducing investments in inventory, facilities, and management efforts.

Manufacturing Resource Planning

MRP II provides effective planning of all resources in a manufacturing company. MRP II

measures operational planning in units and dollars. It also provides a simulation capability to

answer “what-if” questions.

MRP II is made up of a variety of functions that are linked together. MRP II consists of four

major components:

• Capacity Requirements Planning (CRP)

• Master Production Schedule (MPS)

• Distribution Requirements Planning (DRP)

• Demand Requirements Planning

The information generated by MRP II is used throughout the company: Production uses it to

schedule production; Finance receives total cost information; Order Administration receives

current production data and inventory information as input for Available To Promise (ATP); and

Human Resources accesses the information on employee costs and utilization. The evolution of

MRP to MRP II resulted in even better supply chain management, with companies becomingmore responsive to ever-changing demands.



However, it was a bit cumbersome and at times difficult to manage. The information that needs

to flow through the MRP II system is extensive. Additionally, each step doesn’t consider the

constraints in the next step of the planning cycle.

MRP II process flow doesn’t consider the cumulative impact of constraints on each consecutivestep of the planning cycle

The cyclical process of developing a master production schedule (MPS), rough-cut capacity plan

(RCCP), materials resource planning (MRP), resource requirements planning (RRP), and detailed

capacity requirements planning (CRP) may take days to perform. Furthermore, detailed problems

uncovered in the MRP and CRP process might necessitate changes to the MPS.

Enterprise Resource Planning Using PeopleSoft Production Planning

With our vision of reinventing the planning process for the enterprise, PeopleSoft continues to

align best practices with leading-edge technology. We’ve streamlined the old planning paradigm

into a single model that considers capacity and material simultaneously and eliminates the needfor distinctly different planning processes like MPS, RCCP, MRP, and CRP.

PeopleSoft’s Enterprise Resource Planning (ERP) solution leads a trend in globally enabled

enterprise Web-based manufacturing systems. It is one of the first manufacturing application

suites to embed advanced planning and scheduling capabilities (APS) for solving the supply chainand providing planning feasibility at the plant and enterprise levels.

Focusing on the principle that advanced planning and scheduling are essential to a complete and

competitive package, PeopleSoft’s strategy enables manufacturers to seamlessly blend planning

and execution activities.



PeopleSoft Production Planning considers both supply and demand as it considers resource andmaterial constraints when generating and solving a production plan for your enterprise

PeopleSoft Production Planning provides interactive decision support tools for planners. The

system also provides integrated solutions for procurement, production, and distribution resources.

Moving ahead of traditional MRP and ERP solutions, PeopleSoft Production Planning is built

around the concepts of in-memory constraint-based solvers. The decision to embed advanced

planning and scheduling technology, instead of building traditional MPS and MRP planning

systems, has produced an application with the management and production flexibility required to

respond proactively to changes on the production floor, from the customer, and from the market.

What PeopleSoft Production Planning Offers You

To maintain a competitive advantage in today’s global marketplace, you need a single software

solution to manage and synchronize your entire supply chain. PeopleSoft Production Planning

consists of tightly knit and rich functionality that simplifies, automates, and augments your

business processes and data flow to provide a comprehensive, global supply chain planningsolution.

PeopleSoft Production Planning offers maximum flexibility to handle all phases of your planning

needs. You can make planning decisions that take into account multiple constraints you’ve

defined. You can also quickly create multiple “what-if” scenarios that enable you to assess andprepare for critical alternate situations.



Managing Business Processes and Data Flow

Using PeopleSoft Production Planning adds simplicity to the planning process. The flow of

planning data helps you manage the planning process by dividing it into a series of sequential

processes that include different types of plans to meet your enterprise needs. With a focus on

practical business processes and the flow of data, the application assists you in developing

planning models, generating production plans, and intervening to make adjustments to the plans.

PeopleSoft Production Planning uses the following types of production plans to assist you insupply chain planning:

Master Plan Focuses on the manufacture of the items. It looks at the

top-level demand to produce a schedule of planned orders

and order quantities for items at each manufacturing site.

The plan tells you if you can meet the forecasted demand

and provides you a production schedule.

Material Plan Focuses on the availability of raw materials,

subassemblies, and substitutes to meet top-level demand at

each manufacturing site.

Capacity Plan Provides a way for you to ensure the capacity of critical

resources to meet demand. With the plan, you can bucket

aggregate capacity by days, weeks, or months, and use

alternate resource capacity rather than moving tasks

forward or backward in time to meet capacity. Material

requirements are maintained during the processing of the

plan.

Regardless of the type of plan you use to meet business requirements, you’ll use an incremental

business process that logically takes you from one stage to another until you have a completed,

ready-to-use, and feasible plan.

Several steps are required to create these plans.

To develop simulated, master, material, or capacity plans, use the following steps:

1. Establish production-planning data for other PeopleSoft applications. This data ranges from

business units, items, and general options to inventory policies and aggregate resource

attributes and sales and purchase data. You also set up data specifically for PeopleSoft

Production Planning, such as sourcing preferences and demand priorities.

2. Set up the production-planning model using the Production DataLink. The DataLink

provides you a wide variety of options and the flexibility to develop a plan that explicitly

meets your enterprise’s production-planning goals. Using the Production DataLink, you can

indicate which types of supply and demand parameters should be included in the data model.

In addition to setting up the model, you incorporate solver settings at this stage of the process.

Solver settings enable you to automatically generate an initial plan upon loading of the model

into memory.



3. Generate a production plan using the planning model. If you want to override how solvers

process the plan, you can make manual adjustments during this stage. After an initial

production plan is created, use this stage to run iterations to the plan to improve its quality.

You can also generate simulated plans. You use these plans to perform “what-if”

simulations. You can’t send a simulation plan back to the PeopleSoft database for execution,

only for reporting.

At this point of the business planning process, you must ensure that a Planning server is

running and that you are linked to it. The server needs to be running for the remainder of the

business process stages. A facility is provided at each stage of the process to link to the

server.

4. Review the production plan using tools available in the PeopleSoft Production Planning

interface. These include workbenches; Planning Scorecards; plan summaries, details, and

exceptions; and detailed reports. Each tool provides different approaches to plan information

and enables you to view the plan from a different perspective. You can review additional

details and use graphical interfaces (such as spreadsheets and Gantt charts) using the

advanced planning client.

5. Maintain the production plan using workbenches and summaries. Manual intervention

enables you to make the planning decisions that system data can’t handle. Using the

Planning server, you can also use spreadsheets and Gantt charts to maintain the plan. After

you are satisfied with the changes, you can run one or more iterations of the plan to fine-tune

its quality.

6. Commit the production plan using planning messages that are sent from the Planning server

and that reside in your PeopleSoft Production Planning interface to finalize elements of your

master or material Plan.

The preceding process stages apply to any Master, Material, or Capacity Plan you might be

developing.

Using Seamless Integration to Create Production Plans

PeopleSoft Production Planning is part of an integrated suite of intelligent-agent applications that

help you develop Master, Material, and Capacity Plans for your entire supply chain. The

applications run in conjunction with a powerful Planning engine that efficiently handles relatively

large amounts of data.

In this integrated system, PeopleSoft Production Planning imports data from PeopleSoft Order

Management, Inventory, Purchasing, Demand Planning, and Manufacturing and sends critical

data to PeopleSoft Inventory, Purchasing, and Production Management. The results from

PeopleSoft Production Planning are also included in the data model used by PeopleSoftEnterprise Planning.



The Production DataLink enables you to pull data from other PeopleSoft applications and place it

in the PeopleSoft Production Planning system. You have the flexibility to run the Production

DataLink as often as you need.

Using the PeopleSoft Production Planning interface, you can run this engine using a Planning

server without leaving the interface. In addition, you use seamless integration to determine how

you want the production-planning model processed by solvers. Solvers make up a set of planning

tools that generate Master or Material Plans ranging from simple material plans or material- and

capacity-feasible plans to more advanced plans that make manufacturing decisions through aseries of iterations and plan violation repairs.

Planning solvers are designed for you either to automate the planning process or to assist you in a

seamless interactive mode to develop a feasible Master or Material Plan. This capability helps

you make planning decisions from a business-unit level down to the manufacturing floor with

minimal navigation, easy data entry, and an intuitive interface structure. The following diagram

displays how you control planning solvers using your workstation.

Web-based user interface versus Windows-based interface

Two user interfaces are available for interacting with the PeopleSoft Production Planning model.

One is Web-based and enables access to planning information through standard Internet

browsers. Data in the Web browser is presented in traditional spreadsheet formats but is powered

by the advanced planning solvers available in the Planning server.

The other user interface is Windows-based and enables a graphical display and maintenance

capability of the planning model. This includes spreadsheet formats available in the Web-based

interface along with interactive Gantt charts and histograms.

You can also run iterations of the plan to improve its quality from the workstation before

committing the plan.



Moving and Balancing the Supply Chain

A supply chain for an item includes the top-level demand, such as a forecast or sales orders, for

the item. In addition, the chain is made up of the supplies to meet the demand, which might

include production or purchase orders. To facilitate keeping demand and supply balanced for

production plans, PeopleSoft Production Planning uses pegged chains.

Pegged chains tie top-level demand together with the tasks that produce supplies for the demand.

In doing so, solvers in the Planning engine can explicitly move, track, and record which supplies

they are using to satisfy that demands. This means that you can track the production or sourcing

of demand for a specific sales order or forecast. Using Planning servers, you can also view this

link graphically.

Using workbenches in PeopleSoft Production Planning, you can review the pegged demand and

supply. The visibility and ease of maintenance help you make decisions about what production

tasks you can move to better expedite special orders, make the best use of resources, or improve

the efficiency and quality of your production plan.

Using PeopleSoft Production Planning to Manage Your Shop Floor

In a manufacturing environment, you are constantly juggling so many objectives that managing

them can seem to be an impossible task. As a planner, you’re asked to:

• Keep inventory at a minimum.

• Maintain quality.

• Maintain an even load on available resources.

• Produce to the plan.

• Meet shipment due dates.

• Keep costs down.

Using PeopleSoft Production Planning, you can maintain a full model of material and capacity.

You model how to replenish every time you have a shortage. Using production options to build

items, transfer options to transfer material where it is needed, and purchase options to indicate

when and where to purchase items, the system can build and solve a production plan that gets thematerial and resources where you need them when you need them.

The planning system makes possible the combination of multiple resources into single planning

runs, such as material and capacity or material and costs. A wide selection of resources can be

combined. You can create predictive data models, which can be optimized with one another.

Synchronized with supply chain execution processes (such as rescheduling, production order

creation, purchasing, transfers, or capacity leveling), advanced planning creates a system capable

of supporting faster manufacturing cycles.



Master Scheduling

Detailed Material Planning

(MRP)

Rough Cut Capacity

Planning

Detailed Capacity Planning

(CRP)

Executable Plan

Planning

InteractivelyTraditional Planning Process

Traditional Process PeopleSoft Production Planning

-Interactive process

-All dependencies are considered

-Realtime capability

-Adaptable to changing business needs

-Graphical workbench

-Unlimited simulations

-Bucketed logic

-Time consuming sequential process

-I/O intensive

-Provides data instead of information

-Does not view constraints at next level

Executable Plan

MPS

RCCP

MRP

CRP

ScenariosScenarios

ScenariosScenarios

Scenarios

Comparing the traditional MRP planning process to the advanced planning and scheduling processembedded in PeopleSoft Production Planning.

By solving factory-specific planning and detailed schedules in your production facilities,

PeopleSoft Production Planning focuses on such situations as the following:

• What customer demand should be fulfilled above others when supply isn’t enough to meet all

demands?

• If material arrives late, what’s the impact going to be on the entire schedule? How can the

impact be minimized?

• A line goes down. Where can production be rescheduled? Can promise dates still be met?

• It’s quarter end. How do you ship the most revenue for this week?

• Sales orders are exceeding projected forecasts. Are the material and capacity available to meet

this additional demand while still observing material lead times?

The key to feasible and optimized planning is the ability to simultaneously balance multiple

business constraints. Constraints are schedule limits that, when violated, must be repaired to

produce a valid schedule. But constraints, by their nature, are often in conflict with one another:

minimizing capacity issues may cause promise-date constraint violations; minimizing promise-

date violations may cause problems with material availability constraints. With each constraint


1 - 1 0 O V E R V I E W O F P E O P L E S O F T P R O D U C T I O N P L A N N I N G P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

battling the others, the planner’s role is producing a schedule that best meets the business

objectives of the day.

PeopleSoft Production Planning: redefining the planning paradigm

With PeopleSoft Production Planning, you can recognize shorter planning process cycle times,

shorter “what-if” scenario cycle times, forward modeling of key inventories, and a single source

of planning data. PeopleSoft Production Planning helps speed the planning process, reduces

inventory carrying costs, and gets you closer to realizing the utmost capacity on your factories’

floors.

Understanding Plans

PeopleSoft Production Planning represents plans in memory to enable fast computation. There’s

no indication of running a consolidation job to compute projected on-hand balances, netted

requirements, or any of the other background processes such as in MRP systems. PeopleSoft

Production Planning always computes the ramifications of scheduling an event.

A plan is a set of tasks that consumes inventory, supplies inventory, or uses capacity resources.

Tasks model production, purchasing, transferring, and shipping. Each task has a start time and an

end time:

• For production tasks, these are the start and end of the production IDs and schedules.

• For purchase orders, these are the order date and the delivery date.

• For interunit transfers, these are the ship date and arrival date.

• For shipments, these are the ship date and the delivery date for forecast demand and for

customer orders and quotes.

PeopleSoft Production Planning dynamically keeps track of the availability of inventory and

capacity as these start and end times change within the data model. It does so by transforming

BOMs and bills of resources (BORs) into constraints when you create new tasks or orders. The

application maintains the effect of constraints on the schedule as you create, delete, or changetasks or orders. It then designates constraint violations on the Planning Scorecard.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L O V E R V I E W O F P E O P L E S O F T P R O D U C T I O N P L A N N I N G 1 - 1 1

The receipt of material based on a scheduled purchase order delivery is a real-world event that

PeopleSoft Production Planning represents as a PO delivery task. This task has an effect on the

projected on-hand balance of material for the delivered item. The system immediately calculates

the change in the projected on-hand quantity of the delivered material when the PO delivery is

added to the schedule. No consolidation or netting process is required. When you add a

production task to the schedule, the system computes its effects on available balances of material

and capacity availability.

A transfer order or interunit transfer represents both a shipment and receipt of inventory between

two business units. Production planning recognizes the impact on inventory for both the shipping

and receiving sides of a transfer order.

A sales order represents the shipment of material to a customer from a location under PeopleSoft

Production Planning’s control. The system represents this as a shipment of material and changesthe projected on-hand balance in the future.

Working With Constraints

PeopleSoft Production Planning stores planning and scheduling knowledge in objects called

constraints. Constraints test for exceptions and have intelligent heuristics for repairing

exceptions. When PeopleSoft Production Planning explodes production and assigns times to

operations on the schedule, it attaches constraints to the operations. It then refers back to the

tasks causing the exceptions. You view the violated constraints of the system by viewing a

Scorecard.

When PeopleSoft Production Planning automatically resolves exceptions, it needs to know what

trade-offs it can make in over-constrained scenarios. There are many options available when

running the PeopleSoft Production Planning solvers to resolve violated constraints associated

with material and capacity.

For more information about solvers available in PeopleSoft Production Planning, see

“Setting Up the Production DataLink”.

Understanding the Interactive Approach to Supply Chain Management

PeopleSoft Production Planning vastly improves the way you interact with your company’s

information systems. Formerly, you would enter order and inventory transactions into your MRP

or ERP system on a daily basis, and the system would keep track of inventory balances and order

status. Either weekly or monthly, you would create a material requirements plan with abackground transaction that could take many hours to run: overnight or even over a weekend.

When you came back into the office, you would have to manually search through a massive

printout to find exceptions. You would have to devise reactions to the exceptions and execute

them manually without any opportunity to simulate the ramifications of your decisions on thesupply chain.



Now, PeopleSoft Production Planning helps you quickly identify your operational exceptions and

provides assistance in delivering optimal responses to those exceptions. You can immediately

ask for your exceptions, such as capacity overloads, late orders, or inventory shortages.

A Planning Scorecard provides you with this information. You drill down, using the constraint

tabs, to find specific order, item, or capacity problems. PeopleSoft Production Planning is event-

driven. You no longer need to spend enormous amounts of time analyzing situations to identify

problems, they are simply presented to you to drill down and reconcile.

Fixing problems is easy with PeopleSoft Production Planning. You can change plans and

schedules in a number of ways:

• You can move production orders around on Gantt charts.

• You can review production quantities in spreadsheets.

• You can use Material and Capacity workbenches.

• You also use PeopleSoft Production Planning to change due dates or delete planned

production, purchase, or transfer orders. You can automatically resolve exceptions.

As you resolve problems and make a production plan feasible, you use solvers that make it

possible for you to alternate between automated and manual control of plans as shown in the

following diagram:



You can mix manual and automatic optimization to control PeopleSoft Production Planning

For more information about using Solvers, see Resolving Plan Constraints in PeopleSoft

Production Planning.

Using an Integrated Model of Material and Capacity

PeopleSoft Production Planning operates as your intelligent assistant by maintaining a full model

of material and capacity. You draw on this model to determine how to replenish items when you

have shortages. PeopleSoft Production Planning knows about building items through production

options, transferring items through transfer options, and purchasing items through purchase

options. Tasks in the system consume inventory, use resources, and supply inventory.



Although you maintain production options in the system of record (PeopleSoft Supply Chain

Management), you can use the production option pages for viewing data structures such as

production options, bill of material (BOM) entries, bill of resources (BOR) entries, and supply

entries. You can also use this form to change the data structures to perform “what-if”simulations.

Consuming Inventory

Each operation in a production option can consume inventory. You enter the option data, in this

case the bill of material (BOM) and routing, in PeopleSoft Bills and Routings. PeopleSoft

Production Planning ties the BOM and routing entries to the operations of a build option. Each

build option operation consumes items. PeopleSoft Production Planning ensures that the

appropriate material is consumed depending on when you schedule the operation. Component

effectivity dates enable you to model engineering change orders (ECOs).

PeopleSoft Production Planning includes a buildable inventory (BI) constraint and a raw material

(RM) constraint. Use the BI constraint for finished goods items and their buildable

subassemblies. Use the RM constraint to model purchased items.

Using Resources

The bill of resource (BOR) transactions associate resource requests with routing operations. Each

entry asks for a class of resource and a quantity. PeopleSoft Production Planning automatically

ensures that the instance of the resource assigned to an operation is a member of the BOR’s

assigned resource class.

Supplying Inventory

Each operation in a routing can supply inventory. Supplies are represented as production outputs

within planning.

For more information about outputs, see PeopleSoft 8.00.01 Production ManagementPeopleBook, “Maintaining Production Orders and Production Schedules”.

Linking PeopleSoft Production Planning to Your Enterprise

PeopleSoft Production Planning uses data extracted from PeopleSoft Supply Chain Management.

You maintain all data within the associated applications, including static data (such as item

attributes and bills of material) and dynamic data (such as sales, purchase, and production orders).

As activity occurs, the planning system receives relevant data using the Production DataLink.

PeopleSoft Production Planning uses static data from PeopleSoft Bills and Routings and

Production Management and dynamic data from PeopleSoft Purchasing, Inventory, Order

Management, and Production Management.



PeopleSoft Production Planning works with other PeopleSoft Supply Chain Managementapplications to provide a comprehensive, constraint-based production plan

PeopleSoft Production Planning gathers data from other PeopleSoft applications through the

Production DataLink and converts the data to an object-oriented form in memory. PeopleSoft

Production Planning performs batch extracts or incrementally grabs the net changes from your

databases. After processing your data, the system presents you with plans and schedules. It can

also tell you what’s wrong with the plans and schedules. These exceptions are graphically

depicted on a Planning Scorecard panel.

Working with PeopleSoft Production Planning, you can resolve these exceptions. You make

changes to a plan or schedule with an easy-to-use graphical interface, or you can have PeopleSoft

Production Planning automatically resolve exceptions with its solvers.

Using the System of Record

The PeopleSoft Production Planning server is an in-memory application. Creating the production

plan in memory enables you to plan multiple scenarios very quickly. However, the in-memory

system provides no permanent storage of data. This happens in the PeopleSoft database

applications that interact with PeopleSoft Production Planning. All items, for example, are added

through PeopleSoft Inventory and then sent to the planning in-memory server. The PeopleSoftdatabase applications are the system of record.

The user interface for PeopleSoft Production Planning can receive direct user input in memory

without going through the system of record. New items, for example, can be added through the

user interface in PeopleSoft Production Planning, but for simulation purposes only. However,

new planned orders and changes to order quantities and dates are passed from the Planning server

back to the system of record.

The only records that can be added to the user interface and passed back to the system of record

are for planned supply orders. If you enter a new planned purchase order online in a planningsession, it will be passed back to the Purchasing application as a new planned supply order.



Changes to existing supply orders can also be made online in PeopleSoft Production Planning

with respect to start and end dates. These changes are passed back in the Receive Planning

Messages process. Any other changes will not propagate back to the system of record.

Understanding the Production DataLink

PeopleSoft Production Planning uses data extracted from your Supply Chain Management

databases. You maintain all data within these associated applications, be it static data (such as

item attributes and bills of material) or dynamic data (such as sales, purchase, and production

orders). When you want to generate and analyze a plan, you’ll move the data to the Planning

server and a planning in-memory engine using the Production DataLink.

To create appropriate input for PeopleSoft Production Planning, the system combines DataLink

programming elements into scripts. Use these scripts to:

• Extract information from PeopleSoft Purchasing, Inventory, Order Management, Product

Configurator, Production Management, and Bills and Routings. You use Process Scheduler to

run the DataLink.

• Transform the data into transactional commands that PeopleSoft Production Planning

understands.

• Load a command file into memory on the Planning server.

The following diagram illustrates the process used by the Production DataLink to produce a plan

you can analyze, maintain, and commit.

SQR

PLS2000

Exported

.Command

File

Planning ServerClient Station

Running the

Planning

Process

Exported

Schedule

In Memory

Optimization

Updating the

System of

Record

Review/

Approve

Planning

MessagesProcess

Planning

Messages

Review/

Approve

Purchase

Messages

PO Staging

Load

Review

Transfer

Messages

PeopleSoft

Manufacturing

Database

SQR

PLS1000

Apply

Transfers

PeopleSoft Production Planning cycles

PeopleSoft Production Planning cycles separately from the PeopleSoft system of record: accepted

plans and schedules are sent back to the system of record through a streamlined export process.

The application maintains the data input as well as the optimization results in memory. When the

planning session completes, you invoke utilities to extract and load these results from memory

into ASCII files. A PeopleSoft SQR verifies the data against the data already in the PeopleSoft

Supply Chain Management database and loads it into planning message tables for your review in



PeopleSoft Manufacturing, Inventory, Purchasing, and Order Management. You then review,

approve, and apply planning messages in each area.

Resolving Plan Constraints in PeopleSoft Production Planning

Planning solvers are designed for you to automate the planning process or to assist you in an

interactive mode to develop an executable plan. The capability of this set of planning tools

ranges from developing a simple material and capacity planning to helping you make advanced

sourcing decisions. Solvers help you make planning decisions from an enterprise level down tothe manufacturing floor.

You use solvers to create viable medium-term material and capacity requirement plans that are

easy to understand and use. For medium-term planning, you can use solvers available in the

Production DataLink to determine what is required to meet all demands and make your plansmaterial- and capacity-feasible.

Material feasibility means that the longest cumulative lead-time exists within a doable time frame

where there are no material shortages. Capacity feasibility means that there are no critical

capacity violations for aggregate resources that are marked for repair in the planning time period.The following solvers are available:

Material Planning Solver This solver provides a simple plan that resolves material

shortages. It also provides a variety of options, such as

capacity smoothing, generating fixed-period requirements,

and consolidating purchase orders. The Material Planning

Solver provides a good starting point for generating a

feasible plan. You can create a material plan for any

combination of master- or material-planning items in

PeopleSoft Production Planning. You can start the

Material Planning Solver when you generate a plan or run

the Production DataLink.

For more information about running this solver, see “Setting Up the Production DataLink”.

Feasible Planning Solver This solver tries to resolve all material and capacity

exceptions and to meet all due dates, using demand

priority and minimizing lateness as much as possible. The

solver also minimizes excess inventory and tries to

maintain just-in-time scheduling and preserve existing

supply-demand relationships. You can start the Feasible

Planning Solver when you generate a plan or run the

Production DataLink.




LP Solver (Linear

Programming Solver)

This solver is a more complex planning tool that models

the supply chain and computes schedules that optimize a

selected objective while satisfying a set of specified

constraints on operations. It is especially designed to

work with reasonably large data sets. The modeling

process extracts basic supply chain information from the

Planning engine data structures and generates an

aggregated supply chain model in linear programming

form. The solver doesn’t ensure a material- or capacity-

feasible plan. You can use LP Solver solutions that feed

into the Feasible Planning Solver to obtain a viable plan.

You can start the LP Solver when you generate a plan or

run the Production DataLink.


Iterative Repair Iterative Repair is an advanced planning tool available for

creating a plan or detailed schedule. It is also called the

Optimizer, and you can run it by itself or as part of the

overall planning process. While we do not recommend it,

you can run the Optimizer as the initial phase of the

Feasible Planning Solver. Iterative Repair starts an

analysis of a plan and seeks to repair each problem it

finds, at the same time attempting to minimize the impact

of its improvements on other aspects of the schedule. You

use the Production DataLink to start the solver and define

its settings.


Collaborating With PeopleSoft Production Planning

In many organizations today, teams at plant locations around the world conduct production

meetings on a weekly or daily basis: planners, product management specialists, and procurement

specialists wrestle with competing constraints to balance supply and demand. Supply chain

planning requires multisite coordination, and PeopleSoft Production Planning provides around-



the-world collaboration capabilities to help satisfy demand with the inventory and capacity of the

whole enterprise.

Planners can easily conduct an online planning session from their own business unit, each able to

see what changes others are suggesting. The result is a completely new approach to enterprise-

wide planning that dramatically reduces planning cycle time and ensures that all critical personnel

can participate in the process.

Applying a collaborative architecture, planners from around the world can create global supplychain plans to resolve supply chain conflicts

You can access a remote Planning server using a standard modem. The planning client can also

fully interact with the server over ordinary phone lines. This enables remote desktop and portable

systems to participate fully in the planning process from home or on the road. You can provide

this access to key suppliers, field sales staff, or potential customers who need the latest

information on product availability.

Establishing Supply and Demand

PeopleSoft Production Planning creates the demand plan for a single plant, including production

schedules, material requirements plan (MRP), and capacity requirements plan (CRP). The

application calculates a time-phased production schedule that is passed on to Production

Management for execution. It also creates purchase order recommendations for Purchasing to

ensure sufficient supply.

The production plan is calculated using demand in the form of forecasts, customer orders and

quotes, production component demand, and transfer demand less supply in the form of quantity-

on-hand balances in inventory, outstanding purchase orders in PeopleSoft Purchasing, and work

in process in PeopleSoft Production Management. It then applies constraints (such as capacity

constraints, inventory target levels from inventory, automatic replenishment, and due dates for the

production) to generate a feasible plan.



Capacitycrews

machines

tools

Production

orders

Planning

parameters

Bills of material

Routings

Sales

orders

Material

stock

requests

Quantity on hand

Quantity on order

Purchase

orders

Transfer

Orders

Transfer

ordersComponent

list

Demand

Supply

PeopleSoft

Production Planning

Sales

Quotations

Forecasts--

item and

product

Planning model

PeopleSoft Production Planning brings incoming demand together with your manufacturingplanning parameters and current quantities to generate required supply

Analyzing Your Supply Chain Model

A number of inquiries are available for you to view and analyze data before either committing the

plan or running another iteration of the plan. PeopleSoft Production Planning provides the

following inquiries:

Plan Summary The Master or Material Plan Summary provides you with

an aggregate (bucketed) view of the supply and demand

for a business unit item. You can use the summary as part

of the workbench where you can make changes to the plan

or as a stand alone display-only detailed review.

Details The Master or Material Plan Detail Inquiry displays the

sequence of supply and demand over time for an item.

You use the inquiry when you review the sequencing of

demand and supply for an item.



Exceptions Use the Master or Material Plan Exceptions Inquiry to

review exceptions for individual items in a plan. An

exception is a condition that prevents the master or

material plan from being feasible. The Exceptions Inquiry

and Planning Scorecard display the same data. The main

difference is that the Exception Inquiry enables you to

review all exceptions for an item in the same grid, while

the Planning Scorecard provides some summary features

by exception type. The inquiry also displays additional

problems that may not be in the Planning Scorecard, such

as planned demand before current time.

Planning Scorecard Use the Planning Scorecard to review the efficiency of

your overall production plan. It displays constraint

violations, the number of violations, and a score for the

violations. In PeopleSoft Production Planning, a score is

the weighted sum of constraint violations in a schedule.

The score gives you an idea of how valid, or acceptable,

the schedule is.

You can also quickly analyze and troubleshoot your production plans for your supply chain

through Planning servers using the Supply Chain Viewer. This graphical tool builds a block

diagram of your supply chain model, from where you can see detailed information about

problems by drilling down on a business unit node.

The Supply Chain Viewer maps your business units and all possible connections between them.

You can perform a query using the Planning Scorecard and view a business unit’s inventory

movement or resource usage by clicking that business unit to bring up standard pages, such as

spreadsheets and graphical charts.

You can also view transfer and purchase options, as well as vendor and business unit information

and pegged supplies and demand. When you use the Supply Chain Viewer:

• A diagram is automatically generated from the business unit, supplier, and production-order

data in the server.

• You’ll work with a local copy of the diagram.

• Filters help limit the number of objects displayed. You can use separate check boxes to

prevent displaying vendor or customer sites.

• You can display the Vendor or Business Unit pages, as well as a Planning Scorecard for a

business unit, by right-clicking the vendor or business unit.

• You can display the Production Option page by double-clicking an arc in the diagram.

• The colors of the business units correspond to the scoring scenario you choose.



Creating Flexible Reports

A critical measure of an effective, enterprise-wide planning system is its ability to produce

accurate and timely reports with a minimum effort. With PeopleSoft Production Planning, you

can take advantage of innovative relational reporting of all your PeopleSoft Production Planning

data. You can create your own reports quickly and easily, dramatically enhancing productivity.

PeopleSoft Production Planning offers you a wide range of query and reporting possibilities. You

can use any of our standard reports as delivered, or alter them to suit your specific needs. Also,

our relational data structure enables you to create your own reports easily and quickly.

PeopleSoft Production Planning is event-driven. You no longer need to spend enormous amounts

of time analyzing situations to identify problems: they are simply presented to you to drill down

and reconcile.

With PeopleSoft Production Planning, you can:

• Generate planned purchase order and reschedule message reports.

• Determine current and future inventory levels graphically and highlight problem areas with

histograms.

• Use the Planning server to access Gantt charts to visualize what tasks are necessary to

complete a schedule, determine the length and quantity of the tasks, and reschedule the task

using drag and drop.

• Report horizontal planning data by selecting and naming only row types that you want to see.

Row types can include supply, demand, on-hand quantities, and available to promise. You candynamically select the data to be reported.

Maintaining Plan Data Using Workbenches, Graphical Charts, andHistograms

You can work with planning data using a number of tools, beginning with Master and Material

Plan Workbenches. You can use the pages to make changes to the plans. You can change

production, purchase, and transfer order dates and quantities for the plans. You use the respective

workbenches to access single items to work with. The workbenches display exceptions, planned

actions, and planned transfers for the replenishment of distribution or master items.

The Capacity Plan Workbench makes it possible for you to search all resources and identify those

that have capacity violations. You first use the workbench to view the rough-cut capacity plan

details based on certain selection criteria. After you identify overloaded resources, you can view

the loads in a bucketed format over time from the capacity summary, making manual adjustmentsto the plan to resolve capacity problems.

PeopleSoft Production Planning’s graphical tools enable you to easily drag and drop time-based

information to manipulate plans and run quick, interactive simulations. Using Planning servers,

you can efficiently reschedule tasks in plans, update planned orders, and release orders. The

planning system provides histograms you can use to visually determine inventory levels. Using



the servers, you can also maintain tasks with Gantt charts and make use of several time-based

spreadsheets.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L S E T T I N G U P P R O D U C T I O N P L A N N I N G 2 - 1

C H A P T E R 2

Setting Up Production Planning

Before you use PeopleSoft Production Planning, you must define attributes in PeopleSoft

Production Planning as well as in other applications within the PeopleSoft Supply Chain

Management application suite. This section details the key setup pages and components and

describes how they affect PeopleSoft Production Planning.

Before You Begin

Before you begin defining key data elements to support the PeopleSoft Production Planning

process, you’ll need to verify that your installation options are complete, your planning-specific

general options are defined, and your PeopleSoft system backbone attribute settings are correct.

Defining PeopleSoft Production Planning-Specific Installation, User, andGeneral Options

Before you get started actually setting up planning data, there are several planning-related pages

you need to set up and maintain in the Define General Options menu. Most of the data you set up

using these pages you should already have entered when you set up other PeopleSoft applications,

such as PeopleSoft Manufacturing, Inventory, Purchasing, and Order Management. In addition,

you should:

• Define forecast sets to create “what-if” scenarios with different versions of the material and

capacity plan based on different forecasts using the Forecast Sets page.

• Define planner codes so you can use them to filter information for most pages and processes in

PeopleSoft Production Planning using the Planner Code page.

• Create Planning server templates using the Planning Server Definition page. Planning server

templates enable you to automatically transfer the transaction data and plan parameters directly

to the Planning engine to generate, analyze, and implement your plan. These templates make it

easy for you to change the host machine or database you are linked to.

• Define installation default Planning server information based on Planning server templates

using the Installation Options - Planning page.

• Select your own user default Planning servers based on your user preference using the User

Preferences - Planning page.


2 - 2 S E T T I N G U P P R O D U C T I O N P L A N N I N G P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

For more information about setting up General Options, see PeopleSoft 8.00.01 ApplicationFundamentals for FSCM PeopleBook, “Defining Financials and Supply Chain Management

General Options”.

Defining the Concatenation Code for Configured Items

If you’re using PeopleSoft Product Configurator, you need to define a concatenation code to pass

the necessary configuration information for the item to PeopleSoft Production Planning. If the

item uses configuration codes, the item and configuration code are concatenated together (based

on the concatenation code information you define) in the Production DataLink. You define this

concatenation code using the Installation Options - Planning page in the Define General Options

menu.

All attributes for configured items come from the Item Attributes by Unit value defined for the

generic item. These definitions are passed to PeopleSoft Production Planning for each

configuration code. This means that the planning attributes established for the generic configured

item will be used for all configurations of the item.

We strongly suggest that you run the Production Configuration process before running theProduction DataLink process.

For more information about the product configuration process, see PeopleSoft 8.00.01Product Configurator PeopleBook, “Establishing Items and Products for Configuration”.

Setting Up Business Units for Your Production Planning System

With PeopleSoft Production Planning, you don’t need to set up business units specific to

PeopleSoft Production Planning. Instead, you need to make sure that you create business units tosupport supply chain information sharing.

To implement PeopleSoft Production Planning, you should at the minimum create one Inventory

business unit and define it also as a Manufacturing business unit. In addition, you might need to

create Order Management and Purchasing business units. Because of the way PeopleSoft

Production Planning works with other PeopleSoft applications, your business units should already

be set up as part of your PeopleSoft Inventory, Purchasing, Order Management, or Manufacturing

systems.

If you want to set up For more information, see

Inventory business units PeopleSoft Inventory PeopleBook

Manufacturing business units Setting up Your Manufacturing System

Purchasing business units PeopleSoft Purchasing PeopleBook

Order Management business units PeopleSoft Order Management PeopleBook



Make sure you set up your Inventory business unit first.

If you have installed PeopleSoft Enterprise Planning, you can decide where to build the master

plan when you establish your business units. To identify the master-plan items to be planned in

PeopleSoft Enterprise Planning, you use the MFG Business Units Options page in the

Manufacturing Options component of the Define Business Rules menu. If you select the Master

Items in EP check box, the DataLink will send all the master-plan items for the corresponding

business units to PeopleSoft Enterprise Planning. Otherwise, PeopleSoft Production Planning

will plan for the master-plan items.

Depending on your implementation strategy, you may or may not want the master-plan items to

be planned in PeopleSoft Enterprise Planning. You need to consider the following before you

decide to create your master plan in PeopleSoft Enterprise Planning:

• PeopleSoft Enterprise Planning will create a supply schedule for the master-plan items. You

can optionally bring back the supply schedule via the Enterprise DataLink when you receive

the planning messages. This supply schedule can include transfers, purchase orders, or

production IDs or schedules.

• By including the master-plan items, PeopleSoft Enterprise Planning will be able to calculate

loads on Rough Cut Capacity Resources and perform capacity planning at aggregate level.

• If the PeopleSoft Enterprise Planning model is too large, you may encounter sizing constraints.

In that case, you might want to plan for the master-plan items in PeopleSoft Production

Planning.

• If one business unit feeds the key components to another business unit, then we recommend

that you plan your master-plan items in PeopleSoft Enterprise Planning.

• If the manufacturing business units are independent of each other, then we recommend that you

plan your master-plan items in PeopleSoft Production Planning.

Establishing Inventory, Order Management, and Purchasing Options

To run PeopleSoft Production Planning, you need to set up several options in PeopleSoft

Inventory, Order Management, and Purchasing.

Defining Inventory Attributes

In order to use PeopleSoft Production Planning, you need to set up the following attributes in

PeopleSoft Inventory.



Defining Item Attributes by Units

For each item, you need to define the following information using the four Item Attributes by

Unit pages that support PeopleSoft Production Planning:

• General planning information for an item, such as whether the item is planned by distribution

planning, master planning, material planning, or is not planned.

• The item changeover family, which is used by the Line Schedule Editor (LSE) to group items

based on their common production resource usage.

• Planning time fences, planning message parameters, safety stock and excess stock parameters,

lead times, new order fences, and other general information on how you will generate supplyfor inventory items.

PeopleSoft Production Planning generates recommendations for new orders, reschedules, or

order cancellations and then routes these recommendations to PeopleSoft Inventory,

Purchasing, Order Management, and Production Management. In many cases, the volume of

changes number in the thousands. To help manage this activity more effectively, the system

enables you to define a time fence and filters to control the message review and approval

process.

• Item-level parameters to control forecast consumption and incremental material supply and

consumption.

• Transfer, purchasing, and manufacturing order quantities, order multiples, and increments.

For more information about defining item attributes for PeopleSoft Production Planning, see

PeopleSoft 8.00.01 Application Fundamentals for FSCM PeopleBook, “Defining Items”.

Defining Transfer Attributes

To plan transfer for items between business units, you need to define transfer attributes.

Using the Transfer Attributes page, you can define transfer attributes for individual items.

PeopleSoft Production Planning uses these attributes to help fulfill your material needs.

Transfer attributes can then be used to set up sourcing templates for an item in PeopleSoft

Production Planning. Sourcing templates for an item can include transfer, purchase, or

production options. The options are initially evaluated based on least cost; however, you can use

sourcing templates to select default options and to prioritize them when an item has more than

one sourcing option.

For more information about sourcing templates, see Generating Sourcing Templates

(PLS5000).



Defining Forecast Items

Usage Use the Forecast Items page to associate items with forecast sets. When

you run PeopleSoft Production Planning, you select a forecast set you

want to use.

Object Name FORECAST_INV

Navigation Control Inventory, Fulfill Stock Orders, Use1, Forecast Items

Prerequisites You must define Forecast Sets before you associate items to forecast

sets.

Access

Requirements

Enter a Forecast Set, Business Unit, and Item ID.

Control Inventory - Forecast Items page

The following elements are common to multiple pages and are defined in the preface of this

PeopleBook in PeopleBooks Standard Field Definitions: Unit and Std UOM (standard unit of

measure).

The Forecast Set, Unit, and Item ID are default values from the selection criteria you entered to

access this page. The default Source Code appears for the item.

Enter a Date and a forecast Quantity for each date for which you want an item forecast.

In PeopleSoft Demand Planning, the item forecast tables can be automatically populated

based on the features in that application.

For more information about PeopleSoft Demand Planning, see the PeopleSoft 8.00.01Demand Planning PeopleBook, “Understanding the Basics of PeopleSoft Demand Planning

and Inventory Planning”.



Setting Up Stocking Periods

You use the Stocking Periods page to set up time-phased safety stock and excess stock levels.

The information you enter using this page supersedes any stocking level information you enteredon the Item Attributes by Unit - Planning: Order Modifiers page.

For more information about setting up stocking periods, see the PeopleSoft 8.00.01Application Fundamentals for FSCM PeopleBook, “Defining Item Control Values”.

Setting Up Demand Priority Families

You use the Demand Priority Family page to group like items to establish a common priority for

all items within a single group. The demand priorities can then be established for PeopleSoft


For more information about setting up Demand Priority Families, see the PeopleSoft 8.00.01Application Fundamentals for FSCM PeopleBook, “Defining Item Control Values”.

Defining Order Management Options

If you are using PeopleSoft Order Management, you may want to define product forecast

information. PeopleSoft Production Planning uses forecast sets to define different versions of a

forecast. When you run PeopleSoft Production Planning, you select a forecast set that you want

to use. Products are associated with forecast sets when you enter product forecasts in PeopleSoft

Order Management. For planning purposes, you can split product forecasts across multiple

inventory business units as defined on the Forecast Percentages page.

Defining Forecast Product Information

Usage Use the Forecast Products page to maintain forecast information by

product for PeopleSoft Production Planning.

Object Name FORECAST_PROD

Navigation Manage Sales Activities, Analyze Orders, Use, Forecast Products

Access

Requirements

Enter a Forecast Set, Order Management Business Unit, and Product ID.



Manage Sales Activities - Forecast Products page

The Forecast Set, Unit, Product ID, and Item ID are default values from the selection criteria

you entered to access this page.

Enter a Date and forecast Quantity for each date for which you have product forecast

information.

Defining Purchasing Attributes

If you are using PeopleSoft Purchasing, use the Purchasing Attributes component to enter a

variety of data that Production Planning needs. In particular, you need to do the following:

• Access the Purchasing Attributes page to define the lead time and the primary buyer for the

purchased item. The Production DataLink uses the Lead and Standard Price fields from this

page. The Lead Time specified on this page overrides the lead time indicated for thepurchasing attributes.

• Access the Item Vendor page to specify or change a vendor and the lead time for the vendor.

Using this page, you can specify a specific vendor or vendors for PeopleSoft Production

Planning for a purchased item. The application then recommends this vendor to PeopleSoft

Purchasing for each planned order. If you don’t specify a vendor for a purchased item,

PeopleSoft Production Planning creates a planned order without a vendor. You can then use

the purchase order load process to assign a vendor to the item. PeopleSoft Production Planning

also ranks multiple vendors for the same item based on priority.

• Define a Ship To Location that represents an Inventory business unit (IBU). However, the

Inventory business unit and the Ship to Location don’t have to share the same name. You can’t

define a Ship To Location unless the item has purchasing attributes. If an item has purchase

attributes defined but no Ship To Locations, it will be assumed that the item can be ordered at

any IBU. If any Ship To Locations are defined for an item, then each IBU to which the user

wants to order the item must be defined with a Ship To Location.

You can set the lead time that PeopleSoft Production Planning uses for a purchased item at either

the item or vendor level. If you assign a specific vendor to an item in PeopleSoft Purchasing,

define the lead time at the vendor level.



For more information about maintaining purchasing attributes, see PeopleSoft 8.00.01Application Fundamentals for FSCM PeopleBook, “Defining Items”.

Defining Manufacturing Options

There are several parameters available in PeopleSoft Manufacturing to help you define how you

want Production Planning to use work centers and resources.

Manufacturing Data Used by Production Planning

PeopleSoft Production Planning uses the following data from PeopleSoft Manufacturing:

Data Production Planning

Work Centers A work center can consist of one or more

people and/or machines; it can represent a

logical grouping of machines, a department,

or a cost center. For a routing, you can

assign to each operation or task a work center

where the operation or task takes place. You

can also assign one or more resources (crew,

machine, or tool) to each work center.

Resources Resources are the crews, machines, and tools

assigned to work centers to complete tasks.

When analyzing capacity for planning and

scheduling, PeopleSoft Production Planning

considers the individual resources that you

assign to the work centers and schedules

them accordingly.

Routings A routing defines the sequence of steps

needed on the shop floor to create the

assembled item. Based on the routing

definition, you can determine the lead

timelead-times for manufactured items,

which, in turn, determine the start and end

dates for production.

Bills of Material PeopleSoft Production Planning uses the

planning bill of material for aggregate

forecasting or aggregate reporting purposes.

You can create and maintain (on a summary

level) all components that comprise a

planning BOM for a group of assembly items

or product families in a business unit.



For more information about setting up this data, see PeopleSoft 8.00.01 Bills and RoutingsPeopleBook, “Overview of PeopleSoft Bills and Routings”.

Defining Resource Changeover Penalties

The time required to prepare a resource for production is often dependent on the previous

production run. For example, at a printing machine, you might require more time to flush lines of

black paint prior to using white paint than to flush lines of white paint prior to using black. You

can express this changeover factor as a penalty. PeopleSoft Production Planning uses the

changeover cost constraint to sequence production in the proper order for a resource.

Prior to establishing the changeover penalties, you must group your items into unique attributegroups.

For more information about resource changeover penalties, see PeopleSoft 8.00.01 Bills andRoutings PeopleBook, “Defining Resources”.

Defining Planning Resource Attributes

You can model planning resources from work centers, machines, crews, and tools. By defining

parameters using the Work Center Maintenance or Resource Maintenance components:

• You can indicate that a work center or resource represents multiple instances of the same

resource.

• You can indicate whether operations within a work center are wrapping or non-wrapping.

Task wrapping refers to the ability of a specific operation to be stopped and started up againwhen crossing a nonscheduled work period, such as a weekend.

• You can define whether or not resources are available for tasks at other work centers during the

wrapping task’s nonscheduled work period.

The Machine Resources and Crew Size fields, which represent the number of resources you

need for each task performed in the work center, function differently than Planning

Instances. PeopleSoft Cost Management uses machine resources and crew size to perform

cost roll-ups.

For more information about planning attributes for resources, see PeopleSoft 8.00.01 Billsand Routings PeopleBook, “Defining Resources”.


2 - 1 0 S E T T I N G U P P R O D U C T I O N P L A N N I N G P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Using Production Planning Resources in Aggregate or Detail

In PeopleSoft Production Planning, you have the option to plan resources in aggregate or detail.

When you plan in aggregate, the system analyzes capacity loads for a resource in daily, weekly,

or monthly buckets. The number of tasks scheduled in this bucket can be unlimited as long as

there are available hours in the bucket.

When you plan in detail, the system scores capacity loads in a bucketless method. This means

that the planning system will note any capacity overload where the number of scheduled tasksexceeds the number of resources available.

There is a tremendous amount of flexibility when modeling capacity in PeopleSoft Production

Planning. You can decide to mix the aggregate and detailed capacity options with respect to the

different resources modeled. For example, you might model most crews and machines as

aggregate, whereas you would model certain tools that are highly utilized as detailed capacity.

Make this decision on a resource-by-resource basis. Detailed capacity creates higher quantity

schedules but will likely increase the amount of time required for optimization and maintenance

of the plan.

Use the Planning Options page to specify each resource (crews, machines, and tools) as an

aggregate resource. If you don’t define aggregate options on this page, then the resource is

considered a detailed capacity resource.

For more information about planning resources in aggregate or detail, see PeopleSoft 8.00.01Bills and Routings PeopleBook, “Defining Resources”.

Defining Production Planning Attributes

Before you can generate a plan, you may need to define aggregate items, promise and request

dates, Roll Forward phases, and overall planning and work center attributes. These attributes

provide key indicators for how the Production DataLink should process a plan’s data.

Maintaining Aggregate Items

Usage Use the Aggregate Items page to identify which items to include in the

forecasting family.

Object Name PL_AGG_DMD_ITEM

Navigation Plan Production, Maintain Planning Data, Use, Maintain Aggregate

Items

Access

Requirements

Enter a Business Unit and Parent Item ID.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L S E T T I N G U P P R O D U C T I O N P L A N N I N G 2 - 1 1

Plan Production - Aggregate Items page

The Business Unit and Parent Item ID are values for which you selected to maintain aggregate

items.

Aggregate Items

Select an Item ID. The item Description appears and is for display only.

If you want to do a search of all available items, click the transfer button and then click

the Item Search link to access the Item Search page.

Defining Product Forecast Percentages

Usage Use the Forecast Percentages page to define how much of a product

forecast quantity should be directed to a PeopleSoft Inventory business

unit. PeopleSoft Production Planning uses this percentage to allocate

the forecast (defined in the Order Management business unit) among

many inventory business units.

Object Name PL_OM_FCST_PCT

Navigation Plan Production, Maintain Planning Data, Use, Forecast

Percentages

Access

Requirements

Enter an Inventory Business Unit and Order Management Business Unit

if you are allocating percentages by business unit only. Enter the

Inventory Business Unit, Order Management Business Unit, and Product

ID if you want to allocate the forecast percentage by product and

business unit.



Plan Production - Forecast Percentages page

The IN Unit (Inventory business unit), the OM Unit (Order Management business unit), the

Product ID, and Description appear based on the business unit and product combination you

entered to access this page.

Enter the Effective Date for the forecast percentage. Indicate the Status (Active or Inactive) of

the forecast percentage for the business unit or product/business unit combination.

To allocate a specific forecast percentage to the business unit or product/business unit

combination, enter the Forecast Percentage. The percentage can be any number; even if you

define more than one effective-dated percentage, the percentages don’t have to total 100% and

can total more than 100%.

You can link an Order Management business unit to more than one Inventory business unit. For

example, you could allocate the forecast percentage as follows:

Order Mgmt BusinessUnit

Inventory Business Unit Forecast Percentage

GBR01 GBR01 50%

GBR01 GBR02 25%

GBR01 CAN01 25%

Defining Master Plan Data

Usage Use the Master Plan Data page to review the status of the Production

DataLink when you generate your master plan.

Object Name PL_MASTER_PLAN

Navigation Plan Production, Maintain Planning Data, Use, Master Plan Data

Access

Requirements

Define a Business Unit for your search.



Plan Production - Master Plan Data page

The Unit field displays the business unit for which the master plan exists. The DateTime value

is when the previous master plan was generated, regardless of whether it was an iteration or an

initial run. This value also appears in the Production DataLink page in the Previous Master Plan

group.

The Net Change value is the last time that you ran a net change to the plan. This run type

refreshes only planning data created or changed since the last time you ran a master plan using

the Production DataLink. PeopleSoft Production Planning applies net-change data to a session

already running on the Planning server. The Net Change function applies to only new items,

forecasts, transfer orders, material stock requests, production orders, production schedules,

planned production, purchase orders, and sales orders. PeopleSoft Production Planning doesn’tuse net change for other static data such as bills, routings, and calendars.

You can set the following values on the page by selecting or clearing the check boxes:

Processed This check box tells others that you have processed the

master plan. When the check box is selected, you can’t

run receive messages again. If you need to run the

Receive Planning Messages process again, you need to

clear this check box and run the Production DataLink

again. Otherwise, an error message appears to indicate

that you have already run receiving messages.

Lockout The system selects this check box when you run the

Production DataLink. This prevents other users from

converting planned orders from the previous run of the

Production DataLink. For example, if you run the

Production DataLink for Group Code A, bring the

messages back, and then run the Production DataLink

again for Group Code A, at that point you can’t convert

the messages from the original Production DataLink run.

This indicates that a more current planning iteration is

taking place. When you use the Receive Planning

Messages option, the Lockout check box is cleared.

Process Status This check box indicates that the Production DataLink is

currently running. It is intended to alert other users who

try to run the Production DataLink while you are running

it.



When you are ready to convert planned orders after you have run the Production DataLink,

you want to freeze the database so that other users can’t convert planned orders by approving

the planning messages.

Defining Promise and Request Dates

Usage Use the Promise/Request Dates page to assign penalty weights to

promise and request date violations on customer shipments. The system

uses these weights to calculate the score for the promise date and request

date constraints on the Scorecard while optimizing the production plan.

Object Name PL_PR_DATES

Navigation Plan Production, Maintain Planning Data, Use, Promise/Request

Dates

Access

Requirements

Enter a Business Unit and select one of the Penalty By options: either

Promise Date or Request Date.

Plan Production - Promise/Request Dates page

The system uses promise and request dates to monitor commitments to customers. The dates help

you track critical shipments. You use this option to emphasize the importance of meeting these

commitments.

Promise dates represent the dates and times that you promised a customer that a shipment would

arrive. The sales order shipment is scheduled to ship on the date you committed to ship. Request

dates represent the dates that a customer has requested to receive a shipment. A sales order line is

scheduled to ship based on this request date.

The Unit and Penalty By are display-only fields.

In the Offset field, enter the number of days (early or late) for the date violation.



The Offset field value can be a negative number for penalties applied to early shipments.

Then, enter a Penalty Factor using a numeric value. The value can be greater than 0 but must be

less than 1.00. The penalty factor is cumulative but never exceeds 1.00. For example, an early or

late shipment is never scored higher than 1.00, even if the cumulative penalty value is greater

than 1.00.

Using the data on the screen shot as an example, a missed shipment with an offset of 3 or greater

would by default result in a penalty factor for the offset of 0.3000. A missed shipment with an

offset between 1 and 2 would by default result in a penalty factor for the offset of 0.1000.

Defining Roll Forward Phases

You use Roll Forward phases to reschedule tasks that are past due. Past-due tasks are those that

were scheduled to be completed prior to the current time but remain open. PeopleSoft Production

Planning moves tasks from the past and rolls them forward into the current or a future schedule orplan. Then you can view and work with them before running solvers to fine-tune the plan.

After you establish active phases, use the Production DataLink to indicate whether the Planning

engine should run active Roll Forward phases after loading data into the Planning server.

Overview of the Roll Forward Feature

Often tasks in a plan aren’t completed on time. For example, a purchase order is delayed that

affects whether you can meet forecasted demand on time. Or, possibly, a production line might

be closed for several hours, leaving some existing production operations incomplete.

Using Roll Forward phases, you resolve material movement needs using time periods rather than

fixed dates. Time periods, for example, include early time fences or current times, whereas a

fixed date is a specific time such as 3:30 p.m. on October 10. Time periods can be used over and

over and are associated with fixed dates through planning models.

To determine which moveable tasks to roll forward and where to roll them, PeopleSoftProduction Planning uses the following parameters:

• The time period from which you want to roll tasks forward, beginning with the time period

defined in the planning model as the start time.

• The target time period to which you want to roll tasks. This could be the current time or some

time after the current time.

• The status and types of task being rolled forward, such as the different behavior for planned

orders versus frozen orders across transfers, production, and purchases.

PeopleSoft Production Planning never rolls tasks backward, regardless of the parameters you

define for the Roll Forward utility.



For more information about maintaining Roll Forward phases in the Planning engine, see

PeopleSoft 8.00.01 Advanced Planning Client PeopleBook, “Using the Advanced Planning

Client”.

Setting Up Roll Forward Parameters

This section describes how you establish filters that define which tasks to reschedule and when to

reschedule them. You create a Roll Forward phase that contains the parameters for rolling past-due tasks forward.

The following example shows several tasks that are past due and a production task (operation)

that must be rescheduled because materials won’t be available to complete the task in the current

planning horizon.

Planning Horizon

Start of

Time

Current

Time

Scheduling Horizon

Purchase

Task

Transfer

Task

Production

Task

Early Time

Fence

Rescheduled

Purchase Task

Rescheduled

Transfer Task

Rescheduled

Production Task

Target

Time

Late Time

Fence

End of

Time

Rescheduling a task using Roll Forward phases

You are planning for tasks that are past due in the scheduling horizon and you want to reschedule

them to the next planning cycle. The times and fences are the filter elements available for you to

use when you create a Roll Forward phase. The dates for this time line are determined by time

fences defined when running the DataLink.

You can select to move tasks that are in a Frozen status, but you can’t move tasks in a

Canceled status.

You use three fields that combine to define the parameters. The following table shows how the

production task in the preceding example was selected for rescheduling using the three fields.

Roll Forward Selection Field Field Value

Select task that End




On or before Early Time Fence

Third field No entry (default is 0)

The next table shows values for the target time.

Roll Forward Target Field Field Value

Roll task to Start

On Early Time Fence

Third field Plus (2 days)

In the example, all tasks are scheduled to start at the same time. So the Roll Forward target

field values are the same for each.

Let’s look at the past-due transfer task. It was scheduled to begin prior to the start of time.

Suppose you wanted to include all tasks that started within a day of the start of time. To selecttasks in this planning condition, use the following selection parameters:


Select task that Start

On or before Start of Time

Third field Minus (1 day)

The start of time is the earliest time the system uses to select tasks to be rescheduled. If a task

begins before the start of time and ends after the time, it can be rescheduled. In the case of the

transfer, it was scheduled one day prior to the start of time. Using the filters, you limit which

tasks the system selects to reschedule.

The selection parameters for defining the purchase task in the earlier example are in the following

table:


Select task that End

On or before Current Time

Third field No Entry (default is 0)

After you define parameters for Roll Forward phases, you can roll tasks forward based onindividual phases or on all phases.



Setting Up Roll Forward Phases

Usage Use the Roll Forward Phase page to set up PeopleSoft Production

Planning so that you can roll forward past-due tasks to current or future

production plans.

Object Name PL_ROLLFORWARD

Navigation Plan Production, Maintain Planning Data, Use, Roll Forward Phase

Access

Requirements

Enter or select the Roll Forward phase name that you want to add or

maintain.

Plan Production - Roll Forward Phase page

You use this page to add or maintain a Roll Forward phase in PeopleSoft Production Planning.

After it’s created, the phase can be run by the Roll Forward utility in the Planning engine. The

utility is used to reschedule a selected group of past-due tasks to a defined target at a later time.

Enter or update the Roll Forward Phase Name to define the code used to maintain and retrieve

data related to a set of roll forward specifications. The field is required and the name you entermust be unique. The Phase Description field is a short description of the phase.

Select the Active check box to indicate that the Planning engine should use this phase when it

calculates late tasks. Using the check box, you can create a number of Roll Forward phases in

advance, while activating only the phases that you intend to use for the next roll forward run.

If the check box is clear, the phase isn’t used by the system when you select to roll forward active

phases during the Production DataLink run.

Roll Forward Selection

Selections are the types of tasks the system considers for rescheduling during Roll Forward phase

processing. You designate which type of supply and demand task the system processes when it

rolls forward active phases by selecting the check box adjoining the task.



Roll Forward phases don’t reschedule tasks that are in a Canceled status. You can

reschedule frozen task by selecting the Include Frozen Task check box.

You use a series of fields to define date and time filters that determine which tasks the system

considers for movement. Using the Select Tasks field, you define tasks based on the time period

that they exist in the schedule. You can use either their start or end date and time. The default is

the task’s end time.

The On or Before field is made up of entries that filter tasks based on their relative position to a

time fence, rather than a hard-coded date. This enables you to keep Roll Forward phases valid for

reuse as time goes forward. You use this field in conjunction with the remaining fields to apply

time filters. The following values are available:

Start of Time The earliest time for which the system can select tasks to

be rescheduled. Tasks that end after this time or start after

this time are eligible for rescheduling.

Current Time The time considered to be the present planning time. The

system can reschedule tasks that end before the current

time or that begin after the current time. This value is the

default value for the field.

Early Fence This time represents the beginning of a planning interval

and is used with the late fence to define the range of time.

The system uses the early fence time to reschedule tasks

that start or end on or before this time.

Late Fence This time represents the ending of a planning interval and

is used with the early fence to define the range of time.

The system uses the late fence time to reschedule tasks


You use the second On or Before field with the third field. The third field enables you to specify

a time offset from the selected time fence date. This offset can be either added or subtracted from

the date. Using the second field, you determine whether you are going to add time (plus) to the

offset or subtract time (minus) from the offset.

Using the third On or Before field, PeopleSoft Production Planning stores the offset time as

Minutes, Hours, or Days. The offset default is in minutes. The next group box contains the

supply and demand tasks you can roll forward. If a box is selected, those supply or demand tasks

are included when the system rolls forward active phases.

The following tasks are available for rescheduling:

Sales Order Shipments Includes shipment parents that meet the date filters in the

Roll Forward phase.

Downtime Tasks Includes downtime tasks that meet the date filters in the

Roll Forward phase.



Planned Production Includes production operation tasks that meet the date

filters in the Roll Forward phase. PeopleSoft Production

Planning considers an operation planned if the production

parent that it belongs has a status behavior of PLANNED.The system doesn’t reschedule production parents; it

reschedules only those production operations that meet the

date filter criteria.

Existing Production Includes production operation tasks that meet the date

filters in the Roll Forward phase. PeopleSoft Production

Planning considers an operation planned if the production

parent to which it belongs has any status behavior other

than PLANNED or CANCELED.

Planned Transfers Includes transfer tasks that meet the date filters in the Roll

Forward phase. PeopleSoft Production Planning considers

a transfer task planned if it has a status of PLANNED.

Existing Transfers Includes transfer tasks that meet the date filters in the Roll

Forward phase. PeopleSoft Production Planning

considers a transfer task existing if it has any status

behavior other than PLANNED or CANCELED.

Planned Purchase Orders Includes purchase order line delivery tasks that meet the

date filters in the Roll Forward phase. PeopleSoft

Production Planning considers a purchase task planned if

it has a status behavior of PLANNED.

Existing Purchase Orders Includes purchase order tasks and possibly purchase order

line delivery tasks that meet the date filters in the Roll

Forward phase. These purchase tasks are considered

existing if they have any status behavior other than

PLANNED or CANCELED.

Select the Frozen Tasks check box to include frozen tasks for rescheduling by the Roll Forward

utility. If the check box is selected, all frozen tasks that meet the filter criteria are included in the

Roll Forward process.

Roll Forward Target

Use this group box to define the date and time to which tasks are rescheduled during the Roll

Forward phase processing. You define the Roll Forward target using a set of configurable

specifications maintained for each Roll Forward phase.

You use a series of fields (the same as the ones you used to select when past-due tasks should be

moved) to define date and time filters that determine when tasks are rescheduled. Using the Roll

Tasks to field, you define whether tasks will be rescheduled so that they either start or end on the

target date. The default is the End time, meaning that selected tasks will be rescheduled so theyare completed on the specified target date.

The On field is made up of entries that filter tasks based on their relative position to a time fence,

rather than a hard-coded date, allowing you to keep Roll Forward phases valid for reuse as time



goes forward. You use this field in conjunction with the remaining fields to apply time filters that

determine the target time. The following values are available:

Start of Time The earliest time for which the system can select tasks to

be rescheduled. Tasks that end after this time or start after

this time are eligible for rescheduling.

Current Time The time considered as the present planning time. The

system can reschedule tasks that end before the current

time or that begin after the current time. This value is the

default value for the field.

Early Fence This time represents the beginning of a planning interval

and is used with the late fence to define the range of time.

The system uses the early fence time to reschedule tasks


Late Fence This time represents the end of a planning interval and is

used with the early fence to define the range of time. The

system uses the late fence time to reschedule tasks that

start or end on or before this time.

You use the second On field with the third field. The third field enables you to specify a time

offset from the selected time fence date. This offset can be either added or subtracted from the

date. Using the second field, you determine whether you are going to add time (plus) to the offset

or subtract time (minus) from the offset to arrive at a rescheduled date.

Using the third On field, you define the offset UOM (unit of measure) as Minutes, Hours, or

Days.

Defining Planning Attributes

Usage Use the Planning Attributes page to share an associated object with a

group of objects that have the same characteristics. This page is

optional. The DataLink will create the attributes it needs to support the

model that it creates.

Object Name PL_ATTRIBUTE

Navigation Plan Production, Maintain Planning Data, Use, Planning Attributes

Plan Production - Planning Attributes page

You can use Planning Attributes to map entities such as transfer options and sourcing templates

to items. This is accomplished first by creating a global repository of attributes, then associating



the values of those attributes to entities and items. Finally, you map the entities to items using

attribute value matching. For example, you can look up the transfer options that map to a given

item based on the common attributes that contain Transfer Option as their Planning Attribute

Category.

Select a Planning Attribute Category. Your options are Material Flow and Resource

Changeover.

Enter a Planning Attribute Name associated with the attribute.

Assign a Planning Attribute Value to the attribute.

Defining Work Center Attributes

Usage Use the WC Attributes (Work Center Attributes) page to associate a

work center with a planning attribute.

Object Name PL_WC_ATTRIBUTE

Navigation Plan Production, Maintain Planning Data, Use, Work Center

Attributes

Prerequisites You need to have already defined those work centers for which you

want to create work center attributes. You also need to have Planning

Attribute Names and Planning Attribute Categories defined. You define

Planning Attributes using the Planning Attributes page.

Access

Requirements

Enter a Business Unit.

Plan Production - Work Center Attributes page

Select a Work Center from the prompt.

Select a Planning Attribute Category, Planning Attribute Name, and Planning Attribute

Value to be associated with the selected work center.

Prioritizing Demand

When demand exceeds supply and you don’t have the available inventory on hand, you need to

define a set of rules to prioritize the distribution of demand. The rules are called “demand



priority rules” because they are used to determine the order in which you fulfill independent

demand. In addition, you can use the priority rules to define the lateness tolerance rules.

In PeopleSoft Production Planning, you define the demand prioritization rules specific to abusiness unit that you model.

The Production DataLink will use the demand priority rules to generate the priority for a given

independent demand. Once the priority is established, the DataLink passes the independent

demands with different priority codes to the Planning engine. A demand priority code can range

from 1 to 999, with 1 the most important. The priority value of 0 is reserved for the system. The

Planning engine uses the demand priority code to determine which independent demand to fulfill

first, so that higher priority demands are fulfilled before lower priority demands, in situationswhere there isn’t enough available supply or capacity to meet the various demands.

Lateness tolerance represents how sensitive your customers are to their orders not being fulfilled

on time. Lateness tolerance is expressed in terms of the number of days after which the customer

becomes seriously concerned about the independent demand not being met.

Before you can define the lateness tolerance rules, you must first establish the demand priority

values for your independent demands. You can then specify the lateness tolerance rules to

associate with various ranges of demand priority value. Each lateness tolerance rule is defined by

two values: a demand priority range and a lateness tolerance value that is expressed in days. All

of the demands with priorities in a given range are assigned the lateness tolerance value. The

Production DataLink passes the lateness tolerance rules to the Planning engine, which uses these

rules to determine which demands to delay in situations where there isn’t enough available supply

to meet the various demands.

In PeopleSoft Production Planning, you define the lateness tolerance rules specific to a business

unit that you model. Here’s an example of how the two values are combined.

If the demand priority is less than or equalto

Then the number of days for the latenesstolerance is

19 1

29 2

59 4

69 5

99 7

199 14

999 20

In this example, all independent demands are assigned a lateness tolerance (in days) based on the

demand priority range. Demands of:

• 1 - 19 days are assigned 1 day of lateness tolerance.

• 20 - 29 days are assigned 2 days of lateness tolerance.






• 100 - 199 are assigned 14 days of lateness tolerance.


The Feasible Planning Solver and the Linear Programming Solver (LP Solver) use the lateness

tolerance rules and the demand priority values to determine which demands to delay in situations

where there isn’t enough available supply to meet the various demands. The following are threedifferent lateness conditions that are associated with the lateness tolerance:

Not late A demand that isn’t late is one that is met on time (on or

before the order request date, depending on which date the

planner is trying to meet).

Late but within tolerance A demand that is late but within tolerance is one that has

been scheduled after the order request date or promise

date, but before the lateness tolerance associated with that

order.

Late beyond tolerance A demand that is late beyond tolerance is one that has

been scheduled after the lateness tolerance associated with

that order.

Based on the lateness tolerance that you define, the solvers use these lateness tolerance conditionsto determine which demands to delay in situations where demand outpaces supply.

Defining Demand Priority Rules

Usage Use the Priority Rules page to assign a priority ranking based on the

demand source.

Object Name PL_PRIO_DEMAND

Navigation Plan Production, Maintain Planning Data, Use, Demand

Prioritization, Priority Rules

Prerequisites Depending on the demand source you’re using to establish the priority

rules, you must define Demand Priority Family, Customer Groups, and

the Destination Business Units.

Access

Requirements




Plan Production - Demand Prioritization: Priority Rules page

The Unit you selected to access this page appears. Priority Rank defines the priority to be

assigned to each independent demand that satisfies a given priority rule. The lower the value you

select, the higher the priority. The highest value is 999, which is the lowest possible priority, and

the lowest value is 1, which is the highest possible priority. A priority rank value of 0 is reservedfor the system. Priority Rank is a required field.

The Demand Source represents the source of independent demand to which the prioritization

rule applies. Your options are:

Forecasts Forecasts are total expected sales to all customers that you

can maintain at the product, inventory-item, or planning-

item level. At the planning-item level, sales are forecasted

by families and exploded to inventory items through

planning bills of material.

Inter-Unit Transfers Refers to outbound transfers that represent independent

demand in the planning model.

Other Stock Requests Material stock requests that come from inventory and

aren’t transfers. Could be internal or external fulfillment.

Quotations An order management quotation. Quotations are

considered demand and are sent to Planning when the

quotation success percentage is over the planning success

percentage on the Production DataLink run control.

Safety Stock The intended inventory level designed to protect against

stockouts. Deviation from this level is tolerable within a

margin defined by the safety limit and excess limit. When

stock level drops below the safety limit, new supplies are

generated to bring the stock back to the desired level.

Sales Orders Represents the shipment of material to a customer from a

location under Planning’s control. The system represents

this as a shipment of material and changes the projected

on-hand balance in the future.

You can define the Demand Priority Family in PeopleSoft Inventory. A planning priority

family represents an item or a group of items that can be used as criteria for prioritization. This is

an optional field.



Reservation Status is available if you select Sales Orders, Inter-Unit Transfers, or Material

Stock Requests as the demand source. Your options are Reserved and Unreserved. Reserved

orders are those that have been reserved against available/projected quantity on-hand at the

business unit/item level. This is an optional field.

Customer Group, or Customer Allocation Group, is a group corresponding to one or more ship-

to customers. You can select a Customer Group only when you select Sales Orders or

Quotations as the demand source. This is an optional field.

Priority is a valid parameter only when you select Sales Orders as the demand source. For sales

orders, the order priority is a calculated field that is generated during the reservation process. An

order priority value can range between 1 and 999, which is the default. For a given priority rule,

all sales orders with an order priority less than or equal to the value in the Priority field are

considered to match this parameter. For example, if a value of 100 is entered, all sales orders

with an order priority of 100 or less will be evaluated as matching this parameter. This is an

optional field.

Dest Unit (destination unit) is used only when you select Inter-Unit Transfers as the demand

source. You can use this value to prioritize demand for interunit transfer to a particulardestination business unit. This is an optional field.

Although Demand Source, Demand Priority Family, Reservation Status, Customer

Group, Order Priority, and Dest Unit are all optional fields, you must enter at least one of

them, along with the Priority Rank, to create a priority rule.

Defining Lateness Tolerances

Usage Use the Lateness Tolerance Rules page to define the lateness tolerance

rules based on the demand priority.

Object Name PL_PRIO_LATE_TOL

Navigation Plan Production, Maintain Planning Data, Use, Demand

Prioritization, Lateness Tolerance Rules

Access

Requirements


Plan Production - Demand Prioritization: Lateness Tolerance Rules page



The Unit is the business unit that you entered to access this page. Priority is the priority rank

from the priority rule definition. Lateness Tolerance (days) indicates the number of days after

which the customer becomes seriously concerned about the independent demand not being met.

Sourcing Demand

Sourcing demand is the process the Planning system uses to determine how the supply for an

item’s demand is going to be filled. The system sources demand using sourcing options. These

options define parameters for manufacturing, purchasing, or transferring an item to meet demand.

You define these options when you set up an item.

Overview of Sourcing Templates

You use sourcing templates to define how PeopleSoft Production Planning should generate

supply for an item. A sourcing template contains a sequenced list of sourcing options (purchase,

transfer, or production) based on the attributes defined throughout PeopleSoft Purchasing,

Inventory, and Bills and Routings for the item. You can let the system load the options

automatically, or you can set up sourcing templates manually and maintain the options. Thesetemplates are needed when multiple sourcing options exist for an item.

When you assign multiple sourcing options to a single item, you create a more flexible planning

situation by providing the Planning engine with more information to source demand. Material

availability, resource capacity, and lead time can create exceptions that influence the engine’s

sourcing selection. When you provide several options, the Planning engine has more

opportunities to find an option that resolves an exception. For example, if a purchase option

doesn’t have adequate lead time, the engine can go to the next prioritized option to see if thatoption can be used to meet the demand.

There are other advantages of creating sourcing templates. You can review sourcing options

before the Production DataLink run. Also, the DataLink doesn't have to create sourcing

templates for every run, thereby reducing processing time. When you indicate to the system that

you want to maintain sourcing templates manually, it prevents the Create Sourcing Templates

batch job from overwriting any sourcing templates when the Manually Maintained check box isselected.

The system uses the following sourcing options to source demand for an item:

Production Option This is a combination of a bill of material and routing

code that can be effective-dated for seasonal mix

variations. The option defines which material and

resources are required to make a specific item.

Transfer Option This option defines the transfer attributes, such as cost or

transfer time, that are associated with transferring an item

from one business unit to another. You create the option

by defining transfer attributes for an item.



Purchase Option This option defines item and vendor attributes, such as

cost, lead time, and order modifiers. You create the

option by defining item and vendor relationships on the

Item Purchasing Attributes page.

When you create a sourcing template, you sequence the options and define a default option for

use if the Planning engine can’t find an adequate option using prioritization. The Planning engine

uses fixed-priority sourcing logic to determine which sourcing option to use to meet the demand.

Solver Processing of Sourcing Template Data

When you generate a plan, you can use different solvers to process sourcing information. The

following list describes the processing:

• The Material Planning solver always selects the sourcing template’s default option.

• The Feasible Planning Solver, when used to generate an initial plan, also selects the default

sourcing option. However, the solver uses the fixed-priority sourcing template to source

transfers or purchases again during the material phase. It also uses the sourcing templates

during the Lateness Reduction Phase to source items again.

• The LP Solver (Linear Programming Solver) uses the fixed-priority sourcing template to guide

its decisions on which routing option to select, but it ultimately makes decisions based on the

bigger cost trade-off picture.

• The Iterative Repair/Optimizer evaluates each sourcing option when the fixed-priority sourcing

logic is invoked. It processes the options in their order of priority until one passes all of the

selection criteria. The first option that meets all of the criteria is the one that is used. If all of

the sourcing options have been evaluated and none passed the selection criteria, then it uses the

default. If you don’t define a default option, the Optimizer uses the option with the highest

priority as the default. The highest-priority option is the one with the lowest number.

Setting Up Sourcing Templates

A sourcing template provides a list of production, purchase, and transfer sourcing options you can

use to source the demand for an item. Using PeopleTools, you can set a default option and a

priority sequence for all the options available for the item. You can also delete options from thetemplate.

You can generate the template in three ways:

1. You can let the system automatically generate templates for items during each Production

DataLink run. The DataLink loads and prioritizes options based on their costs. Lower-costs

options have priority over higher-cost options. The option with the lowest cost will be set as

the default option.

2. You can manually load and create the template. You manually create a sourcing template for

each item that you want to control. You use the sourcing template and buttons to select

which options you want to load into the sourcing template. You define the priority of each



option and which one is the default option. To protect your settings, you indicate to the

system that options for the item are maintained manually. Then, when the Production

DataLink is run again, it doesn’t override manual settings. However, remember that if you

indicate all templates are to be regenerated during the DataLink run, then manually createdtemplates are removed and refreshed by system-generated templates.

3. You can run the Create Sourcing Templates batch job to generate templates for all or a range

of items. Then, you can maintain individual templates using Sourcing Template

maintenance. If you select to maintain the sourcing template manually, it prevents the CreateSourcing Templates batch job from automatically overwriting your templates.

The DataLink and the Batch Generation process create a sourcing template for an item only whenthere is more than one sourcing option available for the item.

The Production DataLink creates new templates, when necessary, for items that don’t have

templates.

Defining Sourcing Templates

Usage Use the Sourcing Template page to load and define the default for

sourcing options manually and to establish the priority of the options

when more than one option is available. You can also select to work

with and review specific types of sourcing options, including

production, purchasing, and transfer options.

Object Name PL_SRC_TEMPLATE

Navigation Plan Production, Maintain Planning Data, Use, Sourcing Template,

Sourcing Details

Prerequisites In order to create a sourcing template, you must have a valid inventory

item defined along with attributes for generating supply (transfer

attributes, purchase attributes, production options, or bills of material

and routings). Use the Click to add a new value option to assign

sourcing options for an item.

Access

Requirements

Enter a Business Unit and Item ID to access the Sourcing Template

page.



Plan Production - Sourcing Template: Sourcing Details page


PeopleBook in PeopleBooks Standard Field Definitions: Business Unit, Planning System and

Std UOM (standard unit of measure).

When you add a new sourcing template using the Sourcing Template page, you must first either

use the Sourcing Template Load button or use the Production, Transfer, and Purchase

buttons to load sourcing options manually. After adding sourcing options to the template, you

can change the priorities and define a default option.

When the Planning engine processes the plan, it uses the default option according to if solvers

process the templates. If the template is used in processing, solvers use the highest-priority

option first and go through all the remaining options. If a sourcing option can’t be found in the

template to meet the demand, then solvers normally use the default option.

For more information about how the sourcing template is processed by solvers, see Solver

Processing of Sourcing Template Data.

Use the Search Depth field to define how many levels of the supply chain the Planning engine

will explode while solving sourcing and optimization issues. Each sourcing option represents a

single level in the supply chain. For example, suppose part A is made up of part B and part B is

made up of parts C and D. To explode all levels, you would enter a 3 in the Search Depth field.

The search depth you define is used as the default for this item for processing all the sourcing

options in the sourcing template.

Resch Early Lmt (reschedule early limit) indicates the maximum number of days early that you

want to allow solvers to move tasks in order to satisfy a demand when sourcing the demand. You

can either allow the Production DataLink or the Create Sourcing Template batch job to update

and assign sourcing options automatically or you can control how the options are used. You

select the Manually Maintained check box to indicate that the sourcing template is to be

maintained by users. When the check box is selected, the DataLink and the Create SourcingTemplate batch job don’t overwrite any options in the template.

You can’t delete a sourcing template. You can add and delete the options associated with it.



You use the Description field to describe the sourcing template as it is used for this item. To

change the priority, enter the number in the priority field. The Planning engine processes the

priority sequence first. Select the Default check box to define the default sourcing option for the

Planning engine when all others fail. Initially, this is the lowest-cost option.

Multiple views of this page are available by clicking the tabs in the scroll area. We

document fields common to all views first.

Common Page Information

You use buttons to select the sourcing options that you want to load into the sourcing template.

You load the number of production, purchasing, and transfer options that your business requires

for sourcing demand. These options provide you flexibility in planning at the item level.

Click the Sourcing Template Load button if you want to delete the existing sourcing

options and replace them with the current available sourcing options. Click Yes to

refresh with the current sourcing options. Click No to keep the sourcing options as they

appear on the page.

Click the Production button to go to the Update Production page if you want to select

production options for the item.

Click the Transfer button to go to the Update Transfer page if you want to select transfer

options for the item.

Click the Purchasing button to go to the Update Purchasing page if you want to select

purchase options for the item.

The following fields appear as common fields in the Sourcing Template page:

Default Select this check box to indicate that you want to use this

sourcing option as the default value when the Planning

engine sources demand for the current plan. You can

select one sourcing option as the default for the template.

The default option is used to source demand, after the

Planning engine goes through all sourcing template

entries, based on their planning priority, but can’t select

any of them because of problems such as capacity or

material shortages.



Priority Enter a numerical value that defines the priority you want

the Planning engine to place on using a sourcing option to

meet demand. You can enter any positive number up to

999 and the number must be unique.

The Planning engine considers all the sourcing template

options (production, transfer, and purchase) using their

priority in ascending sequence until it finds a template that

can meet the demand without creating planning

exceptions. If the engine can’t find a template without

exceptions, then it uses the default template.

Option Type Defines whether the demand is supplied by a production

task, purchase order, or by a transfer task.

Option Name Displays the name the system uses to track this particular

sourcing option.

For more information about each option type and where they are defined, see the

corresponding option discussions later in this section.

Sourcing Details tab

Viewing the Sourcing Details tab

The following information appears on the tab:

Effective Date Defines the date that a sourcing option is effective.

Unit Cost Displays how much it costs to produce a single unit of the

item defined in the sourcing template. When generate

sourcing templates automatically, the system uses the cost

as the basis for prioritizing sourcing. The lower an item’s

cost the higher the sourcing priority. Sourcing priorities

are defined using lower numbers than those with higher

priorities.



Production tab

Viewing the Production tab

As you select different Sourcing Template tabs, the sourcing options remain the same; however,

data for each type of option changes depending on the tab you select. The Production page

displays additional information associated with any production type sourcing option.

For more information about loading initial information for the Production page, see Loading

Sourcing Options.

The following information appears on the Production tab:

BOM Code This is the bill of material identifier for the production

option within the template. Production options can be pre-

defined or created based on defaults specified at the item

attributes by unit level.

Routing Code This is the routing identifier for the production option

within the template. This column is empty if routings

aren’t being used. The routing code also doesn’t apply to

production options used in PeopleSoft Production

Planning.

Associated Primary BOM When an item is a co-product on multiple primary BOMs,

then one of the items must be assigned as an associated

primary BOM. This allows the Planning engine to

explode the co-product to the next level when it processes

sourcing options at greater search depths.

If an item has an associated primary item different from

itself and also has its own BOM, then the Planning engine

imports production options for both the item itself and the

associated primary item.

For more information about setting up production options, see PeopleSoft 8.00.01 Bills andRoutings PeopleBook, “Defining Production Options”.



Purchasing tab

Viewing the Purchasing tab

As you select different Sourcing Template tabs, the sourcing options remain the same; however,

data for each type of option changes depending on the tab you select. The Purchasing page

displays vendor information.

Options that appear on the Purchasing page are combinations based on the definitions in the

Item/Vendor table.

Vendor Set ID The SetID in which the vendor information was defined.

Vendor ID Identifies a specific vendor as defined on an item/vendor

definition.

Transfer tab

Viewing the Transfer tab

The Transfer page shows active transfer options available for use by the Planning engine.

The following information appears on the Transfer page:

Source Business Unit This is the unit that is going to ship the item.

Ship Via Code This code identifies the method used for shipping the item.

Loading Sourcing Options

You use buttons to define the sourcing options that you want to load into the sourcing template.

You load the number of production, purchasing, and transfer options that your business requires

for sourcing demand. These options offer you flexibility in planning at the item level. This

section describes how to select and load production options and where the options originate.



The Sourcing Details page contains four buttons for loading sourcing options. You use three of

these buttons to select the options and the fourth to load the options. You select the button to see

the options that have been created for items. Using the page, you then select the options you want

to include in the sourcing template. After you select the options that you want to load, click theOK button.

The options you load into the sourcing template for an item remain in the template until you

delete them. As long as you select for the template to be maintained manually, the Create

Sourcing Templates batch job and Production DataLink won’t overwrite an item’s sourcing

options.

Click the Delete button next to the option on the Sourcing Details page to remove the

options you load manually.

If you decide you no longer need a manually maintained sourcing template, you can clear the

Manually Maintain check box at the top of the page. The next time you run the Create Sourcing

Template batch job or the Production DataLink when it is set to regenerate sourcing templates,

the system overwrites the current sourcing template, including the options you’ve defined.

After you select the options, you can use the Sourcing Details page to define the priority in which

you want the Planning engine to use the options to source demand. You also define a single

default option.

Loading Production Options

Click the Production button to select production options.

Sourcing Template - Select Production page

PeopleSoft Production Planning production options define how an item is produced. They

originate from Item Maintenance settings at the business unit level. A production option can be

created for each BOM and routing code combination. You can define the BOM code and routing

code and how production options are created and used at the business unit level.

For more information about setting up and using production options, see PeopleSoft 8.00.01Bills and Routings PeopleBook, “Defining Production Options”.

You can also maintain options for an item when their planning rates aren’t maintained at the

routing level. Use the Maintain Items option to access Item Attributes by Unit. Then access thePlanning page.



Production options are updated immediately when, for example, you change a BOM for an

item. The changes are available in the Select Production page and the Sourcing Inquiry.

For more information about data that appears in the Select Production page, see Verifying

Sourcing Options.

Use the Select check box to select the option or options that you want to load when you return to

the Sourcing Details page. You can select or clear an option using the check box.

After you select the production options that you want to load, click the OK button. When you

return to the Sourcing Details page, only the selected production options will be added to the

sourcing template.

Loading Transfer Options

Click the Transfer button to select transfer options.

Sourcing Template - Select Transfer page

Transfer options define how an item is moved between business units. They originate from the

transfer attributes that you define for the item. To access the Transfer Attributes page use thefollowing link: Transfer Attribute page.

Transfer options are updated immediately when, for example, you change the transportation

cost for an item. The changes are available on the Update Transfers page and the Sourcing

Inquiry.

For more information about data that appears on the Update Transfer page, see Viewing

Sourcing Template - Transfer Options Details.

Select the Select Cost check box to define the option or options that you want to load when youreturn to the Sourcing Details page. You can select or clear an option using the check box.

After you select the transfer options that you want to load, click the OK button. When you return

to the Sourcing Details page, only the selected transfer options are added to the template.



Loading Purchase Options

Click the Purchasing button to select purchase options.

Sourcing Template - Select Purchase: Vendor Details page

Two tabs are available for selecting purchase options. The Vendor Details page displays vendor

information for the item. Using the two pages, you can only change the Select check box toselect or clear an option.

For more information about information that appears on the Vendor Details page, see

Viewing Sourcing Template - Purchase Options Details.

Sourcing Template - Select Purchase: Order Modifiers page

Purchase options define how an item is procured. They originate based on a variety of settings in

PeopleSoft Purchasing. Among the considerations for defining purchase sourcing options arevendor selection criteria, such as lead time and pricing.

For more information about data to create purchasing sourcing options, see PeopleSoft

8.00.01 Purchasing PeopleBook, “Understanding Purchase Order Sourcing”.

Purchase options are updated immediately when, for example, you change the item vendor

priority for an item. The changes are available on the Update Purchasing page and the

Sourcing Inquiry.

For more information about information that appears on the Order Modifiers page, see

Viewing Sourcing Template - Purchase Options Details.



Select the Select check box to define the option or options that you want to load when you return

to the Sourcing Details page. You can select or clear an option using the check box.

After you select the purchase options that you want to load, click the OK button. When you

return to the Sourcing Details page, only the selected purchase options are added to the sourcing

template.

Generating Sourcing Templates (PLS5000)

Usage Use the Sourcing Templates page to define criteria that you want the

system to use when it sources demand automatically.

Object Name RUN_PLS5000

Navigation Plan Production, Maintain Production Data, Process, Create

Sourcing Templates

Access

Requirements

Enter a Run Control ID and Business Unit.

Process

Name

PLS5000

Process Type SQR

Plan Production - Sourcing Templates page


PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID, Report Manager,

Process Monitor, and Run.

You use the Sourcing Templates page to load production, transfer, and purchasing options

automatically into the sourcing template for a single business unit at a time. The priority of each

option is based on lowest cost. After you run the process to load the sourcing options into the

template, you can maintain the priorities and the default option manually. Using the Create



Sourcing Templates batch job is an optional step. You can create and maintain a sourcing

template without running the background process.

A sourcing template isn’t required to source an item. However, it does make it possible to

modify sourcing options and it reduces the amount of Production DataLink processing time.

If an item has a sourcing template, then the system uses entries in the template. If the item

doesn’t have a template, then the Production DataLink dynamically and temporarily creates the

sourcing template for that one-time use.

Plan Currency

The Currency Code represents the base currency for the specified business unit. It is used to

calculate costing information for setting the priorities of sourcing options for the sourcing

template. You can’t change the field.

The Rate Type determines the exchange rate the system uses to convert costs from other

currencies to the single currency code in the Currency Code field. Examples of exchange rates

include spot (immediate), current, negotiated (discount and premium forward rates), average, and

historical rates.

Planning System

You can establish a sourcing template for either PeopleSoft Enterprise or Production Planning or

both. When you select a specific system, the Create Sourcing Template builds the sourcing

templates for items for the corresponding planning system.

Sourcing Options

The Sourcing Options group box contains available options that can be used in the sourcing

template. You can select all or any combination of options. You must select at least one option.

Unselected options remain in any currently existing templates.

For example, if you select only the Purchase Options check box, then Transfer and Production

options remain unchanged in any template that they belong to when the templates are refreshed.

Purchase options will be completely refreshed for the items you select in the Item Option group

box.

The following sourcing options are available:

Production Options This is a combination of a BOM and routing code that can

be effective-dated for seasonal mix variations. The option

defines which material and resources are required to make

a specific item.

For more information about where production options are defined for an item, see Loading

Production Options.



Transfer Options This option defines the transfer attribute, such as cost or

transfer time, that is associated with transferring an item

from one business unit to another. You create the option

by defining transfer attributes for an item.

For more information about where transfer options are defined for an item, see Loading

Transfer Options.

Purchase Options This option defines item and vendor attributes, such as

cost, lead time, and order modifiers. You create the

option by defining item and vendor relationships on the

Item Purchasing attributes page.

For more information about where purchase options are defined for an item, see Loading

Purchase Options.

Item Option

Use the Item Option group box to define which items you want to include in Create Sourcing

Template processing. The following options are available:

All Select this option to include all items with defined

sourcing options in the processing. All is the default. To

clear it, you must select the Range option.

Range Select this option to specify a range of items to be

included. You use the adjoining entry fields to define a

From and To range for item IDs. The system creates

sourcing options only for those items that are within the

range. These fields are required if you select the Range

option.

Only New Items Select this option if you want to include only those items

that have been established since the last sourcing template

was created. You must also enter a date from which you

want the system to consider new items.

Date Added Enter the date from which you want the system to consider

new items. The system creates sourcing templates for any

items that were established after this date. This is a

required field if you select Only New Items.



Click Run to run the Create Sourcing Templates process (PLS5000). Process Scheduler runs the

process at user-defined intervals.

For more information about Process Scheduler, see PeopleTools 8.12 Process SchedulerPeopleBook, “Process Scheduler Basics”.

Verifying Sourcing Options

You can review an item’s sourcing template and sourcing options by using the Sourcing Inquiry

component. The inquiry shows the sourcing template for the item, along with data from

production, purchasing, and transfer options.

You use the Sourcing Inquiry pages before you run the Production DataLink to review sourcing

options that will be sent to the Planning engine. If a sourcing template doesn’t exist for the item,

then the Sourcing Template page is empty and the options appear on the Production, Purchase,

and Transfer Option pages, according to which ones have valid options assigned to them.

Defining Sourcing Inquiry Selection Criteria

Usage Use the Item Planning Inquiry page to define the item for which you

want to review sourcing options.

Object Name PL_PLAN_INQ

Navigation Plan Production, Maintain Planning Data, Inquire, Sourcing

Inquiry, Item Planning Inquiry

Prerequisites For sourcing information to appear for an item, you must first generate a

sourcing template for the item.

Plan Production - Sourcing Inquiry: Item Planning Inquiry page

You can define filters for the following values:

Business Unit This is a required field. Either type or select the business

unit to which the item belongs.



Item ID This is a required field. Either type or select the item for

which you want to see associated sourcing options.

System Defines the planning system in which the item is being

planned. You can select the PeopleSoft Enterprise or

Production Planning system. If you leave the field empty,

sourcing options for both systems appear in the inquiry.

Base Currency If you plan for an item using different currencies, you can

select the currency for which you want to review the

item’s sourcing options. The field isn’t required.

Rate Type Defines how the exchange of currency from one business

unit to another is calculated. For example, you might use

a spot rate, which is the immediate rate, versus a

negotiated rate that might provide an exchange discount.

The field isn’t required.

Click the Search button to retrieve the sourcing information for the item.

Viewing Sourcing Template Details

Usage Use the Sourcing Template page to view sourcing options for an item

along with their priority, default option, and basic details about the

option. Use the remaining tabs to see additional details for each type of

option.

Object Name PL_SOURCE_DTL


Inquiry, Sourcing Template



Access

Requirements

You must define a Business Unit and Item before you access inquiry

data.

Plan Production - Sourcing Inquiry: Sourcing Template page




PeopleBook in PeopleBooks Standard Field Definitions: Unit and Std UOM (standard unit of

measure).

When a sourcing template exists for an item, then the sourcing options appear in the Sourcing

Template. If a template doesn’t exist and valid sourcing options are available, you must use the

Production, Purchase, and Transfer Options tabs to review the options.

The Search Depth field displays how many levels of the supply chain the Planning engine will

explode while solving sourcing and optimization issues. Each routine option represents a single

level in the supply chain.

Resch Early Lmt (reschedule early limit) indicates the maximum number of days that you want

to allow solvers to move tasks up in order to satisfy a demand when sourcing the demand.

The Sourcing Template check box indicates whether a sourcing template exists for the item.

When the check box is selected, a sourcing template has been created for the item and the

Production DataLink doesn’t include this item when it creates sourcing templates automatically.

Options appear regardless of whether a sourcing template has been created.

The following information appears on the Sourcing Template page:

Default Defines the sourcing option used as the default value

when the Planning engine sources demand for the current

plan. Only a single default option can exist.

The default option is used to source demand, after the

Planning engine goes through all sourcing template

entries, based on their planning priority, but can’t select

any of them because of problems such as capacity or

material shortages.

Priority Defines the priority you want the Planning engine to place

on using a sourcing option to meet demand. The lower the

number, the greater the priority.

The Planning engine goes through the sourcing templates

based on their priority until it finds a template that can

meet the demand without planning exceptions. If the

engine can’t find a template without exceptions, then it

uses the default template.

Option Type Defines whether the demand is supplied by a production

task, purchase order, or transfer task.

Option Name Displays the name the system uses to track this particular

sourcing option.

BOM (bill of material) This is the bill of material identifier for the production

option within the template. Production options can be

predefined or created based on defaults specified at the

item-attributes-by-unit level.




Routing This is the routing identifier for the production option



production options used in PeopleSoft Enterprise

Planning.


Vendor ID Identifies a specific vendor as defined on an item/vendor

definition.

Source Business Unit This is the unit that is going to ship the item or product.

Ship Via Code Identifies the method used for shipping the item.


item defined in the sourcing template. When you generate

sourcing templates automatically, the system uses the cost

as the basis for prioritizing sourcing. The lower an item’s

cost, the higher the sourcing priority.

Viewing Sourcing Template - Production Option Details

Usage Use the Production Options page to view detailed production sourcing

information about the item.

Object Name PL_PROD_DTL


Inquiry, Production Options



Access

Requirements

Click the Search button on the Item Planning Inquiry page to access the

production option information.



Plan Production - Sourcing Inquiry: Production Options page

The business Unit, Item, and Std UOM (standard unit of measure) information are display-only

fields and default based on the search criteria you defined on the Item Planning Inquiry page.

Valid options that have been established for sourcing production appear on this page, including

the following production option information:

BOM (bill of material) This is the bill of material identifier for the production

option within the template. Production options can be

predefined or created based on defaults specified at the

item attributes by unit level.


Routing This is the routing identifier for the production option



production options used in PeopleSoft Enterprise

Planning.


Obs Date (obsolescence date) Displays when the option becomes obsolete.

Description Describes the item to which this sourcing option belongs.


item defined in the sourcing template. When you

automatically generate sourcing templates, the system

uses this cost as the basis for prioritizing sourcing. The

lower an item’s cost, the higher the sourcing priority.

Batch Cost Displays the cost of producing a planned quantity of this

item.



Viewing Sourcing Template - Purchase Options Details

Usage Use the Purchase Options page to view detailed purchasing sourcing


Object Name PL_PURCH_DTL1


Inquiry, Purchase Options



Access

Requirements


purchase option information.

Plan Production - Sourcing Inquiry: Purchase Options page


fields and default based on the search criteria you defined on the Item Planning Inquiry page.

Valid options that have been established for sourcing purchases appear on this page, including the

following purchase option information:

Vendor Set ID Groups purchasing business units that share vendor,

purchase order, and receiving information with PeopleSoft

Payables in the same SetID.

Vendor Identifies a specific vendor within a vendor set.

Vendor Name Name of the vendor as defined during vendor

maintenance.

Priority Displays the preference of which vendor to use to supply

this item. The vendor with the lowest priority number is

the most preferred. The Planning engine doesn’t use this

priority to source demand. If two vendors have the exact

same price, you can use the vendor priority as the

tiebreaker to determine which one has a higher template

priority.



Lead Time Days This is the purchasing lead time specified for the vendor

or item/vendor relationship. This represents the amount of

time it takes to get inventory from the vendor.

Std Price (standard price) Displays the standard price for the item. This value

becomes the default price in transactions where another

price, such as a vendor price or a contract price, isn’t

defined for the item.

Min Order Qty (minimum

order quantity)

Displays the minimum amount that can be placed on a

purchase order.

Max Order Qty (maximum

order quantity)

Displays the maximum amount that can be placed on a

purchase order.

Order Multiple Displays the multiple the system uses to determine an

order quantity. For example, if you have a demand for 28

and the multiple is 10, then the system generates a planned

purchase order for 30.

Purchase Yield Defines the usable output from the purchase. The value is

expressed as a percentage. Purchase yield is used in

planning to inflate the planned quantity on purchases to

account for any loss that may occur during the purchase

process.

Viewing Sourcing Template - Transfer Options Details

Usage Use the Transfer Options page to view detailed transfer sourcing


Object Name PL_TRANS_DTL1

Navigation Plan Production, Maintain Production Data, Inquire, Sourcing

Inquiry, Transfer Options



Access

Requirements


transfer option information.

Plan Production - Sourcing Inquiry: Transfer Options page




fields and are defaults based on the search criteria you defined on the Item Planning Inquiry page.

Valid options that have been established for sourcing transfers appear on this page, including thefollowing transfer information:

Source BU (source business

unit)

Displays the unit that is going to ship the item or product.

Total Cost Ship Via Displays the total amount it costs to ship the item using

the shipping method defined in the Ship Via Code field.

Min Order Qty (minimum

order quantity)

Displays the minimum amount that can be placed on a

transfer order.

Max Order Qty (maximum

order quantity)

Displays the maximum amount that can be placed on a

transfer order.

Order Multiple Displays the multiple the system uses to determine an

order quantity. For example, if you have a demand for 28

and the multiple is 10, then the system generates a planned

transfer order for 30.

Transfer Yield Defines the usable output from the transfer. The value is

expressed as a percentage. The transfer yield is used in

planning to inflate the planned quantity on transfers to

account for any loss that may occur during transport.

Defining the Line Schedule Editor Defaults

The Line Schedule Editor (LSE) is a graphical interface screen that displays production tasks for

multiple items on multiple resources across multiple periods of time. In addition, the LSE

enables you to modify the production schedule by changing the scheduled time or resource

assignments of the production tasks.

With the Line Schedule Editor, you can:

• Display resource utilization percentage in a given time period.

• Display overlapping production tasks.

• Display multiple bar definitions.

• Freeze, unfreeze, join, split, compress, and expand production tasks.

• Balance the utilization of resources by time periods and individual resources.

• Dispatch production tasks by sequencing and assigning task times.



Setting Up Item Changeover Families

Usage Use the Item Changeover Family page to associate a SetID with an item

changeover family.

Object Name PL_LSE_FAMILY

Navigation Plan Production, Maintain Planning Data, Use, Item Family Group

Access

Requirements

Enter a SetID.

Plan Production - Item Changeover Family page

SetID is a display-only field that represents a set of control table information or TableSets. A

TableSet is a group of tables (records) necessary to define your company's structure andprocessing options.

Enter the name of the Item Changeover Family with a long Description and Short Description.

The LSE uses the item changeover family to combine items based on their common production

resource (work center, machine, tool, or crew) usage to help visually identify sequencing and

changeover points within the production plan. Using the changeover family, you can group items

that can sequentially run on the same resource without incurring a changeover.

Defining the Line Schedule Editor Color Scheme

Usage Use the Line Schedule Colors page to establish colors for LSE objects.

Object Name PL_COLORS

Navigation Plan Production, Maintain Planning Data, Use, Line Schedule

Colors



Plan Production - Line Schedule Colors page

You can create a new color by changing the color name of an existing color and its corresponding

RGB (red, green, and blue) values. Each RGB value can range from 0 to 255 (inclusive).However, you can’t add a new row to the color legend.

Once you’ve defined the LSE colors, you can then assign colors to the LSE objects.

Setting Up the Line Schedule Editor General Defaults, Colors, Dimensions,and Time Periods

To create an LSE template, you need to define several attributes and maintain them in the

transaction system. Through the DataLink, you transfer the LSE data to the Planning engine,from where you can display the LSE chart.

Once in PeopleSoft Production Planning, you can modify the original settings of the LSE.

However, changes that you make to the LSE definition in the Planning Client aren’t permanent;

therefore, changes must be made in the transaction system for the changes to be saved for future

use. If changes are made to the LSE definition in the transaction system, these changes will be

modeled in the Planning engine only when the Production DataLink is run in Regenerative mode,

not Net Change mode.

Defining LSE General Settings

Usage Use the General - General page to define the general parameters of the

LSE.

Object Name PL_LSE_GENERAL


Editor, General, General

Access

Requirements

Enter a Business Unit, LSE Type (select Aggregate or Detailed), and

LSE Name.



Line Schedule Editor - General: General page

The Business Unit is a display-only field and represents the business unit for which you are

maintaining the Line Schedule Editor. The LSE Type and LSE Name also appear in the header

of the page and are display-only fields.

Select the Copy LSE to Planning check box to include the LSE in the DataLink run (at least one

resource and one time period must be defined). If you don’t select this check box, no data for this

LSE will be transferred to the Planning engine.

Select an Above Line Definition from the available options. The Above Line, which appears

when there is a capacity shortage, is displayed above the production bar. Your options are No

Above Line and Capacity Shortage. The default is No Above Line.

Select a Below Line Definition from the available options. The Below Line, which appears

when there is a material shortage or unmovable bar, is displayed below the production bar. Your

options are No Below Line, Material Shortage, or Unmovable Bar. The default is No Below

Line.

The Bar Split Duration enables you to define a duration of time that can be used to split up a

group of overlapping or continuous tasks that are represented by a single bar in the LSE chart.

The duration can be expressed in Days, Hours, and Minutes. The default is 1 minute. The

following example illustrates how the Bar Split Duration is used. Suppose you have a bar that

represents eight continuous or overlapping production tasks, and suppose you have defined a Bar

Split Duration of 1 hour. If you decide to split this bar, then this bar will be divided into two bars

such that the last task of the first bar and the first task of the second bar are rescheduled so thatthey are one hour apart.

The Header Format determines where you want the utilization percentage to appear within acell. Your options are Right, Left, and Center. The default is Right.

Select a Date Format for the time period. Your options are Date Only, Hours, Minutes, and

Seconds. The default is Date Only.

The Cell Over Maximum enables you to specify the pattern that will appear in the cell when the

capacity usage in the cell exceeds the maximum utilization percentage. Your options are

Forward Diagonal, Backward Diagonal, Cross, Diagcross, Horizontal, Vertical, and None.

The default is Forward Diagonal.



The Cell Under Minimum enables you to specify the pattern that will appear in the cell when the

capacity usage in the cell falls below the minimum utilization percentage. Your options are:

Forward Diagonal, Backward Diagonal, Cross, Diagcross, Horizontal, Vertical, and None.

The default is Backward Diagonal.

If you are creating an Aggregate LSE, you need to specify the Bucket Size. Only aggregate

resources with a bucket size equal to the bucket size value specified on this page can be assigned

to the LSE. In addition, the bucket size determines the size of the LSE time periods; this is done

to ensure that the time periods match the bucket size of the aggregate resources shown in theLSE. Your options are Daily, Weekly, and Monthly. The default is Daily.

Defining LSE Dimensions

Usage Use the General - Dimensions page to define the display dimensions of

the LSE.

Object Name PL_LSE_DIMS


Editor, General, Dimensions

Access

Requirements


LSE Name.

Line Schedule Editor - General: Dimensions page



of the page and are display-only fields. The following dimensional characteristics are available

for use:

Cell Height The height of the cell. The default is 180 pixels.

Cell Width The width of the cell. The default is 280 pixels.



Bar Height The height of the bar. The default is 12.

Bar Space Vertical spacing of the bar expressed. The default is 8

pixels.

Column Label Height The height of the column irrespective of the font. The

default is 26 pixels.

Column Font Height The vertical space of the font in the column expressed in

number of points. The default is 14 pixels.

Row Label Width The width of the row with the label. The default is 100

pixels.

Row Font Height The vertical space of the font in the row expressed in

points. The default is 16 points.

Magnify Cell Height Magnified version of the cell height. The default is 500

pixels.

Magnify Cell Width Magnified version of the cell width. The default is 850

pixels.

Magnify Bar Height Magnified version of the bar height. The default is 15

pixels.

Magnify Bar Space Magnified version of the bar height. The default is 8

pixels.

Bar Line Space The amount of space between the bar and the line above

or below it. The default is 1 pixel.

Magnify Bar Line Space Magnified version of the bar line space. The default is 1

pixel.

Row Font Name The name of the font used for the row. The default is

Arial.

Column Font Name The name of the font used for the column. The default is

Arial.

Defining LSE Color Settings

Usage Use the General - Color Settings page to define the color of LSE objects.

Object Name PL_LSE_COLORSET


Editor, General, Color Settings

Access

Requirements


LSE Name.



Line Schedule Editor - General: Color Settings page




Before you can select a color for the LSE object, the color must exist in the LSE color legend.

You can add a color to the legend using the LSE Colors page in the Line Schedule Colors

component. By changing the RGB (red, green, blue) color value (0-255 inclusive), you cancreate any color you desire. The following color schemes are available for you to use:

Downtime Color Default is Gray.

Default Bar Color Default is Red. If you don’t specify the color, then all the

bars in the display will appear red.

Above Line Color Default is Orange.

Below Line Color Default is Cornflower Blue.

Cell Color Default is Light Gray.

Time Period Color Default is Light Gray.

Resource Entry Color Default is Light Gray.

Resource Entry Offload

Color

Default is Teal.

Cell Under Min Pattern

Color

Default is Goldenrod.

Cell Over Max Pattern

Color

Default is Light Coral.

Time Period Over Min

Color

Default is Yellow.



Time Period Over Max

Color

Default is Red.

Defining LSE Time Periods

Time periods form the x-axis of the Line Schedule Editor. Essentially, a LSE time period is an

offset of the current time. To display the LSE chart, you must first set up at least one time period

for the LSE.

Because time periods for a detailed LSE and aggregate LSE are set up differently, you need to

define them on two separate pages.

Setting Up Time Period for Detailed LSE

Usage Use the General - Time Periods Detailed page to define the time periods

for a detailed LSE.

Object Name PL_LSE_TIME


Editor, General, Time Periods

Access

Requirements

Enter a Business Unit, LSE Type (select Detailed), and LSE Name.

Line Schedule Editor - General: Time Periods (Detailed) page


maintaining the Line Schedule Editor. The LSE Type and LSE Name also appear in the headerof the page and are display-only fields.

Enter a Start Date Offset (Days) for the first LSE time period as an offset (in days) from the

current time. For example, if today’s date is 5/5/00 and you want the start day to be one week

from now, you would enter 7.

Enter a quantity for the Daily Time Periods and Weekly Time Periods.



For Daily Time Periods, specify one Minimum Utilization % (minimum utilization percentage)

and one Maximum Utilization % (maximum utilization percentage) to be assigned to each time

period. Similarly, for Weekly Time Periods, enter a Minimum Utilization % and Maximum

Utilization % for each time period. The default value for the Minimum Utilization % is 0, andthe default value for the Maximum Utilization % is 100.

Select the Always Start Weekly Periods On check box to indicate that the weekly periods

should always begin on a certain day of the week. If you don’t select this check box, then the

weekly periods will begin immediately after the daily periods end. If you select this check box,

then extra daily periods will be added so that the first weekly period begins on the day of the

week that you select from the available options.

Setting Up Time Period for Aggregate LSE

Usage Use the General - Time Periods Aggregate page to define the time

periods for an aggregate LSE.

Object Name PL_LSE_TIME


Editor, General, Time Periods

Access

Requirements

Enter a Business Unit, LSE Type (select Aggregate), and LSE Name.

Line Schedule Editor - General: Time Periods (Aggregate) page




Enter a Start Date Offset (Days) for the first LSE time period as an offset (in days) from the

current time. For example, if today’s date is 5/5/00 and you want the start day to be one weekfrom now, you would enter 7.

Specify the number of Time Periods for the LSE.

For the time periods, specify one Minimum Utilization % (minimum utilization percentage) and

one Maximum Utilization % (maximum utilization percentage) to be assigned to each time



period that you create. The default value for the Minimum Utilization % is 0, and the default

value for the Maximum Utilization % is 100.

Setting Up Line Schedule Editor Resource Entries Defaults

Usage Use the Resources page to view or edit a resource entry and its

corresponding bar definition.

Object Name PL_LSE_RESOURCE


Editor, Resources

Access

Requirements


LSE Name.

Line Schedule Editor - Resources page

LSE resource entries are placeholders for the resource, and they form the y-axis of the graphical

editor. To display the LSE chart, the LSE must contain at least one resource entry. You can add

a resource entry any time after you’ve created the Line Schedule Editor.

Both detailed and aggregate resources can be used as LSE resource entries. The order in which

resource entries are added to a Line Schedule Editor determines the order in which they appear inthe chart.

A detailed resource displays one task at a time and shows how each one is scheduled.

Conversely, an aggregate resource shows all tasks scheduled at the same time.




Select a Resource Type from the available options: Crew, Machine, Rough Cut Resource, Tool,

Workcenter, or Workcenter (Subcontract).

Select a Resource Code from the prompt.

Select a Bar Definition from the following options



Gantt This bar represents a single production task. Each bar

must be displayed alone on its own cell row, which is

similar to the existing task Gantt charts in the PC client.

Item This bar represents a sequence of production tasks for the

same item so that no temporal gap exist between the tasks.

This means that either each task in the sequence overlaps

with the previous and next task of the sequence, or the

task is scheduled exactly “next to” the previous and next

task of the sequence.

Item Changeover Family This bar is similar to the Item bar, except that it represents

a sequence of production tasks for items that belong to the

same item changeover family such that no temporal gaps

exist between the tasks.

Item Utilization This bar represents all production for a specific item in a

cell. Each utilization bar starts at the beginning of the cell

and ends according to how much of the resource it

consumes for that cell. For example, a bar that takes 50%

of the cell utilization will end in approximately the middle

of the cell.

Item Changeover Family

Utilization

This bar represents all production for a group of items in a

cell that belong to the same item changeover family. Each

utilization bar starts at the beginning of the cell and ends

according to how much of the resource it consumes for

that cell. For example, a bar that takes 50% of the cell

utilization will end in approximately the middle of the

cell.

For a detailed resource, the default bar definition is Item. Aggregate resource uses Item

Utilization as the default.

Defining LSE Balancing Defaults

Usage Use the Balancing page to add or edit the balancing parameters for a

resource.

Object Name PL_LSE_LINEBALANCE


Editor, Balancing

Access

Requirements


LSE Name.



Line Schedule Editor - Balancing page

PeopleSoft Production Planning provides a set of line balancing utilities that balance the

utilization of equipment resources by assigning resources (lines) to production tasks. The

primary goal of a line balancing utility is to avoid or reduce overallocation of resources. Line

balancing supports both detailed and aggregate resource. However, you can balance only onetype of resource at a time.

Line balancing utilities provide a flexible mechanism to associate tasks during balancing. You

can associate production tasks by item, item-slot values, or demand priority of a pegged chain. In

addition, you can determine the order in which you balance the associated production.

With line balancing, you can:

• Balance the utilization of resources by time periods.

• Balance the utilization of individual resources.

• Clear all of the production from a resource by time period, grid period, or resource.

• Offload just enough production according to specified criteria.

• Move a specific percentage of production from a source grid period to the destination grid

period.




Select a Move Bar Definition from the available options using one of the following options:

Fill Move enough production tasks from one cell to another so

that the maximum utilization percentage of the source cell

isn’t reached.

Move Task Move tasks around to balance utilization of individual

resources. This is the default.



Offload Move the resource from the source row to the destination

row. You must first select the source row and move it to

another resource row (destination). You can move every

cell in the grid into one bar definition row.

Select a Dispatch Order from the available options. The dispatch order is crucial to the

development of a capacity plan, as it determines how you sequence and assign tasks. The

primary purpose of the dispatch utility is to reduce changeover cost and changeover time of the

items. Your available options are Changeover Cost, Changeover Item, and Changeover Time.

The default is Changeover Cost.

The dispatch order applies only to detailed LSE. There is no dispatch order for aggregate

LSE.

Defining LSE Bar Colors Defaults

Usage Use the Bar Colors page to assign a color to an item and item

changeover family.

Object Name PL_LSE_CHGOVER


Editor, Bar Colors

Access

Requirements


LSE Name.

Line Schedule Editor -Bar Colors page

LSE uses the item changeover family as a criterion to dispatch detailed resources. Items that

belong to the same changeover family have the same bar color.

Before you can associate an item with an item changeover family, you must first define the

changeover family at the SetID level using the Item Changeover Family page in the Item Family



Group component. Once you have created the changeover family, you can then associate it with

an item and color.




Select an Item ID and Item Changeover Family from the respective prompt. Select a Color

Name from the available options.

For more information about item changeover families, see PeopleSoft 8.00.01 AdvancedPlanning Client PeopleBook, “Changing Products and Items”.

Defining LSE Filters Defaults

The Line Schedule Editor provides the capability to include and exclude certain bar items and bar

colors in the LSE chart. You can choose to turn the filtering feature on and off.

Setting Up Bar Item Filters

Usage Use the Filters - Bar Item Filters page to include certain production

items that will be displayed in the LSE.

Object Name PL_LSE_ITEMFILTER


Editor, Filters, Bar Item Filters

Access

Requirements


LSE Name.

Line Schedule Editor - Filters: Bar Item Filters page






Select the Use Bar Item Filter check box if you want to use the bar item filter in PeopleSoft

Production Planning. If you don’t select this check box, then all bar items will be sent to

Planning.

Select an Item ID from the available options. The Description appears when you click the field

heading or select the Use Bar Item filter check box.

Setting Up Bar Color Filters

Usage Use the Filters - Bar Color Filters page to include certain colors that will

be displayed in the LSE.

Object Name PL_LSE_COLORFILTER


Editor, Filters, Bar Color Filters

Access

Requirements


LSE Name.

Line Schedule Editor - Filters: Bar Color Filters page




Select the Use Bar Color Filter check box if you want to use the bar color filter in PeopleSoft

Production Planning. If you don’t select this check box, then all the bar colors associated withitems of changeover families will be displayed in the LSE.

Select a Color Name from the available options. You can add as many colors as you want into

the grid, as long as the color has been defined in the color legend.

Viewing the LSE Chart

If you want to view the LSE chart, you must access the Planning client. You can then use the

LSE pages for the Planning client to further define the LSE parameters before displaying the

chart. In addition, when you display the chart, you can manipulate the LSE objects to generate“what-if” scenarios.



For more information about configuring the LSE in the Planning client, see PeopleSoft8.00.01 Advanced Planning Client PeopleBook, “Using the Line Schedule Editor”.

Verifying Production Planning Data

Before you run the Production DataLink, you’ll want to verify that the planning data you’re

sending to the Planning engine is accurate.

Understanding the Data Verification Process

The Planning Data Inconsistency Report (PLS3000) enables you to identify items to be plannedand validates the items that are currently planned.

Using the Planning Data Inconsistency Report (PLS3000), you can:

• Identify any PeopleSoft Production Planning components whose routing sequence number is

invalid or zero.

• Identify any manufactured PeopleSoft Production Planning items that have no routing in the

routing table.

• Verify that the master-plan items have only master and material components.

• Verify that the material plan items have only material components.

• Identify the Item/Production Areas that have no valid routing.

• Identify the routings that have no Item/Production Areas.

• Report routings that have no planning times.

• Identify items with routings that have no default Production Areas.

Generating the Planning Data Inconsistency Report (PLS3000)

Usage Use the Planning Data Inconsistency Report (PLS3000) to report any

problems in the planning data.


Navigation Plan Production, Maintain Production Data, Report, Planning Data

Inconsistency Report

Access

Requirements

Enter a Run Control ID.



Process

Name

Planning Data Inconsistency Report (PLS3000)

Process Type SQR

Plan Production - Planning Data Inconsistency page


PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID, Language, Report

Manager, Process Monitor, and Run.

Select the business Unit for which you want to generate the Planning Data Inconsistency Report.

Click Run to run the Planning Data Inconsistency Report (PLS3000) using Process Scheduler.


For examples of this and other reports in your application, see the PDF files published on

CD-ROM with your documentation.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L S E T T I N G U P T H E P R O D U C T I O N D A T A L I N K 3 - 1

C H A P T E R 3

Setting Up the Production DataLink

One of the powerful features of PeopleSoft Production Planning is the ability to link your

enterprise system closely with the advanced planning and scheduling system. PeopleSoft

Production Planning uses data extracted from your PeopleSoft Supply Chain Management

databases. You maintain all data within these associated applications, including static data (such

as item attributes and bills of material) and dynamic data (such as sales, purchase, and production

orders). When you want to generate and analyze a plan, you move the data into the PeopleSoftProduction Planning in-memory engine using the Production DataLink.

Extracting information from your PeopleSoft database is the first step you perform to generate a

production plan. Using the Production DataLink, you extract required data from PeopleSoft

Purchasing, Inventory, Order Management, Production Management, and Bills and Routings.

The Production DataLink creates the data model that drives the planning solvers and algorithms

in PeopleSoft Production Planning.

Overview of the Production DataLink Process

You use the Production DataLink to define which options you want to include in your master or

material plan. These options range from time fences to the types of tasks that you want to include

in your plan. You can set up and rerun the DataLink as often as necessary to create a feasible

plan and to improve the quality of plans that are already feasible.

The Production DataLink generates command files that are sent to Planning servers which, in

turn, process the files and send action messages regarding supply and demand back to PeopleSoftOrder Management, Inventory, Purchasing, and Production Management.

A number of command files exist to set up data for the Planning server, including items and

demand and supply files. For example, an Environment file contains the transactions required to

define general parameters such as time fences for the planning model while a Procurement filecontains the transactions required to set up purchase orders.

Planning servers use solvers to process your plan. These planning tools are designed for you to

automate the planning process, or they assist you in an interactive mode to develop an executable

plan. The capabilities of the solvers range from developing a simple material plan to helping you

produce advanced material- and capacity-feasible plans. Solvers help you make planning

decisions from an enterprise level down to the manufacturing floor.


3 - 2 S E T T I N G U P T H E P R O D U C T I O N D A T A L I N K P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

You can run planning solvers several times and in several ways for a given PeopleSoft

Production Planning data model. This includes automatically setting up and running a solver

to generate a plan when you load the initial data or manually specifying parameters and

initiating the solvers. Also, you aren’t limited just to one solver for each planning model. It

might be necessary to control the PeopleSoft Production Planning process by solving

finished-goods material problems before solving lower-level capacity issues.

Using the DataLink, you can define which items you want to plan for in both PeopleSoft

Enterprise Planning and PeopleSoft Production Planning as well as the types of demand andsupply you want to include in your plan.

Flow of data between the PeopleTools transaction system and Planning servers

The Production DataLink is instrumental in bringing together item and inventory data from other

PeopleSoft applications, including Order Management, Purchasing, Inventory, and

Manufacturing. The DataLink creates a planning model that it sends to Planning servers.

Dynamic data that is moved in the example is constantly changing and flexible. This type of data

is made up of demands, such as forecasts, and supplies, such as transfer orders.



PeopleSoft Enterprise Planning servers might contain manufacturing and inventory business

units whereas the PeopleSoft Production Planning servers focus on only a single

manufacturing site.

When the DataLink creates a planning model, it includes but isn’t limited to the following data:

• General planning parameters.

• Business unit definitions and item definitions.

• Inventory balances and policies.

• Production and closure calendar information.

• Transfer and purchasing attributes.

• Manufacturing bills and routings.

• Demand and supply transactions.

After the Production DataLink produces the data model and the Planning solvers generate a

master or material plan, the system returns results in the form of planning messages that you can

use to commit the plan back to PeopleSoft Inventory, Purchasing, Production Management and

Order Management.

For more information about reviewing planning messages, see “Processing Planning

Messages in PeopleSoft Production Management”.

Setting Up Solvers Using the Production DataLink

When you set up the Production DataLink, you can define which solvers you want to use to

process the plan after you load the data model into the Planning engine. The Planning engine

runs the solvers based on the controls you define.

You use solvers to create viable medium-term material and capacity requirement plans that are

easy to understand and use. For medium-term planning, you can use solvers available in the

Production DataLink to determine what is required to meet all demands and make your plansmaterial- and capacity-feasible.

Material feasibility means that the longest cumulative lead-time exists within a doable time frame

where there are no material shortages. Capacity feasibility means that there are no critical

capacity violations for aggregate resources that are marked for repair in the planning time period.

Four solvers are available for you to run automatically during the loading of the data model into

the Planning server. The ultimate goal of the solvers is to produce a plan that doesn’t contain

material shortages or capacity violations. In addition to producing material- and capacity-feasible

plans, solvers identify and report on unavoidable instances in which the plan is jeopardized. For



example, perhaps material cannot be sourced or when there is insufficient lead time to satisfy a

demand.

In determining feasible plans, solvers use pegged chains that tie tasks and top-level demand

together. In doing so, solvers can explicitly track and record which supplies they are using to

satisfy which demands. The Production DataLink uses the following solvers to assist you in

producing a viable plan:

Material Planning Solver Provides a simple plan that resolves material shortages. It

also provides a variety of options, such as capacity

smoothing, generating fixed-period requirements, and

consolidating purchase orders. Using the Material

Planning Solver provides a good starting point for

generating a feasible plan. You can create a material plan

for any combination of master and material-planning

items in Production Planning.

Feasible Planning Solver Tries to resolve all material and capacity exceptions and to

meet all due dates, using demand priority and minimizing

lateness as much as possible. The solver also minimizes

excess inventory and tries to maintain just-in-time

scheduling and preserve existing supply and demand

relationships.

LP Solver (Linear

Programming Solver)

Serves as a more complex planning tool that models the

supply chain and computes schedules that optimize a

selected objective while satisfying a set of specified

constraints on operations. It is especially designed to

work with reasonably large data sets. The modeling

process extracts basic supply chain information from

Production Planning data structures and generates an

aggregated supply chain model in linear programming

form. The solver doesn’t ensure a material- or capacity-

feasible plan. You can use LP Solver solutions that feed

into the Feasible Planning Solver to obtain a viable plan.



Iterative Repair Also called the Optimizer, this advanced planning tool is

available for creating a plan or detailed schedule. You can

run Iterative Repair by itself or as part of the overall

planning process. Iterative Repair doesn’t use pegged

chains or demand priorities. Although we don’t

recommend it, you can run Iterative Repair as the initial

phase of the Feasible Planning Solver.

During each of its phases, the Optimizer runs a series of

iterations and repairs a series of violations. After you run

an iteration, the Optimizer scores the schedule and

determines whether or not to continue working on that

iteration. The process of scoring constraints enables

Iterative Repair to determine which constraints are

violated as well as the order in which the violated

constraints should be repaired.

Reviewing Time Fences Used by Solvers

Fences play an important role in how solvers analyze supply and demand. These fences represent

points in time before or after which solvers take certain actions. Solvers use fences to determine

how far supply or demand tasks can be moved forward or backward to meet planning needs.

Planning and scheduling problems occur within four periods of time. Time fences help define thefollowing types of planning periods:

• Today’s schedule that has been released to the manufacturing floor.

• Short-term scheduling on a time line with shift or daily bucket planning.

• Medium-term planning.

• Long-term planning.

Solvers are best applied to medium-term planning. This planning period typically focuses on

tactical planning issues such as meeting due dates, managing inventory levels, planning material

deliveries and resource loads, and making sourcing decisions. Capacity- and material-feasible

planning occur across medium- and long-term planning.

You use the following types of fences when using solvers:

Start of Time This is the beginning time boundary, before which time

doesn’t exist. Orders and changes aren’t recognized

before this point in time. Used with the end of time, the

region defines the time period within which the system

recognizes orders and changes. Solvers don’t recognize

times before the start of time.



Early Fence This is the beginning time of the interval within which

solvers process the elements of the material- and capacity-

feasible plans. You usually set the early fence to the

current date.

Current Time This is the current date and time as set by the system.

This fence is used to define various time offsets respected

by the planning solvers.

Capacity Fence The date and time that solvers begin ignoring capacity

violations. After the date, the Material Planning, Feasible

Planning, and LP Solvers ignore violations; however, the

Optimizer doesn’t use this date when it processes capacity

violations. If the capacity fence intersects an aggregate

capacity bucket, then aggregate capacity violations are

respected for the current bucket interval but ignored for

the succeeding bucket intervals.

Late Fence The LP Solver and Iterative Repair Solver use this fence

as a point to distinguish the planning horizon. They

cannot schedule task after this fence.

End of Time This is the concluding time boundary. Time doesn’t exist

after this date. Solvers don’t recognize orders or changes

after this date.

The planning horizon for the Material Planning and Feasible Planning Solvers spans the time

between the early fence and the end of time. The planning horizon for the LP Solver and the

Optimizer spans the time between the early time fence and the late time fence.

Each solver is designed to behave in certain ways with respect to fences. For example, the

Material Planning Solver is set to respect the early time fence by not rescheduling any tasks

that begin before the fence.

Planning servers also contain several utilities that use time fences. The Expand utility

reschedules tasks as close to the late fence as possible without creating material or capacity

violations. The Compress utility reschedules tasks as close to the early fence as possible withoutcreating material or capacity violations.

The early fence provides a boundary before which solvers, the Optimizer, and the Compress

and Expand utilities cannot move tasks. As a general rule, the region before the early fence

is frozen to the planning solvers.

Each solver and the utilities process planning conditions work with time fences. You also

maintain tasks within time fences.



PlanningConditions

MaterialPlanningSolver

FeasiblePlanningSolver

LP Solver Optimizer Expand/CompressUtilities

ManualResched.

Reschedule

tasks before

Early Fence

No By

Exception

No No No Yes

Move orders

before Early

Fence

No By

Exception

No No No Yes

Create new

orders before

Early Fence

No By

Exception

No By

Exception

No NA

Respect Late

Fence

No No Yes Yes Yes No

Recognize

violations

before Early

Fence

NA No No No NA NA

Respect

Capacity

Fence

Yes Yes Yes No No No

Beginning

Fence

Ending Fence

Boundaries

Early

Fence

End of

Time

Early

Fence

End of

Time

Early

Fence

Late Fence

Early

Fence

Late Fence

Early

Fence

Late Fence

Start of

Time

End of

Time

Pegged Chain Processing for Solvers

In determining feasible plans, the solvers use pegged chains that tie tasks and top-level demand

together. In doing so, solvers can explicitly track and record which supplies they are using tosatisfy what demands.

The following diagram shows an example of how demand is linked with its supply through

pegged chains. Although the diagram suggests a left-to-right flow, pegged chains appear in the

Supply Chain Viewer on a time line that flows backward from how the example appears.



Pegged chain example

In the example Task A, the sales order shipment represents the top-level demand for the blue

bicycle. The pegging records that Task B supplies this top-level demand by transferring the

supply. Task B, in turn, places the demand for the bicycle on the transferred-from business unit

and is pegged/satisfied by Task C. This relationship continues down the chain as illustrated, so

that all the tasks in the chain are linked and their supply eventually serves the top-level demand

for Task A as recorded in the pegging.

Top-level demand is the highest level in a bill of material (BOM) hierarchy. Independent demand

is a type of top-level demand. Using pegged chains, the planning solvers can:

• Move the entire pegged chain when tasks need to be moved, resolving capacity violations and

fixing late supplies. The movement helps maintain material requirements planning (MRP)-likeproperties, such as lot-for-lot behavior, and minimizes excess inventory.

• Develop more intelligent heuristics that enable you to see the entire cumulative downstream

effects on the plan directly as a task is moved.

• Provide demand priority data to help support manual decisions. For example, if you move a

task manually, you can easily tell which demands the movement affects.

• Provide demand priority data to help make detailed automated decisions. For example, the

system can resolve a capacity overload by selecting candidates to move later based on the

priorities and lateness preferences of the pegged demands.

Using Solvers to Process a Plan

How you use solvers depends on the objectives of your plan. There isn’t a defined order for

running each solver or a predefined set of rules that you must include in a solver run. You can,



for example, use solvers to determine when you intervene to produce a feasible plan. You can

alter the flow of tasks to meet specific planning needs.

Example of using solvers to process feasible plans

To create a material- and capacity-feasible plan, use the following steps:

1. Use the Roll Forward utility to move past-due tasks to a valid time in the future. You can

automatically roll forward active phases or you can use a Planning server to work with the

task you want to roll forward.

For more information about Roll Forward phases, see “Setting Up Production Planning”.


3 - 1 0 S E T T I N G U P T H E P R O D U C T I O N D A T A L I N K P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

2. Set up the Production DataLink to generate an initial material plan using one of the following

solvers:

� Material Planning Solver: Use this solver to generate an initial material plan. Because

this is the initial plan, you can run it in either Regenerative or Net Change mode.

� LP Solver: Use this solver to generate an initial plan when there are more complex trade-

off decisions in the supply chain network. These decisions might include sourcing,

alternate resources, item substitution, or material allocations based on demand priority

decisions. This is a regenerative process in which all independent demands are

rescheduled to their due date and all tasks with status of Planned are deleted. You can

run the Feasible Planning Solver after you run the LP Solver to create a plan that isfeasible.

� Feasible Planning Solver: Use this solver to create a plan that ensures material andresource capacity is available to meet the plan.

When the initial plan isn’t created lot-for-lot, such as with the LP Solver or with the Fixed

Period option in material planning, the Feasible Planning Solver may create temporary excess

inventory in the plan.

3. Review and make manual changes to the plan. The system provides you with a number of

options that you can use to review and resolve tasks with late material supplies, to repair

various problems with the plan, and plan for resources. The following options are available:

� Planning workbenches provide a way for you to interact with the plan using an Internet

browser. Using the workbenches, you can change order quantities, dates, and tasks. You can

also freeze tasks, cancel existing orders, or delete new planned orders.

� A Planning Scorecard provides a way for you to review the number of constraint violations,

the score, and counts for each type of constraint. The Planning Scorecard is available

through an Internet browser or through the Advanced Planning Client.

� Gantt and histogram charts and spreadsheets assist you to locate and resolve problems in the

plan. Use a Planning server to access these options. Gantt charts and histograms are

available through the Advanced Planning Client only. Spreadsheets are available through

the Internet browser and the Advanced Planning Client.

� Pegging Gantt charts show you the pegged relationships between the top-level demand and

dependent demand tasks. Right-click a task in the Gantt chart and select Solver Pegging.

You can review the forward, backward, or entire pegged chain for the task. Use a Planning

server to access this option. Pegging Gantt charts are available in the Advanced Planning

Client only.

� Task property sheets are available for you to make changes to a single or multiple tasks. For

example, you can change the duration or the end time of a late purchase order. Use a

Planning server to access this option. Task property sheets are available through the

Advanced Planning Client.

� The Modify Resources to Repair utility makes it possible to define which resources should

be repaired when you run the solvers. You can use this utility before you run the initial plan.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L S E T T I N G U P T H E P R O D U C T I O N D A T A L I N K 3 - 1 1

Use a Planning server to access this option. You can identify resources to repair persistently

when setting up resources or while working with data using the Advanced Planning Client.

When changing which resources to repair through the Advanced Planning Client, the

changes are only retained for that data model while in-memory within the Planning server.

� The Late Supplies Inquiry enables you to view and define how the Feasible Planning Solver

should handle supplies not available on time to meet demand. Use a Planning server to

access this option. The inquiry is available in the Advanced Planning Client only.

� The Unfulfilled Demand Inquiry enables you to view demand with insufficient pegged

supply and unmet safety-stock requirements. Use a Planning server to access this option.

The inquiry is available in the Advanced Planning Client only.

4. Run the Feasible Planning Solver.

The Feasible Planning Solver uses the existing plan and ensures that it is a material- and,

optionally, a capacity-feasible plan. You can run the solver multiple times using different

options, giving you the opportunity to make manual changes or to view the current state of

the plan. In this way, you use the solver as a powerful net-change mode. Alternatively, all

phases of generating the final plan can be automated into a single run.

5. Develop a detailed plan manually using the Line Schedule Editor. This is an optional step.

You use the Line Schedule Editor primarily for short-term planning. After developing a

detailed plan, you might need to change the early fence date to separate the new short-term

planning horizon from the medium-term horizon. This fence indicates that up to this point

you are satisfied with the plan.

Subsequent solvers assume that you will handle material and capacity exceptions before this

fence and won’t make any short-term planning changes before the fence. While you use the

editor for short-term planning, it may still be useful for intervening in special cases in the

medium-term horizon.

For more information about the Line Schedule Editor, see “Setting Up Production Planning”.

Overview of the Material Planning Solver

The Material Planning Solver creates a simple material plan to give an accurate picture of the

lead-time and materials necessary to satisfy all top-level demands. Material planning handles

production, purchases, and transfer supply task plans in a lot-for-lot manner, unless you use the

fixed period of supply option or order modifiers. Supplies are created just in time to satisfy theirdemand. Before it creates any new planned orders, the solver reschedules or uses existing orders.

The Material Planning Solver uses existing supply or creates supply for all demands in the

system. However, when supply is planned for demand and there isn’t enough lead time or the

demand is before the early fence, the system records the relationship using pegged chains and

creates supply as early as possible after the early fence. When creating this supply, the solver



explodes the primary routing using the primary resource and doesn’t consider alternate routings,

alternate resources, or the cost of getting supplies on time.

When you run the Material Planning Solver, it uses backward planning techniques to create

planned orders by exploding them earlier in time and down the bill of material structure while

respecting all relevant task calendars and legal times. The solver uses the following planning

modes:

Regenerative When Material Planning is run in this mode, all tasks or

orders with a status of Planned are deleted from existing

data and a material plan is generated for all inventory

items. With this mode, all previous supply and demand

relationships (recorded in the pegging) are erased and all

independent demand is rescheduled to its original due

date.

Net Change When you use this mode to run the Material Planning

Solver, the system produces a material plan only for those

items that have shortages. This includes subassemblies

and raw materials. When there is a material shortage

recorded by the pegged chain, the entire part that is in

demand is planned again.

When a supply is late for a demand but is pegged, it isn’t considered a material shortage.

When a part is planned for again in the Net Change mode, all planned supplies are deleted

and any end-demands for that part are returned to their due date. In addition, all pegging

history for that part is deleted. All other parts remain unchanged.

The new net change ignores and may cause material shortages due to late demands as orders are

rescheduled to satisfy supply. You can eliminate these shortages by running the FeasiblePlanning Solver or using the Planning server to run the Late Supplies Inquiry.

Overview of the Feasible Planning Solver

The Feasible Planning Solver ensures material feasibility for all resolvable material violations

between the early fence and end of time. If you use the Make Plan Capacity Feasible option, it

ensures capacity feasibility as well. The solver is designed to start from any initial plan and turn

it into an executable plan. It tries to do this while making only minimal changes to the existing

plan.

When the solver is invoked, it checks any current pegging for consistency and maintains that

pegging. The only situation for which the solver modifies the pegging is when it is necessary to

make the plan material- and capacity-feasible. If pegging doesn’t exist, the Feasible Planning

Solver creates the pegging based on a first-in, first-out (FIFO) basis.



If you have frozen tasks, model errors, or insufficient lead time in the planning horizon, the

Feasible Planning Solver may encounter capacity or material violations that cannot be

resolved. In these cases, the solver identifies unavoidable problems and makes the rest of

the plan feasible.

The most basic use of the Feasible Planning Solver is to have all parameters for it unselected.

The following sections describe how the solver processes a plan when you use this mode and all

other modes.

Verifying Current Supply and Demand Quantities

The solver checks to ensure that the current supply and demand quantities aren’t in disagreement

with any existing pegging. If they disagree, the solver adjusts the pegging to make it consistent.

Then it records the supply and demand quantities for the item, inventory constraints, and item

supplies.

Satisfying Unmet Demand

When the solver finds an unmet demand, it does the following:

• Looks for unpegged supply that is earlier in time and pegs it with the demand. If the supply

isn’t already pegged, it rescheduled it just in time for the new demand.

• Checks to see if the Planning server histogram at the end of time (plus a base safety stock,

which is the level of the stock period at the end of time) indicates that the plan is short in

supply. If it is, the solver creates a minimum amount of supply either to move the histogram

up to a positive value or to satisfy the current demand.

• After it makes the histogram positive, the solver schedules and pegs unpegged supplies that

occur later than the unmet demand, avoiding permanent excess stock.

The Inventory histogram provides a representation of the projected quantity for an item. The

histogram may be negative after unmet demand is satisfied. If a previous solver has decided

that a supply is for a demand as reflected by the pegging, the Feasible Planning Solver

respects that demand as met, even if the supply is late. The late supplies are corrected if you

select the Allow Rescheduling check box.

Verifying Demand Priority for Frozen Tasks

At the start of feasible planning runs, the solver verifies that the frozen priorities are assigned

correctly in case the frozen status has changed between Feasible Planning Solver runs.

The demand priority on a task is based on the highest-priority top-level demand that the task

supplies. For example, if a production task supplies a priority 10, 5, and 3 demand, the priority of



that production task is 3, the highest priority. The system assumes that all subtasks under a parent

have the same priority.

If you change the priority of a task, the existing pegging, in most cases, won’t recognize the

change. If you regenerate the plan, the change will be recognized only for end demands. All

pegging is erased using the Regenerate mode, so component supplies return to the default 999

priority.

If a task is frozen, it has a system-reserved priority of zero. You can see the priority value by

using the Demand Prioritization option in PeopleSoft Production Planning. As with other

priorities, all component tasks inherit the zero priority. When the plan is processed, the Planning

engine interprets the zero priority as unmovable in the forward direction and these tasks are given

the highest priority. In this case, the system does not assume that all subtasks under the parent

have the same priority. Step 3 of a 10-step production process may be frozen, since the priority

zero means a task cannot be moved forward; only component supply for steps 1 through 3 will

have the zero priority. If step 5 demands a component, that component will reflect the priority of

the highest-priority end demand.

Ensuring Positive On-Hand Quantity at the Early Fence

If a supply ends after the early fence and its pegged demand starts before the early fence, the

Feasible Planning Solver cannot resolve this infeasibility without violating the early fence. In

this situation, the solver uses the demand’s move preference in the Late Supplies Inquiry and

either schedules the supply in or schedules the demand out.

Sourcing Allocations and Options to Reduce Lead Time

If you enable material reallocation, alternate routings, or item substitution, the Feasible Planning

Solver tries to shorten the lead time of pegged chains that are late. The solver goes through the

pegged chains in priority order and tries to make them on time. It selects the highest-level late

demands down each branch of the supply chain and tries to find alternate ways to get the supply

based on the reallocation methods you select.

If the solver fails to find a feasible source of supply for a particular demand down a branch, it

tries to find an alternate way to get that demand’s supply higher up in the pegged chain. For

example, you might build bicycles and have a late supply only for tires. If the solver can’t find an

alternate way to replenish the tires on time, it looks for alternate ways to replenish wheels. If it

can’t find wheels on time, it looks for wheel assemblies, and if the solver can’t find wheelassemblies, it looks for bicycles.

Another example might be when an MRP has a demand for bicycles on the early fence and there

isn’t a supply on the schedule. This means that the bicycles are late, the wheel assemblies are

late, and so on down the chain. However, in this case the solver begins the search at the highestlevel of demand. So it begins and ends the search looking for an alternate source of bicycles.

To make a plan material feasible, the Feasible Planning Solver uses the following steps when youselect all options:

1. First, the solver looks for unpegged supply for the primary item when any options are

selected on the page. This is supply that isn’t pegged to another demand.



2. Failing the previous first step, and if Allow Item Substitution is selected, the solver looks for

unpegged supply for substitute items in the full amount required to meet the demand.

3. Failing the second step, and if Allow Alternate Routings is selected, the solver looks at all

transfers, production, and purchases for the supply.

4. Failing the third step, and if the Allow Material Reallocation option is selected, the solver

reallocates the item’s supply on the primary item to the highest-priority demands.

5. Failing the fourth step, and if the Allow Material Reallocation option is selected along with

the Allow Item Substitution option, the solver reallocates all primary and all valid substitutes

to the highest-priority demands.

When supply is reallocated across substituted items, the solver doesn’t consider the priority

of the substitute defined in the bill of materials. For example, a task may lose its primary

item to a higher-priority task that has the reallocated part as a secondary substitute.

Reducing Excess Inventory

At the end of the Feasible Planning Solver run, regardless of the sourcing and allocation options,

the solver tries to reduce excess inventory. Where possible, the solver exchanges a feasible

existing supply for a feasible planned supply and deletes leftover planned tasks and cancels

leftover existing tasks. If you don’t ignore safety stock, the excess clean-up won’t delete suppliessuch that the stock level drops below the current safety limit in the period when the supply ends.

Making the Plan Capacity Feasible

The Make Plan Capacity Feasible option invokes a capacity repair feature when you run the

Feasible Planning Solver. When you make the plan capacity-feasible, the Feasible Planning

Solver resolves aggregate capacity violations by moving tasks, in time, to alternate resources. Or,

if Use Alternate Routings is selected, the solver moves tasks to alternate production options that

have a different bill of resource but the same bills of material.

The capacity-feasible option resolves aggregate capacity violations while maintaining

material feasibility. It doesn’t resolve detailed resource violations.

The Capacity phase of the solver tries to first find opportunities earlier in time to place the task;

failing that, it schedules supplies later to ensure capacity feasibility.

When looking earlier, the solver makes decisions based on the available and alternate resources

and routings, and selects the resource and routings that cause the least change in the backward

direction to the parent task’s start time. For example, if the solver has the choice to schedule a

task on the primary resource two days earlier, on the alternate resource one day earlier, or on the

alternate routing with a primary resource one hour earlier, the solver selects the alternate routing.



When scheduling tasks later for capacity, the solver tries to keep the highest-weighted priority

items in a bucket when it determines which tasks remain in a resource bucket and which ones are

moved. The Feasible Planning Solver uses the following rules to determine which buckets to

repair:

• Buckets that are under capacity are skipped unless other tasks are moved into them from

previous periods and they are pushed over capacity.

• Resources that are set to ignore capacity violations aren’t repaired.

• Frozen, complete, or canceled tasks are never moved using the capacity-feasible option. Tasks

that are components of frozen tasks in the pegged chain aren’t moved later in time because this

would create a material shortage.

After the solver defines movable tasks in an aggregate capacity bucket, it moves the tasks based

on how the resource is allocated. The resource allocation determines whether the task consumes

the resource at the start of the task, at the finish of the task, or in proportion to the fraction of the

task that overlaps the bucket. The solver uses the following process to move tasks:

• It first looks at resources that can be repaired. These are the ones that are not selected to Ignore

Violations.

• Then it determines which resource to repair in conjunction with the first bucket with a

violation.

• Next, the solver selects which tasks that are assigned to the resource in that bucket to move.

� It first tries to move all the movable tasks and their component chains earlier in priority order.

� If this doesn’t repair the capacity bucket, it then moves the remaining candidates to later

buckets using advanced algorithms based on the bucket allocation strategy, the task

priorities, and the quantity of capacity consumed by the task.

When the solver tries to repair aggregate resources, By Unit implies that the task consumes

multiple resource units over units of time. By Time indicates that only a certain amount of time

can be consumed using that bucket's resource. A Yes indicates that the solver tries to fix the

bucket. A No indicates that it ignores the bucket.

CapacityMeasurement

ResourceAllocation

ResourceAllocation

ResourceAllocation

Start Finish Proportional

By Unit Yes Yes Yes

By Time No No Yes

Buckets for resources that you select to Ignore Capacity violations aren’t repaired, regardless

of the resource allocation or resource bucket size.



The next sections describe how the Capacity Feasible Solver moves tasks later using the Start,

Finish, and Proportional allocation strategies.

Using Resource Allocation at Start or Finish (by Unit Only)

The resource allocation method tries to fit the highest sum of weighted priorities into the bucket.

The goal is to get the most product value into the bucket. In this case, value is determined by the

weighted priority, but it is tempered by the size of the task.

Using Proportional Allocation (by Unit or Time)

Using the proportional resource allocation method, tasks might consume resources in several

buckets. The goal of the method is to move lowest-weighted priority tasks first, proceeding until

either the bucket is repaired or the solver has attempted to move all tasks out of the bucket. Itorders tasks one at a time until the bucket’s capacity is filled.

To move tasks, the proportional resource allocation method uses the following steps:

1. By priority, with higher values (999) moving first.

2. By lateness tolerances, where late tasks aren’t moved.

3. By absolute lateness, where the number of days determines what is moved.

4. By tasks with the latest start time.

Determining Weighted Priorities for Capacity Planning

This section describes how the system uses weighted priorities and how weighting interacts with

different resource allocation methods. The Feasible Planning Solver uses weighting and lateness

tolerances to determine which tasks to move.

The demand priority is the placing of importance on independent demand. The lateness tolerance

represents how sensitive your enterprise is to not meeting demand requirements that fall within

the specified priority range. Lateness tolerance data is a table of priorities and a tolerance that

indicate the lateness you are willing to tolerate for that priority of top-level demand. The pegged

chain links the independent demand to tasks associated with dependent demand.

You can set a demand priority from 1 to 999, with 1 as the most important level. Using the

demand priority numerical value, you can then assign a number of days as the lateness tolerance

level your enterprise determines to be acceptable for tasks to fulfill the demand. The following is

an example of how the two values are combined.

A top-level demand with a priority lessthan or equal to:

Is considered tolerably late as long as itslateness tolerance doesn’t exceed thisnumber of days:

19 1

29 2

59 4



A top-level demand with a priority lessthan or equal to:

Is considered tolerably late as long as itslateness tolerance doesn’t exceed thisnumber of days:

69 5

99 7

199 14

999 20

When weighted priorities are the same, you usually keep high-priority late tasks in a bucket and

move lower-priority tasks that aren’t as late.

Use the Demand Prioritization option to define prioritization rules and the demand priority.

PeopleSoft Production Planning priorities are set at the business-unit level. This provides more

flexibility to PeopleSoft Production Planning in modeling production runs for different business

units.

Computing Lateness, Lateness Tolerance, and Relative Lateness

Lateness is the amount of time top-level demand is delayed beyond the demand due date. This

measurement isn’t used directly to compute the weighted priority, but it is used to determine the

independent demand's lateness tolerance and the relative lateness.

The lateness tolerance is computed from the tolerances you define and indicates the relative

importance of task priority groups. If the independent demand's lateness is on or beyond this

tolerance, the independent demand is given a higher weighting.

Relative lateness is a scaled, absolute measure of the lateness of a task. The scale is from 1 to

100. For example, if the worst lateness of a task in a bucket is 5 days, then for all tasks in the

bucket, 5 days becomes a relative lateness of 100. If a task is 4 days late, the system assigns it a

relative lateness of 80. If a task isn’t late, the system assigns it a relative lateness of 0. If a task is

2 days late (using the calculation 100 x (2/5) = 40), the system sets the relative lateness value at

40. The system uses the formula to break ties when tasks have equal priority and have the samestatus relative to intolerably late settings.

Weighted Priority

The weighted priority is a number that is a mix between the task priority, the lateness tolerance

data, and the relative lateness of a task. The lateness tolerance data is part of the environment and

is related to the priority of the task. The Planning engine uses the following formula to determine

the most important tasks:

wt = (1000 - pt )*10000 + yt *(1000)+ ((lt / l*)*100)

The following values are a part of the formula:

t Task.

lt Lateness of task t. This is actually the amount of time past

the tolerably late limit for a task.



l* Maximum of all lateness values.

pt Priority of task t: 999 for unimportant, 0 for frozen.

wt Weighted priority for task t.

yt Zero if the task isn’t late or is tolerably late, and 1 if the

task is on or beyond the lateness tolerance.

The formula works as follows:

• The weighted priority is a 7-digit number.

• The first three digits represent the relative demand priority of the task. This value ranges from

1 to 999.

• The fourth digit can be 0 or 1. It is set to 1 if the task is at or beyond its lateness tolerance.

• The three right-most digits (the fifth, sixth, and seventh digits) represent the lateness relative to

other late tasks. The maximum lateness value for a task is 100. Tasks that aren’t late are equal

to 0.

Improving Plan Quality

The Lateness and Stock Adjustment Phases help you increase the quality of the material- and

capacity-feasible plan.

Using the Lateness Phase, the solver looks for all possible ways to source end items and to reduce

their overall lateness. It does an exhaustive search for gaps in capacity, substitutes, and alternaterouting options (including production with different BOMs) defined in the model.

The repair first searches on late independent demands in priority order, working on intolerably

late orders first. These demands include transfer, forecasts, and sales orders. The search tries to

get the demand on time, or as close as possible to the due date. If it cannot make the demand ontime, it reduces the lateness of the order as much as possible.

The Lateness Phase potentially creates and deletes multiple orders. It shouldn’t be used if

you are trying to minimize “nervous” behavior in the plan.

The Stock Adjustment Phase tries to reduce temporary excess by scheduling supplies just in time

for their demands. In addition, it tries to restore any missed safety-stock periods by scheduling

late any demands that are a lower priority than safety stock.

To reduce nervousness in this phase, you can set the resolution in the Planning server’s Main

Environment. The Stock Adjustment Phase checks this value and won’t reschedule to reduce

excess or repair safety stock if the distance of the move is less than the resolution.



Checking Effectivities

If you don’t interrupt the Feasible Planning Solver, and the selected options have finished

processing, the system checks to see that all the planned production in the system is placed in aneffective time range.

If a planned task exists outside an effective range, the solver deletes it and the demand is sourced

again with effective options. Any new sourced tasks are made material- and, optionally,

capacity-feasible according to the current solver settings.

Overview of the LP Solver

Linear programming provides a global view of the supply chain problem. The solver models the

planning constraints into a system of linear inequalities and then solves this linearly relaxed

system to obtain an optimal solution. Whereas the solution contains global and optimal

information of the problem, it is a linear estimation, containing little task-specific information.

To address this, the solver automatically runs a post processor that provides a real, task-basedsolution for planning.

The post processor is based on logic and procedures that build a task-level schedule from

aggregate solutions, such as sourcing, equipment selection, and general timing. The aggregate

solution is converted into a task-specific plan on a detailed timeline. This makes it possible forthe features of the LP Solver to work with the other solvers.

The LP Solver modeling process extracts basic supply chain information from the Planning

engine data structures and generates an aggregated supply chain model in linear programming

form. Typical LP objective functions might include; penalties for violations, such as low

inventory or late delivery, minimized cost, and maximized profit. Objective functions are real-

valued mathematical functions that are optimized. These objective functions try to maximize or

minimize a particular objective.

The LP Solver’s global perspective is especially important in PeopleSoft Production and

Enterprise Planning and can also prove helpful in single-facility planning when there are

numerous production alternatives competing for shared resources.

The Feasible Planning Solver and LP Solver complement each other. You use the LP Solver to

generate an initial plan when there are more complex trade-off decisions in the supply chain

network. These decisions might include sourcing decisions, alternate resources use, part

substitution, or allocations. When you have a large amount of data, the LP Solver gives you a

more balanced starting point after which you can use the Feasible Planning Solver to obtain more

detailed solutions.

The LP Solver doesn’t ensure a material- or capacity-feasible plan. You can use LP Solver

solutions to run the Feasible Planning Solver to obtain a viable plan.

When you use the LP Solver, an automated procedure extracts all necessary information from

existing planning data structures and constructs an appropriate LP model of the supply chain.You have various controls over the construction of the LP model, that include:



• Specifying the number of days, weeks, and months to use in breaking up the planning horizon

into discrete periods.

• Defining standard lot sizes, by item or globally, used in calibrating the average activities

modeled in the LP.

• Providing a number of weighting factors that determine how a monetary unit of cost or profit is

traded off against a violation of constraints, such as stock levels, delivery milestones, and

equipment capacity.

In modeling the supply chain, linear programming simplifies and stylizes real-world operations in

the following ways:

• The LP Solver uses algebraic relations to represent conditions that would be called constraints

or objectives in planning. These relations must be expressed in terms of weighted sums of

variables representing levels of production and distribution activity.

• LP Solver decision variables can take on any value. Activity levels don’t need to correspond to

specific discrete lot sizes. The post processor restores the actual lot sizes during its processing.

• For any activity, the consumption of resources and the production of output are proportional to

the level of activity. For any resource or material, total usage or production is the sum of the

usage/production of all activities.

• In linear programming, time is typically represented as a sequence of discrete time intervals

with durations considerably longer than one second. Computational burden limits the number

of time intervals that can be included in a model. Depending on the time horizon and the

number of items, units, and options in the supply chain, a practical time interval could be, at

best, a day and may have to be as long as a week or a month.

• An LP Solver model of many facilities and options doesn’t explicitly represent individual

tasks. Rather, the LP Solver solves for average rates of production or shipment over each

modeled time interval.

• In return for these approximations, an LP Solver model permits a global view of the supply

chain over a finite time horizon. It explicitly considers differences in production technology

and resources among units and further recognizes the limitations in the distribution network.

With the big picture in mind, the LP model globally sources production and distribution among

units and over time to make the best use of available resources.

Enforcing Constraints

LP Solver supply chain modeling considers and enforces the following major categories of

constraints:



Material/Inventory Balance If you view supply chain planning as a model to describe

the physical movement of goods, this category of

constraints basically says that in each time period at each

physical location, the goods that go in minus the goods

that go out should equal the accumulation at that location.

The constraints also enforce boundaries on safety and

excess stock.

Resource Capacity The main challenge facing planners is to allocate

resources effectively throughout the enterprise in given

situations such as demand from forecast. It is

fundamentally important to enterprise planners to be able

to produce a plan that is feasible with respect to the

existing resources.

Meet Top-Level Demand Meets sales order, supply, and demand transfer types, and

forecasts demands with or without back-order penalties.

Item Substitution The supplies of the alternate items should meet the

demands of the primary item.

Planning Features Processed by the LP Solver

When you use the LP Solver, you need to set up only a limited number of additional parameters

that determine planning periods and various objective function configurations. Most of the

functions the solver uses aren’t visible to you, but determine the results of your plan. This sectiondescribes PeopleSoft product features that the LP Solver considers during processing.

Objective Function Configurations

The LP Solver finds an optimal aggregate plan with respect to a specified objective function

subject to resource constraints. You can configure the objective function through the LP

parameter settings. For instance, the solver finds a plan with minimum sales order lateness if you

set the carrying cost to zero, or it can solve for a plan to minimize inventory carrying cost if you

set a high carrying cost factor and a low lateness penalty factor.

Item Substitution

The LP Solver uses item substitutions on existing orders for which the task status and the Remap

flag allow substitutions. In post processing, any substitutions made by the solver remain intact.

Substitution choices are based on overall cost. If the priority sequence defined for the item isn’t

by cost, then the solver can decide to create a new supply for a substitute rather than for the

primary item. The solver doesn’t model substitutions on transfers, sales orders, or forecasts.

Use-Up Components

The LP model doesn’t include any purchase or production variables that supply an item in periods

after the item’s phase-out date. When it uses production options with co-products, the solver uses

the latest phase-out date across all co-products. If the date occurs within a planning period, then

the solver enables supplies for the period if most of the period is legal.



In the LP model, the safety-stock level is reduced to zero after the phase-out date. If the solver

finds late arriving demand for a phased-out item, it stockpiles supplies to satisfy the demand. It

does so if the cost of stockpiling is less than the cost of substituting and less than the penalty for

leaving the demand unsatisfied.

Alternate BOM and Routings

This makes it possible for the LP Solver to look for the most cost-effective routing for a

production option. You have to define the production option for valid combinations of BOM and

routing.

Co-Products and By-Products

The LP Solver models co-products and by-products but doesn’t make a distinction between the

two. It reflects the appropriate credits and debits for recycle and waste by-products. If the

disposal of a by-product isn’t explicitly modeled in the supply chain, the costs of the production

variables in the solver are increased to include the disposal charge based on output quantity and

the standard cost of the by-product. If the reuse of by-products isn’t explicitly modeled in the

supply chain, the costs of the production variables in the solver are decreased to reflect a recycle

credit.

If the supply chain explicitly models the reuse of by-products, a recycle credit is automatically

recognized by the solver through the avoided cost of additional supplies of the item. However, if

the supply of the recycled by-product can only be partially reused, the solver uses artificial

variables to absorb the supply and creates a cost credit for the excess supply. The cost credits

derive from the standard costs of the by-product.

Multiple Effective Ranges on Production Options

Production options are included in the LP supply chain when the option is available for use in

planned production orders. The LP Solver allows for multiple, intermittent effective ranges on a

production option. The solver calculates an effective range for each alternative mode of aproduction operation, such as a combination of equipment choices and component substitutes.

The effective range for a production mode is the intersection of the current range and the effective

range or ranges for the production option itself. If an effective range for a production option ends

within a solver period, then the period includes only production variables for the effective option

if most of the period is effective.

Variable Capacity Over Time

The solver queries the resource history to determine available capacity over the LP Solver period.

Forecast Fulfillment

The LP Solver uses the forecast fulfillment process to manage forecasted demand over a period of

time. The process makes it possible for the solver to divide the total forecast demand into

portions so that you can meet certain portions of the forecast if the total forecast cannot be met

entirely. The solver can either meet the supply shortage during the same planning bucket in

which the shortage occurs or carry it over into the next bucket.

The LP Solver tries to fulfill forecasts and moves the forecast if it’s not feasible. Using post

processing, it identifies unfixable problems in the plan induced by planning issues such as



unmovable tasks and negative on-hand inventory. Post processing sizes and schedules forecast

shipment tasks consistent with the sourcing and timing of the aggregate forecast shipments in the

solver solution, producing a feasible and task-oriented plan.

Minimize Inventory Without Excess Stock Constraints

When reasonable default storage costs are provided for inventory storage, the LP Solver

automatically minimizes inventory carryover by item. You use post processing and other solvers

to review a plan and try to reduce excess inventory and work in progress. The solver’s solution

may contain excess inventory if it is cost-effective or is unavoidable. Tasks created by postprocessing can deliver their supply early if it’s part of the solver’s solution.

Partial-Order Sourcing

The LP Solver models aggregate levels of production and transfers. It allows partial sourcing at

the aggregate level. For the most part, the solver uses only a single aggregate source for an itemin a given solver time period.

As aggregate supplies are turned into individual tasks, some demands may receive partial

sourcing, such as when one aggregate supply becomes exhausted and the sourcing moves to

another aggregate supply. For an item with multiple aggregate sources used in the solver solution

in a solver time period, splitting orders should happen to only one demand for each aggregate

source used.

Firmed-Planned Order

The LP Solver tries to reschedule or cancel an existing order according to its task status and flags.

It cannot move frozen tasks.

Supply and Demand Transfer Types

Supply and demand transfers, also called one-sided transfers, are planned for existing interunit

transfers where the LP Solver processes the transfer item for only a single location, reducing the

time it takes for the Planning engine to run distribution and master plans. During the processing,

the solver doesn’t process data, such as bills and routings, associated with the item from either the

shipping or receiving location.

The solver uses the transfer type value to determine how to model a transfer item. A transfer type

is a transfer option attribute that determines which business unit to use to model the transfer of

the item. You can model an item in the To Unit, From Unit, or both business units.

Overview of Iterative Repair/Optimizer

The PeopleSoft Production Planning Iterative Repair/Optimizer Solver generates schedules and

plans that are material- and capacity-feasible. You control the Optimizer by specifying what is

important in the schedule using weights of constraints you set up with the Control Panel in the

Planning server. The Optimizer is also exception-driven. It only tries to fix the problems. This

enables the plan to remain somewhat static instead of having to be recreated for each planning

session.



The Optimizer resolves problems either by adding or rescheduling tasks. Tasks are actions in

your PeopleSoft Production Planning model that create demand or provide supply. Tasks include

purchase order deliveries, forecasts, sales orders, subassembly production, final assembly, and

customer shipments. You can run Iterative Repair Solver by itself or as part of the overall

planning process. Iterative Repair doesn’t use pegged chains or demand priorities. Although it’s

not recommended, you can run Iterative Repair as the initial phase of the Feasible Planning

Solver.

During each of its phases, the Optimizer runs a series of iterations and repairs a series of

violations. After you run an iteration, the Optimizer scores the schedule and determines whether

to continue working on that iteration. The process of scoring constraints enables Iterative Repair

to recognize which constraints are violated as well as the order in which the violated constraints

should be repaired.

PeopleSoft Production Planning provides an optimal solution by solving multi-objective

problems. It also provides a simple way, through the Control Panel, to modify objectives that

match individual and dynamic preferences. The Iterative Repair method examines potential

schedules and chooses among them based on their fitness to multi-objective criteria. When it

reaches a point where it has a schedule that is as good as any that can be distinguished, such as a

zero score, it presents that schedule as an optimal schedule. Among Iterative Repair/Optimizer

features are the following:

• A single integrated solution simultaneously addresses material and capacity feasibility.

• A mix of business objectives, such as sales order performance and changeovers, drives the

optimal solution.

• Incrementally targeting of problems for quick response rather than requiring an MRP

regeneration. This approach is exception-based and based on net-change data.

You initialize an optimization session by loading your command files and setting the Planning

server Control Panel constraints to the desired weights. By setting the weights for the Control

Panel constraints, you identify and rank the restrictions to consider in PeopleSoft ProductionPlanning optimization calculations.

For more information about loading input files into a Planning server, see Setting Up

Command File and Source File Information.

Using the Production DataLink to Create a Master or Material Plan

Using the following set of steps, you can perform the planning requirements for extracting

planning data from PeopleTools, copying the data to a Planning server, loading the server, andreceiving planning messages.

To use the Production DataLink to create a master or material plan, complete the following steps:

1. Make sure item, inventory, and demand planning data from other PeopleSoft applications is

ready for use.



2. Create a Planning server template and define a Process Scheduler Server. The template is a

one-time setup that you can use again and again. The Scheduler server is needed in order to

run the job.

3. Start the Process Scheduler server.

4. Start a Planning server. Make sure it’s the same one that you defined in the server template.

5. Set up the Production DataLink to create the planning model that you want to use to create

your plans. This includes defining which Planning engine solvers you want to process the

plan.

6. Create a Run Control ID to use to process the DataLink run.

7. Use command files to define a valid directory for storing the planning command files.

8. Run the Production DataLink job, noting the process instance that defines the job.

9. Review the Production DataLink job, using the Process Monitor to verify that the run was

successful.

10. After the job finishes, use available tools such as workbenches, scorecards, reports, and

planning messages to work with the plan. The Advanced Planning Client can also be used to

work with the plan.

11. Use the Generate Plan option to rerun the solvers until your enterprise requirements are

satisfied within the constraints of the plan.

12. Commit the plan by approving and applying planning messages.

Setting Up Run Types, Plan Types, Time Fences, and WIP/RollForward Options

The General page provides a way to define a number of parameters that control how the

Production DataLink processes data in your master plan or material plan. Using the page, you

can add or change the following parameters:

• Run Types define whether the Production DataLink run completely refreshes data in the

Planning engine or refreshes only transactional data created or changed since the last time you

ran a plan using the Production DataLink. Transactional data includes sales, transfer,production, and purchase orders, and quantity on hand.

• Currency code and rate define a single currency for the DataLink run when you have multiple

currencies.

• Plan types indicate how you want to plan with this DataLink setup.

• Previous master-plan information indicates when the last plan was run.

• Time fences establish the appropriate start and end fences of the planning horizon as well as

fences that control the planning process.



• Order modifiers verify that the schedule enforces order quantities that fit the minimum,

maximum, multiple, and yield order modifier rules.

• Start-of-time purge removes all of the old planning data that is based on a previous start-time

fence you set during a previous planning session.

• Regenerated sourcing templates replace existing sourcing templates.

• Search depth defines how many levels of the supply chain the Planning engine explodes while

solving sourcing and optimization issues.

• Inventory options define carrying cost rates and available balances and enable you to include or

omit inventory that isn’t in an Open status.

• Capacity options define whether you use work centers only, or all resources for capacity

planning purposes.

Defining General Time Fence Information

Usage Use the General: General page to access information about the

Production DataLink. This is the default page, and you use it to add or

change a number of PeopleSoft Production Planning parameters for the



Navigation Plan Production, Process Production Plan, Process, Production

DataLink, General, General

Access

Requirements


Process

Name

PLPPCL, PLPPCTL, PL_LOAD, PLS1000, PLS9000

Process Type SQR, PSJOB, Application Engine



Production DataLink - General: General page


PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID, Report Manager, and

Process Monitor.

Enter the business Unit for which you want to run the process. This is the inventory business unit

that links to your manufacturing business unit.

The Model ID is an identifier that you create to maintain this specific Production DataLink setup.

In add mode, it defaults to the run control ID. PeopleSoft Production Planning uses this model ID

when you’re ready to transfer the plan back into your PeopleSoft transaction system. The system

uses this along with the version identifier as the filename for the file that it creates during the

export process. For example, if you defined PLAN for the control ID and a version of v1, the

export file created during the export process is named v1_PLAN_export.sql.

Run Type

Select a Run Type from the following options:

Regenerative This run type completely refreshes data in the Planning

engine with input from the PeopleSoft database. Restart

the Planning server to clear all data from previous sessions

before refreshing it with regenerative plan data.



Net Change This run type refreshes only planning data created or

changed since the last time you ran a master plan using the

Production DataLink. PeopleSoft Production Planning

applies net-change data to a session already running on the

Planning server. The net-change function applies to only

new items, forecasts, transfer orders, material stock

requests, production orders, production schedules, planned

production, purchase orders, and sales orders. PeopleSoft

Production Planning doesn’t use net change for other

static data such as bills, routings, and calendars.

Plan Type

Use the Plan Type to indicate how you want to plan with this DataLink setup. The following

values are available:

Simulation Plan A plan you use only to perform “what-if” simulations.

You can send a simulation plan back to the PeopleSoft

database only for reporting, not for execution.

Master Plan A plan you intend to execute by returning data to the

transactional system, for example to create orders and

reschedule orders. Running the master plan resets all net-

change data.

Plan Currency

If you want the Planning system to calculate cost values in a single currency when multiple

currency values are valid, use the Plan Currency group box. Use the box to define a single

currency code and currency rate type that you want the Production DataLink to use when it

creates the data model that will be loaded into the Planning engine.

Use the Currency Code field to define the single, common currency that you want the Planning

engine to use to model all costs. All the currency codes you set up using Define General Options

appear in the drop-down list. Use the Rate Type field to define the exchange rate the system

uses to convert costs from other currencies to the single currency code that you selected. You use

the fields if you are transferring stock from a business unit that uses a different currency from the

receiving unit.

The Production DataLink converts cost information that has been set up for the business unit in

terms of the values you specify in the box. For example, if you are transferring stock from

Mexican pesos to Canadian dollars, you can select to convert those values to a single base

currency, such as U.S. dollars. In doing so, you work with only a single base representation of

costs in your planning model.

The currency code and the exchange rate type aren’t sent to the Planning engine. The values

that the DataLink computes for the currency exchange appear in the Cost columns for

transfers, production, and purchase options. You access the option panels in the Planning

engine using the Modeling Options menu in the Data Browser.



Previous Master Plan

The Previous Master Plan group box displays the last Date and Time that the master plan was

run. If the Processed check box is selected, the master plan was run and the planning messages

resulting from that run were received into the PeopleSoft database using the Receive PlanningMessages process.

For more information about production plan processing, see “Committing the Production

Plan”.

Fences

In this group box, you can establish the appropriate start and end fences for the planning horizon

as well as set other time fences that control the planning process. Enter all time fences in

calendar days with respect to the current date.

Start Fence This is the beginning time boundary; no time exists before

this fence. PeopleSoft Production Planning doesn’t

recognize any orders or changes before this date. After

the planning session starts, you can’t change this start

fence. Its value will usually be a negative number because

PeopleSoft Production Planning needs to capture past-due

activity. For example, if you use a value of -30,

PeopleSoft Production Planning loads all orders with due

dates up to 30 days or earlier than today’s date.

There may be a large time span between the time a sales order shipment is originally

requested and the time a product is actually shipped. Make sure that the Start Fence you

specify is early enough to include all of the past due sales orders for the demand that you

specify in the plan.

End Fence This is the concluding time boundary; no time exists after

this fence. PeopleSoft Production Planning doesn’t

recognize any orders or changes after this date. Make sure

to define the end fence so that it is equal to or greater than

the longest lead-time of any item in your system.

Purchase Fence The date when the system considers all past due purchase

order deliveries available. For example, if you use a

purchase fence value of 0, PeopleSoft Production Planning

recognizes any past due open purchase order deliveries

available on today’s date. You usually set the purchase

order fence between the early fence and late fence.

However, this setting depends on your company’s

particular scheduling practices.



Capacity Fence The number of days after which the capacity for all

resources is no longer considered when you generate a

capacity-feasible plan.

Early Fence The beginning of the interval within which the Planning

engine operates on the schedule. You usually set the early

fence to the current date. However, if you want the

Planning engine to act on past due orders, you can set the

early fence to a negative number. This enables the system

to recognize any late orders or missed promise dates that

occur between the start date and the current date. It is

recommended that the early fence be set to at least one

day later than the start fence.

Late Fence The end of the interval within which the Planning engine

operates on the schedule. The combination of early fence

and late fence identifies the period for which the Planning

engine will plan new supply or reschedule existing tasks.

Level Fence The earliest time that the leveling constraint classes take

effect. You use this fence when you generate an

executable schedule.

Order Modifiers, Start of Time Purge, Regenerate Sourcing Templates, and SearchDepth

Select the Use Order Modifiers check box to verify that the schedule enforces order quantities

that fit the minimum, maximum, multiple, and yield order modifier rules.

Select the Start Of Time Purge Option check box if you want to purge all of the old planning

data that is based on a previous start time fence set during a previous planning session. For

example, if you originally set the start time fence as 1/1/01, and you went back later and reset

your start time fence to 2/1/01, PeopleSoft Production Planning will disregard all planning databefore 2/1/01 if this check box is selected. This is mostly used for net-change run types.

Select the Regenerate Sourcing Templates check box if you want the DataLink run to replace

existing sourcing templates. Sourcing is the process the Planning engine uses to determine how

the supply for an item’s demand is going to be filled. The system sources demand using sourcing

options. These options define parameters for manufacturing, purchasing, or transferring an item

to meet demand. You use sourcing templates to load the options. You can let the system load the

options automatically or set up sourcing templates manually and maintain the options.

Important! If you select the Regenerate Sourcing Templates check box, the system

deletes and refreshes any sourcing options for which you have established priorities and

defaults. The new templates will be prioritized based on low costs. To prevent the

regeneration of templates that you want to maintain manually, use the Sourcing Template

Maintenance page to select the Manually Maintained check box on the template header.

Use the Search Depth field to define how many levels of the supply chain the Planning engine

will explode while solving sourcing and optimization issues. Each routine option represents a



single level in the supply chain. For example, part A is made up of part B and part B is made up

of parts C and D. To explode all levels, enter a 3 in the Search Depth field. The search depth

you define is used as the default for DataLink processing.

If an item has a different value defined for its sourcing template, the Planning engine uses

the value at the item level and ignores the DataLink default search depth value you enter

here.

Inventory Options

Indicate a Carrying Cost Rate (%/year), which is the rate you use to calculate the carrying cost

of inventory on hand. The value that appears in the field is a percentage of the annual cost to

keep the item in inventory. This rate could include costs such as building overhead as well as the

cost of capital for items such as an interest rate or breakage.

Select Available Inventory Balances to transfer inventory balances for each item to PeopleSoft

Production Planning. This also includes staged quantities. If you leave this check box clear,

items will have no on-hand beginning quantities in the planning system.

Depending upon how you defined available quantity in PeopleSoft Inventory, this group box

displays either the Incl Non-Open in Avail Qty (include non-open in available quantity) or

Remove Non-Open in Avail Qty (remove non-open in available quantity) check box.

In PeopleSoft Inventory, there are four inventory statuses: Open, On Hold, Rejected, and

Restricted. You have the option, at the business-unit level, to include or not include On Hold and

Restricted (non-open) in the available quantity bucket. PeopleSoft Production Planning never

includes Rejected. The Include/Remove Non-Open in Avail Qty (include/remove non-open in

available quantity) check box enables you to reverse that option either to include or to removethose quantities for a particular run.

• When the Include Non-Open in Avail Qty (include non-open in available quantity) check box

is displayed, select the check box to include non-open inventory at the business-unit level. For

planning purposes, the system increases the quantity on hand by the On Hold and Restrictedamounts.

• When the Remove Non-Open in Avail Qty (remove non-open in available quantity) check

box is displayed, select the check box to exclude non-open inventory at the business-unit level.

For planning purposes, the system reduces the quantity on hand.

For more information about setting up these options, see PeopleSoft 8.00.01 Inventory

PeopleBook, “Preparing to Implement PeopleSoft Inventory” or PeopleSoft 8.00.01Inventory PeopleBook, “Defining Your Operational Structure in PeopleSoft Inventory”.

Capacity Options

Plan Work Centers Only defines work centers (not machines, crews, or tools) as resources. The

planning system will measure capacity on the work center as a whole and ignore the availability

of individual machines, crews, and tools used to accomplish tasks at the work centers.



Plan Detail Resources includes all resources, work centers, machines, crews, and tools in the

plan. When you select this option, the Planning system evaluates capacity for each resource.

Defining Frozen Fence Offsets

Usage Use the General: Frozen Details page to define frozen fence offsets.

You can set frozen time fences in days for several types of supply.



DataLink, General, Frozen Details

Access

Requirements

Click the Frozen Details link on the General page.

Process

Name



Production DataLink - General: Frozen Details page



Process Monitor.

A frozen fence specifies the number of days from the current date during which you don’t want

solvers or Iterative Repair to change that supply type in the current plan.

Frozen Fence Offsets (in days)

Enter a number of days in the following fence fields you want to use:



Shipment Task Fence Freezes all shipments to customers. Note that PeopleSoft

Production Planning cannot move shipments during the

plan generation process unless you use this fence.

Firm Production Fence Freezes all planned or existing production IDs and

production schedules with a production status of Firm.

Released Production Fence Freezes all existing production IDs and production

schedules with a production status of Released or InProcess.

Purchase Fence Freezes all purchase orders regardless of status.

Transfer Supply Fence The Transfer Supply Fence freezes all transfers from the

shipping business unit after the number of days you enter.

A transfer type is a transfer option flag that determines

which business unit the Planning engine uses to model the

transfer of the item. You can model an item in the To

Unit (Supply Transfer), From Unit (Demand Transfer), or

both (Both) business units.

Transfer Demand Fence The Transfer Demand Fence freezes all transfers to the

destination business unit after the number of days you

enter. A transfer type is a transfer option that determines

which business unit the Planning engine uses to model the

transfer of the item. You can model an item in the To

Unit (Supply Transfer), From Unit (Demand Transfer), or

both (Both) business units.

Freeze Master Items Select this check box to freeze master-planning items.

When you run the Production DataLink, the system

considers supply and demand for the items as frozen.

Defining WIP/Roll Forward Details

Usage Use the General: Wip/Roll Forward Details page if you want to reduce

time between operations, minimize work in process (WIP) inventory,

and indicate if you want to roll past-due tasks forward to a future time in

the plan or to a future plan.



DataLink, General, WIP/Roll Forward Details

Access

Requirements

Click the Wip/Roll Forward Details link on the General page.

Process

Name





Production DataLink - General: Wip/Roll Forward Details page



Process Monitor.

Work In Process

If you want to minimize work in process inventory, select the Minimize WIP (minimize work inprogress) check box.

If you do not select the Minimize WIP check box, the other fields on this page aren’t

available for input.

Indicate the maximum amount of time you want to allow between operation sequences in the

Distance Threshold edit boxes. You can set the maximum amount of time by Seconds,

Minutes, Hours, or Days.

Specify the maximum Number Of Routings To Repair. If the number of routings being

optimized by the Planning engine exceeds the number you define here, the system ignores them.

If minimizing WIP is one of your most relevant constraints, make sure that you set this number

high enough to handle all of the routings you might handle during a planning session.

Indicate the Constraint Relevancy for minimizing WIP. Select one of the following options:

Relevant Repair Enterprise Planning tries to repair the task to minimize

WIP.

Relevant Score Enterprise Planning records the violations but does not

repair them.

None Enterprise Planning does not repair or track the violations.

Select the Aggressive Repair check box if you want PeopleSoft Production Planning to fix the

violation regardless of whether the repair violates other constraints.



Roll Forward

Select the Roll Forward Active Phases check box if you want to reschedule tasks that are past

due. You use the Roll Forward utility to move the tasks within the current plan or to a future plan

when you run the solvers. Past-due tasks are tasks that were scheduled to be completed prior to

the current time but that remain open. The Planning engine moves tasks from the past and rolls

them forward into the current or a future schedule or plan. Then, you can view and work with

them before running solvers to fine-tune the plan.

A Roll Forward phase is a set of specifications that determine which tasks are rescheduled and

when they are rescheduled. Any phase that is marked as active is included in the movement.

You define active phases using the Planning engine.

For more information about setting up and using Roll Forward phases, see “Setting Up

Production Planning”.

Including Demand and Supply in the Production DataLink Run

You can use the Demand page to specify the types of demand that you want to include in the

Production DataLink run. You can also specify forecast consumption options for both finished

products as well as assembled components. Forecasts entered for inventory items through

PeopleSoft Inventory and products through PeopleSoft Order Management are passed toplanning, where forecast consumption is performed.

Use the Supply page to specify the types of supply you want to include in the Production

DataLink run.

Defining Demand Options

Usage Use the Demand/Supply: Demand page to specify the types of demand,

such as orders and forecasts that you want to include in the Production

DataLink run.



DataLink, Demand/Supply, Demand

Access

Requirements

Select the Demand/Supply tab, then click the Demand link on the

Demand/Supply page.

Process

Name





Production DataLink - Demand/Supply: Demand page



Process Monitor.

Select the Apply Demand Priorities check box if you want solvers to use demand priorities for

scheduling supply to meet the demand. The demand priority places importance on independent

demand. The solvers use the demand priority value to determine the order in which you fulfill the

demand. You can set a demand priority from 1 to 999, with 1 as the most important level. A

priority value of 0 is reserved for the system.

Orders

There are a variety of demand types or orders in PeopleSoft Production Planning. You can

include any of the following in your Production DataLink run: Sales Orders, Transfer Orders,

Planned Transfer Orders, Material Stock Requests, and Quotes.

If you consider sales quotes when you generate your plan, you can specify the Quote Acceptance

Percentage, or the minimum success percentage that you’ll accept as demand as defined on each

sales quotation header. For example, suppose the quote acceptance percentage is 80. There are

1500 sales quotations currently active in PeopleSoft Order Management, 350 of which have a

success percentage of 80% or better. The system considers the 350 quotations as demand but the

sales quotations under 80% won’t be considered because they are less than the quote acceptance

percentage

If you don’t specify a percentage here, such as 0%, PeopleSoft Production Planning automatically

considers that 100% of the quotes will be converted to sales orders.

Forecasts

Select the Forecast check box to include one of your predefined forecast sets.

Select a Planning Bucket Size - Daily, Weekly, or Monthly - to indicate the size of bucketed

time periods you can use for forecasting. We recommend that you use weekly or monthly

buckets, because the forecast is only consumed by sales orders within the same bucket. The

Forecast Set is used to keep multiple copies of forecasts in the system.



Use the Forecast Fulfillment Fence field to indicate the number of days from the start date that

the Planning engine uses as the forecast fulfillment time fence. When a forecasted demand

occurs within (before) the time fence and cannot be met entirely, the forecast tasks representing

portions of the forecast that cannot be met are canceled.

If the forecasted demand that occurs past the time fence (a future time) cannot be met entirely, the

forecast tasks representing portions of the forecast that cannot be met are delayed and rolled

forward to future planning buckets where they can be satisfied. Solvers determine how many

forecast tasks can be satisfied and where to reschedule the unfulfilled forecast tasks. If you donot enter a value in this field, the default is the early fence date.

Forecast fulfillment is the process that the Planning engine uses to manage forecasted demand

over a period of time. The forecast fulfillment feature makes it possible for you to divide the total

forecast demand into portions so that you can meet certain portions of the forecast if the total

forecast cannot be met entirely. The Planning engine can either meet the supply shortage during

the same planning bucket in which the shortage occurs or carry it over into the next bucket.

Solvers delay and cancel forecast tasks based on how the forecast is loaded and on the period start

and end time. If you select the Front Load option, the forecast is front loaded and produces

demand at the beginning of the planning period, so that the supply must be available at the

beginning of the period. If you select the Back Load option, the forecast produces demand at the

end of the planning period, so that supply can be scheduled during the planning period. Front

Load is the default option. To clear it, select the Back Load option.

When forecasted demand cannot be supplied, the solvers look at forecast tasks and how their

forecasts were loaded to determine if forecast tasks are late. When a task is late, the solvers

determine if the task should be delayed or canceled.

Forecast Consumption

Forecast consumption options enable you to control the forecast consumption calculations

performed while loading the planning command files. Use the following options to define how

forecasts should be used when the Production DataLink is run:

Select the Allow Forecast Consumption check box to indicate that you want PeopleSoft

Production Planning to consume the forecast.

If you don’t select Allow Forecast Consumption, you can’t select the Explode Demand

for Consumption option or any forecast consumption method.

When you select the Net Change Forecast check box, all actions that trigger a change in the

forecast consumption equation, such as changing a sales order line quantity, also trigger the

forecast consumption process. If you don’t clear this check box, changes aren’t made to forecast

consumption, and you’ll have to use the Regenerate Forecast Consumption option to update the

forecast tasks.

Select the Stock Request Shipments check box to include these shipments in forecast

consumption.

If you select the Explode Demand for Consumption check box, sales order demand or transfer

demand for forecast consumption will be exploded at the global level. If there were forecasts for



production, you would want to explode sales order demand or transfer demand for some end

items by calculating the production demand to be used for forecast consumption. You should not

select this check box if forecasts exist only for sales order demand or transfer demand.

To explode demand for forecast consumption, complete the following steps:

1. Take the sales order and determine the bucket to which you add the transfer or production

demand based on the promise or request date.

2. Use the default item sourcing option as the primary way to source the item.

� For a purchase option, stop the explosion, since it is at the end.

� For a transfer option, take the source item and add the quantity to the transfer demand

bucket.

� For a production option, look at each component of the BOM and calculate the quantity

before adding to the production demand bucket. The formula to calculate the quantity isQPA * quantity of the sales order line.

3. For a transfer option, take the source item and repeat Step 2. For a production option, take

each component and repeat Step 2.

Select the Sales Order Shipments check box if you want sales order shipments to consume

forecast.

Select the Transfer Demand Shipments check box if you want transfer demand shipments to

consume forecast. Using PeopleSoft Production Planning, the shipped transfers consume

forecast, even if they have not been received.

Select Promise Date when you want the plan to consume the forecast based on the sales order

ship set promise date. The Production DataLink uses the promise date on the sales orders to

determine which forecast to consume by the sales order demand. Promise Date is the default.

Because the Material Planning Solver reschedules the sales orders scheduled shipments based on

the promise date before the netting of demand and supply begins, you may want to set the

forecast consumption method to Promise Date. You must select either Promise Date orRequest Date, but not both.

Select Request Date if you want to use the sales order ship set request date to determine which

forecast will be consumed by the sales order demand. You must select either Promise Date or

Request Date, but not both.

For more information on entering forecasts for inventory items, see “Setting Up Production

Planning”.

For more information on entering forecasts for products, see “Setting Up Production

Planning”.



Defining Supply Options.

Usage Use the Demand/Supply: Supply page to specify the types of supply

such as orders and forecasts that you want to include in the Production

DataLink run.



DataLink, Demand/Supply, Supply

Access

Requirements

Select the Demand/Supply tab, then click the Supply link on the

Demand/Supply page.

Process

Name



Production DataLink - Demand/Supply: Supply page



Process Monitor.

Supply Options

You can include any of the following in your Production DataLink run: Purchase Orders,

Planned Purchase Orders, Production Orders (including production IDs and production

schedules), Planned Production Orders, Transfer Orders, and Planned Transfer Orders.

Usually, you’ll want to include all these options when running a regenerative DataLink. When

you run a net-change process using the Production DataLink, you might have a separate run

control to pull net-change data for different types of supply and demand. For example, a net-

change run control can be set up to pull production data over at the end of each shift.



Period of Supply (POS) Histogram Period

Select a scale to view the inventory histograms as measured in period of supply (POS). Your

options are Daily and Weekly. The supply is the total new supply, which comes from scheduled

and planned production, purchase, and transfer. You can calculate the POS at each supply pointand at each demand occurrence.

Select the Round Component Demand check box if you want to round the quantity when the

system calculates dependent component demand. You can determine at the business-unit level

whether to round the component based on the item-rounding rule. The Production DataLink

passes the rounding rule and quantity precision with the item to the Planning engine. However,

you can’t change the item rounding rule and quantity precision within PeopleSoft Production

Planning.

Whether the number is a whole number or a decimal may depend on the item’s unit of measureand quantity precision combination as it was defined in Inventory.

For more information about defining rounding rules and quantity precision for items, see

PeopleSoft 8.00.01 Application Fundamentals for FSCM PeopleBook, “Working With

Items”.

You have the option to round or not round depending on demand calculations. You may

decide not to round the dependent demand calculation because rounding inflates the actual

dependent demand. Rounding problems become more visible as the dependent demand

explodes down more levels.

For more information about exceptions to the rounding rules, see PeopleSoft 8.00.01Application Fundamentals for FSCM PeopleBook, “Working With Items”.

Select one of the Substitute Options where substitute items are assigned to the business unit:

Off Planning performs no item substitutions or use-up

functions.

Active If an item’s requirement isn’t being met, another supply

for the item will be rescheduled before an alternate item is

substituted.

Aggressive If an item’s requirement isn’t being met, an alternate item

is substituted before other supply for the item is

rescheduled. The alternate item with the highest priority

is substituted first. If, for example, there is insufficient

inventory of the highest priority alternate item, the next

highest priority alternate item with sufficient quantity will

be substituted.



When the Planning system is using Linear Programming (LP) mode, substitute items and

thus the replacement items aren’t selected based on highest priority, but are instead selected

based on lowest cost. To ensure correct planning of the replacement item, delete all

substitute items in the substitute item list and leave only the replacement item when in LP

mode.

Substitute Options settings apply to manufacturing only and aren’t used for inventory

transfers or shipping.

Setting Planning Run and Solver Options

Solvers are flexible tools that analyze data and attempt to find a feasible master or material plan.

Using solvers, you first produce a plan based on existing supply and demand for an item to arrive

at a feasible material and capacity plan. You then can intervene to manually repair infeasibilities

and run other more comprehensive solvers that provide a plan that is ready to use when it’s

generated.

For more information about using solver options, see Setting Up Solvers Using the


Selecting a Solver for Plan Generation

Usage Use the Solvers: Common page to define which solver you want to run

when you generate the master or material plan.



DataLink, Solvers, Common

Access

Requirements

Select the Solvers tab, then click the Common link on the Solvers page.

Process

Name





Production DataLink - Solvers: Common page



Process Monitor.

When you set up the Production DataLink, you define which solvers you want to use to process

the plan when you load the data model into the Planning server. The Planning engine runs thesolvers based on the controls you define in this component group.

The solver you select on this page runs the initial master or material plan. Using other pages in

this component, you can indicate that another solver should run immediately after the one you

select on this page.

You can use the Generate Plan option to immediately run a plan. We recommend that you

create initial material and feasible plans using the Production DataLink, then use the

Generate Plan option to run solvers again or to run quality improvement phases for the plan.

Common

Select one of the following Run Solver after Load options:

Feasibility Solver Provides a more complete plan that ensures material and

resource capacity is available to meet the plan.

Iterative Repair Run the Iterative Repair Solver after you create a plan

using the LP, Material, or Feasible Planning solvers. The

Iterative Repair Solver produces plans that show violated

constraints as well as the order in which the violated

constraints should be repaired.

Linear Programming This solver is especially designed to work with reasonably

large data sets. The solver doesn’t ensure a material- or

capacity-feasible plan. You can use LP Solver solutions

to feed into the Feasible Planning Solver to obtain a

feasible plan.

Material Solver Provides a simple plan that resolves material shortages.

You can select to have some capacity repaired during the

processing of material shortages. This solver provides

you with a starting point for a plan.



You can also select to run another solver automatically after you run the initial plan. Use the

solver pages in this component group to indicate whether you want to run another solver

without intervening in the Production DataLink processing.

For more information about each solver, see Setting Up Solvers Using the Production

DataLink.

Defining Material Planning Options

Usage Use the Solvers: Material Planning page to define conditions for

processing a master or material plan. The Material Planning Solver

creates a simple material plan that resolves most material shortages.



DataLink, Solvers, Material Planning

Access

Requirements

Select the Solvers tab, then click the Material Planning link on the

Solvers page.

Process

Name



Production DataLink - Solvers: Material Planning page



Process Monitor.



For more information about material planning, see Overview of the Material Planning

Solver.

Planning Mode

This group box provides options for defining the data that Production DataLink uses when the

material plan is created. The default value is Regenerative. The following values are available:

Regenerative When you run the Material Planning Solver in this mode,

all tasks or orders with a status of planned are deleted

from existing data and a material plan is generated for all

inventory items. Using this mode, all previous supply and

demand relationships (recorded in the pegging) are erased

and all independent demand is rescheduled back to its due

date.







When a supply is late for a demand but is pegged, it isn’t considered a material shortage.

When a part is planned for again in the Net Change mode, all planned supplies are deleted

and any end-demands for that part are returned to their due date. In addition, all pegging

history for that part is deleted. All other parts remain unchanged.


rescheduled to satisfy supply. You can eliminate these shortages by running the Feasible

Planning Solver or using the Late Supplies Inquiry in the Planning server to fix them.

After Material Planning Run

Before you run the Production DataLink, you need to define whether you want to consolidate

planned purchase orders (POs) or run the Feasible Planning Solver after the material planning

run. Select the Consolidate Planned Purchase Orders check box to invoke the purchase order

consolidation algorithm automatically after the solver run. This consolidation is the same as

Fixed Period, except that it acts on purchases only. The default value for the box is clear (notselected).

Select the Run Feasible Planning check box if you want to the Feasible Planning Solver to runautomatically immediately after the Material Planning Solver runs.



Material Planning - General Attributes

The Material Planning Solver uses the following information to process a material-feasible plan.

Select the Calculate Low Level Code check box to verify the accuracy of low-level codes. The

code is a number that identifies the lowest level in a BOM at which a component appears. These

codes are maintained on items and calculated by the Planning engine. When this check box is

selected, the low-level code for each item is calculated prior to the Material Planning run.

Since the Material Planning Solver plans items in low-level code order, it is important to

ensure that the low-level code associated with each item is accurate before you run the

Material Planning Solver, especially if there have been BOM changes.

Select the Ignore Safety Stock check box to indicate whether you want the Material Planning

Solver to plan for meeting safety-stock levels. When this option is selected, the solver ignores

safety-stock constraints. As a result, the solver won’t plan supply for safety-stock demand. Youcan use this option for “what-if” scenarios.

When you select Include Capacity for the planning run, the Material Planning Solver minimizes

capacity violations between the early fence and capacity fence when it generates the plan. This

capacity repair tries to reschedule tasks earlier to find capacity. The solver doesn’t violate the

pegged chain record of supply and demand to reschedule the tasks, nor does it place tasks before

the early fence to reschedule the tasks. As the default, the box is clear.

The Include Capacity option isn’t the same as the Make Plan Capacity Feasible option in the

Feasible Planning Solver. The Material Planning Solver repairs capacity levels by rescheduling

tasks earlier on the primary resource, regardless of creating late supplies. In doing so, it doesn’t

guarantee material feasibility. By contrast, the Feasible Planning Solver moves the tasks earlier,

searches for alternate resources, and finally moves the tasks later without ever creating late

supplies.

We recommend that you use this repair only when you have a plan that isn’t heavily capacity

constrained. In all other cases, you should use the Feasible Planning Solver to resolve

capacity overages.

Select the Use Fixed Period check box to define whether the fixed period of supply algorithm is

applied during the Material Planning run. When a planned production or purchase order needs to

be created after all existing orders have been used, the Material Planning Solver uses this option

to determine the maximum amount needed between the first demand and a fixed-period amount

of time. The time is defined as a number of days on the item record. The solver creates a single

supply for this amount. The default for this check box is clear.

Select the Material Plan Items check box to include material-planning items in the solver

processing. You can run a plan that includes both material- and master-planning items. Select

the Master Plan Items check box to include any items in solver processing that have been

selected as master-planning items. These values are assigned using the Planned By option on theBusiness Unit Item Definition page.



Defining Feasible Planning Solver Options

Usage Use the Solvers: Feasibility Solver page to define the planning elements

that you want to include in material and capacity feasibility planning.

You can use the Feasible Planning Solver to create a master or material

plan.



DataLink, General, General,

Access

Requirements

Select the Solvers tab, then click the Feasibility Solver link on the

Solvers page.

Process

Name



Production DataLink - Solvers: Feasibility Solver page



Process Monitor.


between the early fence and end of time and is designed to start from any initial plan and turn it

into an executable plan. The solver generates an executable plan that contains no tasks in the

past, no material shortages, and, optionally, no capacity violations. The solver guarantees

material feasibility for all resolvable material violations between the early fence and end time,

regardless of the settings.

For more information about how the Feasible Planning Solver processes a plan, see

Overview of the Feasible Planning Solver.



Feasibility Solver

Select the Ignore Safety Stock check box to indicate you do not want the system to respect

safety-stock constraints during the processing of the Feasibility Planning Solver. As a result, the

solver doesn’t plan supply for safety-stock demand. If supply was created for safety stock by an

earlier solver, the Feasible Planning Solver recognizes it as excess. As the default, the box is

clear, so that safety-stock levels are accounted for in the planning process.

Select the Allow Material Reallocation check box to allow the Feasible Planning Solver to

correct material inversions by reallocating supply. These inversions occur when a supply task is

late for the demand that it supplies. When you allow material allocation, the solver tries to

reallocate supply from a lower-priority pegged chain before trying to reschedule the demand later

or the supply earlier.

Select the Allow Rescheduling check box to control the rescheduling of tasks to resolve late

supplies by the Feasible Planning Solver. The pegged chains are rescheduled only after the

Feasible Planning Solver searches for any allowed alternate sources of supply.

If the Allow Rescheduling check box isn’t selected, only the material phase of the Feasible

Planning Solver runs and the solver cannot ensure a material-feasible plan.

You must select Allow Rescheduling in order to use the Make Plan Capacity Feasible and

phase options in plan processing.

The Feasible Planning Solver uses the move preference that you define in the Planning server’s

Late Supplies Inquiry to decide if the demand should be made late or the supply should be

rescheduled before the early fence to resolve any remaining late demands. In case of frozen

demand, the supply is scheduled earlier if the demand cannot be made on time. In all other cases,the default behavior schedules the demand later.

Select the Make Plan Capacity Feasible check box to indicate that you want the Feasible

Planning Solver to resolve capacity violations between the early fence and capacity fence. When

the box is clear, the Feasible Planning Solver considers only material feasibility, not capacityfeasibility, when you run the plan.

The Make Plan Capacity Feasible option in the Feasible Planning Solver isn’t the same as the

Include Capacity option in the Material Planning Solver. The Material Planning Solver repairs

capacity level by rescheduling tasks earlier on the primary resource regardless of creating late

supplies. In doing so, it doesn’t guarantee material feasibility. By contrast, the Feasible Planning

Solver moves the tasks earlier, then searches for alternate resources, and finally moves the task

later without ever creating late supplies.

The Feasible Planning Solver resolves aggregate resource violations, not detailed resource

violations.

For more information about how the Feasible Planning Solver processes a plan to make it

capacity-feasible, see Making the Plan Capacity Feasible.



Select the Allow Alternate Routing check box to allow the Feasible Planning Solver to source

material again to resolve material infeasibilities. When you allow alternate routings, the solver

tries to explode the supply for a violated demand again, using either alternate purchase or transfer

options. The Feasible Planning Solver tries to use alternate purchases or transfers to resolve a

material infeasibility before it tries to reschedule the demand or supply. Enabling alternate

routings also controls if alternate routings are used when the Make Plan Capacity Feasible and

Run Lateness Phase check boxes are selected.

Select the Allow Item Substitution check box to indicate that the Feasible Planning Solver can

use substitute items to correct material inversions. When you select this option, the solver tries to

reallocate the supply of a valid substitute item from a lower-priority pegged chain before it tries

to reschedule the demand or supply. Item substitution is used if it helps make a late supply on

time, and if it helps during all reschedules to reduce excess inventory. If the box is clear,

substitutions are not made during solver processing. For example, the Run Lateness Phase

won’t use item substitution.

If you select the Run Lateness Phase check box, the Lateness Phase of the Feasible Planning

Solver executes after a material- or capacity-feasible plan is in place. This phase maintains the

feasibility of the schedule while searching for opportunities to reduce the lateness of demands that

have been delayed past their due date. As the default, the box is clear. This phase adds quality to

your plan.

If you select the Run Lateness Phase check box, you must also select the Allow

Rescheduling check box.

Use the Time Limit field to define the maximum number of minutes the Lateness Phase is run.

When the Planning engine reaches the limit you set, it stops processing and provides you with a

plan up to the point that it stopped. The default value for this field is 60 minutes. You cannot

enter a negative number.

Run Lateness Phase potentially creates and deletes multiple orders. You should not use it if

you want to change the existing schedule minimally.

Select the Ignore problems later than check box to indicate that you want to limit the scope of

the Lateness Phase by entering a smaller time period. If this option isn’t selected, the system

considers all late demands between the early fence and end of time in this phase. As the default,

the box is clear.

You use the days after Current Time field to indicate how long after the current time the solver

should begin to ignore the Lateness Phase. The system considers this field if you have selected

the Ignore problems later than check box. The value of this field represents a number of days

after current time. This offset from current time defines a boundary after which late demands are

ignored by the Lateness Phase. An attempt isn’t made to reduce the lateness of demands that start

outside this boundary. The default value for the field is 30 days.

The Run Stock Adjustment Phase check box maintains the feasibility of the schedule while

searching for opportunities to reduce excess inventory that occurs between the early fence andend of time. It also searches for opportunities to satisfy unfulfilled safety-stock requirements.



The Stock Adjustment Phase check box causes numerous reschedules and should not be

selected if you want to change the existing schedule minimally.

If the Run Stock Adjustment Phase check box is selected, the Planning engine invokes this

feature when you run the Feasible Planning Solver after a material- or capacity-feasible plan is in

place. As the default, the box is clear.

If you select the Run Lateness Phase check box, the Feasible Planning Solver executes the

Run Stock Adjustment Phase after the Lateness Phase.

Use the Time Limit field to enter the maximum number of minutes you want the Run Stock

Adjustment Phase to run. When the solver reaches the limit you set, it stops processing and

provides you a plan up to the point that it stopped. The default value for this field is 60 minutes.

You cannot enter negative numbers.


the Stock Reduction Phase by entering a smaller time period. If this check box isn’t selected,

excess inventory and unfulfilled safety stock that exists between the early fence and end of time

are considered in this phase. As the default, the check box is clear.

When you type a value in the days after Current Time field, the solver doesn’t attempt to

reduce excess inventory or fulfill safety-stock requirements outside the time periods. The defaultvalue for this field is 30 days.

This field is considered if the Ignore problems later than check box is selected. The value of

this field represents a number of days after the current time. This offset from current time defines

a boundary after which excess inventory and unfulfilled safety-stock requirements are ignored bythe Stock Reduction Phase.

For more information about the Lateness and Stock Adjustment Phases, see Improving Plan

Quality.

Defining Linear Programming Options

Usage Use the Solvers: LP Solver page to define the parameters that you want

linear programming to apply to the master or material plan.



DataLink, Solvers, LP Solver

Access

Requirements

Select the Solvers tab, then click the LP Solver link on the Solvers page.



Process

Name



Production DataLink - Solvers: LP Solver page



Process Monitor.

When you have complex sourcing decisions to make or when you want a plan that considers your

business objectives in a global sense, then you should use the LP Solver. Through its realistic

modeling, this solver enables you to include factors in planning that other solvers cannot process

or do not process to the extent that the LP Solver does. Effective dates, calendars, and penalty

calculations are examples of extended modeling.

The LP Solver uses an aggregate approach to consider different objectives, factors, and

alternatives simultaneously to develop a plan with the minimum cost. The solver first constructs

an LP model based on the settings you define on the LP page, and then it finds an aggregate

optimal planning solution. Finally, the LP post-processor takes the aggregate solution and creates

a task-based executable plan.

The LP Solver doesn’t ensure a material- or capacity-feasible executable plan. If you want

to take the task-based solution produced from the LP post-processor and turn it into a

feasible and executable plan, run the Feasible Planning Solver after you run the LP Solver.

For more information about how the LP Solver processes a master or material plan, see

Overview of the LP Solver.

Linear programming works best for period planning or planning by week, not for detailed

planning. It is particularly effective for sourcing decisions.



LP Solver

Select the Modify LP Parameters (modify linear programming parameters) check box if you

want to change options for how the solver creates your plan.

If you do not select the Modify LP Parameters check box, the other fields on this page

won’t be available for input.

You can use the default values that appear on this page or enter new values. These values specify

your aggregate bucketed data and enable the linear programming process to provide greaterprecision.

Use the Carrying Cost Rate (%/year) field to define the annual percentage rate the solver uses

to calculate the cost of maintaining the inventory. The cost is based on a percentage of the

average inventory value for the year. The default value for the field is 10 percent if values have

not been defined using PeopleSoft Enterprise or Production Planning. You cannot change the

value.

Use the Late Shipment Penalty (%/day) field to define the percentage it costs your business on

a daily basis to miss a shipment date. The percentage is based on the standard cost of the item.The default value for this field is 0.1%; however, you can change the value for an LP Solver run.

The Number of Daily Periods represents the total daily periods from the early fence that you

want to include in the plan. The default value for this field is 7. The smaller the number of

periods you plan for, the more realistic you make your plan.

The Number of Weekly Periods represents the total weekly periods following daily periods that

you want to include in your plan. The default value for this field is 4. You can use this field to

plan implicitly for monthly buckets as well. When the late fence exceeds the last weekly period,

then the LP Solver uses monthly buckets for the rest of the periods.

We recommend that you do not enter more than 30 total periods so that the LP Solver can

find optimal plans for large-scale problems. The total is the sum of daily and weekly

periods.

Select the Run Feasible Planning After LP check box to automatically invoke the Feasible

Planning Solver after the LP Solver is run.

Defining Iterative Repair Settings

Usage Use the Solvers: Iterative Repair page to select parameters for using the

Iterative Repair/Optimizer to run a master or material plan. Iterative

Repair scores the schedule and determines whether to continue working

on an iteration. The process of scoring constraints enables Iterative

Repair to recognize which constraints are violated, as well as the order

in which the violated constraints should be repaired.





DataLink, General, General

Access

Requirements

Select the Solvers tab, then click the Iterative Repair link on the Solvers

page.

Process

Name



Production DataLink - Solvers: Iterative Repair page



Process Monitor.

Iterative Repair is the most extensive tool available for creating a master plan or material plan.

Also called the Optimizer, Iterative Repair is an advanced planning tool for creating a plan or

detailed schedule. Iterative Repair performs a series of iterations. During iterations, it applies a

set of standard repair rules (heuristics) to the constraint violations. Each constraint class has a

series of standard repairs that the system follows. If these repairs do not meet your needs, thenyou can modify the repair.

You can run Iterative Repair by itself or as part of the overall planning process. Iterative Repair

doesn’t use pegged chains or demand priorities. Although we do not recommend it, you can run

Iterative Repair as the initial phase of the Feasible Planning Solver.

During each of its phases, Iterative Repair runs a series of iterations and repairs a series of

violations. After you run an iteration, Iterative Repair scores the schedule and determines

whether to continue working on that iteration. The process of scoring constraints enables

Iterative Repair to recognize which constraints are violated, as well as the order in which the

violated constraints should be repaired.



For more information about the Iterative Repair tool, see Overview of Iterative

Repair/Optimizer.

Iterative Repair

Select the default Optimization Template that you want to use to load into the planning model.

When you run the Production DataLink and select a template, PeopleSoft Production Planning

automatically creates the appropriate planning model. Standard optimization templates include:

All Constraints This is the default template. It enables you to build a

planning model and generate a plan based on all the

constraints that you select when you create your plan.

Material & Aggregate

Capacity

In PeopleSoft Production Planning, this template is

identical to the All Constraints template. It enables you to

build a planning model and generate a plan based on all

the constraints that you select when you create your plan.

In PeopleSoft Enterprise Planning, this template enables

you to build a planning model and generate a plan without

changeover or detailed capacity.

Material Only Selecting this template enables you to build a planning

model and generate a plan without taking capacity into

consideration.

The Min. Stock Violation (hrs) (minimum stock violation in hours) field defines the minimum

number of hours that PeopleSoft Production Planning considers to be a stock violation. For

example, you can accumulate excess inventory that causes a temporary surge in inventory when

you build an item. If you set the minimum violation to three hours, then a temporary surge of two

hours during a build process won’t cause a violation.

Select the Iterations for optimizer field to define the number of times, or iterations, you wantthe Planning engine to search for an optimal schedule.

Depending on the size of your model, Iterative Repair may take a substantial amount of time to

create a schedule. You set optimization stopping rules before running the repair. The

optimization stopping rules cause Iterative Repair to stop and return the best schedule or thecurrent schedule upon termination.

In the Stop optimizer after minutes field, you can enter a time limit to indicate the number of

minutes you want the Planning engine to search for an optimal schedule. Use the Stop

optimizing at this score field to enter an acceptable score at which the Planning engine shouldterminate its search.



Setting Up Command File and Source File Information

Usage Use the Command Files page to view the command files used by the

Production DataLink for a Planning server template. You can edit the

file names on this page. All command files are created for each

DataLink.



DataLink, Command Files

Access

Requirements


Process

Name



Production DataLink - Command Files page (1 of 2)



Production DataLink - Command Files page (2 of 2)



Process Monitor, and Schedule.

There are two File Name columns. The first column contains fields you can edit and controls the

name given to the command file created by the Production DataLink. The second column is for

display only and lists the type of information the Production DataLink includes in the file,

regardless of the name in the first column, during processing.

Important! Don’t leave any of the field values blank if you override the current names in

the first column.

The file names, as currently configured, include the following:

File Name Includes

Environment Data for your PeopleSoft Production

Planning environment, which includes time

fence, solver, attribute, date penalty, linear

programming, PeopleSoft Order Promising

(if installed), lateness tolerance, and forecast

consumption data. The system label in the

right column is always Env.

Attributes Data for your planning attributes. The

system label in the right column is always

Attributes.

Calendars Data for your work period, holiday, calendar

spec, and work calendars. The system label

in the right column is always Calendars.

Items Data of the items for which you will be

planning. The system label in the right

column is always Items.

Resources Data for your rough-cut planning resources.

The system label in the right column is

always Resources.



File Name Includes

Production Options Data for the bills of material and routing

definitions you use to manufacture items.


always Prdn Opts (production options).

Planning BOMs Data for your planning bills of material. The

system label in the right column is always

Pln BOMs (planning bills of material).

Sourcing Data for your sourcing templates and

sourcing options. The system label in the

right column is always Sourcing.

Procurement Data for your existing purchase orders, as

well as any unapplied new purchase orders

from a previous planning run. The system

label in the right column is always PO

(purchase orders).

Productions Data for your existing production IDs and

production schedules, as well as any

unapplied new production messages from a

previous planning run. The system label in

the right column is always Prdn

(production).

Transfers Data for your existing transfer orders, as well

as any unapplied new transfer order messages

from a previous planning run. The system

label in the right column is always

Transfers.

Forecasts Data for your forecasts. The system label in

the right column is always Forecasts.

Sales Orders Data for your sales orders and sales quotes.


always Sales.

Stock Requests Data for your existing material stock

requests. The system label in the right

column is always MSR.

Inventory Balances Data for your quantity-on-hand inventory

balances. The system label in the right

column is always QOH (quantity on hand).

Line Schedule Editor Data for the line schedule editor. The system

label in the right column is always LSE.



File Name Includes

User Defined Data that you might have defined in other

parts of the system to use in the Production

DataLink process. The system label in the

right column is always User.

Load Data for loading all the generated command

files. By loading this one command file, all

other command files are automatically loaded

into the Planning engine. The system label in

the right column is always Load.

Generate Plan Data for running a specific solver after all

other data is loaded into the Planning engine.


always Gen plan.

In the Write DataLink Output To field, indicate the network path where you want the command

files to be created. The network path must end with a back slash (\) for Windows NT or a

forward slash (/) for UNIX.

Because you control the name of the command files and the network path to which they are

written, you should consider how the files are named and the location to which they should

be written. If you are running the Production DataLink for multiple business units, make

sure that the command files aren’t overwriting themselves. You should create a strategy to

identify command files by name (such as the business unit name in the file name) or by

network path, for example, a unique network path for each business unit, such as:

\\<server>\scp80\data\<business unit>.

Click Run to run this request. Process Scheduler runs the Production DataLink process at user-

defined intervals.


Verifying Planning Server Connection Settings

Usage Use the Planning Server page to change Planning server templates.

These templates enable you automatically to transfer the transaction data

and plan parameters directly to the Planning engine to generate and

analyze your plan.



DataLink, Planning Server



Prerequisites To make Planning server templates available, you need to use General

Options to create a template and set up its parameters. You use the

Planning Server Definition page to create permanent server templates.

You can define a template only temporarily by using the Planning

Server page.

Access

Requirements


Process

Name



Production DataLink - Planning Server page

You can temporarily change which host machine or database you are linked to. For example, you

might have established a test database or a different set of data that you work with. Using this

page, you can change among your host machines without navigating to the Define Business Rules

option, where you also define server settings. To access the latter page, use the following link:

Planning Server Definition page.

You use Planning server templates to define how and where the Supply Chain Planning server is

installed and runs. The Planning server definition enables you automatically to transfer the

transaction data and planning parameters directly to the Planning engine to generate, analyze, and

maintain your planning data model.

These templates make it easy for you to change which Planning server you are linked to. For

example, you might have a test model established on one server and a production model defined

on another machine and server. You can also establish logical definitions of Planning servers for

use by PeopleSoft Enterprise Planning, Production Planning, and Order Promising. As you work

with your plans, you select a server by only its template name rather than having to establish allthe technical Planning server information each time you use a plan.



You can link to a server either by using the Planning Server group box to select the server or by

completing fields on this page. The Planning server is also available on the Planning Scorecard

page and can be selected directly from there.

Planning Server

When you want to change a template temporarily, the Server Template Name identifies the

template.

Host

To establish a link between PeopleTools and the Planning engine, use the Host Name field to

define the machine or device that runs the Planning server. The value you enter must represent a

valid host machine. These values aren’t established as part of your PeopleSoft application

installation or maintenance, so make sure that you type the name as it corresponds to the host

machine.

Use the Host User Name field to define a valid user on the host machine you entered. If you use

File Transfer Protocol routines to copy files to and from the Planning server and a password is

required, you need to enter that password in the Host Password field. When you type the

password, wildcard characters appear in the field instead of the password.

Select the Platform on which the Planning server is running. You can select either PSNT (for

Windows NT machines) or PSUNX for (UNIX machines).

Server

Type the Server Name to define the logical name that has been given to the Planning server.

Planning server names are established when you start a Planning server and specify the -idparameter.

If the -id parameter wasn’t specified, the default server name is “Server.” These values aren’t

established as part of your PeopleSoft application installation or administration, so make sure you

type the name as it corresponds to the host machine. Server names are case-sensitive.

The Timeout (Seconds) field defines how long you want the connection to a Planning server to

wait before automatically timing out when you retrieve or update information in the Planning

server. This means that PeopleSoft Production Planning searches this amount of time before

returning an incomplete operation message. For example, the system may have lost its

connection to the server, found no rows of data, or couldn’t connect to the server. The time isentered as a number of seconds.

The User Name defines a unique ID used to access the Planning server if the Server has been set

up to use security. Enter the Server Password established for the user name. Use the Port field

to define a valid port to use to connect to the Planning server.

Use the Load Command Files From field to define the path to the location of the data model

command files on your network file system so that the Planning server can access them. In most

cases this is a path on the host machine where the Planning server runs. If you are using a shared

file system between Process Scheduler and the Planning server, this path can be the same as the

path used during the DataLink process for creating the command files.



The Planning engine looks for the command files in the path specified here when it loads the

Planning server automatically using the Production DataLink process. The path name must end

with a forward slash (/) for Unix or a back slash (\) for Windows NT. Otherwise, the file transfer

won’t take place.

For example, a Unix path name would look like this: /data/command/

A Windows NT name would look like this: \data\command\

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L G E N E R A T I N G T H E P R O D U C T I O N P L A N 4 - 1

C H A P T E R 4


After you build and define your planning model using the Production DataLink, you can generate

a master or material plan using the Generate Plan process. Typically, the master or material plans

are automatically created as a part of the DataLink process. The Generate Plan option enables

you to rerun any of the solvers after you have made manual changes to the plan using the master

plan, material plan, or capacity plan workbenches.

The generation process overrides any values that you have set up for solvers in the Planning

server while making it possible to run a plan specifically for master- or material-planning items.

To invoke the process, you use buttons to start the solver that you want to run.

Overview of the Production Plan Process

Before you begin to generate your master plan or material plan, you need to make sure that youhave a Planning server defined and loaded for the model you will use to create the plan.

Generating your plan can be an iterative process. You can run a plan a number of times until you

have a higher-quality plan. When you define your model, PeopleSoft Production Planning passes

the data you identify as part of the planning process to the Planning engine using the Production

DataLink. If the data is incomplete, for example your forecast numbers are inaccurate or one of

the time fences isn’t set properly, we recommend that you stop your generation process and use

the transaction system to change your model or any incomplete or incorrect data

You can change plan data using the Planning engine; however, only planned orders, ordercancellations, and dates changes are transferred back to the PeopleSoft transaction system.

During processing, the system generates master and material plans using the following rules:

• Master-planning items can only be a component of another master-planning item.

• A master plan can be generated in the production-planning model for any business unit, such as

a feeder plant. Using the plan a more defined view of production can be evaluated. In this

model, production routings used in production management are passed to planning. Alternate

routings are also passed to planning providing a closer view at the capacity for a singleproduction facility.

• If the master plan has been generated using an enterprise-planning model, the master plan is

passed in as a part of the material plan in PeopleSoft Production Planning.

• Material-planning items can be components of either material- or master-planning items.


4 - 2 G E N E R A T I N G T H E P R O D U C T I O N P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

You can change plan data using the Planning engine; however, only new orders and dates

changes are transferred back to the PeopleSoft transaction system.

Before You Begin

The following are the prerequisites to generating a master or material plan:

• Verify that your forecast and on-hand inventory is accurate and that items are correctly defined

for inclusion in the planning process.

• Understand fully the solver and optimization approaches and the constraint settings you’ll be

using to take full advantage of PeopleSoft Production Planning. Constraint settings are made

in the Planning server, while you can make solver settings using either the DataLink or theGenerate option.

For more information about using the constraints, see PeopleSoft 8.00.01 AdvancedPlanning Client PeopleBook, “Managing Constraints”.

For more information about solvers and optimization, see “Setting Up the Production

DataLink”.

• A Planning server must be running.

• Make sure the command file has been generated and loaded into the Planning server.

• A Process Scheduler server must be running. When you click a solver button, the generation

process picks up any running server tied to an application engine.


When you generate a master or material plan in PeopleSoft Production Planning, you use a series

of solvers. Solvers are flexible tools that analyze data and attempt to find a feasible plan based on

your planning needs. Using solvers, you first produce a plan based on existing supply and

demand for an item to arrive at a feasible material and capacity plan. You then can intervene to

manually repair infeasibilities and run other more comprehensive solvers that provide a plan that

is ready to use when it’s generated.

For more information about the generation process, see “Setting Up the Production

DataLink”.



Running Planning Solvers

How you use solvers depends on the objectives of your master or material plan. There isn’t a

defined order for running each solver or a predefined set of rules that you must include in a solverrun. You alter the solver flow to meet specific planning needs.

Using planning solvers, you generate plans using a set of parameters for each solver. You can

run a single solver or all of them at different intervals. Using the Generate Plan option, you can

run iterations of your plan, analyzing your plan and making manual changes between iterations.

For more information about using solvers and suggestions for running them, see “Setting Up

the Production DataLink”.

Defining Global Preferences

Usage Use the Global Preferences page to review the time fences the

Production DataLink uses to create a master or material plan. The

Global Preferences page is the default page for the component group.

Object PL_GEN_GLOBAL_PREF

Navigation Plan Production, Process Production Plan, Process, Generate Plan,

Global Preferences

Prerequisites If you are going to generate a plan immediately, a Planning server and

Process server must be running.

Access

Requirements


Generate Plan - Global Preferences page

The following fields are common to multiple pages and are defined in the preface of this

PeopleBook in PeopleBooks Standard Field Definitions: User ID and Run Control ID.



Fences are points in time before or after which solvers take certain actions. Solvers use fences to

determine how far supply or demand tasks can be moved forward or backward to meet planning

needs.

Planning and scheduling problems occur within four periods of time. Time fences help define the

following types of planning periods:

• Today’s schedule that has been released to the manufacturing floor.

• Short-term scheduling on a time line with shift or daily bucket planning.

• Medium-term planning.

• Long-term planning.

Solvers are best applied to medium-term planning. This planning period typically focuses on

tactical planning issues such as meeting due dates, managing inventory levels, planning material

deliveries and resource loads, and finally making sourcing decisions. Capacity-feasible and

material-feasible planning can occur across the last two planning periods but normally occur just

within the medium-term-planning region. The planning horizon is the time between the early

time fence and the end of time, both of which you can define. The planning algorithms are

applied to only those tasks that reside within this horizon.


might have established a test database or a different set of data that you work with. Using the

Planning Server option, you can change among your host machines to select the server

containing the database that you want to use to generate the plan. You don’t have to use the

Define Business Rules option to make the change; however, only server templates that have been

defined by that option are available here. If you want to define a new server setting template, usethe Planning Server Definition page.

Click the Change Server Settings button to change the settings for a server temporarily.

For more information about using the Change Server Settings button, see “Managing the

Master and Material Plans”.

You use the following types of fences when using solvers:

Start of Time This is the beginning time boundary. Time doesn’t exist

in the Planning server before this fence. Orders and

changes aren’t recognized before this point in time. Used

with the end of time, the region defines the time period

within which the system operates. Solvers don’t

recognize times before the start of time.

Current Time This is the current date and time as seen by the Planning

server. The current date and time are static values that are

initially set by the Production DataLink process. This

fence is used to define various time offsets respected by

the planning solvers.



Early Fence This is the beginning date and time of the interval within

which the solver processes the elements of the material-

and capacity-feasible plans. You’ll usually set the early

fence to the current date.

Capacity Fence The date and time that solvers begin ignoring capacity

violations. After the date, the Material Planning, Feasible

Planning, and LP Solvers ignore violations; however, the

Optimizer doesn’t use this date to process capacity

violations. If the capacity fence intersects with an

aggregate capacity bucket, then aggregate capacity

violations are respected for the current bucket interval but

ignored for the succeeding bucket intervals.

Late Fence The LP Solver and the Optimizer use this fence as a point

to distinguish the planning horizon. They can’t schedule

tasks after this fence.

End of Time This is the concluding time boundary. Time doesn’t exist

in the Planning server after this date. Solvers and the

Optimizer don’t recognize orders or changes after this

date.

Creating a Material Plan

Usage Use the Material Planning page to set up parameters for creating a

material feasible plan. This solver creates a simple material plan for

your master- or material-planning items.

Object PL_GEN_MATERIAL_PL


Global Preferences



Access

Requirements




Generate Plan - Material Planning page


PeopleBook in PeopleBooks Standard Field Definitions: User ID and Run Control ID.

The Material Planning Solver creates a simple material plan that resolves most material shortages.

After you make your selections on this page, click the Run Material Planning button if you

want to generate a plan.


might have established a test database or work with a different set of data. Using the Planning

Server option, you can change among your host machines to select the server that contains the

database you want to use to generate the plan. You don’t have to use the Define Business Rules

option to make the change; however, only server templates that have been defined by that option

are available here. If you want to define a new server setting template, use the Planning Server

Definition page.




For more information about using the Material Planning Solver to generate a master or

material plan, see “Setting Up the Production DataLink”.

Planning Mode

This group box provides options for defining which data the Production DataLink uses when the

material plan is created. The following values are available:



Regenerative This is the default value. When you run the Material

Planning Solver in this mode, all tasks or orders with a

status of planned are deleted from existing data and a

material plan is generated for all inventory items. Using

this mode, the system erases all previous supply and

demand relationships (recorded in the pegging) and

reschedules all independent demand back to its original

due date.







When a supply is late for a demand but pegged, the system doesn’t consider it a material

shortage. When you plan for a part again in the Net Change mode, the system deletes all

planned supplies and returns any end-demands for that part to their due date. In addition, all

pegging history for that part is deleted. All other parts remain unchanged.


rescheduled to satisfy supply. You can eliminate these shortages by running the Feasible

Planning Solver or using the Late Supplies Inquiry in the Planning server to fix them.

The Material Planning Solver uses the following information to process a material feasible plan.

Select the Calculate Low Level Codes check box to verify the accuracy of low-level codes. The

code is a number that identifies the lowest level in a bill of material (BOM) at which a component

appears. The Planning engine maintains and calculates these codes for items. When you select

this check box, the system calculates the low-level code for each item prior to the MaterialPlanning run.

Because the Material Planning Solver plans items in low-level code order, it is important to

ensure that the low-level code associated with each item is accurate before you run Material

Planning, especially if there have been BOM changes.

Select the Ignore Safety Stock check box to indicate whether you want the Material Planning

Solver to plan for meeting safety-stock levels. When this check box is selected, the solver

ignores safety-stock constraints. As a result, the solver doesn’t plan supply for safety-stock

demand. You can use this option for “what if” scenarios.

When you select the Include Capacity check box, the Material Planning Solver minimizes

capacity violations between the early fence and capacity fence when it generates the plan. This

capacity repair tries to reschedule tasks earlier to find capacity. The solver doesn’t violate the

pegged chain record of supply and demand to reschedule the tasks, nor does it place tasks beforethe early fence to reschedule the tasks. As the default, this check box is clear.



The Include Capacity option isn’t the same as the Make Plan Capacity Feasible option in the

Feasible Planning Solver. The Material Planning Solver repairs capacity level by rescheduling

tasks earlier on the primary resource, regardless of whether this action creates late supplies. In

doing so, it doesn’t guarantee material feasibility; on the other hand, the Feasible Planning Solver

moves the tasks earlier, then searches for alternate resources, and finally moves the task later

without ever creating late supplies.

We recommend that you use this repair only when you have a plan that isn’t heavily

capacity-constrained. In all other cases, you should use the Feasible Planning Solver to

resolve capacity overages.

Select the Use Fixed Period check box to define whether the fixed period of supply algorithm is

applied during the Material Planning run. When you select this option and a planned production,

transfer, or purchase order needs to be created, the Material Planning Solver determines the

maximum amount needed between the first demand and a fixed-period amount of time after all

existing orders have been used. The time is defined as a number of days on the item record. The

solver creates a single supply for this amount. The default value for this check box is clear.

Select the Material Plan Items check box to include material-planning items in the solver

processing. You can run a plan that includes both material- and master-planning items. Select

the Master Plan Items check box to include any items in Material Planning Solver processing

that have been selected as master-planning items. These values are assigned using the Planned

By option on the Business Unit Item Definition page.

After Material Planning Run

Before you run the Production DataLink, you’ll need to define whether you want to consolidate

planned purchase orders (POs) or run the Feasible Planning solver after the material planning run.

Select the Consolidate Planned PO (consolidate planned purchase orders) check box to invoke

the purchase order consolidation algorithm automatically after the solver run. This consolidation

behavior is the same as fixed period, except it acts on purchases only. The time period is defined

using purchasing order modifiers on the item definition. The default value for the check box is

clear.

Select the Run Feasible Planning check box if you want to automatically run the FeasiblePlanning Solver immediately after running the Material Planning Solver.

Creating a Feasible Plan

Usage Use the Feasible Planning page to set up parameters for generating an

executable plan that contains no tasks in the past, no material shortages,

and, optionally, no capacity violations. This solver ensures a feasible

plan for your master- or material-planning items.

Object PL_GEN_FEASIBLE_PL


Feasible Planning





Access

Requirements


Generate Plan - Feasible Planning page

The following fields are common to multiple pages and are defined in the preface of thisPeopleBook in PeopleBooks Standard Field Definitions: User ID and Run Control ID.


between the early fence and the end of time. If you select the Make Plan Capacity Feasible

option, it ensures capacity feasibility as well. The solver is designed to start from any initial plan

and turn it into an executable plan. It tries to do this while making only minimal changes to the

existing plan.

When the solver is invoked, it checks any current pegging for consistency and maintains that

pegging. The only time the solver modifies the pegging is as necessary to make the plan

material- and capacity-feasible. If pegging doesn’t exist, the Feasible Planning Solver creates the

pegging based on a first-in, first-out (FIFO) basis.

After you make your selections on this page, click the Run Feasible Planning button if you want

to generate a plan immediately. PeopleTools uses the current settings in the DataLink along with

any changes you made to solvers in the Generate Plan option to run the plan.



Server option, you can change among your host machines to select the server containing the



are available here. If you want to define a new server setting template, use the Planning ServerDefinition page.



4 - 1 0 G E N E R A T I N G T H E P R O D U C T I O N P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L



For more information about using the Feasible Planning Solver to generate a master or

material plan, see “Setting Up the Production DataLink”.

Select the Allow Material Reallocation check box to enable the Feasible Planning Solver to

correct material inversions by reallocating supply in the solver’s pegged chain. These inversions

occur when a supply task is late for the demand that it supplies. When material reallocation is

enabled, the solver tries to reallocate supply from a lower-priority pegged chain before trying to

reschedule the demand later or the supply earlier.

Select the Allow Item Substitution check box to indicate the Feasible Planning Solver can use

substitute items to correct material inversions. When you select this option, the solver tries to

reallocate the supply of a valid substitute item from a lower-priority pegged chain before

attempting to reschedule the demand or supply. You use item substitution if it helps make a late

supply on time, and during all reschedules to reduce excess inventory. If the check box is clear,

no substitutions are made during solver processing. For example, the Run Lateness Phase

doesn’t use item substitution.

Select the Allow Alternate Routing check box to enable the Feasible Planning Solver to source

material again to resolve material infeasibilities. When alternate routings are selected, the solver

tries to explode the supply for a violated demand again, using either alternate purchase or transfer

options. The Feasible Planning Solver will try to use alternate purchases or transfers to resolve a

material infeasibility before attempting to reschedule the demand or supply. Selecting alternate

routings also determines whether the system uses alternate production routings when the Make

Plan Capacity Feasible and the Run Lateness Phase check boxes are selected.

Select the Ignore Safety Stock check box to indicate that you don’t want the system to respect

safety-stock constraints during the processing of the Feasibility Planning Solver. As a result, the

solver won’t plan supply for safety-stock demand. If supply was created for safety-stock by an

earlier solver, the Feasible Planning Solver will recognize it as excess. As the default, the box

isn’t selected, meaning that safety-stock levels are accounted for in the planning process.

Select the Allow Rescheduling check box to control the rescheduling of tasks to resolve late

supplies by the Feasible Planning Solver. The pegged chains are rescheduled only after the

Feasible Planning Solver searches for any allowed alternate sources of supply.

Select the Make Plan Capacity Feasible check box to indicate you want the Feasible Planning

Solver to resolve capacity violations between the early fence and capacity fence. When the box

isn’t selected, the Feasible Planning Solver considers only material feasibility, not capacity

feasibility, when you run the plan.

The Make Plan Capacity Feasible option in the Feasible Planning Solver isn’t the same as the

Include Capacity option in the Material Planning Solver. The Material Planning Solver repairs

capacity level by rescheduling tasks earlier on the primary resource regardless of whether the

action creates late supplies. In doing so, it doesn’t guarantee material feasibility; on the other


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L G E N E R A T I N G T H E P R O D U C T I O N P L A N 4 - 1 1

hand, the Feasible Planning Solver moves the tasks earlier, then searches for alternate resources,

and finally moves the task later without ever creating late supplies.

The Feasible Planning Solver resolves aggregate resource violations, not detailed resource

violations.

If you select the Run Lateness Phase check box, the Lateness phase of the Feasible Planning

Solver is executed after a material-or capacity-feasible plan is in place. This phase maintains the

feasibility of the schedule while searching for opportunities to reduce the lateness of demands that

have been delayed past their due date. As the default, the check box is clear. This phase adds

quality to your plan.

If you select the Run Lateness Phase check box, you must also select the Allow

Rescheduling check box.

Use the Time Limit (minutes) field to define the maximum number of minutes the system runs

the Lateness Phase. When the Planning engine reaches the limit you set, it stops processing and

provides you with a plan up to the point that it stopped. The default value for this field is 60

minutes. You can’t enter a negative number.

The Lateness Phase potentially creates and deletes multiple orders. You shouldn’t use it if

you want to change the existing schedule minimally.

Use the Ignore problems later than check box to indicate that you want to limit the scope of the

Lateness Phase by entering a smaller time period. If the check box is clear, all late demands

between the early fence and end of time are considered in this phase. As the default, the check

box is clear.

You use the days after Current Time field to indicate how long after the current time the solver

should begin to ignore the Lateness Phase. The system considers this field if the Ignore

problems later than check box is selected. The value of this field represents a number of days

after current time. This offset from the current time defines a boundary after which late demands

are ignored by the Lateness Phase. An attempt isn’t made to reduce the lateness of demands that

start outside this boundary. The default value for the field is 30 days.

When you select the Run Stock Adjustment Phase check box the system maintains the

feasibility of the schedule while searching for opportunities to reduce excess inventory that

occurs between the early fence and end of time. It also searches for opportunities to satisfy

unfulfilled safety-stock requirements.

The Run Stock Adjustment Phase check box causes numerous reschedules and shouldn’t

be used if you want to change the existing schedule minimally.



If the Run Stock Adjustment Phase check box is selected, the Planning engine invokes this

feature when you run the Feasible Planning Solver after a material- or capacity-feasible plan is in

place. As the default, the check box is clear.

If you select the Run Lateness Phase check box, the Feasible Planning Solver executes the

Run Stock Adjustment Phase after the Lateness Phase.

Use the Time Limit field to enter the maximum number of minutes you want the Run Stock

Adjustment Phase to run. When the solver reaches the limit you set, it stops processing and

provides you with a plan up to the point that it stopped. The default value for this field is 60

minutes. You can’t enter negative numbers.


the Stock Reduction Phase by entering a smaller time period. If the check box is clear, the system

considers excess inventory and unfulfilled safety-stock that exist between the early fence and end

of time in this phase. As the default, the check box is clear.

When you enter a value in the days after Current Time field, the solver doesn’t attempt to

reduce excess inventory or fulfill safety-stock requirements outside of the time periods. Thedefault value for this field is 30 days.

This field is considered if the Ignore problems later than check box is selected. The value of

this field represents a number of days after the current time. This offset from current time defines

a boundary after which the Stock Reduction Phase ignores excess inventory and unfulfilled

safety-stock requirements.

For more information about the Lateness and Stock Adjustment Phases, see “Setting Up the

Production DataLink”.

Generating a Plan Using Linear Programming (LP)

Usage Use the LP Planning (linear programming planning) page when you

want to model your supply chain and compute schedules that optimize a

selected objective while satisfying a set of specified constraints on

operations. The LP Solver doesn’t ensure a material- or capacity-

feasible plan. You can use LP Solver solutions to feed into the Feasible

Planning Solver to obtain a feasible plan.

Object PL_GEN_LP Component


LP Planning



Access

Requirements



P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L G E N E R A T I N G T H E P R O D U C T I O N P L A N 4 - 1 3

Generate Plan - LP Planning page

The following fields are common to multiple pages and are defined in the preface of thisPeopleBook in PeopleBooks Standard Field Definitions: User ID and Run Control ID.

Linear programming provides a global view of the supply chain problem. The LP Solver models

the planning constraints into a system of linear inequalities and then solves this linearly relaxed

system to obtain an optimal solution. While the solution contains global and optimal information

about the problem, it is a linear estimation, containing little task-specific information. To address

this, the solver automatically runs a post-processor that provides a real, task-based solution forplanning.

The post-processor is based on logic and procedures that build a task-level schedule from

aggregate solutions, such as sourcing, equipment selection, and general timing. The aggregate

solution is converted into a task-specific plan on a detailed timeline. This makes it possible for

the features of the LP Solver to work with the other solvers.

After you make your selections on this page, click the Run LP button if you want to generate a

plan immediately. PeopleTools uses the current settings in the Production DataLink along with

any changes you make to solvers in the Generate Plan option to run the plan.



Server option, you can change among your host machines to select the server containing the



are available here. If you want to define a new server setting template, use the Planning Server

Definition page.


For more information about using the Change Server Settings button, see the “Managing

the Master and Material Plans”.

Use the Carrying Cost Rate (%/year) field to define the annual percentage rate the solver uses

to calculate the cost of maintaining the inventory. The cost is based on a percentage of the

average inventory value for the year. This value is set during the Production DataLink process.



The default value for the field is 10 if values haven’t been defined using PeopleSoft Enterprise or

Production Planning. You can’t change the value using the Generate Plan page.

Use the Late Shipment Penalty (%/day) field to define the percentage it costs your business on

a daily basis to miss a shipment date. The percentage is based on the standard cost of the item.

The default value for this field is 0.1; however, you can change the value for an LP Solver run.

The Number of Daily Periods field represents the total daily periods from the early fence that

you want to include in the plan. The default value for this field is 7. The smaller the number ofperiods you plan for, the more realistic you make your plan.

The Number of Weekly Periods field represents the total weekly periods following daily periods

that you want to include in your plan. The default value for this field is 4. You can use this field

to plan implicitly for monthly buckets as well. When the late fence exceeds the last weekly

period, then the LP Solver uses monthly buckets for the rest of the periods.

We recommend that you don’t enter more than 30 total periods in order for the LP Solver to

find optimal plans for large-scale problems. The total is the sum of daily and weekly

periods.

After the LP Run

Select the Run Feasible Planning after LP check box to invoke the Feasible Planning Solver

automatically after you run the LP Solver. Use the LP Solver to generate an initial plan when

there are more complex trade-off decisions in the supply chain network. These decisions might

include sourcing decisions, alternate resources, item substitution, or material allocations based on

demand priority. This is a regenerative process where the system reschedules all independent

demands to their due date and deletes all tasks with a status of Planned. We recommend that yourun the Feasible Planning Solver after you run the LP Solver to create a plan that is feasible.

For more information about using the LP Planning Solver to generate a master or material

plan, see “Setting Up the Production DataLink”.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L M A N A G I N G T H E M A S T E R A N D M A T E R I A L P L A N S 5 - 1

C H A P T E R 5

Managing the Master and Material Plans

The master plan enables you to plan for finished goods and key component materials. You can

use the master plan to ensure that top-level material and capacity requirements have been

accounted for before exploding lower-level material and capacity requirements. With PeopleSoft

Supply Chain Planning, you can create and maintain the master plan in either Enterprise Planning

or Production Planning.

The material plan enables you to plan for subassemblies and lower-level raw material

requirements. The material plan uses the results of the master plan to determine the requirements

for meeting the master plan.

You use PeopleSoft Production Planning to create and maintain the master and material plans.

Because a Production Planning model contains both master- and material-plan items, the plans

are similar in the information they produce and display. This chapter uses the material-plan pages

to describe how you use both plans; however, differences between the two plans are noted whenthey occur.

Overview of the Master and Material Planning Process

PeopleSoft Production Planning helps you manage the planning process by dividing it into a

series of sequential and incremental processes. Each plan in the process appears as a menu item,

enabling you to analyze item data at different planning levels as it progresses through the

planning process.

The master plan is designed for use in either the PeopleSoft Production Planning or Enterprise

Planning applications. When you use it for Enterprise Planning, the plan provides you a high-

level overview of your manufacturing plan. For example, it checks that you generally have

enough capacity and material to produce the total demand. In PeopleSoft Production Planning,

the master plan provides more detailed manufacturing data. We’ll focus on the master plan’s usewith the Production Planning application.

The material plan is the second in a series of plans. It is designed to provide you a means to

manage inventory levels, schedules, and availability of selected items, either manufactured or

purchased.

PeopleSoft Production Planning creates a model for both master planning and material

planning. You can control the generation of a material plan just for master-plan items or just

for material-plan items, or you can simultaneously generate a plan considering both master-

and material-plan items.


5 - 2 M A N A G I N G T H E M A S T E R A N D M A T E R I A L P L A N S P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

PeopleSoft Demand Planning and Inventory Planning feed both the master and material plan.

Forecasts and inventory replenishment policies provide the basis that PeopleSoft Production

Planning uses to calculate its plans. Forecast quantities define the totals for both plans, while

inventory policies determine how items are planned and stocked.

A final plan in this series is the capacity plan. Data from the master and material plans feeds the

capacity plan. The capacity plan provides you an early warning about any major capacity

shortages with the current material or master plan.

For more information about the using the capacity plan, see “Managing the Capacity Plan”.

You can classify the same item differently across business units. For example, a service part

ordered on a sales order line might be defined as a distribution-plan item at a distribution

center and as a material-plan item at the plant where it is manufactured.

You can control the content and viability of master and material plans using solver controls. For

example, you can generate a plan that produces a simple plan for material but does not attempt to

solve certain types of resource capacity problems. Or, you can generate plans using several

iterations of solvers to produce plans that are material- and capacity-feasible.

After you generate a master or material plan, you can use a number of inquiries to review the

plans. You can also use the workbench to adjust your plan.

The following master and material plan inquiries are available:

Workbench You can use the Master or Material Plan Workbenches to

make changes to the plans. First, you determine which

items to work with using the respective workbenches.

From a link associated with an item, you can access the

Plan Summary page, from which you initiate changes

including production, purchase, and transfer order dates

and quantities. In addition, you can also review related

demand and supply information.

Plan Summary • The Master or Material Plan Summary provides you

with an aggregate (bucketed) view of the supply and

demand for a business unit item. You can use the

summary as part of the workbench, where you can

make changes to the plan or review information.

Details • The Master or Material Plan Detail Inquiry displays the

sequence of supply and demand over time for an item.

You use the inquiry when you want to review the time-

phased list of demand and supply for an item.



Exceptions • Use the Master or Material Plan Exceptions Inquiry to

review exceptions for individual items in a plan. An

exception is a condition that prevents the master or

material plan from being feasible. The Exceptions

Inquiry and Planning Scorecard display similar data.

The main difference is that the Exceptions Inquiry lets

you review all exceptions for an item in the same grid,

while the Scorecard provides some summary features

by exception type.

Planning Scorecard • Use the Planning Scorecard to review the efficiency of

your overall enterprise plan. It shows you constraint

violations, the number of violations, and a score for the

violations. In PeopleSoft Production Planning, a score

is the weighted sum of constraint violations in a

schedule. The score gives you an idea of how valid, or

acceptable, the schedule is.

Master Plan Process Flow

You begin the master-planning process by ensuring that items you want to include in the plan

have been set up for master planning. You can select Master Planning from the Planned By field

available options on the Planning page in the Item Attributes by Units component of PeopleSoft

Inventory. The Production DataLink plans for only those items that have a Planned By value set

to Master Planning or Material Planning.

To implement a master plan, perform the following steps:

1. After you define the business unit and classify the items for master planning, use the Plan

Production menu option to set up planning options that include item source code, time fences,

aggregate items, promise dates, and demand priorities. A master-plan item can only be a

component of another master- plan item and can only supply a master- or distribution-plan

item through a transfer.

Master plan items must have their parent items defined as Master Planning.

2. Use the Production DataLink to establish parameters for the master plan.

3. Generate the initial master plan, defining which solvers you want to run with the plan.

4. Review and make changes to the master plan. After you make changes, you can run as many

iterations of the plan that you need to achieve the most viable plan, using the workbench and

solvers to continue to improve the plan.

5. Commit the plan. For master plan items, you can select whether you want to extract planning

messages for the item.



Material Plan Process Flow

You begin the material-planning process by ensuring that items you want to include in the plan

have been set up for material planning. You can select Material Planning from the Planned By

available options on the Planning page in the Item Attributes by Units component of PeopleSoft

Inventory.

To implement a material plan, perform the following steps:

1. After you define the business unit and classify the items for material planning, use the Plan

Production menu option to set up planning options that include item source code, time fences,

aggregate items, promise dates, and demand priorities. A material-plan item can be a

component of either material- or master-planning items and can supply a master- or material-

plan item through a transfer.

2. Change the Production DataLink to establish parameters for the material plan.

3. Generate the initial material plan, defining which solvers you want to run with the plan.

4. Review and make changes to the material plan. After you make changes, you can run as

many iterations of the plan that you need to achieve the most viable plan, using the

workbench and solvers to continue to improve the plan.

5. Commit the plan. For material-plan items, you can select whether you want to extract

planning messages for the item.

For more information about preparing to create a master plan, see Before You Begin.

For more information about setting up Production Planning data, see “Setting Up Production

Planning”.

Before You Begin

There are several prerequisites to include specific items in a master or material plan. The

following lists highlights those prerequisites:

• Define if you want an item to be sourced by transfer, make, or buy during the planning process,

and set the corresponding Planned By value (Master Planning or Material Planning) within the

Item Attributes by Unit page.

• Define a Planning server using the Planning Server Definition page in the General Options

component of the Define Business Rules menu.

• Ensure a Planning server is running. Using the Production DataLink, the server processes your

plan and returns the results to PeopleSoft Production Planning pages for you to review and

change.



Maintaining Master and Material Plans

In order to effectively maintain the master plan and material plan, you need to have the ability to

view the plan details based on certain selection and filtering criteria, modify the plan as needed,

and save the plan. PeopleSoft Production Planning responds to this need by providing you with a

robust set of workbench and inquiry pages.

You use the Master and Material Plan Workbenches to view plan details based on certain

selection criteria, change plan elements as needed, and save the plan after reviewing the effects of

the changes. The workbenches display exceptions, planned actions, and planned transfers for the

replenishment of material or mater items.

After you identify an item to work with in the Master or Material Plan Workbenches, you can

drill down on the item by clicking the Item ID link from the Item tab of the Plan Summary page.

You can then perform the following tasks using workbench drill-down pages:

• Add production, purchase, and transfer orders.

• Change current task quantities and dates.

• Freeze tasks.

• Show all related supply and demand tasks.

Defining the Master or Material Workbench Search Parameters

Usage Use the Item page to retrieve and work with material- or master-plan

item data. After you access the workbench, you can link to other tools

to maintain the item.

Object Name PL_WBENCH_SRCH

Navigation Plan Production, Manage Master or Material Plan, Use, Master or

Material Plan Workbench

Prerequisites A material or master plan must have been created.

Access

Requirements

Define the Business Unit and Item ID to populate the workbench with

material- or master-plan data



Material Plan Workbench - Item page

Select a Unit from the prompt to use in the workbench. To limit the list of items, use the Item ID

field to define a specific item to work with. The Config Code (configuration code) provides a

way to define a configured item further. The Planner Code defines the person or group

responsible for an item, while the Family and Category display the production planning

classification for the item.

Use the Planned By group box to indicate if you want to include only item data for the material

plan or for the master plan or for both.




Unit Shows the business unit to which the item belongs.

Item ID Displays the unique identifier the system uses to track and

retrieve the item. The remaining data relates to this item.

If you want to see additional material- or master-plan

details for the item, double click it to access summary

information. If you don’t define a single item, then all

items in the business unit appear in the workbench.

Item tab

See the previous exhibit for a view of this tab.

Description A brief description of the material- or master-plan item

you selected to work with.

Planner Cd (planner code) Displays the person who is responsible for the item.

Planned By Displays the type of planning item: Material or Master.



Family Displays the group of products to which this item belongs.

Configuration Code tab

Viewing the Configuration Code tab

The Config Code (configuration code) provides a way to define a configured item further. The

method is based on the use of the item, such as how it’s assembled. When you click an Item ID,

the system takes you directly to the Master or Material Plan Summary page.

Using the Master or Material Plan Summary

Usage Use the Master or Material Plan Summary page to retrieve data for the

material or master plan. You can access this page through either the

Material or Master Plan Workbench.

Object Name PL_MRP_HORIZONTAL


Material Plan Workbench, Master or Material Plan Summary

Prerequisites A master or material plan must have been created.

Access

Requirements

Define the Business Unit and Item ID to populate the summary with

material- or master- plan data.

Material Plan Summary page



The Material or Master Plan Summary provides you with a horizontal aggregate (bucketed) view

of the supply and demand for a business unit item. Using the Master or Material Plan Summary,

you first define the general parameters such as the Start Date, Period Duration, Number of

Periods, and Planning Server. After you define the parameters, you use the Search button topopulate the summary.

The summary includes row types, past-due quantities, and dates that represent the period

duration. The maximum number of columns for the summary is 54: one column for the row type,

one for the past-due quantity, and 52 date columns for all the weeks in one year. To maintain

data for the plan, you select the row type on the date you want to work with. The system provides

drill-down pages and links you use to access and change data for scheduled receipts and planned

orders.

Click the Scheduled Receipts row value on the date you want to work with to performmaintenance functions.

The Unit is the business unit that contains the item for which you want to perform a Material or

Master Plan Summary. It is a required field. You also are required to select an Item ID for the

summary. To define the specific instance of a configured item you want to review, select a

Configuration Code.

The Start Date provides an exact starting time for the period of time you want to review in the

material or master plan. You can review data from the start of the plan or at different intervals in

the plan. If you do not enter a date, the default is Sunday of the current week. For example, if the

current date is Tuesday, the 10th of October, the start date that appears in the field would be

Sunday, the 8th of October.

The Period Duration defines the measurement of time for which you want to review summary

information. Valid values are Day, Week, and Month, with Week being the default value. When

you define the Number of Periods, the value is measured by the value you define for the

duration. The default value for the number of periods is 7. The number of periods you define

determines the number of tabs that appear in the summary. Each tab contains seven planningperiods.

Each time you change a value such as the period duration, item ID, or row type, you must

click the Search button to refresh the page with data from your selection.

Use the available options for the Planning Server to select a different Planning server template

name. This is the server from which you want to extract summary data.

Click the Change Server Settings button to connect to another Planning server

temporarily.

Row types appear in the summary with the following information:

Row Type This is a kind of planning data for the item. The data can

be cumulative or calculated on a period-by-period basis.

You use the Scheduled Receipts and New Planned

Orders row types to make changes to your plan. These

rows provide links to drill-down pages.



Past Due Displays any quantities that are past due on the start date.

Date These sequential dates correspond to the period duration

you define for the page. The dates can be at daily,

weekly, or monthly intervals. You select the Scheduled

Receipts and New Planned Orders row type dates to

make changes to your master or material plan.

For more information about changing row types, see Changing Row Types.

The Change Row Types button provides a means for you to add, delete, or change the display of

data for the summary. The changes you make are temporary. When you exit the workbench and

return, the system uses the default values, not the row types you changed. After you change row

types, use the Search button to refresh the list.

The following row types are available for the Master and Material Plan Summaries:

Actual Supply The scheduled receipts from existing purchase orders,

inventory transfer orders, or production orders.

The actual supply = scheduled production supply +

scheduled purchased supply + scheduled transfer supply.

Customer Orders Displays the quantity of orders generated by customers.

Dependent Demand Displays the demand quantity that occurs when the item is

required to meet demands of another transfer or

production task.

Excess Inventory The maximum amount of inventory that is allowable. The

planned inventory on hand should never exceed this

number.

Independent Demand Displays the total amount of planned production,

purchases, and transfers for this period.

New Planned Orders The sum of planned production, purchases, and transfers

for an item in a period.


5 - 1 0 M A N A G I N G T H E M A S T E R A N D M A T E R I A L P L A N S P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Periods of Supply A forward-looking calculation of a period’s planned on-

hand balance, which determines how many days into the

future that a period’s planned on-hand balance covers the

total demand. When planned on-hand quantities are not

enough to cover all of the total demand for a particular

bucket, Production Planning prorates the number of days

by the ratio of the planned on-hand quantity available over

total demand. When there isn’t enough total demand

through the periods reported, the Periods of Supply bucket

displays 99999.

Planned On Hand Displays a cumulative inventory balance from the

beginning of the planning horizon. This includes the prior

period’s ending on-hand balance plus the total supply,

minus the total demand for the current period. The total

includes planned orders as well.

Planned Production Displays the suggested production orders created for this

period when you generated the material or master plan.

Planned Purchases Displays the suggested purchase orders created for this

period when you generated the material or master plan.

Production Demand Displays the total amount of demand from production for

this time period.

Production Supply Displays the scheduled receipts from manufacturing for

this time period. The receipts are in the form of

production orders.

Projected On Hand Displays the cumulative projected inventory balance from

the beginning of the planning horizon. This includes the

prior period’s ending on-hand balance plus the total

supply, minus the total demand for the current period.

Purchase Supply The scheduled receipts from vendors for this period. The

receipts are in the form of purchase orders.

Safety Stock The minimum quantity of stock planned to always be in

inventory to protect against fluctuations in demand or

supply.

Scheduled Production The total amount of demand from production, with

statuses of Firmed, Released, Dispatched, or In-Process.

Scheduled Purchases The sum of purchases, with statuses of Firmed or Open.

Scheduled Receipts Displays the total quantity for this period from the

following row types: Scheduled Production, Scheduled

Purchases, and Scheduled Transfers.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L M A N A G I N G T H E M A S T E R A N D M A T E R I A L P L A N S 5 - 1 1

Scheduled Transfers Displays the total amount of demand from transfer orders

placed on the source business unit for this time period.

Starting On Hand The cumulative inventory level at the beginning of the

period you defined for the Material or Master Plan

Summary. The history begins with the starting quantity

for the planning horizon.

Target Inventory Level Displays the average of safety stock plus excess inventory.

Total Demand Defined as the sum of Net Forecast, Customer Orders,

Inter-Unit Orders, and Dependent Demand. The total

demand consists of both independent and dependent

demand. The actual forecast is included as independent

demand.

Total Forecast Displays the original forecast quantity in the planning

period, before forecast consumption occurs.

Total Orders Displays the sum of customer orders and interunit orders.

Total Supply Displays the total quantity of actual supply and new

planned orders.

Transfer Demand Displays the scheduled transfers to other business units in

the form of transfer orders.

Transfer Supply Displays the scheduled receipts from other business units

in the form of transfer orders.

Changing Server Settings

Usage Use the Server Configuration Settings page to define the Planning server

from which you want to extract material- or master-plan data or to

review or change the current server settings temporarily. You need to

use this page only if a Planning server has not been defined that meets

your requirements. Use the Planning Server field to select an existing

server.

Object Name PL_CHG_SERVERS_SP

Navigation Plan Production, Manage Material or Master Plan, Inquire,

Planning Scorecard, Change Server Settings button

Prerequisite A valid server and user name must exist for a host in order to link to the

Planning engine.



Server Configuration Settings page

You can change which host machine or database you are linked to. For example, you might have

a simulation server established or a different set of data that you work with. Using this page, you

can change among your host machines without navigating to the Define Business Rules option,

where you also define server settings.

You can link to a server either by using the Planning Server field to select the server or by

completing fields on the page.

To establish a link between PeopleTools and the Planning engine, use the Host Name field to

define the machine or device that runs the Planning system. Type the Server Name to specify

the logical name of the Planning server instance. Use the Port field to define a valid port to use

in connecting to the Planning system.

The Timeout field defines how long the system will wait for a response from the Planning server.

This means Production Planning will wait for this duration before returning an incomplete

operation message. For example, the system may have lost its connection to the server, may have

found no rows of data, or could not connect to the server. You enter the time as seconds.

Changing Row Types

Usage Use the Change Row Types page to define which types of planning data

you want to include in the Material or Master Plan Summary. The data

is extracted from the Planning engine.

Object Name PL_ROW_TYPES_POPUP

Navigation Plan Production, Manage Master or Material Plan, Use, Master

Plan or Material Plan Workbench, Master or Material Plan

Summary, Change Row Types

Prerequisite A valid Server and User Name must exist for a host to link to the

Planning engine.



Change Row Types page

You can retrieve information with row types that display additional details about the master or

material plan item. Row types enable you to choose which reporting variables you want to

display in the summary. This is specific information that can be displayed on a row of the

summary. The information is calculated for specified periods and in some instances is

cumulative for the planning period.

Values that appear on this page are those that already appear in the summary. The values also

appear in the order in which they appear in the summary. To select a new value for the summary

and to define its placement in the summary, use the down arrow. Select the down arrow of the

row type that you want the new row type to follow in the summary list.

To add a row type, click the Add Row Type button after the row type has been defined.

To remove a row type, click the Remove Row Type button.

To save selections you make, click the OK button.

To remove or add row types for the inquiry, click the Search button to refresh the page after

you return to the Material or Master Plan Summary page.

Drilling Down to Maintain Scheduled Receipts

Usage Use the Plan Summary: Scheduled Receipts page to view material- or

master-plan item receipt details. You use this page to review current

orders for the item that you selected to work with in the workbench.

Object Name PL_SCHED_RCPT


Material Plan Workbench, select an Item ID, click the Search

button, click a value on the Scheduled Receipts row



Prerequisites A planning task must exist.

Access

Requirements

You must have a valid link to the Planning server along with an

established port.

Material Plan Workbench - Plan Summary: Scheduled Receipts page


PeopleBook in PeopleBooks Standard Field Definitions: Item ID, Configuration Code, and Std

UOM (standard unit of measure).

The Max Rows (maximum rows) field displays the maximum number of rows of data that can be

retrieved from the Planning engine. Each row of data represents a single planning task. The

system displays up to 500 rows of data. The value is set using the Record Field Properties page

in Application Designer.

The Start Date and End Date display the time period that you selected using the Plan Summarypage. This period is based on the period duration you define for the plan’s summary.

Click the Return button to return to the previous page and update the changes you make when

you add planned orders or link to the existing orders and make changes. For example, if you

decide to change the order quantity using the Order Type link, then you must click the Return

button to see the change in this page.

You can’t make changes to data that appears on the Scheduled Receipts page. When you

return from other links, click the Return button to update the page.

The following information also appears on the Scheduled Receipts page:



Planning Task Displays the unique identifier the system uses to track the

task to which the planned order is related. This might be a

production, purchase, or transfer task.

Show Supply Use this link to access all supply tasks related to this item

for this period. Supply tasks include production,

purchase, and transfer tasks. Select the link to work with

supply tasks.

Show Demand Use this link to access all demand tasks related to this item

for this period. Demand tasks include forecasts and sales

orders. Select the link to work with supply tasks.

Order Type Use this link to access any of the planned production,

purchase, or transfer orders for this item for this period.

Select the type of order you want to link to.

Start Qty Displays the quantity that currently exists for the

corresponding planning task. The quantity can be a

production, purchase, or transfer amount. You can change

the value by linking to the order type.

End Date Time Displays when the quantity from the planning task will be

available. You can change the quantity by linking to the

order type.

Order Status Displays the status of the order: Entered, Released, In

Process, Planned, Canceled, and Completed.

Frozen Flag When you select this, the planning task is frozen,

indicating that the system does not consider it when it

processes the material or master plan.

Showing Supply

Usage Use the Task Supply - Type/Item page to access all supply tasks related

to this item for this period. Supply tasks include production, purchase,

and transfer tasks. Select the link to work with supply tasks.

Object Name None



button, click a value on the Scheduled Receipts row, click Show

Supply


Access

Requirements


established port.



Task Supply: Type/Item page

The Task ID identifies the task that is supplying the item.




Sequence Displays the order in which this task belongs in the

pegged-chain sequence.

Level Displays the BOM level in the pegged chain at which this

task occurs.

Type Displays the type of task this entry represents in the

pegged demand.

Type/Item tab

See the exhibit above for a view of this tab.

Unit Displays the business unit in which the task takes place.

Item ID Defines the item that the supply task is producing.

Quantity Displays the amount of the item that the supply task is

producing.



UOM Displays how the item is measured.

Dates/Vendor/Task Name tab

Viewing the Dates/Vendor/Task Name tab

Start Date Displays when the task is currently scheduled to begin.

End Date Displays when the task is currently scheduled to end.

Vendor Defines the person or organization providing the order.

Task Displays the unique identifier the system uses to track a

task that appears in the pegged chain.





The Configuration Code provides a way to define a configured item further. The method is

based on the use of the item, such as how it’s assembled.

Showing Demand

Usage Use the Pegged Demand - Type/Item page to access all demand tasks

related to this item for this period. Demand tasks include production,

purchase, and transfer tasks. Select the link to work with demand tasks.

Object Name None



button, click a value on the Scheduled Receipts row, click Show

Demand


Access

Requirements


established port.



Viewing the Type/Item tab

A pegged-chain ties tasks and top-level demand together. In doing so, Production Planning can

explicitly track and record what supplies are being used to satisfy what demands. Through this

process the system first determines which independent or top-level demand has the highest

demand priority. Then, it determines the lateness preference ranking for dependent demand tasks.

The result is a sequencing of tasks to reach the demand. The Show Demand page shows these

tasks and information about the tasks.




Sequence Displays the order in which this task belongs in the

pegged chain sequence.

Level Displays the BOM level in the pegged chain at which this

task occurs.

Type Displays the type of task this entry represents in the

pegged demand.

Type/Item tab

See the previous exhibit for a view of this page.

Unit Displays the unit in which the item is being planned.

Item ID Displays the identifier the system uses to track the item.

Quantity Displays the amount of the item to be produced by this

task.

UOM (unit of measure) Displays how the item is measured. This is the

stockkeeping unit of measure for the item.



Dates/Task Name tab

Viewing the Dates/Task Name tab

The Start and End Date values display when the task begins and ends. The Task is the unique

identifier the system uses to track a task that appears in the pegged chain.





Drilling Down to Add or Change Planned Orders

Usage Use the Plan Summary: Planned Orders page to add, change, or review

planned production, purchase, and transfer orders in the material or

master plan. You use this page to review current orders for the item that

you selected to work with in the workbench.

Object Name PL_PLANNED_ORDERS



button, select a value on the New Planned Orders row.

Prerequisites You must select an item that is planned by the current material or master

plan.

Access

Requirements


established port.



Material Plan Workbench - Plan Summary: Planned Orders page


PeopleBook in PeopleBooks Standard Field Definitions: Unit, Configuration Code, and Std

UOM (standard unit of measure).

The Max Rows (maximum rows) field displays the maximum number of rows of data that can be

retrieved from the Planning engine. Each row of data represents a single planning task. The

system displays up to 500 rows of data. The value is set using the Record Field Properties page

in Application Designer.

The Start Date and End Date display the time period that you selected using the Plan Summary

page. This period is based on the period duration you define for the plan’s summary. Click the

following buttons to create new orders:

The Add Production button opens the Planned Production

page, where you can create a new production order.

The Add Purchase button opens the Planned Purchase

page, where you can create a new purchase order.

The Add Transfer button opens the Planned Transfer page,

where you can create a new transfer order.

Use the Return button to return to the previous page and update the changes you make when you

add planned orders or link to the existing orders and make changes. For example, if you decide to

change the order quantity using the Order Type link, then you must click the Return button to see

the change in this page.

You can’t make changes to data that appears on the Planned Orders page. When you return

from other links, click the Return button to update the page.



The following information also appears on the Planned Orders page:

Planning Task Displays the unique identifier the system uses to track the

task to which the planned order is related. This might be a

production, purchase, or transfer task.

Show Supply Use this link to access all supply tasks related to this item

for this period. Supply tasks include production,

purchase, and transfer tasks. Select the link to work with

supply tasks.

Show Demand Use this link to access all demand tasks related to this item

for this period. Demand tasks include forecasts and sales

orders. Select the link to work with supply tasks.

Order Type Use this link to access any of the planned production,

purchase, or transfer orders for this item for this period.

Select the type of order you want to link to.

Start Qty (start quantity) Displays the quantity that currently exists for the

corresponding planning task. The quantity can be a

production, purchase, or transfer amount. You can change

the value by linking to the order type.

End Date Time Displays when the quantity from the planning task will be

available. You can change the quantity by linking to the

order type.

Frozen Flag When you select this check box, the planning task is

frozen, meaning the system does not consider it when it

processes the material or master plan.

Adding Production Orders

Usage Use the Planned Orders - Planned Production page to add a production

order for the current material- or master-plan item.

Object Name PL_ADD_PLAN_PROD



button, select a value on the New Planned Orders row, click the Add

Production button.



Material Plan Workbench - Planned Orders: Planned Production page

When you select to add a new production order, you use the Planned Production page. The order

you create is entered into the Planning server as a planned order. After you enter orderinformation, click the Apply button to create the order.

Click the Return button to return to the Planned Orders page without creating a production order,

or click it after you click the Apply button to create the order. Remember to click Return to

view the production order you create on this page.

You can’t add a production order unless the item is the same as its associated primary item.

If it isn’t, a message alerts you that you can add production orders for primary items only.

This prevents you from creating orders for co-products.

The Business Unit, Item ID, and Config Code (configuration code) fields are the selections you

made to use the Master or Material Plan Workbench and are for display only.

When you add a production order, you complete the following information:

End Date Defines when the quantity from this task will be available.

This field is required.

Production Area Defines where the production is taking place. Use the

drop-down list to obtain valid areas.

Order Qty (order quantity) Defines the amount of the item you want to produce. This

field is required.

Std UOM (standard unit of

measure)

This value is a display-only value and represents how the

item is measured.

Frozen Select this check box to freeze the production task. This

means the system does not consider it when it processes

the material or master plan.

Production Option Defines how the item is manufactured. Use the drop-

down list to obtain valid options. This field is required.



Adding Purchase Orders

Usage Use the Planned Orders - Planned Purchase page to add a purchase order

for the current material- or master-plan item.

Object Name PL_ADD_PLAN_PURCH




Purchase button

Material Plan Workbench - Planned Orders: Planned Purchase page

The new purchase order you create is entered into the Planning server as a planned order. After

you enter order information, click the Apply button to create the order. Click the Return button

to return to the Planned Orders page without creating a purchase order, or click it after you click

the Apply button to create the order. Remember to click Return to view the purchase order you

create in this page.

The Business Unit, Item ID, and Config Code (configuration code) fields are defaults from the

workbench.

When you add a purchase order, you complete the following information:

Purchase Option Defines how the item is purchased, including the vendor.

Use the drop-down list to obtain valid options. This field

is required.

Delivery Date Defines when the quantity from this task will be available.


Frozen Select this check box to freeze the purchase task. This



Order Qty (order quantity) Defines the amount of the item you want to purchase.




Std UOM (standard unit of

measure)

This value is a display-only value and represents how the

item is measured.

Adding Transfers

Usage Use the Planned Orders - Planned Transfer page to add a transfer order

for the current material- or master-plan item.

Object Name PL_ADD_PLAN_TFR




Transfer button

Material Plan Workbench - Planned Orders: Planned Transfer page

If you want to add a new transfer order, you use the Planned Transfer page to define another

business unit (source unit) that can supply the item you need. The order you create is entered into

the Planning server as a planned order. After you enter order information, click the Apply button

to create the order. Click the Return button to return to the Planned Orders page without creating

a transfer, order or click it after you click the Apply button to create the order. Remember to

click Return to view the transfer order you create in this page.

The Dest Unit (destination unit) is the unit for which you want to create supply. The Source Bus

Unit (source business unit) is the unit that is going to supply the item. The field is required. The

Item ID and Config Code (configuration code) fields are for display-only values for the transfer.

When you add a transfer order, you complete the following information:

End Date Defines when the quantity from this task will be available.


Frozen Select this check box to freeze the production task. This



Order Qty (order quantity) Defines the amount of the item you want to produce. This

field is required.



Transfer Option Defines how the item is processed during its movement.

Data appearing in the field is based on transfer options

you create or on the transfer type. A transfer type is a

planned or existing interunit transfer task where the

system processes the transfer item for only a single

location. Use the drop-down list to obtain valid options.


Maintaining Production Orders

Usage Use the Production Orders page to view or make changes to an existing

production order for the current material- or master-plan item.

Object Name PL_VIEW_PRODUCTION



button, select a value on the New Planned Orders row, select a

production Order Type

Prerequisite A planned production order must already exist.

Material Plan Workbench - Planned Orders: Production Orders page


PeopleBook in PeopleBooks Standard Field Definitions: Business Unit, Config Code

(configuration code), Std UOM (standard unit of measure), Production Area, and Production

Status.

The Planned Production page displays the production tasks for the order type you selected on the

Planned Orders page. You can delete the order, freeze it, change its quantity, or change the start

and end times of the production tasks used to complete the order.



The item that appears on the page may not be the same item you accessed in the workbench.

The item ID is based on the item associated with the production ID. If you are using co-

products, the item will always be the primary item.

Select the Cancel Production check box to remove the order from the plan. When you cancel an

order, you make it inactive so that the system does not consider it when processing the material or

master plan. Select the Frozen Flag check box to change the status of the order to Frozen,meaning the system does not consider it when it processes the material or master plan. The

difference between deleting an order and freezing an order is that you can unfreeze and use afrozen order. Use the Order Qty field to change a production order quantity.

The lower portion of the page displays tasks associated with the production order. The Step and

Operation values display the order in which a specific task is performed, while the Start Date

Time and End Date Time values display the beginning and ending times for each task. You can

change these values to a valid time in the planning period, whether the task is frozen or not. You

receive a warning message when you change the time for a frozen task. The Status displays the

current state of the task, not the production status that appears in the top portion of the page. You

can also change the status of a production order’s task by selecting the Frozen Flag check box

for the task.

Use the following buttons to work with production orders:

The View Outputs button links to the View Outputs page,

where you can review the output type and remaining

quantities.

You must click the Apply button after you complete your

changes for the planned production order and tasks. This

enters you changes into the system. You still must use the

Refresh button when you return to the Planned Orders

page to view the changes you made in this page.

Click the Return button to go back to the Planned Orders

page. If you made changes, you must first click the Apply

button to enter the changes before you return to the

Planned Orders page.

Viewing Outputs

Usage Use the Planned Production - View Outputs page to view the end items

for a production order.


Navigation Plan Production, Manage Material or Master Plan, Use, Material or

Master Plan Workbench, select an Item ID, click the Search button,

select a date in the Planned On Hand row type, select a production

Order Type, View Outputs



Access

Requirements

To access the View Outputs page, click the View Outputs button on the

Production Orders page.

Material Plan Summary - Planned Production: View Outputs page

Information on the View Outputs page is for display only. You can view the Output Type for

the Item ID. Output types include the following:

Primary Item The main item being produced on a given piece of

production or production option. One primary item can

exist on a given production or production option. Primary

items must be produced at the last operation.

Co-product An item that is produced on a given piece of production or

production option. Multiple co-products can exist on a

given piece of production or production option. Co-

products must be produced at the last operation.

Recycle by-Product An item that is produced incidentally on a given piece of

production or production option. A by-product is

considered recycled when it can be used in some way,

either by its own or another operation, by another

production option, or by selling it.

Waste by-Product An item that is produced incidentally on a given piece of

production or production option. A by-product is

considered a waste when it isn’t reused in any fashion and

might have to be disposed of.

Teardown A teardown production order enables the breaking up of

an assembly and returning its reusable components to

inventory.



Maintaining Purchase Orders

Usage Use the Purchase Orders page to view or make changes to an existing

purchase order for the current material- or master-plan item.

Object Name PL_VIEW_PURCHASE




purchase Order Type

Prerequisites A planned purchase order must already exist.

Material Plan Workbench - Planned Orders: Purchase Orders page


PeopleBook in PeopleBooks Standard Field Definitions: Business Unit, Std UOM (standard unitof measure), and Purchase Order.

The Purchase Orders page displays the purchase order you selected on the Planned Order page.

You can delete the order, freeze it, change its quantity or change the delivery date. Select the

Delete check box to remove the order from the plan. When you delete an order, you make itinactive so that the system does not consider it when processing the material or master plan.

Select the Frozen check box to change the status of the order to Frozen, meaning the system does

not consider it when it processes the material or master plan. The difference between deleting an

order and freezing an order is that you can unfreeze and use a frozen order. The Status displays

the current state of the purchase order. Use the Order Qty (order quantity) field to change a

production order quantity.

The lower portion of the page displays the Adjusted Schedule Qty (adjusted schedule quantity),

Release Date, and Schedule Qty (schedule quantity). You can change the schedule quantity.

The Delivery Date displays when the order is due to arrive. The date is based on the Receiving

Calendar value so that the order will arrive at the receiving business unit during valid operating

hours. The Vendor ID displays the person or organization that is providing the item.

After you make changes, click the Apply button to enter the changes into the system, then click

the Cancel button to return to the Planned Orders page. Remember that you have to click the

Return button to see the changes you make to the purchase order.



Maintaining Transfer Orders

Usage Use the Transfer Orders page to add a view or make changes to an

existing production order for the current material- or master-plan item.





transfer Order Type

Prerequisites A planned transfer order must already exist.

Material Plan Workbench - Planned Orders: Transfer Orders page


PeopleBook in PeopleBooks Standard Field Definitions: Config Code (configuration code), Std

UOM (standard unit of measure), and Status.

The Transfer Orders page displays the transfer order you selected on the Planned Orders page.

You can cancel the order, freeze it, and change its quantity or delivery date. The Transfer Name

defines the unique ID the system uses to track the movement of an item from one business unit to

another. The Source Bus Unit (source business unit) is the shipping unit to which the itembelongs. The Destination Unit is the receiving business unit.

Select the Cancel check box to cancel the order. When you cancel an order, you make it inactive

so that the system does not consider it when processing the material or master plan. Select the

Frozen check box to change the status of the order to Frozen, meaning the system does not

consider it when it processes the material or master plan. The difference between canceling an

order and freezing an order is that you can unfreeze and use a frozen order.

The lower portion of the page displays information about the transfer task. The Start Qty (start

quantity) field displays the original amount of the transfer. Use the Order Qty (order quantity)

field to change the amount of the transfer. The Start Date Time and Delivery Date values

display when the item leaves the source business unit and arrives at the destination business unit.

You can change the delivery date value to a valid time in the planning period, whether the task is

frozen or not.



The Shipping Calendar and Receiving Calendar fields display the calendars this transfer uses.

When you use shipping and receiving calendars with each other, the Planning system schedules

task start and end times so that they begin within valid calendar dates and times for the sending

unit and so they end in valid dates for the receiving unit. As the system determines valid calendardates, it adjusts the duration of the task to fall within these dates.

Data appears in the Transfer Option field based on the transfer type value. A transfer type is a

planned or existing interunit transfer task where the system processes the transfer item for only a

single location.

After you make changes, click the Apply button to enter the changes into the system, then click

the Cancel button to return to the Planned Orders page. Remember that you have to click theReturn button to see the changes you make to the purchase order.

Analyzing the Master or Material Plan

After you create a material or master plan, you can use four options to review and work with the

plan. The options provide you with different methods for reviewing the plans. You can generate

the plan again to incorporate your changes and to improve the quality of your plan.

The options for analyzing the material or master plan include:

Material or Master Plan

Summary

Provides you with an aggregate (bucketed) view of the

supply and demand for a business unit item. You can use

the summary as part of the workbench where you can

make changes to the plan or as a stand-alone, display-only

detailed review. You mainly want to see that an item’s

supply meets the demand for the item in any given period.


Detail Inquiry

Displays the sequence of supply and demand over time for

an item. Use this inquiry when you want to review the

time-phased view of demand and supply for an item.


Exceptions

Displays exceptions for individual items in a plan. An

exception is a condition that prevents the material or

master plan from being feasible. The Exceptions Inquiry

and Planning Scorecard display similar data. The main

difference is that the Exception Inquiry enables you to

review all exceptions for an item in the same grid,

whereas the Scorecard provides some summary features

by exception type.

Material or Master

Planning Scorecard

Displays constraint violations, the number of violations,

and a score for the violations. In PeopleSoft Production

Planning, a score is the weighted sum of constraint

violations in a schedule. The score gives you an idea of

how valid, or acceptable, the schedule is.



Reviewing the Master or Material Plan Summary

Usage Use the Material or Master Plan Summary page to view and analyze the

current status of the material- or master-plan data for a specific item.


Navigation Plan Production, Manage Master or Material Plan, Inquire, Master

or Material Plan Summary


Access

Requirements


material- or master-plan data.

Plan Summary Page

The objective of the Material or Master Plan Summary is to provide you with an aggregate

(bucketed) horizontal view of the supply and demand for a business unit item.

Using the Material or Master Plan Summary, you first define the item parameters to create the

summary. After you define the parameters, you click the Search button to populate the summary.

You can’t change summary information using the Plan Summary page.

If you are maintaining a material or master plan, you use the Material or Master Plan

Workbench to access the Plan Summary page. Using the workbenches, you can maintain

item data, add orders, and work with tasks in a pegged chain.

The Unit is the business unit that contains the item for which you want to perform a Material or

Master Plan Summary. It is a required field. You also are required to select an Item ID for the

summary. To filter on a specific instance of a configured item you want to review, select a

Configuration Code.



The Start Date provides an exact starting time for the period of time you want to review in the

material or master plan. You can review data from the start of the plan or at different intervals in

the plan. If you do not enter a date, the default is Sunday of the current week. For example, if

today is Tuesday the 10th, the start date that appears in the field would be Sunday the 8th.

The Period Duration defines the measurement of time for which you want to review summary

information. Valid values for the option are Day, Week, and Month, with Week being the default

value. When you define the Number of Periods, the value is measured by the value you define

for the duration. The default value for the number of periods is 7. The number of periods you

define determines the number of tabs that appear in the summary. Each tab contains seven

planning periods.

Use the Planning Server field to select a different Planning server template name. This is the

server from which you want to extract Scorecard data.

The Change Row Types button provides a means for you to add, delete, or change the display of

data for the summary. The changes you make are temporary and do not replace the defaultvalues.

For more information about the available row types and their uses and about using the

summary, see Using the Master or Material Plan Summary.

Viewing the Master or Material Plan Detail

Usage Use the Material or Master Plan Detail page to retrieve and work with

material- or master-plan item data.



Material Plan Workbench, Master or Material Plan Summary


Access

Requirements

Define the group code, unit, and item ID to populate the summary with




Material Plan Detail: Details page


PeopleBook in PeopleBooks Standard Field Definitions: Unit, Configuration Code, Start Date,

End Date, and UOM (unit of measure). The Unit and Item ID values are required to access item

details.

The Material or Master Plan Detail Inquiry displays the sequence of supply and demand over

time for an item. You use the inquiry when you to review the phased list of demand and supply

for an item, a feature that is not available through the Material or Master Plan Summary Inquiry.

The demand and supply information appears along with the running balance for a singleinventory item; you can’t change item information using the inquiry.

The On Hand value in the top portion of the page defines the quantity of the item that is

available on the start date of the material or master plan. If the Safety Stock check box is

selected, safety stock exists for the item and will be displayed in the details. The Maximum

Rows to Retrieve field displays how many rows of data will be retrieved from the Planning

engine. The system displays up to 500 rows of data. The value is set using the Record Field

Properties page in Application Designer. When more than 500 detail rows exist for an item, usethe Start Date and End Date fields to view specific ranges for an item.

Use the available options for the Planning Server to select a different Planning server template

name. This is the server from which you want to extract plan detail data.

Click the Change Server Settings button override connection information for a Planning

server temporarily.

To use the inquiry, define the item that you want to review and generate the inquiry using the

Search button.

The detail rows are sorted by required date. If the demand and supply have the same required

date, supply data appears before demand. The following supply and demand row types are

available in the Material or Master Plan Details Inquiry:

Production This represents a specific production operation where the

item is either a component or an output for the operation.

Production operations from both production IDs and

production schedules are displayed.



Transfer This represents a specific transfer task where the item is

either shipped from a business unit (demand) or received

at a business unit (supply).

Planned Purchase Order This represents a planned purchase order delivery of

inventory.

Purchase Order This represents an existing purchase order delivery of

inventory.

Sales Order This represents either a customer order or customer quote.

It also represents material stock requests that are not

interunit transfers.

Forecast This represents the net forecasted quantity for an item.




Type The type of task for the detail row. See the list above for a

list of types included in the inquiry.

Required Date The required date for the quantity for the associated task.

Details tab


Qty The quantity associated with the task type displayed.

Balance The time-phased balance as determined by adding or

subtracting supply and demand.

Unit For demand tasks, this will be the business unit associated

with the item ID for which the demand task is associated.

For supply tasks, this field will be blank.

Item ID For demand tasks, this is the item associated with the

demand. For transfers and forecasts, this will be the same

item ID for which the inquiry is run. For Production

tasks, this will be the primary item being supplied by the

production ID or schedule.

Description Displays a description of the item.



Task tab

Viewing the Task tab

The Status defines the current state of the item. If the Frozen Task check box is selected, the

task is frozen. When the task is frozen, the system won’t reschedule it when processing the

material or master plan.



The Configuration Code provides a way to define a configured item further. The method isbased on the use of the item, such as how it’s assembled.

Reviewing Master or Material Plan Exceptions

An exception is a condition that prevents the material or master plan from being feasible. You

use the Material or Master Plan Exceptions option to review exceptions for individual items in a

plan.

The Exception option and Planning Scorecards both display information about current exceptions

that exist within the plan. Both could be used to find anomalies within the plan that need to be

corrected. The main difference is that the Exception Inquiry enables you to look at all exceptions



for an item in the same grid, while the Planning Scorecard has some nice summary features by

exception type. It will really be up to you to choose which page to use.

You can link to the Material or Master Plan Workbench if, during your review, you want to makechanges to either plan.

Selecting Exceptions for Review

Usage Use the Selection Criteria page to define filters that you want to use to

limit the material- or master-plan exceptions that appear in the inquiry.

You define selection criteria to reduce the size of the inquiry for a single

item at a time.

Object Name PL_MX_INQ_PNL1


or Material Plan Exceptions, Selection Criteria


Access

Requirements



Material Plan Exceptions - Selection Criteria page


PeopleBook in PeopleBooks Standard Field Definitions: Unit, Config. Code (configuration

code), Category ID Family, and Planner Code.

Use the Planned By group box to indicate if you want to include exceptions that have been

defined in either the material plan or master plan or both. Use the Exception Type group box to

define the types of order and operation exceptions you want to include in the inquiry. You can

include the following types of exceptions in the inquiry:



Request Date Violations Displays when a sales order line is going to ship after the

customer's request date.

Promise Date Violations Displays when a sales order shipment is going to ship after

the date you committed to ship it.

Safety Stock Violations Displays when stock level drops below the safety limit for

the item you define.

Material Shortages Displays when a supply is not going to be available for the

item you define.

Forecast Fulfillment

Violations

Displays when a forecast has been partially filled and any

remaining or canceled quantities.

Sch Rcpts before Current

Time (scheduled receipts

before current time)

Displays receipts of inventory that are scheduled before

the current time, making them past due. This exception is

available on the Exception Inquiry only and not on the

Scorecard.

Planned Order before PTF

(planned order before

planning time fence)

Displays when a planned order is scheduled within the

planning time fence defined for the item. The planning

time fence is an offset from current time and is defined at

the business unit item level. It is typically set to a value

that represents a time frame when it is difficult to react to

changes. This exception is available on the Exception

Inquiry only and not on the Scorecard.

Transfer Shipment Dt

Violations (transfer shipment

date violations)

Displays when demand transfer has been rescheduled and

used by the Optimizer or a solver to repair missed due

dates.

Use the Planning Server field to select a different Planning server template name.

For more information about changing the server settings, see Changing Server Settings.

You can define additional filters for extracting constraint violation information from the Planning

engine. Click the Advanced Filters tab to access filters that help you reduce the amount of

information contained in the Scorecard Inquiry.

The Maximum Rows to Retrieve field displays how many rows of data will be retrieved from

the Planning engine. Each row of data represents a single constraint violation. The system

displays up to 500 rows of data. The value is set using the Record Field Properties page in

Application Designer.



Defining Advanced Filters

Usage Use the Advanced Filters page to define specific customer promise and

request date data and the types of orders and operations that you want to

include in an exceptions inquiry.

Object Name PL_MX_ADV_FILTERS1


or Material Plan Exceptions, Advanced Filters


Access

Requirements



Material Plan Exceptions - Advanced Filters page

Use the Promise/Req. Date Excp. Filters (promise/required date exception filters) group box to

select the Customer ID that you want to include in the inquiry. The promise date and required

date exceptions the system displays will belong to only the customer that you select. You can

also limit the exceptions to a date range using the Date From and Date To fields. This date

range is different from the ranges you define for orders and operations.

In addition, you can select a Vendor ID to limit the exceptions displayed to a specific vendor.

This filter is helpful to identify specific purchase orders that are past due (before current time) ormay need to be expedited (before the planning time fence).

Use the Order/Operation Type group box to limit the inquiry to specific types of orders or

operations. Select the corresponding check box to include your option. If a check box is

selected, the system includes that type of order or operation in the inquiry.

You can also set up a date range for orders and operations. Using the Order/Operation Start

Date and Order/Operation End Date group boxes, you can limit an inquiry to within certain

dates.



Reviewing the Results

Usage Use the Results page to retrieve and review material- or master-plan

item data.

Object Name PL_MX_RESULT_PNL


or Material Plan Exceptions, Results


Access

Requirements



Material Plan Exceptions - Results page

The Results page displays the Exception Types that you originally defined for the inquiry. If the

check boxes are selected, then that exception type is included in the inquiry. Selecting the Max

Rows Limit Hit check box indicates that the number of exceptions is greater than the maximum

rows to retrieve (500). You can also select a Sort Order for the data contained in the inquiry

pages.

For more information about using workbenches, see Defining the Master or Material

Workbench Search Parameters.

As you review item data, you can switch to the Material or Master Plan Workbench to makechanges to the item.

Click the Workbench Link button to access the workbench.






Exception Date Displays when the exception to the material or master plan

occurs. An exception is a constraint violation in a plan.

Exception Type Displays the kind of exception (such as promise date) that

occurs.

Business Unit Defines the business unit within which the exception

occurs.

Item ID Displays the item for which the exception occurs.

Exceptions tab


Description Provides an extended description of the item.

Req Qty (required quantity) Displays the total amount of the item required.

UOM (unit of measure) Displays the unit of measure in which the quantity is

expressed. This is the stockkeeping unit of measure for

the item.

Order/Operation Details tab

Viewing the Order/Operations Details tab

Order/Operation Type Displays what kind of task the exception belongs to. For

example, it might be a production operation or a transfer

order.



Status The status indicates the state or condition of the order or

operation. While you can define the statuses, the

following ones are provided by the system: Planned,

Entered, Firmed, Pending, Dispatched, Active, Frozen,Complete, and Canceled.

Frozen If this check box is selected, then the order or operation is

frozen, meaning the system can’t automatically move the

order.

Start Time Defines the date and time that an order or operation is to

begin.

End Time Defines the date and time that an order or operation is to

end.

Order/Operation Defines the unique ID the system uses to retrieve and

process this order or operation.

Exception Specific Details tab

Viewing the Exception Specific Details tab

Customer/Vendor Displays the person or organization that is going to

receive (customer) or ship (vendor) the item for which the

exception was created.

From Unit Displays the shipping business unit for the item.

To Unit Displays the receiving business unit for the item.

Forecast Delayed Displays the amount of a forecasted quantity that has been

delayed. A forecast quantity can be delayed when partial

quantities can be produced. This column is populated for

forecast fulfillment exceptions only.



Forecast Canceled Displays the amount of a forecasted quantity that has been

canceled. When a forecast quantity is canceled, the

system does not include that quantity in processing. This

is populated for forecast fulfillment exceptions only.





Using the Planning Scorecard to Review Your Master or Material Plan

The PeopleSoft Production Planning Scorecard is a tool that evaluates the efficiency of your

overall enterprise plan by showing you constraint violations, the number of violations, and a score

for the violations. In Production Planning, a score is the weighted sum of constraint violations in

a schedule. The score gives you an idea of how valid, or acceptable, the schedule is.

You use the Planning Scorecard to view the scorecard information for an existing plan.

You use the data in the Planning Scorecard for review purposes only. You don’t maintain

data using the Scorecard.

Along with displaying Planning engine data, you use the Scorecard page to filter the type and

quantity of information you want to display and the Planning server you want to connect to.

Overview of the Planning Scorecard

The Planning Scorecard page contains similar information to that in the Scorecard available in the

Planning engine. Both scorecards display summary information (score/count) for the constraints

that are selected using the Control Panel option in the Planning engine. The DataLink creates the

initial model with all constraints selected so that the scorecard displays all violated constraints. If



you turn off a constraint through the Planning Client, the constraint won’t be scored nor will

details be retrieved in the Planning Scorecard pages.

For more information about using the Control panel, see PeopleSoft 8.00.01 AdvancedPlanning Client PeopleBook, “Managing Constraints”.

The Planning Scorecard uses an early fence that displays the beginning of the time interval that

the Planning engine evaluates and then produces the Planning Scorecard. A late fence displays

the end of the interval and is usually set at the end of the planning horizon. These fences

determine the time interval in which the Scorecard counts constraints to the schedule.

Each constraint has a filtered count, a total count, and a score. The filtered count represents the

number of violations that match any filtered criteria that were defined using the Filters page. The

total count represents the number of violations for a particular type of constraint. The total score

for each type of constraint is based on several weight factors that represent the relative

importance of a constraint. The total count and score do not use filters; they show you all

constraint violations.

A score of zero indicates that the constraint either is not violated or has been cleared. Penalty is a

function that expresses the degree to which the constraint is violated.

Before you send data to the Planning engine and begin to use the Planning Scorecard, you must

setup several pieces of information that PeopleSoft Production Planning uses to populate theScorecard with the type of data that you want.

To process the material and master plan and retrieve Scorecard data, use the following steps:

1. Define DataLink options you that want the Planning engine to use in identifying material- or

master-plan modeling parameters. This includes the solvers that you want to run and the

types of data you want included in the processing.

2. Define a Planning server template name so it can be selected on the Scorecard Summary

page, eliminating the need to enter user, server, and port data each time you access the

Planning Scorecard. A prerequisite to using the Planning Scorecard is that you have a

Planning engine running on a server.

3. Generate the plan. The data goes to the Planning engine and the system starts the solvers you

defined.

4. Use the Planning Scorecard page to review the counts and scores of constraint violations that

exist in the Planning engine. Then, you can determine the types of violations that you want to

work with.

Using the Planning Scorecard Page

Usage Use the Planning Scorecard page to review high-level information about

constraint violations for your current planning model. You can also drill

down to more detailed data, define the extent of data for review, and

connect to different servers in the Planning engine.



Object Name PL_SCARD_SUMMARY

Navigation Plan Production, Manage Master or Material Plan, Inquire,

Planning Scorecard

Prerequisites You must have generated a plan by running one of the solvers.

Access

Requirements


established port to import Scorecard data from the Planning engine.

Planning Scorecard page

Information on the Planning Scorecard page displays the filtered count, the total count, and the

total score for each type of constraint class in the current plan or schedule. The system pulls this

information from the Planning engine and it appears as display-only data. To see specific

constraint violations, select the Filtered Count field.

The following information appears on the Planning Scorecard page, regardless of the constraint

you select to work with:

Early Fence Displays the beginning of the time interval in which

constraint violations are calculated.

Late Fence Displays the ending of the time interval in which

constraint violations are calculated.

Filtered Count Displays the number of violations that match any filtered

criteria that were defined using the Filters page. You

select this value to see additional details about the count.

Total Count Displays the number of violations for a particular type of

constraint.

Total Score Displays the total score for each type of constraint. The

score is based on several weight factors that represent the

relative importance of a constraint.



From the Planning Scorecard page, you can access detail pages associated with the following

types of constraints:

Request Dates A sales order line is scheduled to ship at the customer's

request date. This constraint strives to keep a sales order

delivery scheduled to meet the customer request date. The

constraint exists on each shipment scheduled for a sales

order. It's created automatically by the order processing

transactions.

Promise Dates A sales order shipment is scheduled to ship at the date you

committed to ship. This constraint strives to keep a sales

order delivery scheduled to meet the promise date. The

constraint exists on each shipment scheduled for a sales

order. It's created automatically by the order processing

transactions.

BI Shortages (buildable

inventory shortages)

A buildable inventory shortage occurs when there is a

material shortage for an end item. This constraint tries to

make sure that there is enough available inventory to meet

all of the demands for finished good items.

Aggregate Capacity The aggregate capacity constraint is violated when a

production operation overloads an aggregate capacity

resource. This constraint tries to make sure that the

production does not overallocate the aggregate capacity

buckets.

Safety Stock When stock level drops below the safety limit, existing

supplies must be moved or new supplies must be

generated to bring the stock back to the desired level.

This constraint keeps inventory at a desired level during

user-defined time intervals. Deviation from this desired

level is tolerable within a margin defined by the safety

limit.

Excess Stock When stock level exceeds the excess limit, movement or

deletion of supplies is necessary to bring the stock down

to the desired level. This constraint keeps inventory at a

desired level during user-defined time intervals.

Deviation from this desired level is tolerable within a

margin defined by the excess limit.

RM Shortages (raw material

shortages)

A raw material shortage occurs when there is a material

shortage for a purchased item. This constraint tries to

make sure that there is enough available inventory to meet

all of the demands for purchased items.



Forecast Fulfillment Any forecast task that is not met or is partially met

represents a constraint to the production plan. This

constraint displays all the violated forecast fulfillment

constraints, including the total quantity of filled forecast

tasks for all planning periods, the total quantity of delayed

forecast tasks, and the total quantity of canceled forecasts.

Transfer Ship Date The transfer shipment date is a constraint linked to the

transfer type. This constraint displays any demand transfer

task that has been rescheduled and used by the Optimizer

or a solver to repair missed due dates for a demand

transfer task.

Use the Planning Server field to select a different Planning server template name. This is theserver from which you want to extract Scorecard data.

For more information about changing the server settings, see Changing Server Settings.

You can define additional filters for extracting constraint violation information from the Planning

engine. Use the Filters button to access filters that help you to reduce the amount of information

contained in the Scorecard Inquiry.

For more information about defining filters for the Planning Scorecard, see Filtering

Material or Master Plan Scorecard Data.

The Maximum Rows to Retrieve field displays how many rows of data will be retrieved from

the Planning engine. Each row of data represents a single constraint violation. The system

displays up to 500 rows of data. The value is set using the Record Field Properties page in


You receive a warning message if more than 500 violations are going to be extracted and

returned to the Scorecard.

Reviewing Request Date Constraint Violations

Usage Use the Request Dates page to review Scorecard constraint violations

that relate to shipments requested by customers.

Object Name PL_SC_REQ_DATE


Planning Scorecard, Request Dates Filtered Count

Prerequisites Define any filters that you want to use to limit the request date

information that appears in the Scorecard.



Access

Requirements


established port.

Planning Scorecard - Request Dates: Date/Customer page

Request dates are the dates that a customer has requested to receive a shipment. A sales order

line is scheduled to ship based on this request date. The request date constraint strives to ensure

that a sales order delivery schedule meets the customer’s request date. The constraint exists on

each shipment scheduled for a sales order. It's created automatically by the order processing

transactions.

When you have violations, you can move the shipment date earlier or later in time so that it is

closer to the request date, assuming that such a shipment would be supported by the required

finished goods inventory. This doesn’t change the sales order’s request date.

For more information about the remaining constraints and using this page, see Using the

Planning Scorecard Page.




The Request Date displays the date and time that the customer has requested for the arrival of

stock at the customer location. If the date and time are earlier than the Shipment End date andtime, there is a violation to the material or master plan.

Date/Customer tab




Customer Displays the person or organization that is going to

receive the shipment and whose request date is going to be

missed.

Shipment Start Date/Time Defines when the shipment task is to begin. This is the

date and time that the stock is scheduled to leave the

business unit.

Shipment End Date/Time Defines when the shipment task is to end. This is the date

and time that the stock is scheduled to arrive at the

customer location.

Shipment Displays the identifier for the shipment. This ID is used to

track the movement of stock for the sales order.

Sales Order Displays the sales order code the PeopleSoft Production

planning system uses to track a sales order through its

production and shipment. This sales order is the one with

the constraint violation.

Item ID tab

Viewing the Item ID tab

The Unit column indicates the business unit that is shipping the stock to meet the sales order

demand, and the Item ID identifies the item ordered by the customer. An item may have a

different ID from business unit to business unit. The Planner Code identifies the person

responsible for the item and for completion of the sales order.







Reviewing Safety Stock Constraint Violations

Usage Use the Safety Stock page to review items in your plan that drop below

their safety-stock level.

Object Name PL_SC_SAFETY_STOCK


Planning Scorecard, Safety Stock, Filtered Count

Prerequisites Define any filters that you want to use to limit the information that

appears in the Scorecard.

Access

Requirements


established port.

Planning Scorecard - Safety Stock: Item ID page

When items in the material or master plan drop below their safety-stock limit during the planning

horizon, they appear on this page. When the stock level drops below the safety limit, existing

supplies must be moved or new supplies must be produced to bring the stock back to the desired

level.

This constraint keeps inventory at a desired level during user-defined time intervals. Deviation

from this desired level is tolerable within a margin defined by the safety limit.








Unit Indicates the business unit in which the planned on-hand

inventory level for this item falls below safety levels.

Item ID Identifies the item for which the planned on-hand

inventory falls below safety-stock levels.

Item ID tab


Description Describes the item that has the safety-stock violation.

Start Date/Time Defines the first date on which the item’s planned on-hand

inventory falls below the set safety-stock level. Used with

the End Date/Time column, this column displays the

length of time that the inventory is below the safety-stock

level.

End Date/Time Defines the last date that the item’s planned on-hand

inventory is below safety-stock levels.

Max Deviation Displays the maximum amount the item’s planned on-

hand inventory level is below safety stock during the

planning horizon. While the inventory level may remain

below safety-stock levels for a week, the maximum level

might only last for a single day.

Planner/Configuration Code tab

Viewing the Planner/Configuration Code tab

The Planner Code identifies the person responsible for the item and its inventory. The

Configuration Code provides a way to define a configured item further. The method is based onthe use of the item, such as how it’s assembled.

Reviewing Promise Date Constraint Violations

Usage Use the Promise Dates page to review Scorecard information that relates

to shipments that have been promised to customers.

Object Name PL_SC_PROM_DATE


Planning Scorecard, Promise Dates, Filtered Count





Access

Requirements


established port.

Planning Scorecard - Promise Dates: Date/Customer page

Promise dates are the dates and times that you promise a customer that a shipment will arrive.

The sales order shipment is scheduled to ship on the date you committed to ship. This constraint

strives to keep a sales order delivery scheduled to meet the promise date. The constraint exists on

each shipment scheduled for a sales order. It's created automatically by the order processingtransactions.

When you have violations, you can move the shipment date earlier or later in time so that it is

closer to the promise date, assuming that such a shipment would be supported by the required

finished goods inventory. This doesn’t change the sales order’s promise date.






The Promise Date displays the date and time when stock has been committed to arrive at the

customer location. If the date and time are earlier than the Shipment End date and time, there is aviolation to the production plan.



Date/Customer tab


Customer Displays the person or organization that is going to

receive the shipment and to whom the promise

commitment was made.

Shipment Start Date/Time Defines when the shipment task is to begin. This is the

date and time when the stock is scheduled to leave the

business unit.

Shipment End Date/Time Defines when the shipment task is to end. This is the date

and time when the stock is scheduled to arrive at the

customer location and the promised date that is going to

be missed.

Shipment Displays the identifier for the shipment. This ID is used to

track the movement of stock for the sales order.

Unit Indicates the business unit that is shipping the stock to

meet the sales order demand.

Sales Order Displays the sales order code the PeopleSoft Production

Planning system uses to track a sales order through its

production and shipment.

Item ID tab


The Unit column indicates the business unit that is shipping the stock to meet the sales order

demand, and the Item ID identifies the item ordered by the customer. An item may have a

different ID from business unit to business unit. The Planner Code displays the personresponsible for the item and for the completion of the sales order.

Configuration tab





based on the use of the item (for example, how it’s assembled).

Reviewing Excess Stock Constraint Violations

Usage Use the Excess Stock page to review production plan violations for

excessive levels of stock.

Object Name PL_SC_EXCESS_STOCK


Planning Scorecard, Excess Stock, Filtered Count


appears on the Scorecard.

Access

Requirements


established port.

Planning Scorecard - Excess Stock: Item ID page

Excess stock exists when an item’s inventory level is higher than limits set for the item. The

movement or deletion of supplies is necessary to bring the stock level down to within limits.

This constraint keeps inventory at a desired level during user-defined time intervals. Deviation

from this desired level is tolerable within a margin defined by the excess limit.








Unit Indicates the business unit in which the planned on-hand

inventory goes above excess stock limits.

Item ID Identifies the item for which the planned on-hand

inventory goes above excess stock levels. A Description

follows the item.

Item ID tab


Start Date/Time Defines the first date on which the item’s planned on-hand

inventory is above the set excess stock level. Used with

the End Date/Time, the two values display the length of

time that the inventory is above the excess level.

End Date/Time Defines the last date on which the item’s planned on-hand

inventory is above safety-stock levels.

Max Deviation (maximum

deviation)

Displays the maximum amount that the planned on-hand

inventory level of the item is above excess stock levels.

While the stock level may be in excess for a week, the

maximum level might last for only a single day




Configuration Code provides a way to define a configured item further. The method is based on

the use of the item, such as how it’s assembled.

Reviewing BI Shortage Constraint Violations

Usage Use the BI Shortages page to review Scorecard information relating to

buildable inventory shortages.

Object Name PL_SC_BI_SHORTS


Planning Scorecard, BI Shortages, Filtered Count





Access

Requirements


established port.

Planning Scorecard - BI Shortages (buildable inventory shortages): Item ID page

A buildable inventory shortage occurs when there is a material shortage for a manufactured item.

This constraint tries to make sure that there is enough available inventory to meet all of thedemands for manufactured items.






Unit Indicates the business unit that will experience the

inventory shortage of this item.

Item ID Identifies the manufactured item for which there is not

going to be enough inventory supply to meet a particular

demand. A Description follows the item.

Item ID tab


Date/Time Displays the date and time that the item is required.



Quantity Displays the total amount of the item that is required.

Quantity Short Displays the amount of the item that is going to be short in

the current plan.

Details tab

Viewing the Details tab

The Operation column displays the type of operation that requires the item, such as a production

task or transfer and the Planner Code column identifies the person responsible for the item.





Reviewing RM Shortage Constraint Violations

Usage Use the RM Shortages page to review production plan violations that

relate to raw materials purchased to meet orders in the plan.

Object Name PL_SC_RM_SHORTAGES


Planning Scorecard, RM Shortages, Filtered Count



Access

Requirements


established port.



Planning Scorecard - RM Shortages (raw material shortages): Item ID page

A raw material shortage occurs when there is a material shortage for a purchased item. This

constraint tries to ensure that there is enough available inventory to meet all of the demands forpurchased items.






Unit Indicates the business unit that will experience the raw

material shortage.

Item ID Identifies the purchased item for which there is not going

to be enough planned on-hand inventory to meet a

particular demand. The item’s Description also appears.

Item ID tab


Date/Time Displays the date and time that the item is required.

Quantity Displays the total amount of the raw material required.

Quantity Short Displays the cumulative amount of raw material that is

going to be short.



Details tab


The Operation column displays the type of operation that requires the item, such as a production

task, and the Planner Code displays the person responsible for the item and for completion of itsproduction.




based on the use of the item (for example, how it’s assembled).

Reviewing Aggregate Capacity Constraint Violations

Usage Use the Aggregate Capacity page to review Scorecard constraint

violations for overloaded aggregate resources.

Object Name PL_SC_AGG_CAP


Planning Scorecard, Aggregate Capacity, Filtered Count



Access

Requirements


established port. Also, Scorecard violations must exist before the page

is populated.



Planning Scorecard - Aggregate Capacity: Resource page

aggregate resource planning, the system combines capacity loads for resources in daily, weekly,

or monthly planning buckets. The number of tasks scheduled in this bucket can be unlimited as

long as there are available hours in the bucket.

Aggregate capacity represents the total capacity available to perform tasks in a given time bucket.

This constraint tries to make sure that the production does not overallocate the aggregate capacity

buckets.






Unit Defines the business unit where the aggregate resource is

located.

Assigned Resource Displays the aggregate resource that is overloaded.

Aggregate capacity violations identify production

operations that are scheduled at times that exceed the

available capacity on the assigned aggregate resource.

Resource tab


Start Date/Time Identifies when the resource is scheduled to begin

producing the item.



End Date/Time Identifies when the resource is scheduled to complete the

production of the item.

Load Start Date/Time Displays the start time the system uses to calculate and

allocate the remaining capacity requirement for the

production task when a portion of the task has been

completed. The system calculates a load duration value

based on the remaining task quantity, then uses that value

with the task end time to establish the load start time.

Details tab


The Resource Class identifies the type of resource, either aggregate by time or aggregate by unit.

The Operation identifies the production operation that is scheduled on the resource.

Item ID tab


The Item ID column displays the item that the resource is producing, and the Description

provides a brief description of the operation. The system uses this identification to track the flow

of the requirement and plan for its material needs. The Planner Code displays the personresponsible for the item and completion of its production.




based on the use of the item such as how it’s assembled.



Reviewing Forecast Fulfillment Constraint Violations

Usage Use the Forecast Fulfillment page to review violations relating to

unfulfilled forecasts.

Object Name PL_SC_FCST_FILL


Planning Scorecard, Forecast Fulfillment, Filtered Count



Access

Requirements


established port.

Planning Scorecard - Forecast Fulfillment: Item ID page

Forecast fulfillment is the process the Planning engine uses to meet forecasted demand when

there is not enough supply to meet all of the demand at once. During the process, net forecasts

are divided into tasks that are associated with the original planning period. For example, each

forecast is associated with a planning period, and planning periods are defined to be either daily,weekly, or monthly.

Each task represents a portion of the quantity required to meet the forecasted demand. Constraint

violations that appear on this page are those that are associated with a delayed or canceled

forecast task. The forecast fulfillment score is the number of violated forecast fulfillmentconstraints divided by the total number of forecast fulfillment constraints.








Unit Indicates the business unit that has a forecasted demand

for the item.

Item ID Identifies the item associated with the forecast fulfillment

violation. A Description of the item follows.

Item ID tab


Filled Displays the item’s total forecast quantity that can be met

in the original planning period. If the entire forecast can’t

be met, values appear in either the Delayed or Canceled

columns.

Delayed Displays the total forecast quantity that has been delayed.

If a forecast is front loaded, it is considered to be delayed

if any of its tasks start after the planning period start time.

If a forecast is back loaded, it is considered to be delayed

if any of its tasks start after the planning period end time.

Canceled Displays the total forecast quantity that has been canceled.

Within the forecast fulfillment fence, if a forecast task

can’t be satisfied in its original planning period, then

solvers cancel the task. After the fence, solvers roll over

any unfulfilled forecast task demand to later planning

buckets.

For more information about defining the forecast fulfillment fence, see “Setting Up the









Reviewing Transfer Shipment Date Constraint Violations

Usage Use the Transfer Ship Dates page to review material and master-plan

constraint violations for demand-transfer type tasks that have been

rescheduled by the Planning engine.

Object Name PL_SC_TRSFR_MST


Planning Scorecard, Transfer Ship Date, Filtered Count

Prerequisites Click the Filters button to define any filters that you want to use to limit

the information that appears in the Scorecard.

Access

Requirements


established port.

Planning Scorecard - Transfer Ship Dates: Transfer Details page

This page displays transfer shipment date constraint violations for demand transfer tasks that have

been rescheduled and used by the Planning engine to repair missed due dates for demand transfer

tasks.

A transfer type is a planned or existing interunit transfer in which the system only processes the

transfer item for a single location. This reduces the time it takes for the Planning engine to run

material and master plans. For example, you might model and manufacture an item in one plant

and define a demand transfer of the item to another location. During the processing, the DataLink

and Planning engine do not process data, such as bills and routings, associated with the item from

the shipping location.

Transfers result from either demand or supply requirements. In a single manufacturing

environment, you can set up transfers supplying the plant as the supply side of the transfer and set

up transfers placing a requirement on the plant as the demand side of the transfer. Existing and

planned transfers for an item for each business unit will have the supply side, the demand side, or

both sides modeled in PeopleSoft Production Planning.








The Original Shipment Date/Time defines the date and time that a demand transfer task was

originally scheduled for shipment. The demand transfer was rescheduled by a solver to repairanother problem.

Transfer Details tab


Shipment Date/Time Defines the date and time the transfer will be shipped from

the From Unit.

Receipt Date/Time Defines the date and time the transfer should arrive at the

To Unit.

Unit Defines the shipping unit.

Item ID Defines the item at the From Unit. Using demand transfer

shipments, the Optimizer reduces processing time by

using item data from only one business unit. The

Planning engine does not process item information

associated with the To Unit.

To Unit Defines the destination unit. The item information is

associated with the From Unit.

Shipment Quantity Indicates the amount of the item that the task is scheduled

to transfer.

Transfer Task tab

Viewing the Transfer Task tab



The Transfer Tasks column displays the identifier of the transfer task that is moving the item.

The Planning engine uses the ID to track the transfer during processing.






Filtering Material or Master Plan Scorecard Data

Usage Use the General Filters page to limit the amount of data the system

extracts from the Planning engine. You use filters to define specific

ranges of data for the current material or master plan.

Object Name PL_SC_FILTERS_SP

Navigation Plan Production, Process Production Plan, Inquiry, Planning

Scorecard, Filters

Prerequisites Define any filters you want to use in limiting the information that


Planning Scorecard - General Filters page

Using this page, you can limit the amount of data contained in the Planning Scorecard, reducing

the time it takes to generate the Scorecard and making information easier to review. You use



these filters to extract manageable amounts of data from the Planning engine. No fields are

required on the General Filters page. After you define the filters, click the OK button. The

summary page is then refreshed with the new filtered counts.

If you do not define filters, PeopleSoft Production Planning extracts all constraint violations

from the Planning engine, which may require additional processing time.

Enter the Business Unit from which you are going to extract production plan violations for the

Scorecard. You can also use the Planner Code field to limit the extracted data to a single

planner ID. If you do not enter a unit or planner, then all violations for units or planners are

included in the Scorecard results.

Use the Item ID fields to define an alphanumeric range of items that will be extracted from the

Planning engine. The From item is the first item in the range and the To item is the last in the

range. The Config Code (configuration code) fields make it possible to limit the number of items

in the Scorecard to a specific configuration code. These are IDs that you use instead of part

numbers to define a particular arrangement or assembly of components.

Use the Date From field to select the beginning date for Scorecard data and use the To field to

select the ending date. Only constraint violations that occur within these dates appear in the

Scorecard.

You can also filter data to view promise and request date violations for a specific Customer, or to

view aggregate capacity violations for a specific Aggregate Resource. Only the violations for

the customer or the resource you define appear in the Scorecard.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L M A N A G I N G T H E C A P A C I T Y P L A N 6 - 1

C H A P T E R 6

Managing the Capacity Plan

After you decide the amount of resources available, you need to determine the amount of capacity

required to produce products in the future. You can use a capacity plan to manage your

resources. With the capacity plan, you can view capacity by user-specified buckets and drill

down to production details where you can add, delete, cancel, or reschedule capacity

requirements.

Overview of the Capacity Planning Process

In planning for capacity, you need to:

• Determine the amount of available resources in a specific business unit.

• View the resource load and the production associated with it.

• Identify the required capacity and the overloaded capacity.

• Adjust the order as needed by adding, deleting, or canceling production, rescheduling tasks, or

changing quantity.

Before You Begin

Before you can create a capacity-feasible plan, you must:

• Establish a resource using the Planning Option page in the Define Resources component and

Define Work Centers component in PeopleSoft Manufacturing.

• Start a Planning-server session and generate a production plan. The resources in the Planning

server must correspond to the resources in the workbench.

Maintaining the Capacity Plan

To effectively maintain the capacity plan, you need to easily display information about the

overloaded resources in a bucketed format. PeopleSoft Production Planning responds to this need

by providing you with a robust set of inquiry pages.

You can first use the Resource Workbench to view the capacity-plan details based on certain

selection and sort criteria. After you’ve identified the overloaded resources, you can then view


6 - 2 M A N A G I N G T H E C A P A C I T Y P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

the loads in a bucketed format over time from the Capacity Summary. Consequently, you can

make manual adjustments to the capacity plan to resolve capacity problems.

Defining the Resource Workbench Search Parameters

Usage Use the Resource Workbench page to search all resources and identify

those that have capacity violations.

Object Name PL_CWB1_RI

Navigation Plan Production, Manage Capacity Plan, Use, Capacity Plan

Workbench, Resource Workbench

Prerequisites Establish a business unit, a resource, and a Planning server.

Access

Requirements


Resource Workbench page

Using the search feature, select a Business Unit. Then, select a Resource Type from the

available options: Crew, Machine, Rough Cut Resource, Tool, Work Center, and Workcenter

(subcontract).

You can’t select rough-cut capacity resources from the Capacity Plan Workbench as they

apply to the rough-cut capacity plan in PeopleSoft Enterprise Planning. You must enter a

resource type to return a list of available resources.

Select a Violation Rule from the available options as a criterion to display the violations. Thedefault is All Resources. Your options are:



Consider Violations Select this option if you want to display only resources

with the Ignore Violations check box clear.

Ignore Violations Select this option if you want to display only resources

with the Ignore Violations check box selected.

All Resources Select this option if you want to display all resources

regardless of whether the Ignore Violation check box is

selected or not.

The Ignore Violations functionality is determined on a resource-by-resource basis.

For more information about Ignore Violations, see PeopleSoft 8.00.01 Bills and RoutingsPeopleBook, “Maintaining Work Centers” and “Defining Resources”.

The Max Rows (maximum rows) field displays how many rows of data the Planning engine will

retrieve for the inquiry. Each row of data represents a single constraint violation. The system

displays up to 500 rows of data. The value is set using the Record Field Properties page in the


A resource class identifies what type of resource that you are planning. There are two types of

resource planning: detailed and aggregate. In detailed resource planning, the system assigns

specific times for a specific resource to start and finish a task. In aggregate planning, the system

combines capacity loads for resources in daily, weekly, or monthly planning buckets. The

number of tasks scheduled in this bucket can be unlimited as long as there are available hours in

the bucket.

Select a Resource Class from one of the following options:

Detail Select Detail if you want to do detailed resource planning,

where the system tracks resource usage down to specific

times.

Time Select Time if you want to do aggregate resource planning

based on the amount of time available in the time bucket

that you select.

Unit Select Unit if you want to do aggregate resource planning

based on the number of units the resources can produce in

a given time bucket.

Select a Utilization state for the resources. Your options are All, Overloaded, and Not

Overloaded. The default is All. Use Overloaded to focus in on resources that are currently over

capacity. Select Not Overloaded to see underutilized capacity.

Select a Resource Code. To define resource codes, you use the Define Resources page and

Define Work Centers page on the Structure Engineering menu. This is an optional field. When it

is left blank, all resources matching the other filter criteria will be loaded into the page for furtherreview.



Select a Planning Server from the available options. To define a Planning server, you use the

Planning Server Definition page in the General Options component of the Define Business Rules

menu. Click the Search button to retrieve the data. All the data that appears in the grid comes

from the Planning server.

If you have selected Ignore Violation as the violation rule and Overloaded as the utilization state,

the respective check boxes will be selected in the row corresponding to the resource.

Allocation Strategy is used only for aggregate resources to determine how you are going to

spread the time/unit capacity over the bucket for the resource. Your options are Start, Finish,

and Proportional. This answers the following question: If the task is stretched across two or

more buckets, should the task, in its entirety, be placed in the first bucket or in the last bucket, or

should it be spread proportionally across all buckets? The default is Proportional. This field is

unavailable for detailed resources.

When you click a Resource Code, the system takes you directly to the Capacity Summary page.

Using the Capacity Summary

Usage Use the Capacity Summary page to inquire about the current status of a

capacity plan. The summary displays horizontal capacity information

for a selected resource.

Object Name PL_CAP_PLAN_SUMM

Navigation Plan Production, Manage Capacity Plan, Capacity Plan

Workbench, Capacity Summary


Access

Requirements




Capacity Summary page

The Capacity Summary mimics the Capacity Spreadsheet, the Aggregate Capacity by Time

Spreadsheet, and the Aggregate Capacity by Unit Spreadsheet available in the Planning engine.

You use the summary to view the required resource in different time buckets. The Unit,

Resource Type, and Resource Code are display-only fields.

This page also enables you to filter your data. After you’ve displayed the capacity summary, you

can define the search criteria further by specifying values in the following fields:

Start Date Default value: round down to Sunday of the current week.

Number of Periods Default value: 7.

Period Duration The option is only available for detailed resources.

Default value is Weekly for detailed resources. For

aggregate resources, this value represents the defined

bucket size for the resource. If you select Weekly, the

system rounds the start date to the Sunday before the start

date that you entered. If you select Monthly, the system

rounds the start date to the first day of the month. If you

select Daily, the system leaves all of your selections alone.

If you select an aggregate resource, then you can’t change the Period Duration.

Use the Planning server field to temporarily change the current server settings.

For more information about connecting to the Planning engine, see PeopleSoft 8.00.01Enterprise Planning PeopleBook, “Setting Up the Enterprise DataLink”.



Click the Search button after you have modified the search criteria. The system displays data

related to your search criteria. The Row Types are hard-coded, and you can’t select which ones

to display. The default row types are:

Available Capacity The total capacity available for utilization.

Required Capacity The amount of capacity being utilized for production.

Down Hours A form of unused capacity that is not occupied (for

detailed resources only). An example is machine

shutdown.

Unused Capacity The leftover capacity (Available Capacity, Required

Capacity, Down Time).

Overloaded Capacity The amount that exceeds the available capacity.

Utilization The ratio between required capacity and available

capacity.

The Past Due column displays data prior to the start date specified in the search criteria.

The dates represent time periods that you specify based on the values in the Start Date and

Number of Periods fields. If you enter the number of periods as 7 and the duration is Weekly,

then there should be seven weekly time periods in the grid. A maximum of 52 periods can bedisplayed for each search.

Click a Required Capacity row type value to display production details that are placing capacityload on the resource for a given time bucket.

Viewing the Resource Load

Usage Use the Resource Load page to display the individual production

operations that make up the load on that resource during that time

bucket.

Object Name PL_CWB3_RL


Workbench, Capacity Summary

Prerequisites Create a Required Capacity on the Capacity Summary page.

Access

Requirements

Click the Required Capacity link on the Capacity Summary page.



Capacity Summary - Resource Load: Operation Details page

The top portion of the page displays search parameters you defined for the summary.

For more information about the parameters, see Defining the Resource Workbench Search

Parameters.

The Start Date/Time, End Date/Time, and Percent Utilization fields show the planning periodfor the resource you selected along with its percentage of use.




Production This is the ID for a production task. The remaining

information in the row relates to this task. When you click

the value, the system displays the Production Details page

containing all operations for the associated production ID

or schedule.

Op Seq (operation

sequence)

This is the routing sequence number on which the

resource is used.

For more information about Production, see Viewing the Production Details.



Operation Details tab


Start Date/Time This is the currently scheduled start date and time for the

operation.

Load Start Date/Time This is the start time the system uses to calculate and

allocate the remaining capacity requirement for the

production task when a portion of the task has been

completed. The system calculates a load duration value

based on the remaining task quantity, then uses that value

with the task end time to establish the load start time.

End Date/Time This is the currently scheduled end times for the

production operation

Actual Load This is the number of hours for all resource types and

represents the capacity requirements for the production

operation.

Percent Load This is the percentage obtained using the formula

operations usage divided by the resource’s capacity in the

bucket.

Status The field displays the current status for the production

operation.

Frozen Flag If this check box is selected, you can’t reschedule the

operation.

Item/Qty tab

Viewing the Item/Qty tab

You can view the Item ID, Item Description, and Remaining Qty (remaining quantity) for this

production. When you click a Production, the system takes you to an update page, where you

can make changes to the production order.





If the production consists of configurable items, the Configuration Code will display in the grid.

If you want to take advantage of unused capacity, you can click the Add Production button to

display a page to add production.

Adding Production

Usage Use the Add Production page to add a production to the Planning server.

Object Name PL_CWB3_RL


Workbench, Capacity Summary, click a Required Capacity, Add

Production

Prerequisites Create a Required Capacity on the Capacity Summary page.

Access

Requirements

Click the Add Production button on the Resource Load page.

Add Production page

The Business Unit defaults from the previous page. Specify an item by selecting an Item ID

from the prompt. Select a Config Code (configuration code) from the prompt.

Enter the End Date/Time, and Order Qty (order quantity) of the production. The Std UOM

(standard unit of measure) represents how the item is quantified. Select a Production Area and

Production Option from the available options.


6 - 1 0 M A N A G I N G T H E C A P A C I T Y P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

If you select the Frozen check box, then you can’t change the date and quantity of the

production.

Click the Apply button to add the production. Click the Return button to return to the previous

page without adding a production task. All production that is added through this workbench is

considered “planned” production.

Viewing the Production Details

Usage Use the Production Details page to display the individual orders that

make up the load on that resource during the specified time bucket.


Navigation Plan Production, Manage Capacity Plan, Use Capacity Workbench,

Capacity Summary

Prerequisites Display the Resource Load.

Access

Requirements

Click a Production value on the Resource Load page.

Production Details page

Click the Apply button to move the production to a different time bucket by changing the dates.

The system automatically returns you to the Production Summary page. Click the Return button

to go back to the previous page without updating any information within the Planning server.

You can change the quantity only if the production status is Planned. You can change thestart/end dates for all production.

If the Frozen Flag check box is selected, you should not make any changes regardless of thestatus.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L M A N A G I N G T H E C A P A C I T Y P L A N 6 - 1 1

Existing Production Orders

If an order is an existing production order, you can make the following changes:

• Reschedule the order.

• Change the order status to Cancel.

• Select or clear the Frozen Flag check box.

Planned Production Orders

If an order is a planned production order, you can make the following changes:

• Reschedule the order.

• Delete the planned order.

• Select or clear the Frozen Flag check box.

• Change the Order Qty.

Viewing the Production Outputs

Usage Use the View Outputs page to display the production outputs.

Object Name PL_VIEW_OUTPUT

Navigation Plan Production, Manage Capacity Plan, Use, Capacity Workbench,

Capacity Summary

Prerequisites Create a production order.

Access

Requirements

Click the View Outputs button on the Production Details page.

View Outputs page



For Output Type, Primary is the main output. Other output types are Co-product, By-product

Waste, and By-product Recycled.

For more information about the types of output, see PeopleSoft 8.00.01 Bills and RoutingsPeopleBook, “Maintaining Bills of Material”.

The Item ID represents the item you are working with. The Schedule Qty (scheduled quantity)

represents the number of units originally scheduled for production and the Remaining Qty

(remaining quantity) displays the number of the original quantity that is left to produce.

The Completed Qty (completed quantity) displays the number of units that have been completed.

The Std UOM (standard unit of measure) represents how the item is counted.

Analyzing the Capacity Plan

When you analyze the capacity plan, you can view the Capacity Summary via the Capacity

Workbench. You can also drill down on a resource to display the production details, add a

production order, change the order quantity, and reschedule tasks. However, if you just want to

view the data without attempting to change it, you can simply access the Capacity Plan Summary.

The difference between the Capacity Summary Workbench and the Capacity Plan Summary isthat the latter is for inquiry only.

Viewing the Capacity Plan Summary

Usage Use the Capacity Plan Summary page to enter search criteria to retrieve

resource information.

Object Name PL_CAP_PLAN_SUMM

Navigation Plan Production, Manage Capacity Plan, Inquire, Capacity Plan

Summary


Access

Requirements




Capacity Plan Summary Page

The top portion of the page displays search parameters you defined for the summary. To further

define your search criteria, you can change the Start Date, Number of Periods, and Planning

Server. Click the Search button to retrieve the capacity summary data.

For more information about how to enter the search criteria, see Defining the Resource

Workbench Search Parameters.

The Row Types are hard coded, and you can’t select which ones to display. The default row

types are:

Available Capacity This is the total capacity available for utilization.

Required Capacity This is the amount of capacity being utilized for

production.

Down Hours This is for detailed resources only and is a form of unused

capacity that is not occupied. An example is machine

shutdown.

Unused Capacity This is the leftover capacity (Available Capacity -

Required Capacity - Down Time).

Overloaded Capacity This is the amount that exceeds the available capacity.

Utilization This is the ratio between Required Capacity and Available

Capacity.

Past Due represents data prior to the start date specified in the search criteria.



The dates represent time periods that you specify based on the Start Date and Number of

Periods. If the number of periods is 7 and the duration is Weekly, then there should be seven

weekly time periods in the grid. A maximum of 52 periods can be displayed per search.

Using the Planning Scorecard to Review Your Capacity Plan

An alternate method to review the capacity plan is through the Scorecard Inquiry page, which

displays the number (counts) of violations relating to Aggregate Capacity. The violations identify

production operations that are scheduled at times that exceed the available capacity in hours orunits on the aggregate resource.

Once you’ve identified the violations, you can address them in many ways. You can run one of

the solvers (Material Planning, Feasible Planning, or Linear Programming) with the parameters

for solving capacity included. You can resolve the capacity problem manually by reschedulingthe over capacity resource or adjusting the available capacity for the period in violation.

For more information about the solving capabilities of the solvers, see “Setting Up the


To reschedule the task manually, you can use the Capacity Workbench to drill down to the

overloaded resource and reschedule or cancel production during overloaded periods.

For more information about the Capacity Workbench, see Defining the Resource Workbench

Search Parameters.

Filtering Capacity Plan Scorecard Data

Usage Use the Planning Scorecard page to enter search criteria to retrieve

aggregate capacity violation counts.

Object Name PL_SCARD_SUMMARY

Navigation Plan Production, Manage Capacity Plan, Inquire, Planning

Scorecard

Prerequisites You must have generated a plan running either the Optimizer or one of

the solvers.

Access

Requirements


established port to import Scorecard data from the Planning engine.



Planning Scorecard page

Select a Planning Server from the available options to display the Aggregate Capacity

violations. Click the Filters button to filter the data and display the Scorecard Filters page, where

you can further define your search criteria.

For more information about changing filters, see “Managing the Master and Material Plans”.

Viewing Capacity Violations

Usage Use the Aggregate Capacity page to review Scorecard constraint

violations for overloaded aggregate resources.

Object Name PL_SC_AGG_CAP

Navigation Plan Production, Manage Capacity Plan, Inquire, Planning

Scorecard, click Aggregate Capacity Filtered Count

Prerequisites Define any filters you want to use in limiting the information that


Access

Requirements


established port. Also, Scorecard violations must exist before the page

is populated.



Capacity Plan Summary - Planning Scorecard - Aggregate Capacity Violations: Resource page




Unit The business unit at which the resource is located.

Assigned Resource This is the aggregate resource that is overloaded.

Resource tab


Start Date/Time This is the currently scheduled start date and time for the

operation.

End Date/Time This is the currently scheduled end times for the

production operation

Load Date/Time This is the time the system uses to calculate and allocate

the remaining capacity requirement for the production task

when a portion of the task has been completed. The

system calculates a load duration value based on the

remaining task quantity, then uses that value with the task

end time to establish the load start time.



Details tab


This tab displays the Resource Class and the Operation (task) involved in the overload.

Item ID tab


This tab includes the Item ID, Description, and Planner Code for the assigned resource in a

specific business unit.





If the assigned resource contains configurable items, the Configuration Code appears in the grid.

For more information about the Planning Scorecard and other constraint violations, see

“Managing the Master and Material Plans”.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O M M I T T I N G T H E P R O D U C T I O N P L A N 7 - 1

C H A P T E R 7

Committing the Production Plan

After you create and solve a plan in the Planning engine, you’ll need to transfer the plan, in the

form of planning messages, back to your PeopleSoft database. Once the data is back in the

PeopleSoft transactional system, the planning messages are available for further review and

processing by production control managers, master schedulers, planner/buyers, and stockroom

managers.

Overview of the Commit Plan Process

Once you create a workable plan in PeopleSoft Production Planning, you bring back the

recommendations into the PeopleSoft transactional system using the Receive Planning Messages

(PLS2000) process. There, the recommendations are distributed into the various components as

planning messages, where they are reviewed and can be acted upon. You can also select to have

messages automatically approved, where applicable, and you only need to apply them wherenecessary.

The information transferred from the Planning engine includes:

• Production Messages: You can select, review, approve, and apply production data.

For more information about production messages, see “Processing Planning Messages in

PeopleSoft Production Management”.

• Production Exceptions: You can select and review exception information for the production

messages.

For more information about production exceptions, see “Processing Planning Messages in

PeopleSoft Production Management”.

• Inventory Transfer Messages: You can select, review, approve, and apply inventory transfer

data.

For more information about inventory transfer messages, see “Processing Planning

Recommendations in PeopleSoft Inventory”.


7 - 2 C O M M I T T I N G T H E P R O D U C T I O N P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

• Inventory Exceptions: You can select and review exception information for the inventory

transfer messages.

For more information about inventory exceptions, see “Processing Planning


• Material Stock Request Messages: You can select and review material stock request data.

For more information about material stock request messages, see “Processing Planning


• Material Stock Request Exceptions: You can review exception information for the material

stock request messages.

For more information about material stock request exceptions, see “Processing Planning


• Purchasing Messages: You can select, review, approve, and apply purchasing data.

For more information about production messages, see “Processing Planning

Recommendations in PeopleSoft Purchasing”.

• Purchasing Exceptions: You can review exception information for the purchasing messages.

For more information about purchasing exceptions, see “Processing Planning

Recommendations in PeopleSoft Purchasing”.

• Sales Order Messages: You can select and approve sales order data.

For more information about production messages, see “Processing Planning

Recommendations in PeopleSoft Order Management”.

• Sales Order Exceptions: You can review exception information for the sales order messages.

For more information about sales order exceptions, see “Processing Planning

Recommendations in PeopleSoft Order Management”.



Receiving Planning Messages (PLS2000)

To transfer the data from the Planning server to the PeopleSoft database, you run the Receive

Planning Messages (PLS2000) process to populate each of the components used to review and (in

some cases) apply the planning messages. You can also generate planning reports with your new

data.

PeopleSoft Production Planning can maintain up to two plans for each business unit at any time.These two plans include:

• One master run of a production plan.

• One simulation run of a production plan.

As PeopleSoft Production Planning creates a new simulation or master plan for the same business

unit group and brings it into the PeopleSoft transactional system, the old simulation or masterplan data is deleted for the business unit.

The Receive Planning Messages (PLS2000) process involves exporting the planning information

out of the Planning server, getting the export information in a file where Process Scheduler can

access it, and writing the information to the PeopleSoft transactional system for further

processing. To facilitate this process, you can set up the Receive Planning Messages run control

to automatically perform these steps. You can optionally perform each of the steps one at a time.

Identifying Planning Message Options

Usage Use the Receive Planning Messages page to identify the planning

message file and approval options for the planning message run.


Navigation Plan Production, Commit Production Plan, Process, Receive

Planning Messages, Receive Planning Messages

Access

Requirements


Process Name PLAN_EXPORT, PLS9001, PLS2000

Process Type Application Engine, SQR



Receive Planning Messages - Receive Planning Messages page

The following elements are common to multiple pages in this application and are defined in the

preface of this PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID, Report

Manager, Process Monitor, and Run button.

Select the PeopleSoft Production Planning business unit Group Code for which you want to

retrieve planning messages.

Receive/Rpt (receive/report) Planning Messages

To receive the planning messages, enter the File Name with the complete path for the location of

the file that is created when exporting the planning information from the planning server. For

example:

c:\temp\v1_PLAN_103198.export_sql

The file must be in a directory that can be accessed by the Process Scheduler, as this file is the

input for the Receive Planning Messages SQR (PLS2000.SQR). The file name is controlled by

the export version number specified on the Planning server page in this component and the Model

ID name specified when creating the data model with the Production DataLink. In this example,

the “v1” is the version number and “PLAN_103198” is the data model ID. These two values areconcatenated with an underscore by the Planning engine when the file is created.

When you use the automatic process to generate the export file and receive the data for the

PeopleSoft transactional system, data for both planning messages and reports is contained within

a single file. If you choose to manually export the planning information, you can export just

message data or just report data. Two command files are provided with the Planning engine to set

the export parameters for messages and reports. These command files are messages.command

and reports.command. When manually exporting the message and report data from the same

planning model, you must change the version number on the Planning Server page to prevent the

files from having the same name and overwriting each other.

If you’re generating a planning report before you transfer planning messages to the PeopleSoft

database, indicate the file name for receiving report data and select the Simulation Run check



box. When you run the Receive Planning Messages (PLS2000) process, PeopleSoft Production

Planning verifies that the content of the export file matches the simulation run status specified

here. If it doesn’t match, the system will write a message to the SQR log file and continue

processing. If you’re receiving planning messages, PeopleSoft Production Planning performs an

additional check to ensure that the planning messages being delivered are from the latest master

run of the Production DataLink. If it isn’t, PeopleSoft Production Planning stops processing the

planning messages it is trying to transfer over from the Planning engine.

If you receive the planning messages and report data simultaneously, you can’t create report

data from a simulation run, because simulation runs don’t pass back message data.

For more information on creating planning reports and generating simulation runs for report

data, see Creating Planning Reports.

Receive Messages Options

Select one of the following Approval Options:

Auto Approve All Select this option to automatically approve all messages

brought over from the Planning engine.

Auto Approve Within

Horizon

Select this option to automatically approve all messages

brought over from the Planning engine based on the

parameters you set in the other fields of this group box.

Manual Approve Select this option if you want to manually approve all

messages in their applicable components.

If you select Auto Approve Within Horizon, the From Date, To Date, and Based on fields

become available for entry. Enter the from date and to date for the horizon, and indicate whether

the horizon is based on the Order End Date, Order Start Date, or Both the order start date and

the order end date.

Select the Receive Master Plan Items check box if you also want to receive planning messages

for Master Plan items.

Verifying Planning Server Settings

Usage Use the Planning Server page to select the default server template for the

Receive Planning Messages (PLS2000) process. You can also use this

page to override your Planning server template defaults. This page

enables you to automatically transfer the export files for messages and

reports from the Planning server to your local server for further

processing by Process Scheduler.




Navigation Plan Production, Commit Production Plan, Process, Receive

Planning Messages, Planning Server

Prerequisites You must have previously defined at least one Planning server template

using the Planning Server Definition page in the Define General Options

menu. Optionally, you can also create your own Planning server

template defaults by using the User Preferences - Planning page in the

Define General Options menu.

Access

Requirements


Process

Name

PLAN_EXPORT, PLS9001, PLS2000

Process Type Application Engine, SQR

Receive Planning Messages - Planning Server page




Planning Server

Depending on how you entered the Receive Planning Messages component, one of the following

will appear in the Planning Server Template Name field:

• If you entered the component by adding a new run control ID and your own Planning server

defaults using the User Preferences - Planning page, your Planning server template will default

into this field. If this is the case, the host and server information you defined for your Planning

server template will default into the host and server fields on this page.

• If you entered the component by adding a new run control ID and you haven’t defined your

own Planning server defaults using the User Preferences - Planning page, the Planning server



template defined as the installation default on the Installation Options - Planning page will

default into this field.

• If you entered the component by selecting an existing run control ID, you’ll have to select a

Planning server template from one of the available options. You use the Planning Server

Definition page in the Define General Options menu to define one or more Planning server

templates.

Once you verify that the Planning server template is correct or you select a Planning server

template, you can use the defaults that populate this page or you can override any of the defaults.

Overriding the defaults impacts only the run control definition; it doesn’t update the server

template definition.

If you want to change the Planning server definition default information for the Planning

Server Definition, you’ll need to change the Planning server definition itself.

Verify or change the Host Name, Host User Name, Host Password, host Platform, Server

Name, server User Name, Server Password, Timeout (seconds), Port, and Export Version.

For more information about these fields, about changing Planning server definition defaults,

or about adding a new Planning server definition, see PeopleSoft 8.00.01 ApplicationFundamentals for FSCM PeopleBook, “Defining Financials and Supply Chain Management

General Options”.

In the Write Export Files To field, indicate where the export files that were created by the

Planning server reside. This is controlled by the configuration parameter EXPORT_PATH in the

configuration file for the Planning server (rpsserver.ini for NT or .rps file for UNIX). The

Receive Planning Messages (PLS2000) process looks for the export files on the Planning server

you specify here. If it was specified when selecting the process job to run, this path name

represents what the File Transfer process uses as the source path name for moving files. The file

name and path on the Receive Planning Messages page is used as the destination path name for

moving files. The path name must end with a forward slash (/) for UNIX, or a backslash (\) for

Windows NT; otherwise, the file transfer won’t take place.

Click the Run button to access the Process Scheduler Request page. Select one or more of the

following options to run the Receive Planning Messages (PLS2000) process using Process

Scheduler:

PLAN_EXPORT

(PLAN_EXPORT)

Select this check box to run the PLAN_EXPORT process.

This process creates the file of the plan data to be

exported.

Receive Planning Messages

(PLPPMSG)

Select this check box to run a multi-step process job that

includes the transfer of the planning message export file to

the host (PLS9001) and the Receive Planning Messages

(PLS2000) process.



Planning Export

(PLPPMSG1)

Select this check box to create the file to be exported

(PLAN_EXPORT), transfer of the planning message

export file to the host (PLS9001), and the Receive

Planning Messages (PLS2000) process.

Receive Planning Messages

(PLS2000)

Select this check box to only receive the planning

messages.

Transfer Export File

(PLS9001)

Select this check box to transfer the export file (PLS9001)

to the host for the Receive Planning Messages (PLS2000)

process.

This is a multi-step process that runs the file transfer, then the Receive Planning Messages

(PLS2000) process. If you have already moved the export files to a location that can be

accessed by Process Scheduler (such as an NTFS file server), you might only need to run the

Receive Planning Messages (PLS2000) process; the export files won’t need to be moved.


Once you run this process, you can generate planning messages and, optionally, the plan report

information to create a planning report. Once you generate these messages, you can review,

approve, and apply them using pages in PeopleSoft Production Management, Inventory, Order

Management, and Purchasing.

For more information about reviewing, approving, and applying planning messages in

PeopleSoft Production Management, see “Processing Planning Messages in PeopleSoft

Production Management”.


PeopleSoft Inventory, see “Processing Planning Recommendations in PeopleSoft

Inventory”.


PeopleSoft Purchasing, see “Processing Planning Recommendations in PeopleSoft

Purchasing”.



For more information about reviewing planning messages in PeopleSoft Order Management,

see “Processing Planning Recommendations in PeopleSoft Order Management”.

Using Unprocessed Messages From a Previous Plan

When you run the Production DataLink, PeopleSoft Production Planning generates transfer order,

purchase order, sales order, and production order messages that you can review and, in most

cases, approve and apply to your PeopleSoft database. You can continue applying messages from

a planning run until the next time the Production DataLink is run for your business unit. Once the

Production DataLink process is run, you can’t apply the messages generated from the last

planning run. This prevents you from creating double supply orders.

The lockout function gives you the visibility to know when planned orders and changes can’t beprocessed. When processing planning messages, this function is system-enforced.

There may be times when you make an error and pull data from the database too early. In these

cases, you might want to go back and review, approve, and apply messages from the last

Production DataLink run. To do this, you’ll need to:

• Change the Lockout status using the Master Plan Data page.

• Review, approve, and apply any additional planning messages from the last Production

DataLink run.

Once you apply all of the planning messages from the last Production DataLink run, generate a

new planning message run. You must do this to accurately reflect the messages that were

processed. When you run the Production DataLink again, it sends data back to the Planning

engine and automatically selects the Lockout check box on this page. If the Lockout check box isselected, it indicates that the previous Production DataLink planning data is now invalid.

Using the Master Plan Data Page

Usage Use the Master Plan Data page to view the last date and time a full

regeneration Production DataLink process was run, the last date that a

net change Production DataLink was run, and whether or not the

planning information has been received back into the PeopleSoft

transactional system. Use this page also to change the lockout status.

Object Name PL_MASTER_PLAN

Navigation Plan Production, Maintain Production Data, Use, Master Plan Data

Access

Requirements

Enter the business unit Group Code that corresponds to the specific

planning messages you want to review.


7 - 1 0 C O M M I T T I N G T H E P R O D U C T I O N P L A N P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Master Plan Data page

This page displays the PeopleSoft Production Planning business unit Group code you selected, as

well as the Date Time (date and time) and Net Change status of the last plan generated for the

business unit group by the Production DataLink. The Processed check box indicates whether the

Receive Planning Message (PLS2000) process was previously run against this plan. You can run

the Receive Planning Messages (PLS2000) process against only a single production plan master

run.

Use the Lockout check box to indicate whether or not you can apply additional planning

messages from the current production plan to your PeopleSoft database.

If the Lockout check box isn’t selected, the current production plan messages can be reviewed,

approved, and applied, and a new Production DataLink process hasn’t been initiated. You can

continue to apply planning messages until you generate a new plan through the Production

DataLink.

If the Lockout check box is selected, a new Production DataLink process has already been

initiated and new messages have been generated. In this case, you can clear the check box to run

the Receive Planning Messages (PLS2000) process. When you clear the check box, you can

access any of the messages from the previous Receive Planning Messages (PLS2000) run. You’ll

have to run the Production DataLink process again before reviewing new planning messages.

The Process Status check box will be selected if the Production DataLink is running; typically,

you shouldn’t select or clear this check box.

Creating Planning Reports

A critical measure of an effective, enterprise-wide planning system is the ability to produce

accurate and timely reports with a minimum of effort. PeopleSoft Production Planning provides

you with the solution: standard supply chain planning reports with the flexibility to select and

classify the information you need. Using the Planning Report, you can create your own report

layout and information with over twenty rows of detailed options.

Understanding Planning Report Options

Using the Planning Report (PLS2001), you can include as much or as little information you need

to make scheduling and forecasting decisions. With this functionality, you can:


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L C O M M I T T I N G T H E P R O D U C T I O N P L A N 7 - 1 1

• Create your own layout. You can standardize the look of your report or you can select

different criteria every time you create a new report. You can also modify the report title and

the row type names or labels.

• Generate supply and demand pegging detail. If you want to review the detailed information

that represents your bucket totals, you can generate supply and demand pegging detail. Thisenables you to print row-by-row supply and demand detail for easier bucket reconciliation.

• Generate reports based on simulation or actual plan data. You have the option of analyzing

“what-if” scenarios by generating reports based on the simulation plan. You can also generatereports based on actual plan data.

In addition, each standard planning report includes the following sections:

• Report header: The header contains standard report information such as the report number,

report name, description, page number, and report run date and time. The header appears foreach item on the report.

• First page: The first page lists your selection criteria. Only the criteria you specified when

setting up your report are printed. If you selected a criterion for sort sequence or subtotal

purposes only, None will appear as the value of the selection criteria, followed by the sort

sequence and subtotal.

• Item attributes: These detail the attributes of each item, such as an item description,

configuration code (if one exists), balance on hand, and selling price.

• Row Types: The row types you specified to be included in the report appear for selected

periods. If you decide to print a detailed report only, the planning report, including the row

types, won’t be printed.

With each report, you can include these optional reporting features:

• Schedule Detail (supply pegging) and Actual Demand Detail (demand pegging).

• Subtotals for each of the specified selection criteria.

Creating Your Own Layout

The planning reports you generate using PeopleSoft Production Planning enable you to create

your own report layout and content. You define the rows you want to include in the report as

well as the sort order and row names. In addition, you can:

• Display up to 13 periods across a page, including those periods that are past due. If there are

more than 13 periods, PeopleSoft Production Planning prints the next 13 periods below the first

13 periods if there is sufficient vertical space. If there isn’t enough space, the next 13 periodsprint on the next page.

• Define the bucket size to use for reporting. You can use days, weeks, months, or a

combination of all three. Including the past due and total columns, you can view up to a

maximum of 54 columns. Daily buckets always occur before weeks in the planning horizon,

and weeks occur before months. Weekly buckets run Sunday through Saturday. Monthly

buckets are by calendar month. PeopleSoft Production Planning uses the beginning date of the



bucket to identify a column.

• Specify if you want to print the Planning Report, the Supply and Demand pegging details, or

both.

• Define your own report title.

• Specify the row types you want to appear in the body of the report. In addition, you can

modify each row type name or label to meet your own reporting needs. You can also

determine the sort sequence of the row type.

Generating Supply and Demand Detail

In addition to creating your own layout, you also have the option to review supply and demand

pegging detail on all reports. This row-by-row detail enables you to reconcile your bucket totals.

Supply Detail

This table describes the detail supply sourcing information that PeopleSoft Production Planning

provides with your detailed report:

Column Explanation

Due Date Actual date the scheduled receipt is expected to be completed or

received.

Order Number Identifies the production ID, transfer order ID, purchase order, or

planned transfer. In the case of planned production, this data field is

blank.

Order Quantity Quantity remaining open on the scheduled receipt.

Order Type Indicates whether the planning data is identified as a purchase order

(PURC), production order (PROD), or transfer order (XFER).

Order Status For production IDs or production schedules: Planned, Entered, Firmed,

Released, or In Process.

For purchase orders: Planned or Open.

For transfer orders: Planned or Open.

Reference For purchase orders: Vendor ID.

For transfer orders: From business unit.

Demand Detail

This table describes the actual demand sourcing information that PeopleSoft Production Planning

provides with your detailed report:

Column Explanation

Required Date Ship date or final assembly start date.



Column Explanation

Order Number Identifies the customer sales order ID, material stock request ID,

production ID, production schedule, or transfer order ID. In the case

of forecast, planned production, or planned transfer, this field is blank.

Quantity Quantity open for customer order, transfer order, or production order.

In the case of a forecast, this is the forecast quantity.

Type Indicates whether the planning data is identified as a customer sales

order (CUST), production order (PROD), transfer order (XFER),

material stock request (MSR), or forecast (FCST).

Status The order status of demand.

For forecasts: Open.

For production IDs or production schedules: Planned, Entered, Firmed,

Released, or In Process.

For sales orders: Open or In Process.

For transfer orders: Planned, Open, Released, or In Transit.

For material stock requests: Open or In Process.

Reference For forecasts: blank.

For material stock requests: Customer ID, if one exists; otherwise, the

customer name if available.

For sales orders: Ship to customer ID.

For production: End item ID.

For transfer orders: Destination business unit.

Understanding Simulation and Master Plan Reporting

If you want to review planning data based on “what-if” scenarios, you can create a planning

report based on the simulated plan. This option is available only if you don’t enter a File Name inthe Receive Planning Messages group box on the Receive Planning Messages page.

When generating reports for a master plan, verify that the Simulation Plan check box is clear on

the Production DataLink component. In this case, you can generate report data at the same time

you’re generating planning messages using the Receive Planning Messages component.

For more information on generating planning messages, including the creation of simulation

and master plans, see Receiving Planning Messages (PLS2000).

Generating the Planning Report (PLS2001)

PeopleSoft Production Planning can maintain up to two plans for each business unit at any given

time in the report tables. These two plans include:



• One simulation run of a production plan.

• One master run of a production plan.

As PeopleSoft Production Planning creates a new simulation or master plan for the same business

unit and imports it into the report tables, the old simulation or master plan is deleted for the

respective business unit.

Before You Begin

The first step in generating a planning report is to process the exported file created at the end of

the planning session. This process retrieves the planning data from the flat file created by the

Export to RDBMS process and places it in the PeopleSoft database.

Once you export the data, you need to retrieve the report data from the planning system. To do

this, use the Receive Planning Messages component.

Defining Selection Criteria

Usage Use the Criteria page in the Planning Report component to define the

selection criteria and sort sequence you want to use to create your report.

You can create a planning report for a particular business unit, or you

can create a very specific report based on defined selection criteria.

Object Name RUN_PLS2001_SEL1

Navigation Plan Production, Commit Production Plan, Report, Planning

Report, Criteria

Access

Requirements


Process

Name

PLS2001

Process Type SQR Report



Planning Report - Criteria report page


preface of this PeopleBook in PeopleBooks Standard Field Definitions: Business Unit and

Language.

Select a PeopleSoft Production Planning business unit Group Code from the available options.

This is required. If you select a group code and don’t define additional selection criteria,

PeopleSoft Production Planning will include planning information for the business unit group.

If you want to create a report with more specific information, you can select from any of the

optional selection criteria:

• Business Unit.

• Item ID. If the item is a configured item, specify the Config Code (configuration code).

• Planner Code.

• Family.

• Category ID.

• Source Code: Make and Buy, Make, or Buy.

• Primary Buyer: This field is available if you’re using PeopleSoft Purchasing.

If you don’t specify an object within any of these criteria, PeopleSoft Production Planning

includes all objects within the criteria for the report. This enables you to print subtotals for the

criteria. For example, if you select a single item ID, you can’t collect subtotal information for the

criteria. If you leave the Item ID field blank, you can specify that you want to see a subtotal forall item IDs based on the defined selection criteria.

Once you determine your selection criteria, you can determine the Sort Sequence for the optional

criteria. For example, you might want the report with Planner Code as a primary sort and

Source Code as a secondary sort. In this case, enter a lower number (such as 1) in the Sort



Sequence field for Planner Code, and a higher number (such as 2) in the Sort Sequence field for

Source Code.

Select the Subtotal check box if you want to view a subtotal for the criteria. In order to printsubtotals on your report, you must specify a sort sequence for that criterion.

Defining Report Options

Usage Use the Criteria2 page in the Planning Report component to specify a

report date range, buckets, and print options.

Object Name RUN_PLS2001_SEL2


Report, Criteria2

Access

Requirements


Process

Name

PLS2001


Planning Report - Criteria2 report page


preface of this PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID and

Language.

Select a Vendor Set ID and a Vendor ID. These fields are available if you’re using PeopleSoft

Purchasing.

Enter a Report Title. You can change the report title every time you generate a new report.

Select one of the following Print Options:



Horizontal Report Only Print all the bucket information without row detail.

Horizontal Report with

Detail

Print all the bucket information with supply and demand

detail.

Supply and Demand Detail Print row-by-row information to view the detail that

makes up your bucket totals.

Bucket Size

Define the bucket size for your report. If you don’t specify reporting buckets, only past due

information is printed.

Although you can change it, the As Of Date edit box defaults to the last receive planning data run

date. The Receive Planning Data Run field displays the date you ran the Production DataLink

process for reports. The As Of Date must be equal to or later than the Receive Planning Data

Run date. In addition, the As Of Date controls what gets included in the past due bucket.

For your buckets, specify how many Days, Weeks, and Months you want to include in your

report. You can also combine days, weeks, and months up to a maximum of 52 columns. Daily

buckets always occur before weeks in the planning horizon, and weeks occur before month.

Weekly buckets run Sunday through Saturday. Monthly buckets are by calendar month. Each

column date is the beginning date of the bucket.

For example, the following entries in the Days, Weeks, and Months edit boxes will create a report

with the first 10 buckets as days, the next 12 as weeks, and the last 5 as months.

• Days: 10

• Weeks: 12

• Months: 5

Specifying Row Types

Usage Use the Row Types and Row Types2 pages in the Planning Report

component to select the row types you want to appear in the body of the

report. In addition, you can change any one of the row type names or

labels that appear in the report.

Object Name RUN_PLS2001_LBL1, RUN_PLS2001_LBL2


Report, Row Types

Plan Enterprise, Commit Enterprise Plan, Report, Planning Report,

Row Types2

Access

Requirements


Process

Name

PLS2001




Planning Report - Row Types report page (1 of 2)

Planning Report - Row Types2 report page (2 of 2)


preface of this PeopleBook in PeopleBooks Standard Field Definitions: Business Unit,

Language.

The following row types are available and supported by PeopleSoft Production Planning, and

they are defined using both these pages:

Actual Forecast Actual planning periods for inventory.

Actual Supply Scheduled receipts from either existing purchase orders,

inventory transfer orders, or production orders.

Actual Supply = Production Supply + Purchased Supply

+ Transfer Supply




Available to Promise (ATP) Determines the projected available inventory that hasn’t

been committed to customer orders. PeopleSoft

Production Planning uses the following algorithm:

ATP = Planned Receipts + Scheduled Receipts - Actual

Demand - Carryover Demand

Planned Receipts + Scheduled Receipts = Total Supply

row type

Total Orders row type + Dependent Demand row type =

Actual Demand.

Carryover demand occurs when ATP is driven below 0 in

a time bucket. If this is the case, supply is consumed from

an earlier time bucket.

ATP is reported as a negative number in the first bucket if

carryover demand isn’t satisfied. PeopleSoft Production

Planning doesn’t print ATP and cumulative ATP in the

Past Due bucket since it doesn’t apply.

Cumulative ATP Cumulative or running total of ATP.

Customer Orders Orders generated by customers.

Days Supply A forward-looking calculation of that period’s Planned On

Hand balance, which determines how many days into the

future that period’s Planned On Hand balance will cover

the Total Demand. In the case where Planned On Hand

isn’t enough to cover some but not all of the Total

Demand for a particular bucket, PeopleSoft Production

Planning prorates the number of days by the ratio of the

Planned On Hand available to the Total Demand. If there

isn’t enough Total Demand through the periods reported,

the Days Supply bucket is blank.

Dependent Demand Demand that occurs when the item is required from

higher-level production assemblies.

Excess Inventory The maximum amount of inventory that is allowable. The

planned inventory on hand should never exceed this

number.

Forecast Expected demand based on sales history, leading

indicators, promotions, and so on.

Inter-unit Orders Demand from transfer orders placed on the source

business unit.

Net Forecast Forecast quantity that was consumed by actual demand.




New Planned Orders The sum of Planned Production, Planned Purchases, and

Planned Transfers.

Planned On Hand Prior period ending on hand + (Total Supply - Total

Demand)

Planned Production Suggested production orders created by PeopleSoft


Planned Purchases Suggested purchase orders created by PeopleSoft


Planned Transfers Suggested transfer orders created by PeopleSoft


Production Supply The scheduled receipts from manufacturing in the form of

production orders.

Projected Inventory Turns How many times per year the inventory is turning based

on quantity:

[(Total Demand/Weighted Average Planned On Hand) x

(365/total days in planning horizon)]

This is quantity-based, rather than a traditional inventory

turns calculation (which is dollar-based).

Projected On Hand Prior period ending on hand + (Actual Supply - Total

Demand)

(This doesn’t include new planned orders.)

Purchased Supply The scheduled receipts from vendors in the form of

purchase orders.

Safety Stock The minimum quantity of stock planned to always be in

inventory to protect against fluctuations in demand or

supply.

Target Inventory Level The average of:

(Safety Stock + Excess Inventory).

Total Demand Defined as the sum of Net Forecast, Customer Orders,

Interunit Orders, and Dependent Demand.

Total Orders This sum of Customer Orders and Interunit Orders.

Total Supply The sum of Actual Supply and New Planned Orders.

Transfer Supply The scheduled receipts from other business units in the

form of transfer orders.



To include a row in the report, select the Incl (include) check box next to the row name.

If you want, you can change the Row Type name by entering the new name in the specified Row

Type edit box.

Once you define the rows you want to include in your report, you can optionally define the Sort

sequence. For example, you might want Forecast as a primary sort and Total Orders as a

secondary sort. In this case, enter a lower number (such as 1) in the Sort field for Forecast, and a

higher number (such as 2) in the Sort field for Total Orders. If you leave any of the Sort edit

boxes blank, PeopleSoft Production Planning prints the sort-sequenced row types first, followed

by the unsorted row types in the default order they appear on these pages.

Click Run to generate the Planning Report (PLS2001).

For more information about Process Scheduler, see PeopleTools 8.12 Process Scheduler

PeopleBook, “Process Scheduler Basics”.

Using the Planning Messages Report (PLS4001)

After you run the Receive Planning Messages (PLS2000) process, you can create a report to

display a list of the messages brought over from the Planning engine. On the Planning MessagesReport, you review the messages brought over based on your selection criteria.

Defining Message Selection Criteria

Usage Use the Planning Messages page to print a report of the planning

messages brought over from Production Planning.

Object Name PL_REVPL_MSG


Messages, Planning Messages

Access

Requirements


Process

Name

PLS4001




Planning Messages - Planning Messages report page


preface of this PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID,

Language, and Unit.

Select the business Unit, Item, and Planner Code to narrow the messages displayed on thereport.

Message Selection

Select the New Order check box to include messages on the report for new orders or the

Existing Order check box to include messages for existing orders. You can select both checkboxes, but you must select at least one.

Report Options

Select the Production check box to include production messages on the report, Transfers to

include inventory transfer messages on the report, or Purchasing to include purchasing messageson the report. You can select more than one check box, but you must select at least one.

Status

Unapproved Select this check box if you want to include messages that

weren’t approved in previous review sessions.

Approved Select this check box if you want to include messages that

were previously approved but not processed.

Processed Select this check box if you want to include messages that

were previously approved and processed.

Expedite Select this check box if you want to include messages that

are required before the planning time fence.



Tolerance Select this check box if you want to include messages with

rescheduling tolerances applied to them.

You can select more than one check box, but you must select at least one.

Message Type

Reschedule Select this check box if you want to include messages for

rescheduled items.

Canceled Select this check box if you want to include messages for

canceled items.

Route Chg (change) Select this check box if you want to include messages for

items with routing changes.

Substitute Select this check box if you want to include messages for

substitute items.

You can select more than one check box, but you must select at least one.

Defining Production, Purchase Order, and Inventory Transfer MessageReporting Options

Usage Use the Messages Prdn/PO/Transfer page to select the production,

purchase order, and inventory message reporting options for the

Planning Message report.

Object Name PL_REVPL_MSG2


Messages, Messages Prdn/PO/Transfer

Access

Requirements


Process

Name

PLS4001




Planning Messages - Messages Prdn/PO/Transfer (production, purchase order, and transfer ordermessage selection) report page


preface of this PeopleBook in PeopleBooks Standard Field Definitions: Run Control ID and

Language.

Production

In the Order Status group box, select the Entered check box to include messages for entered

orders on the report, Firmed to include firmed orders, Released to include released orders, and

In Process to include orders in process. You can select more than one check box, but you must

select at least one.

Select the Production Class you want to use, either Production ID, Production Schedule, or

Both to include messages with that class on the report. Enter Production Start From and To

dates to limit the messages included to those in that date range.

Transfers

Enter a Dest Unit (destination business unit) to include only messages from that unit, and Dest

Planner Cd (destination planner code) to include only messages from that destination planner.

Enter Schedule Date From and To dates to limit the messages included to those in that date

range. Enter Schedule Arrival Date From and To dates to limit the messages included to thosein that date range.

Purchasing

Enter Purchase Start Date From and To dates to limit the messages included to those in that

date range.

Click Run to generate the Planning Messages report (PLS4001).




Displaying Planning Item Use Up Information

PeopleSoft Production Planning provides you the ability to plan for end life of components and

beginning of life for their replacement. When one component replaces another component, it is

generally due to: engineering change, technical upgrades, and cost.

The process for handling useup items includes:

• Determine the phase out date of the component.

• Use up the remaining stock of the old component before introducing the new component into

production.

• Based on the effectivity date of the new component, plan for the purchasing of the new

component, while continuing to use the old stock (manufacturing, transfer orders, sales orders)

until such time as the old component is used up.

Displaying Planning Use Up Information

Usage Use this page to inquire about the item use up information that includes

the quantity on hand at the time of the phase out and final available

quantity.

Object Name PL_USEUP_ITEMS

Navigation Plan Production, Commit Production Plan, Inquire, Planning

Useup, Item Useup

Prerequisites Have determined the phase out date.

Access

Requirements

Enter a Business Unit and Item ID.

Item Useup Inquiry page




preface of this PeopleBook in PeopleBooks Standard Field Definitions: Unit, and Item ID.

Select a Business Unit and enter an Item ID.

At the top of the page, the system displays the following:

Phase Out Date This date indicates when use up logic should go into effect

for the original component. After the phase out date,

supplies will be used but not replenished for the original

component. Any required new supply is generated for the

substitute item after this date. The phase out date field is

the future status date for items identified to be

discontinued. The future status and status date are defined

at the item attributes by Business Unit level.

Projected Use Up Date This is the projected date that the use of the component

will start tapering off without any activity. PeopleSoft

Production Planning populates this field.

QOH at Use Up This is the projected quantity on hand at the time of the

projected use up date. The quantity on hand may or may

not approach zero. PeopleSoft Production Planning

populates this field.

Qty Avail This is the current quantity available from the inventory

system.

The system retrieves the following information in the grid:

• Item ID (Parent Item where the item being queried is used).

• Short Desc (Short description of the parent item)

• Sub Item (Substitute Item)

• Short Desc (Short description of the substitute item)

• Priority (the item substitution priority)

• Qty Avail (quantity available for the substitute item)

Generating the Planning Use Up Report

Usage Use the page to generate an item use up report.

Object Name PL_USEUP_RPT

Navigation Plan Production, Commit Production Plan, Report, Planning Useup

Report, Item Useup Report



Prerequisites Have determined a phase out date.

Access

Requirements

Select a Run Control ID.

Item Useup Report page




Report Request Parameters

Select a business Unit from the list. You can select all items (All) or a range of items (Range).

Click this button to access a page that allows you to select a range of items.

To generate a report, enter a Run Control ID and click the Run button.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G M E S S A G E S I N P E O P L E S O F T P R O D U C T I O N M A N A G E M E N T 8 - 1

C H A P T E R 8

Processing Planning Messages inPeopleSoft Production Management

Once demand has been translated into planned production, PeopleSoft Production Planning

creates planned production and rescheduling recommendations for PeopleSoft Production

Management for execution. Within PeopleSoft Production Management, planned production can

be automatically converted into production IDs and production schedules. In addition,

PeopleSoft Production Planning’s solvers review existing production information from

PeopleSoft Production Management, recommending cancellations to existing orders andrescheduling of existing production at both the operation and production levels.

Overview of the Production Messages Review and ApplicationProcess

After you use PeopleSoft Production Planning’s planning engine to optimize your production

plan, you will want to transfer new and existing production information from Production Planning

to PeopleSoft Production Management. PeopleSoft Production Planning’s functionality enables

you to transfer production plan information back and forth between Production Planning and

PeopleSoft Production Management.

PeopleSoft Manufacturing and Distribution data moves into PeopleSoft Production Planning tocreate a plan. The plan is fed back to Manufacturing and Distribution in the form of messages.

Once PeopleSoft Production Planning creates a Master and/or Material plan, you can transfer the

plan back to PeopleSoft Production Management using the Receive Planning Messages


8 - 2 P R O C E S S I N G P L A N N I N G M E S S A G E S I N P E O P L E S O F T P R O D U C T I O N M A N A G E M E N T P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

component. Once the data is in PeopleSoft Production Management, you can review these

recommendations using the Review Planning Messages component. The steps to process

recommendations and apply them to your production management system are:

• Review and approve the planning messages.

• Apply the approved messages to your production data in PeopleSoft Production Management.

Before You Begin

Before you begin reviewing and applying production messages, you must:

• Generate your Production Plan.

For more information about generating the Production Plan, see “Generating the Production

Plan” and “Setting Up the Production DataLink”.

• Receive the production messages back from the Planning engine through the Receive Planning

Messages (PLS2000) process.

For more information about receiving planning messages, see “Committing the Production

Plan”.

Reviewing Production Messages

Before you apply the recommended changes from the Planning engine for your production data in

PeopleSoft Production Management, you’ll need to review the production messages and indicate

which recommendations are approved for processing. Use the Production Messages component

to review and approved the planning recommendations.

Selecting Production Messages for Review

Usage Use the Message Search page in the Production Messages component to

define the selection criteria for the production messages you want to

review.

Object Name PL_PRODUCTION_SRCH

Navigation Plan Production, Commit Production Plan, Process, Production

Messages, Message Search

Plan Enterprise, Commit Enterprise Plan, Process, Production


Manage Production, Maintain Production, Process, Review

Planning Messages, Message Search



Production Messages - Message Search page

You can narrow the list of messages you want to review by selection any of the following:

Enter a Business Unit (required field) or Item ID.

You can also select a Planner Code. PeopleSoft Production Planning uses planner codes to

provide access to information more efficiently. Planner codes are used to filter information in

most pages and processes in PeopleSoft Production Planning.

Message Selection

You limit the messages displayed by selecting either the New Order or Existing Order check

boxes, or both.

Order Status

You can limit the messages displayed by selecting the Entered, Firmed, Released, In Process,

or Cancel check boxes.

For more information about production statuses, see PeopleSoft 8.00.01 ProductionManagement PeopleBook, “Maintaining Production Orders and Production Schedules”.

Production Class

You can select Production ID, Production Schedule, or Both, to narrow the list of production

messages to those of that class. Once you review and approve the production messages for

production IDs and production schedules, you can automatically apply them using the Apply

Production Messages page.

Production Start Dates

You can select the production start range for the messages displayed by entering From and To

dates to limit the messages displayed to that date range.



Status

Finally, you can select a status for messages you want to review; the default is to review

unapproved messages only. You can select one or more of the following:

Unapproved Select this check box if you want to view messages that


Processed Select this check box if you want to view messages that

were previously approved and processed. In this case,

these messages and the production data have been updated

with PeopleSoft Production Planning’s recommended

changes.

Approved Select this check box if you want to view messages that


Reschedule w/in Tolerance

(reschedule within tolerance)

Select this check box if you want to apply rescheduling

tolerances to the messages you review. If you select this

option, the system filters out any messages that fall within

the schedule in and out tolerances defined for the items

selected.

The Reschedule In Factor sets the tolerance for

recommendations to move an order to an earlier date. The

Reschedule Out Factor sets the tolerance for

recommendations to move an order to a later date.

PeopleSoft Production Planning uses these factors to

automatically approve reschedule recommendations. The

message is approved as long as the number of days

rescheduled falls within the tolerance factor. As a result,

review and approval of these messages aren’t necessary.

For example, if you set both factors to 5 and your

production date is 12/10, PeopleSoft Production Planning

automatically approves any order between the reschedule

in date of 12/5 and reschedule out date of 12/15 without

going to the appropriate review page. This only applies if

the change is a reschedule.

Expedite Select this check box if you want to review messages that


Accepted Select this check box if you want to review messages that

have been previously accepted.

Cutoff Flag Select this check box if you want to review messages for

items that have messages beyond the planning message

fence defined for the item.

After you make your entries, click the Search button to display the messages.



Reviewing the Production Message Summary

After you select the production messages, you review them for approval. The details are broken

down into three pages:

• Production Details

• Details

• Configuration Code

Reviewing the Production Message Summary Production Details

Usage Use the Message Summary: Production Details page in the

Production Messages component to view the production details for

the production messages you want to approve.

Object Name PL_PROD_MSG_SUM


Messages, Message Summary




Planning Messages, Message Summary

Access

Requirements

Enter the Business Unit and whether you want a new and/or existing

orders.

Production Messages - Message Summary: Production Details page

At the top of the page, the business Unit is displayed. You can also select one of the followingProduction Status codes for the business unit: Entered, Firmed, or Released.

For more information about production statuses, see PeopleSoft 8.00.01 Production

Management PeopleBook, “Maintaining Production Orders and Production Schedules”.



Click this button (Set Status) to reset the status of all unprocessed planned production

displayed; unapproved messages are changed to a status of Approved, and the status of

new planned orders changes to the status you select.

Multiple views of this page are available by clicking the tabs in the scrolling area. We



The Approved check box and Item ID are common to all the tabs.

Production Details tab

The system displays the production details of the messages for your approval based on the entries

you made on the previous page. The Item ID, Description, Start Date, Production ID, Total

Qty (total quantity), and PL Status (planning status) values display for each message.

Also displayed is one of the following Production Status codes, which you can change by

selecting another.

To approve a message, select the Approved check box on that line.

Click this button (Approve All) to approve all messages displayed.

Click this button (Reset Approval) to clear any messages approved.

Details tab


The system displays the details of the messages for your approval based on the entries you made

on the previous page. The Item ID and a notification of whether the item has been Processed

display for each message.

Also displayed are whether the item has a New Order or a Route Chg (route change), or a

Reschedule, Canceled, or Substitute status.








The system displays the Configuration Code information of the messages for your approval based

on the entries you made on the previous page. The Item ID and Config Code (configuration

code) display for each message.

Click this button (Set Status) to reset the status of all unprocessed planned production

displayed; unapproved messages are changed to a status of Approved, and the status of

new planned orders changes to the status you select.




Reviewing Production and Operations Detail

Usage Use the Production Messages - Production Detail page to display

production detail for each recommendation.

Object Name PL_PROD_MSG_SUM


Messages, Production Detail




Planning Messages, Production Detail

Access

Requirements

Enter the Business Unit and indicate whether you want new and/or

existing orders.



Production Messages - Production Detail page

At the top of the page, the Item, Production ID, Prdn Type (production type), PL Status

(planning status), production Area, Prdn DueDt (production due date), and Due Shift values

appear. If the item has been approved, the Approved check box is selected.

For each item, the Curr Item (current item), Short Desc (short description), Original Item,

Short Desc (short description), Production ID, and Per (quantity per assembly) also appear.

Click this button (Approved by Auditor) to display the Production Details page.

For more information about the Production Details page, see Viewing Additional Production

Details.

Click this button (Details) to display the Operation Detail page.

For more information about the Operation Detail page, see Viewing Operation Details.




Viewing Additional Production Details

Usage Use the Production Details page to display additional production

details.

Object Name PL_SF_HDR_DETAIL1




Messages


Messages


Planning Messages, Production Detail

Access

Requirements

Click the Approved by Auditor button on the Production Messages -

Production Detail page.

Production Details page

The Production ID, Total Qty (total quantity), and Production Status fields appear at the top of

the page.

The Plan Start date, Start Date, Processed, PL Status (planning status), Plan Due date, Due

Date, Plan Routing, Routing, Plan BOM, and BOM fields also appear.

At the bottom of the page, the Approved, New Order, Route Chg (route change), Canceled,

Reschedule, Substitute, and Frozen Substitutes check boxes appear.

Viewing Operation Details

Usage Use the Operation Detail page to display the details for a production message.

Object Name PL_SF_HDR_DETAIL1

Navigation Plan Production, Commit Production Plan, Process, Production Messages

Plan Enterprise, Commit Enterprise Plan, Process, Production Messages

Manage Production, Maintain Production, Process, Review Planning


Access

Requirements

Click the Details button on the Production Messages - Production Detail page.


8 - 1 0 P R O C E S S I N G P L A N N I N G M E S S A G E S I N P E O P L E S O F T P R O D U C T I O N M A N A G E M E N T P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Operation Detail page

The Op Seq (operation sequence), Plan Start, Start Date, Work Center, Task Code, Plan Due,

Due Date, and Frozen Code fields appear at the top of the page, along with the Reschedule

check box.

Resources

The Resource Type, Crew/Machine/Tool, Description, and Qty Used (quantity used) fieldsalso appear.

Reviewing Production Exceptions

When you run the Receive Planning Messages (PLS2000) process, PeopleSoft Production

Planning generates exception messages. These exception messages are generated because a

change in the production data occurred since the Production DataLink was run, or a violation of abusiness rule occurred, such as an invalid calendar date.

The production exception messages are broken down into three pages:

• Exception Details

• Dates/Quantity


Reviewing Production Exception Details

Usage Use the Exception Details page in the Production Exceptions

component to view the exception details for production messages.

Object Name PL_PROD_EXCEPTION


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G M E S S A G E S I N P E O P L E S O F T P R O D U C T I O N M A N A G E M E N T 8 - 1 1


Exceptions, Review Planning Exceptions




Planning Exceptions

Access

Requirements

Enter the Business Unit and indicate whether you want a new and/or

existing order.

Production Exceptions - Review Planning Exceptions: Exception Details page




The Prdn ID (production ID) and Item ID are common to all the tabs.

Exception Details tab

The system displays the exception details found for the business unit, including Prdn ID

(production ID), Item, Description, and exception Message.



Dates/Qty (dates/quantity) tab

Viewing the Dates/Qty tab

The system displays the date and quantity information of the exceptions found for the business

unit, including Prdn ID (production ID), Item, Start Date, Start Time, Due Date, Due Time,

and Total Qty (total quantity).

Production Exception Configuration Codes tab

Viewing Configuration Code tab

The system displays the configuration code details found for the business unit, including Prdn ID

(production ID), Item, and Config Code (configuration code).

Applying Production Messages

Once you’ve reviewed and approved the planning recommendations, you are ready to apply the

production messages to your production data. When applying the planning messages, PeopleSoftProduction Management will:

• Apply any changes to existing production, including rescheduling production, operation

rescheduling, and alternate routing changes for production in the Firm status. In addition,

production frozen by PeopleSoft Production Planning is automatically applied to production

within PeopleSoft Production Management.

• Cancel any existing production IDs and production schedules recommended for cancellation by

PeopleSoft Production Planning.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G M E S S A G E S I N P E O P L E S O F T P R O D U C T I O N M A N A G E M E N T 8 - 1 3

Applying Production Messages

Usage Use the Apply Production Messages page to process the production

messages you have approved.

Object Name SF_PRDN_PLN_REQ

Navigation Plan Production, Commit Production Plan, Process, Apply

Production Messages

Plan Enterprise, Commit Enterprise Plan, Process, Apply

Production Messages

Manage Production, Maintain Production, Process, Apply

Planning Messages

Access

Requirements

Enter the Run Control ID.

Process Name SFPAPLNS

Process Type COBOL, SQL

Apply Production Messages page




Enter a Request ID and choose the business Unit.

Process Frequency

Choose one of the following for this request:



Once Executes the request the next time this process is

scheduled to run. Once the process runs, the process

frequency is automatically set to Don’t Run.

Always Executes the request every time the process is scheduled

to run.

Don’t Run Ignores the request when the process is scheduled to run.

Planner Code Selection

Select All or a Single planner code. If you select Single, enter the Planner Code; only those

items belonging to that planner will be processed.

Production Selection

You can apply messages for production IDs, production schedules, or both by selecting the

Process Production IDs and Process Production Schedules check boxes accordingly.

Production Message Options

Select the appropriate check box to specify whether you want to:

Convert Planned

Production

Convert planned production into production IDs and

production schedules.

Apply Production Changes Apply production change messages to existing production

IDs and production schedules.

Click the Run button to apply the planning messages using Process Scheduler.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T I N V E N T O R Y 9 - 1

C H A P T E R 9

Processing Planning Recommendationsin PeopleSoft Inventory

Once the recommendations have come back from PeopleSoft Production Planning and have been

received into the system using Receive Planning Messages (PLS2000), you can review, analyze,

and apply inventory transfer messages for PeopleSoft Inventory.

Overview of the Inventory Messages Review and Application Process

PeopleSoft Inventory includes an interface to manage fulfillment of, or changes to, interunit

transfer orders from PeopleSoft Production Planning. Managing the information from PeopleSoft

Production Planning is a two-phase process; information about changes can be reviewed and

analyzed using the Inventory Messages component. Then, the messages you approve are acted on

by the Apply Inventory Messages component.

PeopleSoft Production Planning analyzes PeopleSoft Inventory supply and demand by reading

directly from inventory tables. It then sends interunit transfer messages back to PeopleSoft

Inventory through an interface table.

If a message can’t be processed, it’s marked as an exception and viewed in the Inventory

Exceptions component. Each time the Apply Planning Messages process runs, it attempts toprocess all approved messages for the business unit regardless of error codes.

Before You Begin

Before you begin reviewing and applying inventory messages, you must:




• Receive the inventory messages back from the Planning engine through the Receive Planning



9 - 2 P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T I N V E N T O R Y P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L


Plan”.

Reviewing Inventory Transfer Messages

Before you apply recommended changes from the Planning engine, you’ll need to review the

inventory transfer messages and select those recommendations you want to apply.

Selecting Inventory Transfer Messages for Review

Usage Use the Messages Search page in the Inventory Messages component

to define the selection criteria for the planning inventory transfer

messages you want to review.

Object Name DEM_CHG_SRC_INV

Navigation Plan Production, Commit Production Plan, Process, Inventory

Messages, Messages Search

Plan Enterprise, Commit Enterprise Plan, Process, Inventory


Control Inventory, Fulfill Stock Orders, Use1, Review Planning


Inventory Messages - Messages Search page

You can narrow the list of messages you want to review by selecting any of the following: the

inventory Business Unit (required field), Dest Unit (destination business unit), and Item. You

can also enter a Planner Code to limit the messages to those for that planner, and a Destination

Planner Code to limit to those for the item at the destination business unit.



Schedule Date

To limit the messages retrieved to orders in a specific date range, you can enter a From date and

To date. Only messages related to orders with scheduled ship dates falling within those dates are

retrieved.

Schedule Arrival Date

To limit the messages retrieved to orders with a scheduled arrival date within a specific date

range, you can enter a From date and To date.

Priority

To limit the messages retrieved to orders within a specific priority range, enter a From priority

and To priority.

Message Type

You can select one or more of the following check boxes to limit the messages displayed:

New Select this check box if you want to view messages directing

PeopleSoft Inventory to create new material stock requests.

Reschedule Select this check box if you want to view messages recommending

rescheduling material stock requests.

Reprioritize Select this check box if you want to view messages reprioritized by the

Planning engine by a solver.

Canceled Select this check box if you want to view messages suggesting

cancellations to material stock requests.

Status

To limit the messages to those with a specific status, you can select one or more of the followingcheck boxes:

Unapproved Select this check box if you want to view messages not previously

approved in prior review sessions.

Approved Select this check box if you want to view messages previously

approved but not processed.

Expedite Select this check box if you want to view messages required before the

planning time fence.

Accepted Select this check box if you want to view messages that have been

previously accepted.

Rescheduled w/in

Tolerance

(rescheduled within

tolerance)

Select this check box if you want to apply planning rescheduling

tolerances to messages you review. If you select this option, the

system will filter out any messages that fall within the schedule in and

out tolerances defined for the items selected.



Processed Select this check box if you want to view messages that were

previously approved and processed. In this case, these messages and

the production data has been updated with PeopleSoft Production

Planning’s recommended changes.

Cutoff Select this check box if you want to view messages for items that have

messages beyond the planning message fence defined for them.

The default setting is to review unapproved messages only.

After you make your selections, click the Search button to display the messages.

Reviewing the Inventory Transfer Message Summary Details

Usage Use the Messages Summary: Message Details page in the Inventory

Messages component to review the message detail information for

inventory transfer messages.

Object Name DEM_CHG_SUM_INV


Messages, Messages Summary





Access

Requirements

Enter a Business Unit



Inventory Messages - Messages Summary: Message Detail page

At the top of the page, the Business Unit, Dest Unit (destination business unit), Planner Code,

Destination Planner Code, and Item ID appear. Also displayed are the Schedule Date, Arrival

Date, Priority, Status, and Message Type group boxes.




The Approved check box and message Type are common to all the tabs.

Message Detail tab

For each item message, the message Type, Business Unit, Dest Unit (destination business unit),

Source, Msg ID(message ID), PL Status (planning status), Frozen, Sched Date (schedule date),

and Priority columns appear.

You can display the details for the item by clicking the Details button to display the Message

Detail page.

For more information about the Details button, see Displaying Message Details.






Item Information tab

Viewing the Item Information tab

At the top of the page, the Business Unit, Dest Unit (destination unit), Planner Code,

Destination Planner Code, and Item ID appear. Also displayed are the Schedule Date, Arrival

Date, Priority, Status, and Message Type group boxes.

For each message, the Type, Sched Arrv (scheduled arrival), Item, Description, and Qty Base

(quantity base) appear.




Displaying Message Details

Usage Use the Message Detail page to view details for a specific inventory

message line.

Object Name DEM_CHG_MSD_INV







Access

Requirements

Enter Control ID, then click the Details button for a message on the

Inventory Messages - Messages Summary: Message Detail page.



Message Detail page

The Msg ID (message ID), Status, Msg Type(message type), and Source appear for the

inventory message.

In the Order Details group box, the Unit, Destination Unit, Order No (order number), Order

Line, Sch Line (schedule line), Demand Line, Priority, Item, Planner Cd (planner code), Dest

Planner Cd (destination planner code), Ship Via, Sched Date (schedule date), Sched Arrv

(scheduled arrival), and Qty Base (quantity base) appear for the item.

Click the Return button to go back to the Messages Summary - Message Detail page.

Applying Inventory Transfer Messages

Usage Use the Apply Inventory Messages page to process the inventory

messages you have approved. This process applies the messages so

PeopleSoft Inventory can act on the suggestions made by the Planning

engine.

Object Name DEM_CHG_REQ_INV

Navigation Plan Production, Commit Production Plan, Process, Apply

Inventory Messages, Apply Planning Messages

Plan Enterprise, Commit Enterprise Plan, Process, Apply

Inventory Messages, Apply Planning Messages

Control Inventory, Fulfill Stock Orders, Process, Apply Planning

Messages

Access

Requirements

Enter Control ID.

Process Name INPAPLAN

Process Type COBOL, SQL



Apply Inventory Messages page




Process Frequency

Select one of the following options for the request:

Once Executes the request the next time this process is

scheduled to run. Once the process runs, the process

frequency is automatically set to Don’t Run.

Always Executes the request every time the process is scheduled

to run.

Don’t Run Ignores the request when the process is scheduled to run.

Enter a Request ID and Description and choose the business Unit and Destination Unit.

Planner Code

For the Source and Destination planner codes, select All or a Single planner code. If you select

Single, enter the Planner Code in the field provided; only those items belonging to that planner

will be processed.

Item Selection

Select All or a Single item. If you select Single, enter the Item in the field provided; only thoseitems will be processed.

Click the Run button to apply the planning messages using Process Scheduler.



Reviewing Inventory Exceptions

When you apply the inventory messages and the system finds data errors, exception messages are

generated. These exception messages might have been generated because a change in the

production data occurred since the Production DataLink was run, or because a violation of a

business rule occurred, such as an invalid calendar date.

Reviewing Inventory Planning Exceptions

Usage Use the Review Planning Exception: Planning Exceptions page in the

Inventory Exceptions component to view the exception details for

production messages.

Object Name DEM_CHG_EXD_INV


Exceptions, Review Planning Exception


Exceptions, Review Planning Exception


Exceptions

Access

Requirements

Enter an inventory business unit.

Inventory Exceptions - Review Planning Exception: Planning Exceptions page

The inventory business Unit appears.




The Msg ID (message ID) is common to all the tabs.


9 - 1 0 P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T I N V E N T O R Y P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Planning Exceptions tab

For each line, the system displays the Msg ID (message ID), message Type, Status, Source,

Dest Unit (destination business unit), and Item.

Click the Details link to view more information about the message on the Exception Detail page.

For more information about the Details link, see Viewing Inventory Exception Details.


Viewing the Exception Details tab

For each line the system displays the Msg ID (message ID), Description, Order No (order

number), Order Line, Sched Date (schedule date), Priority, Sch Line (schedule line), and

Demand Ln (demand line).

Viewing Inventory Exception Details

Usage Use the Exception Detail page to display the details for an inventory

exception message.

Object Name DEM_CHG_EXD_INV


Exceptions, Review Planning Exception, Planning Exceptions


Exceptions, Review Planning Exception, Planning Exceptions


Exceptions

Access

Requirements

Click the Details link on the Inventory Exceptions - Review Planning

Exceptions: Planning Exceptions page.


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T I N V E N T O R Y 9 - 1 1

Exception Detail page

The inventory business Unit, Destination Unit, Order No (order number), Order Line, Sch

Line (schedule line), Demand Line, Item code and description, Source, Planner Cd (planner

code), Dest Planner Cd (destination planner code), Ship Via, Sched Date (schedule date),

Schedule Arrv (scheduled arrival), Qty Base (quantity base), and Priority appear.

Click the OK button to return to the Inventory Exceptions - Planning Exceptions page.

Reviewing Material Stock Request Messages

Before you can reserve inventory to fulfill an order from any source, you must approve it. To

approve any of the material stock requests recommended by PeopleSoft Production Planning, you

select and review the material stock request messages.

Selecting Material Stock Request Messages

Usage Use the Messages Search page in the External MSR Messages

component to define the selection criteria for the material stock

request messages you want to review.

Object Name PL_SO_INMSG_SRCH

Navigation Plan Production, Commit Production Plan, Process, External

MSR Messages, Messages Search

Plan Enterprise, Commit Enterprise Plan, Process, External MSR


Control Inventory, Fulfill Stock Orders, Inquire, Planning Date

Changes, Message Search



External MSR Messages - Messages Search page

You can narrow the list of messages you want to review by selecting any of the following:

The inventory business Unit (a required field), Order No (order number), Customer ID, or Item

ID.

Schedule Date

To limit the messages retrieved to orders in a specific date range, you can enter a From date and

To date. Only messages related to orders with scheduled ship dates falling within those dates areretrieved.

After you make your selections, click the Search button to display the messages.

Reviewing the Material Stock Message Summary MSR Details

Usage Use the Messages Summary: MSR Details page in the External MSR

Messages component to review the details of the material stock request

messages.

Object Name PL_SO_INMSG_SUM

Navigation Plan Production, Commit Production Plan, Process, External MSR





Changes, Message Summary

Access

Requirements




External MSR Messages - Messages Summary: MSR Details page

At the top of the page, the business Unit and number of Rows appear.




The Order No (Order Number), Line number and Schedule number are common to all the tabs.

MSR Details tab

For each item message, the Order No (order number), Line, Schedule, Demand Line No

(demand line number), IN Sched DT/TM (inventory schedule date/time), PL Sched DT/TM

(planning schedule date/time), Customer ID, and Qty Requested (quantity requested) appear.

Item/Config Code tab

Viewing the Item/Config Code tab

At the top of the page, the business Unit and number of Rows appear.

For each message, the Order Number, Line, Schedule, Demand Line No (demand line

number), Item, Description, and Config Code (configuration code) appear.

Reviewing Material Stock Request Exceptions

After you review the material stock request messages, there might be exception messages thatwere generated.



Viewing Material Stock Request Exception Details

Usage Use the Exception Details page in the External MSR Exceptions

component to view inventory planning message exceptions.

Object Name PL_SO_EXCEP_IN

Navigation Plan Production, Commit Production Plan, Process, External MSR





Errors, Review Planning Exceptions

Access

Requirements

Enter the Business Unit

External MSR Exceptions - Review Planning Exceptions: Exception Details page

The business Unit appears at the top of the page.




The Order No (order number), Line number and Schedule number are common to all the tabs.


For each exception, the Order No (order number), Line, Schedule, Demand Line No (demand

line number), Message, IN Scheduled Date/Time (inventory schedule date/time), PL Scheduled

Date/Time (planning schedule date/time), and Item appear.





For each exception, the Order No (order number), Line, Schedule, Demand Line No (demand

line number), and Configuration Code appear.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T P U R C H A S I N G 1 0 - 1

C H A P T E R 1 0

Processing Planning Recommendationsin PeopleSoft Purchasing

Once you’ve run the Receive Planning Messages (PLS2000) process, you can review therecommendations made by the Planning engine in the form of purchasing messages.

Overview of the Purchasing Planning Messages Review andApplication Process

Both Peoplesoft Production Management and PeopleSoft Production Planning write their

requested purchase orders to a staging area that is scanned by the background process POStage.

POStage writes the inputs to a temporary staging area called PO Staging tables in preparation for

sourcing to a purchase order.

When PeopleSoft Production Planning has made an adjustment to an existing purchase order, or

has suggested that a purchase order be created, a message is loaded into PeopleSoft Purchasing.

You review and approve these messages in much the same way that you handle production

messages.

After you approve the purchasing messages, they are “applied” in PeopleSoft Purchasing by

loading them into purchase order staging tables. If new purchase orders need to be created, they

are built using the purchase order build process. Changes can be made from approved changeorder requests using the change order process.

Before You Begin

Before you begin reviewing and applying purchasing messages, you must:




• Receive the purchasing messages back from the Planning engine through the Receive Planning



1 0 - 2 P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T P U R C H A S I N G P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L


Plan”.

Reviewing Purchasing Messages

Before you apply the recommended changes from the Planning engine for your purchase orders,

you might need to review the purchasing messages and indicate which recommendations are

approved for further processing. Use the Purchasing Messages component to review andapproved the planning recommendations.

Selecting Purchasing Messages for Review

Usage Use the Message Search page in the Purchasing Messages component

to define the selection criteria for the purchasing messages you want to

view.

Object Name PL_PO_MSG_SRCH

Navigation Plan Production, Commit Production Plan, Process, Purchasing


Plan Enterprise, Commit Enterprise Plan, Process, Purchasing


Administer Procurement, Manage Purchase Orders, Use, Review

Planning Messages, Message Search

Purchasing Messages - Message Search page


Inventory Unit (required field), Item ID, or Buyer Name.



You can also select a Planner Code to access information more efficiently. Planner codes are

used to filter information in most pages and processes in PeopleSoft Production Planning.

You can select the start range by entering From and To dates to limit the messages displayed tothat date range.

Msg Selection (message selection)

You limit the messages displayed by selecting either the New Order or the Existing Order

check box, or both. You must select at least one check box here.

Message Type

You limit the messages displayed by selecting either the Reschedule or the Canceled check box.

Status

You limit the messages displayed by selecting either the Unapproved or the Approved check

box, or both. You must select at least one check box here.

Unapproved Select this check box if you want to view messages that


Approved Select this check box if you want to view messages that


In addition, you can select one or more of the following:

Processed Select this check box if you want to view messages that

were previously approved and processed. In this case,

these messages and the purchasing data have been updated

with PeopleSoft Production Planning’s recommended

changes.



Reschedule w/in Tolerance

(reschedule within tolerance)

Select this check box if you want to apply rescheduling

tolerances to the messages you review. If you select this

option, the system filters out any messages that fall within

the schedule in and out tolerances defined for the items

selected.

The Reschedule In Factor sets the tolerance for

recommendations to move an order to an earlier date. The

Reschedule Out Factor sets the tolerance for

recommendations to move an order to a later date.

PeopleSoft Production Planning uses these factors to

automatically approve reschedule recommendations. The

message is approved as long as the number of days

rescheduled falls within the tolerance factor. As a result,

review and approval of these messages isn’t necessary.

For example, if you set both factors to 5 and your

production date is 12/10, PeopleSoft Production Planning

automatically approves any order between the reschedule

in date of 12/5 and reschedule out date of 12/15 without

going to the appropriate review page. This applies only if

the change is a reschedule.

Expedite Select this check box if you want to review messages that


Accepted Select this check box if you want to review messages that

have been previously accepted.

Cutoff Flag Select this check box if you want to review messages for

items that have messages beyond the planning message

fence defined for the item.

After you make your entries, click the Search button to display the messages.

Reviewing the Purchasing Message Summary: PO Details

Usage Use the Message Summary: PO Details page in the Purchasing

Messages component to review purchase order details of the purchasing

messages for approval.

Object Name PL_PO_MSG_SUM






Planning Messages, Message Summary



Access

Requirements

Enter a Business Unit and whether to view new and/or existing orders.

Purchasing Messages - Message Summary: PO Details page

At the top of the page, the Business Unit and number of Rows appear.




The Approved check box and PO type are common to all the tabs.

PO Details tab

For each item message, the PO type, Line, Sched Num (schedule number) Item ID,

Description, Rel Date (release date), and Due Date appear.






Qty/Status Details tab

Viewing the Qty/Status Details tab

For each item message, the PO type, Line, Sched Num (schedule number), Plan’d Qty (planned

quantity), Std UOM (standard unit of measure), Frozen status, and PL Status (planning status)appear.

Also displayed are Ovr Vendor (override vendor), Reschedule, Canceled, and Processed checkboxes.







For each item message, the PO type, Line, Sched Num (schedule number), and Config Code

(configuration code) appear.






Reviewing Purchasing Exceptions

When you run the Receive Planning Messages page in the Run PO process, PeopleSoft

Purchasing generates exception messages. These exception messages are generated because a

change in the purchasing data occurred since the PO process was run, or because a violation of a

business rule occurred, such as an invalid calendar date.

Information about the purchasing exception messages is provided in three pages:

• Exception Details

• PO Dates


Reviewing Purchasing Exception Details

Usage Use the Exception Details page in the PO Exceptions component to

view the purchasing message exceptions.

Object Name PL_PROD_EXCEPTION


Exceptions, PO Exceptions


Exceptions, PO Exceptions


Planning Exceptions, PO Exceptions

Access

Requirements


Purchasing Exceptions - PO Exceptions: Exception Details page






The Item number, Description, PO type, Line number and Sched Num (schedule number) are

common to all tabs.


The system displays the exception details found for the business unit, including Item,

Description, PO number (purchase order number), Line number, Sched Num (schedule

number), and exception Message.

PO Dates tab

Viewing the PO Dates tab

The system displays the date and quantity information of the exceptions found for the business

unit, including Item, Description, PO number (purchase order number), Line, Sched Num

(schedule number), Release Date, and Delivery Due Date from PO (delivery due date frompurchase order).

Configuration Code


The system displays the configuration code details found for the business unit, including Item,

Description, PO (purchase order), Line, Sched Num (schedule number), and Config Code

(configuration code).

Applying Purchase Messages

After you have reviewed and approved the purchasing messages, the data is “applied” as follows:



• The PO Stage Load process (PO_POSTAGE) in PeopleSoft Purchasing looks for purchase

order and change order requests. Purchase order requests are loaded onto the purchase order

stage tables. Change order requests are loaded onto the change request stage tables.

• The rows for purchase order requests on the purchase order stage tables are converted into

purchase orders by the PO Calculations process (PO_POCALC) and the Create PurchaseOrders (PO_POCREATE) process.

• The rows for change order requests on the change request stage tables are converted into

change orders by the Change Purchase Order process (PO_POCHNG).

For more information about the PO Stage Load process, see PeopleSoft 8.00.01 Purchasing

PeopleBook, “Understanding Purchase Order Sourcing”.

For more information about the PO Calculations process, see PeopleSoft 8.00.01 Purchasing

PeopleBook, “Understanding Purchase Order Sourcing”.

For more information about the Create Purchase Orders process, see PeopleSoft 8.00.01

Purchasing PeopleBook, “Understanding Purchase Order Sourcing”.

For more information about the Change Purchase Order process, see PeopleSoft 8.00.01

Purchasing PeopleBook, “Creating Change Orders”

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T O R D E R M A N A G E M E N T 1 1 - 1

C H A P T E R 1 1

Processing Planning Recommendationsin PeopleSoft Order Management

Once you’ve run the Receive Planning Messages (PLS2000) process, you can review the

recommendations made by the Planning engine. When demand outpaces supply, it might become

necessary for the planning solvers to make scheduling changes to a customer order while making

a feasible plan. In addition, the Planner might have manually made changes to the customerorders within the planning model.

Overview of the Order Management Planning Messages ReviewProcess

Using the inquiry pages in PeopleSoft Production Planning, you can review these rescheduled

shipment dates. Additionally, you can view the date change exceptions based on the customer

calendar or changes in the transaction system. The sales order message pages are used for inquiry

only; you must use the features in PeopleSoft Order Management to make any changes.

Before You Begin

Before you begin reviewing and applying sales order messages, you must:




• Receive the sales order messages back from the Planning engine through the Receive Planning


For more information about receiving planning messages, “Committing the Production

Plan”.


1 1 - 2 P R O C E S S I N G P L A N N I N G R E C O M M E N D A T I O N S I N P E O P L E S O F T O R D E R M A N A G E M E N T P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Reviewing Sales Order Messages

During the Receive Planning Message process, the system compares the exported sales order

from PeopleSoft Production Planning with the actual sales orders in PeopleSoft Order

Management. Based on material and capacity constraints, PeopleSoft Production Planning will

suggest rescheduling ship dates for orders that can’t be shipped on the customer-requested ship

date or the promise date.

You can direct rescheduling of demand by establishing demand priorities and lateness tolerance

rules.

For more information about demand prioritization, see “Setting Up Production Planning”.

For more information about lateness tolerance rules, see “Setting Up Production Planning”.

You can select and review the Sales Order Messages component.

Selecting Sales Order Messages for Review

Usage Use the Message Search page in the Sales Order Messages component

to define the selection criteria for the sales order messages you want to

review.

Object Name PL_SO_OMMSG_SRCH

Navigation Plan Production, Commit Production Plan, Process, Sales Order


Plan Enterprise, Commit Enterprise Plan, Process, Sales Order


Sales Order Messages - Message Search page




Select the OM Unit (Order Management business unit) for the sales order messages you want to

review. This is a required field.

Select the Order Number, Ship From business unit, and Ship To Customer to limit the

messages to orders with those parameters. You can also enter a Product ID.

Schedule Date

You can enter a From date and To date to narrow your search.

After you have made your selections, click the Search button to view the data.

Reviewing the Sales Order Message Summary

After you select the sales messages, you review them for approval. The details are provided on

three pages:

• Sales Order Details

• Customer/Product ID


Reviewing Message Summary: Sales Order Details

Usage Use the Message Summary: Sales Order Details page in the Sales

Order Messages component to review sales order details of the sales

order messages for approval.

Object Name PL_SO_OMMSG_SUM





Access

Requirements

Enter an Order Management Business Unit.



Sales Order Messages - Message Summary: Sales Order Details page

For each line, the Ship From, Order No (order number), Line, Schedule, OM Sched DT/TM

(Order Management scheduled date/time), PL Sched DT/TM (Planning scheduled date/time),

Schedule Status, and Qty Sched (quantity scheduled) appear.




The Ship From, Order No (order number), Line number, and Schedule number are common toall tabs.

Customer/Product ID tab

Viewing the Customer/Product ID tab

For each line, the Ship From, Order No (order number), Line, Schedule, Ship To Customer,

Product ID, and Req Ship (requested ship) appear.





For each line, the Ship From, Order No (order number), Line, Schedule, and Config Code

(configuration code) appear.

Reviewing Sales Order Exceptions

The Planning engine generates exception messages when the rescheduled shipment date of a sales

order is invalid based on the shipment exception calendar defined at the inventory business unit

and customer levels. Additionally, net change conditions (when, for example, a sales order ismodified after being extracted into the planning model) also appear as exceptions.

Reviewing the Sales Order Exception Details

Usage Use the Exception Details page in the Sales Order Exceptions

component to review information about exceptions for your sales

orders.

Object Name PL_SO_EXCEP_OM





Access

Requirements

Enter an Order Management Business Unit.

Sales Order Exceptions - Review Planning Exceptions: Exception Details page

The Order Management business Unit appears at the top of the page.






The Ship From, Order No (order number) Line number, and Schedule number are common to

all tabs.


For each line the system displays the Ship From business unit, Order No (order number), Line

number, Schedule number, a brief Message, OM Scheduled Date/Time (Order Management

scheduled date/time), and PL Scheduled Date/Time (Planning scheduled date/time), and

Product ID.



For each line the system displays the Ship From business unit, Order No (order number), Line

number, Schedule number, and Configuration Code.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L P E O P L E S O F T P R O D U C T I O N P L A N N I N G R E P O R T D E S C R I P T I O N S 1 2 - 1

C H A P T E R 1 2

PeopleSoft Production Planning ReportDescriptions

PeopleSoft applications offer a wide range of query and reporting possibilities. In addition to the

standard reports that we deliver, we also provide reporting tools that you can use to create new

reports from scratch.

In this chapter, we provide you with a list of reports provided with PeopleSoft Production

Planning.

For more information about the reporting tools used to generate reports using PeopleSoft

applications, see PeopleTools 8.12 Introduction to PeopleSoft Reporting PeopleBook,“PeopleSoft Reporting Tools”.

PeopleSoft Production Planning Standard Reports

The following is a list of the reports provided with PeopleSoft Production Planning:

Report ID Report Name Report Description Report Type

PLS3000 Planning Data

Inconsistency

Report

Lists items to be planned and validates

items currently planned. Can identify

planned components with invalid routing

sequence numbers, manufactured items

with no routing in the routing table,

item/production areas with no valid

routing, routings with no item/production

area, routings with no planning times,

items with routings with no default

production areas. Also verifies if Master

Plan items only have master and material

components, or only have material

components.

SQR


1 2 - 2 P E O P L E S O F T P R O D U C T I O N P L A N N I N G R E P O R T D E S C R I P T I O N S P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

Report ID Report Name Report Description Report Type

PLS2001 Planning

Report

Lists all the information for business unit ,

and can include as much or as little

information needed to make scheduling

and forecasting decisions. Can create

custom layouts, generate supply and

demand pegging detail, and generate

reports based on simulation or actual plan

data.

SQR

PLS4001 Planning

Messages

Report

Lists messages brought over from the

Planning engine as recommendations for

PeopleSoft Production Management,

PeopleSoft Inventory, PeopleSoft

Purchasing, and PeopleSoft Order

Management. Can include new or

existing orders; production, transfer, or

purchasing messages; unapproved,

approved, processed, expedited, or

tolerance messages; and rescheduled,

cancelled, routing change, and substitute

types. Further parameters that can be

selected include order status, production

class, production start and end dates,

destination business unit, destination

planner code, schedule date, schedule

arrival date, and purchase start date.

SQR

PLS4002 Item Use-up

Report

Lists all discontinued items with the

projected use-up dates. For each item,

lists short description, substitute item

priority, and quantity available.

SQR

Standard Financial Reports

For more information about standard financial reports, see PeopleSoft 8.00.01 Setting UpYour Manufacturing System PeopleBook, “PeopleSoft Manufacturing Report Descriptions”.

P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L I N D E X 1

Index

A

active Roll Forward phase 2-18

Actual Supply row type 5-9

Add Production button 5-21

Add Production page - Capacity Plan Summary

component 6-9

Add Production page - Material or Master Plan

Summary component 5-22

Add Purchase button 5-21

Add Purchases page - Material or Master Plan


Add Row Type button 5-13

Add Transfer button 5-21

Add Transfers page - Material or Master Plan


Advanced Filters page - Material or Master Plan

Exceptions component 5-39

advantages of PeopleSoft Production Planning 1-4

aggregate capacity

using constraints 5-60

violations 5-59

Aggregate Capacity Violations Configuration Code

page - Planning Scorecard - Capacity Plan Summary

component 6-17

Aggregate Capacity Violations Details page - Planning

Scorecard - Capacity Plan Summary component

6-17

Aggregate Capacity Violations Item ID page -

Planning Scorecard - Capacity Plan Summary

component 6-17

Aggregate Capacity Violations page - Planning

Scorecard - Capacity Plan Summary component

6-15

Aggregate Capacity Violations Resource page -

Planning Scorecard - Capacity Plan Summary

component 6-16

Aggregate Items page 2-10

aggregate items, maintaining 2-10

aggregate resources, using 2-10

Apply button 5-27

Apply Inventory Messages page 9-7

Apply Production Messages page 8-13

attributes

defining planning 2-21

setting up for production planning 2-10

B

back-loaded forecast 3-38

Balancing page - Line Schedule Editor component

2-58

balancing resource defaults, setting up 2-58

bar colors

defining 2-60

setting up filters 2-62

Bar Colors Filters page - Line Schedule Editor -

Filters component 2-62

Bar Colors page - Line Schedule Editor component

2-60

Bar Item Filters page - Line Schedule Editor - Filters

component 2-61

bar item filters, setting up 2-61

bar split duration, setting 2-51

BI (buildable inventory) shortages


violations 5-55

BOM (bill of material), description 2-8

business process for Production Planning 1-5

business units, setting up 2-2

buttons

Add Production 5-21

Add Purchase 5-21

Add Row Type 5-13

Add Transfer 5-21

Apply 5-27

Change Server Settings 5-11

Remove Row Type 5-13

Return 5-27

Search 5-32

Sourcing Template Load 2-31

Update Production Options 2-31

Update Purchasing Options 2-31

Update Transfer Options 2-31

View Outputs 5-27

Workbench Link 5-40

C

canceled forecast quantities 5-63

capacity feasibility 3-15

capacity fence 3-6, 3-31

capacity load start date and time, description 5-61

capacity model 1-13

capacity plan

analyzing 6-12

maintaining 6-1

managing 6-1

prerequisites 6-1

reviewing summary 6-12

using 6-4


I N D E X 2 P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

using the Planning Scorecard 6-14

Capacity Plan Summary - Capacity Summary page

6-12

capacity planning process, overview 6-1

Capacity Summary page 6-4

carrying cost rate 3-32

cell over maximum, setting 2-51

Change Row Types page - Material or Master Plan


Change Server Settings button 5-11

changeover families 2-49

changeover penalties, defining 2-9

color schemes, Line Schedule Editor 2-49

Color Settings page - Line Schedule Editor - General

component 2-53

command file data, setting up 3-55

Command Files page - Production DataLink

component 3-55

commit plan process overview 7-1

Common page - Production DataLink - Solvers

component 3-42

Compress utility 3-6

concatenation codes, defining 2-2

Configuration Code page - Material or Master Plan

Detail component 5-36


Exceptions - Results component 5-43


Planning Scorecard - Aggregate Capacity component

5-61


Planning Scorecard - BI (buildable inventory)

Shortages component 5-57


Planning Scorecard - Excess Stock component

5-55


Planning Scorecard - Promise Dates component

5-53


Planning Scorecard - Request Dates component

5-49


Planning Scorecard - RM (raw material) Shortages

component 5-59


Summary - Show Demand component 5-20


Summary - Show Supply component 5-18

configured items, defining concatenation codes 2-2

constraint violations, descriptions 5-46

constraints 1-11

converting costs 3-29

co-products, description 5-28

cost conversion 3-29

Criteria report page - Planning Report component

7-14

Criteria2 report page - Planning Report component

7-16

currency code 3-29

current time 3-6

Customer Orders row type 5-9

D

data verification process, using 2-63

Date/Customer page - Material or Master Plan

Planning Scorecard - Promise Dates component

5-51

Date/Customer page - Material or Master Plan

Planning Scorecard - Request Dates component

5-47

Dates/Task Name page - Material or Master Plan

Summary - Show Demand component 5-20

Dates/Vendor/Task Name page - Material or Master

Plan Summary - Show Supply component 5-17

delayed forecast quantities 5-63

demand

defining for DataLink 3-36

prioritizing 2-22

setting options 3-36

sourcing 2-27

demand and supply data input example 1-4

demand for consumption, exploding 3-39

demand options, setting for Production DataLink

3-36

Demand page - Production DataLink -

Demand/Supply component 3-36

demand priorities

defining rules 2-24

setting up families 2-6

demand sources for creating prioritization rules

2-25

Dependent Demand row type 5-9

detail resources, using 2-10

Details page - Material or Master Plan Detail

component 5-33

Details page - Material or Master Plan Planning

Scorecard - Aggregate Capacity component 5-61


Scorecard - BI (buildable inventory) Shortages

component 5-57


Scorecard - RM (raw material) Shortages component

5-59

Dimensions page - Line Schedule Editor - General

component 2-52

dynamic data 3-2

E

early fence 3-31

end fence 3-30

end-of-time 3-6



Exception Details page 9-10

Exception Details page - External MSR Exceptions

component 9-14

Exception Details page - PO Exceptions component

10-7

Exception Details page - Production Exceptions

component 8-10

Exception Details page - Sales Order Exceptions

component 11-5

Exception Specific Details page - Material or Master

Plan Exceptions - Results component 5-42

exceptions

reviewing Inventory 9-9

reviewing Inventory Planning 9-9

reviewing material stock request 9-13

reviewing Production 8-10

reviewing Production details 8-10

reviewing Purchasing 10-7

reviewing Purchasing details 10-7

reviewing sales order 11-5

reviewing sales order details 11-5

viewing inventory details 9-10

viewing material stock request details 9-14

Exceptions page - Material or Master Plan Exceptions

- Results component 5-40

Excess Inventory row type 5-9

excess stock


violations 5-54

Expand utility 3-6

exploding demand for consumption 3-39

External MSR Exceptions component - Exception

Details page 9-14

External MSR Messages component - Messages

Search page 9-11

External MSR Messages component - Messages

Summary - MSR Details page 9-12

F

Feasibility Solver page - Production DataLink -

Solvers component 3-47

Feasible Planning page - Generate Plan component

4-8

Feasible Planning Solver 3-12, 3-47

allocating resources 3-17

allowing alternate routings 3-49

allowing item substitution 3-49

allowing material reallocation 3-48

allowing rescheduling of tasks 3-48

checking effectivities 3-20

computing lateness tolerance 3-18

computing weighted priorities 3-18

defining DataLink options 3-47

description 3-4

determining weighted priorities 3-17

ensuring positive on-hand quantity 3-14

ignoring safety stock 3-48

making a plan capacity-feasible 3-48

overview 3-12

planning for capacity feasibility 3-15

proportionally allocating resources 3-17

reducing excess inventory 3-15

reducing lead time 3-14

rescheduling tasks 3-48

satisfying unmet demand 3-13

sourcing allocations 3-14

using the Lateness Phase 3-19

using the Stock Adjustment Phase 3-19

verifying demand priority for frozen tasks 3-13

verifying supply and demand quantities 3-13

filled forecast quantities 5-63

filtered scorecard score 5-45

filtering Planning Scorecard data 5-66

filters defaults, defining 2-61

financial reports 12-2

firm production fence 3-34

forecast consumption 3-38

forecast demand priority 2-25

forecast fulfillment 3-23


violations 5-62

forecast fulfillment fence 3-38

Forecast Items page 2-5

forecast items, defining 2-5

Forecast Percentages page 2-11

forecast product data, defining 2-6

Forecast Products page 2-6

front-loaded forecast 3-38

Frozen Details page - Production DataLink - General

component 3-33

frozen fence offsets, setting 3-33

G

Gantt charts 3-10

General Filters page - Material or Master Plan

Planning Scorecard component 5-66

general options, defining 2-1

General page - Line Schedule Editor - General

component 2-50

General page - Production DataLink - General

component 3-27

generating production plans, prerequisites 4-2

generating the Planning Report (PLS2001)

defining selection criteria 7-14

prerequisites 7-14

global collaboration 1-19

Global Preferences page - Generate Plan component

4-3



H

histogram period of supply 3-41

I

Independent Demand row type 5-9

in-memory plans 1-10

installation options, PeopleSoft Production Planning

2-1

integrated material model 1-13

interactive-planning approach 1-11

inter-unit transfer demand priority 2-25

inventory attributes, defining 2-3

inventory consumption 1-14

Inventory exceptions

reviewing 9-9

viewing details 9-10

Inventory Message component - Message Search page

9-2

Inventory Message component - Message Summary -

Message Detail page 9-4

Inventory message details

displaying 9-6

inventory options, establishing 2-3

Inventory Planning component - Planning Exceptions

page 9-9

inventory supply 1-14

Inventory transfer messages

applying 9-7

reviewing 9-2

reviewing summary details 9-4

selecting for review 9-2

item attributes by unit, defining 2-4

item changeover families, setting up 2-49

Item Changeover Family page 2-49

Item ID page - Material or Master Plan Planning

Scorecard - Safety Stock component 5-50




Scorecard - BI (buildable inventory) Shortages

component 5-55


Scorecard - Excess Stock component 5-54


Scorecard - Forecast Fulfillment component 5-62


Scorecard - Promise Dates component 5-53


Scorecard - Request Dates component 5-49


Scorecard - RM (raw material) Shortages component

5-57

Item Planning Inquiry page 2-41

item substitution 3-22

Item Use-up Report (PLS4002) 12-2

Iterative Repair page - Production DataLink - Solvers

component 3-52

Iterative Repair Solver 3-5, 3-24

defining run time 3-54

processing features 3-25

selecting optimization templates 3-54

setting up 3-52

using iterations 3-53

L

late beyond tolerance, description 2-24

late fence 3-6, 3-31

Late Supplies Inquiry 3-11

late within tolerance, description 2-24

lateness tolerance

computing formulas 3-18

processing conditions 2-24

Lateness Tolerance Rules page 2-26

lateness tolerances

defining 2-26

overview 2-23

level fence 3-31

Line Schedule Color page 2-49

Line Schedule Editor

defining bar colors defaults 2-60

defining color settings 2-53

defining defaults 2-48

defining dimensions 2-52

defining filter defaults 2-61

defining general settings 2-50

defining time periods 2-55

establishing color schemes 2-49

setting up time period for detailed LSE 2-55

using with solvers 3-11

viewing the Line Schedule Editor chart 2-62

Line Schedule Editor, setting up

aggregate time period 2-56

bar color filters 2-62

bar item filters 2-61

resource balances 2-58

resource entry defaults 2-57

Linear Programming (LP) Solver 3-4, 3-20, 3-50

canceling firm-planned orders 3-24

controlling the LP model 3-20

defining DataLink options 3-50

defining plan periods 3-52, 4-14

enforcing constraints 3-21

fulfilling forecasts 3-23

minimizing inventory without excess stock

constraints 3-24

modeling co- and by-products 3-23

modifying LP parameters 3-52

post processing 3-20, 4-13

processing alternate BOMs and routings 3-23

querying variable capacity over time 3-23

rescheduling firm-planned orders 3-24



setting the carrying cost rate 3-52, 4-14

setting the late shipment penalty 3-52, 4-14

sourcing partial orders 3-24

substituting items 3-22

using multiple effectivities with production options

3-23

using objective functions 3-22

using supply and demand transfers 3-24

using-up components 3-22

low-level codes 3-46

LP (linear programming) Solver 3-4, 3-20. See also

Linear Programming (LP) Solver

LP Planning page - Generate Plan component 4-12

LP Solver page - Production DataLink - Solvers

component 3-50

LSE See Line Schedule Editor

M

manufacturing objectives 1-8

manufacturing options, defining 2-8

master plan

analyzing 5-31

changing row types 5-12

changing servers 5-11

creating with the Datalink 3-25

defining advanced filters for exceptions 5-39

defining workbench parameters 5-5

generating 4-1

generation process 4-1

implementing 5-3

maintaining 5-5

maintaining planned orders 5-20

maintaining scheduled receipts 5-13

managing 5-1

overview 5-1

prerequisites 4-2

reporting 7-13

reviewing exceptions 5-36

reviewing the summary 5-32

showing demand 5-18

showing supply 5-15

using the summary 5-7

viewing plan details 5-33

Master Plan Data page 7-9

Master Plan Data page, (defining) 2-12

Master Plan Detail page 5-33

Master Plan Summary page 5-7

Master Plan Workbench page 5-5

master-planning data items, defining data 2-12

material feasible planning options 3-44

material model 1-13

material plan

analyzing 5-31

changing row types 5-12

changing servers 5-11

creating with the Datalink 3-25

defining advanced filters for exceptions 5-39

defining workbench parameters 5-5

generating 4-1

generation process 4-1

implementing 5-4

maintaining 5-5

maintaining planned orders 5-20

maintaining scheduled receipts 5-13

managing 5-1

overview 5-1

prerequisites 4-2


reviewing the summary 5-32

showing demand 5-18

showing supply 5-15

using the summary 5-7

viewing plan details 5-33

Material Plan Detail page 5-33

Material Plan Summary page 5-7

Material Plan Workbench page 5-5

Material Planning page - Generate Plan component

4-5

Material Planning page - Production DataLink -

Solvers component 3-44

Material Planning Solver 3-4, 3-11, 3-44

calculating low-level codes 3-46

consolidating planned purchase orders 3-45

ignoring safety stock 3-46

including capacity in the plan 3-46

overview 3-11

using fixed periods of supply 3-46

using the net-change mode 3-12

using the regenerative mode 3-12

material reallocation 3-48

material requirements planning 1-2. See also MRP

material stock request demand priority 2-25

material stock request exception details 9-14

material stock request messages

reviewing 9-11

reviewing details 9-12


selecting 9-11

maximum deviation, description 5-55

maximum rows to retrieve, using 5-34

Message Details page 9-6

Message Search page - External MSR Messages

component 9-11

Message Search page - Inventory Messages

component 9-2

Message Search page - Production Message

component 8-2

Message Search page - Purchasing Message

component 10-2

Message Search page - Sales Order Messages

component 11-2

Message Summary - Message Details page -

Inventory Messages component 9-4



Message Summary - MSR Details page - External

MSR Messages component 9-12

Message Summary - PO Details page - Purchasing

Messages component 10-4

Message Summary - Production Details page -

Production Messages component 8-5

Message Summary - Sales Order Details page - Sales

Order Messages component 11-3

messages overview process

prerequisites for Inventory 9-1

prerequisites for Order Management 11-1

prerequisites for Production Management 8-2

prerequisites for Purchasing 10-1

Messages Prdn/PO/Transfer report page - Planning

Message component 7-23

model ID, creating 3-28

Modify Resources to Repair option 3-11

MRP approaches to planning 1-2

MRP II process flow example 1-3

N

New Planned Orders row type 5-9

O

objective function 3-20, 3-22

Operation Detail page 8-9

optimization template options 3-54

Optimizer See Iterative Repair Solver

Optimizer/Iterative Repair 3-5, 3-52. See also

Iterative Repair Solver

Optimizer/Iterative Repair Solver 3-24

order management options

establishing 2-3

using 2-6

order modifiers, enforcing 3-31

Order/Operation Details page - Material or Master

Plan Exceptions - Results component 5-41

P

partial-order sourcing 3-24

pegged chains

advantages 3-8

description 3-7

example 3-7

reviewing relationships 3-10

top-level demand 3-8

Pegging Gantt charts 3-10

penalties, changeover 2-9

penalty factor, description 2-15

PeopleSoft Inventory message application

overview of process 9-1

prerequisites 9-1

PeopleSoft Inventory message review


prerequisites 9-1

PeopleSoft Inventory, processing Planning

recommendations 9-1

PeopleSoft Order Management message review


prerequisites 11-1

PeopleSoft Order Management, processing Planning

recommendations 11-1

PeopleSoft Production Management message

application


prerequisites 8-2

PeopleSoft Production Management message review


prerequisites 8-2

PeopleSoft Production Management, processing

Planning recommendations 8-1

PeopleSoft Production Planning

advantages 1-4

analyzing the supply chain model 1-20

collaborating 1-18

consuming inventory 1-14

establishing supply and demand 1-19

integrating material and capacity models 1-13

linking to the enterprise 1-14

maintaining plan data 1-22

managing business processes 1-5

managing capacity plans 6-1. See also capacity

plan

managing master plans 5-1. See also master plan

managing material plans 5-1. See also material

plan

managing shop floors 1-8

moving and balancing the supply chain 1-8

overview 1-1

planning for resources 1-3

reports 12-1

resolving plan constraints 1-17

reviewing plan details 5-33

reviewing plan exceptions 5-36

setting up 2-1

solving factory-specific plans 1-9

supplying inventory 1-14

understanding data flow 1-5

using interactive planning 1-11

using material- and master-planning inquiries

5-2

using plan summaries 5-7

using planning stages 1-5

using production plans 1-10

using reports 1-22

using resources 1-14

using seamless integration 1-6

using the capacity-planning process 1-5

using the master-planning process 1-5

using the material-planning process 1-5



using the Planning Scorecard 5-43

using the Production DataLink 1-16

using the system of record 1-15

using workbenches 5-5

working with constraints 1-11

PeopleSoft Production Planning reports

Item Use-up 12-2

Planning 12-2

Planning Data Inconsistency 12-1

Planning Messages 12-2

standard financial reports 12-2

PeopleSoft Production Planning, use

creating reports 7-10

defining general options 2-1

defining manufacturing data 2-8

defining planning attributes 2-10

generating plans 4-1

setting up business units 2-2

setting up the DataLink 3-1

PeopleSoft Purchasing message review


prerequisites 10-1

PeopleSoft Purchasing, processing Planning

recommendations 10-1

period duration settings 5-8, 5-33

period duration, using with detailed resources 6-5

period of supply 3-41

Periods of Supply row type 5-10

plan currency 3-29

plan details, reviewing 5-33

plan exceptions, reviewing 5-36

plan generation

creating a feasible plans 4-8

creating material-feasible plans 4-5

defining global preferences 4-3

generating plans using the LP Solver 4-12

overview 4-1

selecting a solver 3-42

plan summaries, using 5-7

Plan Summary page - Material or Master Plan

Summary 5-32

plan types

master plan 3-29

setting up for DataLink 3-26

simulation plan 3-29

Planned On Hand row type 5-10

planned orders before planning time fence display

5-38

Planned Orders page - Material or Master Plan


Planned Production row type 5-10

Planned Purchase (maintenance) page - Material or

Master Plan Summary component 5-29

Planned Purchases row type 5-10

Planner/Configuration Code page - Material or Master

Plan Planning Scorecard - Forecast Fulfillment

component 5-63


Plan Planning Scorecard - Safety Stock component

5-51


Plan Planning Scorecard - Transfer Ship Dates

component 5-66

planning attributes

defining 2-21

defining forecast items 2-5

defining forecast product data 2-6

defining inventory 2-3

defining item attributes by units 2-4

defining Manufacturing data 2-8

defining manufacturing options 2-8

defining master-planning data 2-12

defining order management options 2-6

defining product forecast percentages 2-11

defining promise and request dates 2-14

defining purchasing 2-7

defining resource changeover penalties 2-9

defining resources 2-9

defining Roll Forward phases 2-15

defining transfer 2-4

defining work centers 2-22

maintaining aggregate items 2-10

setting up demand priority families 2-6

setting up roll forward parameters 2-16

setting up Roll Forward phases 2-18

setting up stocking periods 2-6

using aggregate resources 2-10

using detail resources 2-10

Planning Attributes page 2-21

planning constraints 1-11

Planning Data Inconsistency Report 12-1

Planning Data Inconsistency Report page 2-63

Planning Data Inconsistency Report, generating

2-63

Planning Data InconsistencyReport (PLS3000) 12-1

Planning Exceptions page - Inventory Exceptions

component 9-9

Planning message options, identifying 7-3

Planning Message Report page

defining inventory transfer message options 7-23

defining production message options 7-23

defining purchase order message options 7-23

Planning Message Report page - Planning Message

component 7-21

Planning messages application

overview of Inventory process 9-1

overview of Production Management process 8-1

Planning Messages component - Message

Prdn/PO/Transfer report page 7-23

Planning Messages component - Planning Messages

report page 7-21

Planning Messages Report (PLS4001) 7-21, 12-2

Planning messages review

overview of Inventory process 9-1

overview of Order Management process 11-1



overview of Production Management process 8-1

overview of Purchasing process 10-1

Planning messages, receiving 7-3

planning model 1-5

planning periods display, setting 5-33

Planning recommendations

processing in PeopleSoft Inventory 9-1

processing in PeopleSoft Order Management

11-1

processing in PeopleSoft Production Management

8-1

processing in PeopleSoft Purchasing 10-1

Planning report

defining report options 7-16

generating 7-13

specifying row types 7-17

Planning Report (PLS2001) 12-2

Planning Report component - Criteria report page

7-14

Planning Report component - Criteria2 report page

7-16

Planning Report component - Row Types report page

7-17

Planning reports

creating layouts 7-11

generating supply and demand detail 7-12

understanding simulation and master plan reporting

7-13

Planning reports options 7-10

Planning Scorecard

filtering data 5-66

implementing 5-44

overview 5-43

using 5-43

Planning Scorecard page - Capacity Plan Summary

component 6-14

Planning Scorecard page - Material or Master Plan

Planning Scorecard component 5-44

Planning Scorecard, reviewing

aggregate capacity violations 5-59

buildable inventory (BI) violations 5-55

excess stock violations 5-54

forecast fulfillment violations 5-62

promise date violations 5-51

raw material (RM) violations 5-57

request date violations 5-47

safety-stock violations 5-50

transfer shipment date violations 5-64

Planning Server page - Production DataLink

component 3-58

Planning Server page - Receive Planning Messages

component 7-5

Planning server settings, verifying 3-58, 7-5

Planning server template 3-59

PLS2000, Receive Planning Messages 7-3

PLS2001, generating 7-13

PLS3000, Planning Inconsistency Report 2-63

PLS4001 Planning Message Report 7-21

PLS5000, Sourcing Template generation 2-38

PO Exceptions component - Exception Details page

10-7

post processing, LP Solver 3-20

previous master plan 3-30

previous plan, using unprocessed messages 7-9

primary items, description 5-28

priority rank 2-25

priority rules 2-23

defining demand sources 2-25

ranking priority 2-25

Priority Rules page 2-24

product forecast percentages, setting 2-11

production

viewing details 6-10

viewing outputs 6-11

Production DataLink 1-16

components 3-1

connecting Planning servers 3-58

controlling data 3-2

including demand and supply 3-36

model data 3-3

process overview 3-1

setting up 3-1

solvers 3-3

Production Demand row type 5-10

Production Detail page - Production Messages

component 8-7

Production Details page 8-8

Production exception details, reviewing 8-10

Production Exceptions component - Exception Details

page 8-10

Production Message component - Message Search

page 8-2

Production message summary

reviewing 8-5


reviewing production and operations details 8-7

Production messages

applying 8-12, 8-13

reviewing 8-2



viewing details 8-8

Production Messages component - Message Summary

- Production Details page 8-5

Production Messages component - Production Detail

page 8-7

Production Options page - Sourcing Inquiry

component 2-44

Production Orders (maintenance) page - Material or


Production Orders page - Capacity Plan Summary

component 6-10

production plan

committing 7-1

creating reports 7-10

production plan constraints, resolving 1-17



Production Planning run options, setting 3-42

Production Supply row type 5-10

Projected On Hand row type 5-10

promise dates

defining 2-14


violations 5-51

Promise/Request Dates page 2-14

proportional allocation by unit or time 3-17

purchase fence 3-30, 3-34

Purchase Options page - Sourcing Inquiry component

2-46

Purchase Supply row type 5-10

purchasing attributes, defining 2-7

Purchasing messages

applying 10-8

reviewing 10-2

reviewing exception details 10-7


reviewing PO details 10-4


Purchasing Messages component - Message Search

page 10-2

Purchasing Messages component - Message Summary

- PO Details page 10-4

purchasing options, establishing 2-3

Q

quotation demand priority 2-25

R

rate type 3-29

raw material (RM) violations 5-57

Receive Planning Messages component - Planning

Server page 7-5

Receive Planning Messages component - Receiving

Planning Messages page 7-3

Receive Planning Messages page - Receive Planning

Messages component 7-3

receiving and shipping calendars, description 5-31

recycle by-products, description 5-28

regenerate sourcing templates 3-31

relative lateness 3-18

released production fence 3-34

Remove Row Type button 5-13

reports 1-22

Item Use-up 12-2

Planning 12-2

Planning Data Inconsistency 12-1

Planning Messages 12-2

standard financial 12-2

request dates

defining 2-14


violations 5-47

reschedule early limit days, description 2-30

resolving production plan constraints 1-17

resource allocation at start or finish of bucket 3-17

resource attributes, defining 2-9

resource changeover penalties, defining 2-9

Resource Load - Configuration Code page - Capacity

Plan Summary component 6-9

Resource Load - Item/Qty page - Capacity Plan


Resource Load - Operation Details page - Capacity

Plan Summary component 6-6, 6-8

resource load, viewing 6-6

Resource page - Material or Master Plan Planning


resource planning 1-3

Resource Workbench page 6-2

Resource Workbench, defining search parameters

6-2

Resources page - Line Schedule Editor component

2-57

resources, description 2-8

retrieving rows of data, description 5-34

Return button, 5-27

RM (raw material) shortages


violations 5-57

roll forward

defining details 3-34


Roll Forward Phase page 2-18

Roll Forward phases

defining 2-15

setting up 2-18

Roll Forward utility

defining parameters 2-16

defining phases 2-15

scheduling example 2-16

selecting supply and demand tasks 2-18

setting up planning attributes 2-16

setting up targets 2-20

tasks available for reschedule 2-19

using time fences 2-19

round component demand 3-41

routings, description 2-8

Row Type report page - Planning Report component

7-17

row types

changing 5-12

descriptions 5-9

summaries 5-8

using 5-13

run types

defining the net-change type 3-29

defining the regenerative type 3-28



I N D E X 1 0 P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L

S

safety stock


violations 5-50

Safety Stock row type 5-10

safety-stock demand priority 2-25

sales order demand priority 2-25

sales order exceptions

reviewing 11-5


Sales Order Exceptions component - Exception

Details page 11-5

sales order messages

reviewing 11-2

reviewing summary 11-3

reviewing summary details 11-3


Sales Order Messages component - Message Search

page 11-2

Sales Order messages component - Message Summary

- Sales Order Details page 11-3

Scheduled Production row type 5-10

Scheduled Purchases row type 5-10

scheduled receipts before current time display 5-38

Scheduled Receipts page - Material or Master Plan


Scheduled Receipts row type 5-10

Scheduled Transfers row type 5-11

seamless integration 1-6

Search button 5-32

search depth 3-32

Selection Criteria page - Material or Master Plan

Exceptions component 5-37

server configuration settings 5-11

Server Configuration Settings page - Material or


shipment task fence 3-34

shipping and receiving calendars, description 5-31

solvers

descriptions 3-4

example 3-9

Feasible Planning 3-4

Feasible Planning Solver overview 3-12

improving plan quality 3-19

Iterative Repair Solver overview 3-24

Iterative Repair/Optimizer 3-5

LP (Linear Programming) Solver overview 3-20

Material Planning 3-4

Material Planning Solver overview 3-11

net-change mode 3-12

pegged-chain processing 3-7

processing sourcing templates 2-28, 2-30

processing steps 3-8

regenerative mode 3-12

running 4-3

selecting for plan generation 3-42

setting DataLink run options 3-42

using time fences 3-5

using with the Production DataLink 3-3

source file data, setting up 3-55

Sourcing Details page 2-29

sourcing inquiry selection criteria, defining 2-41

sourcing options

loading 2-34

using production options 2-27

using purchase options 2-28

using transfer options 2-27

verifying 2-41

Sourcing Template Inquiry page 2-42

Sourcing Template Load button 2-31

sourcing template, viewing details 2-42

sourcing templates

defining 2-29

generating 2-38

generation options 2-28

maintaining manually 2-30

overview 2-27

processing data using solvers 2-28

rescheduling early limit days 2-30

search depth 2-30

setting up 2-28

viewing production option details 2-44

viewing purchase option details 2-46

viewing transfer option details 2-47

Sourcing Templates page 2-38

spreadsheets 3-10

stages of planning 1-5

start fence 3-30

start of time 3-5

Starting On Hand row type 5-11

start-of-time purge 3-31

stocking periods, setting up 2-6

substitute item options 3-41

supply

defining for DataLink 3-40

setting options 3-40

supply and demand data input example 1-4

supply and demand planning 1-19

supply chain

analyzing 1-20

balancing 1-8

moving 1-8

planning for material requirements 1-2

planning for resources 1-2

Supply Chain Viewer 1-21

supply options, setting for DataLink 3-40

Supply page - Production DataLink - Demand/Supply

component 3-40

system of record 1-15

T

Target Inventory Level row type 5-11


P E O P L E S O F T P R O P R I E T A R Y A N D C O N F I D E N T I A L I N D E X 1 1

Task page - Material or Master Plan Detail component

5-36

task property sheets 3-10

task, description 1-10

teardowns, description 5-28

time fences

setting 3-27


time fences used by solvers 3-5

time period for detailed LSE, setting up 2-55

Time Periods (aggregate) page - Line Schedule Editor

- General component 2-56

Time Periods (detail) page - Line Schedule Editor -

General component 2-55

top-level demand 3-8

Total Demand row type 5-11

Total Forecast row type 5-11

Total Orders row type 5-11

total scorecard count 5-45

total scorecard score 5-45

Total Supply row type 5-11

traditional material requirements planning vs.

PeopleSoft Production Planning advanced planning

1-8

traditional material requirements planning, description

1-2

transfer attributes, defining 2-4

transfer demand fence 3-34

transfer demand priority 2-25

Transfer Demand row type 5-11

Transfer Details page - Material or Master Plan

Planning Scorecard - Transfer Ship Dates component

5-64

transfer option, description 5-26

Transfer Options page - Sourcing Inquiry component

2-47

Transfer Orders (maintenance) page - Material or


transfer shipment dates


violations 5-64

transfer supply fence 3-34

Transfer Supply row type 5-11

Transfer Task page - Material or Master Plan Planning

Scorecard - Transfer Ship Dates component 5-65

Type/Item page - Material or Master Plan Summary -

Show Demand component 5-18

Type/Item page - Material or Master Plan Summary -

Show Supply component 5-15

U

Unfulfilled Demand Inquiry 3-11

unprocessed messages 7-9

Update Production Options button 2-31

Update Purchasing Options button 2-31

Update Transfer Options button 2-31

user options, establishing 2-1

V

View Outputs button 5-27

View Outputs page - Capacity Plan Summary

component 6-11

View Outputs page - Material or Master Plan


W

waste by-products, description 5-28

Web-based planning 1-7

weighted priority computation 3-18

WIP (work in progress) details, defining 3-34

WIP/Roll Forward Details page - Production DataLink

- General component 3-34

Work Center Attributes page 2-22

work center attributes, defining 2-22

work center, description 2-8

Workbench Link button 5-40

workbenches, using 5-5

Documents

PeopleSoft 8.00.01 Production Planning PeopleBook