, , , , , ,

Item Catalog

An item catalog group is a standard set of descriptive elements to which you assign items. Examples of catalog descriptive elements are color, shape, length, and so on.  For example, a textile manufacturer might define pattern attributes such as color, size, texture, and style.

Usage: An electronics company (say Samsung) can use the catalog to incorporate length, breadth and height of each mobile it produces. As the company Samsung also produces other electronics products such as TV, Refrigerator and etc. We should first create an item category as mobile and then create a catalog group as mobile-catalog with three catalogs length-breadth and height.

Defining and Using Item Catalogs
Follow these steps to define and use item catalogs:
1 Define the item catalog group.

2 Define descriptive elements within each catalog group.

3 Enter categories for the catalog groups.

Items belonging to the above category are attached with the descriptive element of the catalog.
4 Enter descriptive element values for each item.

5 Update item descriptions with catalog group and descriptive element values.

6 Search for items using descriptive elements as the search criteria.
 

Seraching all the items with bredth 20.

/by
, , , , , ,

Default Category Sets

set to each of the following functional areas: Inventory, Purchasing, Order Management, Costing, Engineering, and Planning. Product Line Accounting is seeded with the Inventory category set. Inventory makes the default category set mandatory for all items defined for use by a functional area. If your item is enabled for a particular functional area you cannot delete the item’s corresponding default category set assignment. Default category sets are required so that each functional area has at least one category set that contains all items in that functional area.
You can enable an item for each functional area by using that functional area’s item defining attribute. An item defining attribute identifies the nature of an item. For example, what designates an item as an “engineering item” is the attribute Engineering Item. If a functional area’s item defining attribute is controlled at the Organization level, then that functional area may only have an Organization level default category set.
When you enable an item for a certain functional area, Oracle Inventory automatically assigns the item to the default category set of that functional area and the default category of that set. For example, if you set Inventory Item to Yes, then Inventory automatically assigns the item to the Inventory functional area’s default category set and default category.
You may change a functional area’s default category set under certain conditions. You should ensure that every item within the functional area belongs to the new default category set (which replaces the existing default category set). If the item defining attribute of the functional area is controlled at the Organization level then the new default category set should also be controlled at the Organization level.

 
/by
, , , , , ,

Assigning Items to Categories

When you enable an item in a functional area, the item is assigned to the default (mandatory) category set and default category of the functional area. You can override the category set’s default category. In addition, you can manually assign your item to an unlimited number of category sets. You may optionally assign an item to more than one category within a category set based on the category set definition.

When you assign your item to another organization Oracle Inventory copies Master level category sets, Organization level default category sets, and the associated categories assigned in the Item Master organization. This means that if you manually assign an Organization level category set to the item in the Master organization, Inventory does not copy over that Organization level category set when you assign that item to another organization.
After assigning an item to another organization you can disable the item for one or more functional areas in the new organization. However, Inventory does not remove the corresponding functional area’s default category set. For example, you may have set the value of the Purchased attribute to ”Yes” when you defined the item in the item master organization. When you assign this item to another organization Inventory copies over the ”Yes” value of the Purchased attribute and
therefore assigns the default category set of the purchasing functional area. In the new organization you may decide to set the value of the Purchased attribute to ”No.” After you disable the item for the purchasing functional area in the new organization, the item still retains the purchasing default category set. You may manually delete the purchasing category set in the new organization.
If you copy an item from another item with category sets defined at the Organization level, Inventory assigns the new item the default categories of the mandatory category sets, even if the original item did not have the default categories. This is because Inventory copies the values of the item defining attributes and not the category sets and categories themselves.

/by
, , , , , ,

Category Sets

Category sets may be used as a means to develop custom lists of items on which to report and sort. You can also create other category sets such as John’s Priority or Jane’s Priority, with categories like high, medium, and low.
The category set Inventory is seeded when you install Oracle Inventory.
The category set Purchasing is seeded when you install Oracle Purchasing.
If you plan to use Order Management’s group pricing functionality with item categories, you must add the categories to the Order Entry category set.
Attention:
1. You must use this window to define valid categories for each purchasing category set before you can use Oracle Purchasing.
2. For the Controlled At level, if the item defining attribute of the functional area (e.g. Inventory’s is Inventory Item) is controlled at the Organization level, then the new default Category Set should also be controlled at the Organization level.

Enter a unique category set Name and Description.  In the Flex Structure section, enter which flexfield structure is to be used.  The categories assigned to the category set must have the same flexfield structure as the set itself.  Select a control level and a default category.
You will then need to select Enforce List of Valid Categories if you want validation of the categories at the time of input.  You will then enter in or select the valid categories for the category set.

/by
, , , , , ,

Defining Item Categories

Enter a flexfield Structure Name, a unique Category (value) for each structure segment, and a unique description for the new category.  If you want to make a category inactive, enter a date you want the category to be inactive on.  Save your work.
If you choose a multi–segment flexfield structure you can assign a specific meaning to each segment. For example in our case the category “Electronics.Mobile.Samsung” means an item assinged to this category is a samusng brand mobile device of elcetroincs product group.

/by