Results for “lot_indivisible”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.IC_MOVE_ORDER_LINES_V is a Process Manufacturing Inventory (GMI) view that exposes move order line information in a form suitable for the OPM Pick Lots form (ICPCKLOT.fmb). The view consolidates transaction request line data from IC_TXN_REQUEST_LINES with warehouse details and item master attributes, providing a denormalized, form-friendly result set without requiring the form to join the underlying base tables directly.

Its role in Oracle EBS reporting and integration is that of a read-only presentation layer over move order lines. Rather than querying IC_TXN_REQUEST_LINES and manually resolving warehouse codes, item numbers, and unit-of-measure information, consumers select from this view to obtain move order lines already joined to warehouse and item context. The view is registered as VALID in the APPS schema and is documented under the GMI - Process Manufacturing Inventory product family, which places it squarely within the OPM inventory flow rather than the discrete MTL move order path.

A notable filter is embedded directly in the view definition: MOL.LINE_STATUS IN (3, 7). This restricts the rows returned to the qualifying line statuses recognized by the Pick Lots form, so any query against the view automatically inherits that constraint. This is an important behavioral characteristic, since callers cannot retrieve all move order lines regardless of status through this view.

Underlying Base Objects

The view is defined over four base objects, three of which are OPM tables accessed through APPS synonyms and one of which is the discrete inventory item master. The documented referenced base objects are:

• IC_TXN_REQUEST_LINES (SYNONYM) — aliased MOL; supplies the move order line itself, including organization, item, quantity, UOM, delivered quantities, and line status.
• IC_WHSE_MST (SYNONYM) — aliased WHS; supplies warehouse code and warehouse name.
• IC_ITEM_MST (SYNONYM) — aliased ITM; supplies OPM item attributes such as ITEM_NO, ITEM_DESC1, and the item flags.
• MTL_SYSTEM_ITEMS (SYNONYM) — aliased MTL; provides the discrete-side item identifier and the join bridge to the OPM item master via SEGMENT1.

The join structure is a chain of equality conditions: MOL.ORGANIZATION_ID = WHS.MTL_ORGANIZATION_ID ties the line to its warehouse; MOL.INVENTORY_ITEM_ID = MTL.INVENTORY_ITEM_ID combined with MOL.ORGANIZATION_ID = MTL.ORGANIZATION_ID ties the line to the organization-specific system item; and MTL.SEGMENT1 = ITM.ITEM_NO maps the discrete item concatenated segment to the OPM item number. This last link is the mechanism by which OPM item attributes are joined into a move order line context.

Key Columns

The view projects twenty-one columns. The most significant are summarized below.

• INVENTORY_ITEM_ID and ITEM_ID — the discrete inventory item identifier from the transaction line and the OPM item identifier from IC_ITEM_MST, respectively. These coexist because the view crosses the discrete and process item models.
• DUALUM_IND — the dual unit of measure indicator sourced from the OPM item master. This is the column most directly associated with the search term "dualum_ind". When set, it signals that the item is maintained in two units of measure, which is why the view exposes both primary and secondary quantity columns.
• NONINV_IND and LOT_INDIVISIBLE — OPM item flags indicating non-inventory status and lot indivisibility. These drive picking and lot selection behavior in the Pick Lots form.
• ITEM_NO and ITEM_DESC1 — the OPM item number and primary description, available directly without a further join to IC_ITEM_MST.
• ORGANIZATION_ID, WHSE_CODE, and WHSE_NAME — warehouse and organization context for the line.
• UOM_CODE and SECONDARY_UOM_CODE — the primary and secondary units of measure for the line.
• QUANTITY, QUANTITY_DETAILED, and QUANTITY_DELIVERED — requested and delivered quantities in the primary UOM, with QUANTITY_DETAILED holding the higher-precision value. Each is wrapped in NVL(..., 0) so that null quantities are returned as zero.
• SECONDARY_QUANTITY, SECONDARY_QUANTITY_DETAILED, and SECONDARY_QUANTITY_DELIVERED — the corresponding secondary UOM quantities, meaningful when DUALUM_IND is set. These are also NVL-protected.
• TXN_SOURCE_LINE_ID, LINE_ID, and LINE_STATUS — the transaction source line reference, the move order line identifier, and the line status. As noted, only statuses 3 and 7 are returned by the view definition.

Common Use Cases and Queries

The primary use case is supporting the OPM Pick Lots form and equivalent custom pick/lot selection screens that must display move order lines alongside item attributes such as dual UOM and lot indivisibility. Reporting and integration scenarios include extraction of open move order lines for warehouse operations dashboards, reconciliation of requested versus delivered quantities, and interface programs that need a flattened move order line feed.

A basic query listing open move order lines with their item and warehouse context:

• SELECT line_id, organization_id, whse_code, item_no, item_desc1, uom_code, quantity, quantity_delivered, line_status FROM apps.ic_move_order_lines_v ORDER BY organization_id, whse_code, item_no;

To isolate items maintained under a dual unit of measure, the search term of interest maps directly to a predicate on the OPM item flag:

• SELECT line_id, item_no, item_desc1, uom_code, secondary_uom_code, quantity, secondary_quantity, quantity_delivered, secondary_quantity_delivered FROM apps.ic_move_order_lines_v WHERE dualum_ind = 'Y' ORDER BY item_no;

To measure pick completeness by comparing requested and delivered quantities in the primary UOM:

• SELECT whse_code, item_no, quantity, quantity_delivered, (quantity - quantity_delivered) quantity_open FROM apps.ic_move_order_lines_v WHERE quantity_delivered < quantity ORDER BY whse_code, item_no;

Because LINE_STATUS IN (3, 7) is embedded in the view text, callers should not expect to filter by arbitrary status values. Any requirement to report on lines outside those statuses must be met by querying IC_TXN_REQUEST_LINES directly rather than through this view. Similarly, the view returns one row per qualifying move order line, so aggregation by item or warehouse should be applied explicitly by the consumer.