Oracle Applications : Inventory Technical Table Relations
MTL_Parameters:
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.
HR_ALL_organization_UNITS:
This table store organization information.
Navigation:
Inventory --> Setup --> Organizations --> Organizations
MTL_SYSTEM_ITEMS_B:
MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. You can specify item-related information in fields such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.
You can set up the item with multiple segments, since it is implemented as a flex-field. Use the standard 'System Items' flex-field that is shipped with the product to configure your item flex-field.
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.
MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. You can specify item-related information in fields such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.
You can set up the item with multiple segments, since it is implemented as a flexfield. Use the standard 'System Items' flexfield that is shipped with the product to configure your item flexfield.
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.
mtl_material_transactions:
Records are inserted into this table either through the transaction
processor or by the standard cost update program.
The columns TRANSACTION_TYPE_ID, TRANSACTION_ACTION_ID,
TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_ID and
TRANSACTION_SOURCE_NAME describe what the transaction is and against
what entity it was performed
processor or by the standard cost update program.
The columns TRANSACTION_TYPE_ID, TRANSACTION_ACTION_ID,
TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_ID and
TRANSACTION_SOURCE_NAME describe what the transaction is and against
what entity it was performed
mtl_transaction_accounts:
Thats the write table to look its gets the records from this table for
the transactions and then kick another Concurrent program to post into Gl at the
month end closing time,any bad transactions will result in X number of
un transferred Distribution accounts in this table and the period will close
with errors.
the transactions and then kick another Concurrent program to post into Gl at the
month end closing time,any bad transactions will result in X number of
un transferred Distribution accounts in this table and the period will close
with errors.
MTL_onhand_quantities:
MTL_ONHAND_QUANTITIES is maintained as a stack of receipt
records, which are consumed by issue transactions in FIFO order. 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
if you are using lots numbers,use mtl_transaction_lot_numbers
select *
For more inventory related topics click here
if you are using lots numbers,use mtl_transaction_lot_numbers
select *
FROM APPS.mtl_onhand_quantities moq,
INV.mtl_material_transactions MMT,
MTL_TRANSACTION_LOT_NUMBERS lots
where moq.lot_number = lots.lot_number
and lots.transaction_id - mmt.transaction_id
and moq.organization_id = mmt.organization_id
and moq.inventory_item_id = mmt.inventory_item_idFor more inventory related topics click here
