Search Results shipment_priority




Overview
Explore in AI Chat

Overview

The view APPS.SO_SHIP_PRIORITIES_ACTIVE_V exposes the set of currently active shipment priority values defined within Oracle Order Management. It is a simple lookup-based view that isolates the enabled, date-effective values for the SHIPMENT_PRIORITY lookup type, presenting them in a denormalized form suitable for reporting, validation, and integration consumption. In Oracle EBS 12.1.1 and 12.2.2, shipment priority drives sequencing behavior during pick release and shipping, influencing the order in which delivery lines are allocated, picked, and shipped. Rather than querying the underlying lookup table directly — which contains historical, disabled, and future-dated rows — consumers use this view to obtain only the values that are valid as of the current system date.

The view returns exactly two columns, one carrying the user-facing meaning and the other the code value. This two-column projection makes the view convenient for List of Values (LOV) population, concurrent program parameters, and analytical extracts where the lookup code must be paired with its descriptive meaning.

Underlying Base Objects

The documented metadata identifies two referenced objects: the SO_LOOKUPS synonym and the FND_GLOBAL package.

  • SO_LOOKUPS — The synonym resolves to the Order Management lookup table, which stores all lookup types used by the shipping and order fulfillment modules. The view filters this table on LOOKUP_TYPE = 'SHIPMENT_PRIORITY'.
  • FND_GLOBAL — Referenced as a package in the metadata. Although the view text provided does not invoke FND_GLOBAL explicitly, the ETRM metadata lists it as a referenced base object, typically due to multi-org or session-context resolution used in the underlying synonym definition or in dependent security constructs.

The view text is a single SELECT statement joining no additional tables, applying three filters: ENABLED_FLAG = 'Y', and a date-range predicate that requires the current truncated system date to fall between the lookup's active start and end dates (with NVL defaults substituting SYSDATE when either bound is null). The result is a self-maintaining list of active priorities.

Key Columns

  • SHIPMENT_PRIORITY — Maps to SO_LOOKUPS.MEANING. This is the descriptive, translated value of the priority (for example, the display label shown to users).
  • SHIPMENT_PRIORITY_CODE — Maps to SO_LOOKUPS.LOOKUP_CODE. This is the stored code used by order and delivery line records to reference the priority.

Implicitly, the underlying filters rely on ENABLED_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE, though these are not projected. Consuming code should treat the pair (code, meaning) as the complete contract.

Common Use Cases and Queries

Typical uses include populating shipment priority LOVs, validating user-supplied priority codes during interface imports, and reporting on active priorities for operational configuration reviews. A representative query listing all active priorities follows:

SELECT shipment_priority_code,
       shipment_priority
FROM   apps.so_ship_priorities_active_v
ORDER  BY shipment_priority_code;

To display the priority assigned to open delivery lines, the view is commonly joined to shipping tables on the code column:

SELECT d.delivery_id,
       d.shipment_priority_code,
       v.shipment_priority
FROM   apps.wsh_delivery_assignments d,
       apps.so_ship_priorities_active_v v
WHERE  d.shipment_priority_code = v.shipment_priority_code;

Because the view filters by SYSDATE, results change automatically when a priority is disabled or its effective dates expire, ensuring downstream reports always reflect current configuration without additional maintenance.