Inventory Key Flexfields

Inventory Key Flexfields:

Oracle Inventory provides the following flexfields:

System Item:

You can use the System Items Flexfield (also called the Item Flexfield) for recording and reporting your item information. You must design and configure your Item Flexfield before you can start defining items. All Oracle Applications products that reference items share the Item Flexfield and support multiple-segment implementations. However, this flexfield supports only one structure. You must set up your OE: Item Flexfield profile option to specify the Item Flexfield structure that you will use for your Oracle applications. Users can also set up the OE: Item Flexfield Entry Method profile option to specify your preferred method of entry for this flexfield. You can optionally use the item flexfield to default item information for invoice, debit memo, and credit memo lines or you can enter your own line information.

Owner	Oracle Inventory
Flexfield Code	MSTK
Table Name	MTL_SYSTEM_ITEMS
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	No
Unique ID Column	INVENTORY_ITEM_ID
Structure Column	ORGANIZATION_ID

Item Catalog:

If you make entries for your items in a standard industry catalog or want to group your items according to certain descriptive elements, you need to configure your Item Catalog Group Flexfield. You must indicate how many separate segments your flexfield has, how many characters each segment has, and whether you want to validate the values that you assign to the segments. Once you define the structure of your flexfield and any applicable value sets, you must freeze and compile your flexfield definition. Compiling the flexfield definition enables the Item Catalog Group Flexfield pop-up window. Even if you do not use item cataloging, you must enable at least one segment and compile this flexfield before you can define items.

Owner	Oracle Inventory
Flexfield Code	MICG
Table Name	MTL_ITEM_CATALOG_GROUPS
Number of Columns	15
Width of Columns	40
Dynamic Inserts Possible	No
Unique ID Column	ITEM_CATALOG_GROUP_ID
Structure Column	None

Item Category:

You must design and configure your Item Categories Flexfield before you can start defining items since all items must be assigned to categories. You can define multiple structures for your Item Categories Flexfield, each structure corresponding to a different category grouping scheme. You can then associate these structures with the categories and category sets you define.

Owner	Oracle Inventory
Flexfield Code	MCAT
Table Name	MTL_CATEGORIES
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	No
Unique ID Column	CATEGORY_ID
Structure Column	STRUCTURE_ID

Stock Locator: 

You can use the Stock Locators Flexfield to capture more information about stock locators in inventory. If you do not have Oracle Inventory installed, or none of your items have locator control, it is not necessary to set up this flexfield. If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your Stock Locators Flexfield and implement locator control in your organization. This key flexfield supports only one structure.

Owner	Oracle Inventory
Flexfield Code	MTLL
Table Name	MTL_ITEM_LOCATIONS
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	Yes
Unique ID Column	INVENTORY_LOCATION_ID
Structure Column	ORGANIZATION_ID

Account Alias:

If you want to define logical references to frequently used account number combinations and use them as transaction source types, you need to configure your Account Aliases Flexfield and define account aliases. You must indicate how many separate segments your flexfield has, how many characters each segment has, and whether you want to validate the values that you assign to the segments. Once you define the structure of your flexfield and any applicable value sets, you must freeze and compile your flexfield definition. Compiling the flexfield definition enables the Account Aliases Flexfield pop-up window. Even if you do not use account aliases, you must still compile the Account Aliases Flexfield because all Oracle Inventory transaction inquiries and reports require a frozen flexfield definition. However, you do not need to configure the flexfield in a specific way.

Owner	Oracle Inventory
Flexfield Code	MDSP
Table Name	MTL_GENERIC_DISPOSITIONS
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	No
Unique ID Column	DISPOSITION_ID
Structure Column	ORGANIZATION_ID

Sales Order:

If you want to ship items from inventory to meet customer demand as specified in a sales order, regardless of whether you are using Oracle Order Entry, you must configure your Sales Orders Flexfield. You must indicate how many separate segments your flexfield has, how many characters each segment has, and whether you want to validate the values that you assign to the segments. Once you define the structure of your flexfield and any applicable value sets, you must freeze and compile your flexfield definition. Compiling the flexfield definition enables the Sales Orders Flexfield pop-up window. Even if you do not ship items against sales orders, you must still compile the Sales Orders Flexfield because all Oracle Inventory transaction inquiries and reports require a frozen flexfield definition. However, you do not need to configure the flexfield in a specific way.

Owner	Oracle Inventory
Flexfield Code	MKTS
Table Name	MTL_SALES_ORDERS
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	Yes
Unique ID Column	SALES_ORDER_ID
Structure Column	None

Service Item:

The Service Item flexfield uses the same table as the System Item Flexfield. However, you can set up your segments differently with the Service Item Flexfield.

Owner	Oracle Service
Flexfield Code	SERV
Table Name	MTL_SYSTEM_ITEMS
Number of Columns	20
Width of Columns	40
Dynamic Inserts Possible	No
Unique ID Column	INVENTORY_ITEM_ID
Structure Column	ORGANIZATION_ID