, , , , , ,

Defining Account Aliases

An account alias is an easily recognized name or label representing a general ledger account number. You can view, report, and reserve against an account alias. During a transaction, you can use the account alias instead of an account number to refer to the account.

/by
, , , , , ,

Stock Locators

You use locators to identify physical areas where you store inventory items. Item quantities can be tracked by locator. Items can also be restricted to specific locators.

1. Add the segment values of the KFF stock locator.
Navigation : GL -> Financials -> Flexfields -> Key -> Values

2. Enter the new locator in locator form which can be accessed from below navigation or on subinventory form.

Navigation : Inventory -> Set up -> Stock Locator

 
1. Locator Type: Indicate the locator type available choices are as follows: Dock Door, Receiving, Inspection Station,  Storage Locator, Consolidation Locator, Staging Lane, Packing Station.  Dock doors are used in Oracle Warehouse Management environments only.
 

2. Indicate the material status of this locator, which controls the enabled transactions for all material in this locator. The status is not overridden by the status of any ubinventory, lot or serial, within this locator. The statuses of those objects will be considered when
determining transactions that are not enabled. This field is used if you have Oracle Warehouse Management installed.
3. Enter the subinventory where the locator resides.
4. Enter a picking order value indicating the priority for picking items from this locator relative to another locator. This value is used by Oracle Warehouse Managment to sequence picking tasks. A picking order of 1 means that order management functions pick items from this locator before other locators with a higher number (2, 3, and so on). If you have Oracle Warehouse Management installed, this field determines the picking path through the warehouse and not the order in which material is allocated for a sales order.
5. Enter a dropping order to indicate the priority for dropping items in this locator relative to another locator. Oracle warehouse management uses this value to sequence tasks.
6. Enter the inactive date for the locator. This is the date the locator becomes inactive.


/by
, , , , , ,

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