MRP

EnterpriseOne Requirements Planning Preface
This preface discusses:

• products.
• application fundamentals.
Products
This PeopleBook refers to these products:
• EnterpriseOne Inventory Management.
• EnterpriseOne Configurator.
• EnterpriseOne Forecast Management.
• EnterpriseOne Manufacturing – Shop Floor.
• EnterpriseOne Manufacturing – PDM.
• EnterpriseOne Sales Order Entry.
• EnterpriseOne Sales Order Processing.
• EnterpriseOne Procurement and Subcontract Management.
• EnterpriseOne Manufacturing – ETO Foundation.
Application Fundamentals
Additional, essential information describing the setup and design of the system appears in a companion
volume of documentation called EnterpriseOne Product Data Management.
See Also
EnterpriseOne Product Data Management Preface
About These PeopleBooks

A companion PeopleBook called About These PeopleBooks contains general information, including:
• Related documentation, common page elements, and typographical conventions for PeopleBooks.
• Information about using PeopleBooks and managing the PeopleBooks Library.
• Information on the International Organization for Standardization (ISO) country and currency codes
used within PeopleBooks.
• A glossary of useful terms that are used in PeopleBooks.
See Also
About These PeopleBooks Preface
Using PeopleBooks
Managing the Online Library and PeopleBooks
ISO Country and Currency Codes
Page 1 of 135
Glossary of Terms
Getting Started with EnterpriseOne Requirements

Planning
This chapter provides an overview of Requirements Planning and discusses:
• Requirements Planning integrations.
• Requirements Planning implementation.
Requirements Planning Overview

Requirements Planning provides a means for you to use resource planning tools in distribution or
manufacturing environments. Requirements Planning enables you to use supply and demand balancing logic
to create material schedules and detailed production plans that support single-facility or multifacility planning.
With Requirements Planning, you can:
• Generate demand projections that you use as input for the planning and scheduling systems.
• Use capacity planning to ensure that sufficient capacity is available to accomplish the planned
production schedule.
• Generate a distribution or production plan for one facility.
• Produce a single-facility Material Requirements Planning (MRP) schedule for a single item or all
items.
• Compare prospective resource requirements to the capacity that is available in critical work centers.
• Forecast consumption across multiple time periods.
• Set up and generate multilevel master schedules.
• Process work orders with a batch quantity that corresponds to a batch bill of material and use these
orders for MRP processing.
• Set up and use process planning by defining stocking types for the process, defining co-products
and by-products, and generate Master Production Scheduling (MPS) for the process.
• Use repetitive manufacturing for highly repetitive production that relies on a production rate.
• Set up and maintain multifacility plans to define facility relationships at any level of detail for an entire
facility, a product group, master planning family, or an individual item number.
• Set up information for each of the suppliers and for the items that you are planning to purchase to
generate ad-hoc schedules interactively or generate them by running the Supplier Schedule
Generation program.
Requirements Planning Integrations

The Requirements Planning system integrates with these systems:
• Inventory Management
• Base Configurator
• Forecast Management
Page 2 of 135
• Shop Floor Management
• Sales Order Management
• Procurement
• Engineer to Order
The Requirements Planning system works with other EnterpriseOne systems. We discuss integrations
considerations in the implementation chapters in this PeopleBook. Supplemental information about third-
party integrations is located on the Customer Connection website.
Inventory Management
Inventory Management supplies the basic information about each item (or ingredient), such as part number,
description, unit of measure, stocking type, and location.
Base Configurator
Base Configurator supplies information for assemble-to-order and make-to-order items.
Forecast Management
Forecast Management generates sales projections that are used to create demand and develop the master
production schedule.
Shop Floor Management

Shop Floor Management uses the output from requirements planning as the basis for work order creation
and to schedule work activity within the plant.
Sales Order Management

Sales Order Management provides a source of demand for purchased or manufactured items.
Procurement
Procurement uses expected deliver dates and recommends replenishment actions.
Engineer to Order
Engineer to Order supplies information for engineer-to-order and project specific items.
Requirements Planning Implementation

This section provides an overview of the steps that are required to implement Requirements Planning.
In the planning phase of the implementation, take advantage of all sources of information, including the
installation guides and troubleshooting information. A complete list of these resources appears in the preface
in About These PeopleBooks, with information about where to find the most current version of each.
Global Implementation Steps

Before you can implement Requirements Planning, you must complete several global implementation steps.
Global implementation steps are completed by users of many different systems, and are not specific to
Requirements Planning. Depending on the features and functionality that the organization uses, you might
find that it is not necessary to complete all of these steps. This table lists the suggested global
implementation steps for all EnterpriseOne manufacturing products:
Step Reference
1. Set up global UDC tables. See EnterpriseOne Tools 8.95

PeopleBook: Foundation
Page 3 of 135
Step Reference
2. Set up fiscal date patterns. See Setting Up Fiscal Date Patterns.
3. Set up companies. See Setting Up Companies.
4. Set up business units. See Setting Up Business Units.
5. Set up next numbers. See Setting Up Next Numbers.
6. Set up accounts, and the chart of accounts. See Creating the Chart of Accounts.
(Optional)
7. Set up the General Accounting Constants. See Setting Up Constants for General
Accounting.
8. Set up multicurrency processing, including currency See Understanding Multicurrency

codes and exchange rates. Setup.
9. Set up ledger type rules. (Optional) See Setting Up Ledger Type Rules for
General Accounting.
10. Set up address book records. See Entering Address Book Records.
11. Set up default location and printers See EnterpriseOne Tools 8.95
PeopleBook: Foundation
12. Set up branch/plant constants. See Setting Up Inventory Constants.
13. Set up Manufacturing/Distribution Automatic • Setting Up AAIs in Distribution

Accounting Instructions (AAIs). Systems
• Defining Manufacturing AAIs
14. Set up document types. See Setting Up Document Type

Information.
15. Set up shop floor calendars. See Setting Up Shop Floor Calendars.
16. Set up manufacturing constants. See Setting Up Manufacturing

Constants.
Requirements Planning Implementation Steps

This table lists the implementation steps for the Requirements Planning system.
Step Reference
1. Set up supply and demand inclusion See Setting Up Supply and Demand Inclusion
rules. Rules.
2. Set up Inventory Management for See Setting Up Inventory Management for

Requirements Planning. Requirements Planning.
3. Set up quantity type subsets. See Setting Up Quantity Type Subsets.
Page 4 of 135
Step Reference
4. Set up capacity planning. • Determining Available Capacity

• Generating Resource Profiles
Understanding EnterpriseOne Requirements

Planning
This chapter discusses:
• Requirements Planning overview.
• Requirements Planning features.
• Requirements Planning tables.
Requirements Planning Overview

This section provides an overview of requirements planning.
Requirements Planning is part of the Supply Chain Management product line. Supply Chain Management
(SCM) enables you to coordinate inventory, raw materials, and labor resources to deliver products according
to a managed schedule. This closed-loop manufacturing system helps you manage data and optimize
resources across the entire manufacturing and distribution logistics environment. SCM formalizes the
activities of company and operations planning.
Requirements Planning Features

Requirements Planning consists of these features:
Resource and Capacity Planning

Resource and Capacity Planning enables you to prepare a feasible production schedule that reflects demand
forecasts and production capability. Resource and Capacity Planning consists of:
• Resource Requirements Planning (RRP)
Uses a detail or summary forecast to estimate the time and resources that are needed to make a
product family.
• Rough Cut Capacity Planning (RCCP)
Compares the resource requirements from master production scheduling to the capacity that is
available in critical work centers.
You use RCCP to determine whether you should revise the master schedule to create feasible
workloads or improve the use of limited resources.
• Capacity Requirements Planning (CRP)
Compares the material requirements plans to the capacity available in all work centers.
You use CRP to determine whether you should revise the material requirements plan to create
feasible workloads or improve the use of the resources.
Material Planning Operations
Page 5 of 135
Material Planning Operations provides a short-range plan to cover material requirements that are needed to
make a product. Material Planning Operations analyzes demand from all the operational areas, including:
• Central and satellite distribution centers and warehouses.
• Items that are manufactured in both discrete and process environments.
• Engineer-to-order contracted items.
• Maintenance, repair, and operational items for plant and equipment maintenance.
• Supplier-managed inventory.
Material Planning Operations consists of these feature sets:
• Distribution Requirements Planning (DRP)
Plans and controls the distribution of finished goods, based upon demand.
• Master Production Scheduling (MPS)
Creates a schedule of items and quantities that a company expects to manufacture.
• Material Requirements Planning (MRP)
Uses the master production schedule, open orders, bills of material, and inventory records to
calculate time-phased net requirements for every item, and creates a plan for covering material
requirements.
• Multifacility Planning
Provides centralized control of distribution inventories and creates a coordinated replenishment plan.
• Project Requirements Planning (PRP)
Uses work breakdown structures from projects and related bills of material to create replenishment
plans for project items.
PRP
PRP is an option within the MRP/MPS Requirements Planning program (R3482) that you use to generate
replenishment schedules for production orders and components for an end item that are used in a project.
PRP recognizes the shippable items from the project as the supply of the end item and uses this supply to
drive the demand for its components. Thus, the project supplies its own demand.
The system generates dependent demand by using the bill of material (BOM) structure or the work order
parts list that is associated with the end items. Inventory that is acquired either by purchase order receipts or
work order completions for these project-specific items should be used only for meeting the project's
demand.
The system regards the project demand and supply as standalone or independent so that any additional
demand or supply from forecasts, sales orders, work orders, or purchase orders on the end item does not
interfere with the requirement from the project.
Supplier Scheduling Systems

A dependency on goods and services from other organizations has increased the need to establish planning
and information methods between the supplying links of a supply chain.
Through supplier scheduling, planners can provide suppliers with consistent shipping information and
demand profiles to support production and delivery. Planners negotiate order contracts between consumer
and supplier through scheduling tools. Order contracts are often defined as blanket orders with established
quantities for a demand company. When a company forms a supply chain with a scheduling system, a
supplier has accurate data to project plans for demand forecasts, ordering, production, and delivery. A
consuming company benefits because its deliveries from a supplier are dependable. Enterprises can make
point-of-use deliveries from the exact location where the supplier delivers the goods to the production
location that consumes products. Instead of supplying inventory to stores or warehouses for dissemination,
enterprises can deliver from the point of use.
Page 6 of 135
Partnership contracts between companies reduce inventory-carrying costs, production lead times, and time-
to-market for products. An enterprise uses supplier-scheduling methodologies to share planning information
across business boundaries. Scheduling enables contributors to a product line to develop schedules that
originate from known information. When schedules change, especially in dynamic industries such as
electronics and automotive, the demand and supply partners establish communication links to accommodate
changes as quickly as possible.
Requirements Planning Tables

These tables are used throughout the Requirements Planning system:
Table Description
Item Master (F4101) Contains basic information about each item that is defined in
inventory, such as:
• Item numbers and descriptions
• Category codes
• Units of measure
Item Branch File (F4102) Contains warehouse or plant-level information, such as:
• Costs
• Quantities
• Location
• Branch level category codes
• Lead times
• Planning fences
• Order policy codes
Bill of Material Master Contains information at the business unit level about bills of material,
File (F3002) such as:
• Costs and quantities of components.
• Features and options.
• Levels of detail for each bill.
Capacity Message File Contains the action messages that are generated by the RRP, RCCP,
(F3311) and CRP programs.
Forecast File (F3460) Contains the forecast data that MPS uses for calculations and that
RRP validates.
Routing Master File Stores routing information, including operation sequence, work
(F3003) center, run, setup, and machine time.
Work Center Resource Contains the available capacity for each work center by day, month,
Units (F3007) and year.
Work Center Master File Contains detail data about all defined work centers.
(F30006)
Capacity Resource Contains all of the resource profiles that are used in Resource
Profile (F3303) Requirements Planning.
Branch Relationships Contains the supply and demand relationship among the branches.
Master File (F3403)
Page 7 of 135
Table Description
MPS/MRP/DRP Message Contains the action messages that are generated by MPS, MRP, or
File (F3411) DRP.
MPS/MRP/DRP Lower Contains the source of gross requirements that are posted to items
Level Requirements File from parent items.
(F3412)
MPS/MRP/DRP Summary Contains the time series data for forms and reports.
File (F3413)
Supplier Schedule Contains most of the data that controls scheduling arrangements
Master File (F4321) with the supplier. This table also contains information that is required
for creating and maintaining the schedule, including:
• Ship lead time
• Schedule days
• Ship pattern
• Shipment quantity
• Delivery location
The system uses information from the Supplier Schedule Master File
table for each line item on a blanket order that you use in the
supplier scheduling process.
Supplier Schedule Contains the data that identifies predetermined split percentages
Master File (F43211) between suppliers, by item.
Understanding Requirements Planning Concepts

This chapter discusses:
• Single-facility versus multifacility planning.
• Single-level versus multilevel planning.
• Master Production Scheduling and Material Requirements Planning.
• Requirements planning outputs.
• Parallel processing.
Single-Facility versus Multifacility Planning

Single-facility planning encompasses the generation of a distribution or production plan for one facility. All
supply-and-demand data must be within a single branch plant. If an item is available in other branch plants, it
is not considered during single-facility planning.
In contrast, multifacility planning is set up to consider supply and demand for the same item across multiple
facilities. The objective of multifacility planning is to coordinate the distribution or production plan of several
plants that are part of an integrated company. This type of planning is used to provide a number of business
solutions, including:
• Demand consolidation to support centralized procurement for multiple branch plants.
• Demand fulfillment from an alternate branch plant to minimize inventory.
Page 8 of 135
• Demand integration, in which one plant produces semifinished items that are shipped to and
assembled into end item products at another plant.
You define supply-and-demand relationships between branch plants, the system transfers items among the
plants using Sales Order Management and Procurement.
Single-Level versus Multilevel Planning

Single-level planning is the balance of supply and demand of an end item at the sales and operations
planning level. The planning system does not explode down to the lower level components in the bill of
material.
Both manufacturing and distribution companies use single-level planning, depending on their process flows.
Single-level planning is performed for Master Production Scheduling (MPS) and Distribution Requirements
Planning (DRP) to plan end items or families of end items. Single-level planning at the DRP and MPS levels
provides flexibility to manage inventory by specific time buckets, which can be monthly, weekly, or daily.
DRP focuses on processing end items through the planning system. DRP develops messages only for the
purchase of end items; no parent/component relationships exist.
For example, a distribution company that sells material building supplies forecasts faucets as a demand and
purchases what is needed to meet the forecast. The company then sells the faucets to home builders.
MPS uses single-level planning to focus on the end item. It is run prior to Material Requirements Planning
(MRP) to stabilize and firm up the schedule. Thus, single-level MPS does not explode down to lower-level
components in the bill of material. MPS can develop both purchase order and work order messages.
For example, a manufacturer of building materials might buy bathtubs and then sell these end items to
distributors. The manufacturer uses forecast as demand and purchases bathtubs to meet that demand. They
then sell the bathtubs to a distributor. For end items that the manufacturer builds itself, such as faucets, the
company runs single-level MPS to produce work order messages for the faucets. By running single-level
MPS, the manufacturer has the flexibility to change quantities and dates of the end items before sending the
demand to lower-level components such as O-rings, washers, handles, and bolts.
Pegging records do not exist at the highest level of the bill of material structure because that is where the
demand originates.
MRP is multilevel planning. The planning system explodes parent demand from end items down to lower
level components in a bill of material. MRP creates messages for both purchased and lower level
manufactured items.
Pegging can be done to determine the parent source of demand.
Master Production Scheduling and Material Requirements Planning

An MPS is a statement of what the company expects to produce, based on the tactical plan and budget
constraints. A master-scheduled item is critical in its impact on lower-level components or resources, such as
skilled labor, key machines, or revenues. Single-level scheduling implies master scheduling at the item level
of an end deliverable. multilevel master schedules explode planned orders down to component items.
The master scheduling process consists of:
• Determining gross demand (forecast, customer orders, and interplant demand).
• Subtracting what you have (inventory, purchase orders, and work orders).
• Calculating net requirements and determining when you need them.
You can generate a master schedule for all items or for a net-change generation, which includes only items
that have been affected by transactions since the last generation. After you generate the master schedule,
you can review and respond to messages.
MRP uses information from the bill-of-material and inventory records to calculate the time-phased net-
material requirements for every component item and subassembly. MRP suggests a replenishment plan to
support the production of the quantities that are specified in the MPS.
Page 9 of 135
A single-facility requirements plan critically affects lower-level components or resources, such as skilled labor
or revenues. Single-facility implies MRP at the component level.
The MRP process consists of:
• Determining gross demand (forecast, customer orders, work orders, and interplant demands).
• Subtracting what you have (inventory, purchase orders, and work orders).
• Calculating net requirements and when you need them.
You can process a material requirements plan in one of two ways:
• Freeze the MPS and generate MRP.
• Validate the MPS, and then generate a combination of MPS and MRP.
When you process a material requirements plan, the system summarizes gross material requirements for
each assembly, component, and part number for raw material. The requirements plan supports the MPS for
each time period in the planning horizon.
You can generate a material requirements plan for all items or for a net change generation, which includes
only the items that have changed since the last generation. After you generate MRP output, you can review
and respond to messages.
The system uses these inputs to MRP:
• Demand.
• Forecast.
• Sales orders.
• Planned and firm work orders.
• Supply.
• Firm work orders.
• Rate schedules.
• Purchase orders.
• Inventory.
• In-receipt routing.
• Product data.
• Item Branch File data (F4102).
• Bill of Material Master File data (F3002).
The system generates these outputs from MRP:
• Action and warning messages.
• Time series with calculated quantities for:
 Ending Available (EA).
 Available to Promise (ATP).
 Cumulative Available to Promise (CATP).
 Planned orders.
MPS and Manufactured Items

You use MPS to generate the master schedule for manufactured items. The EnterpriseOne systems plan
replenishment for both purchased items and manufactured items in the same generation program.
Processing options control how the system runs the generation.
Page 10 of 135
DRP and Purchased Items
For distribution businesses, DRP provides replenishment plans for items that are purchased and resold in a
distribution environment.
What Are the Differences Between MRP and MPS?

MPS generally has independent demand, while MRP has dependent demand. Independent demand is
demand for an item that is unrelated to the demand for other items, such as demand for finished goods.
Dependent demand is demand that is directly related to or derived from the bill-of-material structure for other
items or end products. MRP might also include forecast and sales orders if items are sold as service (spare)
parts. The majority of demand, however, is demand from parent orders. The demands on MRP include:
• Firm and planned work orders for a parent item.
• Sales orders and forecast for a service part.
• Interplant demands.
You use MRP to generate material plans for lower-level components. Processing options control how the
system runs the generation.
Requirements Planning Outputs

The primary outputs of requirements planning include messages, time series, and planned orders. You need
to know and understand the elements that affect the process, and look for the outputs, including planning
horizons, quantity types, time fences, and planning message definitions. These elements are common for all
types of requirements planning.
Planning Horizons
APICS, the Educational Society for Resource Management, defines a planning horizon as the amount of
time that a plan extends into the future. Planning horizons must be long enough to cover the cumulative lead
time for all low-level components. For higher-level planning, the horizon must be long enough to enable
increased capacity adjustments, if needed. Changes that extend far into the planning horizon can be
managed with little disruption to the planning schedule. Changes closer to the current date or delivery due
date might have significant schedule and cost impacts to the existing plan.
Cumulative lead time should include visibility to all aspects of the plan, including:
• Engineering and development time
• Purchasing lead time
• Manufacturing lead time
• Final assembly lead time
• Delivery time to customer
The following example illustrates a planning horizon:
• Order raw materials: 20 days.
• Produce component items: 20 days.
• Subassembly production: 20 days.
• Final assembly: 20 days.
The planning horizon must be set to include the entire lead time from raw material through final assembly.
Therefore, this planning horizon should be no less than 80 days in length.
Quantity Types (34/QT)

The system uses the quantity type user-defined code (UDC), 34/QT. Quantity types are predefined codes
that define the display data on the time series screens and reports that use the MPS/MRP/DRP Summary
Page 11 of 135
File table (F3413). The quantity types are used by the MRP/MPS Requirements Planning program (R3482)
and Master Planning Schedule - Multiple Plant program (R3483) to calculate supply and demand.
Quantity types are alpha codes that represent various types of supply or demand on the time series. Any
code that is preceded by a + symbol designates supply. Any code that is preceded by a - symbol designates
demand or a reduction of supply. Some quantity types are designated as unadjusted. Unadjusted quantity
types display the original quantity without planning actions. All other quantity types are displayed as if all
planning actions have been processed.
UDC 34/QT codes are hard-coded; however, the descriptions explaining the codes are not hard-coded. If
changes are made to the descriptions, you should document these changes by using the Row menu to
access Attachments. Creating an attachment to the code with a changed description provides an audit trail of
what was changed and why the change was implemented.
Important! You should not change the 34/QT UDC because the MRP/MPS Requirements Planning and
Master Planning Schedule - Multiple Plant programs build calculations for supply and demand based on
these quantity types.
Time Fences and the Time Series

Planning horizons are divided into time frames that establish operation policies or guidelines for prioritizing
activities.
The time fences define how priority decisions are made with respect to scheduling supply to meet demand.
Time fences denote where defined planning rules are applied in balancing the supply to meet existing
demand. Time fences apply to sources of demand that are used to plan calculations. Time fence rules
stipulate how forecast, customer demand, or a mixture of these are used during the netting calculations
when you are establishing the schedule.
Time fences are points in time when you can make changes to either policy or operating procedures.
EnterpriseOne software includes three fences:
• Freeze
• Planning
• Message Display
Fence Function
Type
Freeze The number of days from the generation start date within which the system
Fence (F) should not create or replan order messages. For example, if the generation
start date is January 3, 2005, and the freeze time fence is three days, the
planning system does not display messages with dates prior to or equal to
January 6, 2005.
Imbalances of supply and demand within the freeze fence are planned outside
the freeze fence.
Planning The number of days that the system uses with the time fence rule to determine
Fence (P) how demand is used. Enter the number of days after the generation start date
when the time fence rule changes from the first rule to the second rule. For
example, if the time fence rule is S (customer demand before the time fence,
forecast after the time fence), the generation start date is January 3, 2005, and
the planning time fence is three days, then the system plans according to
customer demand through January 6, 2005. Beginning on January 7, 2005, the
system plans according to the forecast.
Message The number of days after the generation start date within which the system
Display should display messages. For example, if the generation start date is January
Fence (D) 1, 2005, the shop calendar is seven days a week, and the message fence is 30
days, the system displays messages with dates before or equal to January 31,
2005. The system does not display messages with start dates of February 1,
Page 12 of 135
Fence Function
Type
2005 or later. However, the planning horizon for orders continues past this
date and is reflected in available-to-promise totals.
Time fences are a critical input to the master schedule. The time series is the primary output of the master
schedule.
The diagram shows an example of a time series:
Time series
In the Item Master program (P4101), you specify on the Manufacturing Data tab of the Additional System
Information form the number of days after the generation start date to be included in each time fence period.
For time fences:
• The system does not count the generation start date; that is, the day after the generation start date is
day 1.
• For manufactured items, the system counts working days as defined in the Shop Floor Calendar.
• For purchased items, the system counts calendar days.
Each of the fences is displayed on the time series in their respective bucket. Along with the codes F, P, D,
you will also see Level Lead time (L), Manufacturing Lead time (M), and Cumulative Lead time (C).
You can also generate a master schedule for items by using forecast consumption planning rule H. Forecast
consumption occurs when forecasted demand is reduced by actual sales orders received or shipped, up to
the forecasted quantity. By consuming the forecast, you can revise the production schedules to reflect the
most up-to-date information.
MRP Period Calculations Using Planning Fence Rules

MRP supply and demand netting calculations are generated on a period-by-period basis for each MRP
defined time bucket. The requirement generation uses the planning fence rule to determine what sources of
demand to consider for a given duration.
The example is based on a G planning fence rule of 20 days. The greater than rule will be applied on a
period-by-period basis within the planning fence duration.
Sources of Demand Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
Forecast 100 100 100 100 100 100
Sales Orders 300 200
PLO 300 100 100 100 100 100
Page 13 of 135
This MRP period-by-period comparison would be more pronounced if the MRP time buckets were in days
and the rule duration remained at 20 days.
Note. The planning time-fence duration should approximate the replenishment lead time of the item.
Time Fence Rules for DRP, MRP, and MPS (34/TF)

Time fences are points of time at which you can make changes to either policy or operating procedures. The
system uses 34/TF as the UDC for time fence rules.
For example, you can use a time fence rule for planning that calculates an ending available amount that is
based on the greater of forecast or customer demand. For rules C and G, this situation means that the
forecast is reduced by the amount of the customer demand on that same time bucket. The system displays
all adjusted and unadjusted values. In the table, this applies to rules C, G, and H.
EnterpriseOne software uses the time fence rules for planning:
Rul Description 1 Description 2 Uses

e
Rul Customer Whichever is Rule C is commonly used for make-to-order,

eC demand greater: forecast assemble-to-order, and engineer-to-order items.
or customer
demand
Rul Forecast Forecast plus Rule F is commonly used for make-to-stock items
eF customer where forecast in Description 2 is insufficient for
demand total demand or business policy supports the
building of inventory due to volatile demand.
Rul Whichever is Forecast Rule G is the default.

eG greater: forecast Rule G is commonly used for make-to-stock items
or customer with accurate forecast. Description 1 in Rule G
demand provides a hedge to prevent lost sales or
backorders.
Rul Whichever is NA When you use planning fence Rule H, you should
eH greater: forecast set the Planning Fence field on the Manufacturing
or customer Data tab on the Additional System Information
demand form in the Item Master program to 999.
Rule H is commonly used for make-to-stock items
and is used for forecast consumption. Forecast
consumption enables you to plan for the entire
planning horizon.
Rul Customer Forecast Rule S is commonly used for make-to-order,

eS Demand assemble-to-order, and engineer-to-order items.
Similar to Rule C, Rule S does not take customer
demand into consideration for Description 2.
Rul Zero Forecast Rule 1 is used when you have constraints on the
e1 shop floor that dictate the workload. Neither
forecast nor customer is considered in
Description 1.
Rul Zero Forecast plus Rule 3 is similar to Rule 1; but Rule 3 is used for
e3 customer schedule constraints, and forecast is typically
demand lower than total demand.
Page 14 of 135
Note. With time fence rules C, G and H, you can use the forecast consumption by customer functionality if
you want to calculate net demand for an individual customer.
Time Series Calculations

The time series represents the proposed master schedule. Review the time series to decide whether to
accept or override the planning that the system suggests.
Requirements Planning provides three time series calculations:
• Ending available
• Available to promise
• Cumulative available to promise
Ending Available Calculation

Ending Available (EA) is the amount of product that is available at the end of a time bucket after the system
calculates the effect of all supplies and all demands for the time bucket. The system uses the planning time-
fence rule and the calculation to calculate the ending available amount:
• Add within the time bucket:
• Calculate Beginning Available (+BA)
 For the first time period, +BA = quantity on hand − safety stock.
 For remaining time periods, +BA = ending available from the previous time period (=EA).
• Subtract according to the planning time fence rule:
 Forecast (-FCST).
 Customer demand (sales orders and interplant demand).
• Equals ending available (EA).
The table displays how the system calculates the amount of product that is available at the end of a time
period. Assume that the order policy code equals lot for lot, safety stock equals 20, time fence rule for
planning equals C, and lead time equals 1. The planning fence is between periods 4 and 5.
For example:
On hand (80) − safety (20) = Period 1 + BA (60)
Period 1 + BA (60) − S0(20) = EA (40)
Product Period Period Period Period Period Period Period Period
On Hand = 80 1 2 3 4 5 6 7 8
+BA 60 40 25 25 0 0 0 0
-FCST 20 20 20 20 20 20 20 20
-SO 20 15 40 45
=EA 40 25 25 0 0 0 0 0
+DRP 15 20 20 45 20
(order start) 15 20 20 45 20
Page 15 of 135
Available to Promise Calculation
Available to promise (ATP) is the uncommitted portion of a company's inventory or planned acquisitions. You
use this amount to accurately promise customer orders. As long as manufacturing produces according to the
MPS and sales makes commitments according to the ATP information, this method increases customer
service and reduces inventory carrying cost.
Available to promise uses actual customer orders to identify inventory that can be promised to a customer.
The time fence rule for planning has no effect on ATP. Forecast is never included in ATP calculations.
The system calculates the ATP quantity like this:
• First period ATP = on-hand balance − safety stock+ work orders + purchase orders + planned
orders −sales orders − work order parts list demand − interplant demand - unconsumed lot
quantities that are expired.
• After the first period, ATP = work orders + purchase orders + planned orders - sales orders - work
order parts list demand - interplant demand - unconsumed lot quantities that are expired.
The system does not display negative ATP for the next periods. However, the system reduces the
CATP by the negative amount.
Cumulative Available to Promise Calculation

Cumulative available to promise (CATP) is a running total of the ATP.
For new products or seasonal products, building inventory might be part of the management strategy. In
these cases, sales and marketing might not be expected to sell within the replenishment buckets. The bulk of
sales might not be in the near future.
The system calculates CATP like this:
• First period CATP = beginning available + replenishment - sum of customer orders and parent
demand before the next replenishment.
• After the first period, CATP = CATP from last period + replenishment - sum of customer orders and
parent demand before the next replenishment.
CATP does not assume complete depletion. Rather, the system continues to add inventory.
The table displays how the system calculates CATP. Assume that the order policy code equals fixed 60,
safety stock equals 0, time fence rule for planning equals C, and lead time equals 1. The planning fence is
between periods 4 and 5.
CATP Period Period Period Period Period Period Period Period
1 2 3 4 5 6 7 8
+BA 80 50 25 55 45 25 50 30
–FCST 20 20 20 20 20 20 20 20
-SO 30 25 30 10 35
=EA 50 25 55 45 25 50 30 10
+DRP 60 60
ATP 25 20 25
CATP 25 25 45 45 45 70 70 70
See Also
Page 16 of 135
Understanding Forecast Consumption
Planning Messages
During planning, the system generates recommendations for the user called action messages.
The action messages for DRP, MPS, and MRP are defined in UDC table 34/MT (Message Type). The
character codes are hard-coded. Do not change the character codes in this UDC table.
When you process action messages, the system completes specific events.
After you generate planning schedule output, the system creates action messages that:
• Alert the planner of possible adverse conditions.
• Display action recommendations that the planner can process.
Message Types for DRP, MPS, MRP, and RCCP (34/MT)

The system uses 34/MT as the UDC for message types. All the messages are predefined for these message
types, which the system displays when you generate DRP, MPS, and so on. Because the character code is
hard-coded, you can change the description, but not the function, of the message type.
The system displays messages by type. You can identify which items require attention, based on the action
message types. The table displays what action the system takes when work orders or purchase orders are
processed.
Typ Descriptio Planner Work Order Purchase Order

e n Remarks
A Warning WO missing part Displays work order. You can N/A

message. list. copy the bill of material to
create a parts list.
A Warning BOM does not Error message; record invalid. N/A

message. exist for item.
A Warning Cancel parts list. Error message; record invalid. N/A

message. You must clear or delete the
message.
A Warning Defer parts list. Error message; record invalid. N/A

message. You must clear or delete the
message.
A Warning Lead time is Clears message. Displays N/A

message. zero. work order.
B Order & Blank. Clears message and creates a Clears message and
Expedite. firm order message. Creates a creates a firm order
work order. message. Creates
purchase order.
C Cancel. Blank. Clears message. The system Clears closed message

deletes the work order parts on purchase order line
list if no outstanding issues item. Changes status to
exist. Changes status to 99. 999.
D Defer. Blank. Clears the message and Clears the message and
changes the required date for changes the required
the item on the work order. date for the line item
Page 17 of 135
e n Remarks
on the purchase order.
E Expedite. Blank. Clears the message and Clears the message and
changes the start date on the changes the start date
work order. for the line item on the
purchase order.
F Frozen Frozen order. No action required. The No action required. The

order. message remains until deleted message remains until
or cleared. deleted or cleared.
G Increase Blank. Displays work order with Displays purchase

order updated quantity. Click OK to order with updated
quantity. accept the change. The quantity. Click OK to
system recalculates and accept the change.
changes the number of
required components.
H Decrease Blank. Displays the rate schedule. N/A

rate You must manually change
quantity. the rate quantity for the
suggested date.
I Increase Blank. Displays the rate schedule. N/A

rate You must manually change
quantity. the rate quantity for the
suggested date.
L Decrease Blank. Displays work order with Displays purchase

order updated quantity. Click OK to order with updated
quantity. accept the change. The quantity. Click OK to
system recalculates and accept the change.
changes the number of
required components.
M Manual User entered No action required. The No action required. The

reminder. text. message remains until deleted message remains until
N Create Blank. Clears message and creates N/A

rate. the rate schedule. Displays
rate schedule revisions.
O Order. Blank. Clears message and creates a Clears message and

firm order message. Creates creates a firm order
work order. message. Creates
purchase order.
P Firm order. Firm order. No action required. The No action required. The
message remains until deleted message remains until
S FPO Increase Parts No action required. The No action required. The

adjustment List. Decrease message remains until deleted message remains until
Page 18 of 135
e n Remarks
suggestion. Parts List. or cleared. Action is taken on deleted or cleared.

Expedite Parts the parent item's message. Action is taken on the
List. Defer Part parent item's message.
List.
T Past due Blank. No action required. The No action required. The

