This chapter covers the following topics:
The following table lists the item attributes and the corresponding attribute group to which they belong.
| Variable | Description |
|---|---|
| Acceptable Early Days | See MPS/MRP Planning |
| Acceptable Rate Decrease | See MPS/MRP Planning |
| Acceptable Rate Increase | See MPS/MRP Planning |
| Accounting Rule | See Invoicing |
| Activity Cause | See Asset Management page |
| Activity Notification Required | See Asset Management page |
| Activity Source | See Asset Management page |
| Activity Type | See Asset Management page |
| Allow Description Update | See Purchasing |
| Allow Express Transactions | See Receiving |
| Allow Substitute Receipts | See Receiving |
| Allow Unordered Receipts | See Receiving |
| Assemble to Order | See Order Management |
| Asset Category | See Purchasing |
| Asset Item Type | See Asset Management page |
| ATP Components | See Order Management |
| ATP Rule | See Order Management |
| Autocreated Configuration | See Bills of Material |
| Auto Expire ASN | See General Planning |
| Average Daily Demand Calculation Forecast Type | See General Planning |
| Average Daily Demand Calculation Window Days | See General Planning |
| Back Orderable | See Web Option |
| Base Model | See Bills of Material |
| Billing Type | See Service |
| BOM Allowed | See Bills of Material |
| BOM Item Type | See Bills of Material |
| Build in WIP | See Work in Process |
| Bulk Picked | See Inventory |
| Calculate ATP | See MPS/MRP Planning |
| Carrying Cost Percent | See General Planning |
| CAS Number | See Process Manufacturing |
| Charge Periodicity | See Order Management |
| Check ATP | See Order Management |
| Check Material Shortage | See Inventory |
| Child Generation | See Inventory |
| Child Lot Enabled | See Inventory |
| Collateral Item | See Physical Attributes |
| Configurator Model Type | See Bills of Material |
| Consigned | See General Planning |
| Container | See Physical Attributes |
| Container Type | See Physical Attributes |
| Continuous Inter-Org Transfers | See MPS/MRP Planning |
| Contract Duration | See Service |
| Contract Duration Period | See Service |
| Contract Item Type | See Service |
| Convergence Pattern | See MPS/MRP Planning |
| Conversions | See Main |
| Copy Lot Attributes | See Inventory |
| Cost of Goods Sold Account | See Costing |
| Costing Enabled | See Costing |
| Create Configured Item BOM | See Bills of Material |
| Create Fixed Asset | See Service |
| Create Supply | See MPS/MRP Planning |
| Critical Component | See MPS/MRP Planning |
| Cumulative Manufacturing Lead Time | See Lead Times |
| Cumulative Total Lead Time | See Lead Times |
| Customer Ordered | See Order Management |
| Customer Orders Enabled | See Order Management |
| Cycle Count Enabled | See Inventory |
| Default Buyer | See Purchasing |
| Default Grade | See Inventory |
| Default Lot Status | See Inventory |
| Default Material Status | See Inventory, Oracle Inventory User's Guide |
| Default Serial Status | See Inventory |
| Default Receiving Subinventory | See Inventory |
| Default Shipping Subinventory | See Inventory |
| Default Sales Order Source Type | See Order Management |
| Default Shipping Organization | See Order Management |
| Demand Time Fence | See MPS/MRP Planning |
| Demand Time Fence Days | See MPS/MRP Planning |
| Deviation Factor + | See Main |
| Deviation Factor - | See Main |
| Dimension Height | See Physical Attributes |
| Dimension Length | See Physical Attributes |
| Dimension Unit of Measure | See Physical Attributes |
| Dimension Width | See Physical Attributes |
| Divergence Pattern | See MPS/MRP Planning |
| DRP Planned | See MPS/MRP Planning |
| Downloadable | See Physical Attributes |
| Dual Control | See Main |
| Effectivity Control | See Bills of Material |
| Electronic Format | See Physical Attributes |
| Enable Contract Coverage | See Service |
| Enable Defect Tracking | See Service |
| Enable Provisioning | See Service |
| Encumbrance Account | See Purchasing |
| Enforce Ship-To | See Receiving |
| Engineering Item | See Bills of Material |
| Equipment | See Physical Attributes |
| Event | See Physical Attributes |
| Exception Set | See MPS/MRP Planning |
| Exclude From Budget | See MPS/MRP Planning |
| Expense Account | See Purchasing |
| Expiration Action | See Inventory |
| Expiration Action Interval | See Inventory |
| Financing Allowed | See Order Management |
| Fixed Days Supply | See General Planning |
| Fixed Lead Time | See Lead Times |
| Fixed Lot Multiplier | See General Planning |
| Fixed Order Quantity | See General Planning |
| Format Validation | See Inventory |
| Forecast Control | See MPS/MRP Planning |
| Grade Controlled | See Inventory |
| Hazard Class | See Purchasing |
| Hazardous Material | See Process Manufacturing |
| Hold Days | See Inventory |
| Include in Rollup | See Costing |
| Input Classification Tax Code | See Purchasing |
| Inspection Required | See Purchasing |
| Instance Class | See Service |
| Internal Ordered | See Order Management |
| Internal Orders Enabled | See Order Management |
| Internal Volume | See Physical Attributes |
| Inventory Asset Value | See Costing |
| Inventory Item | See Inventory |
| Inventory Planning Method | See General Planning |
| Invoice Close Tolerance | See Purchasing |
| Invoice Enabled | See Invoicing |
| Invoiceable Item | See Invoicing |
| Invoicing Rule | See Invoicing |
| Item Status | See Main |
| Lead Time Lot Size | See Lead Times |
| List Price | See Purchasing |
| Locator Control | See Inventory |
| Long Description | See Main |
| Lot Control | See Inventory |
| Lot Divisible | See Inventory |
| Lot Expiration (Shelf Life) Control | See Inventory |
| Lot Merge Enabled | See Inventory |
| Lot Substitution Enabled | See Inventory |
| Lot Split Enabled | See Inventory |
| Lot Status Enabled | See Inventory |
| Lot Translate Enabled | See Inventory |
| Make or Buy | See General Planning |
| Market Price | See Purchasing |
| Match Configuration | See Bills of Material |
| Maturity Days | See Inventory |
| Maximum Inventory Days of Supply | See MPS/MRP Planning |
| Maximum Inventory Window | See MPS/MRP Planning |
| Maximum Load Weight | See Physical Attributes |
| Maximum Order Quantity | See General Planning |
| Min-Max Maximum Quantity | See General Planning |
| Min-Max Minimum Quantity | See General Planning |
| Minimum Fill Percentage | See Physical Attributes |
| Minimum License Quantity | See Web Option |
| Minimum Order Quantity | See General Planning |
| Move Order Receipts Subinventory | See Inventory |
| Negative Measurement Error | See Inventory |
| Network Logistics Trackable | See Inventory |
| OE Transactable | See Order Management |
| OM Indivisible | See Physical Attributes |
| Orderable On the Web | See Web Option |
| Order Cost | See General Planning |
| Order Quantity Maximum Days of Supply | See General Planning |
| Order Quantity Fixed Quantity | See General Planning |
| Order Quantity Maximum Quantity | See General Planning |
| Output Classification Tax Code | See Invoicing |
| Outside Processing Item | See Purchasing |
| Outside Processing Unit Type | See Purchasing |
| Outsourced Assembly | See Purchasing |
| Over Return Tolerance | See Order Management |
| Over Shipment Tolerance | See Order Management |
| Overcompletion Tolerance Type | See Work in Process |
| Overcompletion Tolerance Value | See Work in Process |
| Overreceipt Quantity Control Action | See Receiving |
| Overreceipt Quantity Control Tolerance | See Receiving |
| Overrun Percentage | See MPS/MRP Planning |
| Payment Terms | See Invoicing |
| Pegging | See MPS/MRP Planning |
| Pick Components | See Order Management |
| Picking Rule | See Order Management |
| Planned Inventory Point | See MPS/MRP Planning |
| Planner | See General Planning |
| Planning Method | See MPS/MRP Planning |
| Planning Time Fence | See MPS/MRP Planning |
| Planning Time Fence Days | See MPS/MRP Planning |
| Positive Measurement Error | See Inventory |
| Postprocessing Lead Time | See Lead Times |
| Prefix (Lot) | See Inventory |
| Preprocessing Lead Time | See Lead Times |
| Pre-positioning Point | See MPS/MRP Planning |
| Price Tolerance % | See Purchasing |
| Primary Unit of Measure | See Main |
| Process Costing Enabled | See Process Manufacturing |
| Process Execution Enabled | See Process Manufacturing |
| Processing Lead Time | See Lead Times |
| Production Enabled | See Process Manufacturing |
| Purchasable | See Purchasing |
| Purchased | See Purchasing |
| Receipt Close Tolerance | See Purchasing |
| Receipt Date Action | See Receiving |
| Receipt Days Early | See Receiving |
| Receipt Days Late | See Receiving |
| Receipt Required | See Purchasing |
| Receipt Routing | See Receiving |
| Receipt Close Tolerance | See Purchasing |
| Receiving Subinventory | See Receiving |
| Recipe Enabled | See Process Manufacturing |
| Recovered Part Disposition | See Service |
| Reduce MPS | See MPSI/MRP Planning |
| Release Authorization Required | See General Planning |
| Release Time Fence | See MPS/MRP Planning |
| Release Time Fence Days | See MPS/MRP Planning |
| Repair Lead Time | See MPS/MRP Planning |
| Repair Program | See MPS/MRP Planning |
| Repair Yield | See MPS/MRP Planning |
| Repetitive Planning | See MPS/MRP Planning |
| Replenishment Point Minimum Days of Supply | See General Planning |
| Replenishment Point Minimum Quantity | See General Planning |
| Reservable | See Inventory |
| Restrict Locators | See Inventory |
| Restrict Subinventories | See Inventory |
| Retest Interval | See Inventory |
| Returnable | See Order Management |
| Revision Control | See Inventory |
| RFQ Required | See Purchasing |
| RMA Inspection Required | See Order Management |
| Round Order Quantities | See MPS/MRP Planning |
| Rounding Factor | See Purchasing |
| Safety Stock Bucket Days | See General Planning |
| Safety Stock Method | See General Planning |
| Safety Stock Percent | See General Planning |
| Sales Account | See Invoicing |
| Scheduling Penalty Inventory Carry | See Work In Process |
| Scheduling Penalty Operation Slack | See Work In Process |
| Secondary | See Main |
| Serial Generation | See Inventory |
| Serial Status Enabled | See Inventory |
| Service Request | See Service |
| Shelf Life Days | See Inventory |
| Ship Model Complete | See Order Management |
| Shippable | See Order Management |
| Shipping Subinventory | See Order Management |
| Shrinkage Rate | See MPS/MRP Planning |
| Shutdown Type | See Asset Management page |
| Source Organization | See General Planning |
| Source Subinventory | See General Planning |
| Source Type (Replenishment) | See General Planning |
| Standard Lot Size | See Costing |
| Starting Child Lot Number | See Inventory |
| Starting Delay (Days) | See Service |
| Starting Lot Number | See Inventory |
| Starting Lot Prefix | See Inventory |
| Starting Serial Number | See Inventory |
| Starting Serial Prefix | See Inventory |
| Stockable | See Inventory |
| Subcontracting Component | See General Planning |
| Substitution Window Type | See MPS/MRP Planning |
| Substitution Window Days | See MPS/MRP Planning |
| Supply Locator (Process Manufacturing) | See Process Manufacturing |
| Supply Locator (Work in Process | See Work in Process |
| Supply Subinventory (Process Manufacturing) | See Process Manufacturing |
| Supply Subinventory (Work in Process) | See Work in Process |
| Supply Type | See Work in Process |
| Target Inventory Days of Supply | See MPS/MRP Planning |
| Target Inventory Window | See MPS/MRP Planning |
| Taxable | See Purchasing |
| Tax Code (Purchasing) | See Purchasing |
| Tax Code (Invoicing) | See Invoicing |
| Taxable | See Purchasing |
| Track in Installed Base | See Service |
| Transactable | See Inventory |
| UN Number | See Purchasing |
| Under Return Tolerance | See Order Management |
| Under Shipment Tolerance | See Order Management |
| Unit of Issue | See Purchasing |
| Unit Volume | See Physical Attributes |
| Unit Weight | See Physical Attributes |
| Use Approved Supplier | See Purchasing |
| User Item Type | See Main |
| Variable Lead Time | See Lead Times |
| Vehicle | See Physical Attributes |
| Volume Unit of Measure | See Physical Attributes |
| Web Status | See Web Option |
| Weight Unit of Measure | SeePhysical Attributes |
| WIP Supply Locator | See Work in Process |
| WIP Supply Subinventory | See Work in Process |
| WIP Supply Type | See Work in Process |
The following are the Main attributes and their possible values. You set these attributes when you define or update items. See: Defining Items and Updating Organization Level Items.
This is the stocking and selling unit of measure. Any necessary conversions are based on this unit of measure. This attribute is not updatable and assigned at the organization level. See: Defining Units of Measure.
The default primary unit of measure for new items is defined using the INV:Default Primary Unit of Measure profile option. See: Oracle Inventory Profile Options.
The primary unit of measure is the default for invoices and credit memos entered in Oracle Receivables.
Note: If an item belongs to both a master organization and a child organization, and these organizations belong to the same costing organization, the primary unit of measure for the item must be the same within both organizations.
This attribute controls how on-hand balances are tracked. This attribute is assigned at the organization level. The available values are:
| Primary | The system tracks the on-hand balances by the primary unit of measure. |
| Primary & Secondary | The system tracks the on-hand balances by both the primary and secondary units of measure. |
Warning: Oracle Bill of Materials and Dual Unit of Measure (UOM): When the Tracking UOM for an item is Primary & Secondary (a dual unit of measure), do not select the BOM Allowed check box on the Bills of Material tab. Otherwise, an error occurs when you try to create a BOM with this item in Oracle Bill of Materials.
This attribute controls if pricing is based on the primary or secondary unit of measure. If you set the value to secondary, the system reprices the orders line at ship confirmation. This attribute is assigned at the organization level.
If the item is dual unit of measure controlled, or priced in a secondary unit of measure, you can specify a secondary unit of measure. This attribute is assigned at the organization level.
You can stock items in two units of measure. This attribute is assigned at the organization level. The available choices are:
| Fixed | The system stores inventory in both the primary and secondary units of measure. You can enter an item quantity in one unit of measure, and the system converts the quantity to the secondary unit of measure and displays both quantities. |
| Default | The system stores inventory in both the primary and secondary units of measure. You can enter an item quantity in one unit of measure, and the system converts the quantity to the second unit of measure and displays both quantities. You can change the quantity in the secondary unit of measure, without changing the quantity in the primary unit of measure. |
| No Default | The system stores inventory in both the primary and secondary units of measure. Use this option when the default conversion between the two units of measure is usually not the same. The system does not automatically display in the secondary unit of measure when you specify the quantity for the primary unit of measure. You manually enter the quantity of the secondary unit of measure before you process a transaction. The secondary quantity can fluctuate from the default conversion by the factors that you specify in the Deviation + and Deviation - attributes. |
You can enter acceptable deviations as decimal values. This attribute is assigned at the organization level. This produces a plus or minus tolerance of acceptability. For example, if the allowable transaction quantity deviation for the item is 10 percent higher than the established conversion, you would enter 10 in this field.
You can enter acceptable deviations as decimal values. This attribute is assigned at the organization level. This produces a plus or minus tolerance of acceptability. For example, if the allowable transaction quantity deviation for the item is 10 percent lower than the established conversion, you would enter 10 in this field.
Oracle provides several types by default at installation. These types correspond to the item templates also provided. Select one of these values, or one you defined with the Item Type window. See: Defining Item Types.
ATO model
Finished good
Freight
Inventory Type
Kit
Model
Option Class
Outside processing item
PTO model
Phantom item
Planning
Product Family
Purchased item
Reference item
Subassembly
Supply item
Item status codes set or default the values for attributes under status control. User-defined status codes control certain item attributes designated as status attributes. The status attributes are:
BOM Allowed
Build in WIP
Customer Orders Enabled
Internal Orders Enabled
Invoice Enabled
Transactable
Purchasable
Stockable
Recipe Enabled
Process Execution Enabled
These attributes control the functionality of an item over time. See: Status Attributes and Item Status Control, Defining Item Status Codes, and Defining Item Attribute Controls.
The default item status for new items is defined using the INV:Default Item Status profile option. See: Oracle Inventory Profile Options.
| Both | Use both item-specific and standard unit of measure conversions. If you defined an item-specific and a standard conversion for the same unit of measure, the item-specific conversion is used. |
| Item specific | Use only unit of measure conversions unique to this item. |
| Standard | Use only standard unit of measure conversions. If you want to use only standard conversions do not create item specific conversions. |
Indicate the long description for this item. This Long Description is supported in multiple languages.
Related Topics
Relationships Between Attributes
Following are the Inventory attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
This attribute enables you to stock and transact this item in Oracle Inventory. You must turn this option on if you want to enable the following item attributes: Stockable, BOM Allowed, Transactable, and Build in WIP.
This is an item-defining attribute. If you turn this option on, the item is automatically assigned to the default category set for the Inventory functional area. See: Item Defining Attributes.
This attribute enables you to stock the item in Oracle Inventory. You can set this attribute only when you enable the Inventory Item attribute. You must enable this item attribute if you want to transact the item.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
This attribute enables you to perform transactions on the item. You can set this attribute only if you set the item attributes Inventory Item and Stockable. This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
Note: Oracle Order Management uses this along with the Stockable and Returnable item attributes to determine which authorized returned items can be physically received into inventory. (See also OE Transactable).
This attribute enables you to create item revisions. If you turn this option on you must specify an existing revision number for issues and receipts on the revisions tab. See, Defining Item Revisions for more information.
Important: You cannot change revision control when an item has on hand quantity. If Revision Control is controlled at the Master Item level, the check for on hand quantity is against the sum of on hand quantities in all child organizations.
Note: For Oracle Order Management, if item attribute Reservable is checked, you can manually reserve a specific revision at order entry or use Inventory picking rules to suggest the revision when you pick an order. If you do not enable the Reservable item attribute, Inventory picking rules suggest the revision when you pick the order.
This attribute enables you to create material reservations for the item. You can reserve an item only when you have sufficient inventory.
Note: Oracle Inventory has enhanced support for picking non-reservable items. This feature can be employed when on-hand quantities are not closely tracked and when inventory is often driven negative during shipment confirmation. When a line for a non-reservable item is pick released, the system will not attempt to generate allocations for the material; pick confirm will not be required. Instead, the line status is immediately changed to Released and the delivery line becomes eligible for shipment confirmation. The subinventory and locator on the delivery line, which will become the subinventory and locator from which the ship confirmation transaction issues the inventory, is taken from the Shipping Item Transaction Default for that item. If insufficient quantity is available in that location, and if negative quantities are enabled in that organization, the shipment confirmation will drive inventory negative. Reservation control for a subinventory overrides reservation control for an item. In other words, if an item is reservable but a subinventory is not, the item quantity in that subinventory is not reservable.
Note: If the Reservable attribute is checked, Oracle Order Management allows reservation of the item during order entry. If material hasn't been reserved prior to pick release, pick release creates reservations for material when the pick wave move order is allocated.
Important: You cannot turn off reservation control if reservations exist.
This attribute enables you to check for material shortages for the item. Turn this option on to trigger a material shortage alert and shortage notification during transactions of the item. See, Material Shortage Alerts and Shortage Notifications
Oracle Inventory and Oracle Shipping Execution automatically backorder a delivery line at pick release if inventory is unavailable for allocation. In the event that no material is available for allocation, the system deletes the pick wave move order line immediately and changes the delivery line status to Backordered. If the system can allocate part of the required quantity, then the system splits the delivery line. The system updates the requested quantity on the move order line to reflect the available quantity and closes the move order line when you pick the available quantity. You can use the Shipping Transactions window, the Releases Orders window, or the Releases Sales Orders SRS process to re-release the delivery line.
| No control | Do not establish lot control for the item. |
| Full control | Track inventory balances by lot number. You must specify a lot number for issues and receipts. |
You can establish lot number control only for an item that has no quantity on hand. If Lot Control is controlled at the Master Item level, the system checks for on hand quantity in all child organizations.
Note: For Oracle Order Management, if an item is Reservable, you can manually reserve a specific lot at order entry or use Inventory picking rules to suggest the lot when you pick an order. If the item is not Reservable, then Inventory picking rules suggest the lot when you pick an order..
Note: Work in Process recognizes lot control or serial control for an item, but not both. You cannot transact an item in Work in process if it is under both lot and serial control.
Enter a starting prefix for all lot numbers you define for this item. When you set Lot Number Generation to At item level in the Organization Parameters window, then the system uses this prefix you define a lot number for the item.
Enter a starting lot number for the item. When you set Lot Number Generation to At item level in the Organization Parameters window, the system uses this number as the starting lot number. When you create additional lots for the item, the system increments each suceeding lot. See, Defining Organization Parameters.
This is the number of days added to the lot creation date to determine the lot maturity date. If you do not enter a number, the system assumes the lot is mature at creation. Lot Creation Date + Maturity Days = Default Lot Maturity Date.
This is the number of days added to the lot creation date before you can release the lot. If you do not enter a number, the system assumes that you can use the lot immediately. Lot Creation Date + Hold Days = Default Hold Release Date.
Lot Expiration control governs how long items in a given lot remain available.
| Shelf life days | Specify the shelf life of the item in days. The system starts counting the shelf life on the day you receive the lot into inventory. After the specified number of days, the system sends you a warning message. |
| No control | Shelf life control not established for this item |
| User-defined | Specify an expiration date as you receive each lot. You receive a warning but are not prevented from using the lot after expiration. |
Important: You cannot change lot expiration control when on-hand quantity of the item exists. If Lot Expiration is controlled at the Master level, the check for on-hand quantity is against the sum of on hand quantities in all child organizations.
Note: You can customize how the system calculates the lot expiration date. For more information, see My Oracle Support.
Enter the number of days each lot is active. At receipt, the system adds the shelf life days to the system date to determine the expiration date. This is used only when you choose Shelf life days for Lot Expiration Control.
Enter the number of days after the creation date before you need to retest the lot. The system adds this number to the lot creation date to determine the default retest date. Lot Creation Date + Retest Interval = Default Lot Retest Date.
Enter the number of days the system adds to the expiration date before it performs an action on the lot. Lot Expiration Date + Lot Expiration Action Interval = Default Expiration Action Date.
Enter the default action code for this item. This is the action listed on the expiration notification when the lot expires, fails quality inspection, or falls within the experimental error results region.
Select this option to enable cycle counting for the item. See: Overview of Cycle Counting.
Enter the percentage of negative variance acceptable before cycle count creates an adjustment transaction. Your physical cycle count can be less than the quantity on hand by an amount less than or equal to this percentage.
For example, suppose quantity on hand is 100 and negative tolerance is 10%. Inventory does not require approval for if the counted quantity is within tolerance. For physical counts under 90 units, Inventory creates an adjustment, changing the quantity on hand to the physical count.
Enter the percentage of positive variance acceptable before cycle count creates an adjustment transaction. Your physical count can be greater than the quantity on hand by an amount less than or equal to this percentage.
For example, suppose quantity on hand is 100 and positive tolerance is 10%. Inventory does not require approval for if the counted quantity is within tolerance. For physical counts over 110 units, Inventory creates an adjustment, changing the quantity on hand to the physical count.
Important: The lot substitution feature is not supported for items with serial control or any combination such as lot serial, lot revision, or LSR combinations.
| At inventory receipt | Create and assign serial numbers when you receive the item. Thereafter, for any material transaction, you must provide a serial number for each unit. |
| At sales order issue | Create and assign serial numbers when you issue (ship) the item against a sales order. If you select this option, serial numbers are required at ship confirm. If you receive an item on an RMA (return material authorization), you must specify the same serial numbers you created at sales order issue. All other material transactions for this item bypass serial number information. |
| No control | Serial number control not established for this item. All material transactions involving this item bypass serial number information. |
| Predefined | Assign predefined serial numbers when you receive the item. Thereafter, for any material transaction, you must provide a serial number for each unit. |
The following table presents conditions where you can change back and forth between certain options:
| Change back and forth between | Change back and forth between | When |
|---|---|---|
| Dynamic entry at inventory receipt | Predefined serial numbers | Any time |
| Dynamic entry at sales order issue | No serial number control | Any time |
| Dynamic entry at inventory receipt | No serial number control | Item has no on-hand quantity |
| Dynamic entry at sales order issue | Predefined serial numbers | Item has no on-hand quantity |
| Predefined serial numbers | No serial number control | Item has no on-hand quantity |
| Dynamic entry at inventory receipt | Dynamic entry at sales order issue | Item has no on-hand quantity |
If Serial Generation is controlled at the Item level, the check for on-hand quantity is against the sum of on-hand quantities in all child organizations.
Enter a starting alpha prefix for all serial numbers you define. You must enter a value when you choose Predefined and when Serial Generation is At item level in the organization parameters. This prefix is used when you define your serialized units.
Enter a starting numeric suffix for all serial numbers for this item only. You must enter a value when you choose Predefined and when Serial Number Generation is At item level in the organization parameters. This starting numeric suffix is used when you define your serialized units. Thereafter, this number is incremented for each succeeding serial number. See: Defining Organization Parameters.
| Dynamic entry | Define locators when you use them, either as you receive or ship items. |
| No control | Locator control not established. |
| Prespecified | Define locators before you use them. |
Note: For Oracle Order Management, if an item is Reservable, you can manually reserve a specific locator at order entry or let pick release use Inventory picking rules to suggest the locator when the order is picked. If the item is not Reservable, Inventory picking rules will suggest the locator when the order is picked.
Note: Locator control for an organization or for a subinventory overrides locator control for an item.
Indicate whether to restrict transactions of this item to or from a subinventory specified in a list you define with the Item/Subinventory Information window. See: Assigning Subinventories to an Item. This option must be turned on if you choose to restrict locators.
Indicate whether to restrict transaction of this item to or from a locator specified in the list you define with the Item/Subinventory Information window. You cannot restrict locators unless you also restrict subinventories.
Defines the default value of the on-hand status for the receipt transaction for non lot-controlled items. If the field is null, then the subinventory level status serves as the default value for the on-hand status.
Indicate whether an item is subject to status control at the Lot Level. For example, a lot may be In Test. A company may have a policy of allowing Lots In Test to be used in planning and reserved, but not shipped. A lot may also be In Quarantine. For example, a company may have a policy of not allowing lots In Quarantine to be used in planning.
If an item is lot-controlled, you can indicate the Default Lot Status. For example, a lot of microprocessors may be at the Quarantine status until a soak test is complete.
Indicate whether an item is subject to status control at the Serial Level. For example, a company may have a policy of allowing all functions on serial numbers that are New, and a policy of allowing reservations to Reworked serial numbers, not including Reworked items.
If an item is serial-controlled, you can indicate the Default Serial Status. For example, a serial number of analytical equipment may be at the Quarantine status until a soak test is complete.
Indicate whether the item is grade controlled in addition to lot controlled. A grade code represents specific characteristics of a lot. If you select the Grade Controlled check box, then you must specify a default grade for the item.
Note: You cannot modify this check box if you have transacted the item.
Enter a default grade for the item. All items under grade control must have a default grade. You can use the grade change transaction to change the default grade of an item.
Note: You can change the default grade even if you performed transactions for the item.
If you enable child lot control, you can specify a parent lot and a child lot for transactional purposes. The system processes transactions for the lot regardless of whether you specify the parent lot for the transaction. You cannot modify this field if inventory transactions or reservations exist for the item. If you choose to control this attribute at the master organization level, then you can modify this attribute only if no transactions or reservations exist for the master organization or any child organizations that are associated with the master organization.
This field determines how the system generates child lot numbers at the item level. You can choose to generate child lot numbers across the organization level or at the item level. The available choices are:
Parent + Child: When set to parent + child, the parent lot number acts as a prefix, and the next available lot number is added to form the child lot. For example if the parent lot is p1, then the child lot would be p1-1.
Parent: When set to parent, child lot numbers are based on the same sequence as the lot number. For example, if the parent lot is p1, then the child lot is p2.
If you choose to generate child lots at the item level, you can optionally choose to enter a child lot prefix.
Enter the starting number for each child lot. This field is enabled only if the item is child lot enabled.
Select this check box to ensure the child lot number conforms to the child lot parameters that you define for the organization or the item. If you select this check box, then the system verifies the child lot number is the lot number concatenated with the child lot prefix and a numeric suffix for the lot number of the correct zero-padded length, if you enable zero padding at the item level.
Select this check box to ensure that a new child lot inherits all the attributes of the parent lot. If you do not select the check box, then the child lot does not inherit the parent lot attributes.
Indicate whether a lot-controlled item may split into many lots.
Indicate whether many lots of a lot controlled item may merge into one lot.
Enables you to translate lots within a lot controlled item.
Enables you to substitute lots during a transaction.
Important: The lot substitution feature is not supported for items with serial control or any combination such as lot serial, lot revision, or LSR combinations.
Select this check box to enable you to allocate, reserve, or move partial lot quantities. If you do not select this check box you must transact the full lot quantity for this item. You cannot modify this field if transactions exist for the item.
Enables you to pick items in bulk.
Sets the default subinventory for move order receipts.
Related Topics
Relationships Between Attributes
Following are the Bills of Material attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
ORACLE BILLS OF MATERIAL AND ORACLE ORDER MANAGEMENT ONLY
Warning: Oracle Bill of Materials and Dual Unit of Measure (UOM): When the Tracking UOM for an item is Primary & Secondary (a dual unit of measure), do not select the BOM Allowed check box on the Bills of Material tab. Otherwise, an error occurs when you try to create a BOM with this item in Oracle Bill of Materials.
Allows you to define a bill of material for an item, or to assign the item as a component on a bill.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
ORACLE BILLS OF MATERIAL AND ORACLE ORDER MANAGEMENT ONLY
This attribute is controlled at the Master level only.
Select a type to control bill functionality. You must enter a value here if BOM Allowed is turned on.
| Model | The item's bill of material lists option classes and options available when you place an order for the model item. |
| Option Class | This item's bill of material contains a list of related options. Option classes group like options together. Oracle Order Management does not allow ordering of classes outside a model. |
| Planning | This item's bill of material contains a list of items and planning percentages. A planning item can represent a product family or demand channel. Its bill of material facilitates master scheduling and/or material planning. The total component planning percentages on a planning bill can exceed 100%. Oracle Order Management does not allow ordering of Planning bills. |
| Product Family | This item can be used as a product family for planning at an aggregate level. See: Product Families, Oracle Bills of Material User's Guide. |
| Standard | Any item that can have a bill or be a component on a bill, except planning, model, or option class items. Standard items include purchased items, subassemblies, or finished products. |
This attribute is controlled at the Master level only.
Displays the model from which an ATO configuration was created. In Oracle Order Management, you can place an order for an ATO model, choosing from the list of options. Oracle Bills of Material creates a new configuration item, bill, and routing that captures the chosen options. The configuration item lists the ordered model item as its base model.
Select this checkbox if the item is autocreated. If the base model is null, you cannot select this checkbox.
Indicates that the item was created using Oracle Engineering. This attribute is not updatable.
This attribute is used by Oracle Bills of Material when calculating lead times from the Routings form. See Calculating Lead Times, Oracle Bills of Material User's Guide and Creating a Routing, Oracle Bills of Material User's Guide.
| Date | A concurrent program uses the date as the parameter. |
| Model/Unit Number | A concurrent program uses the Unit Number as the parameter. |
This attributes determines the behavior of configurable models in configurator. The available choices are:
Standard
Container
This item attribute is available only for ATO items. It allows you to create configured item bills of materials based on the following options:
| Based on Sourcing | Based on Item Sourcing |
| Items Based on Model | Item is based on the model. |
| BOM And Routing Based on Sourcing | BOM and routing are based on Sourcing |
| Based on Model | The BOM is based on the Model. |
CTO provides the capability to match existing configurations. You can match the configurations of the models depending on the complexities of the BOM. The available choices are as follows:
| Standard | Matches the configuration based on the standard BOM |
| Container | Matches the configuration based on the container |
| Null | Matches the configuration on the profile options BOM: Match to existing configurations and BOM Use custom match function. |
Following are the Asset Management attributes and their possible values. If the current organization is Enterprise Asset Management (eAM) enabled (Enabling Organizations for Enterprise Asset Management page , Oracle Enterprise Asset Management User's Guide), you can access the Asset Management tab. You can set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
This attribute identifies the asset item as an Asset Group, Asset Activity, or Rebuildable item. When you create any one of these asset item types using a template, this field automatically populates with the appropriate value. See: Defining Asset Groups page , Oracle Asset Management User's Guide, Defining Asset Activities page , Oracle Asset Management User's Guide, and Defining Rebuildable Items page , Oracle Asset Management User's Guide.
This is relevant when the Asset Item Type is set to Asset Activity. This indicates the type of maintenance for this asset activity. You use it to define a generic maintenance work order. For example, Inspection, Overhaul, Lubrication, Repairs, Servicing, or Cleaning. See: Asset Activity Types page , Oracle Asset Management User's Guide.
This is relevant when the Asset Item Type is set to Asset Activity. Specifies what situation caused the work to be generated. For example, Breakdown, Vandalism, Normal Wear, or Settings. See: Asset Activity Causes page , Oracle Asset Management User's Guide.
This is relevant when the Asset Item Type is set to Asset Activity. This specifies the reason the activity needs to be executed. For example, Warranty Compliance, OSHA Compliance, or Military Specification Requirements.
This is relevant when the Asset Item Type is set to Asset Activity. Indicates if this maintenance activity requires a shutdown. For Example, Required and Not Required.
This is relevant only when the Asset Item Type is set to Asset Activity. Indicates if the asset is moveable, and needs to be brought into the shop for repairs. This field is for information only.
Related Topics
Defining Asset Activities, Oracle Asset Management User's Guide
Following are the Costing attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate whether to report, value, and account for any item costs. For example, you might disable costing for reference items, or for invoice only (non-stock) items that you never ship and never hold in inventory.
Important: Organizations using average costing always maintain their own item costs, regardless of the control level set for the Costing Enabled attribute. See: Overview of Cost Management, Oracle Cost Management User's Guide.
This is an item-defining attribute. If you turn this option on, the item is automatically assigned to the default category set for the Oracle Cost Management functional area. See: Item Defining Attributes.
Indicate whether to value an item as an asset in inventory. Turning this option off indicates an expense item.
ORACLE BILLS OF MATERIAL AND ORACLE COST MANAGEMENT ONLY
Indicate whether to include an item in the cost roll up.
This attribute is controlled at the Organization level only.
Enter a general ledger account to use as a source for the Cost of Goods Sold Account. The default cost of goods sold account is set when you define organization parameters. See: Defining Organization Parameters.
ORACLE BILLS OF MATERIAL AND ORACLE COST MANAGEMENT ONLY
Enter the standard lot size Oracle Bills of Material uses to calculate assembly lead times. Oracle Cost Management uses this value to calculate unit costs for sub-elements with a Lot basis type. This lot size is separate from the lead time lot size. See: Calculating Manufacturing Lead Times, Oracle Bills of Material User's Guide and Routings, Oracle Bills of Material User's Guide.
Related Topics
Relationships Between Attributes
Following are the Purchasing attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate whether to purchase and receive an item. Turning this option on allows you to set the Purchasable attribute.
This is an item-defining attribute. If you turn this option on, the item is automatically assigned to the default category set for the Oracle Purchasing functional area. See: Item-Defining Attributes.
If an item is vendor managed, you must turn on this option.
Indicate whether to order an item on a purchase order. You can set this only when Purchased is turned on.
Turning Purchasable off allows you to temporarily restrict the ability to buy. If Purchasable is set to Master Level control, then Purchased must be set to Master Level control.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
Indicate whether to use only approved suppliers. If you turn this option on, Oracle Purchasing prevents you from approving a purchase order for an item if you do not use an approved supplier.
Indicate whether to allow updates to the item description on a purchasing document line for an item. See: Defining Purchasing Options, Oracle Purchasing User's Guide.
Indicate whether this is an outsourced assembly item. Selecting this check box indicates that the assembly item has subcontracting components. You can select this attribute only if you enabled charge base chargeable subcontracting.
Indicate whether to require an item quotation when requesting an item. Oracle Purchasing defaults this value on requisition lines for this item. Leave this field blank if you want Inventory to use the value defined in the Purchasing Options window for transactions involving this item. See: Defining Purchasing Options, Oracle Purchasing User's Guide.
Indicate whether you can add the item to an outside processing purchase order line. You can turn this option on only if Purchased is also on.
In addition, this option controls whether you can attach an item to a resource in the Resource window. See: Defining a Resource, Oracle Bills of Material User's Guide and Outside Processing, Oracle Work in Process User's Guide.
Select an option to determine the quantity of an outside processing item you requisition, purchase and receive:
| Assembly | You purchase an outside processing item based on the number of assemblies you ship to the supplier. |
| Resource | You purchase an outside processing item based on the number of assemblies times the resource usage rate or amount. |
Indicate whether the supplier charges a tax. Oracle Purchasing uses the taxable status together with the tax code you associate with a location to determine whether a purchase order shipment is taxable, and what the tax code that applies to this shipment is. Leave this field blank if you want Inventory to use the value defined in the Purchasing Options window for transactions involving this item. See: Defining Purchasing Options, Oracle Purchasing User's Guide.
Select the appropriate tax code for the item. The tax code shows the tax authorities and rates that are available to use for this item. You must select the taxable attribute to enable this field.
Indicate whether you must receive an item before you can pay the invoice. Leave this field blank if you want Inventory to use the value defined in the Purchasing Options window for transactions involving this item. See: Defining Purchasing Options, Oracle Purchasing User's Guide.
Indicate whether to inspect an item upon receipt from the supplier, before paying the corresponding invoice. Leave this field blank if you want Inventory to use the value defined in the Purchasing Options window for transactions involving this item. See: Defining Purchasing Options, Oracle Purchasing User's Guide.
Enter the buyer assigned to purchase an item. Oracle Purchasing displays the buyer you enter here as the suggested buyer for a requisition. See: Defining Buyers, Oracle Purchasing User's Guide.
Enter the unit of measure you typically use to issue the item from inventory. Oracle Purchasing uses this as the default for internal requisition lines sourced from inventory.
You use units of issue to round order quantities, minimizing shipping, warehousing, and handling costs. The unit of issue must be the same for all units of measure belonging to the same unit of measure class as the primary unit of measure. See: Defining Unit of Measure Classes.
Enter the percentage tolerance Oracle Purchasing uses to automatically close purchase order shipments. Oracle Purchasing automatically closes a shipment when your unreceived quantity is within the quantity tolerance percentage of the shipment.
For example, if the original shipment quantity is 50, and you enter 10 here (10%), Oracle Purchasing automatically closes the shipment for receiving when you receive 45 or more.
Closed for Receiving is a status change only. You can receive additional items against the shipment later.
Enter the percentage tolerance Oracle Purchasing uses to automatically close purchase order shipments. Oracle Purchasing automatically closes a shipment when your uninvoiced quantity is within the quantity tolerance percentage of the shipment.
For example, if the original shipment quantity is 50, and you enter 10 here (10%), Oracle Purchasing automatically closes the shipment for invoicing when you invoice match 45 or more.
Closed for Invoicing is a status change only. You can invoice match additional items against the shipment later.
Enter the United Nations identification number. Oracle Purchasing uses UN numbers to identify specific materials (hazardous materials, for example) for international trade purposes. See: Defining UN Numbers, Oracle Purchasing User's Guide.
Oracle Purchasing uses hazard classes to identify categories of hazardous materials for international trade purposes. See: Defining UN Numbers, Oracle Purchasing User's GuideDefining Hazard Classes, Oracle Purchasing User's Guide.
Enter the value that Oracle Purchasing uses as the default price on a purchase order, requisition, RFQ, or quotation.
Oracle Receivables uses this value as the default unit selling price on a transaction. Note that this is the original inventory item price used by Purchasing and therefore should be used as a guide only.
When performing supplier inventory replenishment, a List Price must be specified in order to automatically generate a requisition.
Enter the market value for an item. Oracle Purchasing copies the market price to the purchase order lines you create.
Enter the price tolerance percent, the maximum price percentage over the normal price range for an item. For example, if the tolerance percent is 5, the maximum acceptable price on a purchase order is 5% over the requisition price. Any purchase order price 5% above the requisition price is unacceptable, and you cannot approve the purchase order.
Enter a number between 0 and 1. This factor determines how to round the quantity on an internal requisition that results from conversions between the requisition line unit of measure and the item unit of issue. This factor insures that the unit of issue resolves to an integer, rather than a fractional amount.
For example, suppose the requisition line unit of measure is each, the unit of issue is dozen. for an internal requisition of 20 each, Oracle Purchasing converts the order quantity to 1.75 dozen. With a rounding factor of 0.6 oracle Purchasing rounds up the order quantity to 2 dozen. (Rounding factor of 0.75 also rounds up to 2 dozen.) With a rounding factor of 0.8, Oracle Purchasing rounds down to 1 dozen.
Oracle Purchasing either performs rounding automatically or advises you of the suggested quantity depending on how you set the purchasing options. See: Overview of Internal Requisitions, Oracle Purchasing User's Guide
ORACLE PURCHASING ONLY
This attribute is controlled at the Organization level only.
Enter the default encumbrance account Oracle Purchasing uses when receiving an item. If the item encumbrance account does not exist, Oracle Purchasing uses the subinventory account. You encumber, or reserve against funds, when the purchase requisition or purchase order is approved. When you deliver into a subinventory you reverse the encumbrance. The total receipts plus encumbrances equals your total funds spent.
This attribute is controlled at the Organization level only.
Enter the default inventory account for expense items. This attribute is used only when Inventory Asset Value is turned off. Oracle Purchasing debits this account when you receive an item into inventory only if the item is expensed. If you receive into an expense subinventory, Oracle Purchasing uses the expense account you assigned to the subinventory. If you do not define the account here, Oracle Purchasing uses the expense account assigned to the item.
ORACLE PURCHASING ONLY
Enter the asset category for the item. Oracle Assets uses this attribute to classify your fixed assets. All assets in a category share default information, such as the accounts used when you post to the general ledger. You can enter this field only if you use Oracle Assets. See: Setting Up Asset Categories, , Oracle Assets User's Guide
Related Topics
Relationships Between Attributes
Following are the Receiving attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
| None | No receipt date exception enforced. |
| Reject | Reject receipts when the receive date is outside the range defined by Days Early Receipt Allowed or Days Late Receipt Allowed. |
| Warning | Display a warning message if you attempt to receive an item outside the range defined by Days Early Receipt Allowed or Days Late Receipt Allowed, but perform the receipt, anyway. |
Enter the number of days before the promise date you can receive an item without warning or rejection. For example, if you enter 3 and the promise date is a Friday, you can receive the item on Tuesday.
Note that Oracle Purchasing uses regular calendar days (including weekends and holidays) in this calculation.
If the promise date does not exist, Oracle Purchasing uses the need by date.
Enter the number of days after the promise date you can receive an item without warning or rejection. For example, if you enter 2 and the promise date is a Monday, you can receive the item on Wednesday.
Note that Oracle Purchasing uses regular calendar days (including weekends and holidays) in this calculation.
If the promise date does not exist, Oracle Purchasing uses the need by date.
| None | No over tolerance enforced. |
| Reject | Reject receipts over the tolerance quantity. You receive an error message and are prevented from receiving quantities exceeding the order quantity by more than the Quantity Received Tolerance percent. |
| Warning | A warning message displays if you accept receipts over the quantity determined by the Over-Receipt Quantity Control Tolerance percent, but does perform the receipt. |
Enter the quantity received tolerance percent, the maximum acceptable over-receipt percentage, used by the Over-Receipt Quantity Control Action attribute. For example, if the tolerance percent is 5, then the acceptable quantity on a receipt transaction is within 5% of the quantity you order on a purchase order line. Any quantity more than 5% over the order quantity is unacceptable.
Indicate whether to allow receipt of defined substitutes in place of this item. You define valid substitutes with the Item Relationships window. See: Defining Item Relationships. Leave this field blank if you want Inventory to use the value defined in the Receiving Options window for transactions involving this item. See: Defining Receiving Options, Oracle Purchasing User's Guide.
Indicate whether you can receive an item without a purchase order. If this option is on, you can later match the receipt to the appropriate purchase order. If this option is off, all receipts for an item must have a corresponding purchase order. Leave this field blank if you want Inventory to use the value defined in the Receiving Options window for transactions involving this item. See: Defining Receiving Options, Oracle Purchasing User's Guide.
Indicate whether you can deliver all distributions for this item with one data entry transaction if the quantity to deliver equals the purchase order line balance. If this option is turned off, you must deliver individual distributions separately. Leave this field blank if you want Inventory to use the value defined in the Receiving Options window for transactions involving this item. See: Defining Receiving Options, Oracle Purchasing User's Guide.
| Direct | At receipt, deliver an item directly to its location. |
| Inspection | Receive an item first, inspect it, then deliver. |
| Standard | Receive an item first, then deliver without inspection. |
Select an option to control whether the supplier can deliver to a location that differs from the ship-to location defined on the purchase order:
| None | No ship-to location enforced. |
| Reject | Prevent receipt of items not received to their purchase order ship-to location. |
| Warning | Display a warning message if you attempt to receive an item to a location that differs from the purchase order ship-to location, but perform the receipt, anyway. |
Sets the default subinventory for receiving.
Related Topics
Relationships Between Attributes
Following are the Physical item attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Enter a weight unit of measure.
Enter the weight for one unit of the item in the Weight Unit of Measure.
Enter a volume unit of measure.
Enter the volume for one unit of the item in the Volume Unit of Measure.
Select Container to identify items that are containers used for shipping sales orders.
Select Vehicle to identify items that are vehicles used for shipping sales orders.
For items identified as containers, enter the container type. See: Defining Container Types.
Enter the internal volume of the container or vehicle in the same UOM as the Unit Volume. This attribute is used by shipping to calculate container capacity restrictions.
Enter the maximum load weight of the container or vehicle in the same UOM as the Unit Weight.
Enter the minimum fill percentage under which the container or vehicle should be used.
Dimension unit of measure for an item.
Indicate whether the item is collateral. When you register collateral as a promotion in Oracle Sales and Marketing, you can link it to the item you define here. Then you can use Oracle Sales and Marketing to include this collateral item in a fulfillment request for a contact or a mass mailing. Oracle Sales and Marketing displays a list of valid collateral when creating a fulfillment request or mass mailing, based on the items you define with this flag.
Indicate whether the item created is an Event item. See: Event, Oracle Marketing User's Guide
Indicate whether this is an Equipment item, used in Oracle Warehouse Management. See, Set Up or Verify Equipment Items, Oracle Warehouse Management Implementation Guide.
Indicate whether this item exists only in electronic format and not physical. This attribute is used in Oracle Marketing.
Indicate whether this item is downloadable. This attribute is used in Oracle Marketing.
Indicate whether this item can be ordered in fractions. This attribute support indivisible units of measure.
Related Topics
Relationships Between Attributes
Following are the General Planning attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Select an option for organization level planning. See: Assigning Subinventories to an Item or Assigning Items to a Subinventory.
| Min-max | You define a minimum quantity that you want on hand. When you reach this quantity, you reorder. You also define a maximum on-hand quantity that you do not want to exceed. |
| Not planned | No planning method used. Select this option for MRP/MPS planned items. |
| Reorder point | The reorder point is calculated based on the planning information you define for this item. |
This attribute is controlled at the Organization level only.
Enter the material planner assigned to plan this item. You must define planner codes for your organization before updating this attribute. See Defining Planners, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
The planner defined here is responsible for approving all move order lines requesting the item if move order approvals are used. See Overview of Move Orders.
If an item is vendor managed, you must enter a planner for the item.
Indicate the subcontracting type associated to this item when it is used as a subcontracting component in Chargeable Subcontracting. The available choices are:
Pre-positioned: The item is a subcontracting component sold to a manufacturing partner independently of subcontracting components.
Synchronized: The item is a subcontracting component sold to a manufacturing partner and is synchronized with a specific order.
This attribute is controlled at the organization level.
Select the option that applies to items with Inventory Item set to Yes. The Planner Workbench uses this to default an appropriate value for implementation type. You cannot change the value of the flag if open orders exist for the item.
| Make | Usually manufactured. The Planner Workbench defaults the implementation type Discrete job. The planning process passes demand down from manufactured items to lower level components. |
| Buy | Usually purchased. The Planner Workbench defaults the implementation type to Purchase Requisition. The planning process does not pass demand down from purchased items to lower level components. |
Important: You must also set Purchasable to Yes to create purchase requisitions and purchase orders. If you set Build in WIP to Yes, you can use the Planner Workbench to implement planned orders as discrete jobs.
See Overview of Material Requirements Planning and Creating Planning Exception Sets, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
Enter the quantity minimum for min-max planning. If an item is min-max planned, the Min-Max Planning Report suggests a new order when quantity drops to the min-max minimum. See: Min-Max Planning.
Enter the quantity maximum for min-max planning. If an item is min-max planned, the Min-Max Planning Report suggests an order that brings on-hand up to the min-max maximum. See: Min-Max Planning.
Enter the 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 is unprofitable to build the item. See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide, and Overview of Inventory Planning and Replenishment.
Enter the 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. See Overview of Material Requirements Planning, Overview of Repetitive Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide, and Overview of Inventory Planning and Replenishment.
Enter the fixed cost associated with placing an order of any quantity.
Enter the 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.
| Inventory | Fill requests by creating internal requisitions that become internal sales orders, pulling stock from existing inventory. |
| Supplier | Fill requests by creating purchase requisitions that become purchase orders, procuring the item from a supplier. |
| Subinventory | Fill requests by creating move order requisitions that become move orders, pulling stock from an existing subinventory. |
Important: If you are using Supplier Scheduling, it is generally recommended that this field be left blank. Otherwise, it could override your sourcing rules.
This attribute is controlled at the Organization level only.
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:
the item is assigned to the source organization
the source organization has a valid inter-organization relationship with the current organization
See: Defining Inter-Organization Shipping Networks.
The source organization can be your current organization if the item is MRP planned and you choose a non-nettable Source Subinventory.
This attribute is controlled at the Organization level only.
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.
Select an option to plan use of fixed or dynamically calculated safety stock quantities. For MRP/MPS planned items, you must set the Inventory Planning Method attribute to Not planned, then choose the MRP planned percent option here.
| MRP planned percent | Calculate safety stock as a user-defined percentage (Safety Stock Percent) of the average gross requirements for a user-defined number of days. For discrete items, the user-defined number of days is the Safety Stock Bucket Days. For repetitive items, the user-defined number of days is the repetitive planning period. Note that safety stock for an item varies as the average gross requirements vary during the planning process. |
| Non-MRP planned | Calculate safety stock using methods defined by the Enter Item Safety Stocks window. You can use mean absolute deviation or user-defined percentage of forecasted demand. For Oracle Master Scheduling/MRP and Oracle Supply Chain Planning and Supply Chain Planning, these safety stock quantities are fixed. The Snapshot portion of the planning process loads them, and they do not vary during the planning process itself. |
See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide, Entering and Reloading Item Safety Stocks, and Overview of Inventory Planning and Replenishment.
ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY
Enter the number of days to dynamically calculate safety stock quantities. The planning process multiplies the Safety Stock Percent by the average gross requirements and divides by the number of days you enter here. See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY
Enter the percent to dynamically calculate safety stock quantities for the item. The planning process multiplies this percent by the average gross requirements.
The planning process uses this attribute when you set Safety Stock to MRP planned percent. See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY
Enter the 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. See Overview Material Requirements Planning and Overview of Repetitive Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY
Enter the 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. See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
Enter the fixed lot multiple 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.
When net requirements fall short of the fixed lot size multiplier quantity, planning algorithms suggest a single order for the fixed lot size multiplier quantity.
This is the minimum quantity allowed before replenishment occurs.
This is the minimum allowed days of supply before replenishment must occur.
This is the maximum quantity allowed for replenishment reorder
This is the maximum allowed days of supply for replenishment reorder.
This is a fixed quantity for reorder.
Authorization is require before a sales order is created. You can set the authorization as follows:
Customer: You must obtain release authorization from the customer.
Supplier: You must obtain release authorization from the supplier.
None: Release authorization is not required.
If selected, the item is consigned, meaning residing at your location, but owned by the supplier.
If selected, the advanced shipment notice for the item expires.
This can have one of the following values:
Order Forecast
Sales Forecast
Historical Forecast
Following are the MPS/MRP Planning item attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
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. See: Order Management Attribute Group. |
| 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 Item Defining Attributes.
See Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
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.
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.
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.
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.
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.
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.
If selected, the item is excluded from the budget.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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. |
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.
Indicates whether you use a convergent consumption pattern in planning. The available choices are: Series, Parallel, and Use Global Value.
ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY
This attribute enables you to perform continuous interorganization transfers.
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
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.
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
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.
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.
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.
Following are the Lead Times attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
This attribute is controlled at the Organization level only.
Enter the days you must add to purchasing or manufacturing lead time to place an order.
This attribute is controlled at the Organization level only.
Enter the days required to procure or manufacture an item. For manufactured assemblies, processing days equals manufacturing lead time.
This attribute is controlled at the Organization level only.
Enter the days required to receive a purchased item into inventory from the initial supplier receipt. You cannot enter a value if the Make or Buy attribute is set to Make. See: MPS/MRP Planning Attribute Group.
This attribute is controlled at the Organization level only.
Enter the days required to make an assembly independent of order quantity, such as setup or teardown time.
This attribute is controlled at the Organization level only.
Enter the time to produce one additional unit of an assembly. Total lead time is variable lead time multiplied by order quantity, plus fixed lead time.
This attribute is controlled at the Organization level only.
Enter the 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.
This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material. See: Rolling up Cumulative Lead Times, Oracle Bills of Material User's Guide.
This attribute is controlled at the Organization level only.
Enter the 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.
This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material. See: Rolling up Cumulative Lead Times, Oracle Bills of Material User's Guide.
Enter the quantity used to compute processing lead time (as well as fixed and variable lead times). The default value is the item's standard lot size or, if a standard lot size is not defined, the default is 1. See: Costing Attribute Group.
Related Topics
Relationships Between Attributes
Overview of Lead Time Management, Oracle Bills of Material User's Guide
Following are the Work In Process attributes and their possible values. You set these attributes when defining or updating items. See Defining Items and Updating Organization Level Items.
Indicate whether to create discrete jobs or repetitive assemblies in Oracle Work in Process. See Defining Discrete Jobs Manually, Oracle Work in Process User's Guide and Defining Repetitive Schedules Manually, Oracle Work in Process User's Guide.
This attribute must be turned off if the Inventory Item attribute is turned off or if the BOM Type attribute is not set to Standard.
This attribute is optionally set by the Item Status code. SeeStatus Attributes and Item Status Control.
Select a supply type for components. See Supply Types, Oracle Work in Process User's Guide, Overview of Material Control, Oracle Work in Process User's Guide, Overview of Material Requirements Planning, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide, and Standard Costing, Oracle Cost Management User's Guide.
This attribute is controlled at the Organization level only.
Enter the primary subinventory from which to issue (push) or backflush (pull) an item to work in process.
This attribute is controlled at the Organization level only.
Enter the supply locator from which to issue (push) or backflush (pull) an item to work in process. You can also define a WIP supply locator for any bill that uses this item; the bill supply locator overrides the supply locator you define here. You must enter a WIP supply subinventory before you can enter a locator.
Select Percent or Amount, or leave the field blank. If you do not select an Overcompletion Tolerance Type, the tolerance defaults to the tolerance that you set at the organization level. If you did not set a tolerance at the organization level, the default is Null, which signifies that no over-completions are allowed.
The value for this attribute is the number value for the Overcompletion Tolerance Type that you selected. It determines the acceptable percent or quantity of assemblies that you will allow to be over-completed. For example, if you choose Percent as the Overcompletion Tolerance Type, and enter 100 as the Overcompletion Tolerance Value, you allow over-completions up to 100 percent of the original job or schedule quantity. If you did not select an Overcompletion Tolerance Type, you will not be able to enter a value in this field.
Specify, in units per day, an Inventory Carry penalty for jobs that are not completed before they are scheduled to be finished. For example, the Inventory Carry penalty for a job that is not completed for an item might be 10 per day.
Specify, in units per day, the operation slack penalty for items having lag time between operations.
Related Topics
Relationships Between Attributes
Overview of Lead Time Management, Oracle Bills of Material User's Guide
Following are the Order Management attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate whether to allow an item to be ordered by external customers. You can add any customer orderable items to price lists in Oracle Order Management. This attribute must be turned off if the BOM Item Type attribute is set to Planning. See: Bills of Material Attribute Group.
If you turn this attribute on, you can temporarily exclude an item from being ordered by turning Customer Orders Enabled off.
This is an item-defining attribute. If you turn this attribute on, the item is automatically assigned to the default category set for the Oracle Order Management functional area. See: Item Defining Attributes.
Indicate whether an item is currently customer orderable. If you turn this attribute on you can specify the item in the Enter Orders window in Oracle Order Management.
You can initially define an item with Customer Ordered Item turned on and Customer Orders Enabled turned off. This means prices can be defined for the item, but no orders can be placed for it.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
Indicate whether to allow an item to be ordered on an internal requisition.
If you turn this attribute on, you can temporarily exclude an item from being ordered on an internal requisition by turning Internal Orders Enabled off. See: Overview of Internal Requisitions, Oracle Purchasing User's Guide.
This is an item-defining attribute. If you turn this attribute on, the item is automatically assigned to the default category set for the Oracle Purchasing functional area. See: Item Defining Attributes.
Indicate whether you can currently order an item internally. If you turn this attribute on, you can specify the item on an internal requisition, if Internal Ordered Item is also on.
If you turn Internal Ordered Item on, you can temporarily exclude an item from being ordered on an internal requisition by turning this attribute off.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
ORACLE SHIPPING EXECUTION ONLY
Indicate whether to ship an item to a customer. Shippable items are released by Oracle Shipping Execution's Pick Release program, creating confirmable shipping lines, and are printed on the pick slip. A warning is issued if you change the value of this attribute when open sales order lines exist.
This attribute must be turned off if the BOM Item Type attribute is set to Planning. See: Bills of Material Attribute Group.
Indicate whether demand can be placed for an item by Oracle Order Management, and whether shipment transactions are interfaced to Oracle Inventory. Most items with Shippable turned on also have OE Transactable turned on. For items you do not ship, you may still want OE Transactable turned on if you use the items in forecasting or planning. If you also want to reserve the item, turn Reservable on. A warning is issued if you change the value of this attribute when open sales order lines exist. You cannot turn this attribute off if demand exits.
ORACLE SHIPPING EXECUTION ONLY
Enter the Oracle Shipping Execution primary shipping organization. This organization defaults to the Enter Orders window if Item is the source attribute of the Warehouse object in the standard value rule set for the order. This organization defaults to the Enter Returns window if a receiving warehouse is not defined on the customer or order type.
This item attribute determines if an item is to be drop-shipped. If the value is internal, the item will not be drop-shipped. If the value is external, the item will be drop-shipped. See Drop Shipments, Oracle Order Management User's Guide.
Enter the picking rule that defines the order in which subinventories, locators, lots, and revisions are picked. See: Defining Picking Rules.
This rule will not be employed in WMS enabled organizations. See: Defining Default Inventory Parameters. Oracle Warehouse Management picking rules will be used. See: Overview of WMS Rules Engine, Oracle Warehouse Management User's Guide.
Indicate whether an item has a bill of material with options, classes, or included items picked from finished goods inventory. Pick-to-order items must have this attribute turned on. Assemble-to-order items and items without a bill of material must have this attribute turned off.
You should turn Pick Components on only if the Planning Method attribute is set to Not Planned. See: MPS/MRP Planning Attribute Group.
Turn this attribute on if an item is generally built for sales order demand; a final assembly work order is created based on sales order details. You must turn on this attribute if you auto create requisitions.
An item cannot have Pick Components turned on and this attribute turned on at the same time. See: Configure to Order, Oracle Bills of Material User's Guide.
Select Check Material Only, Check Material and Resources, Check Resources Only, or None to indicate whether to check available to promise and/or capable to promise information when placing demand. See Available to Promise and Capable to Promise, Oracle Master Scheduling / MRP and Oracle Supply Chain Planning User's Guide.
This attribute also determines whether you can view component ATP information for material requirements in Work in Process.
Indicate whether to include, in available to promise checking, additional components in the bill of material for ATO and PTO items. These components are included in ATP checking if Check ATP for the component is turned on.
Enter a user-defined available to promise rule. ATP rules define supply and demand sources, time-fence parameters, and available-to-promise calculation methods. You can give ATP rules meaningful names, such as ATO ATP Rule.
If there is no ATP rule for the item, the organization's default ATP rule is used. See Defining Organization Parameters.
Sets the default subinventory for shipping.
The time the system uses to price a persistent or recurring service or product. The system derives the list of values for this attribute from the profile option OM: UOM Class for Charge Periodicity. Each UOM in this class is a periodicity value. An item has only one periodicity value, and the default value is null.
This attribute is controlled at the master organization level.
Indicate whether any configuration derived from this model can ship only when all required quantities of all configuration components (options or included items) are available.
If you turn this attribute on, the Pick Components attribute and the profile option OE: Reservations must be Yes; the BOM Item Type attribute can be Model or Standard.
Indicate whether to allow customers to return an item. If an item is returnable, you can enter it on the Returns window in Oracle Order Management. Order Management uses this attribute along with Stockable and Transactable to determine which authorized returned items you can physically receive into inventory.
Indicate whether inspection is required for items returned by the customer. The item then must be separately transferred to inventory. Credits are never automatically generated by Oracle Order Management for customer return items awaiting inspection.
Indicate whether a customer can finance this item.
Enter the Over Shipment Tolerance percentage. This determines the amount of the shipment you can exceed at the time of ship confirmation.
Enter the Under Shipment Tolerance percentage. This determines the amount of the shipment you can ship below at the time of ship confirmation. When shipping confirms shipped quantities for the shipments belonging to an order, Shipping Execution will validate any further shipments pending for the order or return. If there are pending shipments, Shipping Execution will calculate the new tolerance value. If the new shipping tolerance level is less than the old tolerance level, Order Management notifies you of the shipped quantity and the new tolerance value. Order Management determines whether the total shipped quantity for the order or return is within the under shipment tolerance value, and closes the line as an under shipment.
Enter the Over Return Tolerance percentage. This determines the amount of the shipment you can exceed at the time of receiving or receipt creation.
Enter the Under Return Tolerance percentage. This determines the lower limit of the received quantity to be considered as full receipt.
Following are the Invoicing attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate whether to include an item on an Oracle Receivables invoice. If you turn this option on, you can temporarily exclude from invoicing when Invoice Enabled is turned off. This option must be on if Invoice Enabled is on.
Indicate whether to activate an item for invoicing in Oracle Receivables. If Invoiceable Item is turned on, you can temporarily exclude from invoicing by leaving Invoice Enabled turned off.
If you turn this option on, the item appears in the Invoice Entry item list of values in Oracle Receivables. If you turn this feature off, the item does not appear in the list of values and AutoInvoice rejects the item.
This attribute is optionally set by the Item Status code. See: Status Attributes and Item Status Control.
Enter an accounting rule to identify special revenue recognition rules for an item, such as recognizing revenue over time. See: Defining Invoicing and Accounting Rules, Oracle Receivables Reference Manual, Release 10.
This attribute is for reference information only.
Enter an invoicing rule to determine the period in which you send an invoice when you recognize revenue over time.
ORACLE RECEIVABLES AND ORACLE ORDER ENTRY ONLY
Enter a tax code to use when calculating tax based on location and tax codes. You assign specific rates to a Tax Code in the Other Tax Rates window. See: Defining Other Tax Rates, Oracle Receivables Reference Manual, Release 10.
This attribute is controlled at the Organization level only.
Enter the general ledger account Oracle Receivables uses to record revenue when you bill the customer. If AutoAccounting is based on items, accounting entries are created at that time. See: Defining AutoAccounting, Oracle Receivables Reference Manual, Release 10.
Enter a valid payment terms code. This attribute is for reference information only.
The following are the Process Manufacturing attribute and their possible values. You set these attributes when you define or update items. See: Defining Items and Updating Organization Level Items
Select this check box if you plan to use the process manufacturing quality module with this item. You must select this check box if you plan to create samples and specifications for this item.
Select this check box if you plan so use the process costing module with this item. You must enabled the Inventory Asset attribute to enabled process costing. If the organization is process manufacturing enabled, the master level and organization level control does not apply for costing. The system stores costs for each organization and if multiple organizations need to use the same cost, then you must perform the setups in process costing.
Select this check box to enable use of this item in recipes or formulas in process manufacturing. You can modify this attribute at any time, however; if you deselect the check box you cannot use this item in future recipes.
Note: This attribute is not mutually exclusive with the BOM allowed attribute.
Indicate if the item is hazardous.
Indicate the CAS number. The CAS uniquely identifies a chemical substance. The CAS scientists assign a CAS registry number to a substance when it enters the CAS registry database. The CAS scientists identify new substances and assign them in sequential order in the database.
Select this check box if you plan to use this item in a production batch as an ingredient, product, or by-product. This attribute is not mutually exclusive of the Build in WIP attribute. You can set both attributes to yes to use the item in both WIP and process manufacturing.
Enter a subinventory from which the item is normally consumed as an ingredient in process manufacturing. This subinventory represents the production shop floor or the staging area.
Enter a locator from which the item is normally consumed as an ingredient in process manufacturing.
Enter a subinventory in which you place results of a production batch.
Enter a locator in which you place the results of a production batch.
Following are the Service attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate the contract item type.
| Service | Days and times of coverage, reaction times, billing types, resolution times and preferred resources. A service is defined with a list price and may be sold from Oracle Order Management or Oracle Service Contracts. If sold from Order Management, the service may cover an item on an order or a customer product in the Install Base. If sold from Oracle Service Contracts, the service can be defined to cover a customer product or set of products in Oracle Install Base. |
| Subscription | These can represent intangible or tangible items. Tangible items can be shipped, counted or tracked by the Install Base. The recommended channel to sell subscription items is Oracle Service Contracts because it supports recurring billings, flexible shipping patterns and ongoing management of the subscription agreement. |
| Usage | Usage Items are used to facilitate metered billing in Oracle Service Contracts. Price breaks defined in Oracle Advanced Pricing are used to calculate the usage bill. |
| Warranty | Days and times of coverage, reaction times, billing types, resolution times and preferred resources. A warranty is sold in Order Management along with the product as a component of a bill of material configuration. It has no associated list price in the price list and is never sold stand alone. |
| Null | This is the default value for non-contract item types. |
Enter the template associated with the contract item type. A template is mandatory for service and warranty, and optionally for subscription. For service and warrant, the template is a coverage template and represents days and times of coverage, reaction times, resolution times, preferred resources and billing types.
For subscriptions, the template is a subscription template and represents the subscription type, media type, fulfillment channel and frequency of the subscription.
For tangible subscription items, the fulfillment channel is Order Management. When the subscription contract is defined, the Order Management interface schedule is automatically generated depending on the frequency i.e. daily, weekly, monthly, yearly, etc. If the subscription item is intangible there is no fulfillment channel. Both the subscription template and the coverage template are defined in Oracle Service Contracts.
Enter a positive number to indicate the service duration. Duration and Duration Period are required for warranty and service contract item types only. The number you enter here along with the duration period e.g. Month, Year, provide defaults when you order the service in Oracle Order management. You can select any period or unit of measure as long as it is associated with the Time unit of measure class.
Selecting a value for Billing Type allows the item to be used in the Task Debrief and Service charges windows. Billing Types are user definable and must be tagged with one of three Billing Category Codes as follows: material (M) labor (L) or Expense (E). Billing Types are used in Contracts to define Discount Percents.
Select if you can create a service request for the item. The available choices are:
Enabled: You can create a service request for the item.
Disabled: Service requests are disabled for the item.
Inactive: Service requests are inactive for the item.
Null: You cannot create a service request for the item.
Select the check box to make the item eligible for electronic fulfillment by the service fulfillment manager. Additional setup is required in the service fulfillment manager.
Indicate whether the item is eligible to be covered by a service contract. Items eligible for contract coverage must also be defined as Track in Installed Base. When you turn on this option, you can order service for this item either in Oracle Order Management, or from Oracle Service Contracts.
Select the check box to enable the Billing Type field.
Indicate if you want to track defects of this item.
This field is planned for future use. Currently all three disposition types cause the part to be transacted into the technician's default or designated subinventory. In the future this field will control the process for returning defective or unused parts to a warehouse consolidation point.
This flag enables life cycle tracking in Install Base and enterprise Install Base applications. Once set, you should not change this flag. Set this flag at the master item level.
This flag is used in Telecommunication Service Ordering for defining a configured link. The only available option is Link. This is only applicable when Installed Base Tracking is on.
Enter a positive number indicating how many days after shipment the warranty should start. The warranty start date is determined by adding the ship date plus the Service Starting Delay. If the installation date is entered on the order, it is used instead of the ship date to determine the warranty start date.
This indicates whether the item creates a depreciable inventory asset used in Enterprise Install Base. A value of Yes is only applicable when you turn on Installed Base Tracking.
Related Topics
Relationships Between Attributes
Following are the Web Option attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.
Indicate the web status of this item.
| Disabled | This item is not web enabled. |
| Published | This item is web enabled, and published. |
| Unpublished | This item is web enabled, and unpublished. |
Indicate whether this item is orderable on from the web. Oracle iStore can sell items with this attribute enabled.
Indicate whether this item can be backordered, it ATP fails.
This attribute identifies the minimum number of licenses a customer must order for products ordered on Oracle iStore and distributed based on licensing.
Related Topics