Results for “invbv_move_orders_lines”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.INVBV_MOVE_ORDERS_LINES view is an Inventory (INV) module reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the line-level detail of move orders — the internal replenishment and subinventory transfer documents managed by Oracle Inventory — in a flattened, security-filtered, read-only form. The view is defined with the WITH READ ONLY clause, meaning it cannot be used for DML operations and is intended purely for querying. It also carries an organization-level security predicate ('_SEC:TRL.ORGANIZATION_ID' IS NOT NULL), which restricts results to the organizations the querying user is authorized to access. In practice, INVBV_MOVE_ORDERS_LINES serves as the line-grain companion to the move order header view, giving developers, report authors, and integration builders a stable, denormalized surface over the underlying transaction request tables.
Underlying Base Objects
The view is defined over a single documented base object: MTL_TXN_REQUEST_LINES, accessed via its APPS synonym (aliased TRL in the view text). MTL_TXN_REQUEST_LINES is the Inventory table that stores individual move order lines, including the source and destination subinventory, locator, item, quantity, and status information. Because the view is a direct projection with no joins, essentially all of its columns map one-to-one to columns of MTL_TXN_REQUEST_LINES. The view adds value not by joining additional tables but by applying the organization security filter and by converting certain coded columns into user-readable values through Oracle's descriptive flexfield/attribute translation constructs.
Key Columns
The view exposes the source and destination details of each move order line, which is central to the user's search term from_subinventory_id:
FROM_SUBINVENTORY_ID— the internal identifier of the subinventory from which material is drawn. Note that this is an ID, not the display name.FROM_SUBINVENTORY_CODE— the human-readable subinventory code corresponding to the source subinventory, suitable for reporting without a lookup join.TO_SUBINVENTORY_ID/TO_SUBINVENTORY_CODE— the destination subinventory identifier and code.FROM_LOCATOR_ID/TO_LOCATOR_ID— the source and destination locators within those subinventories.LINE_ID,HEADER_ID,LINE_NUMBER— the line's primary key and its parent move order header reference.ORGANIZATION_ID— the inventory organization, and the column governed by the view's security predicate.INVENTORY_ITEM_ID,REVISION,LOT_NUMBER,SERIAL_NUMBER_START,SERIAL_NUMBER_END— item and lot/serial identification.QUANTITY,QUANTITY_DELIVERED,QUANTITY_DETAILED,UOM_CODE— quantities requested, delivered, and detailed, with the unit of measure.LINE_STATUS— the coded status; the accompanying_LA:LINE_STATUS_NAMEcolumn resolves it to a meaning via theMTL_TXN_REQUEST_STATUSlookup.REFERENCE_TYPE_CODEand its resolved_LA:REFERENCE_TYPEcolumn,REFERENCE_ID,PROJECT_ID,TASK_ID, andTRANSACTION_HEADER_ID— sourcing, project, and transaction linkage.
Common Use Cases and Queries
Typical uses include move order open-line reporting, replenishment analysis, subinventory transfer auditing, and integration extracts feeding warehouse or planning systems. Because the view already resolves lookup meanings, reports can display status and reference type directly. A representative query filtering on the searched column is:
SELECT line_id, header_id, organization_id, inventory_item_id, from_subinventory_code, to_subinventory_code, quantity, quantity_delivered, line_status, "_LA:LINE_STATUS_NAME" FROM invbv_move_orders_lines WHERE from_subinventory_id = :p_from_subinventory_id AND organization_id = :p_org_id;- Joining to
MTL_TXN_REQUEST_HEADERSonheader_idretrieves header-level attributes such as request type and requesting user. - Filtering on
line_statusisolates open versus closed movement lines for reconciliation.
All queries return only rows for organizations the user is permitted to see, so results are implicitly organization-security compliant.
-
APPS.INVBV_MOVE_ORDERS_LINES·↳ MTL_TXN_REQUEST_LINES·Explore INV module →
-
APPS.INVBV_MOVE_ORDERS_LINES·↳ MTL_TXN_REQUEST_LINES·Explore INV module →
-
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.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2