order. message remains until deleted message remains until
Parallel Processing
Parallel processing is a method that distributes work that an application performs across multiple processors
within a CPU. The parallel processing method achieves significant performance gains that are limited only by
the number of processors that are available on the server. Thus, parallel processing reduces the time that a
system requires to complete the work. For example, if you have excessive data volume, such as large bills of
material, parallel processing can reduce processing time. These instances determine whether the system
would benefit from parallel processing:
• Server with multiple processors.
• Large volume of data at any level of MRP.
A method of parallel processing is to create an application that divides data into separate, independent
paths. The paths process data simultaneously on multiple processors. The benefit of this method is that the
application automatically divides data among processors and also eliminates data administration. The
MRP/MPS Requirements Planning program and the Master Planning Schedule - Multiple Plant program use
this method of parallel processing.
When you run the parallel processing versions of the MRP/MPS Requirements Planning and Master
Planning Schedule - Multiple Plant programs, you plan items concurrently within the same low-level code,
because the items do not depend on each other. The system processes items with a low-level code that
equals 1. The system processes all of the items at the current level before it can process any items at the
next level: current level + 1. The system repeats this process until it has processed all of the items. Also, if a
server has multiple processors, you can plan multiple items concurrently with the same low-level codes.
Parallel processing uses the software's subsystem capabilities to run multiple copies of a batch program.
The system provides a unique subsystem version of a Universal Batch Engine (UBE) that enables you to
specify the number of available processors on the server. When the system runs the batch program,
preprocessing fills the subsystem table and begins the subsystem jobs. The jobs run the same version of the
application and access the same processing option values. Each record in the subsystem table contains data
that the system passes to a report. Each subsystem job processes records from the same table, one at a
time. After the system processes all of the records, the system terminates the subsystem jobs.
The system has several applications that parallel processing supports. To use the parallel processing
versions, you must perform these tasks:
• Indicate the maximum number of the same subsystem jobs that the system can process at the same
time.
Add or modify the value, UBESubsystemLimit=N, in the UBE section of the jde.ini file.
N represents the maximum number of similar subsystem jobs.
• Set up multithreaded job queues.
Note. Technical support must complete standard tasks in system setup before you can perform the
parallel processing method.
The MRP/MPS Requirements Planning and Master Planning Schedule - Multiple Plant programs have a
processing option, Number of Subsystem Jobs, on the Parallel tab that indicates how many concurrent jobs
Page 19 of 135
can process the MRP data. You must use subsystem parallel versions that are specifically designed for
parallel processing.
Important! You should not run more than one version of MRP at a time.
See Also
EnterpriseOne Tools 8.95 PeopleBook: System Administration
Setting Up Requirements Planning

This chapter provides an overview of the setup requirements for Requirements Planning and discusses how
to:
• Set up supply and demand inclusion rules.
• Set up inventory management for requirements planning.
• Set up quantity type subsets.
• Set up multifacility planning.
• Set up forecast consumption.
• Set up process planning.
Understanding the Setup Requirements for Requirements Planning

You must complete setup tasks to define the information that the system uses prior to using material and
capacity planning. You set up information in EnterpriseOne Inventory Management, EnterpriseOne
Manufacturing – PDM, EnterpriseOne Manufacturing – Shop Floor, EnterpriseOne Sales Order Entry,
EnterpriseOne Sales Order Processing, and EnterpriseOne Requirements Planning.
Setup includes such tasks as defining user-defined codes (UDCs), order policy rules, and supply and
demand inclusion rules. Requirements Planning uses setup information to determine how to select and
display data.
To successfully create a single-level plan for Master Production Scheduling (MPS) or Distribution
Requirements Planning (DRP), you must verify certain system setups.
You must verify that the Planning Code field in the Item Branch program (P41026) on the Additional System
Info form is set to a value of 1. This setting indicates that the item is planned by MPS and DRP.
Verify that the Generation Type field on the Parameters tab in the MRP/MPS Requirements Planning
program (R3482) is set to a value of 1. The generation types enable you to develop a strategy for the
different planning levels for the items. A setting of 1 indicates that the system generates a single-level MPS
or DRP plan.
For a single-level DRP run, you must set the Purchase Orders field on the Document Types tab in the
MRP/MPS Requirements Planning program with the appropriate document type. This type is generally OP.
For a single-level MPS run, you must set both the Purchase Orders and the Work Orders fields on the
Document Types tab in the MRP/MPS Requirements Planning program with the appropriate document type.
These fields are generally set to OP and WO, respectively.
You must also set up the supply and demand inclusion rules. The system processes the supply and demand
to include document types, line types, and status codes per the setup. DRP creates only purchase order
messages while MPS creates both purchase order and work order messages.
Page 20 of 135
When the supply and demand inclusion rules are set up, you must enter the rule version in the Version of
Supply/Demand Inclusion Rules field on the Parameters tab in the MRP/MPS Requirements Planning
program.
You set up quantity types that are specific to DRP and MPS. Quantity types are predefined codes that define
the display of data on the time series in time-phased buckets. You might want to set up your own quantity
types because DRP does not need to see codes for work orders, whereas MPS includes codes for work
orders. The DRP quantity types are defined in UDC table 34/DR, and the MPS quantity types are defined in
UDC table 34/MS.
Setting Up Supply and Demand Inclusion Rules

This section provides an overview of supply and demand inclusion rules and discusses how to:
• Set processing options for Supply/Demand Inclusion Rules (P45004).
• Set up supply and demand inclusion rules.
Understanding Supply and Demand Inclusion Rules

You set up supply and demand inclusion rules to define what order type, line type, and line status
combinations should be considered as supply or demand for various planning calculations.
Select each record that includes the order type and line status for which you want the inclusion rules to
apply, and click Select.
For example, a purchase order for a stock item that has already been received, (Order Type equals OP, Line
Type equals S, Line Status equals 999) should not be included as supply because the quantity on the
purchase order is already in inventory.
A sales order for a stock item that is waiting for a pick slip to be printed (Order Type equals SO, Line Type
equals S, Line Status equals 540) should be included as demand because the items have not been picked
from inventory yet.
When you apply inclusion rules to work order documents, line types do not appear. Line types are not
applicable to the Work Order system.
Form Used to Set Up Supply and Demand Inclusion Rules

Form Name FormI Navigation Usage
D
Work With W3400 Material Planning Setup Work with the supply and demand
Supply/Demand 4A (G3442), inclusion rules. Select the order type,
Inclusion Rules Supply/Demand line type, and line status for which you
Inclusion Rules want the inclusion rule to apply.
Setting Processing Options for Supply/Demand Inclusion Rules (P45004)

One processing option exists for Supply/Demand Inclusion Rules, which enables you to specify the work
order type.
WO Types
Work Order Specify the WO document types for the inclusion rules. These can be stacked up one on
Document Types top of another for multiple document types. If you leave this processing option blank, WO
will be used.
Setting Up Supply and Demand Inclusion Rules

Access the Work With Supply/Demand Inclusion Rules form.
Page 21 of 135
Work With Supply/Demand Inclusion Rules form
Rule Enter a UDC (40/RV) that identifies an inclusion rule that you want the system to use for this
Version branch/plant. Manufacturing and Warehouse Management use inclusion rules in this way:
• For Manufacturing:
Enable multiple versions of resource rules for running MPS, MRP, or DRP.
• For Warehouse Management:
Enable multiple versions of inclusion rules for running putaway and picking. The system
processes only those order lines that match the inclusion rule for a specified
branch/plant.
Complete this field to locate the status values for the inclusion code.
Skip to Enter a UDC (00/DT) that identifies the type of document. This code also indicates the origin of
Order the transaction. The system has reserved document type codes for vouchers, invoices, receipts,
Type and time sheets, which create automatic offset entries during the post program. (These entries
are not self-balancing when you originally enter them.)
These document types are defined in the system and should not be changed:
P: Accounts Payable.
R: Accounts Receivable.
T: Payroll.
I: Inventory.
O: Purchase Order Processing.
J: General Accounting/Joint Interest Billing.
S: Sales Order Processing.
Setting Up Inventory Management for Requirements Planning

When you set up the item master and branch/plant information, you provide Requirements Planning with the
information that it needs to create accurate master schedules, material requirements plans, and distribution
requirements plans. Requirements Planning uses the values in these fields:
• Stocking Type
• Planner
• Buyer
• Supplier
• Lot processing information
• Planning family
• Category codes
• Units of measure
• Order policy codes
• Order policy values
• Planning code
• Planning fence rule
• Planning fence
• Freeze fence
• Message display fence
• Time Basis
Page 22 of 135
• Shrink Factor
• Leadtimes
• Reorder quantities
When the items are defined in the Item Master program (P4101), you can further define the items at the
branch/plant level using the Item Branch program.
Use the Item Branch program to specify information for each item. This information is critical to
Requirements Planning:
Stocking Type
In the distribution systems, the stocking type for each item typically identifies how you stock the item.
However, the planning system uses the second description and the special handling code in the stocking
type UDC table definition (41/I) to determine whether the item is a manufactured, purchased, processed, or
project-specific item.
Order Policy Rules

You must set up order policy rules to control how the planning system calculates dates and quantities. The
order policy rules that you set up are:
Planning Enter a code that the system uses to process the item when running the MRP/MPS
Code Requirements Planning and Master Planning Schedule - Multiple Plant (R3483) programs. Use
planning codes 1, 2, or 3 for single-level or multilevel master scheduling. Use planning codes 4
and 5 for forecasting with a planning bill.
Order Enter a code that the system uses to designate the rule for reordering inventories, including
Policy fixed-order quantity, lot for lot, or number of days supplied.
Code
Order Enter a value that the system uses with order policy codes 1, 2, 4, and 5. For example,
Policy purchasing a 90-day supply of V-8 engines requires that the order policy code is set to 4 and the
Value order value policy value equals 90.
Lead Times
You must set up lead times for items. You must set the lead time for phantom items to zero so that the
parent-planned orders are recorded directly to the options as a gross requirement without being offset by the
lead time. The system multiplies the planned orders by the feature planning percentage before placing the
planned orders as component gross requirements.
See Also
Entering Item Master Information
Entering Branch/Plant Information
Setting Up Quantity Type Subsets

You should not change the 34/QT UDC table; however, you can create a subset or a custom quantity type
UDC table. Because companies like to make decisions about what quantity types appear on the time series,
creating a custom quantity type UDC table gives them flexibility. For example, a distribution warehouse does
not want to see the quantity types for work orders.
The software provides multiple subsets of the UDC 34/QT; for example, 34/DR for Distribution Requirement
Plan (DRP) and 34/MS for Master Production Schedule (MPS).
For the system to access 34/QT during DRP, MPS, or Material Requirements Planning (MRP) generation,
you must set the UDC Type field on the Parameters tab in the processing options for the MRP/MPS
Requirements Planning and Master Planning Schedule - Multiple Plant programs. Setting this processing
option with a value of QT enables the planning system to use all of the available data and create a time
series for every transaction that it is capable of making.
Page 23 of 135
You can use the custom UDC 34/DR or 34/MS quantity types by setting the Alternate UDC Type (Optional)
field on the Defaults tab in the processing options for the MPS Time Series program (P3413). You can then
use the Alternate Quantity Type option on the Work With Time Series form to determine which UDC quantity
types you view in the time series.
Distribution Requirement Plan Quantity Type (34/DR)

The system uses 34/DR as the UDC for DRP quantity types. Quantity types are predefined codes that define
the display data on the time series screens and reports that use the MPS/MRP/DRP Summary File table
(F3413).
The system provides the 34/DR UDC table as a subset of 34/QT. Upon review of 34/DR, notice that the
quantity types have been reduced from the original quantity types in the 34/QT UDC table. Unadjusted
quantity types have been removed and +DRP reflects planned replenish order quantities.
This table lists the valid quantity types and descriptions for DRP in UDC table 34/DR:
Quantity Type Description
+BA + Beginning Available
+IR + In Receipt Routing
+PO + Purchase Orders
–LEXP - Lot Expired
-FCST - MPS/Forecast
-SHIP - Shipped Quantity
-SO - Sales Order
-ID - Interplant Demand
=EA = Ending Available
+DRP + Distribution Requirements Plan
ATP Available to Promise
CATP Cumulative Available to Promise
Master Production Schedule Quantity Type (34/MS)

The system uses 34/MS as the UDC for MPS quantity types. Quantity types are predefined codes that define
the display data on the time series screens and reports that use the F3413 table.
The UDC table 34/MS was developed as a subset of 34/QT. Upon review of 34/MS, notice that the quantity
types have been reduced from the original quantity types in the 34/QT UDC table.
This table lists the valid quantity types and descriptions that are defined for MPS in UDC table 34/MS:
+BAU +Beginning Available (Unadjusted)
+BA +Beginning Available
Page 24 of 135
+IR In Receipt Routing
+POU +Purchase Orders (Unadjusted)
+PO +Purchase Orders
+WOU +Work Orders
+WO +Work Orders
+RSU +Rate Schedule (Unadjusted)
+RS +Rate Schedule
-LEXP -Lot Expired
-FCSI -MPS/Forecast (Unadjusted)
-FCST -MPS Forecast
-SHIP -Shipped Quantity
-SOU -Sales Orders (Unadjusted)
When you set up the time series inquiry, you can create a new UDC table for the quantity types and change
the appropriate processing option to display this new table. You can also use processing options to display
two different tables, such as adjusted and unadjusted quantities.
Each table displays only items that are pertinent to its application. For example, UDC table 34/DR displays
only data items that apply to DRP items. If the code is not defined in UDC table 34/DR, it does not appear on
the Work with Time Series form or report. DRP and MPS calculations are not affected by the appearance of
this code.
If you do not specify a particular UDC list, all quantity types appear. However, the time series calculation is
not affected by the quantity types that are not pertinent to the application.
Adjusted Values Only (MPS) (34/AS)

The system uses 34/AS as the UDC for adjusted values only (MPS) quantity types. Quantity types are
predefined codes that define the display data on the time series screens and reports that use the F3413
table.
The 34/AS UDC table was developed as a subset of 34/QT. Upon review of 34/AS, notice that the quantity
types have been reduced from the original quantity types in 34/QT. The 34/AS UDC table provides an
adjusted view of the time series. This adjusted view depicts what the plan will be if all the planning
recommendations are acted on.
Unadjusted Values Only (MPS) (34/US)

The system uses 34/US as the UDC for unadjusted values only (MPS) quantity types. Quantity types are
predefined codes that define the display data on the time series screens and reports that use the F3413
table.
The 34/US UDC table was developed as a subset of 34/QT. Upon review of 34/US, notice that the quantity
types have been reduced from the original quantity types in 34/QT. The 34/US UDC table provides an
unadjusted view of the time series. This unadjusted view depicts what the plan would look like if the planner
did not act on the messages.
Page 25 of 135
Setting Up Multifacility Planning
This section provides an overview of the multifacility planning setup and discusses how to:
• Set processing options for Branch Relationships Revisions (P3403T).
• Set up supply and demand relationships.
Understanding the Multifacility Planning Setup

You set up multifacility planning to track supply, demand, and movement of material among the individual
facilities of the enterprise. Multifacility planning provides a flexible method for planning supply and resupply
activities.
In multifacility planning, you must set up a table of supply and demand relationships among the facilities. The
system uses these relationships to generate and maintain multifacility plans.
Set up supply and demand relationships for any level of detail that you select, including:
• Branch/plant
• Product group
• Master planning family
• Individual item number
This approach enables you to maintain supply-and-demand relationships in one central location and reduce
inventory errors that are caused by complex facility relationships. In addition, when you set up supply-and-
demand relationships, you can use these optional features:
• Markup
You can have the system automatically mark up the cost of an item when you create a transfer
order. The system can adjust the cost by a fixed amount or percentage.
• Availability checking
You can ensure that the branch from which you are ordering has enough inventory in stock to fill the
order. If the required quantity is not available, the system checks subsequent facilities in the
sequence that you define.
• Effectivity dates
Use effectivity dates to control the demands that are placed on the supply branches. If an effectivity
date that was assigned to a supply branch has expired, the system checks for another facility.
The MRP, DRP, and MPS versions of the Branch Relationships Revisions program use the same
processing options. You can vary the settings in the processing options to accommodate the
different requirements for a material requirements plan.
Important! When you delete a supply-and-demand relationship, the system deletes the entire
record.
Form Used to Set Up Multifacility Planning

D
Branch W3403 Multifacility Setup Define which branch/plants, product group,

Relationship TC (G3443), Branch planning family, and item are included or
Revisions Relationships excluded in generating a multifacility
Revisions planning schedule.
On Work With Branch
Relationships, click
Add.
Page 26 of 135
Setting Processing Options for Branch Relationships Revisions (P3403T)
You must set this processing option to ensure that the level of the component branch is one level higher than
the header for the source branch. The branch level on the Defaults tab, along with the branch priority,
determines the sequence in which the system processes supply and demand plants. The system processes
the branches with the highest numerical branch levels first.
Defaults
Use these processing options to specify the default settings for branch relationship revisions.
Enter the default Branch Relationship display Specify the default mode for the branch/plant.
mode. D: Demand branch
S: Supply branch
Branch Level update Specify the update to the branch.
Enter 1 to automatically update the Branch Level
field.
Setting Up Supply and Demand Relationships

Access the Branch Relationship Revisions form.
Item Number Enter an item number to display all branch/plants that either supply or demand a certain part.
Planning Enter the planning family to display all branch/plants that either supply or demand parts that
Family belong to a specific master planning family.
Branch Level Enter the level at which a component branch should be processed in multiplant processing.
The lowest level branches (which are assigned a higher numerical value) are processed first,
followed by the higher level branches (which are assigned a lower numerical value).
Note. Assign branch levels carefully so that the planning system generates all demand before
allocating supply.
Branch Enter a value to determine the sequence within a level in which the branches are processed in
Priority multiplant DRP/MPS/MRP. Use this field along with the Branch Level field to check inventory
availability first in one branch, and then another.
Include/ Enter a code that indicates whether the system includes or excludes the item/category code in
Exclude the Branch Relationships Master table (F3403) when generating a multiplant schedule. If an
item/category code is excluded, then that item/category code will be purchased or
manufactured at the demand branch.
Some parts might come from certain branch/plants. In multifacility planning, if Exclude is
selected, then the item is supplied by the demand branch only.
Transfer Enter the number of days to ship items from the supply branch to the demand branch.
Leadtime This lead time is set up in the Branch Relationships Master table and can vary for different
category codes or even for different items.
Effective Enter a date that indicates:
From • When a component part goes into effect on a bill of material.
• When a rate schedule is in effect.
The default is the current system date.
You can enter future effective dates so that the system plans for upcoming changes.
Items that are no longer effective in the future can still be recorded and recognized in
Product Costing, Shop Floor, and Capacity Requirements Planning. Material
Requirements Planning determines valid components by effectivity dates, not by the
bill-of-material revision level. Some forms display data based on the effectivity dates
that you enter.
The default date comes from the bill of material.
Source Enter an amount as a percent. The system uses source percentage to determine what
Percent percentage of the planned order should be supplied by the source branch.
Page 27 of 135
For example:
Demand Branch - ATL
Supply Branch - DEN source percentage = 40 percent, CHI source percentage = 60 percent
If ATL needs 100 parts, the system generates a message to transfer 40 parts from DEN and 60
parts from CHI.
A source percentage of 100 transfers the entire supply from that branch/plant.
Availability Specify whether the planning system checks availability of the item or family at the supply
Check branch/plant. If you enable availability checking on the item or family that is being demanded,
the available inventory at the branch/plant is committed until a zero balance results. If you
disable availability checking, the inventory balance in the supplying branch/plant can be
negative.
Percent To Enter a value that is used during multiplant processing to determine what percent of an order
Fill should be filled to place a transfer order message. For example:
• Percent to Fill - 75 percent
• Demand - 200
• If the supply branch has 150 (75 percent of 200) or more available, then the planning
system places the transfer order message.
The system generates the transfer order message when the percent to fill is zero.
This amount of the source percent must be available to be filled by this branch/plant. The
percent of demand should be filled to place a transfer order message. A transfer order is
generated if Availability Check is on.
Setting Up Forecast Consumption

This section provides overviews of the forecast consumption setup and the customer address relationship
setup, lists prerequisites, and discusses how to:
• Set up forecast consumption periods.
• Define customer address relationships.
Understanding the Forecast Consumption Setup

You set up forecast consumption periods to identify a period of time in which forecasts are consumed by
sales orders. The system stores this information in the Forecast Consumption Periods table (F3405).
You define the end date for each forecast consumption period on the Work With Forecast Consumption
Revisions form. The periods apply system-wide. You cannot have different forecast consumption periods for
different locations or branch/plants.
The system adds the forecast consumption periods to the number of time series periods that you specified in
the processing options for the MRP/MPS Requirements Planning program. The total for all time periods
cannot exceed 52.
Note. You are not confined to entering forecast in the same period patterns as the consumption periods. For
example, you can have weekly forecasts to smooth the demand while having a monthly consumption period.
You must set up the Planning Fence field on the Additional System Information form, Plant Manufacturing
tab with a value that is beyond the end of the planning horizon (a planning fence of 999 is recommended). If
you do not set the planning fence beyond the planning horizon, the batch planning programs
(DRP/MPS/MRP Regeneration and Net Change) do not work properly.
Understanding the Customer Address Relationship Setup

To use the forecast consumption by customer functionality, you have to be able to match forecast and sales
order records by a common customer number. Because sales orders have two applicable address book
numbers, sold to and ship to, you have to define which number the system uses to match a sales order to a
forecast.
Page 28 of 135
You can use the Forecast Consumption Customer Address Relationship program (P3406) to define whether
the system uses the sold-to or the ship-to address when searching for sales orders. You can set up the
relationship for the customer only, or you can set it up for a combination of item and customer.
When running MRP/MPS Requirements Planning or Master Planning Schedule - Multiple Plant, you can set
a processing option that determines whether the system uses the sold-to or the ship-to number to search for
sales orders. This processing option is used if no customer address relationship is set up in the F3406 table.
Note. You should use the processing option to provide a default value for the customer address relationship
and use the Forecast Consumption Customer Address Relationship program to provide override information
where necessary.
Prerequisites
Before you complete the tasks in this section, verify that the following information has been set up:
• Planning fence rule H is in UDC 34/TF.
• The order types in UDC 40/CF are included to support shipped-order calculations.
• The -SHIP quantity type is in UDC 34/QT to calculate shipped orders quantity.
• The order types in UDC 40/IU are included to update inventory (includes order type SO).
• The Planning Fence Rule field on the Additional System Information form, Plant Manufacturing tab,
is a value of H.
• The Planning Fence field on the Additional System Information form, Plant Manufacturing tab, is a
value beyond the end of the planning horizon.
• The appropriate processing options in the MRP/MPS Requirements Planning program.
Forms Used to Set Up Forecast Consumption

D
Work With Forecast W340 Material Planning Setup (G3442), Define the time series
Consumption Revisions 5A Forecast Consumption Periods period for forecast
consumption.
Forecast Consumption W340 Material Planning Setup (G3442), Define which customer
by Customer Address 6A Work with Forecast Consumption number is used to match
Relationship Revisions by Customer Address sales orders to forecast.
Relationship.
On Work With Forecast
Consumption by Customer
Address Relationship, click Add.
Setting Up Forecast Consumption Periods

Access the Work With Forecast Consumption Revisions form.
Work With Forecast Consumption Revisions form
Period End Date Enter a date on which the defined forecast consumption period ends.
Period Type Enter a type of record to be used in conjunction with Forecast Consumption. Values are:
FC: Forecast consumption period
TS: Time series bucket
Page 29 of 135
Defining Customer Address Relationships
Access the Forecast Consumption by Customer Address Relationship Revisions form.
Forecast Consumption by Customer Address Relationship Revisions form
Item Number Enter a number that identifies the item. The system provides three separate item numbers
plus an extensive cross-reference capability to alternative item numbers. The three types
of item numbers are:
• Item Number (short): An 8-digit, computer-assigned item number.
• 2nd Item Number: A 25-digit, user-defined, alphanumeric item number.
• 3rd Item Number: Another 25-digit, user-defined, alphanumeric item number.
In addition to these three basic item numbers, the system provides an extensive
cross-reference search capability. You can define numerous cross-references to
alternative part numbers. For example, you can define substitute item numbers,
replacements, bar codes, customer numbers, or supplier numbers.
Customer Enter a number that identifies an entry in Address Book, such as employee, applicant,
Number participant, customer, supplier, tenant, or location.
Customer Enter a value that specifies which address book number on a sales order the system uses
Address to search for sales orders. Values are:
Relationship 1: Ship To
2: Sold To
Setting Up Process Planning

This section provides an overview of process planning setup, lists a prerequisite, and discusses how to set
up the Co/By Products Planning Table program (P3404).
Understanding Process Planning Setup

You use the Co-Product Planning/Costing Table program (P3404) to set up co-product and by-product
processes for MRP/MPS Requirements Planning. The planning table specifies the percentage of the demand
for co-products that is satisfied from a process work order and the percentage that is satisfied from process
work orders and the percentage that is satisfied from other sources.
You can also specify circumstances. For example, by entering 75 percent in the table, you specify that 75
percent of demand is satisfied from process work orders and the balance from other sources. The system
automatically satisfies the balance, for example, by planning co-product work orders or creating purchase
orders.
If a co-product can be produced by more than one process, both processes appear in the table when you
locate the co-product. For example, a 65 percent to 35 percent relationship can exist between the two
processes.
Prerequisites
Before you complete the task in this section, verify that the stocking type for a process is R.
Form Used to Set Up Process Planning

D
Co/By-Products W340 Material Planning Setup Specify the amount of co-product

Planning Table 4N (G3442), Co/By Products and by-product that is planned for
Revisions Planning Table. each process.
On Work with Co/By-Products
Page 30 of 135
D
Planning Table, click Add.
Setting Up the Co/By Products Planning Table

Access the Co/By-Products Planning Table Revisions form.
Co/By-Products Planning Table Revisions form
Plan %(plan Specify the percent of demand for the co-product or by-product that is planned for by
percent) each process.
Cost %(cost Specify the percent of cost from each process that is allocated to the co-product or by-
percent) product.
Setting Up Capacity Planning

This section provides an overview of capacity planning setup requirements and discusses how to:
• Set up user-defined codes (UDCs) for capacity planning.
• Set up work center capacity information.
• Determine available capacity.
• Generate resource profiles.
Understanding Setup Requirements for Capacity Planning

Capacity planning is the process of validating if you have sufficient resources to complete the requirements
plan. Setting up capacity planning is the process of defining the available capacity and critical areas where
capacity constraints exist.
Prerequisite
Set up the work centers and dispatch groups as business units.
See Setting Up Business Unit Supplemental Data.
Setting Up User-Defined Codes for Capacity Planning

In order to run capacity planning you must set up the UDCs.
Capacity Requirements Planning Display (33/CR)

The system uses 33/CR as the UDC for the capacity requirements planning display. Use the capacity
requirements planning display to specify row descriptions for all Capacity Requirements Planning (CRP)
forms and reports.
Rough Cut Capacity Planning Display (33/RC)

The system uses 33/RC as the UDC for the rough cut capacity planning display. Use the rough cut capacity
planning display to specify row descriptions for all Rough Cut Capacity Requirements (RCCP) forms and
reports.
Page 31 of 135
Resource Requirements Planning (33/RR)
The system uses 33/RR as the UDC for resource requirements planning. The resource requirements
planning display identifies the types of loads on a work center. You can review these types of loads on the
Review Work Center Load form in the Capacity Load program (P3313).
Unit Types (33/UT)

The system uses 33/UT as the UDC for unit types. You need to identify all of the different types of resource
units that can be associated with any work center.
Setting Up Work Center Capacity Information

This section provides an overview of the work center capacity setup and discusses how to set up work center
capacity information for requirements planning.
Understanding Work Center Capacity Setup

Set up the work center information to correspond to the facilities on the shop floor. Specify whether the work
center is machine- or labor-paced, and whether it is a critical work center. You also specify other values,
such as the percent efficiency and utilization of the work center and the crew.
Work centers also provide additional information such as:
• Pay points.
• Prime load codes.
• Number of machines and workers.
• Crew size.
• Backflush locations.
• Rates.
See Also
Creating Work Centers
Form Used to Set Up Work Center Capacity Information

D
Work Center W300 Daily PDM Discrete (G3011), Define capacity information
Master Revisions 6A Enter/Change Work Centers. for work centers.
On Work With Work Centers, click
Add.
Setting Up Work Center Capacity

Access the Work Center Master Revisions form.
Work Center Enter a number that identifies a branch, plant, work center, or business unit.
Dispatch Group Enter a category code to group work centers within an overall business unit.
For example, you can use this code to group similar machines that operate out of
several work centers and report to one business unit.
Location Branch Specify the branch plant of the location that is associated with the work center.
Prime Load Enter a code that determines if a work center is machine-or labor-intensive. The
system also uses prime load codes in Resource Requirements Planning and Capacity
Requirements Planning calculations to develop load profiles.
Page 32 of 135
Codes are:
L: Run labor hours only.
M: Machine hours only.
B: Run labor plus setup labor hours.
C: Machine plus setup hours.
O: Other (will not generate resource units).
Critical W/C (critical Enter a code that indicates whether the work center is critical or not critical when the
work center) system calculates capacity. Values are:
N: Not a critical work center.
1: A critical work center in calculating RRP only.
2: A critical work center in calculating RCCP and CRP.
3: A critical work center in calculating RRP, RCCP, and CRP.
The system also displays Type 3 work centers when you select Type 1 or Type 2 in
this field.
4: Not a capacity work center. The system does not include this work center in capacity
planning.
Note. The data selection is a system feature that processes certain groups of
information with the RRP, RCCP, and CRP programs.
Resource Offset Enter a value from the Resource Profile table (F3303) to determine the number of days
that the actual use of a work center resource should be offset from the forecasted need
date.
Standard Capacity Enter the standard capacity level at which a production line usually operates. Capacity
is stated in units per hour. This level is used for repetitive processing only.
Capacity UOM Enter a unit of measure to express the capacity of a production line. Examples of units
(capacity unit of of measure include hours, number of stampings, coats of paint, and so on.
measure) This item is used for repetitive processing only.
Minimum Capacity Enter the lower limit of the capacity, beyond which the production line should not
operate. Management sets this limit, based on factors such as efficiencies, costs, and
so on.
Capacity is stated in units per hour. This limit is used for repetitive processing only.
Maximum Capacity Enter the upper limit of the capacity, beyond which a production line cannot produce.
Capacity is stated in units per hour. This limit is used for repetitive processing only.
Queue Hours Enter the total hours that an order is expected to be in queue at work centers and
moving between work centers.
The system stores this value in the Item Branch table (F4102) table. You can calculate
this value using the Leadtime Rollup program (R30822A) or you can enter it manually.
When you run the Leadtime Rollup program, the system overrides manual entries and
populates the table with calculated values.
Move Hours Enter the planned hours that are required to move the order from this operation to the
next operation in the same work center.
If the Routing Master values are blank, the system retrieves the default value from the
work order routing. However, the system uses these values only for backscheduling
variable leadtime items.
If you leave the Hours field on the Routing Revisions form blank, the system uses the
value in this field for leadtime and scheduling calculations.
Replen. Hrs. Enter the time that is required before a consuming location has a replacement kanban
(replenishment hours) available from its supplying location.
This value is used only for kanban card processing in Shop Floor Management.
Efficiency Enter a user-defined value that indicates how efficiently a work center operates.
This value usually refers to staff efficiency. When you enter a value in this field and the
Modify Cost by Work Center Efficiency field in the Job Shop Manufacturing Constants
table (F3009) is set to Y, the system creates a new cost component (B4) from the cost
Page 33 of 135
calculated from the direct labor cost (B1).
For example, if the constant is set to Y, the value of this field is 80 percent, and the
direct labor cost is 10, the system creates a B4 cost component for two in the Item
Cost Component Add-Ons table (F30026).
The Work Center Resource Units Generation program (R3007G) also uses this value
as a default when calculating rated capacity.
Enter percents as whole numbers. For example, enter 80 percent as 80.00.
Note. The system expects that the routing times for each operator are the actual times
it takes to complete an operation. Efficiency does not affect total cost. Efficiency does
reassign some of the costs into different cost components. Efficiency does not change
the duration or backscheduling of a work order.
Utilization Enter a percentage that indicates how intensively a work center is being used. This
value usually refers to machine use. It is the ratio of the direct time charged for
production activities to the planned hours.
The Work Center Resource Units Generation program also uses this value as a default
when calculating rated capacity.
Determining Available Capacity

This section provides an overview of determining available capacity, list prerequisites, and discusses how to:
• Set the processing options for Work Center Resource Units Generation (R3007G).
• Generate resource units automatically.
• Set the processing options for Work Center Resource Units (P3007).
• Revise resource units manually.
Understanding Available Capacity

You must determine how much production capacity the work centers have. You determine a work center's
available capacity on a given day by entering resource units.
You can have the system generate resource units or you can enter them manually. Use the Work Center
Resource Units Generation program to automatically recalculate the work center hours. The system
generates resource units, based on an hours (HR) unit of measure. Revise units manually if you need to
make adjustments.
You can assign resource units for different units of measure in different work centers. For example, you
might want to estimate the square footage that you need to store items as well as the hours that you need to
produce an item.
You can revise resource units manually if you need to make adjustments to them. For example, you might
need to make adjustments to account for machine downtime or employee vacations. You can change the
values on the Enter/Change Resource Units form to account for scheduled or unscheduled downtime,
additional shifts, or vacation time.
Important! Each time that you run Work Center Resource Units Generation, based on effectivity dates, the
program recalculates the form values and overwrites the manual changes, based on information in the Work
Center Master File table (F30006), the Workday Calendar program (P00071) (shop floor calendar), and the
F3009 table.
Prerequisites
Before you complete the tasks in this section:
• Before you enter resource units, you must ensure that work centers exist for these resource units.
• Set up manufacturing constants.
Page 34 of 135
• Determine the branch/plants for which you want to generate resource units.
• Verify that you have set up a current shop calendar for the time period that you specify.
Form Used to Determine Available Capacity

D
Work Center W300 Periodic Resource/Capacity Planning (G3321), Revise resource

Resource Unit 7B Enter/Change Resource Units. units manually.
Revision On Work with Resource Units, complete the
Branch/Plant and Work Center fields and click
Find.
Select the record to revise.
Setting Processing Options for Work Center Resource Units Generation

(R3007G)
Use these processing options to specify the default processing for programs and reports.
Defaults
These processing options define default values.
1. From Date Specify the beginning date that the system uses to generate resource units. Enter the
beginning date or select a date from the calendar. The system generates resource units and
refreshes them for the month in which the From date falls. For example, if the From Date is
January 1, 2005 and the Thru Date is January 31, 2005, the system generates resource units
for January, 2005. The system requires that you enter values for this processing option before
you can run the generation.
2. Thru Date Specify the ending date that the system uses to generate resource units. Enter the ending
date or select a date from the calendar. Resource units are generated, refreshed, or both, for
the entire month. For example, if the From Date is January 1, 2005 and the Thru Date is
January 31, 2005, the system generates resource units for January, 2005. The system
requires that you enter values for this processing option before you can run the generation.
3. Specify the branch/plant that is updated by the system in the Work Center Resource Units
Branch/Plant table (F3007) when you generate resource units.
Enter the branch/plant or select a branch/plant from the Business Unit Master Search form.
This processing option is required before you can run the generation.
Process
These processing options define processing criteria.
1. Shift Code Specify a UDC (06/SH) that identifies the type of shift (for example, day, night, or graveyard).
through 6. Shift These processing options specify the shift codes to include in the resource unit generation.
6 Code You can enter up to six different shift codes. Enter the code or select it from the Select User
Define Code form. If you leave all shift codes blank, the system processes all valid shifts for
the requested branch/plant.
Generating Resource Units Automatically

