Search Results custom_measure

Overview

The APPS.POA_CUSTOM_MEASURE_LOV_V view is a public Oracle E-Business Suite database object owned by the APPS schema and registered in the Applications FND design data as PO.POA_CUSTOM_MEASURE_LOV_V. Its current status is VALID. In Oracle EBS 12.1.1 and 12.2.2, this view functions as the value-set backing for a List of Values supporting the "custom measure" column used in Procurement-related analytics and purchase order/agreement descriptive flexfield contexts. The name convention "LOV" indicates its intended role: presenting a concise, user-friendly list of custom measure codes and their descriptions that can be attached to a value set, lookup, or reporting query. It is not a transactional fact view; rather it is a reference/lookup view that standardizes the set of custom measures available to applications and reports.

The view is documented with the warning that Oracle does not support direct access to applications data through this object except from standard Oracle Applications programs, so it is generally consumed either by Oracle forms, OAF pages, or by custom reporting/integration code that accepts the same risk posture.

Underlying Base Objects

According to the documented dependency information, APPS.POA_CUSTOM_MEASURE_LOV_V references PO_LOOKUP_CODES and FND_GLOBAL. PO_LOOKUP_CODES is the Purchasing lookup codes table that stores the seeded and user-defined lookup types and their associated lookup codes and meanings. The view draws its custom measure codes, display names, and descriptions from that lookup source. FND_GLOBAL provides session context such as the current user, responsibility, and application, supporting row-level filtering or security-aware behavior during query execution. The ETRM metadata notes that the view is not referenced by any other database object, which confirms that it is a leaf-level reporting/LOV object rather than a dependency for further views or packages.

Key Columns

• CUSTOM_MEASURE_CODE (VARCHAR2(30)) — the short, unique code that identifies each custom measure; this is the value typically returned to the referencing column.
• CUSTOM_MEASURE (VARCHAR2(80)) — the display name or meaning of the measure presented to users in the LOV.
• DESCRIPTION (VARCHAR2(240)) — a longer free-text description clarifying the purpose or business meaning of the measure.

These three columns form the standard LOV pattern: a code, a display label, and an explanatory description. All are character columns, sized to accommodate the underlying lookup code definitions.

Common Use Cases and Queries

The primary use case is populating a List of Values control on a form or OAF page, or resolving a custom_measure_code into a readable measure name during reporting. The canonical query is:

• SELECT CUSTOM_MEASURE_CODE, CUSTOM_MEASURE, DESCRIPTION FROM APPS.POA_CUSTOM_MEASURE_LOV_V;
• Filtering for a specific measure: SELECT CUSTOM_MEASURE, DESCRIPTION FROM APPS.POA_CUSTOM_MEASURE_LOV_V WHERE CUSTOM_MEASURE_CODE = :p_code;
• Joining to a fact or transaction table that stores a custom measure code to produce descriptive labels.

Because the view is documented as having no dependent database objects, changes to its query text affect only the view itself. Consumers should treat it as an Oracle-managed reference object, avoid modifications, and validate that the expected lookup values exist in PO_LOOKUP_CODES before relying on the view in custom reports or integrations.