Search Results custom_measure_code

Overview

POA_CUSTOM_MEASURE_LOV_V is a read-only Purchasing (PO) view exposed within Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the standard EBS convention for list-of-values (LOV) views, and it is designed to supply the set of valid "custom measure" values selectable in Purchasing-related user interfaces and inquiries. In ETRM terminology, the view serves as a lookup-driven LOV source for the POA_CUSTOM_MEASURE lookup type, surfacing the code, the displayable value, and an accompanying description for each measure.

The view is defined with the WITH READ ONLY clause, so no DML is permitted against it. It is not implemented as a physical database object in all environments; the ETRM metadata marks it as "Not implemented in this database," which indicates that availability depends on the installed baseline and any customer-specific deployment. Where it does exist, it provides a stable reporting and integration surface for retrieving custom measure reference data without querying the underlying lookup infrastructure directly.

Underlying Base Objects

The view is defined over a single documented base object: PO_LOOKUP_CODES, the Purchasing lookup codes table that holds Oracle-standard and extensible lookup values across many Purchasing lookup types. The definition applies a fixed predicate on LOOKUP_TYPE equal to 'POA_CUSTOM_MEASURE', thereby restricting the result set to only those lookup rows relevant to custom measures. Because the filter is embedded in the view text, consumers automatically receive an already-scoped dataset and do not need to reproduce the lookup type restriction in their own queries.

No other base objects are documented as referenced by this view. Conceptually, the relationship is a simple projection: one row in PO_LOOKUP_CODES matching the target lookup type produces one row in the view, with column aliasing applied to present the lookup code as the custom measure code, the displayed field as the measure itself, and the description as descriptive text. Because lookups are commonly maintained through the application's lookup maintenance forms, the view reflects the current configured set of custom measures at query time.

Key Columns

• CUSTOM_MEASURE_CODE — The lookup code value identifying the custom measure. This is the stored code used as the key when the measure is referenced elsewhere, and it is the column most likely returned by integrations and downstream reporting logic.
• CUSTOM_MEASURE — The displayed value for the measure, derived from the lookup's displayed field. This is typically the label presented to users within an LOV or report.
• DESCRIPTION — Free-text description associated with the lookup row, providing additional explanatory context for the measure.

These three columns correspond directly to LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION in PO_LOOKUP_CODES, with the first two aliased to Purchasing-specific names.

Common Use Cases and Queries

Typical uses include validating that a custom measure value captured in data entry or integration exists in the configured lookup set, presenting descriptive labels alongside stored codes in reports, and reconciling custom measure reference data between environments. A simple retrieval of all configured measures is:

SELECT custom_measure_code,
       custom_measure,
       description
  FROM poa_custom_measure_lov_v
 ORDER BY custom_measure;

To check whether a specific code, such as the value a user searched for, is valid:

SELECT custom_measure_code,
       custom_measure,
       description
  FROM poa_custom_measure_lov_v
 WHERE custom_measure_code = :p_code;

For reporting that requires both code and human-readable text in a single output column:

SELECT custom_measure_code,
       custom_measure || ' (' || custom_measure_code || ')' AS display_value
  FROM poa_custom_measure_lov_v;

Because the object is read-only and lookup-backed, it is safe for concurrent reporting access and requires no special locking considerations. Where the view is not deployed, equivalent results can be obtained by querying PO_LOOKUP_CODES directly with the same LOOKUP_TYPE filter.