Run the Work Center Resource Units Generation program to automatically recalculate the work center
hours. You can view the results in the Work Center Resource Units program or on the Work Center
Resource Unit Revision form (W3007B). You can also change values on the Work Center Resource Unit
Revision form.
Page 35 of 135
You should run this program whenever you revise the hours per day on the Manufacturing Constants
Revision form (W3009B), the number of machines in a work center, or the number of employees who are
assigned to a work center. You can also run the program to define resource units for specific time periods.
The system recalculates the resource units for a work center based on:
• Hours per day in the F30006 table.
• Shop floor calendar.
• The F3009 table.
Important! The system overwrites any manual changes that you make to the units on Work Center
Resource Units when you run Work Center Resource Units Generation, based on effectivity dates.
Resource Unit Calculations

The program uses resource unit calculations:
Machine-related hours Number of machines × work hours per day

(Prime load code = C or M)
Labor-related hours Number of employees × work hours per day

(Prime load code = L or B)
Setting Processing Options for Work Center Resource Units (P3007)

Processing options enable you to specify the default processing for programs and reports.
Defaults
This processing option defines a default value.
1. Enter the Default Unit of Measure for Work Specify a UDC (00/UM) that indicates the quantity in which
Center Resource Units. If left blank, HR will be to express an inventory item (for example, CS (case) or BX
used as the default Unit of Measure. (box)).
Work Day Calender (P00071)
Identifies a specific set of data selection and sequencing
settings for the application. You can name versions using
any combination of alpha and numeric characters.
Revising Resource Units Manually

Access the Work Center Resource Unit Revisions form.
Work Center Resource Unit Revision form
Work Center Enter a number that identifies work center.

Month Enter a number that corresponds to the month in a calendar year.
Year Enter the calendar year for this calendar.
UM (unit of Displays the default value that comes from the component and production units of measure
measure) from the Item Master table.
Work Center Enter a user-defined value that indicates how efficiently a work center operates.
Efficiency This value usually refers to staff efficiency. When you enter a value in this field, and the
Modify Cost by Work Center Efficiency field in the F3009 table is set to Y, the system creates
a new cost component (B4) from the cost calculated from the direct labor cost (B1).
For example, if the constant is set to Y, the value of this field is 80 percent, and the direct
labor cost is 10, the system creates a B4 cost component for two in the F30026 table.
Page 36 of 135
The Refresh Resource Units program also uses this value as a default when calculating rated
capacity.
Note. The system expects that the routing times for each operator are the actual times it takes
to complete an operation. Efficiency does not affect total cost. Efficiency does reassign some
of the costs into different cost components. Efficiency does not change the duration or
backscheduling of a work order.
Work Center Enter a percentage that indicates how intensively a work center is being used. This value
Utilization usually refers to machine use. It is the ratio of the direct time charged for production activities
to the planned hours.
The Refresh Resource Units program also uses this value as a default when calculating rated
capacity.
Total This value identifies the monthly total resource units for the work center.
Resource
Units
Generating Resource Profiles

This section provides an overview of resource profiles, list prerequisites, and discusses how to:
• Set the processing options for Resource Profile Generation (R3365).
• Generate resource profiles automatically.
• Define resource profiles manually.
Understanding Resource Profiles

Long-range load is an estimate of how many load hours are required to meet sales projections. To determine
long-range load, the system uses resource profiles. The resource profile is a list of all work centers and their
load requirements for a master-scheduled item. The resource profile is the sum of all labor, machine, and
setup hours that are required for all work centers and for all parts in the multilevel bill of material for a
master-scheduled item.
You can have the system automatically generate a resource profile, or you can manually enter the profile.
You manually enter the profile if you have not defined bills of material and routings for an end item. You can
also use the manual method for prototype items and new products.
Prerequisites
• Enter all applicable bills of material, routings, and work centers.
• Review these topics in the Product Data Management Guide:
 Entering Bills of Material.
 Working With Routing Instructions.
 Working with Work Centers.
Form Used to Generate Resource Profiles

Form FormI Navigation Usage
Name D
Resource W330 Periodic Resource/Capacity Create resource profiles manually. You

Profile 3B Planning (G3321), must set up item branch/plant
Page 37 of 135
Name D
Revisions Enter/Change Resource Profile. information before entering a resource

On Work with Resource Profile profile.
Revisions, click Add.
Setting Processing Options for Resource Profile Generation (R3365)

Process
These processing options define processing criteria.
1. Enter the Effective From:

effectivity dates for Specify a date that indicates:
the regeneration:
• When a component part goes into effect on a bill of material.
• When a routing step goes into effect as a sequence on the routing for an item.
• When a rate schedule is in effect the default is the current system date.
You can enter future effective dates so that the system plans for upcoming
changes. You can still record and recognize items that are no longer effective
in the future in Product Costing, Shop Floor Management, and Capacity
Requirements Planning. The Material Requirements Planning system
determines valid components by effectivity dates, not by the bill of material
revision level. Some forms display data based on the effectivity dates you
enter.
Effective Thru:
Specify a date that indicates:
• When a component part is no longer in effect on a bill of material.
• When a routing step is no longer in effect as a sequence on the routing for an
item.
• When a rate schedule is no longer active. The default is December 31 of the
default year that is defined in the Data Dictionary for Century Change Year.
You can enter future effective dates so that the system plans for upcoming changes.
You can still record and recognize items that are no longer effective in the future in
Product Costing, Shop Floor Management, and Capacity Requirements Planning. The
Material Requirements Planning system determines valid components by effectivity
dates, not by the bill of material revision level. Some forms display data based on the
effectivity dates that you enter.
Generating Resource Profiles Automatically

If you have defined bills of material (BOMs) and routings for an end item and all of its subassemblies, you
can run the Resource Profile Regeneration program (R3365) to automatically generate the resource profile.
The program calculates the load on a work center by extending the hours in the routing by the forecasted
quantities for the master-scheduled items.
The Resource Profile Regeneration program creates units of measure only in hours (HR). Enter the resource
profile manually if you want to use other units of measure.
Resource Profile Regeneration changes or updates the resource profile by using components with effectivity
dates within the period that you specify. The specific items that are affected by the program are determined
by such factors as:
• The system retrieves routings only for BOM components that are effective within the range of
effectivity dates in the processing options for the regeneration.
Page 38 of 135
• The system creates resource profiles only from BOM components with effectivity dates that are
within the effectivity dates that are assigned to the item and the processing options.
• The Effective From date in the resource profile is the earliest of the dates in the processing option,
the BOM, or the routing Effective From dates.
• The Effective Through date for resource profiles is the latest of the dates in the processing option,
the BOM, or the routing Effective Through dates.
This graphic illustrates all the BOMs and routings with effectivity dates that are within the Effective From and
Effective Through dates:
BOMs and Routings Regeneration Effectivity Dates diagram
Defining Resource Profiles Manually

Access the Resource Profile Revisions form.
Unit Type Enter a code that indicates the type of resource unit that is associated with this work center.
Possible types are:
1: Run Labor Hours
2: Setup Labor Hours
3:: Machine Hours
9: Miscellaneous (storage space, and so on)
From • When a component part goes into effect on a bill of material.
Page 39 of 135
• When a routing step goes into effect as a sequence on the routing for an item.
• When a rate schedule is in effect the default is the current system date.
You can enter future effective dates so that the system plans for upcoming changes. You
can still record and recognize items that are no longer effective in the future in Product
Costing, Shop Floor Management, and Capacity Requirements Planning. Material
Requirements Planning determines valid components by effectivity dates, not by the bill
of material revision level. Some forms display data based on the effectivity dates you
enter.
Thru • When a component part is no longer in effect on a bill of material.
• When a routing step is no longer in effect as a sequence on the routing for an item.
• When a rate schedule is no longer active.
The default is December 31 of the default year that is defined in the Data Dictionary for
Century Change Year. You can enter future effective dates so that the system plans for
upcoming changes. You can still record and recognize items that are no longer effective
in the future in Product Costing, Shop Floor Management, and Capacity Requirements
Planning. Material Requirements Planning determines valid components by effectivity
dates, not by the bill of material revision level. Some forms display data based on the
effectivity dates that you enter.
Time Enter a UDC (30/TB) that indicates how machine or labor hours are expressed for a product.
Basis Time basis codes identify the time basis or rate to use for machine or labor hours that are entered
for every routing step (for example, 25 hours per 1,000 pieces or 15 hours per 10,000 pieces).
You can maintain the time basis codes in the Time Basis Codes UDC (30/TB).
The system uses the values in the Description-2 field on the User-Defined Code form for costing
and scheduling calculations. The description is what the code represents, but it is not used in
calculations.
Setting Up Supplier Release Scheduling

This chapter provides an overview of the supplier release scheduling setup and discusses how to:
• Define supplier contract information
• Define shipment patterns
• Define supplier split percentages
Understanding Supplier Release Scheduling Setup

To perform supplier release scheduling, you need to set up information for each of the suppliers and for the
items that you are planning to purchase. The information that is required to generate supplier release
schedules varies, depending on whether you want to generate schedules that are based on blanket orders or
ad-hoc schedules. You can enter ad-hoc schedules interactively through the self-service portal work spaces
or generate them when running the Supplier Schedule Generation program (R34400).
If you want to schedule releases against blanket orders, you set up supplier schedule master information that
is tied to a blanket order, such as:
• Shipment pattern and dates.
This setup indicates the days of the week that you accept deliveries.
• Supplier split percentages.
You use this value to use more than one supplier for an item.
Page 40 of 135
• Frozen days
You use this value to specify the time period after the schedule generation date during which
quantities cannot be changed and no releases are permitted.
• Releasable schedule days
Releasable schedule days indicate the time fence from the schedule generation date for releasing
committed quantities.
To create ad-hoc schedules, you can set up shipment patterns and dates, as well as split percentages
without a blanket order; and use information set up for the item in the Item Branch program (P41026), such
as:
• Supplier
• Freeze fence
You do not have to set up a release fence for ad-hoc schedules until you actually run the Supplier Schedule
Release Generation program (R34410). You use a processing option to define the period in days from the
generation start date within which committed quantities can be converted into purchase orders.
Defining Supplier Contract Information

This section provides an overview of supplier contract information, lists the prerequisites, and discusses how
to:
• Set processing options for Supplier Schedule Master Revisions (P4321).
• Set up supplier contracts.
Understanding Supplier Contract Information

When you set up a supplier contract that is based on a blanket order, you can define information, such as
time fence periods and releasable schedule days. You can also specify a delivery location, a minimum
shipment quantity, and a shipment lead time. Finally, you can define whether you display the supplier
schedule in days, weeks, or months.
When you generate a schedule, the system:
• Sorts blanket order releases that are outstanding into appropriate time periods.
• Accumulates past due quantities and quantities that you received prior to the requested date.
• Expresses past due amounts as positive numbers in the Past Due field.
• Expresses early receipt amounts in the Early Receipt field and adds the amounts to the cumulative
received quantity.
When you regenerate the schedule, the system displays the quantities in the Past Due and Early Receipt
fields on the Vendor Schedule Master Revisions form. When you delete supplier information, the system
deletes the entire record, including the history.
Note. It is recommended that you specifically designate items for which you want to create vendor
schedules. You can use category codes to use an item for supplier release scheduling.
Prerequisite
Create a blanket order line for every item that you want to schedule, using blanket scheduling.
Page 41 of 135
Form Used to Set Up Supplier Contracts
D
Vendor W432 DRP Daily Operations (G3411), Enter the schedule

Schedule 1C Enter/Change Supplier Info. information that
Master MRP Daily Operations (G3413), represents the supplier
Revisions Enter/Change Supplier Info. contract
On Work With Vendor Schedule Master,
complete the Order Number, Line Number,
Order Type and Order Company fields and
click Add.
Setting Processing Options for Supplier Schedule Master Revisions (P4321)

Use these processing options to specify the default processing for programs and reports.
Versions
This processing options specify the version of each program.
Enter the version of each program. If you leave this option blank, the system uses ZJDE0001.
1: Purchase Order Header, Purchase Order Header (P4310)
2: Purchase Orders, Work With Purchase Order Detail (P4310)
3: Supplier Schedule (P34301)
4: Supplier Split Percentage (P43211)
Defaults
These processing options specify the default processing.
1. Enter the Specify a UDC (00/DT) that identifies the origin and purpose of the transaction. The
Document Type to reserved document type prefixes for codes are:
display. P: Accounts payable
R: Accounts receivable
T: Time and Pay
I: Inventory
O:: Purchase order
S: Sales order
2. Work Day Calendar Specify a UDC (42/WD) to define how to use the calendar. For example, the calendar
Type might be specific to an industry, such as banking, or you might use it to schedule
delivery persons for a route.
Note. If you use the default value of * (asterisk), the system updates the value to
blank even though blank is not set up as a value in the UDC table.
3. Work Day Calendar Specify a code to classify values within a calendar type. For example, if the calendar
Key type is ROUTE, you can enter a code that specifies a particular route, such as Daily
or Weekend.
Note. The system does not validate the code that you enter.
Setting Up Supplier Contracts

Access the Vendor Schedule Master Revisions form.
Vendor Master Schedule Revisions form
Page 42 of 135
Releasable Days Enter a time fence that indicates the number of workdays from the generation start date
to use when identifying the cutoff date for actual blanket order releases. The system
uses the time fence when you run the supplier schedule release generation program.
Deliver to Location Enter the location to which a shipment should be delivered, such as a particular
receiving dock or work center.
Shipment Quantity Enter the minimum quantity that the supplier is willing to ship.
Ship Units/Cont Enter the standard quantity of containers that you use in the manufacturing process
(ship units/container) (typically, in a repetitive manufacturing environment). The quantity that you enter
determines the number of bar code labels that you will need for shipping. It also
modifies order release quantities.
Identifies the container requirements of the supplier. When the system generates the
supplier schedule, it calculates the shipping units per container as a multiple and
adjusts the planned quantities as needed.
Shipment Leadtime Enter the time it takes a shipment to move from the supplier's dock to the customer's
dock. The system uses this value to offset the required date to determine the actual
date that the shipment should take place. The shipment leadtime is also known as
transit time. The level leadtime for a purchased item should include the shipment
leadtime.
Vendor Lot Size Enter a value that identifies the lot size requirements of the supplier. When the system
generates the supplier schedule, it calculates the vendor lot size as a multiple and
adjusts the planned quantities as needed.
Frozen Days Enter the number of workdays from the generation start date that the quantity buckets
will be frozen with no changes and releases possible. The system also uses this value
to calculate the cumulative frozen quantity (see CFRO).
Fabrication Days Enter the number of workdays, from the generation start date, that the customer
guarantees the fabrication costs for the quantity that was ordered.
Raw Material Days Enter the number of workdays, from the generation start date, that the customer
guarantees the raw material costs for the quantity that was ordered.
Vendor Schedule Select an option to create the vendor schedule in days, weeks, or months.
D/W/M
Number Enter the number of workdays, weeks, and months to display on the supplier schedule.
Defining Shipment Patterns

This section provides an overview of shipment patterns and discusses how to:
• Create shipment patterns.
• Revise shipment dates.
Understanding Shipment Patterns

You must define which days are valid to receive a shipment. You can define a pattern that governs the
frequency of supplier deliveries. For example, you can define one of shipment patterns such as:
• All work days.
• Every Monday.
• Monday through Friday of the first and third weeks of the month.
To set up a shipment patterns and shipment dates for a supplier schedule that is based on a blanket order,
you access the Shipment Pattern Revisions (P43212) and Shipment Date Revisions (P43213) programs
from the Supplier Schedule Master Revisions program.
Note. If you are creating ad-hoc schedules and need to set up a shipment pattern for the supplier, you
access these programs from the menu.
Page 43 of 135
Forms Used to Define Shipment Patterns
D
Shipment W4321 On Vendor Schedule Master Enter the date pattern for the
Pattern 2A Revisions, select Shipment Pattern shipments that you receive
Revisions from the Form menu. from a supplier
Shipment W4321 Vendor Schedule Master Revisions, Revise the shipment pattern
Date 3B select Shipment Dates from the you created before, when
Revisions Form menu. necessary.
On Work With Shipment Dates,
select a record and click Select.
Creating Shipment Patterns

Access the Shipment Pattern Revisions form.
Shipment Pattern Revisions form
Day of Week Select the check boxes to indicated the day(s) that you allow shipments. Selecting any of the
check boxes disables the Day of Month and All Work Days options.
Day Of Month Enter a specific day of the month (1 through 31) when shipments you allow shipments.
All Work Days Select this check box to allow shipments on any work day.
Week of Select the check boxes to indicate the week(s) that you allow shipments. Selecting the fourth
Month check box indicates that the shipment pattern is valid from the 22nd through the 28th of the
month.
Recur Every Enter a code that determines the weekly pattern that the system builds based on the effective
Week(s) from date.
Codes are:
1: Every week is scheduled.
2: Every second week is scheduled.
Revising Shipment Dates

Access the Shipment Date Revisions form.
Shipment Date Revisions form
Defining Supplier Split Percentages

This section provides an overview of supplier split percentages and discusses how to set up supplier split
percentages.
Understanding Supplier Split Percentages

Buyers can order the same item from multiple suppliers to avoid relying on a single supplier. Supplier
scheduling enables multiple suppliers to supply a single item, based on a predetermined split percentage.
Use the Supplier Split Percentages Revisions program (P43211) to define the split percentages among the
suppliers.
Page 44 of 135
Form Used to Set Up Supplier Split Percentages
D
Work With W4321 DRP Daily Operations If you use more than one supplier you
Supplier Split 1C (G3411), Supplier Split define the delivery volume
Percentages Percentages. percentage for each supplier.
MRP Daily Operations
(G3413), Supplier Split
Percentages
Setting Up Supplier Split Percentages

Access the Supplier Split Percentage Revisions form.
Supplier Split Percentage Revisions form
Split Enter the percentage to apply.

Percent For Suppler Release Scheduling, enter the percentage of the planned quantity that the system
applies to the corresponding supplier. The total planned quantity must equal 100 percent.
Otherwise, the system displays an error message.
Planning Production Capacity

This chapter provides an overview of capacity planning and discusses how to:
• Generate resource requirements plans.
• Validate resource requirements plans.
Understanding Capacity Planning

Use Capacity Planning to ensure that sufficient capacity is available to accomplish the planned production
schedule that is generated by Master Production Schedule (MPS) or Material Requirements Planning (MRP).
If sufficient capacity is not available, then you must alter the plan or the capacity.
EnterpriseOne Capacity Planning comprises:
• Resource Requirements Planning (RRP)
• Rough Cut Capacity Planning (RCCP)
• Capacity Requirements Planning (CRP)
This flowchart illustrates the planning system:
Page 45 of 135
Capacity Planning
RCCP identifies capacity constraints at critical work centers.

CRP matches the available personnel and equipment resources to the resource requirements as generated
by MRP. CRP indicates whether you need to revise the material requirements plan or increase resources.
Work center capacity is based on available hours to produce products within certain time frames. MPS,
MRP, and Shop Floor Management provide the actual hours to produce products, based on the quantity that
is required.
Manufacturing must determine whether the production plan is supportable as is or whether additional future
resources are needed, such as:
• Additional skilled labor.
• New machinery.
• New facilities or additional real estate.
Demand forecasting is the logical starting point for developing a resource requirements plan. However, you
must remember that the demand forecast is not the actual plan, but that it is used as input into the plan. RRP
provides an estimate of the time and resources that you need to produce a product.
You generate a resource requirements plan after you generate the long-term forecast but before you run the
Master Scheduling program. RRP uses the data from a forecast of future sales to estimate the time and
resources that are required to meet the production plan.
RRP can help you resolve long-range planning issues, such as:
• Expanding existing facilities.
• Acquiring new facilities.
• Staffing loads.
• Determining capital expenditures for equipment.
RRP enables you to support the company's strategic business plan with a realistic tactical plan. The tactical
plan:
Page 46 of 135
• Is shorter in range than the strategic plan and has a planning horizon of 12 months to 3 years.
• Enables planning at the product family level and has greater detail than the strategic plan.
• Validates the monetary amounts that are allotted to the business plan.
The Resource Requirements Planning program (P3380) generates a capacity plan by critical work center. To
answer long-range planning questions, you need to know the current capacity and the requirements to
support the planned workload.
Generating Resource Requirements Plans

This section provides an overview of resource requirements planning and discusses how to set processing
options for Resource Requirements Planning.
Understanding Resource Requirements Planning

After you have entered resource units and resource profiles, you run the Resource Requirements Planning
Regeneration program to generate the resource requirements plan. The plan contains long-range estimates
of the capacity needs at the work centers. These needs might include:
• The number of production staff that you need to hire to meet future production needs.
• The number of additional machines that you will need for a new product line.
• The real estate that you will need to buy for additional facilities.
Because you use the forecast in place of work orders for long-range planning, the data that this program
creates is an estimate of capacity needs that is based on the forecast. The resource profile offsets required
dates for capacity.
The types of data that you can create include:
• Over-capacity or under-capacity messages.
• Period summaries about work centers.
• New load profile information based on the type of work center load:
 Rated profile is the number of available units from the Work Center Resource Units table
(F3007).
 Loaded profile is the forecasted load that is derived from the master planned items' forecasts
and their resource profiles.
 Percent resource used is the loaded profile divided by the rated profile.
 Resource available is the rated profile minus the loaded profile.
 Accumulated resources available is a running total of the resources that are available.
When you set up the versions for planning the resource requirements, you need to determine the data
selection for work centers, branch/plants, and dispatch groups that you want to process.
Work centers to process

You can make one of these choices:
• N: Process only non-critical work centers.
• 1: Process critical work centers in calculating resource requirement plans only.
• 2: Process critical work centers in calculating capacity requirements plans only.
• 3: Process critical work centers in calculating resource requirements plans and capacity
requirements plans.
• 4: Not a capacity work center (will not be processed in Capacity Requirements Planning).
Page 47 of 135
Branch/plant and dispatch group
You can select specific information for planning facilities and dispatch groups:
• A specific planning facility or the dispatch groups, or both.
• A group of planning facilities or the dispatch groups that are using the RANGE or LIST values, or
both.
Prerequisites
Before generating requirements plans, verify:
• Resource units exist for all of the work centers in the facility.
• Resource profiles exist for all of the master-scheduled items.
• Resource profile is set up with the appropriate units of measure.
You can use a maximum of five units of measure.
• Create a detail forecast for the master-scheduled items using the Forecast Revisions program
(P3460).
See Working with Detail Forecasts.
• Determine which forecast types that you want to use in the generation.
You can use a maximum of five.
See Setting Up Summary Forecasts.
• Set up the shop floor calendar for all summary time periods for which you want to generate resource
requirements plans.
Setting Processing Options for Resource Requirements Planning Regeneration

(R3380)
Use these processing options to set planning parameters, specify forecast types used as input, and specify
the output unit of measure.
From the Periodic Resource/Capacity Planning menu (G3321), select Resource Requirements Planning.
Bucket Info
These processing options specify the regeneration start date, the planning horizon periods, and the past due
periods in a planning process.
1. Regeneration Specify the date that the program uses to start the planning process. This date is also
Start Date the beginning of the planning horizon.
If you leave this option blank, the system uses the system date.
Number of Specify the number of weeks that the system creates in a planning period. For example,
Planning Weeks when the system displays the Time Series program (P3413), the system also accesses
data for the number of planning weeks.
Number of Specify the number of months that the system creates in a planning period. For
Planning Months example, when the systems displays the Time Series program, the system also
accesses monthly data for the number of planning months.
3. Past Due Specify the number of past due periods that the system generates for a loaded profile.
Periods These values represent the number of past due periods for the program's generation
date. Values are:
0: Zero periods (default)
1: One past due period
2: Two past due periods
Process
Page 48 of 135
These processing options enable you to specify the branch that a system uses for the CRP/RCCP
Regeneration program (R3382) and the percentages for underrated and overrated capacity. Additionally, you
determine whether you want work centers to be rolled up by dispatch group in the planning.
1. Branch Specify the branch that the system uses for the CRP/RCCP Planning Regeneration
program.
2. Under Rated Specify the tolerance percent under the rated capacity that the system uses to determine
Capacity whether a work center is underloaded. The system displays messages with a status of U
Percent (under) for capacity loads that are less than the identified percentage under the rated value.
For example, if the rated capacity is 100 units and the underrated capacity is set to 5
percent, then the system still considers a capacity load of 95 units as a valid load at a work
center. Similarly, the system would consider a capacity load of 94 units as an underload.
3. Over Rated Specify the tolerance percent over the rated capacity that the system uses to determine
Capacity whether a work center is overloaded. The system displays messages with a status of O
Percent (over) for the capacity load that is greater than the identified percentage over the rated
value.
For example, if the rated capacity is 100 units and the overrated capacity is set to 5
percent, then the system would still consider a capacity load of 105 as a valid load at a
work center. Similarly, the system would consider a capacity load of 106 units as an
overload.
4. Roll Up To Specify whether multiple work centers within a dispatch group roll up to that dispatch group
Dispatch Group for review. Values are:
Blank: Do not roll up work centers to a dispatch group.
1: Roll up work centers to a dispatch group.
Forecast Types
These processing options enable you to specify the forecast type that the system processes when it runs the
Resource Requirement Planning Regeneration program. You can enter up to five forecast types in the
system. Forecast types are user defined and stored in the F3460 table.
Forecast Type 1 through Specify the forecast type that the system processes when you run the
Forecast Type 5 Resource Requirements Planning program.
Forecast types are user defined and are stored in the Detail Forecast table.
UOM
This processing option enables you to specify the units of measure that the system processes when you run
the Resource Requirements Planning Regeneration program. The system can process up to five units of
measure at a time.
Unit of Measure 1 through Unit Specify the unit of measure that the system processes when you run the
of Measure 5 Resource Requirements Planning program.
Validating Resource Requirements Plans

This section provides an overview of resource requirements plan validation and discusses how to:
• Set processing options for Capacity Message Summary (P3301).
• Review dispatch groups.
• Set processing options for Capacity Load (P3313).
• Review work center loads.
• Set processing options for Period Summary (P3312).
• Review period summaries.
• Set processing options for Capacity Planning Message Revisions (P3311).
Page 49 of 135
• Review capacity planning message details.
Understanding Resource Requirements Plan Validation

Validating a resource requirements plan consists of identifying the overloaded work centers, making
adjustments in forecast or resources, and generating the plan again to see whether the adjustments
distributed the loads among the work centers. Repeat the steps until all of the loads at each work center are
appropriate.
Resource Requirements Plans

When you generate a resource requirements plan, the system creates a time series that displays the load
during each planning period for a work center. If you organize several work centers as a dispatch group
according to common functions, similar operations, or steps in a routing, you can view the group to see how
the production plan affects the capacity of the work centers as a group.
You can review summaries of each period to determine the load that is placed on a work center by each item
or order. You can also review messages for each work center and delete, clear, or the hold messages.
If the system encounters over-capacity or under-capacity conditions, you can review the plan and identify the
periods or work centers in which the conditions occur. You might have to adjust the forecast or capacity, and
then generate the resource requirements plan again.
Dispatch Groups for RRP

If several work centers are organized as a dispatch group, you can review the group to determine how
capacity affects all of the work centers in the group. Dispatch groups enable you to organize work centers
according to common functions, similar operations, or steps in a routing.
When you review dispatch groups, you can also review messages about all the work centers in the group
and use that information to redistribute the load within the group.
Work Center Load for RRP

The Resource Requirements Planning Regeneration program provides a numerical breakdown, by planning
period, of the capacity load that is placed on a work center. Use this information to determine whether to
adjust capacity or the forecast.
The code in the Prime Load field on the Work Center Master Revisions form determines the type of load. For
example, if you enter machine and setup hours as the prime load code, the numbers that appear differ from
those that appear if you enter machine hours only.
Calculations for the types of load are:
Calculation Type Description
Rated profile The amount of capacity that is available for a work center.
Loaded profile The capacity that is required to meet the forecast

Loaded profile = (forecast quantity × labor or machine hours) ÷ (efficiency × utilization) ×
time basis code.
Percent resource The loaded profile divided by the rated profile.

used
Resource available The rated profile minus the loaded profile.
Accumulated A running total of resources that are available.

resources available
Page 50 of 135
When the system calculates the demand, it is offset by the Resource Offset value from the Capacity
Resource Profile table (F3303). The resource offset determines the number of days that the actual use of a
work center resource should be offset from the forecasted need.
Period Summaries
In addition to reviewing the capacity load of a work center, you can also evaluate the load that is placed on a
work center. Evaluate the load by period and by item. You can review:
• The items that are scheduled for a work center.
• The number of units of an item that make up the load.
• The percent of the total load on the work center that is for a specific item's forecast.
The system summarizes the load by the period, using the unit of measure that you specify.
You use this information to determine whether to adjust the forecast or the capacity at the work center.
Message Detail
Each time that you generate a resource requirements plan, the system creates messages to identify work
centers with loads that conflict with planned capacity. Review Message Detail indicates whether you have
overload or underload conditions. Messages for each work center appear alphabetically by message type.
Use the Capacity Planning Message Revisions program to clear, hold, or delete messages. You cannot
process capacity messages. You can add remarks for each message to record the actions that you take. In
addition, you can access related forms to confirm or change dates, amounts, and manufacturing data for key
plants for the work center.
You can generate a plan more than once. When you regenerate a resource requirements plan, the system
deletes all messages except:
• Messages that you entered manually.
• Messages that you placed on hold.
See Also
Revising Detail Forecasts
Forms Used to Validate Resource Requirements Plans

D
Work With Capacity W330 Daily Resource Requirements Determine how capacity
Message Summary 1A Planning (G3311), Review Dispatch affects work centers.
Group
Review Work W331 Daily Resource Requirements Determine required

Center Load 3A Planning (G3311), Review Work adjustments to capacity or
Center Load. forecast.
Work With Period W331 Daily Resource Requirements Evaluate work center load.
Summary Review 2A Planning (G3311), Review Period
Summary
Work With Capacity W331 Daily Resource Requirements Release, clear or place
Messages 3B Planning (G3311), Review Message messages on hold.
Detail
Capacity Message W331 On Work With Capacity Messages, Delete messages.

Revisions 1A select Revisions from the Row
Page 51 of 135
D
menu.
Setting Processing Options for Capacity Message Summary (P3301)

Use these processing options to set default values and specify versions.
Defaults
These processing options specify the default processing.
1. Enter the Critical Work Center Specify a code that indicates whether the work center is critical or not
Code to be displayed or blank for all critical when the system calculates capacity. Values are:
Work Centers N: Not a critical work center.
3: A critical work center in calculating RRP, RCCP, and CRP. The
system also displays Type 3 work centers when you select Type 1 or
Type 2 in this field.
4: Not a capacity work center. The system does not include this work
center in capacity planning.
Note. The data selection is a system feature that processes certain
groups of information with the RRP, RCCP, and CRP programs.
2. Enter the Capacity Mode Specify a code indicating which planning is being used. Values are:
1: Resource Requirements
2: Rough Cut Capacity
3: Capacity Requirements
3. Enter the default Unit of Measure Specify a UDC (00/UM) that identifies the unit of measurement for an
amount or quantity. For example, it can represent a barrel, box, cubic
meter, liter, hour, and so on.
Versions
This processing option specifies the version of the program.
Work Center Specify the version for the Work Center Revision program. If left blank, version ZJDE0001
Revision will be used. Identifies a specific set of data selection and sequencing settings for the
(P3006) application. Versions may be named using any combination of alpha and numeric
characters.
Reviewing Dispatch Groups

Access the Work With Capacity Message Summary form.
Dispatch Group Enter a category code used to group work centers within an overall business unit.
For example, you can use this code to group similar machines operating out of
several work centers that report to one business unit.
All W/C (all work Select the option to specify the type of processing for an event.
centers)
Critical W/C (critical Enter a code that indicates whether the work center is critical or not critical when the
work center) system calculates capacity. Values are:
N: Not a critical work center.
Page 52 of 135
3: A critical work center in calculating RRP, RCCP, and CRP. The system also
displays Type 3 work centers when you select Type 1 or Type 2 in this field.
4: Not a capacity work center. The system does not include this work center in
capacity planning.
Note. The data selection is a system feature that processes certain groups of
information with the RRP, RCCP, and CRP programs.
Message Type Enter a code that distinguishes different messages generated in Capacity Planning.
Values are:
A: Warning messages
M: Manual messages
O: Over capacity
U: Under capacity
U/M (unit of measure) Enter a UDC (00/UM) that indicates the quantity in which to express an inventory
item, for example, CS (case) or BX (box).
Outstanding Enter a brief description of an item, remark, or explanation.
Messages A summary of the detailed messages for the work center. For example, if the work
center has four under-capacity messages (message type U), this field displays
UUUU.
Setting Processing Options for Capacity Load (P3313)

Use these processing options to set default values and specify versions.
Defaults
These processing options specify the defaults for processing.
1. Enter the Capacity Specify a code indicating which level of planning is being used. Values are:
Mode 1: Resource Requirements
2. Enter the User Defined Specify a code that identifies the table that contains UDCs. The table is also
Code for the list of row referred to as a UDC type.
descriptions to appear
3. Enter the default Unit of Specify a UDC (00/UM) that identifies the unit of measurement for an amount or
Measure quantity. For example, it can represent a barrel, box, cubic meter, liter, hour, and
so on.
4. Enter the version of the Specify a user-defined set of specifications that control how applications and
Dispatch List program to reports run. You use versions to group and save a set of user-defined
call. The default is processing option values and data selection and sequencing options. Interactive
ZJDE0001. versions are associated with applications (usually as a menu selection). Batch
versions are associated with batch jobs or reports. To run a batch process, you
must select a version.
Versions
This processing option specifies the version of the Operation Dispatch Inquiry program.
Enter the version for each program. Operation Dispatch Inquiry (P31220)
If left blank, version ZJDE0001 will Specify a specific set of data selection and sequencing settings for
be used. the application. Versions may be named using any combination of
alpha and numeric characters.
Page 53 of 135
Reviewing Work Center Loads
Access the Review Work Center Load form.
Description Review the type of calculation used to determine the work center load: Rated Profile, Loaded
Profile, % Resource Used, Resource Available, Accumulated Resource Available.
Setting Processing Options for Period Summary (P3312)

