Results for “freight_charges_type”

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

Overview

APPS.QP_CHARGE_LOOKUP is a reporting and integration view in Oracle E-Business Suite that exposes a curated subset of Oracle Advanced Pricing freight-related lookup values. Rather than presenting the entire FND_LOOKUP_VALUES table, the view filters that repository to two specific lookup types associated with freight charge and freight cost classification: FREIGHT_CHARGES_TYPE and FREIGHT_COST_TYPE. The view is owned by the APPS schema and is intended to give downstream reports, concurrent programs, and interface logic a single, stable access point for the valid freight lookup codes used within the pricing and shipping domains.

The view is significant for users searching on the term "freight_cost_type." That term maps directly to the FREIGHT_COST_TYPE lookup type referenced in the view predicate, where VIEW_APPLICATION_ID equals 665. The companion predicate, VIEW_APPLICATION_ID = 661 with LOOKUP_TYPE = 'FREIGHT_CHARGES_TYPE', covers the related freight charges classification. By combining both predicates with an OR condition, QP_CHARGE_LOOKUP presents freight charge and freight cost lookup values side by side, keyed by LOOKUP_TYPE so consumers can distinguish them.

Underlying Base Objects

The view is defined solely over FND_LOOKUP_VALUES, accessed through a synonym in the APPS schema. No join to any pricing or shipping base table is present in the documented view text. All filtering is performed against columns of FND_LOOKUP_VALUES itself: LANGUAGE, SECURITY_GROUP_ID, VIEW_APPLICATION_ID, and LOOKUP_TYPE.

Three constants constrain the result set. LANGUAGE is resolved dynamically via USERENV('LANG'), so the view returns values in the session's current language. SECURITY_GROUP_ID is fixed at 0, restricting output to the standard, non-seeded security grouping. The VIEW_APPLICATION_ID and LOOKUP_TYPE pairings isolate exactly the two freight lookup families. Because the view is a thin projection, its behavior mirrors FND_LOOKUP_VALUES and reflects the current enabled and date-bounded state of those lookup codes.

Key Columns

• LOOKUP_TYPE — Identifies which of the two freight lookup families the row belongs to, either FREIGHT_CHARGES_TYPE or FREIGHT_COST_TYPE. This is the primary discriminator for consumers filtering on freight_cost_type.
• LOOKUP_CODE — The internal code value stored on transactional records such as freight charges; the value referenced by pricing and shipping logic.
• MEANING — The user-facing display name for the lookup code, typically shown on forms, reports, and user interfaces.
• DESCRIPTION — Supplemental free-text explanation of the lookup code.
• ENABLED_FLAG — Indicates whether the lookup value is currently active; Y denotes enabled and N denotes disabled.
• START_DATE_ACTIVE and END_DATE_ACTIVE — The effective date range during which the lookup value is valid, enabling time-bounded classification.

Common Use Cases and Queries

The view is commonly used to populate LOVs, validate freight cost type values during order or freight charge entry, and join lookup descriptions to transactional freight data. A frequent pattern retrieves only enabled, currently effective codes for the freight cost type.

The following query lists valid freight cost types:

SELECT lookup_code, meaning, description, enabled_flag, start_date_active, end_date_active FROM apps.qp_charge_lookup WHERE lookup_type = 'FREIGHT_COST_TYPE' AND enabled_flag = 'Y' ORDER BY lookup_code;

To retrieve both freight lookup families in a single result set, the WHERE clause can be relaxed to rely on the view's own predicate, filtering instead by lookup type as needed. Joining the view to freight charge records on LOOKUP_CODE provides descriptive labels for reporting, while filtering on START_DATE_ACTIVE and END_DATE_ACTIVE supports point-in-time analysis. Because the view isolates these two lookup types and excludes other security groups, it simplifies report logic and avoids exposing unrelated lookup values.