MPS/MRP Planning Attribute Group

Planning Method

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Select the option that Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses to decide when to plan the item:

Not planned

The item does not require long-term planning of material requirements. Choose this option for high volume and/or low cost items that do not warrant the administrative overhead of MRP; typically dependent demand items.

You master schedule the item and require manual planning control. Choose this option for items with independent demand, items that are critical to your business, or items that control critical resources.

MRP/DRP Planned

Choose this option when you want both MRP and DRP planning for the item.

MPS/DRP Planned

Choose this option when you want both MPS and DRP planning for the item.

DRP Planned

Choose this option when you have multiple organizations for which you are exercising Distribution Requirements Planning for the item.

This is an item defining attribute. If you select MPS or MRP planning, the item is automatically assigned to the default category set for the Oracle Master Scheduling/MRP and Oracle Supply Chain Planning functional area. See: Item Defining Attributes.

Forecast Control

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Select an option to determine the types of demand you place for the item. This guides the key processes of two-level master scheduling: forecast explosion, forecast consumption, planning, production relief, and shipment relief. This is appropriate only for items that are models, option classes, options, or mandatory components of models and option classes.

Consume

You forecast demand directly, rather than by exploding forecast demand.

Consume and derive

You forecast demand directly, explode forecast demand, or use a combination of both methods.

Exception Set

This attribute is controlled at the Organization level only.

Enter the name of the planning exception set that groups together the sensitivity controls and exception time periods for item-level planning exceptions for the item. The item-level planning exceptions include: overcommitted, shortage, excess, and repetitive variance. The planning process uses this attribute to decide when to raise planning exceptions for the item.

Since different items may require different sensitivity controls and exception time periods, you can define multiple planning exception sets and assign different sets to different items. In other cases, where many items require the same sensitivity controls and exception time periods, you can associate the same set to multiple items. See: Overview of Material Requirements Planning and Creating Planning Exception Sets.

This option traces the end assembly the item is pegged to at the top of the bill of material. Even if you do not select end assembly pegging, you can still calculate and view end assemblies on-line.

End Assembly/ Soft Pegging

Choose this option for both soft pegging and end assembly pegging.

Hard Pegging

This option allocates supply to demand based on the Reservation Level option set in the MRP Plan options. This pegs supply to demand and demand to supply by project at all levels of a bill of material. This allows you to pre-allocate supply to demand and generate planned orders based on the plan level options. See: Reviewing or Adding Plan Options.

End Assembly/ Hard Pegging

Choose this option for both hard pegging and end assembly pegging.

None

This option disables project material allocation, end assembly pegging, and full pegging.

Attention: You must use the memory-based planner to calculate end assembly pegging.

Round Order Quantities

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Indicate whether the planning process uses decimal or whole number values when calculating planned order quantities or repetitive rates. When this option is turned on, decimal values round up (never down) to the next whole number. The planning process carries any excess quantities and rates forward into subsequent periods as additional supply. See: Overview of Material Requirements Planning.

Shrinkage Rate

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Enter a factor that represents the average amount of material you expect to lose during manufacturing or in storage. The planning process inflates demand to compensate for this expected loss. For example, if on average 20% of all units fail final inspection, enter 0.2; the planning process inflates net requirements by a factor of 1.25 (1 / 1 - shrinkage rate). See: Overview of Material Requirements Planning.

Acceptable Early Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Enter the number of days before which the planning process will not reschedule orders. The planning process only suggests rescheduling out if:

the new calculated order date is later than the original order due date plus the acceptable early days

the new calculated order is does not violate the order of current scheduled receipts

For example, if the original order due date is 10-JUN, and Acceptable Early Days is 3, the planning process not suggest rescheduling if the new due date is less than or equal to 13-JUN. When rescheduling does not occur (because of Acceptable Early Days), a second order, due before the first, will not be rescheduled past the first order.

This lets you reduce plan nervousness and eliminate minor reschedule recommendations, especially when it is cheaper to build and carry excess inventory for a short time than it is to reschedule an order.

Repetitive Planning

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Indicate whether to plan material requirements in repetitive daily rates. The planning process suggests repetitive schedules you can implement using the Planner Workbench. Turn this option off to plan material requirements in discrete quantities. The planning process suggests planned orders you can implement as discrete jobs or as purchase requisitions. See: Overview of Planner Workbench.

Overrun Percentage

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Enter a percentage the planning process uses to suggest new daily rates. The planning process only suggests a new daily rate if the current rate exceeds the suggested rate by more than the acceptable overrun amount.

The acceptable overrun amount is calculated by multiplying this percentage by the suggested daily rate. For example, if the suggested daily rate is 100/day, and Overrun Percentage is 10, the planning process only suggests a new rate if the current rate is greater than 110/day (100/day + 100/day x 10%).