Use these processing options to set system defaults and specify versions.
Defaults
These processing options specify the defaults used for processing.
1. Enter the Specify a code indicating which level of planning is being used. Values are:
Capacity Mode 1: Resource Requirements
2. Enter the Specify a UDC (00/UM) that identifies the unit of measurement for an amount or quantity.
default Unit of For example, it can represent a barrel, box, cubic meter, liter, hour, and so on.
Measure.
3. Enter the Specify a user-defined set of specifications that control how applications and reports run.
version of the You use versions to group and save a set of user-defined processing option values and
Dispatch List to data selection and sequencing options. Interactive versions are associated with
call. applications (usually as a menu selection). Batch versions are associated with batch jobs
or reports. To run a batch process, you must select a version.
Versions
These processing options specify the version of the program.
1. Work Center Revision Specify a specific set of data selection and sequencing settings for the application.
(P3006) Versions may be named using any combination of alpha and numeric characters.
If left blank, version ZJDE0001 will be used.
2. Forecast Revision Specify a specific set of data selection and sequencing settings for the application.
(P3460) Versions may be named using any combination of alpha and numeric characters.
3. MRP/MPS Message Specify a specific set of data selection and sequencing settings for the application.
Revision (P3411) Versions may be named using any combination of alpha and numeric characters.
4. Mfg Scheduling Specify a specific set of data selection and sequencing settings for the application.
Workbench (P31225) Versions may be named using any combination of alpha and numeric characters.
Reviewing Period Summaries

Access the Work With Period Summary Review form.
Period Displays the date that an item is scheduled to arrive or that an action is scheduled for completion.
End
Units Displays a value that represents the available quantity, which might consist of the on-hand
balance minus commitments, reservations, and backorders. You enter this value in the
Branch/Plant Constants program.
Percent Displays the percent received.
Order Displays a number that identifies an original document. This document can be a work order, a
Number sales order, a forecast, a planned order, and so on.
Setting Processing Options for Capacity Planning Message Revisions (P3311)

Use these processing options to specify system defaults.
Page 54 of 135
Defaults
These processing options specify the defaults used by the program.
1. Enter the Capacity Mode Specify the capacity mode.

1: Resource Requirements
2. Enter the default Unit of Specify a UDC (00/UM) that identifies the unit of measurement for an
Measure amount or quantity. For example, it can represent a barrel, box, cubic meter,
liter, hour, and so on.
3. Enter the default version of Specify a specific set of data selection and sequencing settings for the
Work Center Revision (P3006) application. Versions may be named using any combination of alpha and
numeric characters.
Reviewing Capacity Planning Message Details

Access the Work With Capacity Messages form.
Work With Capacity Messages form
Message Displays a code that distinguishes different messages generated in Capacity Planning. Values
Type are:
A: Warning messages
M: Manual messages
O: Over capacity
U: Under capacity
Message Review the associated message.
To clear a message, select it and select Clear from the Row menu.
To view cleared messages, check the Include Cleared box and click Find.
To hold or release a message, select it and select Hold/Release from the Row menu. Messages
on hold are highlighted. The system retains held messages until you manually release, clear, or
delete them.
Total Units Enter a value that represents the available quantity, which might consist of the on-hand balance
minus commitments, reservations, and backorders. You enter this value in the Branch/Plant
Constants program.
To delete a message, access the Capacity Message Revisions form, select the message and
click Delete.
Planner Enter a remark about an item.
Remark
Planning Material Requirements

This chapter provides an overview of material requirements planning (MRP), lists the prerequisite, and
discusses how to:
• Analyze planning input.
• Generate material requirements plans.
• (Rapid Start) Plan requirements for an inventory item.
• Analyze planning output.
Page 55 of 135
• Process planning output.
• (Rapid Start AUS, CAN, NZL, and USA) Review detailed messages.
Understanding Material Requirements Planning

Single-facility planning encompasses the generation of a distribution or production plan for one facility. All
supply and demand calculations occur within a single branch/plant. If an item is available in other
branch/plants, it is not considered during single-facility planning.
Analyzing Planning Input

This section provides an overview of planning input and discusses how to:
• Set processing options for Net Change Review (P3402).
• Review items for net change.
Understanding Planning Input

Prior to generating a requirements plan, planners review input data that is used by the planning system for
accuracy and changes. Data that is used by requirements planning is derived from sales orders, forecasts,
bills of material, and item net change activities.
If forecasts change in response to market conditions, these changes affect the requirements plan generation.
An inquiry on the bill of material provides information about item lead time and part availability.
Item Net Change

Use the Net Change Review program to review items that have changed, either through planned or
unplanned activities throughout the Requirements Planning system. You can locate a selected group of
items by planner number, planning family, branch/plant, and specific planning codes. You can access related
time series, inventory, and scheduling information forms for any of the items.
If an item has changed, it appears on the Work with Net Change and Summary form with a Y in the Net
Change field.
This table identifies the activities that automatically activate the net change flag:
Activity Net Change
Parts List Any addition, change, or deletion activates the flag for that item. If a branch
Revisions changes for an item, the system updates both old and new locations.
Parts List Any selection activates the flag for both the selected item and the item being
Substitutes substituted.
Work Order Any addition or deletion activates the flag for the item. If you change a request
Entry date for an item or quantity, the system activates the flag for the item. If an
item status changes to 99, and the quantity ordered is not equal to the
quantity completed, the system activates the flag for that item. If a branch
changes for an item, the system updates both old and new locations.
Work Order Only over-issues activate the flag.

Inventory
Issues
Work Order If an item status changes to 99 and the quantity ordered does not equal the
Inventory quantity completed, the system activates the flag for that item.
Completions
Page 56 of 135
Activity Net Change
Inventory The system activates the flag for any item with an adjusted inventory.
Adjustments
Inventory When inventory is transferred from one branch to another, the system
Transfers activates the flag for the affected items in both locations.
Bill of Any addition or deletion of a component item activates the flag for the parent
Materials of the changed component. If the item, quantity per, scrap, or effectivity dates
Master change for any component item, the system activates the flag for the parent of
that component.
Where Used Any change to a component item activates the flag for the parent of the
Bill of Material changed component.
Update
Detail If you take action on an order message, and the quantity, start date, or request
Message date changes, the system activates the flag for the item. If you take action on
Review an expedite or defer message, and the recommended start date or
recommended request date changes, the system activates the flag for the
item.
Forecast Any addition, change, or deletion activates the flag for the item.
Revisions
Manufacturing Any addition, change, or deletion activates the flag for the item.
Data
Revisions
Repost Open A repost cancels the committed quantity of any component inventory on work
Quantities orders that have a status equal to the status that is indicated in the processing
option (usually status 99). The repost activates the flag for any canceled
inventory.
Leadtime This program can change critical manufacturing data in the Item Branch table
Rollup (F4102) table. If changed, the flag is updated for an item.
Sales Order Any addition, change, or deletion activates the flag for the item.
Entry
Purchase Any addition, change, or deletion activates the flag for the item.
Order Entry
Net Change Any manual update to the Net Change field activates the flag for the item.
Review
Additionally, any transaction that causes a change in supply or demand during the next MRP run updates the
net change flag in the F4102 table. Examples include:
• You have taken action on an order message, and either the quantity, start date, or requested date
changes.
• You have taken action on an expedite or defer message, and the recommended start date or
recommended requested date changes.
• You cancel an order.
Page 57 of 135
See Also
Understanding Forecast Management
Working with Work Orders and Rate Schedules
Prerequisite
Validate a resource requirements plan.
See Generating Resource Requirements Plans.
Form Used to Analyze Planning Input

D
Work With Net W340 Single Site Periodic Planning Verify items with changes that
Change 2A Operations (G3422), Net affect the material requirements
Summary Change Review plan generation.
Setting Processing Options for Net Change Review (P3402)

Use this processing option to default the planning code in the Planning Code field when accessing the Work
With Net Change Summary program.
Defaults
This processing option specifies the default used by the program.
1. Planning Code Specify a planning code, or leave this field blank to include all planning codes.
Codes are:
Blank: Include all planning codes.
0: Not planned by MPS, MRP, or DRP.
1: Planned by MPS or DRP.
2: Planned by MRP.
3: Planned by MRP with additional independent forecast.
4: Planned by MPS, parent in planning bill.
5: Planned by MPS, component in planning bill.
These codes are hard-coded.
Reviewing Items for Net Change

Access the Work With Net Change Summary form.
Work With Net Change Summary form
Planner Enter the address number of the material planner to limit the search for only those items
Number associated with this planner.
Net Change Review the net change value.
If an item has changed, it appears on the Work with Net Change and Summary form with a Y in
the Net Change field.
You can update the net change flag from the Net Change Review program. Set the security
parameters so that only appropriate personnel, such as the master scheduling supervisors,
have access.
Generating Material Requirements Plans

Page 58 of 135
This section provides an overview of material requirements planning and discusses how to set processing
options for MRP/MPS Requirements Planning (R3482).
Understanding Master Schedules

You can generate a master schedule for a single item or all items. When you generate a master schedule,
the system evaluates selected information, performs calculations, and recommends a time-phased planning
schedule for all selected items. At a minimum, you should generate a master schedule weekly to keep the
plan current.
DRP Regeneration and MPS Regeneration use versions of the MRP/MPS Requirements Planning program
to produce a single-level DRP or MPS schedule for all items that meet the data selection criteria. The
program:
• Reads the selected forecast and sales orders.
• Uses data from the DRP/MPS/MRP inclusion rules to calculate requirements for master planned
items.
• Does not explode planned orders to the bill of material components.
The MRP Regeneration version of the MRP/MPS Requirements Planning program explodes planned orders
for bill of material items to produce a multilevel material plan.
Before the program generates a schedule, it deletes the message and time series tables for the selected
items.
When you set up the versions to generate a planning schedule, you should consider:
• Data selection: base the data selection on branch/plant, category codes (usually master planning
family), and planning code.
Any selection from based-on table fields can be processed.
• Data sequence: copy the data sequence from the report example.
Do not change this sequence, or unpredictable results might occur.
Understanding Net Change Planning Schedules

You can set the Generation Mode processing option to use net change processing if you want to have
Regeneration and Net Change versions. With net change processing, the system includes only those items
that have changed since the last generation. Use the Net Change Review program to determine which items
to include in the net change generation.
DRP Net Change, MPS Net Change, and MRP Net Change are versions of the MRP/MPS Requirements
Planning program. Use a processing option to specify net change. You can further define the data selection
to include only specific items that appear on the Work With Net Change Summary form. When you run DRP
Net Change, MPS Net Change, or MRP Net Change, the system:
• Evaluates selected information.
• Performs calculations.
• Generates a time series and messages for the selected items.
The system selects items from the Net Change Review program that are based on:
• Bill of material changes.
• Inventory transactions.
• Forecast adjustments.
• Work order changes.
• Purchase order changes.
• Lead time roll-up that results in new lead time values.
Page 59 of 135
• Sales order changes.
• Changes in parent order requirements.
You should run net change on a regular basis to continually update the schedule. The program writes to the
Action Message, Pegging, and Time Series tables. You can view the information that is generated by this
program online by using the time series and message review programs.
Understanding Material Requirements Planning

Use the MRP- Gross Regeneration version of MRP/MPS Requirements Planning to produce a single-facility
MRP planning schedule for the items that you select. Alternatively, you can use the MRP - Net Change
version of MRP/MPS Requirements Planning to produce a single-facility MRP planning schedule. You can
generate a material requirements plan for:
• A single item.
• All items.
• Only items that are affected by transactions since the last generation.
When you generate a material requirements plan, the system evaluates selected information, performs
calculations, and recommends a time-phased replenishment plan for all selected items. MRP regeneration
uses the same programs as DRP/MPS regeneration.
MRP output consists of information in the time series, action messages, and pegging. Use the time series
information to decide whether to accept the planning that is suggested by the system or to override it. You
should review the action messages for individual item numbers to determine which action, if any, that you
need to take. Use pegging to identify parent demand for components.
MRP runs most effectively when you ensure the accuracy and validity of the following planning information:
Planning Description
Informatio
n
Master Ensure that the master schedule is at least 95 percent accurate. Accuracy is
schedule measured by comparing the creation of an end product to the performance of the
schedule.
Bill of Ensure that the bill of material is at least 98 percent accurate and contains the
material correct components and quantities. Accuracy is measured by comparing how the
item is built in the factory to the correct components and quantities that are
contained in the bill of material.
Inventory Ensure that the inventory count is at least 95 percent accurate. You achieve this
accuracy through the cycle count process.
Lead times Ensure that the lead times are valid. The system provides planned lead times. In
runtime, the actual time to complete an order can vary.
Bill of Material
MRP uses the bill of material to explode demand to all component items. If a parts list does not exist for a
work order, MRP generation uses the standard bill of material to explode demand.
You should define a bill of material type M (standard manufacturing bill) for work order headers without a
parts list and for parent planned orders. The MRP generation uses bill type M to schedule items according to
how the product is built.
Low-Level Code
The system uses the low-level code to determine parent and component relationships. The system explodes
parent demand to the components. MRP generation explodes lower-level demand only for manufactured
Page 60 of 135
items. The system does not explode demand to levels below a purchased item, even if that item has a bill of
material.
Generation Type
You must use generation types 4 and 5 to generate a master planning schedule for MRP items. If the status
of MPS is frozen, generation type 5 explodes only the component items of the master scheduled item. Select
generation type 4 to explode MPS items and component items.
Frozen Orders
If you identify work orders or purchase orders for an item as frozen, the program does not replan any orders
for the item. Instead, you receive a frozen order message for that item.
Data Selection
To run an MRP regeneration, base the selection on branch/plant, category codes, and planning code. The
system can process any selection from based-on table fields.
To run a net change generation, set the net change flag to 1 to select items that have changed since the last
generation of the program.
Setting Processing Options for MRP/MPS Requirements Planning (R3482)

From Single Site Periodic Planning Operations, select DRP Regeneration, MPS Regeneration, or MRP
Regeneration. For a net change version, select DRP Net Change, MPS Net Change, or MRP Net Change.
Horizon
These processing options control the dates and time periods that the program uses when creating the plan.
1. Generation Specify the date that the program uses to start the planning process. This date is also the
Start Date beginning of the planning horizon.
2. Past Due Specify a value. The program includes supply and demand from this number of periods
Periods prior to the generation start date. Values are:
0: 0 periods (default)
1: 1 period
2: 2 periods
3. Planning Specify the periods used in the planning horizon.
Horizon Periods
Number of Specify the number of days to be included in the plan. For example, when you view the
planning days time series, you see daily data for the number of planning days, then weekly data for the
number of planning weeks, then monthly data for the number of planning months.
Number of Specify the number of weeks to be included in the plan. For example, when you view the
planning weeks time series, you see daily data for the number of planning days, then weekly data for the
Number of Specify the number of months to be included in the plan. For example, when you view the
planning months time series, you see daily data for the number of planning days, then weekly data for the
Parameters
These processing options control processing criteria.
It is important to understand the choice of generation type:
Generation type 1 = single-level MPS/DRP. This generation type can be used either in a distribution
environment for purchased parts with no parent and component relationship or in a manufacturing
environment with parent and component relationships.
The program produces a time series for each item that is specified in the data selection with a planning code
of 1 on the Plant Manufacturing Data tab on the Additional System Information form, whether the item is
manufactured or purchased.
Page 61 of 135
For manufactured items, no demand is exploded down to the components. Use generation type 1 if you want
to process only the master scheduled end items first. Thus, you can stabilize the schedule before placing
demand on the components.
No pegging records are created.
Generation type 2 = planning bill. Use this generation type to plan for items that have a planning bill of
material. A planning bill has a pseudo parent item that is never actually manufactured; rather, it is used to
represent the average composition of a group of products.
This generation type explodes a parent forecast to its components by multiplying the parent's forecast by the
feature planned percent (from the bill of material) for each component. The program then creates a new
forecast for the components. For example, a pseudo parent item bike might have a forecast of 1,000. The
program distributes that forecast into a forecast of 100 mountain bikes, 500 touring bikes, and 400 commuter
bikes.
This information must be set up correctly to use this generation type:
• The pseudo parent item must have a planning code of 4 on the Additional System Information form,
Plant Manufacturing tab.
• The components must have a planning code of 5.
• The feature planned percents must be set up correctly in the bill of material.
• You must specify in processing options the forecast type to read from the parent, and to create for
the components.
Generation type 3 = multilevel MPS. This generation type is an alternative to generation type 1, and performs
a complete top-to-bottom processing of master scheduled items. The program explodes demand for all
parent items that you specify in the data selection down to the components. You must specify all of the items
to be processed in the data selection, not just the parent items. The program also creates pegging records.
Generation type 4 = MRP with or without MPS. This generation type has the same functionality as
generation type 3. If you have done a complete generation and stabilized the master schedule, you can limit
data selection to MRP items (with planning codes of 2 or 3), thereby reducing processing time. This action is
possible because demand from the master scheduled items is still stored in the MPS/MRP/DRP Lower Level
Requirements File table (F3412).
Generation type 5 = MRP with frozen MPS. This generation type freezes the master schedule after it has
been stabilized. Before running this generation type, you should make all of the necessary adjustments to
master scheduled items and release orders to cover the demand. This generation type freezes the entire
planning horizon similar to the way the freeze fence freezes a part of the horizon. The results of running this
generation type are:
• No new orders will be planned.
• No messages for existing orders will be created.
• The adjusted ending available quantity is allowed to go negative.
• Demand is only exploded down to components from existing work orders.
No -PWO demand from parent items exists—only -FWO demand.
1. Generation Mode Specify the generation mode. A gross regeneration includes every item in the
data selection. A net change includes only those items in the data selection that
have changed since the last time you ran the program. Values are:
1: Net change
2: Gross regeneration
2. Generation Type Specify the generation type. Please see the help for the Parameters tab for
detailed information. Values are:
1: Single-level MPS/DRP.
2: Planning bill.
3: Multi-level MPS.
4: MRP with or without MPS.
Page 62 of 135
5: MRP with frozen MPS.
3. UDC Type Specify the UDC table (system 34) that contains the list of quantity types to be
calculated and written to the F3413 table. The default value is QT.
4. Version of Specify which version of supply/demand inclusion rules the program reads.
Supply/Demand These rules define the criteria that are used to select items for processing.
Inclusion Rules
On Hand Data
These processing options control how the program calculates on-hand inventory.
1. Include Lot Specify whether the system considers lot expiration dates when calculating on-hand
Expiration Dates inventory. For example, if you have 200 items on hand with an expiration date of August
31, 2005, and you need 200 on September 1, 2005, the program does not recognize
the expired lot and creates a message to order or manufacture more of the item to
satisfy demand. Values are:
Blank: Do not consider.
1: Consider.
2. Safety Stock Specify whether to plan based on a beginning available quantity from which the safety
Decrease stock quantity has been subtracted. Values are:
Blank: Do not decrease.
1: Decrease.
3. Receipt Routing Specify whether items in transit, in inspection, or otherwise dispositioned are
Quantities considered in the beginning available calculation or they are part of the In Receipt (+IR)
bucket on the time series.
Quantity in Transit In a manufacturing environment, sometimes it is necessary to establish where stock is,
in order to determine whether it is available for immediate use. Enter 1 if you want
quantities in transit to be included in the Beginning Available calculation on the time
series. Otherwise, the program includes these quantities in the In Receipt (+IR) line of
the time series. The quantities are still considered available by this program. The
difference is only in how you view the quantities in the time series. Values are:
Blank: Do not include in on-hand inventory.
1: Include in on-hand inventory.
Quantity in In a manufacturing environment, sometimes it is necessary to establish where stock is,
Inspection in order to determine whether it is available for immediate use. Enter 1 if you want
quantities in inspection to be included in the Beginning Available calculation. Otherwise,
the program includes these quantities in the In Receipt (+IR) line of the time series. The
quantities are still considered available by this program. The difference is only in how
you view the quantities in the time series. Values are:
User Defined In a manufacturing environment, sometimes it is necessary to establish where stock is,
Quantity 1 and User in order to determine whether it is available for immediate use. Enter 1 if you want these
Defined Quantity 2 user defined quantities (defined on the Receipt Routings Revisions form in the Update
Operation 1 or Update Operation 2 fields) to be included in the Beginning Available
calculation. Otherwise, the program includes these quantities in the In Receipt (+IR) line
of the time series. The quantities are still considered available by this program. The
difference is only in how you view the quantities in the time series. Values are:
4. Lot Hold Codes Specify the lots to be included in the calculation of on-hand inventory. You can enter a
(up to 5) maximum of five lot hold codes (41/L).
Blank: Do not include held lots in calculation of on-hand inventory.
*: Include all held lots in calculation of on-hand inventory.
5. Include Past Due Specify whether the system considers open quantities from rate schedules that are past
Page 63 of 135
Rates as a supply due as a supply. If you enter a 1 in this processing option, the system includes these
quantities in the calculation of the rate schedule unadjusted (+RSU) and the rate
schedule adjusted (+RS) quantities. Values are:
1: Consider.
Forecasting
These processing options control what forecast types the program reads as demand, as well as the forecast
consumption that is used by the system.
1. Forecast Types Used (up Specify up to 5 forecast types.

to 5) Forecasts are a source of demand. You can create forecasts using 12 different
forecast types (34/DF) within the Forecasting system. One is considered the
Best Fit (BF) type compared to an item's history of demand. Use this
processing option to define which forecast quantities created by which forecast
type are included in the planning process. Enter multiple values with no spaces
—for example: 0102BF.
2. Forecast Type For Specify the forecast type (UDC 34/DF) that the system uses to create forecasts
Planning Bills/Forecast for components when you explode generation type 2 planning bills. This value
Consumption By Customer must equal that of the Forecast Types Used processing option for this feature.
When you set the Forecast Consumption Logic processing option to 2 (forecast
consumption by customer), this processing option specifies the forecast type
(34/DF) that is used to create a forecast for the actual daily demand by the
customer. This value cannot equal the value for the Forecast Types Used
processing option.
3. Forecast Consumption Specify whether to use forecast consumption logic during the requirements
Logic planning processing. Values are:
Blank: Do not use forecast consumption.
1: Use forecast consumption. This value invokes forecast consumption logic
applied to aggregate sales order and forecast quantities within the forecast
consumption period for selected items with a planning fence rule equal to H.
2: Use forecast consumption by customer. This value invokes forecast
consumption logic applied to sales order and forecast quantities for individual
customers. Use this value in conjunction with the Forecast Type for Planning
Bills / Forecast Consumption by Customer processing option.
4. Default Customer Specify which address book number on the sales order the system uses for
Address Relationship for calculation when you use forecast consumption by customer logic. Values are:
Forecast Consumption by 1: Ship to address book number.
Customer
2: Sold to address book number.
Document Types
These processing options establish default document types.
1. Purchase Specify the document type used when the system suggests creating purchase orders.
Orders When you receive messages related to purchase order creation, this document type appears
as the default. The default value is OP.
2. Work Specify the document type used when the system suggests creating work orders.
Orders When you receive messages related to work order creation, this document type appears as
the default. The default value is WO.
3. Rate Specify the document type used when the system suggests creating rate schedules.
Schedules When you receive messages that relate to rate schedule creation, this document type
appears as the default. Enter the UDC 00/DT of the document type for the rate schedule that
you want to use. The default value is SC.
Lead Times
Page 64 of 135
Use safety lead times to allow extra time for delays in receipt or production. Use damper days to filter out
unwanted messages.
1. Purchased Item Specify a value to be used in the lead time calculation.

Safety Lead Time For items with stocking type P, the program adds the value that you enter here to the
item's level lead time to calculate the total lead time.
2. Manufactured Item Specify a value to be used in the lead time calculation.
Safety Lead Time For items with stocking type M, the program adds the value that you enter here to the
3. Expedite Damper Specify the number of days before the system generates an Expedite message. If the
Days number of days between the date when the order is actually needed and the due date
of the order is less than the number of days entered here, the system does not
generate an Expedite message.
4. Defer Damper Specify the number of days before the system generates a Defer message. If the
generate a Defer message.
Performance
These processing options define output, and increase or decrease processing time.
1. Clear F3411/F3412/F3413 Warning! Use this processing option with extreme caution!
Tables
If you enter 1, the system purges records in the F3411, F3412, and
MPS/MRP/DRP Summary File (F3413) tables.
Access to this program should be limited. If multiple users run this program
concurrently with this processing option set to 1, a record lock error results
and prevents complete processing. Values are:
Blank: Do not clear tables.
1: Clear tables.
2. Input B/P Where Planning Specify which branch/plant records in the F3411, F3412, and F3413 tables
Tables Will Be Cleared are purged.
Note. This option is only valid when the Clear F3411/F3412/F3413 Tables
processing option on the Performance tab is set to 1 and the Delete
Branch/Plant processing option has a valid branch/plant.
This processing option enables a preprocess purge of these tables. If this

processing option is not enabled or set to Blank, the system purges records
for a given branch/plant and item as you plan the item. Depending on
processing option combinations, these scenarios can occur:
Example 1:
Clear F3411/F3412/F3413 Tables is set to 1.
(a) Delete Branch/Plant is set to Blank.
All records from the three tables will be prepurged.
(b) Delete Branch/Plant contains a valid branch/plant number.
Records for all the items that belong to the valid branch/plant will be
prepurged from the three tables.
(c) Delete Branch/Plant contains an invalid branch/plant number.
No records will be prepurged from the three tables.
Page 65 of 135
Example 2:
Clear F3411/F3412/F3413 Tables is set to Blank
Delete Branch/Plant is not active.
No records from any of the three tables will be prepurged.
3. Initialize MPS/MRP Print Specify a value to initialize records in the F4102 table.
Code. If you enter 1 in this processing option, the program initializes every record in
the F4102 table by setting the Item Display Code (MRPD) to Blank.
If you leave this field blank, processing time is decreased. The system does
not clear the records in the F4102 table.
Regardless of how you set this processing option for each item in the data
selection, the MRPD field is updated as follows:
• 1 if messages were not created.
• 2 if messages were created.
The Print Master Production Schedule program (R3450) enables you to enter
data selection based on the MRPD field. Values are:
Blank: Do not initialize.
1: Initialize.
4. Messages And Time Series Specify whether the program generates messages and time series for
For Phantom Items phantom items. Values are:
Blank: Do not generate.
1: Generate.
5. Ending Firm Order Status Specify the work order status at which messages are no longer exploded to
components. If you leave this processing option blank, all messages are
exploded to components.
6. Extend Rate Based Specify whether adjustments for rate based items are exploded to
Adjustments components, thereby creating messages for the components. Values are:
Blank: Do not extend.
1: Extend.
7. Closed Rate Status Enter the status of closed rates. When planning for a rate based item, the
program does not consider rate orders at this status or higher.
8. Set Key Definition For Specify to run multiple MRP/MPS jobs concurrently. The value that you enter
Table F3411 and 9. Set Key specifies the range for the number of records in the F3411 and F3412 tables
Definition For Table F3412 for a given run. This value must be large enough to include the number of
records that will be generated for the table. For example, if you enter a value
of 8 for the first run and 10 for the second run, the range of records that the
system reserves for two simultaneous MRP/MPS runs would be as follows:
First run:
The system reserves records in the range of [1] to [1 × 10^8], or 1 through
100,000,000.
Second run:
The system reserves records in the range of [1 × 10^8 + 1] to [2 × 10^10], or
100,000,001 through 20,000,000,000.
Note. The values that you enter are the exponents in the previous
calculations. Enter a value from 7 to 14. If you do not enter a value, the
system uses 10.
This processing option is applicable only when a subsequent MRP/MPS job
is submitted while an existing job is currently running. The number of records
that the MRP/MPS Requirements Planning program and Master Planning
Schedule - Multiple Plant program (R3483) generate is based on the values
that you enter in this processing option. You determine the optimum number
Page 66 of 135
of records that the system includes. All values should be the same for all
versions. If version settings differ, the system might generate unpredictable
results.
10. Suppress Time Series Specify whether the MRP/MPS Requirements Planning program generates
the time series. Values are:
Blank: Generate.
1: Do not generate.
Note. Performance improves if the system does not generate the time series.
11. Planning Control UDC Specify the UDC table in system 34 that contains the list of planning control
Type flags. The default value is PC.
Mfg Mode
These processing options define whether the system generates plans for process items, projects, and
configurator items.
1. Process Specify plan generation for process items.

Planning If you use process manufacturing, enter 1 to generate the plan based on the forecasts of
the co-products and by-products for the process. The program then creates messages
for the process. Values are:
Blank: Run Discrete planning.
1: Run Process planning.
2. Project Specify whether the system includes supply and demand from items that are associated
Planning with a project. Project-specific items have a stocking type of G or H. Values are:
Blank: Do not include.
1: Include.
3. Configurator Specify whether the system processes configurator components from the Configurator
Components Component table (F3215) and adds them to the Sales Order Detail File table (F4211)
Table and Work Order Parts List table (F3111). If you enter a 1 in this processing option, the
system processes the items on the F3215 table as demand items.
Blank: Do not process.
1: Process.
Parallel
These processing options specify the number of processors that the system uses during parallel processing.
These options also specify whether the system runs preprocessing during parallel processing.
1. Number of Specify the number of subsystems in a server.

Subsystem The default is 0 (zero).
Jobs
2. Pre Specify whether the system runs preprocessing during parallel processing. During
Processing preprocessing, the system checks supply and demand and plans only the items within
supply and demand. Preprocessing improves performance when you run MRP and is valid
only when the number of items actually planned is less than the total number of items in the
data selection. Values are:
Blank: Do not run preprocessing.
1: Run preprocessing.
(Rapid Start) Planning Requirements for an Inventory Item

The interactive program may be used if you want to review messages before processing. The batch program
might be used to process all messages starting before a particular date. This section discusses:
• How to plan requirements for an inventory item.
Page 67 of 135
• Preconfigured processing options for Rapid Start Review Planning Family (P3401).
Planning Requirements for an Inventory Item

This table lists the tasks for planning requirements for an inventory item:
Task Navigation Program Preconfigured Data Data to Configure

and Onsite
Version
Plan Maintenance P3401/RIS0 • Document Type: • Branch/plant B10

requiremen of 002 OP is set up in the
ts for an Procurement • Line Type: S = preconfigured
inventory Process, MRP Stock Item data. Some setup
item. Planning will need to be
• Order Activity
Family changed if other
Rues: Order
Review branches are
activity rules
are provided for used.
the combination • Enter item
of document numbers in the
type OP and line system as part of
types S and T. defining
• Item: item inventory.
Sample3, • Enter supplier
Sample4 can be numbers in the
used for this system.
process.
Last Status = 216
Data reports provide additional information about data that has been preconfigured for Rapid Start.
See (AUS and NZL) Rapid Start Data Reports.
See (CAN and USA) Rapid Start Data Reports.
See (FRA) Rapid Start Data Reports.
See (GBR) Rapid Start Data Reports.
Preconfigured Processing Options for Rapid Start Review Planning Family

(P3401)
These processing options show the values that are preconfigured for version RIS0002.
Versions 1
Processing Option Description Value or Status
Enter the Versions for the following programs.
1. Manufacturing Work Bench Version RIS0001
2. Message Detail Version RIS0002
3. Item Availability Version RIS0001
4. Time Series Version RIS0002
5. Forecast Maintenance Version RIS0002
Page 68 of 135
6. Supplier Schedule Version RIS0001
Versions 2
Enter the Versions for the following programs.
1. Supplier Master Version RIS0001
2. Item Branch (P41026) RIS0001
Defaults
Enter MPS Type or ' ' for all.
1. Planning Code blank
Taxes
Processing Option Description Value or

Status
Enter '1' to default Tax area from Ship to Address. If Blanks, Tax area will be
from Supplier address number.
1. Tax Area flag blank
Analyzing Planning Output

This section provides an overview of planning output, list the prerequisite, and discusses how to:
• Set processing options for MPS Time Series (P3413).
• Review the time series.
• Review messages for a planning family.
• Set processing options for MRP/MPS Detail Message Revisions (P3411).
• Review detail messages.
• Set processing options for Pegging Inquiry (P3412).
• Review pegging demand.
Understanding Planning Output

When generating a planning schedule, the planning system evaluates selected supply and demand
information, performs calculations, and recommends a time-phased planning schedule for selected items.
Planners are presented with action and warning messages that suggest new orders or the rescheduling of
existing orders. Other planning tools include supply and demand inquiry and pegging records.
Page 69 of 135
MPS/DRP Time Series
The time series is a record of time-phased supply and demand netting for selected items. The system
retrieves this data from the most recent generation or net change that has been run.
Use the DRP or MPS versions of the MPS Time Series program to review the master schedule and decide
whether to accept the planning that the system suggests or to override it. You should review the action
messages for individual item numbers to determine what action, if any, to take.
Use processing options in the MRP/MPS Requirements Planning program to set up daily, weekly, or monthly
time periods.
The DRP and MPS time series contain data such as:
Data Explanation
Quantities for You can review:

specific time • Time-phased inventory activity in any unit of measure.
periods • Available-to-promise quantities in any valid unit of measure.
• Time fences and the lead time at the item level.
• Cumulative and manufacturing lead time occurrences.
Adjusted or Period quantities are either adjusted or unadjusted.

unadjusted The calculations for adjusted quantities assume that the user will process the
period messages.
quantities The calculations for unadjusted quantities assume that the user will not
process the action messages. The U at the end of a quantity type indicates
that period quantities are unadjusted.
Forecast When you use planning time fence rule G, C, or H, which calculate demand
consumption based on the greater of forecast or customer orders, the forecast is
consumed. Consumed means that the forecast is reduced by the amount of
the customer demand in the same or related period.
Note. The time series displays the aggregate demand and forecast for all
customers. If you are using forecast consumption by customer functionality,
the aggregate forecast and customer demand quantities might appear out of
balance from standard forecast consumption.
Various display You can display the time series in different formats. For example, you can:
formats • Summarize all demand lines into one demand line.
• Summarize all supply lines into one supply line.
• Select rows of information to select or suppress.
• Toggle between two different quantity type tables as set up in the
processing options.
Access to other You can access other programs while reviewing the time series:
programs • Supply/Demand Inquiry and Pegging Inquiry to determine where higher
level demands are being generated.
• MRP/MPS Detail Message Revisions to review message detail and take
any appropriate actions.
• Additional System Info to verify item setup details.
• Detail Forecast Revisions to review item forecasts and sales history.
• Rate Schedule Revisions to review item rate schedules.
• MPS or DRP generation to run an online regeneration for the displayed
item.
MRP Time Series
Page 70 of 135
The Time Series - MRP inquiry is the same program as that used to inquire on the DRP/MPS time series.
Use the appropriate version of the MPS Time Series program to review the item series for the material
requirements plan. You can vary the settings in the processing options to accommodate the different
requirements for MRP.
Use the MPS/MRP/DRP Key Window program (P34KEY) to review the quantity types that are generated for
the material requirements plan. These quantity types include:
Quantity Explanation
Type
Planned order Represents recommended replenishment orders for an item.

