Results for “lookup_code”

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

Overview

QP_CHARGE_LOOKUP is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Advanced Pricing (QP) product family and is classified as VALID in the ETRM registry for both release 12.1.1 and 12.2.2. The view exposes the set of charge types that are available when configuring Freight and Special charges within Oracle Advanced Pricing. Rather than storing data of its own, it consolidates a constrained subset of lookup codes drawn from two distinct lookup sources, presenting them through a uniform column layout that mirrors the standard Oracle lookups interface.

Because pricing, freight, and order management functionality depends on consistent charge type codes across modules, this view serves as the canonical read interface for charge type enumeration. Reporting tools, concurrent programs, and integration layers can query QP_CHARGE_LOOKUP instead of hard-coding decode logic or querying multiple lookup tables independently.

Underlying Base Objects

The view text is defined as the UNION of two lookup queries. The first selects from QP_LOOKUPS where LOOKUP_TYPE equals 'FREIGHT_CHARGES_TYPE'. The second selects from WSH_LOOKUPS where LOOKUP_TYPE equals 'FREIGHT_COST_TYPE'. Both branches project the same seven columns, allowing the UNION to produce a single de-duplicated result set. Note that the documented ETRM 12.2.2 metadata lists FND_LOOKUP_VALUES (accessed via a synonym) as the referenced base object, reflecting the underlying standard lookup infrastructure onto which the QP and WSH lookup views are built.

The UNION operator implies that identical rows returned by both branches are collapsed, so a charge type appearing in both lookup types is returned only once. This behavior matters when the same lookup code is replicated across the QP and WSH lookup families, which is common for shared freight charge definitions.

Key Columns

• LOOKUP_TYPE — Identifies the source lookup category, either FREIGHT_CHARGES_TYPE or FREIGHT_COST_TYPE. This value indicates which functional area contributed the row.
• LOOKUP_CODE — The internal code stored on transactional and setup records to identify the charge type.
• MEANING — The user-facing display name for the charge type, typically shown in LOVs and reports.
• DESCRIPTION — Optional extended text describing the charge type's purpose.
• ENABLED_FLAG — Indicates whether the lookup value is currently active ('Y') or disabled ('N').
• START_DATE_ACTIVE — The date from which the lookup value becomes valid.
• END_DATE_ACTIVE — The date after which the lookup value is no longer valid.

Common Use Cases and Queries

Typical uses include populating charge type lists in custom freight or special charge setups, validating charge codes passed through integration interfaces, and building lookup reports for pricing administrators. The following query returns all currently enabled freight charge types:

• SELECT lookup_type, lookup_code, meaning, description FROM qp_charge_lookup WHERE enabled_flag = 'Y' ORDER BY lookup_type, meaning;

To restrict to active values by date at a point in time, apply the effective date range:

• SELECT lookup_code, meaning FROM qp_charge_lookup WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

To distinguish codes originating from the WSH freight cost lookup family:

• SELECT lookup_code, meaning FROM qp_charge_lookup WHERE lookup_type = 'FREIGHT_COST_TYPE';

Because the view is read-only and derives entirely from seeded lookup data, charge types are added or modified through the standard lookup maintenance forms rather than DML against the view itself. Any new charge type must be defined under one of the two supported lookup types to appear in QP_CHARGE_LOOKUP.