Search Results org_freight_vl

Overview

ASO_I_FREIGHT_CODES_V is a PL/SQL view owned by the APPS schema and shipped as part of the ASO (Order Capture) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose a validated list of freight carriers and shipment methods for use in a List of Values (LOV) within the Order Capture and order entry flows. Functionally, the view supplies the freight code values that an order entry clerk or an integration program selects when assigning a carrier and method to a sales order or order line. In the technical sense, it acts as a thin, filtered projection over a single underlying view, returning only those freight codes whose disable date has not yet passed as of the current system date. This design keeps historical freight codes available in the base data while preventing them from appearing in active selection lists.

Underlying Base Objects

The ETRM metadata records a single referenced base object for ASO_I_FREIGHT_CODES_V: the view ORG_FREIGHT_VL. The relationship is a direct projection. The view text is:

• SELECT ORGANIZATION_ID, FREIGHT_CODE, DESCRIPTION FROM ORG_FREIGHT_VL WHERE TRUNC(SYSDATE) < TRUNC(NVL(DISABLE_DATE, SYSDATE+1))

Several implications follow from this definition. First, ASO_I_FREIGHT_CODES_V inherits its column structure and multilingual (_VL) behavior from ORG_FREIGHT_VL; in Oracle EBS, the _VL suffix denotes a view that presents translated descriptive columns alongside the base key columns, resolving the appropriate language row for the current session. Second, the ORGANIZATION_ID column confirms that freight codes are defined at the inventory organization level, so the same freight code can exist under multiple organizations with distinct descriptions. Third, the WHERE clause introduces a soft-retirement filter: any row whose DISABLE_DATE is null is treated as permanently enabled (via the NVL substitution of SYSDATE+1), whereas a row with a DISABLE_DATE on or before the current date is suppressed. The DISABLE_DATE column is evaluated from the underlying ORG_FREIGHT_VL even though it is not projected into the outer view.

Key Columns

The view exposes three columns, as documented:

• ORGANIZATION_ID — The inventory organization identifier under which the freight code is defined. Callers must typically filter by this column to restrict the LOV to the operating unit's or order's warehouse context.
• FREIGHT_CODE — The carrier and method code value stored on the order. This is the value that is written back to the freight code attribute of the sales order when the LOV selection is made.
• DESCRIPTION — The translated, user-facing description of the freight code, presented in the session's current language through the underlying _VL view.

Common Use Cases and Queries

The principal use case is populating the freight carrier and method field in Order Capture. A form or OAF page issues a query against this view, constrained by organization and often by a partial code or description for type-ahead behavior. Typical query patterns include retrieving all active freight codes for a given warehouse:

• SELECT freight_code, description FROM aso_i_freight_codes_v WHERE organization_id = :org_id ORDER BY description;
• SELECT freight_code, description FROM aso_i_freight_codes_v WHERE organization_id = :org_id AND (UPPER(freight_code) LIKE UPPER(:partial) OR UPPER(description) LIKE UPPER(:partial));

Integration and reporting teams also use the view to validate an inbound freight code before writing an order interface record, or to build a reference extract of enabled carriers per organization. Because the view already excludes disabled codes, consumers need not replicate the disable-date logic. However, since DISABLE_DATE is not projected, callers that require visibility into retired codes must query ORG_FREIGHT_VL directly. Queries should always include ORGANIZATION_ID to avoid returning codes from unrelated inventory organizations.