(+PLO)
Planned work Represents demand for components that are required from the parent's
order (-PWO) planned work order (+PLO).
Work order Represents a supply manufacturing order for the component that has a work
(+WOU) order header. The -WOU is the work order as it is in the Work Order Master File
(+WO/WOU) table (F4801). +WO is the work order if you processed all of the applicable
action messages.
Firm work Represents demand for components that will be consumed from the parent's
order (-FWO) released work order (+WOU).
Time Fence Display Codes

Item lead time and time fence days are displayed on the time series. Time fences and lead times are noted
in their respective time periods as follows:
Code Description
L Level lead time
M Manufacturing lead time
C Cumulative lead time
F Freeze fence
P Planning fence
D Message Display fence
Planning Family Messages

You can manually review and process messages using the MRP/MPS Detail Message Revisions program or
automatically process the messages using the MRP/MPS Detail Message Processing program (R3411).
The action messages for DRP, MPS, and MRP are defined in UDC table 34/MT. The character codes are
hard-coded. Do not change the character codes in this list.
Each time that you generate a material requirements plan, the system generates action messages to identify
situations in which demand requires:
• Changing the existing supply orders.
• Placing new orders.
Page 71 of 135
Use the Message Detail - MRP version of the MRP/MPS Detail Message Revisions program to review
exception messages from the latest planning generation. These messages might help you evaluate planned
and existing orders. You can review the most critical messages first and review other messages in the order
that you process them.
Note. For Demand Flow® Manufacturing (DFM) items only, set the Suppress MRP Messages option in the
Item Branch program (P41026) to suppress the display and processing of MRP messages. The Suppress
MRP Messages option is used in DFM where assemblies and sub-assemblies are inclusive of the line design
daily planning, but messages are still needed to drive lower-level demand. If you set the option to suppress
MRP message processing, you will not see or be able to process MRP messages for DFM items.
Detail Messages
Detail messages include all of the messages from the Message Summary program (P3401). After you
generate master schedule output, you review the action messages for the individual item numbers. After you
review each message, you can perform one of these actions:
• Place the message on hold.
• Clear the message.
• Delete the message.
You can delete any message that you have reviewed but did not process.
• Process the message.
Work Order Output from DRP/MPS/MRP

This table describes how the system uses document types, quantity types, and work order codes during the
MRP generation process:
Document Other Description Component Demand

Type (Time Codes
Series)
WP (+PLO) Status = P Planned orders. WP is a system-generated -PWO

(planned) document type for orders without a header
in the F4801 table. DRP/MPS/MRP
automatically changes schedule dates and
quantities each time that you run the
program.
WO (+WO Status = Firm orders. A work order header is in the -FWO/-FWOU. Message
does not 10 (firm) F4801 table. DRP/MPS/MRP creates type A warns about
always equal messages that require planner action to parent supply/demand
+WOU in balance supply and demand. For imbalances. -FWO
schedule component demand, the system assumes does not always equal
dates or that the planner will take action. -FWOU in schedule
quantities) dates or quantities.
WO (+WO Status = Firm orders that have parts lists and -FWO/-FWOU. Message
does not 40 (firm) routing instructions attached. type A warns about
always equal DRP/MPS/MRP creates messages that parent supply/demand
+WOU in require planner action to balance supply imbalances. -FWO
schedule and demand. For component demand, the does not always equal
dates or system assumes that the planner will take -FWOU in schedule
quantities) action. dates or quantities.
WO (+WO Status = Firm orders with firm plans. These are -FWO/-FWOU. Message
does not 41 (firm orders that have been planned by a type S warns about
always equal planned generation of DRP/MPS/MRP, specifying supply/demand
Page 72 of 135
Document Other Description Component Demand
Type (Time Codes
Series)
+WOU in order) status 41 in the Ending Work Order Status imbalances for FPO
schedule processing option. DRP/MPS/MRP creates parent. -FWO always
dates or messages that require planner action to equals -FWOU in
quantities) balance supply and demand. For schedule dates or
component demand, the system assumes quantities.
that the planner will not take action. The
messages have FPO planner remarks.
WO (+WO Inside All firm orders inside freeze fence. -FWO/-FWOU. The
equals freeze DRP/MPS/MRP does not display action program does not
+WOU in fence (any messages inside the freeze fence. The create change
schedule status program creates message type A warnings messages from the
dates or code) to indicate a supply and demand parent demand.
quantities) imbalance inside the freeze fence. The
program generates an action message
outside the freeze fence to correct the
supply/demand imbalance.
WO (+WO Freeze Frozen firm orders. DRP/MPS/MRP does not -FWO/-FWOU. The
equals code on create action messages for these work program does not
+WOU in work orders. The program creates message type create change
schedule order A and F warnings. The program creates messages from the
dates or header messages for new orders to satisfy parent demand.
quantities) (any supply/demand imbalances.
status
code)
MRP Pegging Demand

Use Pegging Inquiry (P3412) to determine, or peg, the source of demand for dependent requirements.
Pegging Inquiry displays only those parents that contain planned or open orders. Pegging Inquiry enables
you to:
• Display the parent work orders that require a particular item.
• Trace the source of demand for each item.
• Display the different levels in a bill of material so that you can peg demand from the beginning level
through the parent item.
You can trace the path of dependent requirements up through parent items to the final assembled item and
even to the sales order or forecast. You can use this information to determine if you need to reschedule or
change orders.
Prerequisite
Generate a current material requirements plan that includes the start and end dates for the planning periods
that you want to review.
Forms Used to Analyze Planning Output

D
Work With W341 DRP Daily Operations Review time-phased supply and
Time Series 3A (G3411), DRP Time demand quantities.
Page 73 of 135
D
Series/ATP Inquiry
MPS Daily Operations
(G3412), MPS Time
Series/ATP Inquiry
(G3413), MRP Time
Series/ATP Inquiry
Work with W340 DRP Daily Operations Review summarized message records
Message 1D (G3411), DRP Planning by planning family.
Summary Family Review
(G3412), MPS Planning
Family Review
(G3413), MRP Planning
Family Review
Work With W341 DRP Daily Operations Review detail messages generated by
Detail 1D (G3411), DRP Detail the Requirements Planning
Messages Message Review Regeneration program.
(G3412), MPS Detail
Message Review
(G3413), MRP Detail
Message Review
Work With W341 MRP Daily Operations Review the sources of dependent
Pegging 2A (G3413), Pegging Inquiry demand.
Inquiry
Setting Processing Options for MPS Time Series (P3413)

Use these processing options to set default value, define how the system processes data, and specify
versions.
Defaults
These processing options enable you to specify the required and alternate UDC types for the time series row
descriptions in the MPS Time Series program.
1. UDC Type Specify the UDC code in system 34 for the list of row descriptions that appear on the time
(Required) series. If you leave this option blank, the system uses the quantity type code (QT).
2. Alternate UDC Specify the UDC code in system 34 for the list of alternate row descriptions that appear on
Type (Optional) forms that are associated with the Time Series program. Select the Alternate Quantity Type
option to display the alternate row descriptions. If you do not select an option, the system
does not display the alternate row descriptions.
Process
These processing options identify what information appears on the Time Series form and how the
information appears. You can select specific past due and forecast consumption periods. Additionally, you
can select to summarize supply and demand data into a single row.
1. Past Due Periods Specify the number of periods that the system displays prior to the MRP
Page 74 of 135
generation start date on the time series. Values are:
0: Zero periods (default) prior to the MRP generation start date.
1: One period prior to the MRP generation start date.
2: Two periods prior to the MRP generation start date.
This value should correspond to the MRP Generation (R3482/R3483) past due
periods. If the MRP Generation program has one past due period, this option
should be set to 1.
2. Summarize Supply Specify whether to summarize supply lines into a single row and demand lines into
and Demand another single row on forms that are associated with the Time Series program.
Values are:
Blank: Do not summarize.
1: Summarize.
3. Forecast Specify whether the system indicates the forecast consumption periods in the
Consumption Periods Time Series program when MRP uses forecast consumption. Values are:
(FCP) Blank: Do not indicate.
1: Indicate the forecast consumptions periods by placing an asterisk next to the
date.
Versions
These processing options enable you to specify versions of reports and programs such as MRP/MPS
Requirements Planning and MRP/MPS Detail Message Revisions that you access through the Row and
Form menus from the MPS Time Series program.
1. Single Item MRP Specify the version of the Single Item MRP program (R3482) that the system uses
(R3482) when you access it from the Form menu on the Work With Time Series form. If you
leave this option blank, the system uses the ZJDE0001 version.
2. MRP Detail Specify the version of the MRP Detail Message Review program (P3411) that the
Message Review system uses when you access it from the Row menu on the Work With Time Series
(P3411) form. If you leave this option blank, the system uses the ZJDE0001 version.
3. Supply and Specify the version of the Supply and Demand Inquiry program (P4021) that the system
Demand Inquiry uses when you access it from the Form menu on the Work With Time Series form. If
(P4021) you leave this option blank, the system uses the ZJDE0001 version.
4. Forecast Specify the version of the Forecast Revisions program (P3460) that the system uses
Revisions (P3460) when you access it from the Form menu on the Work With Time Series form. If you
5. Pegging Inquiry Specify the version of the Pegging Inquiry program (P3412) that the system uses when
(P3412) you access it from the Form menu on the Work With Time Series form. If you leave this
option blank, the system uses the ZJDE0001 version.
6. Rate Schedule Specify the version of the Rate Schedule Revisions program (P3109) that the system
Revisions (P3109) uses when you access it from the Form menu on the Work With Time Series form. If
you leave this option blank, the system uses the ZJDE0001 version.
7. Work Day Specify the version of the Work Day Calendar program (P00071) that the system uses
Calendar (P00071) when you access it from the Form menu on the Work With Time Series form. If you
8. Item Branch Specify the version of the Item Branch program (P41026) that the system uses when
(P41026) you access it from the Form menu on the Work With Time Series form. If you leave this
option blank, the system uses the ZJDE0001 version.
Reviewing the Time Series

Access the Work With Time Series form.
Work With Time Series form
Page 75 of 135
Suppress Blank Lines Select this check box to suppress blank lines so they are not displayed on the
screen.
Summarize Select this check box to displays records in summarized form. Clear the check box
Supply/Demand to displays records in detail form.
Alternate Quantity Select this check box to toggle between the alternate quantity types specified in the
Type processing options of the Time Series program.
Item Number Enter the item for which you want to review the time series.
Reviewing Messages for a Planning Family

Access the Work with Message Summary form.
Work with Message Summary form
Planning Enter a UDC (41/P4) that represents an item property type or classification, such as commodity
Family type or planning family. The system uses this code to sort and process like items.
See Also
Processing Purchase Order Messages
Setting Processing Options for MRP/MPS Detail Message Revisions (P3411)

PO Info
Use these processing options to define purchase order information.
1. Line Type Specify how the system processes lines on a transaction. The line type affects the systems
with which the transaction interfaces (General Ledger, Job Cost, Accounts Payable, Accounts
Receivable, and Inventory Management). The line type also specifies the conditions for
including a line on reports and in calculations. Some examples of values, which have been
defined on the Line Type Constants Revisions form (P40205), are:
S: Stock item.
J: Job cost, subcontracts, or purchasing to the General Ledger.
B: GL account and item number.
N: Non-stock item.
F: Freight.
T: Text information.
M: Miscellaneous charges and credits.
W: Work order.
2. Beginning Specify the beginning status, which is the first step in the order process. You must specify a
Status UDC (40/AT) that has been set up on the Order Activity Rules form for the order type and the
line type that you are using.
3. Specify whether you want to consolidate all processed messages that apply to one supplier
Consolidate on one purchase order. Values are:
1: Consolidate.
Blank: Do not consolidate.
4. Price Specify whether the system retrieves the price from a blanket order or the Procurement Price
Control Management system. Values are:
Blank: Retrieve the price from the blanket order.
1: Retrieve the price from the Procurement Price Management system.
WO Info
Page 76 of 135
Use these processing options to define work order information.
1. Beginning Status Specify the UDC (00/SS) that identifies the default status of the work order to use
when a work order is created.
2. Cancelled Orders Specify the default user defined status code (00/SS) for a canceled work order.
Status
OT Info
Use this processing option to define transfer order information.
1. Specify whether you want to consolidate all processed messages that apply to one
Consolidate branch/plant on one transfer order. Values are:
1: Consolidate.
Blanket Info
Use this processing option to define blanket order information.
1. Blanket Order Specify whether you want the program to perform an interactive release against a
Document Type to matching blanket order when processing messages to create purchase orders. Enter a
Release document type (UDC 00/DT) to release against. If you leave this processing option
blank, the program does not release against a blanket order.
Versions
Use these processing options to define what version to use when this program accesses another program.
When you select a version, review the version's processing options to ensure that the version meets the
requirements.
1. Blanket Order Specify a version of the Blanket Order Release program. The system calls this
Release (P43216) version when you access Blanket Order Release from this program.
2. Time Series (P3413) Specify a version of the Time Series program.
The system calls this version when you access Work with Time Series from the Form
menu of the Work with Detail Messages or Detail Message Revisions form.
3. Pegging Inquiry Specify a version of the Pegging Inquiry program. The system calls this version when
(P3412) you access Work with Pegging Inquiry from the Form menu of the Work with Detail
Messages or Detail Message Revisions form.
4. Supply/Demand Specify a version of the Supply and Demand Inquiry program. The system calls this
Inquiry (P4021) version when you access Work with Supply and Demand from the Form menu of the
Work with Detail Messages or Detail Message Revisions form.
5. Purchase Order Specify a version of the Purchase Orders program. The system calls this version
Entry (P4310) when you access Work with Order Details from the Row menu of the Work with
Detail Messages or Detail Message Revisions form.
6. Work Order Entry Specify a version of the Work Order Processing program. The system calls this
(P48013) version when you access Work Order Processing from this program.
7. Rate Schedule Specify a version of the Enter/Change Rate Schedule program. The system calls this
Revisions (P3109) version when you access Work with Rate Schedules from the Form menu of the
Work with Detail Messages or Detail Message Revisions form.
8. Transfer Order Specify a version of the Sales Order Entry program. The system calls this version
Entry (P4210) when you access Sales Order Entry from this program.
9. Scheduling Specify a version of the Manufacturing Scheduling Workbench program. The system
Workbench (P31225) calls this version when you access Work with Work Order Scheduling from the Form
menu of the Work with Detail Messages or Detail Message Revisions form.
10. Bill of Material Specify a version of the Bill of Material Inquiry program. The system calls this version
Inquiry (P30200) when you access Bill of Material Inquiry from the Row menu of the Work with Detail
Page 77 of 135
Messages or Detail Message Revisions form.
11. Item Branch Specify a version of the Item Branch program.
(P41026) The system calls this version when you access Plant Manufacturing Data from the
Row menu of the Work with Detail Messages or Detail Message Revisions form.
Display
Use this processing option to specify whether to view messages for demand branch/plant or supply
branch/plant.
1. Viewing Messages Specify whether to view messages for demand branch/plant or supply branch/plant.
For Values are:
Blank or D: Demand branch/plant.
1 or S: Supply branch/plant.
Reviewing Detail Messages

Access the Work With Detail Messages form.
Work With Detail Messages form
Setting Processing Options for Pegging Inquiry (P3412)

Versions
Enter the version for each program. If you leave a processing option blank, the system uses version
ZJDE0001.
1. Message File Specify a group of items that can be processed together such as reports, business units,
Revisions or subledgers.
2. Time Series Specify a sequence number that identifies versions of a menu selection. For example,
where multiple versions of a report menu selection are set up, this sequence number
identifies each of those versions.
3. Supply and Specify multiple versions of certain menu selections (for example, reports). This
Demand Inquiry sequence number identifies each of those versions.
4. Item Branch Specify a specific set of data selection and sequencing settings for the application.
(P41026B) Versions may be named using any combination of alpha and numeric characters.
Reviewing Pegging Demand

Access the Work With Pegging Inquiry form.
Work With Pegging Inquiry form
Requested Date Enter the date that an item is scheduled to arrive or that an action is scheduled for
completion.
Processing Planning Output

This section provides an overview of planning output processing and discusses how to:
• Process purchase order messages.
• Set processing options for MRP/MPS Detail Message Process (R3411).
• Add a freeze code to a work order.
Page 78 of 135
• Add a freeze code to a purchase order.
• Analyze supply and demand.
Understanding Planning Output Processing

After you have analyzed the planning output, you process the messages into orders to meet the demand.
You can place messages on hold so that the system does not change the message during the next
generation (for example, to preserve a manual reminder). The system retains held messages until you
manually clear or delete them.
You can clear a message from the MRP/MPS Detail Message Revisions form if you decide not to process it.
Work Order Messages

When you process work order messages, the system creates work order headers in the F4801 table and
assigns work order numbers. The system does not attach a parts list or routing information at this time.
You can process work order messages by using any of these methods:
• Process a single action message for an item.
• Process multiple action messages for an item.
• Process messages using a planning family.
• Process messages automatically.
The system first processes work order messages. Work order messages appear on the MRP/MPS Detail
Message Revisions form with an order type of WO. The master schedule remains firm or does not change
from the beginning date through the end date when the system processes these work order messages.
These firm orders are not automatically replanned in subsequent MPS generations. However, if the
subsequent MPS generation finds a mismatch between the supply quantities or dates and the demand
quantities or dates, the program recommends realignment of the existing work orders.
When you use fixed order quantity (FOQ), MPS/DRP does not generate an Increase message for an existing
order to cover demand. Instead, the system generates Order messages in multiples of FOQ as needed to
cover the demand.
When you create or update an order, you can modify the status of the order to indicate the stage of
production. To do so, enter a new status in the Status field. The system displays this field only for messages
that are related to order processing.
Purchase Order Messages

Purchase order messages appear on the MRP/MPS Detail Message Revisions form with an order type of
OP. You can process a purchase order message by using any of these methods:
• Process a single action message without blanket order checking or consolidation.
• Process one or more action messages with blanket order checking.
• Process messages using purchase order consolidation to include more than one item on a purchase
order.
• Process purchase order messages by using a planning family.
• Process messages using the Supplier Scheduling system.
Note. If an item does not have a supplier assigned to it, the system displays an error message. Enter
a supplier number and click OK.
To expedite message processing, it is recommended that you set up a different version of MRP/MPS Detail
Message Revisions for each of the previous methods. That is, set up one version to process a single action
message without blanket order checking or consolidation, another version to process one or more action
messages with blanket order checking, and so on.
Page 79 of 135
Depending on how you set the processing option for the MRP/MPS Requirements Planning program, the
program creates either a purchase requisition (document type OR) or a purchase order (document type OP).
The program includes a user ID on the purchase order and uses the system date as the date on which the
purchase order was created.
In addition, the program creates the purchase order in the purchasing unit of measure, even though the
action message displays the primary unit of measure. The program makes the appropriate unit of measure
conversions. After the next DRP/MPS regeneration, the quantities that are associated with processed
messages appear in the time series display on the +PO Quantity Type row.
When you process messages, the system firms that portion of the DRP/MPS replenishment plan.
Subsequent DRP/MPS regeneration does not change the timing or quantities that are associated with
previously processed messages. However, if the new regeneration finds a mismatch between the supply and
demand quantities or dates, the program issues a message recommending that you realign the existing
+POs.
Purchase Order Consolidation

The system creates one purchase order header with as many detail line items for messages as necessary.
Dates correspond to the messages. If a part has more than one supplier, you can change the supplier
number in the message detail area. The system produces a purchase order for each supplier.
Automatic Message Processing

As an alternative to processing messages interactively, you can run MRP/MPS Detail Message Processing
(R3411). The program processes these types of messages for work orders, purchase orders, and transfer
orders:
• B: Order and expedite.
• C: Cancel.
• D: Defer.
• E: Expedite.
• G: Increase order quantity to.
• L: Decrease order quantity to.
• O: Order.
The program does not produce a report. Review error messages in the Work Center (P012501) in the
Submitted Jobs queue. View any message that the program did not process on the Work with Detail
Messages form.
Freeze Codes
You can freeze the time and quantity values in a purchase order so that DRP and MPS do not generate any
action messages to change the order. You freeze purchase orders before negotiations are final or when a
purchasing contract has been signed with a supplier.
You can freeze the time and quantity values in a work order so that DRP and MPS do not generate any
action messages to change the order. You freeze work orders when the order is within the freeze time fence.
See Also
Setting Processing Options for Net Change Review (P3402)
Understanding MRP Supply and Demand

Use the Supply and Demand Inquiry program to review the current demand for a selected item. Supply and
Demand Inquiry enables you to:
• Display the current inventory position, including all scheduled supply and demand.
• Review item quantity supply, demand, and order availability in date order.
Page 80 of 135
Planning Fence Rule Impact on Supply and Demand Inquiry
The supply and demand inquiry view of the Supply and Demand Inquiry program uses the identified planning
fence rule for an item when calculating real-time net requirement values. The supply and demand inquiry
view respects the designated planning fence rule when identifying which demand elements are considered
during real-time netting calculations for an item.
Note. Supply and demand inquiry reflects all of the planning fence rules with the exception of the Forecast
Consumption rule (rule H). Forecast Consumption logic is displayed using the time series view only.
Available-to-promise calculations can be displayed on the demand inquiry view by setting the appropriate
processing option for the Supply and Demand Inquiry program.
See Also
Entering Branch/Plant Manufacturing Information
Forms Used to Process Planning Output

Name D
Work With W3411 DRP Daily Operations (G3411), DRP Detail Process work order and
Detail D Message Review purchase order messages
Messages MPS Daily Operations (G3412), MPS Detail individually by selecting
Message Review Process Message(s) from
MRP Daily Operations (G3413), MRP Detail the Row menu.
Message Review Clear messages by selecting
On the Work with Message Summary form, Clear Message from the
select Message Detail from the Row menu. Row menu.
Detail W3411 On the Work With Detail Messages form, Place messages on hold.
Message B select a row, and select Message Revision
Revisions from the Row menu. On the Detail
Message Revisions form, select
Hold/Release from the Row menu.
Suppliers W4303 On the Work with Detail Messages form, Generate purchase orders.
Selected 2A select Process Message(s) from the Row
for Order menu. Click Close on the Work With Detail
Messages form.
Work Order W4801 Daily Order Preparation - Discrete Enter a freeze code for a
Details 3A (G3111), Enter/Change Order work order.
Select a work order, and click Select.
On the Work Order Details form, select the
Status & Type tab.
Order W4310 Purchase Order Processing (G43A11), Enter a freeze code for a
Detail - E Enter Purchase Orders purchase order.
Page II On the Work With Order Headers form,
select a purchase order.
Select Detail Revision from the Row menu.
On the Order Detail form, select a row,
and then select Additional Info 2 from the
Row menu.
Page 81 of 135
Name D
Work With W4021 MRP Daily Operations (G3413), Review supply and demand
Supply and B Supply/Demand Inquiry changes that result from
Demand orders.
Processing Purchase Order Messages

Access the Suppliers Selected for Order form.
To generate purchase orders, select the Generate Order options from the Form menu.
Suppliers Selected for Order form
Setting Processing Options for MRP/MPS Detail Message Processing (R3411)

From DRP Daily Operations (G3411), select DRP Detail Message Processing.
From MPS Daily Operations (G3412), select MPS Detail Message Processing.
From MRP Daily Operations (G3413), select MRP Detail Message Processing.
PO Info
Use these processing options to specify processing specific to purchase orders.
1. Enter the Line Type Specify how the system processes lines on a transaction. The line type affects
the systems with which the transaction interfaces (General Ledger, Job Cost,
Accounts Payable, Accounts Receivable, and Inventory Management). The line
type also specifies the conditions for including a line on reports and in
calculations.
Some examples of values, which have been defined on the Line Type Constants
Revisions form (P40205), are:
S: Stock item.
J: Job cost, subcontracts, or purchasing to the General Ledger.
B: GL account and item number.
N: Non-stock item.
F: Freight.
T: Text information.
M: Miscellaneous charges and credits.
W: Work Order.
2. Enter the Beginning Specify the beginning status, which is the first step in the order process. You
Status must specify a UDC (40/AT) that has been set up on the Order Activity Rules
form for the order type and the line type that you are using.
3. Enter '1' to Consolidate Specify whether you want to consolidate all processed messages that apply to
all messages onto one one supplier on one purchase order. Values are:
purchase order by 1: Consolidate.
supplier
4. Price Control Specify whether the system retrieves the price from a blanket order or the
Procurement Price Management system. Values are:
Blank: Retrieve the price from the blanket order.
1: Retrieve the price from the Procurement Price Management system.
WO Info
Use these processing options to specify processing specific to work orders.
Page 82 of 135
1. Enter the Beginning Status. Specify the UDC (00/SS) that identifies the default status of the work order
to use when a work order is created.
2. Enter the Status for Specify the default UDC status code (00/SS) for a canceled work order.
Cancelled Orders.
OT Info
Use this processing option to specify processing specific to transfer orders.
1. Enter '1' to Consolidate Specify whether you want to consolidate all processed messages that
Transfer Order messages. apply to one branch/plant on one transfer order. Values are:
1: Consolidate.
Blanket Info
Use these processing options to specify processing specific to blanket orders.
1. Enter Document Type Specify whether you want the program to perform an interactive release
associated with Blanket against a matching blanket order when processing messages to create
Orders. Blanks will not check purchase orders. Enter a document type to release against. If you leave
for open blanket orders. this processing option blank, the program does not release against a
blanket order.
Versions
All versions use ZJDE0001 as the default.
When you select a version, review the version's processing options to ensure that the version meets the
requirements.
1. Enter the version of WO Specify a version of the Work Order Processing program. The system calls this
Entry (P48013) to be used. version when you access Work Order Processing from this program.
2. Enter the version of Specify a version of the Purchase Orders program. The system calls this
Purchase Order Entry version when you access Work with Order Details from the Row menu of the
(P4310) to be used. Work with Detail Messages or Detail Message Revisions form.
3. Enter the version of Rate Specify a version of the Enter/Change Rate Schedule program. The system
Schedule Revisions calls this version when you access Work with Rate Schedules from the Form
(P3109) to be used. menu of the Work with Detail Messages or Detail Message Revisions form.
4. Enter the version of Specify a version of the Sales Order Entry program. The system calls this
Transfer Order Entry version when you access Sales Order Entry from this program.
(P4210) to be called.
5. Enter the version of Specify a version of the Blanket Order Release program. The system calls this
Blanket Release (P43216) version when you access Blanket Order Release from this program.
to be called.
SO Hold
Use these processing options to specify processing specific to sales orders.
1. Enter the Hold Code for the related sales order if a Specify a UDC (42/HC) that identifies why an order
work order is cancelled, deferred, or expedited. was placed on hold (for example, credit, budget, or
Blanks will not update the sales order. margin standards were exceeded).
PO Hold
Use these processing options to specify processing specific to purchase orders.
1. Enter the Hold Code for the related purchase order if a work order is Specify a UDC (42/HC)
cancelled, deferred or expedited. Blanks will not update the purchase order. that identifies why an
The purchase order will be updated only if the work order routings are order is on hold.
Page 83 of 135
recalculated.
Subsystem Job
Use this processing option to specify processing for subsystem jobs.
1. Enter a valid mode for the Subsystem Job. Use this option on Specify a valid mode for the
the version specified for Subsystem Job. subsystem job. Values are:
Blank: Do not add job to subsystem.
1: Add job to subsystem.
Adding a Freeze Code to a Work Order

Access the Work Order Details form.
Work Order Details form
Adding a Freeze Code to a Purchase Order

Access the Order Detail - Page II form.
Order Detail - Page II form
Analyzing Supply and Demand

Access the Work With Supply and Demand form.
Work With Supply and Demand form
(Rapid Start) Reviewing Detailed Messages

This section discusses:
• How to review detailed messages.
• Preconfigured processing options for and the United States Message Detail - DRP (P3411).
Reviewing Detailed Messages

This table lists the task for reviewing detailed messages:
Task Navigation Program Number Preconfigured Data

and Version
Review detailed Master P3411/RIS0001 Forecast types are:

messages. Scheduling, • AA – stores actual sales
Research and history.
Edit Messages • BF – stores forecast sales.
Branch plant is B10.
Work center is W10.
Items are SAMPLE1, SAMPLE2,
SAMPLE3, and SAMPLE4.
Data reports provide additional information about data that has been preconfigured for Rapid Start.
See (AUS and NZL) Rapid Start Data Reports.
See (CAN and USA) Rapid Start Data Reports.
Page 84 of 135
See (FRA) Rapid Start Data Reports.
See (GBR) Rapid Start Data Reports.
Preconfigured Processing Options for Message Detail - DRP (P3411)

These processing options show the values that are preconfigured for version RIS0001.
PO Info
1. Line Type S
2. Beginning Status 220
3. Consolidate blank
WO Info
1. Beginning Status 10
2. Cancelled Orders Status 99
OT Info
1. Consolidate blank
Blanket Info
1. Blanket Order Document Type to Release OB
Versions
Exit Versions blank
1. Blanket Order Release (P43216) RIS0001
2. Time Series (P3413) RIS0002
3. Pegging Inquiry (P3412) RIS0002
4. Supply/Demand Inquiry (P4021) RIS0001
5. Purchase Order Entry (P4310) RIS0001
Page 85 of 135
6. Work Order Entry (P48013) RIS0001
7. Rate Schedule Revisions (P3109) RIS0001
8. Transfer Order Entry (P4210) RIS0007
9. Scheduling Workbench (P31225) RIS0001
10. Bill of Material Inquiry (P30200) RIS0001
11. Item Branch (P41026) RIS0001
Display
1. Viewing Messages For Blank / blank
Validating Requirements Plans

This chapter provides an overview of requirements plan validation and discusses how to:
• Regenerate Capacity Requirements Planning and Rough Cut Capacity Planning (CRP/RCCP).
• Validate requirements plans.
Understanding Requirements Plan Validation

After you generate the requirements plan, either a master schedule or material requirements plan, you can
validate it to ensure that you have sufficient work center capacity. Use the CRP/RCCP Regeneration
program (R3382) to generate capacity planning information.
In EnterpriseOne software, the same batch program generates capacity planning information for both RCCP
and CRP. The only difference is in the work centers that you identify in the data selection.
The primary differences between RCCP and CRP are:
• RCCP is generally run for end items on the Maser Production Schedule (MPS) and considers only
critical work centers.
• CRP is generally run for all manufactured items and considers all work centers.
If critical work centers appear in the routings of component work orders that are generated by Material
Requirements Planning (MRP), then the system can also include MRP orders in RCCP because both RCCP
and CRP use the same batch program.
The CRP/RCCP Regeneration program generates:
• Over-capacity and under-capacity messages.
• Work center load.
• Period summary.
Page 86 of 135
The pacing resource for critical work centers is either labor or machine, depending on which one would
increase the work center's capacity. A work center is paced by labor if adding employees to the work center
increases capacity. A work center is paced by machine if adding machines increases capacity. Use the
Prime Load field on the Work Center Master Revisions form to define the pacing resource.
These terms are important for understanding master schedules:
Resource The resource units are the units associated with a work center for each workday on the Work
Units Day Calendar. The system displays resource units as hours, units, monetary amounts, floor
space, and so on. This information is associated with a work center for each workday on the
Work Day Calendar. The system uses this information to backschedule work orders in Shop
Floor Management and to calculate available hours for capacity planning. You can manually
enter or revise resource unit information for each work center and for each workday using the
Work Center Resource Units program (P3007).
Work Work Center Hours are recalculated using the Work Center Resource Units Generation
Center program (R3007G). You use this program only for processing data. It does not produce a
Hours printed report. However, you can view the results of the most recent refresh operation on the
Work Center Resource Units form.
Regenerating CRP/RCCP
This section provides an overview of capacity plan generation, lists prerequisites, and discusses how to:
• Set processing options for CRP/RCCP Regeneration.
• Run the CRP/RCCP Regeneration.
Understanding Capacity Plan Regeneration

Use the CRP/RCCP Regeneration program to compare prospective resource requirements to the capacity
that is available in critical work centers. The capacity plan indicates whether you should revise the schedule
to create feasible workloads or improve the use of limited resources.
When you run the CRP/RCCP Regeneration program, the system:
• Identifies critical work centers.
• Identifies the pacing resource for critical work centers.
• Calculates the rated capacity for critical work centers.
• Calculates the MPS load for critical work centers.
To calculate rated capacity for critical work centers, the system uses this standard formula:
Number of employees (or machines) × hours per day × efficiency factor × utilization factor
You can manually calculate efficiency by dividing standard hours by actual hours. For example, a crew
requires ten hours to complete a job that has standard hours established at eight hours, the crew is working
at 80 percent efficiency (8 ÷ 10 = .80).
For reference, the inverse operation (actual hours ÷ standard hours) is called realization.
The program calculates utilization by finding the number of hours in a day that the work center is actually
available for working compared to standard. One hundred percent utilization is an unrealistic goal because
preventive maintenance, employee breaks, and other factors typically affect utilization.
You calculate the MPS load for critical work centers by using either the routing table for planned work orders
(+PLO) or the routing instruction table for firm work orders (+WO) with a routing attached. If the work order is
firm (meaning that a header is created) but does not have a routing instruction attached, the system uses the
routing table. The formulas for calculating MPS load are:
Planned orders × pacing hours from the routing table
Firm orders × pacing hours from the routing instruction table
Page 87 of 135
The code in the Prime Load field in the Work Center Master File table (F30006) determines the type of
pacing at the work center.
Operations are backscheduled using the same logic in Shop Floor Management. This operation schedule
places load into the proper time frame. You must enter the time basis code and order quantity into the
equation for load calculation.
The system uses this formula to calculate the load for an operation:
Work order quantity × number of pacing hours on routing ÷ time basis code
The system generates messages that indicate whether the load is over-capacity or under-capacity.
Prerequisites
Capacity Requirements Planning follows the same level of operational planning as Material Requirements
Planning. You should synchronize the following information for both MRP and CRP:
• The planning horizon.
• The work-order document types.
• The statuses in the supply-and-demand inclusion rules.
Setting Processing Options for CRP/RCCP Regeneration

