Item Planning Attributes
Attribute Group | Attribute Name | Description |
---|---|---|
General Planning | Inventory Planning Method |
Organization level planning:
|
Make or Buy |
Option that applies to items with the Inventory Item set to Yes. The Planner Workbench uses this to populate the appropriate value for the implementation type. You can’t change this value if open orders exist for the item.
|
|
Planner |
Material planner assigned to plan this item. You must define planner codes for your organization before updating this attribute. The planner defined here’s responsible for approving all move order lines requesting the item if move order approvals are used. If an item is Supplier Managed, you must enter a Planner for the item. |
|
Subcontracting Component |
Indicate the subcontracting type associated to this item when it’s used as a subcontracting component in Chargeable Subcontracting. The available choices are:
|
|
Min-Max Quantity | Minimum | Minimum on-hand quantity before replenishment for Min-Max Planning. |
Maximum | Maximum on-hand quantity that you don’t want to exceed for Min-Max Planning. | |
Order Quantity | Minimum |
Minimum order quantity or repetitive rate (units per day). Planning algorithms (reorder point, min-max, MPS, and MRP) use this to modify the size of planned order quantities or repetitive daily rates. For discrete items, when net requirements fall short of the minimum order quantity, planning algorithms suggest the minimum order quantity. For repetitive items, when average daily demand for a repetitive planning period falls short of the minimum order quantity, planning algorithms suggest the minimum order quantity as the repetitive daily rate. For example, use this to define an order quantity below which it’s unprofitable to build the item. |
Maximum |
Maximum order quantity or repetitive rate (units per day) of the item. Planning algorithms (reorder point, min-max, MPS, and MRP) use this to modify the size of planned order quantities or repetitive daily rates. For discrete items, when net requirements exceed the maximum order quantity, planning algorithms suggest the maximum order quantity. For repetitive items, when average daily demand for a repetitive planning period exceeds of the maximum order quantity, planning algorithms suggest the maximum order quantity as the repetitive daily rate. For example, use this to define an order quantity above which you do have insufficient capacity to build the item. |
|
Cost | Order | Cost associated with placing an order for the item, which can include expenses like processing fees, shipping costs, and other related expenses. |
Carrying Percentage | Percentage used to calculate the annual carrying cost. This is the percentage of the unit cost that represents your internal cost to stock one unit for one year. | |
Source | Replenishment Type |
Method in which the requests are fulfilled:
Note:If you're using Supplier Scheduling, it’s generally recommended that this field be left blank. Otherwise, it could override your sourcing rules. |
Organization |
Optionally enter the organization from which an internal requisition draws the item. This applies only when Inventory is the replenishment source type. You can choose organizations that meet the following criteria:
|
|
Subinventory | Enter the subinventory within the source organization from which an internal requisition draws the item. This applies only when Inventory or Subinventory is the replenishment source, and only when you specify a source organization. For MRP planned items, you must enter a non-nettable source subinventory when the source organization is the current organization. | |
Safety Stock | Safety Stock Planning Method |
Planning method to be used in calculating safety stock levels:
|
Demand Period | Number of days to use for average daily demand calculation. | |
Days of Cover | Number of days times average demand that defines the safety stock level. | |
Order Modifiers | Fixed Order Quantity |
Quantity used to modify the size of planned order quantities or repetitive daily rates. When net requirements fall short of the fixed order quantity, the planning process suggests the fixed order quantity. When net requirements exceed the fixed order quantity, the planning process suggests multiple orders for the fixed order quantity. For discrete items, use this attribute to define a fixed production or purchasing quantity. For repetitive items, use this attribute to define a fixed production rate. For example, if your suppliers can provide the item in full truckload quantities only, enter the full truckload quantity as the fixed order quantity. |
Fixed Days Supply |
Number of days used to modify the size and timing of planned order quantities. The planning process suggests planned order quantities that cover net requirements for the period defined by this value. The planning process suggests one planned order for each period. For example, use this to reduce the number of planned orders for a discrete component of a repetitive item. |
|
Fixed Lot Size Multiplier | Define a specific quantity that the planning process should use when creating planned orders for an item. This attribute ensures that the resulting order quantities are always a multiple of the specified value | |
Apply Order Modifier to Start Quantity | Indicates whether to apply the item order modifier settings to the calculation of planned order start quantities. This attribute is a part of the Planning Order Modifiers attribute group. | |
Supplier Managed | Automatically Expire ASN | Indicate whether the advance shipment notice expires automatically. This attribute is reserved for future use. |
Consigned | If enabled, the item is consigned, meaning residing at your location, but owned by the supplier. | |
Release Authorization Required |
Authorization is required before a sales order is created. You can set the authorization as:
|
|
Replenishment Point | Minimum Order |
Minimum order quantity or repetitive rate (units per day). Planning algorithms (reorder point, min-max, MPS, and MRP) use this to modify the size of planned order quantities or repetitive daily rates. For discrete items,when net requirements fall short of the minimum order quantity, planning algorithms suggest the minimum order quantity. For repetitive items, when average daily demand for a repetitive planning period falls short of the minimum order quantity, planning algorithms suggest the minimum order quantity as the repetitive daily rate. For example, use this to define an order quantity below which it’s unprofitable to build the item. |
Minimum Days of Supply | Indicate the minimum allowed days of supply before replenishment must occur. | |
Order Quantity | Maximum Order |
Maximum order quantity or repetitive rate (units per day) of the item. Planning algorithms (reorder point, min-max, MPS, and MRP) use this to modify the size of planned order quantities or repetitive daily rates. For discrete items, when net requirements exceed the maximum order quantity, planning algorithms suggest the maximum order quantity. For repetitive items,when average daily demand for a repetitive planning period exceeds of the maximum order quantity, planning algorithms suggest the maximum order quantity as the repetitive daily rate. For example, use this to define an order quantity above which you do have insufficient capacity to build the item. |
Maximum Days of Supply | Indicates the maximum allowed days of supply for replenishment reorder. | |
Fixed Quantity | Indicates the fixed quantity for reorder. | |
Average Daily Demand Calculation | Forecast Type |
Type of forecast:
|
Window Days | Period for which a forecast is considered by the planning engine. | |
MPS MRP Planning | Planning Method |
Select the option that decides when to plan the item:
|
Round Order Quantities | Indicates whether the planning process uses decimal or whole number values when calculating planned order quantities or repetitive rates. If Yes is selected, 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. | |
Create Supply | Indicates if the application 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 supply for the item as part of meeting the demand for the original item. | |
Planning Time Fence |
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 can’t 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. 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 day that’s not a workday) plus the value you select here. The planning time fence values are:
|
|
Demand Time Fence |
Determines a point in time inside which the planning process ignores the forecast demand and considers only the sales order demand when calculating gross requirements. This reduces the risk of carrying excess inventory. Calculate the demand time fence as the plan date (or the next workday if the plan is generated on a day that’s not a workday) plus the value you select here. The demand time fence values are:
|
|
Critical Component | If selected, marks the item as a critical component for MPS and MPP planning. This lets you plan master scheduled items with respect to only critical component and their material resource constraints. Hidden by default. | |
Release Time Fence |
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:
Auto-release of repetitive schedules isn’t 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 day that’s not a workday) plus the value you select here.
|
|
Shrinkage Rate | 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). | |
Forecast Control |
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.
|
|
Acceptable Early Days |
Number of days before which the planning process won’t reschedule orders. The planning process only suggests rescheduling out if:
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 doesn’t occur (because of Acceptable Early Days), a second order, due before the first, won’t be rescheduled past the first order. This lets you reduce plan nervousness and eliminate minor reschedule recommendations, especially when it’s cheaper to build and carry excess inventory for a short time than it’s to reschedule an order. This applies to discrete items only. |
|
Planning Time Days | Calculates the planning time fence as the plan date (or the next workday if the plan is generated on a day that’s not a workday) plus the value you enter here. | |
Demand Time Days | Calculates the demand time fence as the plan date (or the next workday if the plan is generated on a day that’s not a workday) plus the value you enter here. | |
Release Time Days | Calculate the release time fence as the plan date (or the next workday if the plan is generated on a day that’s not a workday) plus the value you enter here. | |
Create Supply After | Date after which you can use the item to create supply for Oracle Fusion Cloud Supply Chain Planning. You can't set a past date for this attribute. You can specify this date only if Create Supply is set to Yes. | |
MPS Planning | 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 Where:
Note:You can use this attribute only when you integrate Product Hub with Oracle E-Business Suite. This attribute is invalid in an Oracle Fusion Cloud Applications only scenario, where Product Hub interacts with the Fusion Applications source system. |
Repair Lead Time | Time,in days, to repair the part at the supplier site. The definition is in context with the final usable part of product 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. Valid values are decimal numbers greater than or equal to 1. | |
Repair Yield | Yield percentage when you upgrade or repair a defective part. For example, a repair yield of 23% is entered as 0.23. 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. Valid values are decimal numbers greater than zero and less than 1. | |
Lead Times | Preprocessing Days | Days you must add to purchasing or manufacturing lead time to order. |
Postprocessing Days | Days required to receive a purchased item into inventory from the initial supplier receipt. You can't enter a value if the Make or Buy attribute is set to Make. | |
Processing Days | Days required to procure or manufacture an item. For manufactured assemblies, processing days equals manufacturing lead time. | |
Variable | Time to produce one additional unit of an assembly. Total lead time is variable lead time multiplied by order quantity, plus fixed lead time. | |
Enforce Purchasing Lead Time | System considers the specified lead time when planning and scheduling production or procurement for that item. | |
Cumulative Total | Total lead time of the assembly plus the largest adjusted cumulative total lead time of its components,where each is adjusted by subtracting the operation lead time offset. | |
Fixed | Days required to make an assembly independent of order quantity, such as setup or tear downtime. | |
Cumulative Manufacturing | Manufacturing lead time of an assembly (in days) plus the largest adjusted cumulative manufacturing lead time of its components, where each is adjusted by subtracting the operation lead time offset. Purchased items have no cumulative manufacturing lead time. | |
Lead Time Lot Size | Quantity used to compute processing lead time (and fixed and variable lead times). The default value is the item's standard lot size or, if a standard lot size isn't defined. |