Results for “ahl_mr_actions_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AHL_MR_ACTIONS_V view is a reporting and integration object within the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul. It is owned by the APPS schema and carries a VALID status, indicating that it is a compiled, deployable database object rather than a placeholder or disabled artifact. The view consolidates maintenance requirement (MR) action data into a single denormalized structure, joining the base actions view to lookup value translations and to quality plan definitions. This design allows developers, report authors, and integration developers to retrieve maintenance action records together with their human-readable action meaning and the associated quality plan name without writing multi-table joins themselves.

Its role in EBS reporting and integration is principally one of convenience and standardization. Because it resolves the lookup code to a translated meaning and the plan identifier to a plan name in a single query, it is well suited to concurrent-program reports, Oracle XML Publisher (BI Publisher) data templates, and outbound interface staging. The presence of the standard fifteen attribute columns confirms that the object participates in Oracle's descriptive flexfield (DFF) model, enabling organizations to expose custom maintenance-action context without altering the base tables.

Underlying Base Objects

The ETRM documentation defines AHL_MR_ACTIONS_V as a view based on three referenced objects. The primary source is AHL_MR_ACTIONS_VL, itself a view that supplies the maintenance requirement action rows, including the surrogate key, object version number, header reference, action code, plan reference, description, and DFF attributes. The second object is FND_LOOKUP_VALUES_VL, the standard Oracle Application Object Library lookup values view, which is joined to AHL_MR_ACTIONS_VL on the action code using the lookup type AHL_FMP_MR_ACTION. This join supplies the translated MEANING value for each action. The third object is QA_PLANS, physically referenced as a synonym, joined on PLAN_ID to supply the quality plan NAME.

Both the lookup join and the quality plan join are written as outer joins in the view text, so maintenance action rows are returned even when no matching lookup value or quality plan exists. Because AHL_MR_ACTIONS_VL and FND_LOOKUP_VALUES_VL are views and QA_PLANS is accessed through a synonym, the object is read-only in practical terms; it is not a table and cannot be directly updated through the view.

The join conditions are:

• F.LOOKUP_TYPE (+) = 'AHL_FMP_MR_ACTION' AND F.LOOKUP_CODE (+) = A.MR_ACTION_CODE — resolves the action meaning.
• Q.PLAN_ID (+) = A.PLAN_ID — resolves the quality plan name.

Key Columns

• MR_ACTION_ID — primary identifier of the maintenance requirement action record.
• OBJECT_VERSION_NUMBER — optimistic locking and concurrency control value inherited from the underlying row.
• MR_HEADER_ID — foreign key to the maintenance requirement header that owns the action.
• MR_ACTION_CODE — the lookup code representing the action; joined to lookup type AHL_FMP_MR_ACTION.
• MEANING — the translated, user-facing description of the action code from FND_LOOKUP_VALUES_VL.
• PLAN_ID — identifier of the associated quality plan.
• PLAN_NAME — the quality plan name resolved from QA_PLANS.NAME.
• DESCRIPTION — free-text description of the action.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context and segment columns.

Common Use Cases and Queries

Typical scenarios include listing all actions for a given maintenance requirement header with their meanings and plan names, building a report of actions that reference quality plans, and staging MR action data for external systems. The following query retrieves all actions for a specific header:

SELECT mr_action_id, mr_action_code, meaning, plan_id, plan_name, description FROM apps.ahl_mr_actions_v WHERE mr_header_id = :mr_header_id ORDER BY mr_action_id;

To report only actions that are linked to a quality plan:

SELECT mr_action_id, mr_action_code, meaning, plan_name FROM apps.ahl_mr_actions_v WHERE plan_id IS NOT NULL;

Because the lookup and plan joins are outer joins, callers should test for NULL in MEANING or PLAN_NAME when the referenced lookup value or plan is missing. Reports should also expect the DFF attribute columns to be populated only when an attribute category applies.