Use these processing options to define how the system processes data.
Process
These processing options enable you to specify the variable information that the system uses to regenerate
the CRP/RCCP.
1. Under Rated Specify the percent under the rated capacity that the system still considers as an
Capacity Percent underloaded work center. The system displays messages with a status of U (under)
for a capacity load that is less than the identified percentage under the rated value.
2. Over Rated Specify the percent over the rated capacity that the system displays as overrated and
Capacity Percent as an overloaded work center. The system displays messages with an O status
(over) for capacity loads that are greater than the identified percentage over the rated
value.
3. Branch Specify the branch that the system uses for the CRP/RCCP Planning Regeneration
program.
4. Supply/Demand Specify which supply-and-demand inclusion rule the system uses for the generation
Inclusion Rule of an item. Supply and demand inclusion rules define the criteria that the system uses
to select active orders for processing.
5. Capacity Mode Specify which capacity mode the system uses. Values are:
2: Use rough cut capacity planning.
3: Use capacity requirements planning.
6. Unit of Measure Specify the unit of measure that the system uses for backscheduling the capacity
load. The default unit of measure is HR (hour).
7. Roll Up to Dispatch Specify whether the system rolls up multiple work centers to a dispatch group for
Group review. Values are:
Blank: Do not roll up to a dispatch group.
1: Roll up to a dispatch group.
8. Closed Routing Specify the status for closed routing operation. CRP will not calculate loads for
Operation Status operations whose status (OPST) is greater than or equal to this value. If you leave
this processing option blank, loads will be calculated for all routing operation steps.
Page 88 of 135
Running CRP/RCCP Regeneration Program
From the Periodic Resource/Capacity Planning menu (G3321), select Capacity Requirements Plan.
Validating Requirements Plans

This section provides an overview of the validation process, lists prerequisites, and discusses how to:
• Review work center loads.
• Review period summaries.
• Set processing options for Operation Dispatch Inquiry (P31220).
• Review work schedules for production status.
• Set processing options for Work Center Schedule Review (P31224).
• Review rate schedule and work center loads.
• Review the Shop Floor Workbench for MRP.
Understanding the Validation Process

The validation process includes reviewing and revising capacity information in several programs.
Period Summaries
Use the Period Summary program (P3312) to review specific items that make up the capacity load for a
defined period for a work center. You can view the detail of all current and future orders that have been
scheduled for a work center.
The system summarizes the load by period using the unit of measure that you select. The system also
displays the percentage of total load that is planned for that period for an item on an order.
Work Center Scheduling Information

Use the Operation Dispatch Inquiry program to locate and update work center scheduling information. This
workbench environment serves as a starting point for work center scheduling and the release of work to the
shop floor. Use this program to:
• Access work order information, including the header, the parts list, and the routing instructions.
• Review work order information, such as work center, remaining labor, and machine and setup hours.
• Sort work orders by start date, requested date, or operation status codes.
• Change the work order status code, start date, or requested date.
Rate Schedule and Work Center Load

Use the Work Center Schedule Review program to review the rate schedule load and the work order load for
a work center. You can review a day, week, or month of the rate schedule load and the work order load. You
can also select a specific date range for which to view the load for the work center. If you need to adjust the
scheduled load at the work center, you can access several different forms on which to make adjustments.
Work Center Schedule Review is used primarily for rate-based items and is an alternative for viewing the
load on a work center. A processing option enables you to include loads that is generated by a work order
before or after rate loads.
Shop Floor Workbench

After a work order is on the shop floor, you must review the order and check capacity at the planned
production line. You might need to change a schedule to keep the Material Requirements Planning schedule
valid.
Page 89 of 135
Prerequisites
• Report hours and quantities for operations that are complete or partially complete to ensure that the
numbers for released load remaining for existing work orders are correct.
See Hours and Quantities Tracking.
• Verify that resource units exist for all of the critical work centers in the generation.
See Creating Work Centers.
• Set up supply and demand inclusion rules for Rough Cut Capacity Planning.
• Run the Master Production Schedule program.
Forms Used to Validate Requirements Plans

D
Review Work W3313 Daily Rough Cut Capacity Planning Review work center load and
Center Load A (G3312), Review Work Center Load review with the capacity.
Daily Capacity Requirements
Planning (G3313), Review Work
Center Load
Work With W3312 Daily Rough Cut Capacity Planning Evaluate the work center
Period Summary A (G3312), Period Summary - Rough load for a period.
Review Cut Capacity
Daily Capacity Requirements
Planning (G3313), Period Summary -
Capacity Requirements
Work With W3122 Daily Rough Cut Capacity Planning Update work center
Operation 0B (G3312), Operation Dispatch Inquiry scheduling information.
Dispatch Daily Capacity Requirements
Planning (G3313), Dispatch List
Work Center W3122 Daily Order Preparation - Discrete Review work-order or rate-
Schedule 4B (G3111), Work Center Schedule schedule load for the work
Review Review center.
Work With Order W3122 MRP Daily Operations (G3413), Shop Evaluate order schedule and
Scheduling 5D Floor Workbench compare to material
requirements plan.
Reviewing Work Center Loads

Access the Review Work Center Load form.
Review Work Center Load form
Reviewing Period Summaries

Access the Work With Period Summaries form.
Setting Processing Options for Operation Dispatch Inquiry (P31220)

Page 90 of 135
Defaults
Use these processing options to specify the defaults to use for processing.
1. Enter the Default OPERATION From Status

Status Information to preload to Specify the status user defined code (31/OS) on the Work with Operation
the screen at initial inquiry. If left Dispatch form that specifies the beginning date for the selection of work
blank, no value will be preloaded order information.
Thru Status
Specify the status (UDC 31/OS) on the Work with Operation Dispatch
form that specifies the end date for the selection of work order
information.
2. Enter the Default Number of Specify the from date on the Work with Operation Dispatch form. You
Days can specify a from date prior to the current date by entering the number
of days that the system must subtract from the current date. For
example, if the current date is 6/15 and you want the system to use 6/10
as the from date, enter 5. The system subtracts five days and sets the
from date to 6/10. If you leave this processing option blank, the system
uses the current date as the from date.
Note. The from date/period specifies that the system display
transactions beginning with this date or period. Totals are calculated for
the transactions that are displayed.
Specify the thru date on the Work with Operation Dispatch form. You can
specify a thru date later than the current date by entering the number of
days that the system adds to the current date. For example, if the current
date is 6/15 and you want the system to use 6/20 as the thru date, you
enter 5. The system adds five days and sets the thru date to 6/20. If you
leave this processing option blank, the system uses the current date as
the thru date.
Note. The thru date/period specifies that the system display transactions
ending with this date or period. Totals are calculated for the transactions
that are displayed.
Versions
Use these processing options to specify the versions of programs.
1. Work Order Specify the version that the system uses when you select the Work Order Entry
Processing (P48013) program (P48013) from the Row menu on the Work With Operation Dispatch form. If
you leave this processing option blank, the system uses version ZJDE0001.
2. Work Order Routing Specify the version that the system uses when you select the Work Order Routing
(P3112) program (P3112) from the Row menu on the Work With Operation Dispatch form. If
3. Work Order Parts Specify the version that the system uses when you select the Work Order Parts List
List (P3111) program (P3111) from the Row menu of the Work With Operation Dispatch form. If
4. Work Order Parts Specify the version that the system uses when you select the Work Order Parts List
Inquiry (P3121) Inquiry program (P3121) from the Row menu on the Work With Operation Dispatch
form. If you leave this processing option blank, the system uses version ZJDE0001.
5. Operation Dispatch Specify the version that the system uses when you select the Operation Dispatch
Inquiry (P31220) Inquiry program (P31220) from the Row menu on the Work With Operation Dispatch
form. If you leave this processing option blank, the system uses version ZJDE0001.
6. Work Order Quantity Enter a user-defined set of specifications that control how applications and reports
(P31121) and 7. Work run. You use versions to group and save a set of user-defined processing-option
Order Hours (P31122) values and data selection and sequencing options. Interactive versions are
associated with applications (usually as a menu selection). Batch versions are
associated with batch jobs or reports. To run a batch process, you must select a
Page 91 of 135
version. If you leave these processing options blank, the system uses version
ZJDE0001.
Process
Use this processing option to specify system processing.
Quantity Specify whether the system subtracts the quantity that is scrapped or canceled from the
Calculation remaining quantity. Values are:
Blank: Include the quantity that is scrapped or canceled in the remaining quantity.
1: Subtract the quantity scrapped or canceled from the remaining quantity.
Reviewing Work Schedules for Production Status

Access the Work With Operation Dispatch form.
Work With Operation Dispatch form
Thru Op Status (through Enter a UDC (31/OS) that indicates the status of an operation. The thru operation
operation status) status is used as an ending point to select work order information to display.
Setting Processing Options for Work Center Schedule Review (P31224)

Use these processing options to set system defaults, define how the system processes data, and specify
versions.
Defaults
This processing option defines the default document type.
1. Document Specify the default document type that is associated with the work order or rate schedule.
Type Document type is a UDC (00\DT) that identifies the origin and purpose of the document. Enter
the document type to use as a default value or select it from the Select User Define Code form.
Disp Options
1. Subfile Dates Specify how the system calculates and displays the loads. Values are:
Blank: Calculates and displays daily loads.
1: Calculates and displays monthly loads.
2: Calculates and displays weekly loads.
3: Calculates and displays daily loads.
WO Processing
1. Include Work Specify whether the system includes work order loads before rate schedules, after rate
Order Generated schedules, or not at all. Values are:
Loads Blank: The system does not recognize work order loads.
1: The system includes work order loads before rate schedules.
2: The system includes work order loads after rate schedules.
2. From Operation Specify the status that the system uses for the work orders or rate schedules as the
Status routing steps are completed. Operation status is a UDC (31/OS) that describes the status
of a work order or rate schedule. Enter the operation status to use as the default value or
select it from the Select User Define Code form.
3. To Operation Specify the operation status that the system uses for the work orders or rate schedules
Status as the routing steps are completed. Operation status is a UDC (31/OS) that describes the
status of a work order or rate schedule. Enter the operation status to use as the default
value or select it from the Select User Define Code form.
Page 92 of 135
Versions
1. Rate Specify the version that the system uses when you access the Enter/Change Rate Schedule
Revisions program from the Row menu from the Work Center Schedule Review program. If you leave
(P3109) this field blank, the system uses the ZJDE0001 version of the Enter/Change Rate Schedule
program.
Versions control how the Enter/Change Rate Schedule program displays information.
Therefore, you might need to set the processing options to specific versions to meet the
needs of the needs of the organization.
Reviewing Rate Schedule and Work Center Loads

Access the Work Center Schedule Review form.
Reviewing the Shop Floor Workbench for MRP

Access the Work With Order Scheduling form.
Work With Order Scheduling form
Planner Enter the address book number of a manager or planner.

Note. A processing option for some forms enables you to enter a default value for this field
based on values for category codes 1 (Phase), 2, and 3. You set up the default values on
the Default Managers and Supervisors form. After you set up the default values and the
processing option, the default information appears automatically on any work orders that
you create if the category code criterion is met. You can either accept or override the
default value.
Customer Enter a customer Address Book number.

Parent WO Enter a number that identifies the parent work order. You can use this number to:
(parent work • Enter default values for new work orders, such as Type, Priority, Status, and
order) Manager.
• Group work orders for project setup and reporting.
Status From Enter a UDC (00/ SS) that describes the status of a work order. Any status change from 90
through 99 automatically updates the date completed.
Search X-Ref Enter an alphanumeric value to use as a cross-reference or secondary reference number.
(search cross- Typically, this is the customer number, supplier number, or job number.
reference)
Quantity Open Enter the original quantity for the order detail line, plus or minus any changes to that
quantity, minus all quantities that are shipped, received, and vouchered to date.
Forecast Consumption
This chapter provides an overview of forecast consumption and discusses:
• Forecast consumption across multiple periods.
• Forecast consumption by customer.
See Also
Setting Up Forecast Consumption
Page 93 of 135
Understanding Forecast Consumption
Forecast consumption is based on the assumption that actual sales orders reduce, or consume, the
forecasted quantities. This approach ensures that sales orders are not treated as additional demand to the
forecast during a planning period. The plan begins with gross forecast. Actual sales orders are placed that
consume the forecast. The result is an adjusted forecast-that is, the forecast balance not consumed by sales
orders.
In EnterpriseOne software, you have two types of forecast consumption strategies that are available to you:
• Forecast consumption by period (time fence rules C and G).
• Forecast consumption across multiple periods (time fence rule H).
Either of these options can be limited to forecast consumption by customer.
Forecast consumption by period only requires that you use planning fence rule C or G, and create a forecast
for the item. The aggregate forecast will be reduced by the aggregate sale orders for a period.
Forecast consumption across multiple periods requires that you use planning fence rule H, create a forecast
for the item, and define forecast consumption periods. These forecast consumption periods span multiple
weekly or monthly planning periods or buckets. The aggregate forecast within the forecast consumption
period is reduced by the aggregate sales order in the same period. This calculation includes shipped sales
orders.
When you use the forecast consumption by customer functionality through processing options in
requirements planning, the system only reduces the forecast quantities for specific customers by the sales
order quantities for the same customer. If a customer does not have a customer-specific forecast, the system
uses the aggregate forecast consumption logic.
Forecast Consumption Across Multiple Periods

Forecast consumption is associated with planning fence rule H.
Forecast consumption periods (FCPs) are user defined and stored in the Forecast Consumption Periods
table (F3405). Within an FCP, the system processes sales orders against the gross (unadjusted) forecast
(quantity type of -FCSU) on a first-in, first-out (FIFO) basis. The system creates additional time periods if the
forecast end dates of the consumption period do not coincide with the period end dates of the time series.
The additional forecast consumption time periods are incremental to the number of time periods that are
identified in the MRP/MPS Requirements Planning program (R3482). The total for all time periods cannot
exceed 52.
The system only applies the forecast consumption calculations if you set the appropriate processing option
for the Master Schedule Planning - Multiple Plant program (R3483). To use forecast consumption, an item's
planning fence rule must be H, and the planning fence must be 999. These values are set on the Additional
System Information form in the Item Master (P4101) or Item Branch (P41026) programs.
Past Due Time Buckets

The graphic illustrates that you can set the number of past due time buckets to 1 or 2:
Page 94 of 135
Past due time buckets
Planning Horizon Time Periods

You can specify both forecast consumption and period end dates of the time series on the Work with
Forecast Consumption Revision form. You specify the number of daily, weekly, and FCP periods that are
included in the planning horizon in the processing option for the MPS - Gross Regeneration version of the
MRP/MPS Requirements Planning program. The system does not allow more than 52 total time series and
forecast consumption period buckets.
If you specify a number of planning horizon weeks in the processing options and the time series end does
not coincide with a forecast consumption period end, the system creates another time series bucket to reflect
the forecast consumption period.
If you define the forecast consumption periods by month and the forecast consumption period end does not
coincide with the month-end date in the shop floor calendar, the system displays the forecast consumption
date (not the month-end date) as a time series bucket.
You can set a processing option so that the system highlights all of the forecast consumption periods on
Time Series Inquiry. This action helps you differentiate between the time series and the forecast
consumption periods.
Forecast Consumption Calculation

You define forecast consumption periods to represent a period in which selected forecasts are partially or
fully consumed, or over-consumed by sales orders. This action enables you to include more than one time
series bucket in the calculation of the forecast consumption. That is, you can designate a longer period of
time (the forecast consumption period) for the system to compare the gross forecasts to the combined gross
sales orders and shipments.
With forecast consumption processing, the system uses these quantity types:
Type
-FSCU Unadjusted forecast quantity (gross) for a specific item from the detail forecast
table.
-SOU Actual sales orders from the sales order detail table.
Page 95 of 135
Type
-SO Portion of total sales orders that consumes the forecast. -SO can exceed the
forecast when sales orders are greater than forecast.
-SHIP Shipments that occur within the forecast consumption period.
-FCST Unconsumed forecast (net).
+WO, Work orders and planned orders: replenishment orders that cover the net
+PLO requirements.
In the next example, work orders for 50 and 135 units are open. The forecast is spread through the forecast
consumption period and is consumed on a first in first out basis.-SHIP + -SOU = Total Demand (10 + 40 +
175 = 225). Total Demand consumes FIFO; therefore, the beginning forecast is consumed and posted in the
-SO line. The net balance of the forecast is posted in the -FCST line. Notice in the first three periods that the
-FCST (net) has been reduced by a total of 225 pieces. The -SO indicates the amount that is consumed in
each period and also totals 225 pieces. Work order messages suggest increasing +WOU from 50 to 85.
Messages suggest expediting and decreasing +WOU in 6-30 from 135 to 100 in period June 17th. The
forecast consumption period is monthly and indicated with the asterisk in the period. This feature is turned on
when the processing options for the times series are set.
Qty Type Weeks Weeks Weeks Weeks Weeks
1 2 3 4 5
6-03-05 6-10-05 6-17-05 6-24-05 * 6-30-05
+BAU 75 15 -35 -135 -235
+BA 75 15
+WOU 50 135
+WO 85 100
-FSCU 60 100 100 100 80
-FCST 35 100 80
-SHIP 10
-SOU 40 175
-SO 60 100 65
=EAU 15 -35 -135 -235 -180
=EA 15
You can set the number of past due time buckets to one or two. The first past due bucket (PD2) includes all
activity that is scheduled to occur before the current generation date but within the current forecast
consumption period. The second past due bucket (PD1) includes all activity that is scheduled to occur before
the beginning of the current forecast consumption period.
Page 96 of 135
If you use at least one past due period, the system calculates unconsumed quantity for the first time bucket
as follows:
• Past due forecasts (-FCST prior to the generation date, but after the forecast consumption beginning
date) are consumed by:
 Past due sales orders (that have not shipped) that are within the forecast consumption
period.
 Sales orders that were shipped within the forecast consumption period, but prior to the
generation date.
• Any remaining -FCST is added to the -FCST in the first bucket that is not past due.
Forecast Consumption by Customer

Forecast Consumption by Customer enhances the ability of a supplier to meet the requirements from large
customers. When working with large customers, you might want to consider the demand for each customer
separately and plan production quantities accordingly. You can set up the system to net forecasts and sales
orders for a particular customer separately, so that you can plan more accurately for the specific demand
coming from individual customers.
If you do not use the forecast consumption by customer functionality, you compare total sales with total
forecast for a particular time period without considering individual customers. Calculating the difference
between total forecast and sales yields a different result than calculating the difference between forecast and
sales for an individual customer.
Note. If the system does not find a customer number in the forecast to match the customer number from the
sales order, the sales order consumes generic forecast quantities.
To use forecast consumption by customer, you have to enter a forecast for a specific customer. In this case,
the forecast record has a customer number in the Customer Number field. Based on the customer number,
the system can search for sales orders with matching customer numbers in the ship-to or sold-to field to
calculate the remaining demand for the customer. You specify whether the system uses to the ship-to or
sold-to field from the sales order by setting a processing option or by defining a customer address
relationship.
When you run the MRP/MPS Requirements Planning program, you can set up the program to use forecast
consumption by customer. You can use this functionality for items that are defined with planning fence rule
C, G or H. You cannot use forecast consumption logic for process items.
When you run the MRP/MPS Requirements Planning program and have activated the Forecast Consumption
by Customer functionality, the program calculates the net difference between forecast and sales orders for a
period for individual customers. The process consists of these steps:
• Check the Item Branch record for the item to see that the time fence rule is set to C, G or H.
• Read the Forecast File table (F3460) and the Sales Order Header File table (F4201) record for each
customer.
• Compare sales orders and forecast for each customer to determine which is greater.
The greater value of the two is written to the F3460 as a new forecast record with a forecast type
that indicates that it is the result of a Forecast Consumption by Customer calculation.
You can use the MPS Time Series program (P3413) to review the results of the calculation. The net forecast
that results from the Forecast Consumption by Customer calculation is displayed as the adjusted forecast
quantity (-FCST).
Note. You can use Forecast Consumption by Customer as well, if you are planning for multiple facilities, by
using the Planning Schedule - Multiple Plant program. You can set the same processing options as for the
MRP/MPS Requirements Planning program and determine, in addition, whether to consider interplant
demand as customer demand.
Forecast Consumption by Customer Calculation
Page 97 of 135
These tables illustrate the different results that are reached, depending on whether you differentiate by
customer. The first table demonstrates the results of a calculation that does not differentiate by customer:
Customer Sales Order Forecast Greater of Forecast and Sales Order
A 100 80
B 400 375
C 700 750
Total 1200 1205 1205
In this calculation, you aggregate all of the sales orders and all of the forecasts for an item and compare the
totals with each other. In this case, the total forecast is greater than the total sales order quantity. Therefore,
the forecast becomes the total demand.
This table demonstrates the results of a calculation that nets each individual sales order against a forecast
with matching customer number:
Customer Sales Order Forecast Greater of Forecast and Sales Order
A 100 80 100
B 400 375 400
C 700 750 750
Total 1250
In this calculation, the sales order and forecast quantities are not totaled. Instead, each sales order is
compared to a matching forecast. The greater quantity in each comparison is added to the total demand. In
this case, the total demand is greater than if the first method had been used.
Forecast Consumption by Customer Considerations

In order to use Forecast Consumption by Customer, you need to consider:
• Set up a forecast type for forecast consumption by customer in the UDC table 34/DF (Forecast
Type).
• Set up a version of the MRP/MPS Requirements Planning program by using these processing
options:
 Set the Forecast Consumption Logic processing option for using forecast consumption by
customer.
 Specify the forecast type to be used for forecast consumption by customer.
 Specify whether the system uses the sold-to or the ship-to number on the sales order when
searching for sales orders to net against a forecast.
• If you use multifacility planning, set up a version of the Master Planning Schedule - Multiple Plant by
using these processing options:
 Set the Forecast Consumption Logic processing option for using forecast consumption by
customer.
 Specify the forecast type to be used for forecast consumption by customer.
 Specify whether the system uses the sold-to or the ship-to number on the sales order when
searching for sales orders to net against a forecast.
Page 98 of 135
 Specify whether the system treats interplant demand as customer demand consumes the
forecast.
 Ensure that the items for which you are creating a requirements plan are defined with
planning fence rule C, G or H.
Working With Multilevel Master Schedules

This chapter provides an overview of multilevel master schedules and discusses how to:
• Set up a feature planned percentage.
• Generate a multilevel master schedule.
Understanding Multilevel Master Schedules

Multilevel master schedules support assemble-to-order production and delivery.
You set up and generate multilevel master schedules to:
• Define demand information on a family basis and make changes as needed.
• Define planning bills to acquire the options and features that you expect to sell.
When several material purchasing options are available, the planners can make informed decisions
within the available time frame. The system uses planning bills to notify planners when special
attention is needed.
• Update a product plan with a change in customer demand or design specifications.
• Customize the schedule generation to include only the information that you require.
• Explode planned orders down to component items.
Setting Up a Feature Planned Percentage

This section provides an overview of planning bills and discusses how to set up a feature planned
percentage.
Understanding Planning Bills

Planning bills are groups of items in a bill of material format that reflect how an item is sold. Planning bills
help you manage the acquisition of a variety of options and features that might be included in a saleable end
item.
Planning bills enable you to configure a pseudo end item. For a pseudo item, you do not have to assign a
unique part number or maintain a bill of material for every combination of options and features that might be
included in the end product.
You define planning bills to acquire the options and features in the proportion that you expect to sell. A final
assembly schedule coordinates the material selection and assembly after you order the product options.
Example: Automobile with two engine options

A part number can be assigned to the engine feature for planning purposes. The two engine options cannot
be assembled together, so the engine feature never actually exists in inventory. It is a pseudo item.
A stocking type of K identifies that the parent (automobile) is planned for in the same way as a kit. The
feature item (engine) has a stocking type of 0 (phantom). Phantoms call for a special type of processing for
which the leadtime is zero and the order policy is lot-for-lot.
Page 99 of 135
The planner does not know which automobile will ship with which engine next month, but the ratio of engine
types consumed is predictable. The planning bill of material identifies the percentages of each type of engine
that you expect to ship.
By exploding this bill against the master schedule for the planning family of automobiles, the system can
calculate the total requirements for each type of engine.
Example: Exploding Planned Orders

In this example, the system uses phantom processing to pass planned order releases from the parent
(T1000 automobile) directly through to the planned order releases of the engine feature. The system uses
the feature planning percentages to explode the planned order releases for the engine feature down to the
gross requirements for V-8 and V-6 engines.
This graphic depicts how feature planned percentages are used to explode a planned order release down to
gross requirements:
Exploding Planned Orders
Page 100 of 135

Form Used to Set Up Feature Planned Percentages
D
Enter Bill of W300 Daily PDM Discrete Define the feature percentage for an
Material 2A (G3011), Enter/Change item that is used for planning
Information Bill requirements
Setting Up a Feature Planned Percentage

Access the Bill of Material Revisions form.
Feat Plan % (feature Enter the percentage of demand for a specified feature based on projected production.
planned percentage) For example, a company might produce 65 percent of their lubricant with high
viscosity, and 35 percent with low viscosity, based on customer demand.
Material Planning uses this percentage to accurately plan for a process's co-products
and by-products.
Enter percentages as whole numbers, for example, enter 5 percent as 5.0. The default
value is 100.00 percent.
Generating a Multilevel Master Schedule

This section provides an overview of multilevel master schedule generation and discusses how to run the
MPS Regeneration for multilevel schedules.
Understanding Master Schedule Generation

When you run the MPS - Gross Regeneration version of the MRP/MPS Requirements Planning program
(R3482), the system compiles a master schedule. Select the MPS - Net Change version of the MRP/MPS
Requirements Planning program when you want to include only those items that have changed since the last
generation. You can create a version of the MRP/MPS Requirements Planning program specifically for
multilevel master scheduling.
When you generate a multilevel master schedule, the system explodes planned orders to the bill of material
component and identifies the percentages of all component items. By exploding the bill of material against
the total number of expected sales of a parent item, you can obtain the total requirements for each item at
each level in the bill of material.
When you generate a master schedule, the system evaluates selected information, performs calculations,
and recommends a time-phased planning schedule for all selected items.
Running the MPS Regeneration for Multilevel Schedules

From the Single Site Periodic Planning Operations menu (G3422), select MPS Regeneration.
Planning for Process and Repetitive

Manufacturing
This chapter provides overviews of process manufacturing planning and repetitive manufacturing planning
and discusses how to:
• Generate a master planning schedule for batch bills.
• Generate a master planning schedule for processes.
Page 101 of 135

• Generate a master planning schedule for repetitive items.
Understanding Process Manufacturing Planning

Process manufacturing results in products such as liquids, fibers, powders, and gases. Pharmaceuticals,
foodstuffs, and beverages are typical examples of process products. Products such as these are usually
manufactured by a two-step process:
1. Mixing or blending
2. Filling or packaging
These kinds of products might involve intermediate steps, such as curing, baking, or preparation.
Process manufacturing uses ingredients and bills of material. Ingredients can be either consumed or
produced during the manufacturing process. In a process bill of material, the quantity of a component can
vary, according to its grade or potency.
Unique features of process manufacturing are:
• Pacing co-products.
• Planned co-products (by-products are unplanned).
• Additional processing options in MPS/MRP.
Process manufacturing produces co-products and by-products. A co-product is a saleable end item that
results from a process. A by-product is a material of value that is produced incidental to or as a residual of
the process.
The different types of process manufacturing are:
• Batch
• Continuous
In batch processing, you usually produce a product in a standard run or lot size determined by vessel size,
line rates, or standard run length. Because of the life cycle of the product after its completion, you typically
schedule items that are made this way in short production runs. Co-products and by-products can be
generated during batch processing. Typical items that are produced with batch processing include:
• Pharmaceuticals
• Foods
• Inks and paints
• Glues
• Oil or chemical products
In the continuous flow environment, production runs typically continue for an extended duration. Equipment
is dedicated to one product or product line. This method of manufacturing is characterized by difficulty in
matching output volume with demand and varying yield from process operations. Examples are petroleum-
based products and water purification. Co-products and by-products are generally more prevalent in
continuous processing than in batch processing.
Master Production Scheduling (MPS) calculates the time series for co-products. Demand for the co-product
generates MPS order messages to drive the production process. Co-products that are fully satisfied by the
process do not receive order messages. Processes might also make a by-product that has value but is not
the central purpose of the process. For example, the lubricant process has co-products of household
lubricant and graphite lubricant, and a by-product of sludge. The lubricant would not be processed primarily
to obtain sludge.
Usually, both batch and continuous processing methods require extensive record keeping, such as recording
quality and tolerance values during the process, and strict adherence to lot tracing and tracking.
Batch Planning
Page 102 of 135

With batch manufacturing, a product is made from a bill of material in a standard run. The run is determined
by vessel size or standard run length. Typical products that use batch manufacturing include:
• Pharmaceuticals
• Foods
• Glues
• Fermented beverages
• Paints
The objective for batch manufacturing is to process work orders with a batch quantity that corresponds to a
batch bill of material and to use these orders for Material Requirements Planning (MRP) processing. Just as
the bill type uniquely defines a bill of material, you can use the batch quantity with bill type to further define a
unique bill.
With this manufacturing method, some restrictions on capacity determine the size of the batch that is
produced. For example, you might need to fill the vats to a certain level for the process to perform properly.
In addition, the system specifically defines the component quantities for the batch. For example, a 50-gallon
vat requires a given quantity of one component, but the system does not necessarily double the component
for a 100-gallon vat. Such components are often enzymes or catalysts.
Vats are often physically located close to a more repetitive downstream process. For example, in the
manufacture of bread, dough is mixed and left to rise in a vat before being formed into individual loaves and
sent for baking and packaging.
You often express units of measure for batches in terms of volume or weight, such as liters or kilograms.
After you create a batch bill of material and batch routing for the work order header, you process the batch
work order to attach the parts list and routing instructions to the work order header. Then you generate a
master schedule of batch work orders and review the output.
Understanding Planning for Repetitive Manufacturing

Use repetitive manufacturing for highly repetitive production that relies on a production rate. Repetitive
manufacturing enables you to specify a rate schedule by effective date in daily, weekly, or monthly
quantities.
Repetitive manufacturing has these characteristics:
• Production volume is stable and predictable.
• Lead time is short.
• Factory layout is product-oriented and often characterized as cellular manufacturing in which
dissimilar operations are physically grouped so that the product flows rapidly from one operation to
the next.
• Setups are short so that switching between products does not significantly affect the time that is
available for production.
• Group technology is often incorporated into the design engineering and manufacturing engineering
to accommodate some variety with little effect on cost or production speed.
• Unit of measure is often each.
However, it can also be volume- or weight-related when it is used in an environment that is similar to
process manufacturing (as opposed to discrete).
Examples of repetitive products are:
• Electronic goods.
• Automobiles.
• Durable consumer goods (washing machines, refrigerators, and so on).
Page 103 of 135

Generating a Master Planning Schedule for Batch Bills
This section provides an overview of MPS generation for batch bills and discusses how to generate MPS for
batch bills.
Understanding MPS Generation for Batch Bills

Use the MPS - Gross Regeneration version of the MRP/MPS Requirements Planning program (R3482) to
generate a master schedule for all items or for selected items. This program functions differently, depending
on whether more than one batch bill exists.
If only one batch bill exists, MPS uses the batch quantity in the following way:
• As a multiple, if the net requirements are greater than the batch quantity.
• As a minimum, if the net requirements are less than the batch quantity.
In either case, the program generates a separate planned order for each batch quantity.
For example:
Batch Quantity MPS Requirement Resulting MPS Planned Order
1000 1500 1000

1000
1000 967 1000
If the batch quantity is 1000 and the MPS requirement is:

• 1500, the program generates two planned orders for 1000 each.
• 967, the program generates a planned order for 1000.
If one batch bill is greater than all of the batch quantities, the program uses the largest batch quantity in
combination with any of the other quantities to most accurately satisfy the requirement.
For example:
400 1500 1000

600 600
800
1000
400 3000 1000

600 1000
800 1000
1000
If the batch quantities are:

• 400
• 600
• 800
• 1000
and the MPS requirement is for 1500. The program generates a planned order for 1000 and a planned order
for 600. Using the batch quantities, 1600 is the quantity that most accurately satisfies the requirement.
Page 104 of 135

If multiple batch bills exist and the net requirement is less than the largest batch quantity, the program uses
the next highest batch quantity to satisfy the requirement.
For example:
400 780 800

600
800
1000
If the batch quantities are:

• 400
• 600
• 800
• 1000
and the MPS requirement is for 780. The program generates a planned order for 800.
After you generate a master schedule, use MPS Time Series (P3413) and MRP/MPS Detail Message
Revisions (P3411) to review the time series and messages from the MPS generation.
The time series is a record of time-phased supply-and-demand netting for selected items. The messages
reflect how the system uses batches to generate order quantities for net requirements for each time period.
See Also
Setting Up Bills of Material
Setting Processing Options for MRP/MPS Requirements Planning (R3482)
Generating MPS for Batch Bills

Select Single Site Periodic Planning Operations (G3422), MPS Regeneration.
Generating a Master Planning Schedule for Processes

This section provides on overview of MPS Generation for processes, lists prerequisites, and discusses how
to generate a master planning schedule for processes.
Understanding MPS Generation for Processes

After you generate a master schedule, use the Time Series - MPS version of MPS Time Series and the
Message Detail - MPS version of MRP/MPS Detail Message Revisions to review the time series and
messages that the system generates.
Many processes produce multiple co-products. In each time period, whichever co-product has the greater
demand is the pacing co-product. For example, a process might produce both plastic and ethylene glycol
(antifreeze). If greater demand for plastic in a time period exists, the system plans for the process based on
the demand for plastic, which might result in excess antifreeze production.
The time series is a record of time-phased supply-and-demand netting for selected co- and by-products. Co-
products that are fully satisfied by the process do not receive order messages. Instead, the system creates
warning messages for co-products that are planned by a process.
Note. Process item numbers do not have a time series.
After you have defined the stocking types and co- and by-products for the process, you can generate and
review a master schedule of all process work orders and output. This output consists of time series and
messages for the co-products and by-products.
Page 105 of 135

