Results for “packlist_number”

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

Overview

CSP_PACKLIST_HEADERS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSP – Spares Management module. Its documented purpose is to present packlist header information, that is, the top-level attributes of a packlist used to group and track spare parts shipments. A packlist is the logical container that records where and when goods were packed, dispatched, and received, along with carrier and waybill details. Because the view exposes the header record rather than line-level detail, it serves as the natural starting point for queries that need packlist identity, status, and the relevant business dates.

In both EBS 12.1.1 and 12.2.2 the object carries a VALID status and is documented as an APPS-owned view over the CSP_PACKLIST_HEADERS base object. The view is not a materialized structure; it is a straightforward projection whose role is to provide a stable, read-accessible interface for the underlying packlist header data. Reporting tools, concurrent programs, and integration interfaces can therefore query the view without depending on internal table access patterns.

Underlying Base Objects

According to the documented metadata (ETRM 12.2.2), the view references a single base object: CSP_PACKLIST_HEADERS, exposed through a synonym. This relationship is confirmed by the view text, which is a simple SELECT of the listed columns from CSP_PACKLIST_HEADERS, aliased as B, including B.ROWID in the projection. There are no joins, unions, or aggregations; the row count of the view is therefore identical to that of the base table. Because the view does not alter or restrict the data, all filtering, sorting, and security considerations that apply to the base table also apply here.

Key Columns

The view exposes several categories of columns. Identifying and key columns include PACKLIST_HEADER_ID, the surrogate primary key, and ROW_ID, the physical row identifier of the underlying table row. Standard EBS audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. Operational columns include ORGANIZATION_ID, PACKLIST_NUMBER, SUBINVENTORY_CODE, and PACKLIST_STATUS, which together describe the inventory organization, human-readable packlist identifier, originating subinventory, and lifecycle state.

The date columns are of particular interest given the user search term "date_shipped". DATE_CREATED, DATE_PACKED, DATE_SHIPPED, and DATE_RECEIVED represent the four principal milestones of a packlist. DATE_SHIPPED records the date the shipment left the shipping organization and is the column most commonly used for dispatch reporting, on-time shipment analysis, and carrier performance measurement. Distribution and logistics attributes include CARRIER, SHIPMENT_METHOD, and WAYBILL, which identify the transporting party, the mode of shipment, and the tracking number respectively. LOCATION_ID and PARTY_SITE_ID point to the ship-to location and the receiving party site. COMMENTS holds free-text notes, and the fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide the standard EBS descriptive flexfield storage, allowing implementations to add country-specific or business-specific fields without structural change.

Common Use Cases and Queries

The view is typically used to monitor shipment activity, reconcile packlists against receipts, and supply data to custom reports or downstream interfaces. A frequent requirement is to list packlists shipped within a date range, which directly addresses the "date_shipped" search:

• SELECT packlist_number, organization_id, packlist_status, date_shipped, carrier, waybill FROM csp_packlist_headers_v WHERE date_shipped BETWEEN :p_from_date AND :p_to_date ORDER BY date_shipped;
• Filtering by status to identify open or received packlists: SELECT packlist_number, date_packed, date_shipped, date_received FROM csp_packlist_headers_v WHERE packlist_status = :p_status;
• Joining to line-level and receipt tables on PACKLIST_HEADER_ID to perform shipment-to-receipt reconciliation, or to LOCATION_ID and PARTY_SITE_ID to resolve ship-to addresses.

Because the view is a direct projection, no special performance tuning beyond indexing on the base table columns (for example on DATE_SHIPPED, PACKLIST_NUMBER, or PACKLIST_STATUS) is required. All queries should use the APPS schema or a synonym, and access must respect the organization-level security that applies to the underlying CSP_PACKLIST_HEADERS data.