Total Pageviews

May 1, 2016

5/01/2016 12:09:00 AM

A conversion common to any item (Standard)
A conversion for a specific item within a unit of measure class
(Intra–class)
A conversion for a specific item between unit of measure classes (Inter–class)

NOTE: You must define a conversion between a non–base unit of measure and the base unit of measure before you can assign the non–base unit of measure to an item.

When you define an item you decide which type of unit of measure conversion to use:

Item specific: Only uses unit of measure conversions unique to this item. If none exist, you can only transact this item in its primary unit of measure.

Standard: Uses standard unit of measure conversions for this item if an item–specific conversion is not available.

Both: Uses both item–specific and standard unit of measure
conversions. If both exist for the same unit of measure and item combination, the item–specific conversion is used.

Item Master Organization: you define an item in the Item Master, you can assign it to any number of other organizations.

There is no functional or technical difference between the Item Master organization and other organizations. However, for simplicity, Oracle recommends that you limit the Item Master to just an item definition organization.

You cannot associate items in one item master organization with
another item master organization.

Information such as unit of measure, description, and so on is
maintained at the Master level.


There are two types of attribute control:
Master Level
Item level.

A status code controls certain item attributes designated as status attributes. These attributes control the functionality of an item over time.

The status attributes are:
– BOM Allowed
– Build in WIP
– Customer Orders Enabled
– Internal Orders Enabled
– Invoice Enabled
– Transactable
– Purchasable
– Stockable

An item-defining attribute identifies the nature of an item. What designates an item as an “engineering item” is the attribute Engineering Item, but what controls the functionality of the item are the collection of attributes that describe it. You can buy an engineering item if you want to; simply set Engineering Item, Purchased, and Purchasable to Yes.

Each status attribute is dependent on the value of at least one other attribute. For example, you cannot set Stockable to Yes if you set Inventory Item to No.


What are pending statuses:
We use pending statuses to automatically update an item’s status on a specified date. For each item, specify a list of pending statuses and the corresponding effective dates.

What are the relationships between attributes?

When you define items, Oracle Inventory enforces particular
relationships between some of the item attributes:

Required attribute—you must enter a value for the attribute
based on the settings for other related attributes.

Interdependent attributes—you can enter only certain values
depending on other attribute values.

Updatable attributes—you can update values under certain
conditions.

Control level dependencies—you can update the control level of
some attributes only under special conditions and with certain
consequences.


What are the item attribute controls we have?
Centralized control (Master level)
Decentralized control (item level)

What are the status settings we have for status attribute?

Defaults Value: Value of this attribute, as defined by the status code, defaults when you assign the status to an item. You can change this default value.

Not Used: Use neither default nor status control.

Sets Value: Value of this attribute, as defined by the status code, defaults when you assign the status to an item. Once assigned, you cannot change the default.