Search Results so_freight_carriers_active_v

Overview

The SO_FREIGHT_CARRIERS_ACTIVE_V view is a reporting object owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) product family. Its purpose is to expose the set of currently active freight carriers (also referred to as freight codes) configured against an operating unit, so that order management, shipping, and integration processes can present or validate only those carriers that remain valid as of the current date. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

Functionally, the view applies a date-based filter so that carriers whose DISABLE_DATE has already passed are excluded from the result set. This makes it suitable for list-of-values (LOV) definitions, concurrent report sources, and external interfaces that must not allow selection of retired carriers. Because the object is a view rather than a base table, it carries no storage of its own and reflects the live contents of the underlying freight configuration at query time. This is significant in EBS because freight carrier setup can change during an accounting period, and consumers of the view automatically inherit the current state without additional maintenance.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object, ORG_FREIGHT, accessed through an APPS-owned synonym. ORG_FREIGHT is the Order Entry table that stores freight carrier and freight charge configuration at the organization (operating unit) level. It holds the freight code, its translated description, the owning organization, and the effective/disable dates that drive the view's filtering logic.

The view does not join to additional tables in the documented definition; the translation-aware description is obtained directly from columns in ORG_FREIGHT (FREIGHT_CODE_TL and DESCRIPTION). Because the referenced base object resolves through a synonym in the APPS schema, querying the view requires standard APPS access and, where applicable, the organization-level security context used by Order Entry. Multi-org considerations apply: the ORGANIZATION_ID column originates in ORG_FREIGHT and reflects the inventory organization or operating unit under which the carrier was defined.

Key Columns

• FREIGHT_CARRIER — A display label produced by NVL(DESCRIPTION, FREIGHT_CODE_TL). When a descriptive translation exists it is shown; otherwise the freight code itself is returned. This column is the natural choice for user-facing LOVs and report columns.
• FREIGHT_CODE — The underlying carrier code stored in ORG_FREIGHT. This is the value typically stored on order and shipment records and used in programmatic interfaces.
• DESCRIPTION — The descriptive text for the freight carrier, retained for reporting when a longer label is required.
• ORGANIZATION_ID — Identifies the organization (operating unit) to which the carrier belongs. It enables filtering in multi-org deployments so callers retrieve carriers relevant to a specific organization.

Common Use Cases and Queries

Typical scenarios include populating freight carrier LOVs on order entry forms, driving ship-confirm and freight-charge reports, and supplying valid carrier lists to integrations. The view's implicit predicate TRUNC(SYSDATE) < TRUNC(NVL(DISABLE_DATE, SYSDATE+1)) guarantees that only carriers not yet disabled are returned.

• List all active carriers: SELECT freight_carrier, freight_code FROM so_freight_carriers_active_v ORDER BY freight_carrier;
• Filter by organization: SELECT freight_code, description FROM so_freight_carriers_active_v WHERE organization_id = :p_org_id;
• Validate a carrier on an interface: SELECT COUNT(*) FROM so_freight_carriers_active_v WHERE freight_code = :p_code AND organization_id = :p_org_id;

Because the date comparison uses TRUNC, a carrier becomes inactive at the start of the day following its disable date; carriers with a NULL disable date are treated as active indefinitely. Consumers should therefore avoid caching results across day boundaries when strict active-status enforcement is required.