Prerequisites
• Define co- and by-products for the process.
• Set up stocking type for process.
See EnterpriseOne Product Data Management 8.11 SP1 PeopleBook.
Forms Used to Generate a Master Planning Schedule for Processes

D
Work With W341 MPS Daily Operations Review time-phased supply-and-demand

Time Series 3A menu (G3412), MPS Time quantities.
Series/ATP Inquiry.
Work With W341 MPS Daily Operations Review detail messages that were
Detail 1D (G3412), MPS Detail generated by this version of Requirements
Messages Message Review Planning Regeneration (R3482).
Generating a Master Planning Schedule for Processes

Select Single Site Periodic Planning Operations (G3422), MPS Regeneration.
Generating a Master Planning Schedule for Repetitive Items

This section provides an overview of MPS generation for repetitive items, lists prerequisites, and lists the
forms used to validate master planning schedules for repetitive items.
Understanding MPS Generation for Repetitive Items

When you run the MPS - Net Change or the MPS - Gross Regeneration version of the MRP/MPS
Requirements Planning program (P3482), the system:
1. Evaluates selected information.
2. Performs calculations.
3. Generates a time series and messages for the selected items.
To generate the master production schedule for repetitive items:
1. Set the processing options to generate the master production schedule.
2.
Enter the type of rate schedule that you want to use for processing.
3. Set the appropriate processing option to extend rate adjustments to lower-level items.
After you generate a master production schedule, use MPS Time Series and MRP/MPS Detail Message
Revisions to review the time series and messages that the system has generated.
The time series is a record of time-phased supply-and-demand netting for selected items. The system links
the planned order releases for the parent item to the gross requirements of component items.
If a component does not have its own rate schedule, the system applies the demand from the parent item.
The demand from the rate-scheduled parent follows the same logic as regular work orders. When a rate
schedule is added for a component of a rate-based parent, the calculation includes the information for the
component in both the rate schedule (+RS) and unadjusted rate schedule (+RSU) data lines. The component
is processed as supply, and regular MRP logic applies.
Page 106 of 135

The messages reflect how the system uses rate-scheduled items to generate quantities for net requirements
for each time period. The MPS/MRP program produces three main action messages that pertain to repetitive
items:
Message Description
I= Updates an existing rate to the increased quantity.

Increase
rate to
H= Updates an existing rate to the decreased quantity.

Decrease
rate to
N= Treats messages as a group from the MPS/MRP Detail Message Review form. You
Create can answer more than one message at a time.
rate Instead of creating a single rate for a given schedule period type over a date range,
the system creates a series of rates to cover the entire period. For instance, instead
of having one weekly rate in effect for four weeks, the system creates four weekly
rates, each in effect for a week.
When you process a Create Rate message, the system can attach the parts list and
routing automatically.
When the system processes messages to update rates (I and H messages), it does not validate the dates
that are received. The MPS/MRP regeneration produces messages with valid dates. However, you can
change these dates before processing the message. To avoid updating invalid rates, ensure the validity of
the dates that you enter whenever you change message dates before processing.
Note. Non-repetitive items use lead time to backschedule the start date of an order. A repetitive item does
not use this logic. Repetitive items use the rates effective from and thru dates for backscheduling.
See Also
Setting Up Item-to-Line Relationships
Entering Work Centers and Routing Instructions
Prerequisites
• Set Stocking Type to M for manufactured item.
• Set
Order Policy Code to 5 (Rate Scheduled Item).
• Set Order Policy Value to define the length of the rate schedule.
• Ensure that all routings are set up.
• Ensure that all production lines are identified.
• Ensure that all rate schedules are set up.
Forms Used to Generate a Master Planning Schedules for Repetitive Items

D
Work With W341 MPS Daily Operations Review time-phased supply and demand
Time Series 3A menu (G3412), MPS Time quantities
Page 107 of 135

D
Series/ATP Inquiry
Work With W341 MPS Daily Operations Review detail messages that were
Detail 1D (G3412), MPS Detail generated by this version of Requirements
Messages Message Review Planning Regeneration (R3482).
Working with Multifacility Planning

This chapter provides overviews of multifacility planning and multifacility forecast consumption and discusses
how to:
• Generate multifacility requirement plans.
• Validate multifacility planning output.
Understanding Multifacility Planning

In a multifacility operation, planned orders at the demand facility are the source of demand at the supply
facility. You set up and maintain multifacility plans to:
• Manage the movement of material through distribution networks and multiple production facilities.
• Formalize the process of transferring items among the facilities.
• Create internal transfer orders to help ensure traceability of materials and their costs between
facilities.
• Ensure that the facility from which you are ordering has enough inventory in stock to fill the order or
schedule the supply plant to produce it.
• Schedule production according to realistic time frames.
• Use assembly lines at one plant to begin the assembly of a product and a different plant for final
assembly.
• Manage all resupply movements throughout the manufacturing network.
Multifacility plans enable greater control of the enterprise. You can define facility relationships at any level of
detail for an entire facility, a product group, a master planning family, or an individual item number. In
addition, you can incorporate all the facilities into a single plan.
In Material Requirements Planning (MRP), the system transfers items among the manufacturing plants at the
component level. The system transfers component items by generating:
• Purchase orders at the demand plant for the supply plant.
• Sales orders from the demand plant at the supply plant.
In this example, the demand plant (M55) receives components from three different supply plants. Supply
plants can also manufacture the end deliverable item. This diagram illustrates multifacility plan:
Page 108 of 135

Multifacility planning example
Understanding Multifacility Forecast Consumption

Multifacility forecast consumption in MRP is a process to reduce the forecast quantity through the number of
sales orders and shipped orders. The goal of forecast consumption is to have the forecast quantity be
greater than the total of sales orders and shipped orders. The forecast quantity is consumed either fully or
partially. For example, when the sales order quantity is greater than the forecast quantity, then the forecast
quantity is fully consumed. The option that you select is dependent on the need to forecast interplant
demand.
The system uses user-defined code (UDC) for quantity types (34/QT) for multifacility consumption:
Quanti Description
ty
Type
-FIDU Firm interplant (unadjusted). This quantity type represents orders for transfer sales
that the system generates. This quantity does not use planning messages to increase,
decrease, expedite, or defer the orders.
-FID Firm interplant demand. This quantity type represents orders for transfer sales that
the system generates. This quantity uses planning messages to increase, decrease,
expedite, or defer the orders.
-TIU Total independent demand (unadjusted). This quantity type represents the total
quantity that the system uses to consume forecast when you use forecast
consumption. When you compare customer demand to forecast quantity (for example,
the G or the C planning rule), -TIU is the quantity that the system uses as customer
demand. This quantity might or might not include interplant demand (-ID and -FID).
Interplant demand depends on the Interplant Demand processing option for the
Master Planning Schedule - Multiple Plant program (R3483).
-TI Total independent demand. This quantity type represents the quantity for customer
demand after the system runs forecast consumption logic.
-ID Interplant demand. This quantity type represents the quantity of demand that the
system generates to support another facility's requirements.
Calculations
Page 109 of 135

If the Interplant Demand processing option for the Master Planning Schedule - Multiple Plant program
(R3483) is selected, the transfer orders consume the supply plant's forecast. The system does not plan the
transfer orders again. The system uses these calculations when the Interplant Demand processing option is
selected:
• −TIU = (−SOU) + (−ID) + (−FID)
• +PLO = (−FSCT) + (−TI)
If the Interplant Demand processing option is not selected, the system processes the transfer orders as
additional demand for the supply plant. The system uses these calculations when the Interplant Demand
processing option is not selected:
• (TIU) = (−SOU)
• +PLO = (−FSCT) + (−FID) + (−TI) + (−ID)
Additional Options for Multifacility Forecast Consumption

To have interplant demand consume forecast, you need to add the transfer order type to UDC table 40/CF.
The system then accumulates ship-confirmed transfer orders in the −SHIP quantity type while still using the
orders to consume forecast. Also, regardless of the setting of the Interplant Demand processing option, the
system processes interplant demand consistently whether the order is planned demand or firm demand. For
example, interplant demand either consumes or does not consume forecast.
If you do not want to use the new quantity types, you can make a copy of the UDC table (34/QT) with the
necessary quantity types. The system completes the calculations but does not display them on the time
series. The system displays the following results when you remove quantity types:
−FIDU The system does not write the orders to the time series.
−FID The system writes the orders to the −ID quantity type.
−TIU The system does not write the orders to the time series.
−TI The system writes the orders to the −SO quantity type.
Generating Multifacility Requirement Plans

This section provides an overview of multifacility plan generation, lists a prerequisite, and discusses how to:
• Run the Master Planning Schedule - Multiple Plant program.
• Set processing options for Master Planning Schedule - Multiple Plant (R3483).
Understanding Multifacility Plan Generation

After you have set up the supply and demand relationships among the branch/plants, you can use the
Distribution Requirements Planning (DRP), Master Production Scheduling (MPS), and MRP gross
regeneration versions of Master Planning Schedule - Multiple Plant to generate a multifacility plan.
Alternatively, you can use the DRP, MPS, and MRP net change versions of Master Planning Schedule -
Multiple Plant to generate a multifacility plan.
When you generate a multifacility plan, the system evaluates selected information, performs calculations,
and recommends a time-phased plan for all selected items.
Prerequisite
Set up DRP/MPS multifacility planning.
Page 110 of 135

Running the Master Planning Schedule - Multiple Plant Program
Use one of these navigations:
• Multifacility Planning menu (G3423), MPS Regeneration.
• Multifacility Planning menu (G3423), MRP Regeneration.
Setting Processing Options for Master Planning Schedule - Multiple Plant

(R3483)
Use these processing options to:
• Define the planning horizon.
• Define program parameters.
• Specify which inventory buckets the system considers on-hand.
• Define the forecast to use as demand.
• Define document types to use when creating supply.
• Define the leadtimes and damper days.
• Define the manufacturing mode and multifacility parameters.
Horizon
These processing options specify dates and time periods that the program uses when it creates the plan.
1. Generation Start Date Specify the date for starting the planning process. This date is also the beginning of
the planning horizon.
2. Past Due Periods Specify the number of past due periods prior to the generation start date that is
displayed on the time series.
3. Planning Horizon Specify the number of days, weeks, and months for which you want to see planning
Periods data.
Parameters
Use these processing options to define processing criteria. The generation type selection is important:
• Generation Type 1, single-level MPS/DRP.
You can use this generation type either in a distribution environment for purchased parts with no
parent-to-component relationship, or in a manufacturing environment with parent-to-component
relationships. When you use this generation type, the system performs these actions:
 Produces a time series for each item that you specify in the data selection with a planning
code of 1 on the Plant Manufacturing Data tab of the Work with Item Branch form. This code
indicates whether the item is manufactured or purchased.
 Does not explode demand down to the components for manufactured items. Use generation
type 1 if you first want to process only the master-scheduled end-items. Thus, you can
stabilize the schedule before placing demand on the components.
 Does not create pegging records.
• Generation Type 3, multilevel MPS.
This generation type is an alternative to generation type 1 and performs a complete top-to-bottom
processing of master-scheduled items. For all parent items that you specify in the data selection, the
program explodes demand down to the components. You must specify all of the items to be
processed in the data selection, not just the parent items. The program also creates pegging
records.
• Generation Type 4, MRP with or without MPS.
Page 111 of 135

This generation type performs the same functions as generation type 3. After you perform a
complete generation and stabilize the master schedule, you can limit data selection to MRP items
(with planning codes of 2 or 3), thereby reducing processing time. This action is possible because
the system still stores demand from the master-scheduled items in the MPS/MRP/DRP Lower Level
Requirements File table (F3412).
• Generation Type 5, MRP with frozen MPS.
This generation type freezes the master schedule after it has been stabilized. Before using this
generation type, make all necessary adjustments to master-scheduled items and release orders to
provide supply for the demand. This generation type freezes the entire planning horizon, which is
similar to the way the freeze fence freezes a part of the horizon. Running this generation type
produces results that apply to MPS items only:
 No new orders will be planned.
 No messages for existing orders will be created.
 The adjusted ending available quantity can be negative.
 Demand is exploded down to components from existing work orders only. No -PWO demand
from parent items exists; only -FWO demand exists.
1. Generation Mode Specify the generation mode.

A gross regeneration includes every item that is specified in the data selection.
A net change includes only those items in the data selection that have changed
since the last time you ran the program.
Values are:
1: Net change
2: Gross regeneration
2. Generation Type Specify the generation type.
Please see the help for the Parameters tab for detailed information.
Values are:
1: Single-level MPS/DRP.
3: Multi-level MPS.
4: MRP with or without MPS.
5: MRP with frozen MPS.
3. UDC Type Specify the UDC table (system 34) that contains the list of quantity types to be
calculated and written to the Time Series table (F3413). The default is QT.
4. Version of Specify which version of supply/demand inclusion rules the program reads.
Supply/Demand Inclusion These rules define the criteria that is used to select orders for processing.
Rules
On-Hand
These processing options define how the program calculates on-hand inventory.
1. Include Lot Specify whether the system considers lot expiration dates when calculating on-hand
Expiration Dates inventory. For example, if you have 200 on-hand with an expiration date of August 31,
2005, and you need 200 on September 1, 2005, the program does not recognize the
expired lot and creates a message to order or manufacture more of the item to satisfy
demand. Values are:
1: Consider.
2. Safety Stock Specify whether to plan based on a beginning available quantity from which the safety
Decrease stock quantity has been subtracted. Values are:
Blank: Do not decrease.
1: Decrease.
3. Receipt Routing Specify whether items in transit, in inspection, or otherwise dispositioned are
Page 112 of 135

Quantities considered in the beginning available calculation or are part of the In Receipt (+IR)
bucket on the time series.
In a manufacturing environment, sometimes you need to establish where stock is to
determine whether it is available for immediate use. Enter 1 in the Beginning Available
field if you want quantities in transit to be included the beginning available calculation
on the time series. Otherwise, the program includes these quantities in the In Receipt
(+IR) line of the time series. The quantities are still considered available by this
program. The only difference is in how you view the quantities in the time series. Values
are:
Quantity in Specify whether to include quantities in inspection when the system calculates the
Inspection beginning available amount. Otherwise, the system includes these quantities in the In
Receipt (+IR) line of the time series. The system still considers the quantities available,
but the way in which you view the quantities in the time series differs. Values are:
1: Include.
User Defined Specify a value.
Quantity 1 and User In a manufacturing environment, sometimes you need to establish where stock is to
Defined Quantity 2 determine whether it is available for immediate use. Enter 1 if you want these user-
defined quantities (defined on Receipt Routings Revisions in the Update Operation 1
field or the Update Operation 2 field) to be included in the beginning available
calculation. Otherwise, the program includes these quantities in the In Receipt (+IR) line
of the time series. The quantities are still considered available by this program. The only
difference is in how you view the quantities in the time series. Values are:
4. Lot Hold Codes Specify the lots to be included in the calculation of on-hand inventory. You can enter a
( up to 5 ) maximum of five lot hold codes (41/L).
Blank: Include no held lots in the calculation of on-hand inventory.
*: Include all held lots in the calculation of on-hand inventory.
5. Include Past Due Specify whether the system considers open quantity from past-due rate orders as
Rates as a supply supply. If you enter 1, open quantities from past-due rate orders are included in the rate
schedule unadjusted (+RSU) line as well as the rate schedule adjusted (+RS) line of the
Master Planning Schedule - Multiple Plant program). Values are:
1: Consider.
Forecasting
These processing options serve two purposes:
• They determine which forecast types the program reads as demand.
• They initiate special logic for forecast consumption.
1. Forecast Types Used Specify forecast types.

( up to 5 ) Forecasts are a source of demand. You can create forecasts using 12 different
forecast types (34/DF) within the Forecasting system. One is considered the
Best Fit (BF) type compared to an item's history of demand. Use this processing
option to define which forecast quantities created by which forecast type are
included in the planning process. Enter multiple values with no spaces, for
example: 0102BF.
2. Forecast Consumption Specify whether the system uses forecast consumption. If you use forecast
Logic consumption, any sales order that is due in the same period as the forecast is
included as part of the forecast for that period. The sales order is not
considered an additional source of demand. For forecast consumption to be
Page 113 of 135

used, the planning fence rule for the item must be H and the planning fence
must be 999. You enter these values on the Plant Manufacturing Data form.
Note. When you use forecast consumption, the system applies forecast
consumption logic to the aggregate sales order and forecast quantities.
Blank: Do not use.
1: Use.
3. Interplant Demand Specify whether to use interplant demand to consume forecast when using
Consumes Forecast forecast consumption. When using any other planning rule, you can use this
option to specify whether to consider interplant demand as customer demand.
When the option is set, the system considers interplant demand for firm and
planned transfer orders.
When the option is blank, the system ignores interplant demand by forecast
consumption or planning rules and considers interplant demand as a separate
source of demand. Values are:
Blank: Do not consider interplant demand as customer demand.
1: Consider interplant demand as customer demand.
4. Forecast type for Specify the forecast type UDC (34/DF) that the system uses to create a forecast
forecast consumption by for the actual daily demand by customer. This processing option applies when
customer you set the Forecast Consumption Logic processing option to 2 (Forecast
Consumption by Customer). This value cannot equal the value in the Forecast
Types Used processing option.
5. Default Customer Specify which address book number on the sales order the system uses for
Address Relationship for calculation when you use forecast consumption by customer logic. Values are:
Forecast Consumption by 1: Ship to address book number.
Customer
2: Sold to address book number.
Document Types
These processing options establish default document types.
1. Purchase Specify a value.

Orders When you receive messages that are related to purchase order creation, this document
type will appear as the default. The default value is OP.
2. Work Orders Specify a value.
When you receive messages that are related to work order creation, this document type will
appear as the default. The default value is WO.
3. Rate Specify a value.
Schedules When you receive messages that are related to rate schedule creation, this document type
will appear as the default. The default value is AC.
Lead Times
These processing options let you specify safety lead times to allow extra time for delays in receipt or
production. Use damper days to filter out unwanted messages.
1. Purchased Item Specify a value.

Safety Lead Time For items with stocking type P, the program adds the value that you enter here to the
2. Manufactured Item Specify a value.
Safety Lead Time For items with stocking type M, the program adds the value that you enter here to the
3. Expedite Damper Specify the number of days before the system generates an expedite message. If the
of the order is less than the number of days that are entered here, the system does
not generate an expedite message.
Page 114 of 135

4. Defer Damper Specify the number of days before the system generates a defer message. If the
generate a defer message.
Performance
These processing options define output and specify conditions that might decrease processing time.
1. Clear F3411/F3412/F3413 Warning! Use this processing option with extreme caution.
Tables
If you enter 1, all records in the MPS/MRP/DRP Message table (F3411), the
MPS/MRP/DRP Lower Level Requirements (Pegging) table (F3412), and the
MPS/MRP/DRP Summary (Time Series) (F3413) table are purged.
Access to this program should be limited. If multiple users run this program
concurrently with this processing option set to 1, a record lock error results
and prevents complete processing. Values are:
Blank: Do not clear tables.
1: Clear tables.
2. Input the Branch/Plant Specify which Branch/Plant records in the MPS/MRP/DRP Message File
Where Planning Tables Will table, the MPS/MRP/DRP Lower Level Requirements File table, and the
Be Cleared MPS/MRP/DRP Summary (Time Series) table (F3411, F3412 and, F3413,
respectively), are purged.
Note. This option is valid only when the Clear F3411/F3412/F3413 Tables
processing option on the Performance tab is set to 1 and the Delete
Branch/Plant processing option contains a valid branch/plant.
This processing option enables a preprocess purge of these tables. If this
processing option is not enabled or is cleared, the system purges records for
a given branch/plant and item as you plan the item. Depending on processing
option combinations, certain scenarios can occur.
Example 1:
Clear F3411/F3412/F3413 Tables is set to 1.
(a) Delete Branch/Plant is set to Blank.
All records from the three tables will be purged.
(b) Delete Branch/Plant contains a valid branch/plant.
Records for all the items that belong to the valid branch/plant will be purged
from the three tables.
(c) Delete Branch/Plant contains an invalid branch/plant.
No records will be purged from the three tables.
Example 2:
Clear F3411/F3412/F3413 Tables set to Blank
Delete Branch/Plant is not active.
No records from the three tables will be purged.
3. Initialize MPS/MRP Print Specify a value to initialize the F4102 table.
Code If you enter 1 for this processing option, the program initializes every record
in the Item Branch table (F4102) by setting the Item Display Code (MRPD) to
blank.
If you leave this field blank, processing time is decreased. The system will
not clear the records in the Item Branch table (F4102).
Regardless of how you set this processing option, for each item in the data
selection the MRPD field is updated in this way:
• 1 if messages were not created.
• 2 if messages were created.
The Print Master Production Schedule program (R3450) enables you to enter
data selection based on the MRPD field.
Page 115 of 135

Values are:
Blank: Do not initialize the Item Branch file.
1: Initialize the Item Branch file.
4. Messages And Time Series Specify whether the program generates messages and time series for
For Phantom Items phantom items. Values are:
Blank: Do not generate.
1: Generate.
5. Ending Firm Order Status Specify the work order status at which messages are no longer exploded to
components. If you leave this processing option blank, all messages are
exploded to components.
6. Extend Rate Based Specify whether adjustments for rate based items are exploded to
Adjustments components, thereby creating messages for the components. Values are:
Blank: Do not extend.
1: Extend
7. Closed Rate Status Specify the status of closed rates. When you plan for a rate-based item, the
system does not process rate orders that are at a closed-rate status or a
higher status.
8. Set Key Definition For Specify whether to support concurrent MRP/MPS runs. The value that you
Table F3411 and 9. Set Key enter determines the range for the number of records in the F3411/F3412
Definition For Table F3412 tables for a given run. The number must be large enough to include the
number of records that will be generated for the table. For example, if you
enter a value of 8 for the first run and 10 for the second run, the range of
records that the system reserves for two simultaneous MRP/MPS runs will
include:
First run:
The system reserves records in the range of 1 to [1*10^8], or 1 through
1,000,000,000.
Second run:
The system reserves records in the range of [1*10^8 + 1] to [2*10^10], or
100,000,001 through 20,000,000,000.
Notice that the values that you enter serve as the exponent in the previous
equations. Values are:
Default value: 10
Minimum value: 7
Maximum value: 14
Note. This process runs only when a subsequent MRP/MPS job is submitted
while an existing job is currently running. The MRP/MPS Requirements
Planning program (R3482) and Master Planning Schedule - Multiple Plant
program (R3483) enforce these values. You determine the optimal value for
the key definition. All values for this table should be the same for all versions.
If version settings are not the same, the results are unpredictable.
10. Set Maximum Number Of Specify the maximum number of branches that the system processes when
Branches you run the Master Planning Schedule - Multiple Plant program (R3483).
Because this processing option controls the allocation of memory for arrays,
you should use the minimum number of branches that are necessary.
Warning! The system supports up to 99 locations. If you specify more
locations than 99, the program might generate unpredictable results. You
should make incremental adjustments to this value.
11. Suppress Time Series Specify whether the system generates the time series. Values are:
Blank: Generate.
1: Do not generate.
Page 116 of 135

Note. Performance improves when the time series is not generated.
Mfg Mode
These processing options specify integration with other systems.
1. Process Specify a value.

Planning If you use process manufacturing, enter 1 to generate the plan based on the forecasts of
the co- and by-products for the process. The program then creates messages for the
process. Values are:
Blank: Discrete
1: Process
2. Configurator Specify whether the system processes configurator components from the Configurator
Functionality Component Table (F3215) and adds them to the Sales Order Detail File table (F4211) and
the Work Order Parts List table (F3111). If you enter 1 in this processing option, the
system processes the items on the Configurator Components table as demand items.
Blank: Do not process.
1: Process.
3. Project Specify whether the system includes supply and demand from items that are associated
Planning with a project. Project-specific items have a stocking type of P. Values are:
1: Include.
Multi-Facility
These processing options define criteria for a multifacility environment.
1. Date Branch Specify the default branch/plant from which to retrieve the shop floor calendar.
If you leave this processing option blank, the calendar for each branch/plant is used and
processing time increases.
2. Consolidation Specify a value.
Method The simple consolidation method (1) adds the supply and demand for each branch,
calculates a new time series, and places the result in the consolidated branch that is
specified in the Consolidation Branch processing option.
The branch relationships method (2) uses the Branch Relationships table. This is the
default. Values are:
1: Simple consolidation.
2: Branch relationships (default).
3. Consolidation Specify a branch/plant.
Branch If the consolidation method is 1 (simple consolidation), enter the branch/plant to contain
the consolidated results. If the consolidated branch/plant also contains its own time
series data, that data is included in the totals.
4. Category Code Specify a code.
If the consolidation method is 2 (branch relationships), enter the category code of the
part that is supplied by one branch/plant to another. Five UDC tables are exist.
Values are:
1: 41/P1
2: 41/P2
3: 41/P3
4: 41/P4
5: 41/P5
5. Manufacture At Enter 1 if manufactured and purchased items are in the same category code, but you
Origin want to obtain the purchased items from another branch/plant. Transfer order
messages are created for purchased items, and work order messages are created for
Page 117 of 135

manufactured items. Values are:
Blank: Create transfer orders for manufactured and purchased items.
1: Create transfer orders only for purchased items.
6. Transfer Order Specify a document type.
Document Type When you receive messages that are related to transfer order creation, this document
type will appear as the default. The default value is OT.
Parallel
These processing options specify the number of processors that the system uses during parallel processing.
These processing options also specify whether the system runs preprocessing during parallel processing.
1. Number of Specify the number of subsystems in a server.

Subsystem The default is 0 (zero).
Jobs
2. Pre Specify whether the system runs preprocessing during parallel processing. During
Processing preprocessing, the system checks supply and demand and plans only the items within
supply and demand. Preprocessing improves performance when you run MRP and is valid
only when the number of items actually planned is less than the total number of items in the
data selection. Values are:
Blank: Does not run preprocessing.
1: Runs preprocessing.
Validating Multifacility Planning Output

This section provides an overview of multifacility planning output and lists the forms used to validate
multifacility planning output.
Understanding Multifacility Planning Output

Multifacility planning output consists of information in the time series and transfer order messages. Use the
time series information to either accept or override the planning that the system suggests. You should review
the transfer order messages for individual item numbers to determine which action, if any, you need to take.
Branch Relationships
Use the Branch Relationships Chart (P34031) to review supply and demand relationships in a graphical,
hierarchical format. The Branch Relationships Chart displays:
• Branch.
• Level of the branch.
• Supply branches for the corresponding demand branch.
The MRP, DRP, and MPS versions of the Branch Relationships Chart program use the same processing
options. You can vary the settings in the processing options to accommodate the different requirements for a
material requirements plan.
Reviewing the Time Series for the Multifacility Schedule

Use MPS Time Series (P3413) to review the time series for the multifacility schedule. The multifacility
schedule is a record of time-phased supply and demand for selected items. This data is derived from the
most recent regeneration or net change run. Processing options in the Master Planning Schedule - Multiple
Plant program enable you to set up daily, weekly, or monthly time periods (buckets).
This table lists the quantity types displayed in the time series for multifacility planning:
Page 118 of 135

Quantity Description
Type
+PLO Planned orders. Represents the recommended replenishment orders for an item.
This quantity type appears on the demand branch's time series.
−ID Interplant demand. This quantity type indicates the net demand that the system
transfers to the supply branch/plant for all demand branch/plants.
Transfer Order Messages for the Multifacility Schedule

Use MRP/MPS Detail Message Revisions (P3411) to review the transfer order messages for the multifacility
schedule. Multifacility scheduling creates messages that are appropriate to the demand and supply facilities.
If you process the messages, the system automatically creates transfer orders. You can transfer items
between facilities either at cost or at a markup.
See Also
Setting Up Multifacility Planning
Forms Used to Validate Multifacility Planning Output

D
Work With Branch W3403 Multifacility Setup (G3443), Branch Review branch
Relationships 1D Relationships Chart relationships.
Hierarchy
Work With Time Series W3413 Multifacility Planning Daily Review transfer order
A Operations (G3414), Time quantities
Series/ATP Inquiry
Work With Detail W3411 Multifacility Planning Daily Review and process
Messages D Operations (G3414), Detail transfer order messages
Message Review
Working With Supplier Release Scheduling

This chapter provides an overview of supplier release scheduling and discusses how to:
• Generate contract-based supplier release schedules.
• Enter ad hoc schedules.
• Capture supplier commitments.
• Release supplier schedules.
Understanding Supplier Release Scheduling

Supplier release scheduling provides the suppliers with consistent shipping information and advanced
demand profiles to support the goal of just-in-time production and delivery. You can create supplier release
Page 119 of 135

schedules that meet the buyer's purchasing needs and enable suppliers to plan their production and shipping
schedules. Using supplier schedules enables you to convert the purchase order messages that are
generated by running the MRP/MPS Requirements Planning program (R3482) into a realistic supplier plan.
The supplier schedule identifies both short- and long-term needs for purchased items at the facility.
Buyers can use supplier schedule master information, based on blanket orders, to set up and maintain
supplier contracts with information about delivery criteria. If you want to use more than one supplier for an
item, you need to define supplier split percentages. You can communicate supplier schedules to the
suppliers using electronic data interchange (EDI) or print.
Supplier release scheduling enables you to:
• Support item-specific relationships for scheduled shipments at the supplier's site.
• Set up blanket purchase orders and material shipping arrangements with each supplier.
• Generate a shipping schedule for all supplier-scheduled demand within the release horizon.
• Generate multiple supplier schedules for a single item.
• Adjust the shipping schedule for unplanned events, and create blanket order releases.
• Release commitments against existing blanket orders in the form of purchase orders at the release
fence automatically.
• Print supplier schedule information, or send it to the supplier using EDI.
• Maintain a history of supplier schedules and commitments.
Supplier Release Scheduling Using the Self-Service Portal Workspaces

If you have the Supplier Relationship Management portal installed, you can collaborate with the supplier
using the supplier self-service portal. The supplier can view the schedules that you have generated and enter
commitments against them. The Buyer Workspace also enables the buyer to enter ad hoc schedules
manually. You create ad hoc schedules when you have not set up supplier schedule information for a
supplier.
Supplier release scheduling using the self-service workspaces enables you to:
• Enter and maintain ad hoc schedules.
• Respond to exception messages in the form of portal alerts.
• Release commitments against blanket and ad hoc schedules in the form of purchase orders.
Generating Contract-Based Supplier Release Schedules

This section provides overviews of supplier schedule generation and supplier schedule revisions, lists
prerequisites, and discusses how to:
• Generate contract-based supplier release schedules.
• Set processing options for Supplier Schedule Generation (R34400).
• Set processing options for Supplier Schedules Revisions (P34301).
• Revise contract-based supplier release schedules.
Understanding Supplier Schedule Generation

You use the Supplier Schedule Generation program (R34400) to process purchase order messages of
message types O, B, G, and L on the material requirements plan. You can use this program to generate
blanket order-based schedules, as well as ad hoc schedules.
Page 120 of 135

When you generate the supplier schedule, the system uses the messages from the most recent Material
Requirements Planning (MRP) generation, blanket orders, and the information that is defined in the Supplier
Schedule Master File table (F4321) to create a supplier schedule. The system determines demand from the
MRP messages.
Important! Do not change the messages after the system has generated them from MRP.
You can set the appropriate processing option for the Supplier Schedule Generation program to clear MRP
messages after schedule generation. The system clears only those messages that are inside the releasable
time fence.
If you use multiple suppliers, the system creates multiple supplier schedules for a single item. It does so by
splitting the MRP messages by the percentages that you defined in the F4321 table.
When you generate a supplier schedule, the system creates a draft of the supplier schedule and prints a
report that details any discrepancies that might make the supplier schedule ineffective. You can review the
draft of the supplier schedule by using the Supplier Schedule Revisions program (P34301) and make any
necessary revisions prior to committing to a final schedule. Blanket order-based schedules are stored in the
Vendor Schedule Quantity File table (F3430).
When you have generated the schedule and communicated it to the supplier, the supplier can make
commitments for items that require commitments. You can use the processing options to indicate whether
you require commitments from the suppliers in response to the planned quantities on the supplier schedule.
If you use EDI to send the schedule to the supplier, the supplier can communicate committed quantities back
to you, using EDI standards. If you do not use EDI, the supplier can send commitments by other means—for
example, fax—and you enter the committed quantity into the schedule. Commitments that are entered for a
blanket order-based schedule are stored in the Vendor Schedule Commitment File table (F3435).
You can run the Supplier Schedule Generation program multiple times to accommodate changes. For
blanket order-based schedules, a snapshot of the schedule is saved to the Vendor Schedule History File
table (F3440) every time that you run the program. You can view the values from the previous schedule in
the previous quantity fields in the Supplier Schedule Revisions program.
If you rerun the schedule generation after the committed quantity was entered, the current Committed
Quantity value does not change. If the Committed Quantity field was populated from the Planned Quantity
field for an item that does not require a supplier commitment and the planned quantity changes due to a
supplier schedule regeneration, the committed quantity changes accordingly.
Self-Service Portal Workspaces

If you are working with the self-service portal workspaces, you can also use the Supplier Schedule
Generation program to generate ad hoc schedules. You use processing options to determine whether the
program generates ad hoc schedules and the date until which purchase-order planning messages can be
converted into ad hoc schedules.
The self-service portal enables you to review both blanket and ad hoc schedules after you have generated
them. You use the Supplier Schedule Revisions program to review and revise blanket schedules. You use
the Ad Hoc Schedule Revisions program (P34302) to review and revise ad hoc schedules.
When the supplier has been notified using email that a schedule exists, he or she can use the supplier self-
service portal to enter committed quantities into the schedule. Commitments that are entered for ad hoc
schedules are stored in the Ad Hoc Vendor Schedule File table (F3450).
See Also
Working with Blanket Orders
Understanding Supplier Schedule Revision

After you have generated a supplier schedule that is based on the supplier contract information that you
have set up, you can use the Supplier Schedule Revisions program to review the schedule and make
revisions. After you review the schedule and make any necessary revisions, you can commit to a final
schedule.
Supplier Schedule Revisions enables you to:
• Review planned, committed, released, and historical quantity information.
Page 121 of 135

