Item Basic Attributes

The following are the basic attributes and their possible values. You set these attributes when you define or update items.

A few attributes might not be displayed on the user interface because it's hidden.

Attribute Group	Attribute Name	Description
Descriptions	Item	Name of the item.
	Description	Description for the item.
	Long Description	Long description for this item. This long description is supported in multiple languages.
	Formatted Description	Description of the item using a rich text component, that can be displayed by various downstream applications.
Main	Item Status	Approval status of the item.
	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
	Completeness Score	Percentage of completeness for an item based on the values that are returned for specific attributes
	Created By	Person who has created the item
	Creation Date	Date when the item was created
	Approval Status	Approval status of the item.
	Item Object Type	Indicates the object type for the item.
	User Item Type	Oracle provides several types by default at installation. These types correspond to the item templates. Note: When creating an item, User Item Type lists only the enabled user item types and doesn’t list the disabled user item types. When updating an existing item, User Item Type lists both the enabled and disabled user item types. However, if you select a disabled item type, it displays an error.
	Engineered	Indicates whether the item is an engineered item. 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. 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 Number These constraints are applicable only from the UI perspective. You can create, edit, or query the previous objects using web services and imports. If the Engineered option is Yes for an item, such items aren’t visible in other modules.
	Preliminary	Indicates whether the item is a preliminary item.
	Pack Type	Global Trade Item Number (GTIN) hierarchy level. Hierarchy is used as link between different levels of a product (item) logistical chain. Pack type is also known as Trade Item Unit Descriptor (TIUD).
Unit of Measures	Primary Unit of Measure	Stocking and selling unit of measure. Any necessary conversions are based on this unit of measure. This attribute is assigned at the organization level.
	Tracking Unit of Measure	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.
	Pricing	This attribute is assigned at the organization level. Indicates 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 shipment 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 DefaultingControl 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 doesn’t 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.
	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.
	Defaulting Control	Use this option when the default conversion between the two units of measure is usually not the same. The available values are: 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. 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.
	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'd enter 10 in this field.
	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'd enter 10 in this field.
	Conversions	Indicate the conversion of the transactions: Item specific: Use only unit of measure conversions unique to this item. Standard: Use only standard unit of measure conversions. To use only standard conversions, don’t create item specific conversions. Both: Use Item-specific and Standard. To redline user item type for both engineering and commercialization change orders, use the simplified change management interface.
	Packaging String	If one of your items has a non-standard UOM conversion specific to that item itself, you can add a predefined packaging string when you create or edit an item or define a new packaging string to fit your requirements. For details about packaging strings, see Add Packaging Strings to Items.