Appendix-INVTRAN

MTL_MATERIAL_TRANSACTIONS
This table stores a record of every material transaction or cost update performed in
Inventory. TRANSACTION_QUANTITY describes the Quantity of Transaction,
TRANSACTION_UOM describes the Transaction unit of measure,
PRIMARY_QUANTITY describes the Transaction quantity in terms of primary uom of
the item, TRANSACTION_DATE describes the Date of the Transaction,
TRANSACTION_ACTION_ID describes the Transaction action,
TRANSACTION_TYPE_ID describes a type of the Transaction,
TRANSACTION_SOURCE_TYPE_ID describes the Transaction source type,
TRANSACTION_SOURCE_ID and TRANSACTION_SOURCE_NAME describes the
Source of the Transaction. Item revision stored in REVISION and locator control stored
in LOCATOR_ID.
If the item is under lot control then the lot records are stored in
MTL_TRANSACTION_LOT_NUMBERS, If the item is under
Serial controls then the serial records are stored in MTL_UNIT_TRANSACTIONS.
TRANSACTION_ID, INVENTORY_ITEM_ID, LOCATOR_ID, and
SUBINVENTORY_CODE are the key join columns.

New Columns in MTL_MATERIAL_TRANSACTIONS (RELEASE 12)

1.

TRANSFER_PRICE (Transfer Price)

2.

EXPENSE_ACCOUNT_ID (Expense Account Identifier)

3.

COGS_RECOGNITION_PERCENT

4.

SO_ISSUE_ACCOUNT_TYPE

5.

OPM_COSTED_FLAG (Flag to mark if the transaction is costed or not (for

Process Organizations))

Related Key tables to MTL_MATERIAL_TRANSACTIONS are

MTL_TXN_SOURCE_TYPES
This table contains information about valid transaction source type in the system. There
are two kinds of transaction source types, System transaction source types and User

defined transaction source types. System transaction source types are those seeded
when the system is installed, bear source type identifiers of 1 through 13 and use
system validation. User defined transaction source types have identifiers higher than
100, and may have validation set up through the use of the descriptive flex context in
the 'Transaction Source' descriptive flex field. TRANSACTION_SOURCE_TYPE_NAME
describes Name of the Transaction source type.
DESCRIPTIVE_FLEX_CONTEXT_CODE defined for the 'Transaction Source'
descriptive flex for linkage to a value set. TRANSACTION_SOURCE_TYPE_ID
describes Transaction source type. Transaction source types are used in defining user
transaction types, which would in turn be used in different inventory transactions. The
following Join is used for this table.
MTL_TXN_SOURCE_TYPES.TRANSACTION_SOURCE_TYPE_ID=
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_SOURCE_TYPE_ID
MTL_TRANSACTION_TYPES
This table contains seeded transaction types and the user defined ones. The table also
stores the TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID that
is associated with each transaction type. LOCATION_REQUIRED_FLAG is an
additional column, indicates whether the Location is mandatory for the given
Transaction.
TRANSACTION_TYPE_ID describes Transaction type, TRANSACTION_TYPE_NAME
describes Name of the transaction type, and USER_DEFINED_FLAG is set to 'Y' if this
type is user-defined. The following Join is used for this table
MTL_TRANSACTION_TYPES.TRANSACTION_TYPE_ID =
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_TYPE_ID
MTL_TRANSACTION_LOT_NUMBERS
This table stores lot number information for transactions in the
MTL_MATERIAL_TRANSACTIONS table.
TRANSACTION_QUANTITY describes the Transaction quantity, TRANSACTION_DATE
describes the date of Transaction, and LOT_NUMBER describes the Lot number. The
following Join is used for this table
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID =
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID

MTL_PHYSICAL_INVENTORIES
This table contains certain user-defined options for a physical inventory; including the
approvals required, sub inventory scope, tolerances, and whether tags may be created
in the Physical Inventory Counts window or whether they must be pre-generated.
PHYSICAL_INVENTORY_ID identifies Physical inventory,
PHYSICAL_INVENTORY_DATE stores date of taking physical inventory,
PHYSICAL_INVENTORY_NAME describes Name of physical inventory,
APPROVAL_REQUIRED describes Type of approval required on adjustment
transactions, ALL_SUBINVENTORIES_FLAG indicates whether or not this physical
inventory covers all sub inventories with the organization,
DYNAMIC_TAG_ENTRY_FLAG indicates whether or not dynamic tag creation is
permitted in the Physical Inventory Counts window.
MTL_CYCLE_COUNT_HEADERS
This table stores information about cycle count names. Oracle Inventory uses this
information to keep track of all cycle count names defined, to indicate
tolerance/approval limits, cycle count calendar and exception set, ABC initialization
information, scheduling options, and recount options. A cycle count name is also a
management entity, whose purpose is to be the repository of cycle count requirements
for a specific application.
A cycle count name is used in performance reports, accuracy reports, and in grouping
scheduling requests, count requests, count entries and
approvals.CYCLE_COUNT_HEADER_ID identifies Cycle count,
CYCLE_COUNT_HEADER_NAME describes User-visible name of this cycle count,
and ORIENTATION_CODE describes Scope of cycle count: organization-wide, or
subset of sub inventories.
MTL_MATERIAL_TRANSACTIONS_TEMP
This table is the gateway for all material transactions. Records are processed from this
table into Inventory through the transaction processor. Outside applications must write
transaction records to MTL_TRANSACTIONS_INTERFACE to be processed through
MTL_MATERIAL_TRANSACTIONS_TEMP and the Transaction processor by the
Transaction Worker concurrent program. Lots and serial numbers for a
MTL_MATERIAL_TRANSACTIONS_TEMP record are stored in the tables
MTL_TRANSACTION_LOTS_TEMP and MTL_SERIAL_NUMBERS_TEMP. If the item
is under lot control, then