• Display the current supplier schedule.
• Review cumulative quantity information.
• Update planned and committed quantities in the schedule before you release them.
• Finalize the supplier schedule.
The system recalculates the quantities in the Cumulative Frozen, Cumulative Fabrication, and Cumulative
Raw Material fields when a change is made. If the schedule was generated multiple times, the values from
the previous generation are displayed in Previous columns. For each schedule record, the system displays
what kind of fence was defined, if any.
Any changes that you make to the schedule do not affect the most recent Master Production Scheduling
(MPS), MRP, or Distribution Requirements Planning (DRP) generation. After you release the supplier
schedule and create purchase orders for the blanket order releases, the next MPS, MRP, or DRP generation
treats the purchase orders as available supply items.
Self-Service Portal Workspaces

You can access the Supplier Schedule Revisions program using the self-service portal workspaces and to
review and revise the planned quantity. The supplier can also access the program using the supplier self-
service portal to enter the quantity that he or she wants to commit in response to the planned quantity. The
system compares the committed quantity that is entered by the supplier with the planned quantity and then
issues an alert if a shortage exists. Alerts are displayed on the self-service portal workspaces.
Prerequisites
Before you complete the tasks in this section, verify the information below:
• Set up supplier schedule master information.
• Create an active blanket order for the item, if necessary.
• Run the MPS/MRP/DRP generation so that the system can create order messages for supplier
scheduled items.
• Set the processing option if you want the Supplier Schedule Generation program (R34400) to
generate ad hoc schedules.
• Set the processing options to define the blanket order, order type, line type, and status in the version
of supply/demand inclusion rules that is used during supplier schedule generation.
Form Used to Revise Contract-Based Supplier Release Schedules

D
Vendor W3430 MRP Daily Operations Revise vendor schedules and

Schedule 1B (G3413), Enter/Change contract-based supplier release
Revisions Schedule schedules.
Generating Contract-Based Supplier Release Schedules

Select Single Site Periodic Planning Operations menu (G3422), Generate Supplier Schedule.
Setting Processing Options for Supplier Schedule Generation (R34400)

Defaults
These processing options control the generation start date and document type, and which version of the
supply/demand inclusion rules the system uses when you generate a supplier schedule.
Page 122 of 135

1. Generation Start Specify the date that the system uses to start the Supplier Schedule Generation
Date process. If you do not specify a date, the system uses the current date.
2. Document Type Specify the document type (user-defined code (UDC) 00/DT) that the system uses to
locate an item blanket order when you run the Supplier Schedule Generation program.
If you leave this processing option blank, the system uses document type OB (blanket
order).
3. Supply/Demand Specify which version of the supply/demand inclusion rules the system reads. This
Inclusion Rule rule defines the criteria that the program uses to select blanket orders to run the
supplier scheduling process.
Commitment
These processing options control whether and for what types of items suppliers are required to enter
commitments.
1. ABC code type Specify which ABC code type the system
uses when checking whether commitments
are required for an item. Values are:
Blank: Do not use ABC codes because no
commitments are required.
1: Use Sales - Inventory ABC codes.
2: Use Margin - Inventory ABC codes.
3: Use Investment - Inventory ABC codes.
2. Commitment required for Class A Items, 3. Commitment Specify whether commitments are required
required for Class B Items, 4. Commitment required for for class A, B, C, or D items. Values are:
Class C Items, and 5. Commitment required for Class D Blank: Not required.
Items
1: Required.
Ad Hoc Schedules
These processing options control whether the program creates ad hoc schedules and specify an end date for
generating ad hoc schedules.
1. Create Ad Specify whether the system generates ad hoc release schedules. Values are:
Hoc Schedule 0: Does not generate.
1: Generates.
2. End Ad Hoc Specify the end date for generating ad hoc schedules. If you do not specify a date, the
Schedule Date system generates ad hoc schedules for all planning messages that are available for the item
after the generation start date. You generate ad hoc schedules only if no valid vendor
schedule information was set up.
Process
These processing options control how the system clears messages and updates the schedule. In addition,
you can specify the manner in which the system uses messages.
1. Supplier Specify the schedule status after the system runs the Supplier Schedule Generation
Schedule Status program. If you leave this processing option blank, the system does not update the
schedule.
2. Clear Messages Specify whether the system clears MPS/MRP/DRP messages after it runs the Supplier
Schedule Generation program (R34410). Values are:
Blank: Does not clear messages.
1: Clears messages.
3. Regeneration Specify whether the system reruns the Supplier Schedule Generation program when
Flag the system uses previously cleared MPS/MRP/DRP messages. The system displays
messages only after the MRP Regeneration program has run. Values are:
Blank: Use cleared messages.
Page 123 of 135

1: Do not use cleared messages.
4. Frozen Days Flag Specify whether the system ignores the frozen time fence for supplier release and
enables normal operations within the frozen time fence. If the system ignores the frozen
time fence, it places quantities within the frozen time fence. Values are:
Blank: Do not ignore.
0: Ignore.
5. Transfer Order Specify whether the system ignores the transfer order messages while generating the
Messages Flag schedule. If the system ignores the transfer order messages, it schedules quantities
only for the purchase order messages. Values are:
Blank: Do not ignore.
0: Ignore.
Setting Processing Options for Supplier Schedules Revisions (P34301)

Versions
Enter the version for each program. If this processing option is left blank, version ZJDE0001 will be used for
1 through 7.
1. Open Order Inquiry (P4310) Specify a group of items that can be processed together such as reports,
business units, or subledgers.
2. Supply/Demand Inquiry Specify a sequence number that identifies versions of a menu selection.
(P4021) For example, where multiple versions of a report menu selection are set
up, this sequence number identifies each of those versions.
3. Purchase Order Entry (P4310) Specify a value.
You can set up multiple versions of certain menu selections (for example,
reports). This sequence number identifies each of those versions.
4. Vendor/Blanket Information Specify a group of items that can be processed together, such as reports,
(P4321) and 5. Pegging business units, or subledgers.
Information (P3412).
6. Supplier Schedule Release Specify the version to use.
Generation (R34410) This is the DREAM Writer version for fiscal and anniversary rollover. If a
version is entered, the rollover will occur automatically during the payroll
cycle. If the processing option is left blank, fiscal and anniversary
deductions, benefits, and accruals (DBAs) will have to be rolled over
manually using the menu selection.
7. Item Branch (P41026B) Specify a specific set of data selection and sequencing settings for the
application. You can name versions using any combination of alpha and
numeric characters.
8. Enter the version of Specify a UDC (40/RV) that identifies an inclusion rule that you want the
Supply/Demand Inclusion Rules system to use for this branch/plant. The Manufacturing and Warehouse
to use for active Blanket Order Management systems use inclusion rules in this way:
selection • For Manufacturing: Enables multiple versions of resource rules for
running MPS, MRP, or DRP.
• For Warehouse Management: Enables multiple versions of
inclusion rules for running putaway and picking.
The system processes only those order lines that match the
inclusion rule for a specified branch/plant.
9. Purchase Order Inquiry Self Specify the version of the Purchase Order Self-Service Inquiry program
Service (P4310SS) (P4310SS) that the system uses to display purchase order information. If
you leave this processing option blank, the system uses version
ZJDE0001.
Defaults
Page 124 of 135

These processing options specify the defaults that are used by the program.
Document Order Specify a UDC (00/DT) that identifies the type of document. This code also indicates the
Type origin of the transaction.
1. Enter the document type to filter on the form. Values are:
P: Accounts Payable documents
R: Accounts Receivable documents
T: Payroll documents
I: Inventory documents
O: Purchase Order Processing documents
J: General Accounting/Joint Interest Billing documents
S: Sales Order Processing documents
2. Supplier Self Specify whether to activate the supplier self-service feature in Java or HTML
Service environments. Values are:
Functionality Blank: The system does not activate supplier self-service.
1: Activate Supplier Self Service functionality for use in JAVA/HTML.
3. Item Cross- Specify the code with which the system searches cross-reference information using a
Reference Type supplier item number. Cross-references associate the internal item numbers with the
Code supplier's item numbers. You can set up items in the Item Master Information table
(F4101) and create the cross-reference information in the Item Cross Reference
Revisions program (P4104). You must enter a value that has been set up in UDC 41/DT.
If you leave this processing option blank, the system does not display or process any
cross-reference information.
4. Allow changes Specify whether to allow changes to the schedule. Values are:
to the schedule Blank: Allow changes to the schedule.
1: Do not allow changes to the schedule.
Note. The row for planned schedules is disabled when the value is 1. This processing
option is operational only when web mode is activated (Tab Defaults, Option 2).
Status Update
These processing options specify the statuses.
Vendor Enter Status for vendor schedule update. This is updated as the schedule moves through
Schedule the system.
Status
To Status Enter the status beyond which changes cannot be made to the vendor schedule. If this
processing option is left blank, the schedule will always be open to change. This is updated
as the schedule moves through the system.
Revising Supplier Schedules

Access the Vendor Schedule Revisions form.
Vendor Schedule Revisions form
As of Date Enter the promised shipment date for either a sales order or purchase order. The Supply
and Demand programs use this date to calculate available to promise information. This
value can be automatically calculated during sales order entry. This date represents the
day that the item can be shipped from the warehouse.
Planned QTY Enter the quantity of units that are planned for each period in the time series or plan.
(planned quantity)
Committed QTY Indicates the quantity that the vendor has committed to delivering in response to the
(committed planned quantity on the vendor schedule.
quantity)
Page 125 of 135

Entering Ad Hoc Schedules
This section provides an overview of ad hoc schedules and discusses how to:
• Set processing options for Ad Hoc Schedule Revisions (P34302).
• Enter ad hoc schedules.
Understanding Ad Hoc Schedules

If you do not have supplier information that is based on a blanket order, you can still perform supplier release
scheduling by creating ad hoc schedules. You can create an ad hoc schedule when the schedule quantities
have changed after regenerating the supplier schedule to fulfill additional requirements.
Ad hoc schedules are created for the supplier who is specified in the order message in the MPS/MRP/DRP
Message File table (F3411). During the MRP generation, the Supplier field on the message is populated from
the Item Branch File table (F4102) if a supplier was defined for the item. If you did not define a supplier for
the item, you can add a supplier to the message manually. If the message does not specify a supplier, the
system uses the split percentage that was set up for the item in the Supplier Schedule Master File table. If no
split was defined for the item, you cannot generate an ad hoc schedule.
There are two methods for creating ad hoc schedules:
• You can run the Supplier Schedule Generation program and set a processing option to create ad
hoc schedules for items for which no blanket orders exist.
• You can use the Ad Hoc Schedule Revisions program to enter ad hoc schedules manually—for
example, to meet unplanned demand.
You create ad hoc schedules based on item branch information, as well as supplier information that you can
set up independently from a blanket order. For example, you can set up shipment patterns and dates, as well
as split percentages for the suppliers.
When you use the Supplier Schedule Generation program to create a supplier release schedule and no
blanket order exists for the item, the system reads the MRP messages from the MPS/MRP/DRP Message
File table and searches for available supplier information—for example, a shipment pattern that is defined for
a supplier and an item. If the system locates a shipment pattern, it adjusts the MRP request date to the first
available shippable date, based on the shipment pattern. If you did not define shipment dates for the item,
the system uses the MRP message request date for scheduling.
The Ad Hoc Schedule Revisions program, which is accessible through the self-service portal workspaces,
can be used by both the buyer and the supplier. This program enables you to enter schedules even when no
MRP messages and no forecast exist for the item. The buyer can use this application for:
• Entering a new ad hoc schedule, for example, in response to an alert.
• Editing the planned quantity in an existing ad hoc schedule.
• Editing the committed quantity that is entered by the supplier on an ad hoc schedule.
Every time that a schedule changes, the system automatically notifies the supplier using email.
The buyer can use the application to respond to a new ad hoc schedule by entering a commitment quantity.
Schedules are displayed in chronological order, starting with the earliest date and displaying planned,
committed, and released quantities, as well as cumulative values and the difference between planned and
committed quantities.
Forms Used to Enter Ad Hoc Schedules

D
Add Ad Hoc W3430 EnterpriseOne Collaborative Portal, Ad Add ad hoc schedule.

Schedules 2E Hoc Schedule Advanced Search. The supplier enters
On Search For Ad Hoc Schedules, committed quantities.
Page 126 of 135

D
complete filter fields and click Find.

On View Ad Hoc Schedules, click Add
Record.
Edit Ad Hoc W3430 On View Ad Hoc Schedules, click Edit. Edit ad hoc schedules.
Schedules 2C
Setting Processing Options for Ad Hoc Schedule Revisions (P34302)

Defaults
These processing options control default settings, such as the item cross-reference type code.
1. Item Cross- Specify the code with which the system searches cross-reference information using a
Reference Type supplier item number. Cross-references associate the internal item numbers with the
Code supplier's item numbers. You can set up items in Item Master Information and create the
cross-reference information in the Item Cross Reference Revisions program. You must
enter a value that has been set up in UDC (41/DT). If you leave this processing option
blank, the system does not display or process any cross-reference information.
Specify whether to allow changes to the schedule. Values are:
Blank or 2: Allow changes to the schedule.
1: Do not allow changes to the schedule.
Note. The row for planned schedules is disabled when the value is 1. This processing
option is operational only when web mode is activated (Tab Defaults, Option 2).
Entering Ad Hoc Schedules

Access the Add Ad Hoc Schedules form.
Supplier Number Enter a number that identifies an entry in Address Book, such as employee, applicant,
participant, customer, supplier, tenant, or location.
Start Date Enter the start date for the order. You can enter this date manually, or have the system
calculate it using a backscheduling routine. The routine starts with the required date and
offsets the total lead time to calculate the appropriate start date.
Planned QTY Enter the quantity of units that are planned for each period in the time series or plan.
(planned quantity)
Committed QTY Indicates the quantity that the vendor has committed to delivering in response to the
(committed quantity) planned quantity on the vendor schedule.
Capturing Supplier Commitments

This section provides an overview of supplier collaboration and discusses how to:
• Enter supplier commitments for blanket schedules through the EnterpriseOne Collaborative Portal.
• Enter supplier commitments for ad hoc schedules.
• Capture supplier commitments using EDI.
Page 127 of 135

Understanding Supplier Collaboration
Collaboration between buyers, suppliers, and the EnterpriseOne planning systems is essential for
supporting e-fulfillment processes. The system provides self-service programs that enable both buyers and
suppliers to review and modify supplier schedules. By accessing these programs using the supplier self-
service portal and the buyer workspace, buyer and supplier can collaborate in real time. After you have
created a supplier schedule, the supplier can view it using the portal and respond to it by entering
commitments.
The collaborative process includes a set of alerts that makes managing supplier schedules by exception
possible. Under certain conditions, for example, if a mismatch exists between planned and committed
quantity, the system issues alerts to both buyer and supplier to enable them to respond to the issue. The
system captures a history of schedules and commitments that provides a basis for exception and
comparative alerts.
The portal also enables buyers not only to review and revise blanket and ad hoc schedules that are created
by running the Supplier Schedule Generation program, but also to manually enter ad hoc schedules when
necessary. You can use ad hoc schedules to meet unexpected demand or to cope with shortages.
To create ad hoc schedules, this information is required:
• Supplier
• Freeze fence
• Shipment dates
Commitments
After a supplier schedule is generated, based on MRP requirements and supplier information that is available
in the system and communicated to the supplier, the supplier can facilitate planning and the smooth flow of
orders and goods by creating commitments for the planned quantities on the supplier schedule.
Commitments do not represent an order, but an intent to meet the order.
Important! Commitments that are used for supplier release scheduling are different from the commitments
that are created and tracked in Procurement.
Depending on the needs of the business, you can specify whether you want suppliers to state their
commitments. You use the processing options for the Supplier Schedule Generation program to determine
commitments. You can specify that suppliers are not required to provide commitments in response to the
planned quantity that is communicated using the supplier schedule. In that case, the planned quantity
becomes the default value for the committed quantity when you run the schedule generation. If you want the
suppliers to respond to the supplier schedule with commitments, you can indicate the type or types of items
for which you require commitments, based on the ABC ranking that is assigned to an item in the Item Branch
program (P41026). For example, after specifying which type of inventory value you want to use, you can
indicate whether to make commitments for A, B, or C class items. ABC codes are used to categorize items
by their sales, margin, or investment inventory value.
When a schedule is generated for an item class that requires a commitment, the supplier is notified by email
and can enter committed quantities in the supplier self-service portal by using the Supplier Schedules
Revisions program or the Ad Hoc Schedule Revisions program.
Note. If you communicate with the supplier using EDI, the supplier can send committed quantities using EDI.
If you have specified that commitments are necessary, but the supplier does not specify a committed
quantity matching the planned quantity, the system issues an appropriate alert that, in most cases, is visible
to both buyer and supplier.
After the supplier has sent the committed quantity information, you can review the information in the self-
service programs. The commitments for blanket order-based schedules are stored in the Vendor Schedule
Commitment File table; the commitments for ad hoc schedules are stored in the Ad Hoc Vendor Schedule
File table. Committed quantities that are within the release fence (releasable days) are converted into
purchase orders when you run the Supplier Schedule Release Generation program. Committed quantities
that are scheduled outside the release fence remain committed.
Portal Alerts
Page 128 of 135

To facilitate the collaboration between buyer and supplier, the supplier release scheduling system provides
alerts. These alerts enable both the buyer and supplier to manage the schedule on an exception basis. Alerts
can be used if the supplier and buyer agree to use supplier commitments as part of the planning process.
The alerts that are displayed to the user describe conditions that deviate from the original plan and that might
require action on the part of the supplier or the buyer. You can specify how long the alerts are to be
displayed and how much time the supplier has to respond to the alert. The system also provides a count of
the number of the alerts that are displayed on the portal.
When either the buyer or supplier accesses the system by using the self-service portal workspaces, the
number of alerts is displayed on the portal form. Click any of the Alerts links to investigate and respond to the
alerts, and access the View Supplier Schedule form or the Ad Hoc Schedule form. If you use the Alerts link
to access these forms, only the schedules to which the alert applies are displayed.
The system currently provides six alerts. Four of these alerts apply to blanket order-based schedules; the
other two apply to ad hoc schedules. This table describes the conditions that generate alerts, as well as to
whom the alert is addressed:
Alert Condition Owner Schedule

Type
Commit not equal The committed quantity is not equal to the Buyer Blanket
to planned planned quantity.
Commit not equal The committed quantity is not equal to the Buyer Ad Hoc
to planned planned quantity.
No Commitment The supplier has not committed to the planned Buyer and Blanket
quantity within a specified number of days from supplier
the release fence.
No Commitment The supplier has not committed to the planned Buyer and Ad Hoc
quantity within a specified number of days from supplier
the release fence.
Commit not equal The supplier decreases the commitment from Buyer Blanket
to previous commit what was previously committed and does not only
meet the schedule quantity.
Planned not equal Indicates the number of schedule changes from Buyer and Blanket
to previous the previous planned schedule. supplier only
planned
Shortages
After the supplier release schedule is generated and commitments have been entered, the buyer or planner
can review the schedule to identify shortages, based on the alerts that the system has issued.
To cover any shortages, the buyer can negotiate with an alternative supplier, if one is available, on quantity,
price, and delivery. This negotiation occurs outside of the supplier release scheduling process. As a result,
the buyer can enter an ad hoc purchase order, if possible, within the MRP horizon. In this case, you can run
MRP again to recognize the quantity on the ad hoc purchase order. When you regenerate the supplier
release schedule, the planned quantity reflects the purchase order quantity.
Note. Running MRP again after creating an ad hoc purchase order to cover a shortage is not mandatory, but
it is recommended. If you do not run MRP again, the ad hoc purchase order quantity is not accounted for in
the supplier schedule generation process and has to be subtracted manually.
Another method for covering shortages is creating a blanket order for the alternative supplier, changing the
supplier split percentage to a fixed percentage for the new supplier, and then generating the supplier release
schedule again.
Page 129 of 135

See Also
Entering Purchase Orders
Forms Used to Capture Supplier Commitments

Name D
Edit W3430 EnterpriseOne Collaborative The buyer enters changes to the

Supplier 1B Portal, Blanket Schedule supplier schedule.
Schedule Advanced Search. The supplier uses this form to enter
On Search for Blanket commitments.
Schedules, click Find. When you click an alert link, the form
On View Blanket Schedules, displays only the schedule for which
click Edit. the alert was issued.
Click an Alert link on the
portal.
Edit Ad Hoc W3430 On View Ad Hoc Schedules, Make changes to the Ad Hoc schedule.
Schedules 2C click Edit. When you click an alert link, the form
Click an alert link on the displays only the schedule for which
portal. the alert was issued.
Entering Supplier Commitments for Blanket Schedules Through the

EnterpriseOne Collaborative Portal
Access the Edit Supplier Schedule form.
Entering Supplier Commitments for Ad Hoc Schedules

Access the Edit Ad Hoc Schedules form.
Capturing Supplier Commitments Using EDI

Communication of planned and committed quantities between buyers and suppliers can occur when you are
using EDI.
The EDI 830 standard establishes both the contents and the standardized format for the transaction set that
is required for a planning schedule with release capability. Using EDI 830 Planning Schedule with Release
Capability for supplier release scheduling in the software, you can perform these transactions:
• Send forecasts or supplier release schedules (both blanket order and ad hoc schedules) with
planned quantities outbound.
• Receive forecasts or supplier release schedules inbound.
The supplier can perform these transactions:
• Send back a response with the committed quantities.
• Send an inbound release schedule with planned quantities (both for blanket order and ad hoc
schedules).
These processes can be used to support business scenarios:
• The buyer sends a planning forecast that is for information only and conveys anticipated demand.
• The buyer sends a net rolling forecast to the supplier, supported by a blanket order that commits
resources to a stated time period.
The 862 Shipping Schedule transaction is sent as a separate release mechanism to support just-in-
time releases.
Page 130 of 135

• The buyer sends a material release schedule in the form of a net rolling forecast to the supplier,
supported by a blanket order that commits resources to a stated time period.
Firm requirements are identified as such and are released as soon as their dates fall within the
prenegotiated time frame. Requirements falling outside this window are considered planned with
resources committed, but not released.
• The buyer sends a planning schedule containing gross requirements, inventory levels, and minimum
and maximum inventory targets.
The supplier nets forecast data to determine shipping requirements, based on the buyer's inventory
levels and minimum and maximum targets.
According to the material release schedule scenario, which is the most typical for supplier release
scheduling, the buyer generates a material release schedule and sends it to the supplier. This schedule is
regenerated on a regular basis, factoring in all the changes from the previous run. The supplier uses the
material release schedule to plan for future orders from the buyer. If required, the supplier generates a
response to the material release schedule. The buyer evaluates any responses that are received and takes
appropriate action, for example, adjusting the schedule.
Using EDI to communicate planning forecasts and release schedules between buyer and supplier consists of
these processes:
• The planning schedule records are extracted from the F3430 table into the EDI Planning Schedule
Header - Outbound table (F47066) and the EDI Planning Schedule Detail - Outbound table (F47067)
by running the Outbound Extraction - Supplier program (R470621).
Whenever order number and type, company, suffix, line number item, or branch change, the system
creates a new document number within the same batch.
• For ad hoc schedules, the records are extracted from the Ad hoc Vendor Schedule File table into the
EDI 830 outbound tables by running the Outbound Extraction - Ad Hoc Supplier Release Schedules
program (R470622).
For each supplier within the same batch, the system creates a new document number. You can run
the universal batch engine (UBE) in proof and in final modes.
• The records in the EDI 830 outbound tables are translated into flat file format by running the EDI
Planning Schedule Extraction Conversion program (R47062C).
• When the supplier sends an EDI 830 Response (Planning Schedule with Release Capability)
indicating the committed quantity, it is received back into the system by running the Inbound Flat File
Conversion program (R47002C) that populates the EDI Planning Schedule Header - Inbound table
(F47061) and the EDI Planning Schedule Detail - Inbound table (F47062).
• Running the Inbound EDI Planning Schedule Edit/Create program (R47061) reads the records from
the EDI 830 inbound tables and updates the committed quantities in the following tables, if the
document represents a response to the schedule from the supplier.
 Vendor Schedule Commitment File.
 Ad Hoc Vendor Schedule File.
• Running the Inbound EDI Planning Schedule Edit/Create program reads the records from the EDI
830 inbound tables and updates the planned quantities in the following tables if the inbound
transaction is not a response to a planned quantity:
 Ad Hoc Vendor Schedule File.
 Vendor Schedule Quantity File.
You can view the results of this process in the Supplier Schedule Revisions program for blanket order-based
schedules and in the Ad Hoc Schedule Revisions program for ad hoc schedules.
Releasing Supplier Schedules

This section provides an overview of supplier schedule release generation, lists a prerequisite, and
discusses how to:
Page 131 of 135

• Run Supplier Schedule Release Generation.
• Set processing options for Supplier Schedule Release Generation (R34410).
Understanding Supplier Schedule Release Generation

After finalizing a schedule by using Supplier Schedule Revisions or Ad Hoc Schedule Revisions, you use the
Supplier Schedule Release Generation program to release the current supplier schedule. The release
process generates:
• Purchase orders for all committed quantities within the release fence.
• A shipping schedule that is based on when you need the items, the shipping lead time, and other
defined variables.
After the schedule is processed, the system updates the planned, committed, and released quantities on the
supplier schedule that are inside the time fence.
When you run the Supplier Schedule Release Generation program, the program releases both blanket order-
based schedules and ad hoc schedules, if any exist. It creates purchase orders for quantities matching the
committed quantities. Purchase orders are created only for committed quantities with dates that are inside
the release fence. Committed quantities outside the release fence remain committed. For schedules that are
based on blanket orders, the system uses the value from the Releasable Days field in the Supplier Schedule
Master Revisions program (P4321). After purchase orders are created, the Released Quantity field on the
vendor schedule is updated with the purchase order quantity.
For blanket order-based schedules, the program creates purchase orders against the blanket order and uses
the supplier schedule master information to create a release schedule. For ad hoc schedules, the purchase
orders are created using the version of the Purchase Orders program that you define in the processing
options.
In the process of generating release schedules, the program also consolidates the purchase orders. You can
use a processing option to determine what criteria the system uses for consolidation. By default, the program
consolidates purchase orders by branch, supplier, and item. However, you can also consolidate by branch
and supplier only, or by branch, supplier, and date. In this process, purchase orders that are created against
blanket orders and ad hoc schedules are merged.
Ad Hoc Schedules
When you run the Supplier Schedule Release Generation program for ad hoc schedules, you can use the
processing options to specify release fence days. To create purchase orders for ad hoc schedules, the
system searches for pricing blanket orders. If no pricing blanket orders are available, the system creates
independent purchase orders.
Prerequisite
Generate a current supplier schedule.
Running Supplier Schedule Release Generation

Select Single Site Periodic Planning Operations menu, Release Supplier Schedule.
Setting Processing Options for Supplier Schedule Release Generation

Defaults
These processing options control the version of the Purchase Orders program to use for creating purchase
orders, as well as the consolidation method for purchase orders and the release fence for ad hoc schedules.
1. Purchase Order Specify which version of the Purchase Orders program that the system calls to
Entry Version (P4310) generate purchase orders when running the Supplier Schedule Release Generation
program. If you leave this processing option blank, the system uses version
ZJDE0001.
Page 132 of 135

2. Purchase Order Specify how to consolidate purchase orders when you run the Supplier Schedule
Consolidation Release Generation program. Values are:
Blank: Consolidate purchase orders by branch/plant supplier and item.
1: Consolidate purchase orders by branch/plant and supplier.
2: Consolidate purchase orders by branch/plant, supplier, and date.
3. Release Fence Days Specify the release fence days for ad hoc schedules. Release fence days are the
for Ad hoc Schedules number of work days from the current date within which a release can occur.
Process
These options enable you to specify the processing that the system uses to generate the supplier schedule
release.
1. Supplier Specify the supplier schedule status that the system assigns after you run the Supplier
Schedule Schedule Release program.
Status If you leave this option blank, the system does not update the supplier schedule status.
2. Clear Specify whether to clear MPS/MRP/DRP messages after the system runs the Supplier
Messages Schedule Release program. Supplier scheduling uses the messages from the most recent
MRP generation to determine demand. The system clears only the messages that are inside
the release fence. Values are:
Blank: Does not clear messages.
1: Clears messages.
3. Blanket Specify whether the system automatically releases blanket orders during the Supplier
Order Release Schedule Release program. Values are:
Blank: Does not automatically release blanket orders.
1: Automatically releases blanket orders.
4. Price Specify whether the system retrieves the price from a blanket order or the Procurement Price
Control Management system. Values are:
Blank: Blanket order.
1: Procurement Price Management.
Appendix: EnterpriseOne Requirements Planning

Reports
This appendix provides an overview of EnterpriseOne Requirements Planning reports and enables you to:
• View summary tables of all reports.
• View details for selected reports.
EnterpriseOne Requirements Planning Reports

This product does not include many stand-alone reports.
EnterpriseOne Requirements Planning Reports: A to Z

This table lists the EnterpriseOne Requirements Planning reports, sorted alphanumerically by report ID.
Page 133 of 135

Report ID Description Navigation
and Report
Name
R34450 You can use Supplier Schedule Print to print Single Site Periodic Planning
Supplier a report of the supplier schedule. Operations (G3422), Print
Schedule Supplier Release
Print
R34460 You can use the Purge Supplier Schedule Single Site Periodic Planning
Supplier History program to delete history records Operations (G3422), Purge
Schedule that have become redundant. Supplier Schedule History
History
EnterpriseOne Selected Requirements Planning Reports

Some reports include a more detailed description, as well as information about processing options. These
reports are listed alphanumerically by report ID.
R34460 - Supplier Schedule History

EnterpriseOne provides a batch program that you can use to purge the supplier schedule history. You can
use the Purge Supplier Schedule History program to delete history records that have become redundant.
You can select to delete all of the history records in the Vendor Schedule History File table (F3440) or just a
subset of these records. It is recommended that you run this batch program periodically.
R34450 - Supplier Schedule Print

You can use Supplier Schedule Print to print a report of the supplier schedule. Run the Supplier Schedule
Release Generation (R34410) batch process. The system uses the information that you have entered on the
other forms to create the report. This program generates a consolidated report of both blanket and ad-hoc
schedules, and the purchase orders that the system generated. It displays planned committed and released
quantities, as well as the cumulative difference between planned and committed quantities.
Processing Options for Supplier Schedule Print

Process
Blanket Order Type Specify a UDC (00/DT) that identifies the type of document. This code also indicates the
origin of the transaction.
1. Enter the document type to use when retrieving an item's blanket order. If left blank,
OB will be used.
P: Accounts Payable
R: Accounts Receivable
T: Payroll
I: Inventory
O: Purchase Order Processing
J: General Accounting/Joint Interest Billing
S: Sales Order Processing
Supplier Schedule The current status of the supplier schedule. This is updated as the schedule moves
Status through the system.
2. Enter the status to use for updates to the supplier schedule. If left blank, no change
will be made to the schedule's current status.
Page 134 of 135

Versions
Supply/Demand Specify a UDC (40/RV) that identifies an inclusion rule that you want the system to
Inclusion Rules Version use for this branch/plant. Manufacturing and Warehouse Management use
inclusion rules as follows:
1. Enter the version of Supply/Demand Inclusion rules to use for active blanket
order selection.
• For Manufacturing: Allows multiple versions of resource rules for running
MPS, MRP, or DRP.
• For Warehouse Management: Allows multiple versions of inclusion rules
for running putaway and picking. The system processes only those order
lines that match the inclusion rule for a specified branch/plant.
Associated Text
Print Associated Blanket Specify the type of processing for an event.

Order Text 1. Enter a 1 to print associated blanket order text. If left blank, no associated
text will be printed
Page 135 of 135

MRP

Uploaded by

Copyright:

Available Formats

MRP

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MRP

Uploaded by

Copyright:

Available Formats

EnterpriseOne Requirements Planning Preface

This preface discusses:

About These PeopleBooks

Getting Started with EnterpriseOne Requirements

Requirements Planning Overview

Requirements Planning Integrations

Shop Floor Management

Sales Order Management

Requirements Planning Implementation

Global Implementation Steps

1. Set up global UDC tables. See EnterpriseOne Tools 8.95

2. Set up fiscal date patterns. See Setting Up Fiscal Date Patterns.

3. Set up companies. See Setting Up Companies.

4. Set up business units. See Setting Up Business Units.

5. Set up next numbers. See Setting Up Next Numbers.

8. Set up multicurrency processing, including currency See Understanding Multicurrency

12. Set up branch/plant constants. See Setting Up Inventory Constants.

13. Set up Manufacturing/Distribution Automatic • Setting Up AAIs in Distribution

14. Set up document types. See Setting Up Document Type

16. Set up manufacturing constants. See Setting Up Manufacturing

Requirements Planning Implementation Steps

2. Set up Inventory Management for See Setting Up Inventory Management for

3. Set up quantity type subsets. See Setting Up Quantity Type Subsets.

4. Set up capacity planning. • Determining Available Capacity

Understanding EnterpriseOne Requirements

Requirements Planning Overview

Requirements Planning Features

Resource and Capacity Planning

Material Planning Operations

Supplier Scheduling Systems

Requirements Planning Tables

Understanding Requirements Planning Concepts

Single-Facility versus Multifacility Planning

Single-Level versus Multilevel Planning

Master Production Scheduling and Material Requirements Planning

MPS and Manufactured Items

What Are the Differences Between MRP and MPS?

Requirements Planning Outputs

Quantity Types (34/QT)

Time Fences and the Time Series

MRP Period Calculations Using Planning Fence Rules

Sources of Demand Week 1 Week 2 Week 3 Week 4 Week 5 Week 6

Forecast 100 100 100 100 100 100

Sales Orders 300 200

PLO 300 100 100 100 100 100

Time Fence Rules for DRP, MRP, and MPS (34/TF)

Rul Description 1 Description 2 Uses

Rul Customer Whichever is Rule C is commonly used for make-to-order,

Rul Whichever is Forecast Rule G is the default.

Rul Customer Forecast Rule S is commonly used for make-to-order,

Time Series Calculations

Ending Available Calculation

Product Period Period Period Period Period Period Period Period

Cumulative Available to Promise Calculation

CATP Period Period Period Period Period Period Period Period

Message Types for DRP, MPS, MRP, and RCCP (34/MT)

Typ Descriptio Planner Work Order Purchase Order

A Warning WO missing part Displays work order. You can N/A

A Warning BOM does not Error message; record invalid. N/A

A Warning Cancel parts list. Error message; record invalid. N/A