Search Results pon_pe_allocation_basis

Overview

APPS.INL_ALLOCATION_BASIS_VL is a reporting and integration view in Oracle E-Business Suite that exposes the set of allocation basis codes available to Oracle Landed Cost Management (LCM) and related trade management modules. The view derives its content from the lookup type PON_PE_ALLOCATION_BASIS, presenting each valid allocation basis as a lookup code with a corresponding descriptive name and an associated unit-of-measure classification. It is a "VL" (value-list) style view, meaning it is designed for use in list-of-values windows, concurrent program parameters, and downstream reporting queries rather than as a transactional table.

The view plays a supporting role in allocation processing, where landed cost charges or procurement expenses are apportioned across receipt or inventory lines according to a chosen basis. By surfacing allocation basis codes alongside their UOM class and base UOM code, the view enables callers to identify both the basis of apportionment (for example, quantity, volume, or weight) and the unit of measure against which that basis is measured. The constant ALLOCATION_BASIS_ID value of -1 reflects that the underlying lookup entries are not keyed by a numeric primary key in this view; instead, the lookup code itself serves as the functional identifier that users search on.

Underlying Base Objects

The view is defined over two principal sources, joined through an outer join relationship. The first is FND_LOOKUP_VALUES_VL, the standard Oracle Application Object Library value-list view that exposes lookup codes and their meanings filtered by lookup type. The view restricts this source to the lookup type PON_PE_ALLOCATION_BASIS, so only allocation basis codes configured for procurement and expense allocation are returned.

The second source is MTL_UNITS_OF_MEASURE, referenced through a synonym. The join is expressed with the Oracle outer-join operator (+) on the units-of-measure side, meaning lookup codes with no matching unit-of-measure classification are still returned, with null UOM columns. The correlation between the two sources is established through a DECODE expression that maps the lookup code value to a corresponding UOM class: 'QUANTITY' maps to Quantity, 'VOLUME' maps to Volume, and 'WEIGHT' maps to Weight. The join further restricts the unit-of-measure row to records where BASE_UOM_FLAG equals 'Y', ensuring only the base unit for each class is selected. The documented metadata also references the FND_PROFILE package, which is commonly used within such views to resolve profile-dependent behavior such as language or operating unit context.

Key Columns

• ALLOCATION_BASIS_ID — A constant value of -1 for every row. It provides a placeholder primary-key-style column for consumers that expect an identifier, but it does not uniquely distinguish rows.
• ALLOCATION_BASIS_CODE — The lookup code from PON_PE_ALLOCATION_BASIS. This is the value users search for and the functional identifier of the allocation basis, such as QUANTITY, VOLUME, or WEIGHT.
• ALLOCATION_BASIS_NAME — The meaning (translated description) associated with the lookup code, providing a user-facing label for display in lists of values.
• UOM_CLASS — The unit-of-measure class resolved through the DECODE mapping, identifying the measurement dimension against which the basis operates.
• BASE_UOM_CODE — The base unit of measure for the resolved class, where a matching base unit exists; otherwise null due to the outer join.

Common Use Cases and Queries

Typical use cases include populating allocation basis list-of-values in LCM charge configuration, validating allocation basis codes passed as concurrent program parameters, and joining allocation transactions to descriptive basis names for reporting. Because the view is small and read-only, it is safe to query directly in custom reports and integrations.

A basic query listing all available allocation bases:

• SELECT allocation_basis_code, allocation_basis_name, uom_class, base_uom_code FROM apps.inl_allocation_basis_vl ORDER BY allocation_basis_code;

A query restricted to bases with a resolved base UOM, suitable for validating quantity-based apportionment:

• SELECT allocation_basis_code, allocation_basis_name FROM apps.inl_allocation_basis_vl WHERE uom_class IS NOT NULL AND allocation_basis_code = 'QUANTITY';

For integration, the view can be joined to allocation or landed cost tables on allocation_basis_code to enrich transactional data with the descriptive name and UOM class. When searching by "allocation_basis_code," the lookup code column is the correct filter target, since ALLOCATION_BASIS_ID does not carry unique values in this view.