Results for “freight_code”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
POS_ORG_FREIGHT_V is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and deployed in support of the ICX (Oracle iProcurement) product family. It is documented as a VALID object in both EBS 12.1.1 and 12.2.2 and forms part of the point-of-sale (POS) view family used by iProcurement to populate freight-related list-of-values (LOV) selections during requisition and checkout processing. As its name suggests, the view supplies a concise, pre-joined set of freight codes and descriptions scoped to an operating unit or inventory organization, allowing iProcurement pages and dependent programmatic interfaces to present valid freight carriers and charges without querying the base transaction table directly.
In the broader Oracle EBS reporting and integration landscape, the view functions as a lightweight abstraction layer over the freight definition table. It exposes only the descriptive attributes relevant to an LOV, filtering and ordering the results so that front-end components receive predictable, sorted results. This aligns with Oracle's conventional POS_*_LOV_V design pattern, where purpose-built views shield the UI from complex multi-organization joins and enforce the organization-level security context.
Underlying Base Objects
Per the ETRM metadata, the view is defined over a single documented base object: the synonym ORG_FREIGHT. In EBS, ORG_FREIGHT is the underlying table that stores freight carrier and freight charge definitions at the organization level; the APPS-level synonym resolves to the actual base table (typically ORG_FREIGHT in the APPLSYS or product schema such as BOM or INV). The view text is a direct projection:
- SELECT DESCRIPTION, FREIGHT_CODE, ORGANIZATION_ID FROM ORG_FREIGHT ORDER BY DESCRIPTION
There are no additional joins, unions, or analytic functions documented, which confirms the view is a simple, read-only projection. Because the projection restricts columns to DESCRIPTION, FREIGHT_CODE, and ORGANIZATION_ID, the view does not expose audit columns such as CREATION_DATE, CREATED_BY, or LAST_UPDATE_DATE present on the base table, reinforcing its LOV-only purpose.
Key Columns
The view exposes the following documented columns:
- FREIGHT_CARRIER — The carrier identifier associated with the freight definition. In the documented metadata this column appears in the column listing and in many releases is exposed as part of the LOV output, though the view's SELECT clause in 12.2.2 projects DESCRIPTION, FREIGHT_CODE, and ORGANIZATION_ID, so treat FREIGHT_CARRIER as a metadata-listed attribute whose availability depends on the exact patch level.
- FREIGHT_CODE — The unique short code identifying the freight definition within the organization; this is the value captured on requisitions and purchase orders when a user selects a freight entry.
- ORGANIZATION_ID — The inventory or operating unit organization to which the freight definition belongs, providing the security and filtering context.
- DESCRIPTION — The user-facing, human-readable description of the freight carrier or charge, and the column on which the view is explicitly ordered. This is the primary display value in the LOV.
Common Use Cases and Queries
The view is most commonly queried to validate freight codes during requisition entry, to populate custom LOVs, and to reconcile freight definitions loaded by interfaces. Reporting use is typically for organization-scoped freight lookups.
- List all freight definitions for a specific organization:
SELECT freight_code, description, organization_id FROM pos_org_freight_lov_v WHERE organization_id = :org_id ORDER BY description;
- Resolve a description to its code for validation:
SELECT freight_code FROM pos_org_freight_lov_v WHERE organization_id = :org_id AND description = :desc;
- Detect duplicate descriptions within an organization for data-cleanup:
SELECT description, COUNT(*) FROM pos_org_freight_lov_v GROUP BY description, organization_id HAVING COUNT(*) > 1;
Because the view is read-only and ordered, it is safe for high-frequency LOV lookups in iProcurement without imposing write locks on the base ORG_FREIGHT table.
-
View: POS_ORG_FREIGHT_LOV_V 12.2.2
APPS.POS_ORG_FREIGHT_LOV_V·↳ ORG_FREIGHT·Explore ICX module →
-
View: POS_ORG_FREIGHT_LOV_V 12.1.1
APPS.POS_ORG_FREIGHT_LOV_V·↳ ORG_FREIGHT·Explore ICX module →
-
View: POS_ACK_SELECT_V 12.1.1
APPS.POS_ACK_SELECT_V·↳ FND_PROFILE·↳ HR_EMPLOYEES·↳ HR_GENERAL·Explore ICX module →
-
View: POS_ACK_SELECT_V 12.2.2
APPS.POS_ACK_SELECT_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ HR_EMPLOYEES·Explore ICX module →