You are on page 1of 5

Key Tables in Oracle Inventory

Posted by Dibyajyoti Koch on July 16, 2011 in Apps Tables, Oracle Inventory

4 Votes

Here is a brief description of the key tables in Oracle Inventory.


It maintains a set of default options like general ledger accounts; locator, lot, and serial controls, inter-organization options, costing method, etc. for each organization defined in Oracle Inventory. Each organization’s item master organization (MASTER_ORGANIZATION_ID) and costing organization (COST_ORGANIZATION_ID) are maintained here.


This is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore, the same item can be defined in more than one organization. Items now support multilingual description. MLS is implemented with a pair of tables: MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL. Translations table (MTL_SYSTEM_ITEMS_TL) holds item Description and Long Description in multiple languages.


This is the definition table for material status codes. Status code is a required item attribute. It indicates the status of an item, i.e., Active, Pending, Obsolete.


This is the definition table for both the 25-character and the 3character units of measure. The base_uom_flag indicates if the

Items may be assigned to different categories in different category sets to represent the different groupings of items used for different purposes. MLS is implemented with a pair of tables: MTL_CATEGORY_SETS_B and MTL_CATEGORY_SETS_TL. STRUCTURE_ID identifies the flexfield structure associated with the category set. MTL_DEMAND This table stores demand and reservation information used in Available To Promise. what the locator physical capacity is. For each category assignment. this table stores the item. MTL_CATEGORIES_TL table holds translated Description for Categories. an item can be assigned to either many or only one category in that category set. MTL_CATEGORY_SETS_TL table holds translated Name and Description for Category Sets. etc. There are three major row types stored in the table: Summary . however. MTL_ITEM_CATEGORIES This table stores inventory item assignments to categories within a category set. MTL_CATEGORY_SETS_B It contains the entity definition for category sets. depending on the Multiple Assignments Allowed attribute value in a given category set definition. Item categories now support multilingual category description. A category set is a categorization scheme for a group of items. An item may be assigned to only one category within a category set. Items always may be assigned to multiple category sets. and the category. the category set. However. Planning and other Manufacturing functions. MTL_CATEGORIES_B This is the code combinations table for item categories. Category Sets now support multilingual category set name and description.unit of measure is the primary unit of measure for the uom_class. MLS is implemented with a pair of tables: MTL_CATEGORIES_B and MTL_CATEGORIES_TL. MTL_ITEM_LOCATIONS This is the definition table for stock locators. The associated attributes describe which subinventory this locator belongs to. Items are grouped into categories within the context of a category set to provide flexible grouping schemes. Oracle Inventory uses this table to keep track of the units of measure used to transact an item.

MTL_ONHAND_QUANTITIES It stores quantity on hand information by control level and location. i. etc. MTL_ITEM_ATTRIBUTES This table stores information on item attributes. the item inherits the descriptive elements for that group which then behave like . which are consumed by issue transactions in FIFO order. MTL_ITEM_CATALOG_GROUPS_B This is the code combinations table for item catalog groups. indicating a list of valid places where this item will physically exist in inventory. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. The columns TRANSACTION_TYPE_ID. The table stores the attribute name.e.Demand rows. finished goods. and the kind of validation enforced on the attribute. the corresponding user-friendly name seen by the users. MTL_SECONDARY_INVENTORIES This is the definition table for the subinventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. MTL_MATERIAL_TRANSACTIONS This table stores a record of every material transaction or cost update performed in Inventory. TRANSACTION_ACTION_ID. USER_DEFINED_FLAG will distinguish the two. A subinventory is a section of inventory. raw material. The quantity on hand of an item at any particular control level and location can be found by summing TRANSACTION_QUANTITY for all records that match the criteria. Open Demand Rows. Subinventories are assigned to items (in a many to one relationship). TRANSACTION_SOURCE_ID and TRANSACTION_SOURCE_NAME describe what the transaction is and against what entity it was performed. TRANSACTION_SOURCE_TYPE_ID.. The table also stores the TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID that is associated with each transaction type. MTL_TRANSACTION_TYPES It contains seeded transaction types and the user defined ones. Each row in the table corresponds to an attribute. and Reservation Rows. It is maintained as a stack of receipt records. When an item is associated with an item catalog group.

The customer item definition is organization independent. Descriptive elements are defining properties used to describe in the catalog group. MTL_SYSTEM_ITEMS_INTERFACE It temporarily stores the definitions for inventory items. When an item is associated with a particular item catalog group. MTL_ITEM_REVISIONS_B It stores revision levels for an inventory item. . It contains the user-defined name (TEMPLATE_NAME) and description (DESCRIPTION) ONLY for backward compatibility. and Address. MTL_DESCRIPTIVE_ELEMENTS It stores the descriptive element definitions for an item catalog group. engineering items and purchasing items before loading this information into Oracle Inventory. Each record can be defined at one of the following levels: Customer. It stores customer item information for a specific customer. ORG_ACCT_PERIODS MTL_CUSTOMER_ITEMS It holds the open and closed financial periods for organizations. MTL_ITEM_TEMPLATES_B This is the definition table for item templates. You can use a template to set certain item attributes. When an item is defined a starting revision record is written out to this table.additional item attributes. Address Category. MTL_DESC_ELEM_VAL_INTERFACE This table temporarily stores descriptive element values for an item that is associated with an item catalog group before loading this information into Oracle Inventory. receipts etc. so every item will at least have one starting revision. issues. one row per descriptive element (for that catalog group) is inserted into this table. to Oracle Inventory transaction module. MTL_ITEM_REVISIONS_INTERFACE It temporarily stores revision levels for an inventory item before loading this information into Oracle Inventory. MTL_ITEM_CATEGORIES_INTERFACE This table temporarily stores data about inventory item assignments to category sets and categories before loading this information into Oracle Inventory. MTL_DESCR_ELEMENT_VALUES It stores the descriptive element values for a specific item. MTL_TRANSACTIONS_INTERFACE It allows calling applications to post material transactions (movements.

Records inserted into this table are processed by the Demand Manager concurrent program. MTL_INTERFACE_ERRORS It stores errors that occur during the item interface process reporting where the errors occurred along with the error messages .MTL_DEMAND_INTERFACE It is the interface point between non-Inventory applications and the Inventory demand module.