Results for “packlist_line_number”

42 results




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

Overview

CSP_PACKLIST_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the CSP – Spares Management product family. It exposes packlist line information, presenting one row for each line on a spares management packlist. A packlist represents the physical packing of picked inventory items into boxes or containers prior to shipment, and each line identifies a specific item, its quantity packed, shipped, and received, and the unit of measure in which those quantities are expressed.

The view is a straightforward projection: it selects a fixed list of columns from the CSP_PACKLIST_LINES base table without joins, filters, or aggregation. This makes it a stable, read-only query surface for concurrent programs, Oracle Reports, Oracle Forms LOVs, business intelligence extracts, and custom integrations that need packlist line data without addressing the underlying table directly. Because the view is a simple pass-through, row counts and values are identical to the base table, and no additional query cost is incurred beyond the definition itself. The view is marked VALID in 12.1.1 and 12.2.2, and it also forms part of the documented ETRM 12.2.2 metadata set with APPS as owner and CSP_PACKLIST_LINES as the referenced base object.

Underlying Base Objects

The view is defined over a single object: the CSP_PACKLIST_LINES synonym, which resolves to the CSP_PACKLIST_LINES table in the APPS schema. There are no joins to inventory, order management, or shipping tables inside the view definition, so any enrichment with item descriptions, order numbers, or shipment information must be performed by the calling query. The view preserves all standard audit columns from the base table, including CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, and it also carries the full set of fifteen descriptive flexfield columns, ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15. The base table is the transactional store written by the spares management packing process; the view simply renames no columns and applies no transformation, which means the two are fully interchangeable in terms of data content. Because the object is a synonym-backed view rather than a table, no DML should be issued against it; inserts and updates must target CSP_PACKLIST_LINES through supported APIs.

Key Columns

  • PACKLIST_LINE_ID – Primary key of the packlist line; use it to join to related child or reference data.
  • PACKLIST_HEADER_ID – Foreign key to the packlist header, grouping lines belonging to the same packlist document.
  • PACKLIST_LINE_NUMBER – Sequence number of the line within its header.
  • BOX_ID – Identifier of the box or container into which the item was packed.
  • PICKLIST_LINE_ID – Links the packlist line back to the originating picklist line.
  • PACKLIST_LINE_STATUS – Current processing status of the packlist line.
  • INVENTORY_ITEM_ID – The packed inventory item; join to MTL_SYSTEM_ITEMS_B for descriptions.
  • QUANTITY_PACKED – Quantity placed into the box during packing.
  • QUANTITY_SHIPPED – Quantity actually shipped; the column most commonly queried for shipment reconciliation and reporting.
  • QUANTITY_RECEIVED – Quantity acknowledged as received at the destination.
  • UOM_CODE – Unit of measure for the three quantity columns.
  • ORGANIZATION_ID – Inventory organization owning the transaction.
  • LINE_ID – Secondary line identifier carried from the source document.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield context and segment values.

Common Use Cases and Queries

Typical uses include shipment confirmation reporting, packing discrepancy analysis (comparing packed against shipped and received quantities), and integration extracts feeding downstream warehouse or logistics systems. The following query returns shipped quantities by item and organization:

  • SELECT organization_id, inventory_item_id, uom_code, SUM(quantity_shipped) shipped_qty FROM apps.csp_packlist_lines_v WHERE packlist_line_status = 'SHIPPED' GROUP BY organization_id, inventory_item_id, uom_code;
  • SELECT l.packlist_line_id, l.packlist_line_number, l.inventory_item_id, l.quantity_packed, l.quantity_shipped, l.quantity_received FROM apps.csp_packlist_lines_v l WHERE l.quantity_packed <> l.quantity_shipped;
  • SELECT l.* FROM apps.csp_packlist_lines_v l WHERE l.packlist_header_id = :header_id AND l.organization_id = :org_id ORDER BY l.packlist_line_number;

Because the view performs no aggregation, always apply your own filters (organization, header, status, or date range) to avoid full-table scans on large packlist volumes. Join INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B for item numbers and descriptions, and use the audit columns for incremental extracts. Report against QUANTITY_SHIPPED only after the line has reached the appropriate status, since quantities may be populated progressively during packing and shipping.