Key Tables in Oracle Inventory

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





Description 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 25character and the 3-character units of measure. The base_uom_flag indicates if the unit of measure is the primary unit of measure for the uom_class. Oracle Inventory uses this table to keep track of the units of measure used to transact an item.

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

which are consumed by issue transactions in FIFO order. This is the definition table for the subinventory. A subinventory is a section of inventory. finished goods. It is maintained as a stack of receipt records. It stores quantity on hand information by control level and location. and the kind of validation enforced on the attribute. 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. TRANSACTION_ACTION_ID. the corresponding user-friendly name seen by the users. The table stores the attribute name. This table stores a record of every material transaction or cost update performed in Inventory. This is the code combinations table for item catalog groups. TRANSACTION_SOURCE_ID and TRANSACTION_SOURCE_NAME describe what the transaction is and against what entity it was performed. An item catalog group . The table also stores the TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID that is associated with each transaction type.. i. Each row in the table corresponds to an attribute. Subinventories are assigned to items (in a many to one relationship). USER_DEFINED_FLAG will distinguish the two. TRANSACTION_SOURCE_TYPE_ID. raw material. It contains seeded transaction types and the user defined ones. indicating a list of valid places where this item will physically exist in inventory. and Reservation Rows.e. etc.MTL_SECONDARY_INVENTORIES MTL_ONHAND_QUANTITIES MTL_TRANSACTION_TYPES MTL_MATERIAL_TRANSACTIONS MTL_ITEM_ATTRIBUTES MTL_ITEM_CATALOG_GROUPS_B There are three major row types stored in the table: Summary Demand rows. The columns TRANSACTION_TYPE_ID. Records are inserted into this table either through the transaction processor or by the standard cost update program. Open Demand Rows. This table stores information on item attributes.

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


0 .:- 47. ..42.


.47.-08 .03947 3.0 .558 3. 0 9.