Performing Mass Maintenance

This topic provides an overview of mass maintenance and mass maintenance action types.

Page Name

Definition Name

Usage

Mass Maintenance - Header Page

PL_PI_MSMNT_REQ1

Define mass maintenance header information and item-related selection criteria.

Mass Maintenance - Selection Detail Page

PL_PI_MSMNT_REQ2

Define mass maintenance step information and transaction-related 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.

Mass Maintenance Definition

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.

Mass Maintenance Steps

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 Type

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 Action Types

Set value actions update fields on a transaction to a scalar value.

Reschedule Action Types

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:

Term

Definition

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 Action Types

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:

Term

Definition

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 supplier SetID, supplier ID, and supplier 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 supplier SetID, supplier ID, and supplier location codes.

Sourcing actions apply only to planned POs where the new business unit, item code, supplier SetID, supplier ID, and supplier 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:

  • Where the business unit, item code, source business unit, and ship type ID combination is a valid item transfer option that exists on the PL_TRANS_IT_OPT table.

  • Where the business unit and item code combination has a planned by attribute defined as Distribution. In this scenario, the business unit, source business unit, and ship type ID combination must be a valid generic transfer option that exists on the PL_TRANS_OPT table.

Consolidate Action Types

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.

Use the Mass Maintenance - Header page (PL_PI_MSMNT_REQ1) to define mass maintenance header information and item-related selection criteria.

Navigation:

Supply Planning > Refine Plan > Mass Maintenance

Field or Control

Description

Description

Enter a description of the mass maintenance. A description is required.

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

Field or Control

Description

Step

Enter a step number. Each step operates on one transaction type only.

Each step has two main sections:

  • The selection criteria for records to be maintained.

  • The actions to be taken on the records that meet the selection criteria.

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 values.

Use the Mass Maintenance - Selection Detail page (PL_PI_MSMNT_REQ2) to define mass maintenance step information and transaction-related selection criteria.

Navigation:

Supply Planning > Refine Plan > Mass Maintenance

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.