This chapter provides an overview of refining supply planning details and discusses how to:
Refine plan definition details.
Review sourcing information details.
Refine manufacturing details.
Refine forecasting details.
Refine inventory details.
Refine order management details.
Refine production control parameters.
Refine purchasing details.
Perform mass maintenance.
This section provides an overview of items in PeopleSoft Supply Planning and discusses how to :
Review business unit details.
Maintain calendar details.
Maintain general item details.
Maintain item attribute information.
Maintain item forecast information.
Maintain quantity on hand information.
Maintain stocking period information.
PeopleSoft Supply Planning obtains all of the item information from the PL_BU_ITEMS table, which contains the combined data from the business unit item and the planning item definitions in the transaction system. PeopleSoft Supply Planning supports inventory items (configured and nonconfigured), planning items, and phantom items. The system includes items in a planning instance when the item is associated with one of the business units in the business unit group; when the item has a planned by option defined as a distribution, master, or material plan; when the item has a source code defined as make, buy, or planning; an when the item has a status defined as active, hold, or discontinue.
Inventory items include demand and supply transactions and quantities on hand in the planning instance. PeopleSoft Supply Planning obtains attributes for inventory items from the transaction system and stores the attributes with the planning instance on the PL_BU_ITEMS table. You can generate new planned supply for inventory items, as defined by the options that you defined for the item on the sourcing template.
The system obtains the quantity on hand for each inventory item during the Load Planning Instance process (PL_LOAD_OPT). PeopleSoft Supply Planning calculates quantity on hand by summing the quantity available, quantity reserved, staged inventory quantities (interface and staged item quantities), quarantined quantities, and quantities shipped but not depleted.
The system calculates quantity on hand for configured items for each instance of a configuration code and stores the code in the PL_BU_CFG_ITEMS table.
PeopleSoft Supply Planning generates planned transfers or purchase orders (POs) for configuration-coded items only if these are valid sourcing options for the configurable item. The system assumes that you ran the Submit Production Request process (CP_PRDN_RQST ) to generate the configured production supply prior to running the Load Planning Instance process.
Planning items are noninventoried items used to define families for forecasting. Planning items cannot have individual transactions and do not use quantity on hand. PeopleSoft Supply Planning allocates forecasts for planning items to components of the planning items as defined on the item's planning bill of material (BOM).
Phantom items are built but rarely stocked before they are used in the manufacturing process. In PeopleSoft Supply Planning, supply and demand transactions can exist with quantity on hand for phantom items. PeopleSoft Supply Planning explodes a phantom item BOM when the phantom item exists as a component on another BOM. If supply and demand exist directly for the phantom item, PeopleSoft Supply Planning nets the requirements and generates supply for the phantom item as necessary, using the sourcing template options that you defined for the phantom item.
Access the Review Business Units page.
Primary |
Select to indicate that the associated business unit is defined in the business unit group. The Load Planning Instance process includes business units needed for transfer order relationships that are not specifically defined in the business unit group. The Load Planning Instance process does not load items for non-primary business units into the planning instance. |
Reverse Quarantine Quantity |
Select to indicate that on-hold quantities are considered part of the quantity on hand. |
Always Open for Shipping |
Select to indicate that no closure calendars exist for shipping and the business unit can ship on all of the days and at all times. PeopleSoft Supply Planning does not create a corresponding shipping calendar in the planning instance when you select this option. |
Available Inventory Balances |
Select to indicate that the planning instance includes inventory balances from the transaction system. If this option is not selected, the system sets all of the quantity on-hand values in the planning instance for the item and business unit combination to zero. |
Always Open for Receiving |
Select to indicate that no closure calendars exist for receiving and that the business unit can receive on all of the days and at all times. When you select this option, PeopleSoft Supply Planning does not create a corresponding receiving calendar in the planning instance. |
Manufacturing Business Unit |
If selected, indicates that the associated business unit is used for production. |
Calendar Code |
Displays the manufacturing calendar for the business unit |
Round Component Demand |
Select to round the component demand when generating planned orders. |
BOM Explosion Date |
Indicates whether the production components added to an order are based on the production start or end date. |
Allow Substitution |
Select to indicate that the solvers can fulfill the production component demand of an item with the available supply of a defined substitute. |
Create Substitute Supply |
Select to indicate that the solvers can create new supply for substitute components to resolve constraints. If you do not select this option, the substitute algorithm can use on-hand quantities only. This option is available only when you select Allow Substitution for the business unit. |
Check Substitute First |
Select to indicate that the solvers can attempt to use substitute components before using alternate sourcing options. If you do not select this option, the solver checks alternate sourcing options before using substitutes to resolve a constraint failure. This option is available only when you select Allow Substitution for the business unit. |
Access the Review Business Unit Calendars page.
Select to indicate that no closure calendars exist for shipping, and the business unit can ship on all of the days and at all times. PeopleSoft Supply Planning does not create a corresponding shipping calendar in the planning instance when you select this option. |
|
Select to indicate that no closure calendars exist for receiving and that the business unit can receive on all of the days and at all times. When you select this option, PeopleSoft Supply Planning does not create a corresponding receiving calendar in the planning instance. |
Access the Calendars page, which displays the times open or available per day.
The yellow calendar day indicates the current date. Grey calendar days fall outside of the month that currently appears.
Click the date on any calendar day to access the Daily Calendar page, where you can change, add, and delete calendar times.
Access the Items page.
Item Early Fence Date |
Enter a value that falls between the planning instance start and end dates. This field is required. |
Planned By |
Displays the planned-by value defined in the transaction system item definition. |
Standard UOM (standard unit of measure) |
Displays the item's standard UOM defined in the transaction system. The system displays all of the quantities in PeopleSoft Supply Planning in the item's standard UOM. |
Fixed Period (days) |
Displays the number of days that the system looks ahead for demand when determining the amount of supply covered by an order. |
Low Level Code |
A number that identifies the lowest level in the supply chain at which a particular item appears. The system does not calculate net requirements for a given item until all of the gross requirements have been calculated down to that level. The system assigns a low level code of -1 to indicate that the low-level code has not been calculated and -999 to indicate the low-level coder could not be calculated. You can calculate low-level codes when running the solvers. |
Planning Item Precision |
Represents the decimal precision for quantities in the standard UOM. |
Reference Routing Item |
Displays the item whose production routing the system uses when generating new planned production. |
Average Order Quantity |
Displays the average order quantity defined in the transaction system, often represented by the batch or lot size used to supply the item. The Enterprise solver uses this value to calculate average lead times when evaluating new production. |
Inventory Item |
Select to indicate that this item is a finished good, a component of a manufactured assembly, a subassembly, buildable inventory, a purchased component, or a raw material. |
Phantom Item |
Select to indicate that the associated item is a phantom item. The system uses these items to drive demand straight through the phantom to the BOM components, which eventually become inventory items. Phantom items can have quantity on hand and individual transactions for supply and demand. |
Phase-Out |
Select to indicate that the item is being discontinued. The system displays a discontinuation date when you select this option. It plans no further supply for an item beyond this date. |
Lot for Lot |
Select to indicate that the item has no order modifiers. Solvers attempt pegging and quantity matching between demands and supplies when you select this option. |
Configuration Code Generation |
Select to indicate that the item is tracked using individual configuration codes. Balances and individual supply and demand display specific configuration codes. |
Rounding Rule |
Displays the rounding method that the system applies to calculations not involving yield. |
Access the Items - Attributes page.
Buyer |
Displays the primary buyer for the item. The system uses this default hierarchy when selecting a value:
|
Access the Items - Forecast page.
Demand Fence Date |
A time fence before which the forecast demand for the item is not considered (or consumed) by the planning engine. Any value that you enter must fall between the planning instance start and end dates. This is a required field. Solvers consider only actual orders as demand before this fence. |
Forecast Fulfillment Size |
Displays the standard quantity used to break large forecast demand into smaller forecast tasks. When the forecast demand of a planning period cannot be met completely, the planning engine determines which smaller forecast tasks can be delayed or canceled, thereby satisfying part of the forecast demand while maintaining plan feasibility. If you do not define this value (or use the default value 0), the system creates a single forecast task for the forecast demand of the item in that planning period. |
Forecast Priority Rank |
Displays a numeric value ranging from 1 (highest priority) to 999 (lowest priority) used by the planning engine to determine the order in fulfilling various independent demands, which include forecast demand. The priority 0 is reserved for the system. Note. You cannot enter the value 0 in the Forecast Priority Rank field. |
Forecast Adjustment Action |
Displays the adjustment method used by forecast consumption when allocating forecasts from larger periods (typically, forecasts from PeopleSoft Demand Planning) to smaller periods (typically, planning periods used in PeopleSoft Supply Planning). The system uses No Adjustment as the default value. |
Weight Profile |
Displays the PeopleSoft Demand Planning weight profile that the system uses to convert the forecast periods in PeopleSoft Demand Planning into daily intervals for establishing the forecast buckets in PeopleSoft Supply Planning. The Load Planning Instance process will assign a default weight profile if Demand Planning is not used or a weight profile is not defined in Demand Planning. |
Explode Demand for Consumption |
Select to indicate that the system explodes sales order demand or transfer demand through lower levels for the item for forecast consumption. |
Aggregate Demand |
Select to identify the item as representing a group of items for forecast consumption. For an aggregate demand item, you establish aggregate demand children. The forecast for the aggregate demand children is rolled up to one demand total for the aggregate demand item. Forecast consumption is then performed at the aggregate-item level rather than at the individual-item level. You can identify both planning items and inventory items as aggregate demand items. |
Forecast Consumption Method |
Identify which demands are included in forecast consumption. |
Access the Items - Quantity On Hand page.
Base Currency |
Displays the currency of the planning instance. Define the base currency of a planning instance on the Load Planning Instance - General page. |
Unit Cost |
Displays an item's primary ledger unit cost converted into the base currency of the planning instance. |
Quantity on Hand Date/Time |
Displays the date and time at which the quantity fields were populated during the Load Planning Instance process. |
Quantity Available |
The business unit's quantity available, which represents a subset of the quantity on hand, reflecting the total item quantity that can be used to fulfill demand. If soft reservations processing is in effect for the item, the Quantity Available field contains the total item quantity that can be reserved for orders by the Material Reservations process (INPLDMND), or through the Material Stock Reservations component. If soft reservations processing is not in effect, this field reflects the total item quantity you can include on push picking plans or confirmed as picked by the Picking Confirmation process (INPBCONF). Once quantity is soft reserved for the business unit or allocated from a specific storage location, the quantity available for the business unit is decreased and the quantity reserved is increased. |
Quantity Reserved |
If soft reservations processing is selected, this field represents the total item quantity reserved or hard allocated for all demand lines within the business unit that have not yet been depleted. If soft reservations is not selected, this field represents the total quantity allocated from specific storage locations for all demand lines in the business unit that have been confirmed but not yet depleted. The Quantity Reserved field value also includes nettable, available WIP quantity, regardless of whether soft reservation processing is in effect. |
Staged Interface Quantity |
Displays the quantity received, but not staged for putaway in inventory. |
Staged Item Quantity |
Displays the quantity staged but not putaway. |
Quarantine Quantity |
Displays the quantities in storage areas that are on hold or restricted. The Load Planning Instance process populates this value only if the you selected the Reverse Quarantine Quantity option for the business unit. |
Shipped Not Depleted Quantity |
Displays the quantity which has been recorded as shipped but has not been physically depleted from the item's inventory balance. |
Inventory Quantity On Hand |
Displays the sum of the quantity available, the quantity reserved, the staged interface quantity, the staged item quantity, and the quarantine quantity, minus the shipped not depleted quantity. |
Overridden |
Select to indicate that the quantity on hand was manually overridden in the planning instance. |
Reset |
If you change the inventory quantity on hand, click to reset the quantity on hand to its original value. |
Projected Useup Quantity On Hand |
Displays a phase-out item's remaining quantity on hand at the useup date. Note. This option is only available if the item has an affiliated phase-out attribute. |
Access the Items - Stocking Periods page.
Start Date and End Date |
Defines the period for which the corresponding safety and excess stock information are established in PeopleSoft Supply Planning. |
Safety Limit |
Displays the minimum quantity on hand you want to maintain to satisfy unexpected requirements. |
Excess Limit |
Displays the maximum quantity on hand you want to maintain to satisfy unexpected requirements. Any value that you enter in this field must be greater than the value defined in the Safety Limit field. |
This section discusses how to:
Review sourcing templates.
Review business unit and item-specific transfer options.
Review production options.
Review purchasing options.
Maximum Order Quantity |
Displays the maximum quantity when creating new planned supplies. |
Minimum Order Quantity |
Displays the minimum quantity when creating new planned supplies. |
Order Multiple |
Displays the incremental quantity when creating new planned supplies. |
Access the Review Sourcing Templates page.
Common Information
Default |
The system uses a default option to source demand when the planning engine cannot select other sourcing options because of capacity or material shortages. The Material solver uses the default option only when generating planned supply. Define at least one sourcing option as the default. |
Priority |
Displays the sourcing priority and sequence used by the Material and Capacity Feasible and Enterprise solvers. |
Option Type |
Displays whether the demand is supplied by a production order, purchase order, or by a transfer order. |
Sourcing Tab
Select the Sourcing tab.
Minimum Quantity |
When specified, identifies a minimum individual demand quantity that must be met before considering the related sourcing option. If the demand is greater than or equal to the minimum quantity specified, the system uses the sourcing option to generate the necessary supply. If the demand quantity is less than the minimum, the system does not consider the sourcing option a valid sourcing option. |
Maximum Quantity |
When specified, identifies a maximum individual demand quantity that is to be considered for the related sourcing option. If the demand quantity is less than or equal to the maximum quantity specified, the system uses the sourcing option to generate the necessary supply. If the demand quantity is greater than the maximum, the system does not consider the sourcing option a valid sourcing option. |
Production Tab
Select the Production tab.
BOM(bill of material) |
Displays the BOM identifier for the production option in the template. Production options can be predefined or created based on defaults specified at the item attributes by unit level. |
Routing |
Displays the routing identifier for the production option in the template. This column is empty if you are not using routings. |
Associated Primary BOM(associated primary bill of material) |
For all of the secondary co-products, displays the primary co-product for which the BOM or routing exists. When an item is a co-product on multiple primary BOMs, then one of the primary co-products must be assigned as an associated primary BOM. The system uses the production option for the associated primary to generate supply for the secondary co-products. |
Purchase Tab
Select the Purchase tab.
Vendor SetID |
Displays the setID under which you define the vendor and purchasing information. |
Vendor ID |
Displays the vendor ID for the purchase option. |
Vendor Name |
Displays the vendor name for the vendor ID on the purchase option. |
Vendor Location |
Displays the vendor location used to create the purchase option. |
Buyer |
Displays the buyer ID associated with the purchase option vendor. Solvers assign this buyer when creating new planned purchases. If this buyer is blank, the solver assigns the primary buyer associated with the item. |
Transfer Tab
Select the Transfer tab.
Source BU (source business unit) |
Displays the business unit that supplies the item. |
Ship Via |
Displays the method used for shipping the item. |
Access the Review Business Unit Transfer Options or the Review Item Transfer Options page, as appropriate.
Note. You cannot add transfer options on this page.
Note. Unit-level transfer options are valid only for items defined with Distribution as the planned by value.
Ship Via Code |
Displays the method shipping the item. |
Intransit Days |
Displays the number of days required to transport completed units from one operation to the next. |
Intransit Hours |
Displays the number of hours required to transport completed units from one operation to the next. |
Transfer Yield |
Displays the usable output from the transfer. Expressed as a percentage, the transfer yield is used in PeopleSoft Supply Planning to inflate the planned quantity on transfers to account for any loss that occurs during transport. |
Access the Review Production Options page.
Production Type |
Production options in PeopleSoft Supply Planning are always defined asProduction. Rework and teardown production orders are visible to PeopleSoft Supply Planning but you cannot create new production of these types. |
BOM Code |
Displays the BOM identifier for the production option in the template. Production options can be predefined or created based on defaults specified at the item attributes by unit level. |
BOM Quantity |
Displays the BOM quantity used for scaling component QPA's for single output BOMs or the expected batch quantity expected for multiple output BOMs. |
Routing Code |
Displays the routing identifier for the production option in the template. If the corresponding item uses lead time instead of production routings, the system does not populate this field with a value. |
Fixed Lead Time |
Displays the item's fixed lead time when generating planned orders without routings. |
Variable Lead Time |
Displays an item's variable lead time when generating planned orders without routings.
|
Use Lead Time |
If selected, the associated item uses the fixed or variable lead times (instead of production routings) to schedule start and due dates for production. |
Expected Yield % (expected yield percentage) |
Displays the expected cumulative yield for the production order. PeopleSoft Supply Planning uses yield to inflate the starting quantity of production to account for loss that occurs during the manufacturing process. |
Effectivity Dates |
Displays the effectivity dates of the production option if the item is production option-controlled. |
Access the Review Purchase Options page.
Lead Time Days |
Displays the purchasing lead time specified for the vendor or item and vendor relationship. This value represents the amount of time it takes to get inventory from the vendor. |
Purchase Yield |
Defines the usable output from the purchase. The value is expressed as a percentage. Purchase yield is used in planning to inflate the planned quantity on purchases to account for any loss that may occur during the purchase process. |
This section provides an overview of work centers and discusses how to:
Update work centers.
Review BOM component information.
Review BOM output information.
Review BOM substitute information.
Review routing production information.
Review routing scheduling information.
Review routing time information.
A work center can consist of one or more people and machines and can represent a logical grouping of machines, a department, or a cost center. You can assign each operation or task on a routing to a work center in which the operation or task takes place. Additionally, you can assign one or more resources (crew, machine, or tool) to each work center.
Define work center types by time or by unit. For work center types that you define by time, solvers plan capacity based on the amount of time available as defined on the appropriate manufacturing calendar. For work center types that you define by unit, solvers plan capacity based on the amount of units that can be produced at the work center as defined by the capacity multiplier definition on the work center itself.
You can associate work centers with a calendar to calculate capacity. If you do not associate a calendar with a work center, PeopleSoft Supply Planning uses the calendar on the work center's business unit for all of the calculations.
Consider:
PeopleSoft Supply Planning defines capacity as 0 prior to the current time; no capacity is available before the current time.
A specific work center is associated with a routing operation step.
When you create a production operation, the system calculates required capacity and the work center usage is subtracted from the corresponding capacity bucket for the work center.
Solvers record a violation if the work center capacity is exceeded for a given capacity bucket.
For partially completed operations, PeopleSoft Supply planning calculates the capacity requirement with the remaining quantity, using a new start time based on the duration for the remaining quantity and the actual end time.
Rate parameters exist on the operation.
Values are Setup, Fixed, Run, Post Production and In Transit. PeopleSoft Supply Planning always includes setup in the lead time calculation for the first operation. You can elect to ignore setup, however, for all of the remaining operations. Lead time calculation for a production operation is:
Intransit time for the previous operation (excluded for the first operation) + setup time (if you selected the Include Setup option) + fixed run + run rate * quantity.
Work center usage start time is equal to the production operation start time. The duration of work center usage includes any post production time. The system uses the work center calendar for the calculation of the duration and adds post production time to the production end time.
Capacity multipliers are effective-dated, and can vary over a period of time. Calendar periods used in all of the capacity calculations consider legal time only—the working period in the calendar—based on the bucket size:
Daily = 24 hours.
Weekly = 7 days (starting from Sunday).
Monthly = the number of days in the corresponding month.
PeopleSoft Supply Planning calculates an initial capacity profile for all of the buckets from start of time to the end of time. For example, suppose that the period start date is September 8, 2003 (a Monday), and you define the bucket size as Weekly, the next period would begin on the following Sunday, September 14, 2003. Consider that you defined two capacity multipliers as September 1, 2003 until September 11, 2003, and from then on for the remaining time. The bucket from September 8, 2003 to September 12, 2003 (assuming a calendar week of five days) contains two varying capacity multipliers—one from September 8, 2003 to September 10, 2003 and another from September 11, 2003 to September 12, 2003.
PeopleSoft Supply Planning calculates the capacity when you create the resource as:
For work centers defined as By Time:
Available Capacity = duration of a period in hours * capacity multiplier effective during the period * available percentage.
The duration of a period in hours includes the legal calendar period only.
For work centers defined as By Unit:
Available Capacity = capacity from above / total number of hours in the period, specified by the bucket size.
The total number of hours for a daily bucket is 24. The total number of hours in the weekly bucket (7 days) is 7 * 24 hours. The total number of hours for a monthly bucket varies based on the number of days for the period. A utility function in PeopleSoft Supply Planning calculates the number of hours for the month.
In this example, the calculation for a work center defined as By Time is:
Calendar is Monday to Friday, 8 a.m. to 4 p.m.
Number of hours/day = 8 hours.
Capacity multiplier of 1 is effective until September 11, 2003. A Capacity Multiplier of 2 is effective afterward. Duration of hours from September 8, 2003 to September 10, 2003 is calculated as 8 hours/day * 3 days = 24 hours.
Duration of hours from September 11, 2003 to September 12, 2003 is 8 hours/day * 2 days = 16 hours.
The capacity in the bucket from September 8, 2003 to September 12, 2003 is 24 hours * 1 * availability percentage + 16 hours * 2 * availability percentage.
See Also
Maintaining Bills and Routings
BOM Type |
Only production BOM types defined are visible in PeopleSoft Supply Planning. Rework and teardown BOM types are not used to create new supply. |
BOM Quantity |
When BOMs contain a single item output, the BOM quantity acts as a scaling device that enables you to enter a product structure when the end item's specifications are in a base greater than 1 unit. When BOMs contain multiple outputs, if a primary item and co-products are specified as output items on the BOM, the BOM quantity represents the expected batch quantity for the order. Typically, this quantity matches the primary item's average order quantity. |
Effective Date and Obsolete Date |
Displays the effective and obsolete dates for the components on a BOM. |
Operation Sequence |
Indicates where in the manufacturing process you need the component. The operation sequence refers to an operation on the assembly item's routing. The default operation sequence is 0, which is the first operation of the manufacturing process. Define operation sequence on the item's routing by using the Routing Definition Summary page. If you set the operation sequence for all of the items to 0, the system assumes that all of the component items are needed at the beginning of production and therefore need to be issued at the start of the first operation. |
Routing Type |
Only those routing types defined as production types are visible to PeopleSoft Supply Planning. See Structuring Routings. |
Routing Code |
Displays the routing identifier for the production option in the template. If the corresponding item uses lead time instead of production routings, the system does not populate this field with a value. The system reserves a routing code of 1 for an item's primary production routing and uses it as the default routing for planning and costing (in PeopleSoft Supply Planning, PeopleSoft Cost Management and PeopleSoft Production Management) including production conversion cost calculations. |
Expected Yield |
Displays the cumulative expected yield for the entire order. PeopleSoft Supply Planning stores this value at the production header level. |
Subcontracted |
Select to indicate that the task is a subcontracted operation. |
Work Center |
The work center associated with the corresponding operation. Click the work center ID to access the Work Center page, where you can review and maintain work center details associated with the planning instance. |
Access the Work Centers page.
Resource Name |
Displays the code and description of a specific work center. |
Indicates whether you have defined the work center as an aggregate resource by time or an aggregate resource by unit.
|
|
Bucket Size |
Displays the summation period over which you are aggregating capacity. Monthly buckets start on the first of the month and weekly buckets start on a Sunday. |
Allocation Strategy |
Displays the method that you use to spread the time and unit capacities when the operation crosses multiple buckets. Values are Start, Finish, and Proportion. For example, suppose that a task is stretched across two or more buckets, you might place the task capacity in its entirety in the first bucket, the last bucket, or spread the task capacity proportionally across all of the buckets. Note. Work center types that you define as By Time can use the Proportion allocation strategy only. |
Availability % (availability percentage) |
Displays the percentage of the total capacity time that the resource is available for use. The percentage might include scheduled maintenance or a buffer for unexpected repairs. The availability percentage is used to factor the available capacity for the entire planning horizon. |
Calendar Code |
Displays the run time calendar for the work center. You can associate a calendar code with the work center. If you use a production calendar, as opposed to a five-day work week definition, define at least one calendar code and the associated calendar on the Calendar Code Definition page. |
Ignore Violations |
Select this option to enable a solver to report over-capacity work centers, but not repair them during the capacity phases during the solver process. You can select this option for noncritical work centers to enable the solvers to ignore these work centers and focus on critical work centers for capacity repair. |
Average Daily Hours |
Displays the average number of hours that the work center is in operation each day. This field determines the operation's setup, fixed run, run rates, and post production times in hours, when the time unit for an operation is expressed in days for planning and costing purposes. For example, suppose that you set the run rate for an operation to 100 units per day and the work center's average daily hours to 8 hours, the system converts this to 100 units per 8 hours. |
The system uses these fields to determine the available capacity on a work center. Using effective dates, you can vary the work center's available capacity over time. If you define the work center as an aggregate resource by time, the system uses the capacity multiplier to represent the number of identical work centers that exist for scheduling purposes. For example, suppose that you define a work center as an aggregate resource by time with weekly buckets, and it has a capacity multiplier of 2, with an effective date of March 5, 2002. Beginning on March 5, 2002, PeopleSoft Supply Planning views this aggregate resource as two identical work centers that it can use simultaneously for jobs. If the work center has 40 hours of available calendar time in a weekly bucket, then the available capacity for the bucket, based on a capacity multiplier of 2, is 80 hours total. PeopleSoft Supply Planning uses this capacity multiplier to determine the work center's available capacity until the next capacity multiplier becomes effective. If you define the work center as an aggregate resource by unit, the system uses the capacity units to represent the number of units that can be produced on that work center in an entire bucket (assuming a 24 hours per day, 7 days per week calendar during the entire bucket). For example, suppose that you define a work center as an aggregate resource by unit with weekly buckets. This resource has capacity units of 100 with an effective date of April 10, 2002. Beginning on April 10, 2002, PeopleSoft Supply Planning views this work center as being capable of producing 100 units per week, based on a 24-hour per day, 7 days per week calendar. The actual available capacity on this work center is then calculated by factoring in the actual production calendar during each weekly bucket. If the work center has 40 hours of available calendar time in a weekly bucket, then the available capacity for the bucket, based on a capacity unit of 100, would be (100 units * 40 hours per week) / (24 hours per day * 7 days per week) = 24 units. PeopleSoft Supply Planning uses these capacity units to determine the work center's available capacity until the next capacity multiplier becomes effective. |
Access the Review Bills of Material - Components page.
Details Tab
Select the Details tab.
Yield |
Displays the expected percentage of usable components in a batch of components issued to production. A 100 percent yield assumes that the entire quantity of the component is usable and none are to be scrapped. The system considers component yield in the PeopleSoft Supply Planning to inflate component requirements to account for the expected loss during the assembly process. When scheduling the number of components to be used in production, the system divides the required quantity by the component yield value to derive the scheduled quantity. For example, suppose that an assembly has a demand of 100 units and the quantity per assembly is 1 with a component yield of 90 percent, then planning requires 111 components (100/.90). If the expected 10 percent yield loss occurs, 11 components (111x.10) are unusable, leaving you with the original required 100 components. When calculating the cost of the assembly, the system includes the component yield loss, thereby increasing the cost contribution of the component. |
Substitutes Exist |
Indicates whether you have defined substitutes on the BOM for this component item. You can review substitute information on the Substitutes tab. |
Access the Review Bills of Material - Outputs page.
Output Type |
Displays the type of output associated with the BOM. Output types include Primary, Co-product, Recycle, Teardown, and Waste.
|
Access the Review Bills of Material - Substitutes page.
Priority |
Displays the substitute item's priority relative to other substitute options. The planning engine considers substitute items with the highest priority (the lowest number) first. |
Substitute Item ID |
Displays the unique substitute item for the item. When you define substitutes for items on the Manufacturing BOMs - Components: Substitutes page, PeopleSoft Supply Planning automatically selects these substitutes when the quantity on hand for discontinued items run out. If you do not define substitutes for items designated as discontinued, a shortage of that item might occur if demand exceeds the existing quantity on hand. See Maintaining BOMs. |
From Date and To Date |
Displays the start and end date to indicate when the substitution is valid. |
Rate |
Indicates the quantity of the substitute item required to replace the original item in the item's standard UOM. The conversion rate can be different at the setID, business unit, and BOM levels. |
Access the Review Routings - Routings page.
Continuous Scheduling |
Select to complete the corresponding operation in a single run of continuous valid calendar time, with no down time. |
Ignore Capacity |
Select to prevent solvers from checking the corresponding operation for capacity violations. |
Operation Yield % (operation yield percentage) |
Displays a percentage of the quantity of goods expected to make it through the operation. In many manufacturing processes, parent items (subassemblies, primary items, or final assemblies) are lost during manufacturing. This loss manifests itself as assembly scrap, which can be due to breakage, poor quality, or nonconformance to specifications. Use operation yield percentage to incorporate expected loss into the cost of the usable end items. Additionally, PeopleSoft Supply Planning can use the process yield to increment the demand by calculating the additional resources necessary to meet the scheduled quantity with the anticipated yield loss. |
Access the Review Routings - Resources page.
Crew Size |
Displays the number of people in a given crew for the operation |
Machine Resources |
Displays the number of machines used at the operation. |
Resource Type |
Displays the type of resource used. Valid resources are primary or alternate machine, crew, or tool. |
Crew/Machine/Tool |
Displays the machine, crew, or tool code, as well as the description. |
Status |
Displays the availability of a resource for this work center. |
Quantity Used |
Displays the number of tools used at the operation. This option applies to tools only. |
Priority |
Displays the relative priority between alternate resources. The lowest number represents the highest priority. |
Access the Review Routings - Scheduling page.
Intensity |
This value appears by default from the task and determines the basis of the scheduling. Values are: Labor Time: The start and due date of the operation can be based on the operation's labor time (labor intensive). Machine Time: The start and due date of the operation can be based on the operation's machine time (machine intensive). Longest: The start and due date can be based on the longest of the two times, evaluated for each time type in the operation. For example, suppose that labor setup is 7 minutes, machine setup is 10 minutes, labor run is 20 minutes, machine run is 25 minutes, labor fixed run is 11 minutes, and machine fixed run is 7 minutes, the total operation time would be machine setup (10) + machine run (25) + labor fixed run (11) = 36 minutes. Cumulative: The start and due date can also be based on the sum of the machine and labor time. |
Indicates whether a subsequent operation can begin prior to the completion of the prior operation. Values are:
|
Access the Review Routings - Times page.
Operation Time |
Use in conjunction with the time unit, defines the amount of time to complete one unit. |
Time Unit |
Displays the unit of time for the corresponding operation time. For example, suppose that 5 is the value that appears in the Operation Time field and Days is the value that appears in the Time Unit field. Then the operation completes one unit every five days. The system determines the number of hours in a day by the work center's average daily hours, defined on the Work Center Definition page. See Structuring Routings. |
Operation Rate |
Use in conjunction with the rate unit. Defines the rate at which operations are completed. |
Rate Unit |
Displays the unit of time for the corresponding operation rate. For example, suppose that 3 is the value that appears in the Operation Rate field, and Units/Day is the value that appears in the Rate Unit field. The operation completes three units every day. |
Include Setup |
Select to indicate that the system considers setup in the operation lead time calculation. If you elected to include setup, the setup time is factored into the task or operation's lead time. The system always considers setup in the lead time calculation of the first operation, if setup is specified, regardless of the check box setting. This option applies only to Planning Labor Setup and Planning Machine Setup operation types. If this option is not selected, setup can begin prior to any production units arriving at the work center. The system assumes that setup can occur at any time after the start of production and does not include it as part of the item's lead time, except at the first operation. |
This section discusses how to:
Review planning BOMs.
Review aggregate demand items.
Review demand calendar weights.
Maintain actual forecasts.
Maintain net forecasts.
Access the Review Planning BOMs page.
BOM Quantity |
BOM quantities enable you to enter product structures when the end item's specifications are in a base greater than one unit.
|
Effective Date and Obsolete Date |
Displays the effective and obsolete dates for the components on the planning BOM. The system explodes to components only those forecasts that are in effect during this date range. |
Access the Actual Forecasts page.
Percentage Multiplier |
Displays the percentage to increase or decrease all of the forecast quantities that appear in the forecast schedule. Percentage multipliers greater than 100 increase the forecast quantities; percentage multipliers less than 100 decrease the forecast quantities. |
Calculate |
Click to apply the percentage multiplier. All of the forecast rows in the forecast schedule are impacted by the calculation.
|
Start Date/Time and End Date/Time |
Displays the starting and ending dates that represent the period which the forecast quantity applies. For example, PeopleSoft Demand Planning might generate forecasts in monthly buckets. In this case, the start and end dates represent the start and end of the month for which the forecast quantity applies. The system uses the demand calendar weights to translate the actual forecast period information into the PeopleSoft Supply Planning forecast buckets. |
Forecasted Quantity |
This value represents the unconsumed total forecast for the corresponding period from PeopleSoft Demand Planning or PeopleSoft Inventory. This field is required. |
Access the Net Forecast page.
Family Forecast |
Select to indicate that the forecast was allocated to the item as a result of a planning BOM or aggregate demand relationship. |
Forecast Date/Time |
Displays the current date PeopleSoft Supply Planning intends to fulfill the outstanding forecast demand. |
Original Date/Time |
Displays the date that the forecast consumption process intended the outstanding forecast demand be fulfilled. |
Forecasted Quantity |
Displays the portion of the net forecast quantity for the date specified. |
Frozen |
Select to change the status of the forecast to frozen; the solvers do not delay or cancel net forecast quantities that have been frozen. |
Priority Rank |
Displays a numeric value ranging from 1 (highest priority) to 999 (lowest priority) used by the planning engine to determine the order in fulfilling various independent demands, which include forecast demand. The priority 0 is reserved for the system. Note. You cannot enter the value 0 in the Forecast Priority Rank field. |
Include Quantity |
Select to include the forecast in all of the planning functions. The system populates this field by default. This option enables you to load a forecast in PeopleSoft Supply Planning and ignore the forecast during simulations. If you do not include the forecast quantity, the forecast appears on the net forecast maintenance page only; the forecast quantity does not appear on workbenches or reports and is ignored by solvers. |
Cancel |
Select and click the Save button to cancel the forecast. |
Note. Updates to the net forecast are not reflected in the solution until the next solver run.
This section provides an overview of extra demand and discusses how to:
Maintain transfers.
Maintain planned transfers.
Maintain stock requests.
Maintain extra demand.
Extra demand is a demand transaction that enables you to model demands on inventory from other sources (such as spare parts planning, quality assurance demands, and shrinkage), and simulate what-if scenarios for point demands that are not forecasted.
All of the extra demand in PeopleSoft Supply Planning is related to a specific planning instance. Extra demand cannot be shared across planning instances. During the Load Planning Instance process), you can retain prior extra demand for the planning instance or delete extra demand for the planning instance.
Extra demand transactions are visible only to the planning environment and stored in the Planning Instance Extra Demand table (PL_EXTRA_DMD). PeopleSoft Supply Planning does not commit extra demand data to the transaction system.
Extra demand uses demand priority to enable solvers to create feasible plans. The solvers see extra demand as another demand stream that can consume forecast. Unless you select the frozen option for an extra demand, solvers can reschedule that extra demand to another due date. Each extra demand is independent of any other demand.
Approved |
Select to approve an order manually. The system sends the order back to the transaction system as an approved order, and bypasses the approval logic in the Post Updates process. |
Backorder Base |
Represents the portion of the quantity requested base that could not be fulfilled with the business unit's current quantity available for the item. The value is recorded in the standard UOM. |
Configuration Code |
If the item is a configured item, the unique identifier appears. Configuration codes are 50-character, alphanumeric identifiers for configured items. The system automatically generates configuration codes as you configure items, using information about the customer's selections that you define as elements of the code. Configuration codes enable you to easily identify the options for a configured item. You can also use configuration codes to track and cost configured inventory. After you define the elements of the configuration code for an item, the system automatically assigns a configuration code to each product that it configures during distribution configuration. If the item is configuration coded, a valid configuration code is required. |
Consume Forecast |
Select to consider demand when running the Forecast Consumption process. |
Demand Line |
In PeopleSoft Inventory, orders for stock consist of demand lines. A demand line is the smallest request for stock that can be processed by the various fulfillment processes. If an order line can be fulfilled with the available on-hand quantity in the business unit, it is assigned one demand line (line number 1), requesting the total quantity required to fulfill the order line. If the order line cannot be fulfilled with the available on-hand quantity and partial quantities are allowed, the system generates a backorder (if you have elected to cancel backorders, the additional quantity requested is canceled). The backorder process adds a demand line for the unfulfilled quantity; the only change in the demand key for the second demand line is the demand line number (line number 2). |
Demand Source |
Displays the source of the independent demand. |
Frozen |
Select to change the status of the order to frozen; the system does not reschedule frozen demands during the solver process. Frozen demands cannot be delayed, even if the demand priority defined for a frozen demand is lower than the demand priority for demand that is not frozen. |
Include Quantity |
Select to include the corresponding inventory transaction quantity in all of the planning functions. The system populates this field by default. This option enables you to load an order in PeopleSoft Supply Planning and ignore the order during simulations. If you do not include an order quantity, the order appears on the corresponding refine page only; the order does not appear on workbenches or reports and is ignored by solvers. |
Line |
Displays the order line number. |
Order Number |
Displays the unique order ID for the corresponding inventory transaction. You can define order numbers manually or set up automatic numbering in PeopleSoft Inventory. If you use automatic numbering, PeopleSoft Inventory generates an order number based on the default sequence that you defined on the User Preferences - Inventory page; if no default sequence exists, the system generates a number based on the default sequence that you specified for material stock requests on the Automatic Numbering page. |
Pick Base |
Represents the picked quantity in the item's standard UOM. |
Planning Arrival Date/Time |
The current scheduled transfer arrival date to the destination business unit. The system validates this value against the receiving calendar. Note. When you change either the Planning Date/Time or Planning Arrival Date/Time value, the system recalculates the other based on lead time. |
Planning Date/Time |
The current scheduled transfer shipping date from the source business unit. The system validates this value against the shipping calendar. This value must be less than or equal to the value in the Planning Arrival Date/Time field. Note. When you change the value in either the Planning Date/Time or Planning Arrival Date/Time field, the system recalculates the other based on lead time. |
Priority and Priority Rank |
Enter a demand priority value between 1 and 999. The system assigns priorities to demands during the Load Planning Instance process based on established demand priority rules. In the absence of demand priority rules or for a matching demand priority rule for a given demand, the system assigns to the priority 999.The system also uses the demand priority value,999, as a default value when assigning priorities. When manually adding demand to a planning instance, specify the priority. See Setting Up Demand Priority Rules. Note. The priority 0 is reserved for the system. |
Requested Base |
Represents the order quantity in the source business unit. You cannot enter a negative value for this field. This field is required. If you modify the value in this field, you must enter a value equal to or greater than the value in the Pick Base field. |
Reserved |
If selected, indicates that the system inserted the order line into the PeopleSoft Inventory DEMAND_INV table by some form of reservation processing: soft reservation, nonsoft reservation, ATP reservation, or lot allocation. Once inserted into DEMAND_INV, the order line can be released for picking. |
Schedule |
Displays the schedule number. |
Scheduled Arrival Date/Time |
Date that the transaction system expects to receive the transfer in the destination business unit. |
Scheduled Date/Time |
Date that the transaction system expects to ship from the source business unit. |
Ship Base |
Represents the portion of the quantity requested base confirmed as shipped in the item's standard UOM. |
Ship Via |
Displays shipping method. |
Access the Transfer Orders page.
Note. You cannot add or delete transfer orders on this page.
Schedules Tab
Select the Schedules tab.
Schedule |
In order to make sure that we will not have an overflow issue bringing the line number into planning, we have to divide the Stock Request schedule line number from PeopleSoft Inventory by 100 during the LOAD. For example, a transfer Stock Request schedule line number of 1 from Inventory, will be displayed as 0.01 on the Transfer Orders page in Supply Planning. We then convert it back during the POST process. |
Interunit Status |
Values are:
|
Quantities Tab
Select the Quantities tab.
Remaining Demand |
Displays the outstanding demand for the source business unit. |
Remaining Supply |
Displays the outstanding supply expected for the destination business unit. |
Allocated Base |
Displays the quantity allocated to the order line, in the item's standard unit of measure. |
Activity Tab
Select the Activity tab.
Receipt Base |
Displays the current quantity received for the destination business unit in the item's base UOM. |
Inventory Pegging
Select the Inventory Pegging Tab.
Peg Status |
Displays the pegging status of the line item.
|
Peg Details |
Click the link to display the pegged demand information. This column will only be available if the Peg Status is Open or Completed. |
Access the Planned Transfer Orders page.
Note. You can add and update transfers on this page.
Planning Sequence Number |
Represents the numbering scheme that the system uses to keep planned orders in the Planning Instance table synchronous with those in the transaction system. Each time that you run the Load Planning Instance process in regeneration mode, the process initializes the next available planning sequence number to zero. The process resequences all of the planned orders that exist in the transaction system when inserting them into the Planning Instance tables. After inserting all of the orders into the tables, the process updates the next available planning sequence number on the Planning Instance table to equal the last planning sequence number used, plus one. When new planned orders are inserted in the planning instance, the system increments the planning sequence number for each new record. |
Delete |
Click to delete the planned transfer order. |
Status |
Displays the current status for the planned transfer. Values are:
|
Intransit |
Displays the number of days and hours required to transfer the item between business units. |
Access the Stock Requests page.
Note. Solvers consider material stock requests (MSRs) as single point demands that have no sourcing options and are supplied internally or externally on the request date.
Note. You cannot add or delete stock requests on this page. Enter and maintain stock requests in the PeopleSoft Supply Chain Management system on the Fulfill Stock Orders - Stock Requests page.
Schedules Tab
Select the Schedules tab.
Cancel |
Select to cancel the stock request. If you cancel a stock request, you also remove its demand from the planning instance. |
Quantities Tab
Select the Quantities tab.
Allocated Base |
Displays the quantity allocated to the order line, in the item's standard unit of measure. |
Remaining Quantity |
Displays the outstanding demand due for the stock request. |
Details Tab
Select the Details tab.
Confirm |
If selected, indicates that the specified quantity has been picked from the appropriate storage location. Picked lines must be confirmed before they are eligible for the Picking Confirmation process. If the demand line is picking confirmed, the Cancel field on the Schedules tab, and the Requested Base field on this tab are not available for entry. |
Shipped |
Select to indicate that the stock request has shipped. If the demand line has been shipped, only the Include Quantity and Consume Forecast fields on the Schedules tab are available for entry. |
Post Ship Complete |
Select to indicate that shipped quantities have been depleted from inventory. |
Inventory Pegging
Select the Inventory Pegging Tab.
Peg Status |
Displays the pegging status of the line item.
|
Peg Details |
Click the link to display the pegged demand information. This column will only be available if the Peg Status is Open or Completed. |
Access the Extra Demand page.
Note. You can add and update extra demand on this page.
Delete |
Click to delete the extra demand order from the planning instance. |
Scheduled Quantity |
Enter the number of items to include in the order. The value that you enter here cannot be a negative number. This field is required. |
Comments |
Enter a description of the order. |
This section discusses how to maintain customer orders and buying agreements.
Note. The Sales Order Demand tables reflect the sales order demand in the transaction system. However, the transaction system is the system of record. Changes that you make to the PeopleSoft Supply Planning Sales Order Demand tables are not automatically updated in the transaction system.
Access the Sales Orders/Quotes page or the Buying Agreements page.
Common Information
Business Unit |
For sales order and quote transactions, this business unit represents the PeopleSoft Order Management business unit. |
Start Date |
Displays the date that the buying agreement becomes valid. The term of the buying agreement can span multiple fiscal years. This field appears on the Buying Agreements page only. |
Grace End Date |
Displays an automatic extension date beyond the end date of the buying agreement. Orders entered after the buying agreement expiration date are based on the buying agreement price until the grace end date. If you have not provided an extension, a 0 appears as the value in this field. This field appears on the Buying Agreements page only. |
Order Date |
Displays the initial date that you created the order. This field appears on the Sales Orders/Quotes page only. |
Order Type |
Indicates whether the order is a sales order or a quote order. This field appears on the Sales Orders/Quotes page only. |
Order Status |
Select a valid order header status. Values are:
|
Quote Due Date |
Displays the quote deadline specified by the customer or prospect. This field appears on the Sales Orders/Quotes page only. |
Quote Expiration Date |
Displays the expiration date on which prices and terms on the quote are no longer valid. This field appears on the Sales Orders/Quotes page only. |
Success Percent |
Displays the forecasted success that the quotation will result in a sales order. Quotations are loaded into the planning instance as demand when their success percentage is greater than the percentage that you define in the Accept % (accept percentage) field on the Load Planning Instance - Orders/Forecast: Orders page. This field appears on the Sales Orders/Quotes page only. |
Line |
Displays the order line number. |
Schedule |
Displays the schedule line number. At the schedule level, break down the order quantity into one or more shipments. An order can include multiple lines, and each line can have multiple schedules. The number in this field increases by the increment value that you defined on the Order Management Definition - Order Management Setup page. |
Kit |
Displays the product kit code. A product kit is a fixed set of components that are sold as a unit. A product kit is not a stockable inventory item, but its components may be. PeopleSoft Supply Planning assumes that kit components are shipped together—including configured or custom kits— in one sales order. Note. All of the kits for a schedule must have the same ship date and time. If you change a kit ship date and time, the system also updates the ship date and time of the other items in the kit. |
Schedules Tab
Select the Schedules tab.
Status |
Displays a valid order line status. Values are:
|
Ship Base |
Displays the quantity shipped. This is expressed in the item's standard UOM. If the demand line has already been shipped, this value is the quantity shipped. If the line has not been shipped, this value is the quantity picked. |
Remaining Quantity |
Displays the outstanding demand for the shipment schedule. |
Frozen |
Select to change the status of the order to frozen; the system does not reschedule customer orders that are frozen. |
Include Quantity |
Select to include the order in all of the planning functions. The system selects this field by default for all of the customer orders and buying agreements in the planning instance tables. This option enables you to load an order in PeopleSoft Supply Planning and ignore the order quantity during simulations. If you do not include the order quantity, the order or buying agreement appears on the corresponding maintenance page only; the order does not appear on workbenches or reports and is ignored by solvers. |
Priority Rank |
Enter a demand priority value between 1 and 999. The system assigns priorities to demands during the Load Planning Instance process based on established demand priority rules. In the absence of demand priority rules or for a matching demand priority rule for a given demand, the system assigns the priority 999.The system also uses the demand priority, 999, as a default value when assigning priorities. When manually adding demand to a planning instance, specify the priority. See Setting Up Demand Priority Rules. Note. The priority 0 is reserved for the system. |
Quantities Tab
Select the Quantities tab.
Schedule Base |
Define the scheduled shipment quantity. This is expressed in the item's standard UOM. You cannot define this field with a negative value. This field is required. Note. This field appears on the Sales Orders/Quotes page only. |
Shipments Tab
Select the Shipments tab.
Ship From |
Displays the PeopleSoft Inventory ship from business unit. |
Estimated Ship ID |
Select an estimated shipment code. Estimated shipments are logical groupings that indicate what can be packed into the same shipping container. These groupings are temporary—the estimated shipment ID for a demand line can change at any time until freight has been calculated. If a demand line does not meet the criteria for an existing estimated shipment, the system creates a new estimated shipment for the line. Demand lines that have already been freighted (and therefore assigned to an estimated shipment) are not available to be packed. Note. Schedules sharing the same estimated ship ID must also have identical planning ship date and times. |
Planning Ship Date/Time |
Displays the current scheduled ship date PeopleSoft Supply Planning intends to ship. |
Target Date/Time |
Displays the requested date or scheduled ship date, depending on the date that you selected in the Demand Date field on the Load Planning Instance - Orders/Forecast: Orders page. PeopleSoft Supply Planning attempts to generate supply for the demand by this date. |
Scheduled Ship Date/Time |
Displays the date that the transaction system expects to ship. |
Details Tab
Select the Details tab.
Product ID |
Displays the product ID for the sales order line from the original customer order in the order management system. |
Reserved |
Select to indicate that the customer order line has a quantity reserved by one of the reservation or lot allocation processes in the inventory system.
|
Inventory Pegging
Select the Inventory Pegging Tab.
Peg Status |
Displays the pegging status of the line item.
|
Peg Details |
Click the link to display the pegged demand information. This column will only be available if the Peg Status is Open or Completed. |
This section discusses how to:
Maintain general production and planned production parameters.
Maintain production and planned production operation parameters.
Maintain production and planned production time parameters.
Maintain production and planned production component parameters.
Maintain production and planned production output parameters.
Note. Planned production orders in PeopleSoft Supply Planning are orders that have not been committed in the transaction system.
The Planned Production component enables you to maintain planned production created by the solvers or planned production that
you created manually. You can add or delete planned production in the Planned Production component.
The Production component enables you to maintain production from the transaction system. You cannot add or delete production
orders in the Production component.
Configuration Code |
If the item is a configured item, the unique identifier appears. Configuration codes are 50-character, alphanumeric identifiers for configured items. The system automatically generates configuration codes as you configure items, using information about the customer's selections that you define as elements of the code. Configuration codes enable you to identify the options for a configured item easily. You can also use configuration codes to track and cost configured inventory. After you define the elements of the configuration code for an item, the system automatically assigns a configuration code to each product that it configures during distribution configuration. If the item is configuration coded, a valid configuration code is required. |
Intensity |
This value appears by default from the task and determines the basis of the scheduling. Values are: Labor Time: The start and due date of the operation can be based on the operation's labor time (labor intensive). Machine Time: The start and due date of the operation can be based on the operation's machine time (machine intensive). Longest: The start and due date can be based on the longest of the two times, evaluated for each time type in the operation. For example, suppose that labor setup is 7 minutes, machine setup is 10 minutes, labor run is 20 minutes, machine run is 25 minutes, labor fixed run is 11 minutes, and machine fixed run is 7 minutes, the total operation time would be machine setup (10) + machine run (25) + labor fixed run (11) = 36 minutes. Cumulative: The start and due date can also be based on the sum of the machine and labor time. |
Operation Overlap % (operation overlap percentage) |
Displays the percentage of processing time remaining at one operation before the next operation can start. An overlap percentage of 100 percent means that the next operation can start at the same time as the current operation. An overlap percentage of 5 percent means that 95 percent of the operation must be completed before the next can start. Operation overlap cannot be less than 0 percent or more than 100 percent, and there can be no overlap on the last routing operation sequence or prior to a subcontracted operation. However, the vendor can send the end item back in multiple shipments. Therefore, you can define operation overlap for a subcontracted operation. |
Operation Sequence |
Displays where you need the components in the manufacturing process. PeopleSoft Production Management uses the work center associated with each operation and the WIP location associated with each work center to determine where to deliver components. The component's issue method in combination with the operation sequence determines when and where the material is delivered and how the system updates inventory in the WIP location or the issue quantity on the component list. When the system sets the operation sequence to zero or an invalid operation sequence is specified, it is assumed that the component item is to be used at the first operation. |
Original Start Date/Time and Original End Date/Time |
Displays the date and time that the transaction system intends to start and end the operation. |
Production ID |
Displays the unique ID assigned to a production order or schedule in PeopleSoft Production Management.
|
Production Type |
Specifies the production type. Values are:
|
Send Ahead Quantity |
Displays the number of units that must be accumulated or finished before they can be sent to the next operation and the next operation can begin. The send ahead quantity must be a positive number. Whether a whole number or a decimal appears depends on the item's UOM and quantity precision combination that was defined in PeopleSoft Inventory. For example, suppose that item ID A0007 has a UOM of EA and a Natural Round whole number combination, then you can only enter whole numbers. |
Sequence |
Displays the planning sequence number that the system assigned to track planned orders during the planning cycle. This field appears in the Planned Production component only. |
Work Center |
Work center where the operation step and tasks are performed. |
Access the Production - Production page or the Planned Production - Planned Production page.
Indicates where the production ID or production schedule is in the production cycle. Values are:
|
|
Production Area |
Displays the production area where the process identifier (PID) is currently scheduled to be completed. This field does not appear on the Planned Production component. |
BOM Code |
Displays the BOM used to generate the initial component list for the production order. |
Routing Code |
Displays the routing identifier used to generate the initial operation list for the production order. |
Reference Routing Item |
Displays the item whose routing is used to manufacture the end item. Each assembly item may have its own unique primary and alternate routings or reference another item's primary and alternate routings. |
Start Date/Time and End Date/Time |
Displays the beginning and completion dates and times for the production. Note. If you change the production start or end date, the system must reschedule all of the operations. |
Start Quantity |
Displays the quantity of the end item to be started in the production process. |
End Quantity |
Displays the quantity of the end item that is expected at the end of production. It is adjusted for scrap and yield. |
Completed Quantity |
Indicates whether assemblies have been completed to stock, routed to another WIP location, or issued directly to another production ID. This field does not appear on the Planned Production component. |
Scrapped Quantity |
Displays the number of assemblies that have been scrapped in the process. This field does not appear on the Planned Production component. |
Priority Rank |
The system formats production priority rank based on the highest priority demand to which the production order or planned production order provides supply. |
Frozen |
Select to change the order to frozen; the system does not reschedule or cancel frozen production orders during the solver process. |
Frozen Substitutes |
Select to prevent the solvers from suggesting substitutes for this production or planned production order. |
Include Quantity |
Select to include the production order in all of the planning functions. The system populates this field by default. This option enables you to load an order in PeopleSoft Supply Planning and ignore the order during simulations. If you do not include the quantity, the production order appears on the corresponding maintenance page only; the order does not appear on workbenches or reports and is ignored by solvers. |
Approved |
Select to approve an order manually. The system sends the production order back to the transaction system as an approved order. The production order bypasses the approval logic in the Post Updates process when committing the plan. |
Access the Production - Operations page or the Planned Production - Operations page.
Operation Summary Tab
Select the Operation Summary tab.
Planning Start Date/Time |
Displays the current date PeopleSoft Supply Planning intends to begin the operation. Note. If you change the operation date and time, the system must reschedule all of the operations and production header date and times. |
Planning End Date/Time |
Displays the current date PeopleSoft Supply Planning intends to finish the operation. Note. If you change the operation date and time, the system must reschedule all of the operations and production header date and times. |
Ignore Capacity |
Select to ignore the operation when consuming capacity against the work center. |
Assembly Starts |
Displays the number of assemblies started for the operation. |
Expected Completions |
Displays the number of assemblies expected to complete at the corresponding operation based on yield for the operation. |
Operation Yield % (operation yield percentage) |
Displays a percent of the quantity of goods expected to complete the production process. PeopleSoft Supply Planning considers operation yield to increment the supply by the expected loss to meet demand at the completion of the manufacturing process. |
Details tab
Select the Details tab.
Quantity Completed and Through |
Displays the number of assemblies that completed the operation successfully. |
Quantity Scrapped |
Displays the number of assemblies that were scrapped at the operation. |
Operation Completed |
Select to indicate that the operation is complete. |
Note. The Details tab does not appear on the Planned Production component.
Attributes tab
Select the Attributes tab.
Continuous |
Select to complete the operation in a single run with no down time. For example, suppose that a plant operates Monday through Friday, this operation cannot start Friday afternoon and complete the following Monday. |
Subcontracted |
Select to subcontract the operation. |
Access the Production - Resources or Planned Production - Resources page.
Crew Size |
Displays the number of people in a given crew for the operation |
Machine Resources |
Displays the number of machines used at the operation |
Resource Type |
Displays the type of resource used. Valid resources are primary or alternate machine, crew, or tool. |
Crew/Machine/Tool |
Displays the machine, crew, or tool code, as well as the description. |
Status |
Displays the availability of a resource for this work center. |
Quantity Used |
Displays the number of tools used at the operation. This option applies to tools only. |
Access the Production - Times page or the Planned Production - Times page.
Type and Resource Type |
Displays a value that appears by default from the routing information. Values are: Setup, Fixed, Run, Post Production, and In Transit. |
Operation Time |
Used in conjunction with the time unit, defines the amount of time to complete one unit. |
Time Unit |
Displays the unit of time for the corresponding operation time. For example, suppose that 5 appears in the Operation Time field, and Days appears in the Time Unit field, then the operation completes one unit every five days. The system determines the number of hours in a day by the work center's average daily hours, which are defined on the Work Center Definition page. |
Operation Rate |
Used in conjunction with the rate unit, defines the rate at which operations are completed. |
Rate Unit |
Displays the unit of time for the corresponding operation rate. For example, suppose that 3 appears in the Operation Rate field, and Units/Day appears in the Rate Unit field, the operation completes three units every day. |
Include Setup |
Select to indicate that the system considers setup in the operation lead time calculation. If you elected to include setup, the setup time is factored into the task or operation's lead time. The system always considers setup in the lead time calculation of the first operation, if setup is specified, regardless of the check box setting. This option applies only to planning labor setup and planning machine setup operation types. If this option is not selected, setup can begin prior to any production units arriving at the work center. The system assumes that setup can occur at any time after the start of production and does not include it as part of the item's lead time, except at the first operation. |
Access the Production - Components or Planned Production - Components page.
Common Information
Component ID |
Indicates the name of the component being used in the corresponding operation sequence. |
Note. Components cannot be substituted once an issue or scrap has occurred. Substitutions always occur for the original component and not the current component.
Component Summary Tab
Select the Component Summary tab.
Original Component ID |
Displays the original component from the BOM that the system uses to create the component list. When the component ID and the original component ID do not share the same value, a substitution has occurred. |
Scheduled Quantity |
Displays the number of assemblies scheduled for production for the corresponding operation sequence. |
Remaining Quantity |
Displays the outstanding demand for the component at a particular operation sequence. Note. Remaining quantity applies only to existing production orders and schedules. For planned production, the scheduled quantity and remaining quantity are the same. For all orders other than orders in process, the system calculates outstanding demand using the CURR_SCHED_QTY. For orders that are in process orders:
Note. The system determines QTY_COMP_AND_THRU and QTY_SCRAPPED by analyzing the operation list associated with the component list. If the operation sequence of the component is equal to zero, or if the operation sequence is not a valid operation list sequence, the system obtains these two quantities from the first operation for the assembly item. If the operation sequence of the component has a valid operation list sequence, the system obtains QTY_COMP_AND_THRU from that operation list sequence. In this case, QTY_SCRAPPED is equal to the sum of QTY_SCRAPPED from all prior operations. If no operation lists exist for the production ID, the system uses quantities from the production ID header. The system sets QTY_COMP_AND_THRU equal to COMPLETED_QTY and sets QTY_SCRAPPED equal to SCRAP_QTY.
|
Quantities Tab
Select the Quantities tab.
Quantity |
Displays the number of components required based on per assembly or per order. |
Per |
Displays the component requirements, expressed as an amount per assembly with a unit of 1 or per order, an amount regardless of the order size. |
Yield |
Displays the expected percentage of usable components in a batch of components issued to production. |
Issue Quantity |
For components using the issue or replenishment material issue method, displays the quantity consumed from the WIP location for the component and is charged to work in process. For components using the kit method, this is the quantity issued directly to the production ID. |
Yield Loss Quantity |
Displays the quantity scrapped during the end item process and consumed from the WIP location. |
Pending Issue Quantity |
Displays the quantity used based on the quantity completed at the operation multiplied by the quantity per assembly. If the component's quantity is expressed as per order, this is the per order quantity. The per order quantity is completely consumed at the first backflush. This quantity has not yet been consumed from the WIP location due to material shortages. |
Pending Yield Loss Quantity |
Displays the quantity of components scrapped during the end item process but not yet consumed from the WIP location due to material shortages. |
Note. Substitutes require the system to recalculate the quantity per and current scheduled quantity.
Note. The Quantities tab doesn't appear on the Planned Production component. However, some fields on this tab appear on the Planned Production Component Summary tab.
Details Tab
Select the Details tab.
Component Issue Method |
Indicates how the end item's components are issued for production. Values are:
|
Note. The Details tab does not appear on the Planned Production component.
Access the Production - Outputs page or the Planned Production - Outputs page.
Common Information
Output Type |
Displays the type of output associated with the BOM. Values include Primary, Co-product, Recycle, Teardown,and Waste.
|
Output Item |
The item must be an existing, inventory, and standard costed item. Output items cannot be floor stock or expense items. |
Output Summary Tab
Select the Output Summary tab.
Remaining Quantity |
Outstanding supply for the co-product and by-product. Calculated as Scheduled Quantity - Completed Quantity. |
Resource % (resource percentage) |
Displays the resource allocation percentage. This field indicates the percent of the BOM quantity each co-product represents. It is used during completions to determine what percentage of the components should be consumed for each co-product and primary item. This field does not appear on the Planned Production component. |
Details Tab
Select the Details tab.
Per |
Displays the component requirements, expressed as an amount per assembly with a unit of 1, or per order, an amount regardless of the order size. |
Scheduled Quantity |
Displays the quantity expected from the production reduced by production scrap. |
Completed Quantity |
Displays the number of assemblies completed. This field does not appear on the Planned Production component. |
Inventory Pegging
Select the Inventory Pegging Tab.
Peg Status |
Displays the pegging status of the line item.
|
Peg Details |
Click the link to display the pegged demand information. This column will only be available if the Peg Status is Open or Completed. |
This section provides an overview of the Purchasing pages and discusses how to:
Maintain POs.
Maintain planned POs.
View closed POs.
Approved |
Select to approve the PO manually. The system sends the PO back to the transaction system as an approved order and bypasses the approval logic in the Post Updates process. |
Configuration Code |
If the item is a configured item, the unique identifier appears. Configuration codes are 50-character, alphanumeric identifiers for configured items. The system automatically generates configuration codes as you configure items, using information about the customer's selections that you define as elements of the code. Configuration codes enable you to identify the options for a configured item easily. You can also use configuration codes to track and cost configured inventory. After you define the elements of the configuration code for an item, the system automatically assigns a configuration code to each product that it configures during distribution configuration. If the item is configuration coded, a valid configuration code is required. |
Frozen |
Select to change the status of the PO to frozen; solvers do not reschedule or cancel frozen POs. |
Include Quantity |
Select to include the PO in all of the planning functions. The system populates this field by default. This option enables you to load an order in PeopleSoft Supply Planning and ignore the order during simulations. If you do not include purchase quantities, the order appears on the corresponding maintenance page only; the order does not appear on workbenches or reports and is ignored by solvers. |
Access the Purchase Orders page.
Note. You cannot add or delete a PO, PO line, schedule, or distribution on this page.
Common Information
PO Date (purchase order date) |
Displays the date that you created the PO. |
PO Type (purchase order type) |
Displays the type of PO. This is used for informational purposes. |
PO Status (purchase order status) |
Displays the status of the entire PO. Values include: Initial, Open, Pending Approval, Approved, Dispatched, Canceled,and Complete. |
Location |
Displays the primary vendor location. |
Buyer |
Displays the name of the buyer on the PO. |
Line |
Displays the PO line. PO lines contain information such as the item ID, item description, category, and quantity. You can access schedules and distributions through the PO line. |
Schedule |
Every PO line has one or more due dates and external delivery locations carried on a schedule. In PeopleSoft Purchasing, you create a schedule for each unique delivery address and due date. |
Distribution Line |
Distribution lines contain information about how the item quantity charges and internal delivery locations. Distributions also contain interface information for PeopleSoft Inventory, Projects, Order Management, and Asset Management. You can have more than one distribution for each schedule. |
Schedules tab
Select the Schedules tab.
Due Date/Time |
Displays the date that the transaction system expects to receive the distribution. |
Planning Due Date/Time |
Displays the current scheduled date on which planning intends to receive the distribution. |
Lead Time |
Displays the number of days it takes to get inventory from the vendor. |
Release Date/Time |
Displays the date that you must dispatch the PO to get the receipt by the due date and time. |
Quantities tab
Select the Quantities tab.
Quantity Base |
Represents the initial quantity specified on the PO in the item's standard UOM. This field is required. |
Received Base |
Displays the quantity received and put away into PeopleSoft Inventory. |
Returned Base |
Displays the quantity returned to the vendor for replacement. |
Remaining Quantity |
Displays the outstanding supply due from the vendor. The system calculates this value as round down (quantity base * purchase yield) received base + returned base. |
Details tab
Select the Details tab.
Status |
You can change the PO line status to Active or Canceled. |
Inventory Pegging tab
Select the Inventory Pegging tab.
Peg Status |
Displays the pegging status of the line item.
|
Peg Details |
Click the link to display the pegged demand information. This column will only be available if the Peg Status is Open or Completed. |
Access the Planned Purchase - Orders page.
Planning Sequence Number |
Represents the numbering scheme that the system uses to keep planned orders in the Planning Instance table synchronous with those in the transaction system. Each time that you run the Load Planning instance processing regeneration mode, the process initializes the next available planning sequence number to zero. The process resequences all of the planned orders that exist in the transaction system when inserting them into the Planning Instance table. After inserting all of the orders into the table, the process updates the next available planning sequence number on the Planning Instance table to equal the last planning sequence number used plus one. As the system inserts new planned orders in the planning instance, the system increments the planning sequence number for each new record. |
Status |
Displays the current status for the planned PO. Values are:
|
Due Date/Time |
Represents the day that you except to receive the inventory. |
Release Date/Time |
Displays the day that you must dispatch the order to receive the inventory on the due date and time. |
Lead Time |
Displays the number of days that it takes to get inventory from the vendor. |
Quantity |
Represents the initial PO quantity. This field is required. |
Remaining Quantity |
Represents the outstanding supply due from the vendor. The system calculates this value as round down (quantity * purchase yield). |
Spot Buy |
Designates if the item is a spot buy item, which can be sourced by soliciting bids for a required quantity and date. |
Access the Closed Purchase Order page.
The Closed Purchase Order page enables you to view the details of closed purchase orders. You can use this information to calculate vendor shipments when considering vendor capacity. For example, if vendor capacity for an item is 100 for the month of January, you can view the Closed Purchase Order page to take into account a closed PO for a quantity of 25 that you received during the first week of January.
This section provides an overview of the mass maintenance definitions and action types and discusses how to:
Define mass maintenance header criteria.
Define mass maintenance selection criteria.
The Mass Maintenance component enables you to:
Modify multiple objects at a time.
For example, you can freeze all of the production orders for an item.
Retain maintenance tasks that are repeated for each planning cycle.
For example, you can define and retain a maintenance task to ignore all of the overdue supplies.
Make changes during planning cycle processing.
The Mass Maintenance functionality provides run control in the planning environment to define the mass maintenance steps. You can update all of the supply and demand transactions, set scalar values in fields, reschedule demands and supplies, change sourcing options, and consolidate multiple transactions.
Define the mass maintenance steps for planning instance data on a run control record. The maintenance definition is independent of planning instance, enabling you to change the planning instance on a run control and retain the associated mass maintenance steps.
A mass maintenance run control consists of:
A header section that describes the overall function of the mass maintenance and the attributes common to all of the steps.
The steps associated with the mass maintenance.
Each step may only operate on one transaction type. Each step contains the selection criteria for records to be maintained, as well as the actions that the system performs on the records that meet the selection criteria.
Mass Maintenance Reporting
You can generate the Mass Maintenance report (PLS7000) that summarizes, for each step, the selection criteria, the number of records that meet the selection criteria, and the records impacted by the maintenance step. Additionally, you can generate this report to determine potential outcomes without executing the setup, and use the report as an audit trail after execution.
To define a maintenance step, define the supply or demand transaction type on which you want the system to perform the actions. Each mass maintenance step applies to one transaction type only. The transaction types supported are:
Production.
Planned production.
POs.
Planned POs.
Transfers.
Planned transfers.
MSRs.
Forecasts (forecast demand only).
Extra demand.
Sales orders.
Quotes.
Buying agreements.
Next, define the records that you want the system to select for the specified transaction type. Lastly, define the maintenance actions that you want the system to perform on the selected records.
Four types of mass maintenance actions are available in the Mass Maintenance component. You can:
Set scalar values in fields.
Reschedule demands and supplies.
Change sourcing options.
Consolidate multiple transactions.
The actions available to you in the Mass Maintenance - Header page determine which values appear in the Transaction Type field. This table lists valid combinations supported by mass maintenance:
Transaction Types |
Set Value |
Reschedule |
Sourcing |
Consolidate |
Production |
X |
X |
||
Planned Production |
X |
X |
X |
X |
POs |
X |
X |
||
Planned Purchase |
X |
X |
X |
X |
Orders Transfers |
X |
X |
||
Planned Transfers |
X |
X |
X |
X |
Material Stock |
X |
|||
Requests Forecasts |
X |
|||
Extra Demand Sales |
X |
|||
Orders Quotes |
X |
|||
Buying Agreements |
X |
Set value actions update fields on a transaction to a scalar value.
Reschedule actions and reschedule supply transactions to occur on a new date. These action types can reschedule forward from a new start date or backwards from a new end date.
Note. Reschedule action types ignore the Frozen option, and do not check for material and capacity violations.
Consider these options when using reschedule action types with these transaction types:
Production Orders and Planned Production Orders |
Reschedule actions adjust a target date to a valid production date. If the start date is invalid, the system reschedules from the first valid production date after the supplied date. If the end date is invalid, the system reschedules backwards at the first valid production date before the supplied date. |
Purchase Orders and Planned Purchase Orders |
Reschedule actions use the target date as the new release date when forward scheduling and ensure the new due date time is a valid receiving date according to the receiving calendar. When backward scheduling, reschedule actions use the target date as the due date and do not ensure that the due date time is a valid receiving day. These actions assume the target due date is the expected actual receipt date. |
Transfer Orders and Planned Transfer Orders |
When forward scheduling from the scheduled ship date (PL_SCHED_DTTM), reschedule actions ensure the new arrival date time is a valid receiving date according to the receiving calendar. These actions do not validate the ship date. When backward scheduling, reschedule actions do not ensure that the arrival date time is a valid receiving day. These action types assume that the arrival date that you enter is the expected actual receipt date. Reschedule actions do ensure that the ship date is a valid shipping date. |
Sourcing actions change the sourcing supply option on selected transactions. These actions use the new sourcing option to reschedule the transaction backwards from the end date.
Sourcing actions can change yield values. A change in yield can change the start quantity, any component requirements, and any by-product output quantities.
Sourcing actions respect order modifiers. New quantities must be a valid interval equal to or less than the maximum order size. The system creates multiple orders if the original transaction quantity exceeds the maximum order size.
Note. Sourcing actions do not check for material and capacity violations.
Consider these options when using sourcing action types with these transaction types:
Planned Production Orders |
If you change the sourcing option on planned production, the system requires you to enter a new BOM code and routing code on the Maintenance Step definition. Modifying a sourcing option is equivalent to deleting an existing production order, creating a new production order for the same output quantity and end date, and using new BOM and routing codes. Sourcing actions apply only to planned production orders where the new business unit, item code, BOM code, routing code, and production type combination is a valid production option that exists on the PL_PROD_OPT table. |
Planned Purchase Orders |
If you change the sourcing option on a planned PO, the system requires you to enter a new vendor set ID, vendor ID, and vendor location. Modifying a sourcing option is equivalent to deleting an existing PO, creating a new PO for the same output quantity and due date, and using new vendor set ID, vendor ID, and vendor location codes. Sourcing actions apply only to planned POs where the new business unit, item code, vendor set ID, vendor ID, and vendor location combination is a valid purchase option that exists on the PL_PURCHASE_OPT table. |
Planned Transfer Orders |
If you change the sourcing option on a planned transfer order, the system requires you to enter a new source business unit and ship type ID. Modifying a sourcing option is equivalent to deleting an existing transfer order, creating a new transfer order for the same output quantity and arrival date, and using source business unit and ship type ID codes. Sourcing actions apply to planned transfer orders in two different situations:
|
Consolidate actions and group multiple planned supply transactions according to business unit, item, sourcing option, and order status into a single transaction with an aggregated quantity.
These actions can reschedule the consolidated transaction forward from a new start date or backwards from a new end date.
Consolidation actions respect order modifiers. New quantities must be a valid interval equal to or less than the maximum order size. The system creates multiple orders if the consolidated total exceeds the maximum order size.
Note. Consolidation action types ignore the Frozen option, and do not check for material and capacity violations. You cannot consolidate planned transactions for configurable items.
Access the Mass Maintenance - Header page.
Description |
(Required) Enter a description of the mass maintenance. |
Planning Instance |
The maintenance definition is independent of planning instance. You can change the planning instance for a run control and retain the associated mass maintenance steps. |
Run |
Click to initiate the Mass Maintenance process (PL_PI_MSMNT) for the corresponding transaction type. |
Start Planning Engine |
Click to start the planning engine for the corresponding planning instance. |
Execute Maintenance Actions |
Select to execute the maintenance steps on this run control. If you do not select this option, the system does not execute the steps on this run control when you run the Mass Maintenance Application Engine process (PL_PI_MSMNT). Note. The data that the Mass Maintenance Application Engine process writes to the report tables remains in the report tables until you rerun the Mass Maintenance Application Engine process for the corresponding run control. To refresh the data in the report tables, select the Execute Maintenance Actions option and the Run Maintenance Report option, and run the Mass Maintenance Application Engine process. |
Run Maintenance Report |
Select to clear all previous report information from report tables and refresh the tables with the information on the run control, steps, and affected transactions for each step of the current run. If you do not select this option, all information from a prior run of the same run control remains in the report tables, and the system writes no new information to the tables when you run the Mass Maintenance Application Engine process. Note. If you elect to run the Mass Maintenance report (PLS7000) prior to running the Mass Maintenance Application Engine process on the Process Scheduler Request page, the report results might be incomplete. For example, if you freeze plan production in step 1, and then select frozen plan production in step 2, then step 1 must execute before step 2 can accurately depict the changes. If you are running in report mode only, this execution does not occur, and the reported list of affected transactions for step 2 is incomplete. |
Maintenance Steps
Step |
Enter a step number. Each step operates on one transaction type only. Each step has two main sections:
|
Description |
Enter a description for the corresponding step. |
Action |
Select the action type that you want to perform on the transaction. The value that you select here determines the values that appear in the Transaction Type field. |
Transaction Type |
Select the supply or demand transaction type on which the system performs the action that you selected in the Action field. Each mass maintenance step applies to one transaction type only. The values available in this field are determined by the value that you selected in the Action field. |
Date/Days Offset Selection |
When specifying values for date fields, you can elect to state an explicit date or a stated number of days offset from the current date associated with planning instance. |
Item Selection Criteria
Define item selection criteria for each mass maintenance step that you include in the run control. Filter criteria on the Header page consists of fields from the item on the transaction.
Each field has a corresponding operator column or values column. Values (for example, Both, Yes,and No) appear when a field contains a finite set of valid values.
Access the Mass Maintenance - Selection Detail page.
Maintenance Steps
The fields that appear in this group box are the same fields you defined in the Maintenance Step group box on the Header page. You can overwrite those values here.
Selection Criteria
Define item selection criteria for each mass maintenance step that you include in the run control. Filter criteria on the Selection details page consists of fields specific to the transaction type. For example, if you selected Forecasts as the transaction type, the system displays forecast-related fields in the Selection Criteria group box, such as Forecast Family, Forecast Date, and Priority Rank.