Results for “csp_packlist”

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

Overview

APPS.CSP_PACK_LIST_NAV is a reporting and navigation view in the Oracle E-Business Suite Supply Chain / Order Fulfillment module, belonging to the CSP (pick, pack, and ship) schema family. It presents pack list header records in a form suitable for consumption by navigational frameworks and reporting tools, rather than as a pure transactional data source. The view combines pack list header information with node-type metadata drawn from the navigation configuration, producing a result set that describes the pack list node as it should appear within a navigation UI or dashboard.

Because the view selects pack list headers filtered by the currently logged-in operating unit through csp_pick_utils.csp_global_org_id, it is inherently organization-aware. Each row represents a single pack list header visible within the active inventory organization context, ranked by pack list number in descending order. The view exposes identifiers, display icons, status codes, and literal flags ('N', 'PLIST_STATUS') that client-side navigation logic consumes to render and label the pack list node.

Underlying Base Objects

The view is defined over three documented base objects, all referenced in the ETRM metadata:

• CSP_NAV_NODE_TYPES (VIEW) — Supplies navigation node-type attributes. The join is restricted to rows where root_key = 'CSP_PACKLIST' and node_type = 'PACK_LIST', ensuring only the pack list navigation node is returned.
• CSP_PACKLIST_HEADERS (SYNONYM) — The principal data source, providing pack list header identifiers, pack list numbers, statuses, and organization identifiers.
• CSP_PICK_UTILS (PACKAGE) — Referenced through the function csp_pick_utils.csp_global_org_id, which supplies the session's global organization ID used to filter headers to the correct operating unit.

The relationship is an equi-join between the two data-bearing objects on the node-type definition, with the organization filter applied as a predicate against the headers table. The resulting join is essentially a cross-product of one pack list node type with each qualifying pack list header, which is appropriate because the node type is a constant in this context.

Key Columns

• packlist_number — The human-readable identifier of the pack list header; also the ORDER BY 1 DESC sort key, so the most recent pack list numbers appear first.
• node_type — The navigation node type, always 'PACK_LIST' given the filter predicate.
• packlist_header_id — The primary key of the underlying pack list header; used by downstream navigation logic as the link target or key reference.
• icon_name — The icon associated with the node type, used by the UI to render the pack list node.
• 'N' — A literal constant generally used to indicate a boolean-like flag (for example, non-expandable or non-detailed node behavior) in the navigation model.
• 'PLIST_STATUS' — A literal node label or status key used by the navigation framework to associate the row with a status field.
• packlist_status — The current status of the pack list header (for example, open, closed, or cancelled), surfaced for display alongside the node.

Common Use Cases and Queries

The view is typically used to drive navigation trees, dashboards, or LOV-style pickers that allow users to select or browse pack lists within the current organization. A representative query is:

• SELECT packlist_number, packlist_header_id, packlist_status FROM apps.csp_pack_list_nav;

Because the organization filter is embedded via csp_pick_utils.csp_global_org_id, callers should set the global organization context (for example, through the standard FND global org mechanism or the CSP initialization routines) before querying, otherwise results may be empty or reflect an unintended organization. Common downstream uses include retrieving header IDs for a selected pack list node, displaying current status in a navigation panel, and joining back to CSP_PACKLIST_HEADERS or dependent tables for detailed pack list reporting. It is not intended as a high-volume extraction source; for bulk data movement, querying CSP_PACKLIST_HEADERS directly with an explicit organization predicate is preferable.