Search Results ahl_mr_actions_b




Overview
Explore in AI Chat

Overview

AHL_MR_ACTIONS_B is the base (non-translated) table within the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module that stores discrete maintenance actions associated with a maintenance requirement. Each row represents a single actionable step or operation defined under a maintenance requirement header, forming the operational detail layer of the maintenance requirement model. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the AHL schema and holds 27 documented columns. Its role is to bridge maintenance requirement definitions to execution and quality planning by linking actions to requirement headers and, where applicable, to QA plans.

From a heuristic Data Vault modeling perspective, this table leans toward a satellite classification. It carries descriptive attributes and business keys (MR_ACTION_CODE, PLAN_ID) that attach to the hub represented by AHL_MR_HEADERS_B, with a foreign key to the header and a dependent translation table.

Key Information Stored

The surrogate primary key is MR_ACTION_ID, enforced by AHL_MR_ACTIONS_B_PK. Business-key candidate unique indexes are AHL_MR_ACTIONS_B_U1 (on MR_ACTION_ID) and AHL_MR_ACTIONS_B_U2 (a composite of MR_HEADER_ID, MR_ACTION_CODE, and PLAN_ID). The most significant columns include:

  • MR_ACTION_ID — surrogate primary key uniquely identifying each maintenance action.
  • MR_HEADER_ID — foreign key to AHL_MR_HEADERS_B, the parent maintenance requirement.
  • MR_ACTION_CODE — the business code identifying the action within its header.
  • PLAN_ID — foreign key to QA_PLANS, associating a quality plan with the action.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS controlling row-level access.
  • OBJECT_VERSION_NUMBER — optimistic locking control.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns for the most recent change.
  • CREATION_DATE / CREATED_BY — audit columns recording initial creation.
  • LAST_UPDATE_LOGIN — login audit reference.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS DFF (Descriptive Flexfield) column set for extensibility.

Common Use Cases and Queries

Typical scenarios include retrieving all actions for a given requirement, joining to QA plans for quality execution, and reporting on action usage across headers. A representative query follows:

  • List actions for a header: SELECT MR_ACTION_ID, MR_ACTION_CODE, PLAN_ID FROM AHL.AHL_MR_ACTIONS_B WHERE MR_HEADER_ID = :header_id;
  • Join to header and QA plan: SELECT b.MR_ACTION_CODE, h.MR_HEADER_NAME, p.PLAN_NAME FROM AHL_MR_ACTIONS_B b JOIN AHL_MR_HEADERS_B h ON b.MR_HEADER_ID = h.MR_HEADER_ID JOIN QA_PLANS p ON b.PLAN_ID = p.PLAN_ID;
  • Fetch translated descriptions: SELECT t.MR_ACTION_NAME FROM AHL_MR_ACTIONS_TL t WHERE t.MR_ACTION_ID = :id AND t.LANGUAGE = USERENV('LANG');

Reports frequently resolve DFF attributes and enforce security group filtering for multi-org access.

Related Objects

The principal related objects, derived from documented foreign keys, are:

  • AHL_MR_HEADERS_B — parent table joined on MR_HEADER_ID.
  • AHL_MR_ACTIONS_TL — translation table joined on MR_ACTION_ID.
  • QA_PLANS — quality plan reference joined on PLAN_ID.
  • FND_SECURITY_GROUPS — security reference joined on SECURITY_GROUP_ID.