Search Results mtl_child_lot_numbers
Overview
MTL_CHILD_LOT_NUMBERS is an Oracle Inventory (INV) table that stores child lot number sequences. In Oracle EBS 12.1.1 and 12.2.2, child lot functionality allows a parent lot to be subdivided into one or more child lots, each tracking its own quantity and, in some cases, gradable attributes. This table records the sequence counters used to generate the next child lot number for a given parent lot. It is the bookkeeping anchor that ensures child lot numbers are issued sequentially and uniquely per parent lot per item per organization. The table resides in the INV schema and is registered with a status of VALID.
From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone, meaning the object does not participate as a hub, link, or satellite in the documented relationship graph. Its role is functional and operational rather than transactional; it maintains generation state rather than a history of lot movement.
Key Information Stored
The documented physical schema contains nine columns. The most significant are:
- ORGANIZATION_ID — identifies the inventory organization that owns the parent lot.
- INVENTORY_ITEM_ID — identifies the item associated with the parent lot.
- PARENT_LOT_NUMBER — the parent lot for which the child lot sequence is maintained; this is the column users reference when searching for "parent_lot_number".
- LAST_CHILD_LOT_NUMBER_SEQ — the last sequence value issued for child lots under this parent lot, used to derive the next child lot number.
- CREATION_DATE, CREATED_BY — audit columns capturing when and by whom the sequence row was created.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification.
The surrogate primary key is MTL_CHILD_LOT_NUMBERS_PK, composed of ORGANIZATION_ID, INVENTORY_ITEM_ID, and PARENT_LOT_NUMBER. Because the same three columns form the only documented unique index, they also serve as the business-key candidate; the parent lot number combined with item and organization uniquely defines a sequence counter.
Common Use Cases and Queries
Typical scenarios include diagnosing why child lot numbering appears to skip, duplicate, or restart, and reconciling the last issued child lot number against actual child lot entries. A common query retrieves the sequence state for a specific parent lot:
- SELECT organization_id, inventory_item_id, parent_lot_number, last_child_lot_number_seq FROM mtl_child_lot_numbers WHERE parent_lot_number = :parent_lot;
- SELECT parent_lot_number, last_child_lot_number_seq FROM mtl_child_lot_numbers WHERE organization_id = :org AND inventory_item_id = :item ORDER BY parent_lot_number;
- Reporting use case: joining this table to MTL_LOT_NUMBERS to compare the sequence counter with the count of child lots actually recorded.
These queries support inventory analysts and technical consultants investigating child lot generation issues and validating sequence integrity.
Related Objects
The most significant objects that reference or depend on this table through the shared columns include:
- MTL_LOT_NUMBERS — joins on ORGANIZATION_ID, INVENTORY_ITEM_ID, and LOT_NUMBER / PARENT_LOT_NUMBER to relate stored lots to the parent sequence.
- MTL_CHILD_LOT_NUMBERS_PK — the primary key index enforcing uniqueness.
- MTL_SYSTEM_ITEMS_B — supplies item context via INVENTORY_ITEM_ID.
- ORG_ORGANIZATION_DEFINITIONS — supplies organization context via ORGANIZATION_ID.
- MTL_MATERIAL_TRANSACTIONS — child lot transactions that consume the generated numbers.
- INV_LOT_API / INV_LOT_NUMBER_API — APIs used to generate and validate lot numbers that read this sequence.
-
Table: MTL_CHILD_LOT_NUMBERS
12.2.2
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_CHILD_LOT_NUMBERS, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID, product: INV - Inventory , description: Child Lot Number Sequences , implementation_dba_data: INV.MTL_CHILD_LOT_NUMBERS ,
-
Table: MTL_CHILD_LOT_NUMBERS
12.1.1
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_CHILD_LOT_NUMBERS, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID, product: INV - Inventory , description: Child Lot Number Sequences , implementation_dba_data: INV.MTL_CHILD_LOT_NUMBERS ,
-
SYNONYM: APPS.MTL_CHILD_LOT_NUMBERS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID,
-
VIEW: INV.MTL_CHILD_LOT_NUMBERS#
12.2.2
owner:INV, object_type:VIEW, object_name:MTL_CHILD_LOT_NUMBERS#, status:VALID,
-
SYNONYM: APPS.MTL_CHILD_LOT_NUMBERS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID,
-
TABLE: INV.MTL_CHILD_LOT_NUMBERS
12.1.1
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_CHILD_LOT_NUMBERS, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID,
-
VIEW: INV.MTL_CHILD_LOT_NUMBERS#
12.2.2
-
TABLE: INV.MTL_CHILD_LOT_NUMBERS
12.2.2
owner:INV, object_type:TABLE, fnd_design_data:INV.MTL_CHILD_LOT_NUMBERS, object_name:MTL_CHILD_LOT_NUMBERS, status:VALID,
-
PACKAGE BODY: APPS.INV_LOT_API_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:INV_LOT_API_PUB, status:VALID,
-
PACKAGE BODY: APPS.INV_LOT_API_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:INV_LOT_API_PUB, status:VALID,
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
APPS.INV_LOT_API_PUB SQL Statements
12.1.1
-
APPS.INV_LOT_API_PUB SQL Statements
12.2.2
-
APPS.INV_LOT_API_PUB dependencies on MTL_CHILD_LOT_NUMBERS
12.2.2
-
APPS.INV_LOT_API_PUB dependencies on MTL_CHILD_LOT_NUMBERS
12.1.1
-
PACKAGE: APPS.INV_LOT_API_PUB
12.1.1
-
PACKAGE: APPS.INV_LOT_API_PUB
12.2.2
-
APPS.INV_LOT_API_PUB dependencies on FND_GLOBAL
12.1.1
-
APPS.INV_LOT_API_PUB dependencies on FND_GLOBAL
12.2.2
-
PACKAGE BODY: APPS.INV_LOT_API_PUB
12.1.1
-
PACKAGE BODY: APPS.INV_LOT_API_PUB
12.2.2
-
eTRM - INV Tables and Views
12.2.2
-
eTRM - INV Tables and Views
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
eTRM - INV Tables and Views
12.1.1
-
eTRM - INV Tables and Views
12.2.2