This lets you reduce plan nervousness and eliminate minor rate change recommendations, especially when it is cheaper to carry excess inventory for a short time than it is to administer the rate change.

This attribute applies to repetitive items only. For discrete items, use Acceptable Early Days.

Acceptable Rate Decrease

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Enter the amount the planning process uses to decrease current daily rates inside the planning time fence. The planning process does not suggest a new daily rate less than the current daily rate minus the acceptable rate decrease amount.

The acceptable rate decrease amount is calculated by multiplying this value by the current daily rate. For example, if the current daily rate is 100/day, and the Acceptable Rate Decrease is 10, the planning process does not suggest a new daily rate that is less than 90/day (100/day - 100/day x 10%).

If you do not enter an Acceptable Rate Decrease, the planning process assumes no lower limit to the new daily rate it can suggest inside the planning time fence. If you enter zero, the planning process assumes it cannot suggest any rate less than the current daily rate inside the planning time fence.

This lets you minimize disruption to shop floor schedules by restricting short term rate change suggestions. This applies to repetitive items only. See: Overview of Repetitive Planning.

Acceptable Rate Increase

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Enter the amount the planning process uses to increase current daily rates inside the planning time fence. The planning process does not suggest a new daily rate greater than the current daily rate plus the acceptable rate increase amount.

The acceptable rate increase amount is calculated by multiplying this value by the current daily rate. For example, if the current daily rate is 100/day, and the Acceptable Rate Increase is 10, the planning process does not suggest a new daily rate that is greater than 110/day (100/day + 100/day x 10%).

If you do not enter an Acceptable Rate Increase, the planning process assumes no upper limit to the new daily rate it can suggest inside the planning time fence. If you enter zero, the planning process assumes it cannot suggest any rate greater than the current daily rate inside the planning time fence.

This lets you minimize disruption to shop floor schedules by restricting short term rate change suggestions. This applies to repetitive items only. See: Overview of Repetitive Planning.

Calculate ATP

Indicate whether to calculate and print available to promise (ATP) on the Planning Detail Report, using the following formula:

Attention: ATP calculated by the planning process is not related to ATP information calculated and maintained by Oracle Inventory. As such, planning ATP does not consider ATP rules from the Available to Promise Rule window, and is not related to the ATP information displayed in the View Item Available to Promise Information window.

Reduce MPS

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Select an option to decide when to reduce master production schedule (MPS) quantities to zero.

If Oracle Work in Process and Oracle Purchasing are installed, you get automatic production relief when you create a discrete job, purchase requisition, or purchase order. In this case, you would typically set this attribute to None.

If you do not have automatic production relief, you may select one of the following options to reduce MPS quantities and avoid overstating your supply.

None

Do not reduce order quantities on the MPS.

Past due

Reduce order quantities on MPS entries to zero when the entry is past due.

Demand time fence

Reduce order quantities on MPS entries to zero when the due date moves inside the demand time fence.

Planning time fence

Reduce order quantities on MPS entries to zero when the due date moves inside the planning time fence.

Planning Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Choose one of the following options to determine a point in time inside which certain restrictions on planning recommendations apply. For discrete items, the planning process cannot suggest new planned orders or rescheduling existing orders to an earlier date. For repetitive items, the planning process can only suggest new daily rates that fall inside the acceptable rate increase and decrease boundaries. For items having a WIP Supply Type of Phantom, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning ignores the planning time fence.

A time fence increases manual control of the plan, minimizing short term disruption to shop floor and purchasing schedules.

Calculate the planning time fence as the plan date (or the next workday if the plan is generated on a non-workday) plus:

Planning Time Fence Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the planning time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this value when Planning Time Fence is User-defined.

Demand Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Select an option to determine a point in time inside which the planning process ignores forecast demand and considers only sales order demand when calculating gross requirements. This reduces the risk of carrying excess inventory. For items having a WIP Supply Type of Phantom, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning ignores the demand time fence.

Attention: Oracle Master Scheduling/MRP and Oracle Supply Chain Planning also uses the demand time fence when loading master schedules. The demand time fence is calculated as the start date of the master schedule load plus one of the following options.

Calculate the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus:

Demand Time Fence Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this attribute when Demand Time Fence is User-defined.

Release Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Choose an option to determine a point in time inside which planned orders for discretely planned items are automatically released as WIP jobs or purchase requisitions. The planned orders must meet the following auto-release criteria:

the new due date lies within the auto-release time fence

the lead time is not compressed

the orders are for standard items (will not release models, option classes, and planning items)

the orders are not for Kanban items

the orders are for DRP planned items in a DRP plan, MPS planned items in an MPS plan, or MRP planned items in an MRP plan (See: Auto-release Planned Orders.)

the release time fence option is defined as anything other than Do not auto-release, Do not release (Kanban), or Null

Release Time Fence Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the release time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this value when Release Time Fence is User-defined.