MTL_MATERIAL_TRANSACTIONS_TEMP .TRANSACTION_TEMP_ID joins to

MTL_TRANSACTION_LOTS_TEMP .TRANSACTION_TEMP_ID. If the item is also
under serial number control,
Then MTL_TRANSACTION_LOTS_TEMP.SERIAL_TRANSACTION_TEMP_ID joins to
MTL_SERIAL_NUMBERS_TEMP.TRANSACTION_TEMP_ID. If the item is only under
serial number control,
Then MTL_MATERIAL_TRANSACTIONS_TEMP .TRANSACTION_TEMP_ID joins to
MTL_SERIAL_NUMBERS_TEMP.TRANSACTION_TEMP_ID. Transfer transactions are
stored in this table as a single record.

MTL_TXN_REQUEST_HEADERS
This table stores all of the move order headers. The headers contain all information
which pertains to entire move orders, including the transaction type of the move order,
the move order type, the Move order status, and the request number of the move order.
HEADER_ID identifies the Header, REQUEST_NUMBER Describes the Request
number of the move order. The following Join is used for this table
MTL_TXN_REQUEST_HEADERS.TRANSACTION_TYPE_ID =
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_TYPE_ID
MTL_UNIT_TRANSACTIONS
This table stores a record of every material transaction of a serialized unit in Inventory.
Many serial numbers may be specified for a given transaction record.
MTL_UNIT_TRANSACTIONS.TRANSACTION_ID joins to
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID when only under serial control;
MTL_UNIT_TRANSACTIONS.TRANSACTION_ID joins to
MTL_TRANSACTION_LOT_NUMBERS.SERIAL_TRANSACTION_ID when also under
lot control. SERIAL_NUMBER describes Serial number, TRANSACTION_DATE
describes the Date of the Transaction, TRANSACTION_SOURCE_TYPE_ID describes
the Disposition type code, and RECEIPT_ISSUE_TYPE describes the previous receipt
or issue code. The following Join is used for this table.
MTL_UNIT_TRANSACTIONS.TRANSACTION_ID =
MTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID
New Columns in Related Tables (RELEASE 12)

MTL_TRANSACTION_TYPES
1.

LOCATION_REQUIRED_FLAG (Indicates whether the Location is mandatory for

the given Transaction)

MTL_TRANSACTION_LOT_NUMBERS are
1.

EXPIRATION_ACTION_CODE (Expiration Action Code)

2.

EXPIRATION_ACTION_DATE (Expiration Action Date)

3.

HOLD_DATE (Hold Date)

4.

ORIGINATION_TYPE (Type of Origination)

5.

PARENT_LOT_NUMBER (Parent Lot Number)

6.

REASON_ID (Reason identifier)

7.

SECONDARY_TRANSACTION_QUANTITY

8.

PARENT_OBJECT_TYPE (For Genealogy Relationship)

9.

PARENT_OBJECT_ID ( Genealogy Object Id of the Parent entity)

10. PARENT_OBJECT_NUMBER (Object Number of the Parent Entity)

11. PARENT_ITEM_ID (Inventory Item Id of the parent Object (lot or serial))
12. PARENT_OBJECT_TYPE2 (used for lot+serial controlled items and will have
value 1=lot)
13. PARENT_OBJECT_ID2 (used for lot+serial controlled items and will have
Genealogy object id of lot number corresponding to serial number in parent
object number)
14. PARENT_OBJECT_NUMBER2 (used for lot+serial controlled items and will have
lot number corresponding to serial number in parent object number)
MTL_PHYSICAL_INVENTORIES
1.

EXCLUDE_ZERO_BALANCE (Exclude zero balance)

2.

EXCLUDE_NEGATIVE_BALANCE (Exclude negative balance)

MTL_MATERIAL_TRANSACTIONS_TEMP
1.

TRANSFER_SECONDARY_QUANTITY (Transfer Secondary Quantity)

2.

TRANSFER_SECONDARY_UOM (Transfer Secondary UOM)

3.

RELIEVE_RESERVATIONS_FLAG (Indicates whether to relieve the reservations

during transaction processing)

4.

RELIEVE_HIGH_LEVEL_RSV_FLAG (Indicates whether to check for high level

reservations that needs to be relieved during transaction processing)

5.

TRANSFER_PRICE 1(Transfer Price)

MTL_UNIT_TRANSACTIONS
1.

PARENT_OBJECT_TYPE (Parent Object Type)

2.

PARENT_OBJECT_ID (Genealogy Object Id of the Parent entity)

3.

PARENT_OBJECT_NUMBER (Object Number of the Parent Entity)

4.

PARENT_ITEM_ID(Inventory Item Id of the parent Object (lot or serial))

5.

PARENT_OBJECT_TYPE2 (used for lot+serial controlled items and will have

value 1=lot)

6.

PARENT_OBJECT_ID2 (used for lot+serial controlled items and will have

Genealogy object id of lot number Corresponding to serial number in parent
object number)
7. PARENT_OBJECT_NUMBER2 (used for lot+serial controlled items and will have
lot number corresponding to serial number in parent object number)