Search Results configuration_item_flag

Overview

BOM_PICKING_LINES_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite (documented for 12.1.1 and ETRM 12.2.2). Its row set represents order picking lines, the individual component-level records that make up a picking header within shipping execution. Business documentation describes the object as "Order picking lines - used by delete constraints," indicating that its primary functional purpose in the BOM product is to expose the picking line rows in support of referential integrity and deletion logic, rather than to serve as a standalone reporting entity. Because it is a view rather than a table, it stores no data of its own; all rows and columns are projected from the synonym that masks the underlying picking lines table.

For reporting and integration purposes, the view behaves as a thin passthrough. It presents the full column list of the base object without filtering, joins, or computed expressions, which means consumers can rely on column-level fidelity: every attribute returned corresponds directly to a column of the base table. This makes it useful when an integration or report requires a stable APPS-owned object name while the underlying storage is accessed through a synonym, and it explains the appearance of the searched term, invoiced_quantity, within this view.

Underlying Base Objects

The view is defined over a single referenced base object: SO_PICKING_LINES_ALL, accessed through a synonym. There are no joins, aggregations, DISTINCT clauses, or analytic functions in the view text. The definition is a straight SELECT of every column from the base object, in physical column order, with no WHERE predicate. Consequently, the view inherits the row cardinality, indexing behavior, and security characteristics of the underlying table, and any row inserted, updated, or deleted in SO_PICKING_LINES_ALL is immediately visible through the view. Because the definition is unfiltered, no row-level security is applied by the view itself; any such restriction must come from the base table or from the application layer.

Key Columns

• PICKING_LINE_ID — Primary key of the picking line, unique per row.
• PICKING_HEADER_ID — Foreign key to the parent picking header; groups lines into a single pick.
• ORDER_LINE_ID — Order line fulfilled by the picking line.
• INVENTORY_ITEM_ID — Inventory item being picked; joined to item master for description and category.
• REQUESTED_QUANTITY, ORIGINAL_REQUESTED_QUANTITY — Quantity demanded and its original value prior to revision.
• SHIPPED_QUANTITY, CANCELLED_QUANTITY — Quantities shipped and cancelled against the line.
• INVOICED_QUANTITY — Quantity of the line that has been invoiced; the column of primary interest for the search term and a key measure for revenue and billing reconciliation.
• RA_INTERFACE_STATUS — Status of the row in the Receivables interface, indicating whether invoicing has been transmitted to AR.
• WAREHOUSE_ID, SHIP_TO_SITE_USE_ID, SHIP_METHOD_CODE — Fulfillment and destination attributes.
• DEMAND_CLASS_CODE, LATEST_ACCEPTABLE_DATE, SCHEDULE_DATE — Planning and scheduling attributes.
• COMPONENT_CODE, COMPONENT_RATIO, COMPONENT_SEQUENCE_ID, CONFIGURATION_ITEM_FLAG — Configured-item and component context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, etc.) plus ATTRIBUTE1–15 and CONTEXT descriptors.

Common Use Cases and Queries

A frequent requirement is reconciling invoiced quantities against shipped quantities by order line, or identifying lines that remain uninvoiced.

• Lines with an invoiced quantity recorded:

  SELECT picking_line_id, order_line_id, inventory_item_id,
         requested_quantity, shipped_quantity, invoiced_quantity
  FROM   apps.bom_picking_lines_view
  WHERE  invoiced_quantity IS NOT NULL
  AND    invoiced_quantity > 0;

• Variance between shipped and invoiced quantity:

  SELECT pl.picking_line_id, pl.order_line_id,
         pl.shipped_quantity, pl.invoiced_quantity,
         pl.shipped_quantity - pl.invoiced_quantity variance
  FROM   apps.bom_picking_lines_view pl
  WHERE  pl.shipped_quantity > NVL(pl.invoiced_quantity,0);

• Aggregate invoiced quantity per item for a period:

  SELECT inventory_item_id, SUM(invoiced_quantity) invoiced_qty
  FROM   apps.bom_picking_lines_view
  WHERE  creation_date >= :from_date
  GROUP  BY inventory_item_id;

Because the view is unfiltered, queries should always constrain on the driving columns such as ORDER_LINE_ID, PICKING_HEADER_ID, or date ranges to avoid full scans of the base table.