Search Results position_inventory_item_id

Overview

The view APPS.AHL_MR_EFFECTIVITIES_V is a reporting and integration layer within the Oracle Enterprise Asset Management (EAM) and Enterprise Asset Management for Complex Maintenance, Repair, and Overhaul (CMRO) modules. It presents maintenance program effectivity data, which defines the conditions, thresholds, and durations under which a maintenance requirement or maintenance program becomes applicable to a specific asset, position, or relationship. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is primarily consumed by Oracle Forms-based maintenance program setup screens, concurrent programs, and external integrations that require a denormalized, user-friendly representation of effectivity records. The view resolves internal surrogate identifiers into meaningful values, including item concatenated segments, position references, and lookup meanings, thereby simplifying downstream reporting without requiring callers to perform multiple joins manually.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is owned by APPS and is defined over several referenced base objects. The principal source is AHL_MR_EFFECTIVITIES_APP_V, an application-layer view that supplies the core effectivity attributes such as MR_EFFECTIVITY_ID, MR_HEADER_ID, PC_NODE_ID, threshold dates, and duration values. The view outer-joins to MTL_SYSTEM_ITEMS_KFV (a synonym) to resolve inventory item identifiers into concatenated segment descriptions, and to AHL_PC_NODES_B (a synonym) to obtain the position or configuration node name. The AHL_POSITION_ALTERNATES_V view participates in the relationship-based joins that map alternate position references. Two lookup joins are performed against FND_LOOKUP_VALUES_VL: one for the program duration unit of measure (AHL_UMP_TIME_UOM) and one for the AHL_YES_NO_TYPE default flag meaning. The AHL_MC_PATH_POSITION_PVT package is referenced in the select list to derive position references by ID, and FND_PROFILE is documented as a referenced object, typically used for profile-driven filtering or value resolution within the underlying application view.

Key Columns

The view exposes a comprehensive set of columns that describe maintenance effectivity records. Key structural identifiers include MR_EFFECTIVITY_ID, OBJECT_VERSION_NUMBER, and MR_HEADER_ID, which link the effectivity to its parent maintenance requirement header. Item and position context is provided through INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, RELATIONSHIP_ID, and PC_NODE_ID, with PC.NAME supplying the node description. Effectivity timing is captured by THRESHOLD_DATE, PROGRAM_DURATION, and PROGRAM_DURATION_UOM_CODE, the latter resolved to a display value via UOM.MEANING from the AHL_UMP_TIME_UOM lookup. The DEFAULT_FLAG column, decoded through DEF.MEANING, indicates whether the effectivity is the default for its context. The view also exposes fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) and APPLICATION_USG_CODE, supporting extensibility and usage classification between maintenance and non-maintenance contexts.

Common Use Cases and Queries

The view is commonly used to report which maintenance effectivities apply to particular assets or positions, to drive preventive maintenance scheduling, and to feed integrations that synchronize maintenance programs with external planning systems. A typical query retrieves all effectivities for a given maintenance header with resolved item and UOM descriptions:

• SELECT mr_effectivity_id, mr_header_id, concatenated_segments, pc_node_id, name, threshold_date, program_duration, meaning FROM apps.ahl_mr_effectivities_v WHERE mr_header_id = :p_header_id ORDER BY threshold_date;
• Filtering on the duration UOM preference, which aligns with the user search term ahl_ump_time_uom: SELECT mr_effectivity_id, program_duration_uom_code, meaning FROM apps.ahl_mr_effectivities_v WHERE program_duration_uom_code = 'DAY';
• Identifying default effectivity records using the AHL_YES_NO_TYPE lookup meaning to distinguish primary from alternate configurations.

Because the view performs the lookup and item resolution joins on behalf of callers, it is preferred over direct queries against AHL_MR_EFFECTIVITIES_APP_V in reporting contexts, though consumers should note the use of outer joins and the DISTINCT qualifier, which can affect performance when queried across large maintenance program datasets.