Item Main Specifications
The following are the item main specification attributes and their possible values. You set these attributes when defining or updating items.
Item Main Specification Attributes
Approval Status
The approval status of the item.
Engineered
Indicate whether the item was created in Product Development or Product Information Management. If the value is Yes, then the item was created in Product Development. If the value is No, then the item was created in Product Information Management. You can’t change the value of this attribute. However, if you create an item in Product Information Management, you can’t set the Engineered option to Yes.
The following validations and rules apply to the Engineered option:
-
If the Engineered option is Yes for an item, then you can’t change the lifecycle phase of the item from Design lifecycle phase to any other phase in Product Information Management. The Change Lifecycle Phase action is disabled and unavailable on the UI.
-
You can’t create a new item revision when the Engineered option is Yes for the item and the lifecycle phase is Design. The Manage Revision action is disabled and unavailable on the UI.
-
If the Engineered option is Yes for an item, then in the Design Lifecycle Phase, the following objects are disabled and unavailable on the UI:
Structures tab
MPN (Manufacturer Part Number)
Item Revision Attachment
These constraints are applicable only from the UI perspective.
-
You can create, edit, or query the previous objects using web services and imports from Product Development.
-
If the Engineered option is Yes for an item, such items aren’t visible in other modules.
-
In the create item by copy flow, you can’t view items in the source list of values when the Engineered option of the item is Yes and the item is in the Design lifecycle phase.
Item Description
Enter a description for the item.
Formatted Description
Indicate the description of the item using a rich text component, that can be displayed by various downstream applications.
Item Status
Item status codes set or default the values for attributes in status control. Predefined item status codes are Active and Inactive. Both predefined and user-defined item status codes control certain item attributes designated as status-controlled attributes. All of the status-controlled attributes have the values Yes and No. The status-controlled attributes are:
Attribute Group |
Attribute |
---|---|
Costing |
Costing Enabled |
Costing |
Inventory Asset Value |
Inventory |
Inventory Item |
Inventory |
Stocked |
Inventory |
Transaction Enabled |
Invoicing |
Invoice Enabled |
Invoicing |
Invoiced |
Process Manufacturing |
Hazardous Material |
Process Manufacturing |
Process Execution Enabled |
Process Manufacturing |
Recipe Enabled |
Purchasing |
Purchasable |
Purchasing |
Purchased |
Purchasing |
Taxable |
Sales and Order Management |
Customer Ordered |
Sales and Order Management |
Customer Orders Enabled |
Sales and Order Management |
Internally Transferable |
Sales and Order Management |
Transfer Orders Enabled |
Service |
Enable Contract Coverage |
Web Store |
Orderable on the Web |
Work in Process |
Build in WIP |
These attributes control the functionality of an item over time
Lifecycle Phase
Each phase represents a set of tasks and deliverables that are required before promoting the object to the next phase of the item life cycle
For example, the life cycle phases for a computer component life cycle might be:
Concept
Design
Prototype
Pre-Production
Production
Retirement
Pack Type
Also known as Trade Item Unit Descriptor (TIUD)
Describes the Global Trade Item Number (GTIN) hierarchy level. Hierarchy is used as link between different levels of a product (item) logistical chain.
Style Item
A Style represents a silhouette or model item use to group multiple similar items (SKUs) within. Generally, the items group in a particular style item will be differentiated by 1 or more product variant attributes. Examples include color and size for fashion, flavor and size for grocery.
User Item Type
Oracle provides several types by default at installation. These types correspond to the item templates. Select one of these values:
ATO model
Finished good
Freight
Inventory Type
Kit
Model
Option class
Outside processing model
PTO model
Phantom item
Planning
Product Family
Purchased item
Reference item
Subassembly
Supply item
Conversions
Indicate the conversion of the transactions.
Item specific
Use only unit of measure conversions unique to this item.
Standard
Defaulting Control
Fixed
The application stores inventory in both the primary and secondary units of measure. You can enter an item quantity in one unit of measure, and the application converts the quantity to the secondary unit of measure and displays both quantities.
Default
The application stores inventory in both the primary and secondary units of measure. You can enter an item quantity in one unit of measure, and the application 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 application 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 application doesn’t 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.
Negative Deviation Factor
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 ten percent lower than the established conversion, you would enter 10 in this field.
Positive Deviation Factor
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 ten percent higher than the established conversion, you would enter 10 in this field.
Primary Unit of Measure
This is the stocking and selling unit of measure. Any necessary conversions are based on this unit of measure. This attribute isn’t updatable and assigned at the organization level.
Secondary Unit of Measure
This attribute may be controlled at the Master or Organization level based on the setup.
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.
Tracking Unit of Measure
This attribute controls how on-hand balances are tracked. This attribute is assigned at the organization level. The available values are:
Primary
The application tracks the on-hand balances by the primary unit of measure.
Primary and Secondary
The application tracks the on-hand balances by both the primary and secondary units of measure.
Long Description
Indicate the long description for this item. This long description is supported in multiple languages.
Pricing
This attribute is assigned at the organization level.
Indicate if pricing is based on the primary or secondary unit of measure. If you set the value to secondary, the application reprices the orders line at ship confirmation. You can change the Pricing Unit of Measure (UOM) from Primary to Secondary but not conversely. You can change the pricing UOM only when there are no orders.
When the secondary UOM is available for the item, the Defaulting Control value will determine whether the conversion from primary to secondary quantity is defaulted by the application and that can be over written or fixed. In this case, you can’t edit the converted quantity. The positive and negative deviation factors allow the flexibility to deviate from the converted quantities.
When Defaulting Control is set to No Default, it does not default a value in the down-stream applications. In this case, dual UOM items aren’t supported in order management. Dual UOM items are supported in order management only when the type of the Item Structure is set to Standard.