Oracle Item master Attributes and its meaning in detail

Oracle Inventory Item master attributes and its meaning in depth

Item Attributes and its meaning

Tab at Item level: MPS / MRP Planning Attribute Group

Following are the MPS/MRP Planning item attributes and their possible values. You set these attributes when defining or updating items.

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 cannot use this option unless the Pick Components attribute is checked.
MRP planning	Choose this option for non-critical items that do not require manual planning control, typically dependent demand items.
MPS planning	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 Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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.
None	You place sales order demand but do not forecast demand.

See Overview of Two-Level Master Scheduling, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide. 

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, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

Pegging

Enter the pegging option. See Reviewing Item Planning Information, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

Soft Pegging	This option allocates supply to demand based on the Reservation Level option set in the MRP Plan options. See Reviewing or Adding Plan Options, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
End Assembly Pegging	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. .
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.

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

Planned Inventory Point

Indicates if the item is an Inventory Point item. This means that material can be stored at the item level without losing materials or quality characteristics. Inventory Points generally point to major stocking phases in the manufacturing cycle. 

Create Supply

ORACLE ADVANCE PLANNING AND SCHEDULING ONLY

Indicates if the system can suggest supply for this item. If you use an item as a substitute to meet demand for another item, then this attribute indicates whether you can create new supply for the item as part of meeting the demand for the original item. 

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, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide and Enforce Integer Requirements, Oracle Bills of Material User's Guide.

Exclude from Budget

If selected, the item is excluded from the budget.

Critical Component

If selected, flags the item as a critical component for MPS and DRP planning. This allows you to plan master scheduled items with respect to only critical component and their material resource constraints.

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

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 does not violate the order of current schedule 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.

This applies to discrete items only. For repetitive items, use Overrun Percentage. 

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, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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.

See Overview of Repetitive Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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 - the acceptable rate decrease amount. The system multiples the acceptable rate decrease by the current daily rate. For example, if the current daily rate is 100 per day and the acceptable rate decrease is ten, then the planning process does not suggest a new daily rate that is less than 90 per day. (100 per day - 100 per day x 10%). If you o not enter an acceptable rate decrease, then the planning process assumes no lower limit to the daily rate it can suggest inside the planning time fence. If you enter zero, then the planning process assumes it cannot suggest any rate less than the current daily rate inside the planning time fence. 

Calculate ATP

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

ATP = Planned production - committed demand

Planned production = planned orders, scheduled receipts (purchase orders, jobs, and repetitive schedules), suggested repetitive schedules, nettable quantity on hand.

Committed demand = sales orders, component demand (from planned orders, discrete jobs, suggested repetitive schedules, and lot expirations). Committed demand does not include forecasted demand.

Important: 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.

See Starting the Planning Manager, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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:

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Planning Time Fence Days.

See Overview of Time Fence Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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.

Note: 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:

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Demand Time Fence Days.

See Overview of Time Fence Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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 order date lies within the auto-release time fence for any order type (make or buy).
• Order Date = Start Date - Pre-Processing Lead Time. For example if the Order Date = April 5 and the Start Date = April 7, if the pre-processing lead time is 2 days. When the order date falls inside the release time fence, the planned order is released.
• 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, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide
• the release time fence option is defined as anything other than Do not auto-release, Do not release (Kanban), or Null
• DRP, MPS, and MRP plans must be run with the Memory-based Planning Engine See Overview of the Memory-based Planning Engine, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide

Auto-release of repetitive schedules is not applicable for repetitively planned items. No material availability check is performed before WIP jobs are released.

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

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Release Time Fence Days.
Do not auto- release	The item cannot be auto-released.
Do not release (Kanban)	For Kanban items, prevent release of planned orders manually or automatically.

See Overview of Time Fence Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.

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.

Substitution Window

Calculates until what time a substitute can be considered for an item.

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Release Time Fence Days.

Substitution Window Days

If the substitution window type is User-defined, you specify the number of days a substitute is considered for an item. See End Item Substitution, Oracle Advanced Planning and Scheduling Implementation and User's Guide.

Convergent Consumption Pattern

Indicates whether you use a convergent consumption pattern in planning. The available choices are: Series, Parallel, and Use Global Value.

Continuous Interorganization Transfers

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY

This attribute enables you to perform continuous interorganization transfers. 

Divergent Supply Feeding Pattern

Indicates whether you use a divergent supply pattern for planning. The available choices are: Series, Series with Minimum Transfer Quantity (MTQ), and Use Global Value

DRP Planned

Indicates whether planning method is distribution requirements planning. Distribution requirements planning (DRP) uses the same demands, supplies and cost data as MPP/MPS and MRP plans. However DRP can be used as demand schedules for MPP/MPS?MRP plans. An item can be specified as being DRP planned in which case, you can also specify the target and maximum inventory levels and replenishment windows.

Repair Program

Indicates the relationship with the vendor for the repair of an item. The available choices are:

• Advanced Exchange on Defective Receipt
• Advanced Exchange on PO Issue
• Repair Return

Repair Yield

Indicates the yield when you upgrade or repair a defective part. The repair yield is always in context with the final usable part or product and not based on the defective part. The repair yield represents the yield of the repair process. You define the repair yield in the repair organization.

Repair Lead-time

Time to repair the part at the supplier site. The definition is in context with the final usable part of preoduct and not based on the defective part. For example, if you can repair an item a from a defective item B, planning assumes the repair lead-time from item A when it calculates the repair of defective item B. A repair organization requires the time equal to the repair lead-time to convert a defective part to a usable part. You define the repair lead time in the repair organization. 

Preposition Point

The preposition point represents the push type relationship with a trading partner. When planning hits a preposition point for an item, it pushes all the existing supply downstream until this point.

In the case of multi-souring repair, you should not set the preposition point for the item-repair vendor. If you set select this check box for a multi-sourced item, then the system pushes the entire inventory to the first trading partner it encounters in the planning process.