Search Results price_element_code

Overview

The INL_CHARGE_LINE_TYPES_VL view is a multilingual (VL, "view language") dictionary view owned by the APPS schema in Oracle Landed Cost Management (INL). It exposes Charge Line Type information translated into the session's runtime language, presenting a user-facing identity for each charge line type alongside the attributes required by Landed Cost Management processing. In Oracle E-Business Suite 12.1.1 and 12.2.2, INL provides landed cost estimation, actual cost adjustment, and invoice matching for imported goods, and charge line types form the configurable backbone of that functionality: each type represents a category of landed cost (for example freight, duty, insurance, or brokerage) that can be attached to a shipment or trade transaction and ultimately allocated across the received items.

The view is classified as VALID and is intended for read-only reporting, inquiry, and integration rather than as a transactional entity. Because it is a _VL view, it joins the underlying base view to translation data so that the code (the primary identifier) remains language-independent while the name (CHARGE_LINE_TYPE_NAME) is returned in the caller's language. This makes it a reliable source for custom reports, LOV queries, and interface extracts that must display charge line type descriptions in the user's locale.

Underlying Base Objects

According to the documented ETRM metadata for release 12.2.2, the view is defined over a single referenced base object: PON_COST_FACTORS_VL, which is itself a view owned by APPS. This is a deliberate design decision in Landed Cost Management: rather than maintaining a separate charge line type table, INL reuses the Oracle Purchasing cost factor (price element) infrastructure to define the chargeable elements that drive landed cost calculations. The view text performs a direct projection from PON_COST_FACTORS_VL, renaming and, in several cases, defaulting or decoding attributes so that the Purchasing cost factor is presented in the shape expected by Landed Cost Management consumers.

Because the view is a thin wrapper, any change to the underlying cost factor record—such as re-enabling or disabling a price element—is immediately reflected in INL_CHARGE_LINE_TYPES_VL. No additional base tables are documented as directly referenced by this view.

Key Columns

• CHARGE_LINE_TYPE_ID — Mapped from PRICE_ELEMENT_TYPE_ID; the unique surrogate key of the charge line type, used as a foreign key elsewhere in INL.
• CHARGE_LINE_TYPE_CODE — Mapped from PRICE_ELEMENT_CODE; the language-independent, user-visible short code for the charge line type.
• CHARGE_LINE_TYPE_NAME — Mapped from NAME; the translated, session-language description of the charge line type.
• ALLOCATION_BASIS — Derived as NVL(ALLOCATION_BASIS, 'VALUE'); identifies the basis by which the charge is apportioned across lines, defaulting to VALUE when the underlying cost factor does not specify one. This column is the most commonly searched attribute on this view and answers the business question "how will this charge be spread across the received goods?"
• DFLT_LANDED_COST_FLAG — Hard-coded to 'Y', indicating that the elements surfaced here are intended as landed cost charge line types.
• AP_LINE_TYPE_CODE — Hard-coded to 'MISCELLANEOUS', reflecting the default Oracle Payables invoice line type used when a landed cost charge is billed.
• ACTIVE_FROM_DATE / ACTIVE_TO_DATE — Derived dates establishing the effective period; ACTIVE_TO_DATE is set to 01-JAN-1900 when the underlying ENABLED_FLAG is not 'Y', effectively terminating the record's active range.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit (WHO) columns inherited from the base view.

Common Use Cases and Queries

Typical usage includes populating custom Landed Cost inquiry reports, driving value sets and LOVs for charge line type selection, and auditing which allocation bases are configured across the system. A representative query to list active charge line types and their allocation bases is:

• SELECT charge_line_type_id, charge_line_type_code, charge_line_type_name, allocation_basis FROM apps.inl_charge_line_types_vl WHERE active_to_date = TO_DATE('01-JAN-1900','DD-MON-YYYY') ORDER BY charge_line_type_name; — note the counterintuitive convention that an ACTIVE_TO_DATE of 1900 denotes an enabled record.
• SELECT allocation_basis, COUNT(*) FROM apps.inl_charge_line_types_vl GROUP BY allocation_basis; — summarizes configured allocation bases (for example VALUE, QUANTITY, WEIGHT, or VOLUME) across all charge line types.
• SELECT charge_line_type_code, charge_line_type_name FROM apps.inl_charge_line_types_vl WHERE UPPER(charge_line_type_name) LIKE UPPER('%FREIGHT%'); — locates charge line types by descriptive name.

Because the view exposes no insert, update, or delete semantics, all maintenance of charge line types and their allocation bases must be performed through the underlying Purchasing cost factor setup or the Landed Cost Management configuration UI; the view should be treated strictly as a query surface.