Results for “mr_id”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL.AHL_SNAPSHOTS is a table owned by the AHL schema (Complex Maintenance Repair and Overhaul). Per the ETRM repository, the table is VALID and its documented purpose is to store information about snapshots. In operational terms, it records point-in-time captures of maintenance, repair, and overhaul (MRO) execution data — specifically the pricing and cost position of a visit, a visit task, or a maintenance requirement header at a given moment. This supports cost tracking, estimate-versus-actual comparison, and historical analysis of MRO work packages.

The documented schema contains 32 columns, with a primary key constraint named AHL_SNAPSHOTS_PK on SNAPSHOT_ID. The heuristic Data Vault classification derived from the foreign key structure is link. As a modeling suggestion, this reflects the table's role as an associative entity connecting a visit, a visit task, and a maintenance requirement header to a snapshot record, rather than a pure descriptive satellite.

Key Information Stored

The most significant columns fall into identity, relationship, financial, and audit categories.

• SNAPSHOT_ID — surrogate primary key and the column underlying AHL_SNAPSHOTS_PK.
• SNAPSHOT_NUMBER — the human-readable business key candidate; the externally referenced snapshot identifier.
• VISIT_ID — foreign key to AHL_VISITS_B, identifying the visit the snapshot belongs to.
• VISIT_TASK_ID — foreign key to AHL_VISIT_TASKS_B, identifying the visit task captured.
• MR_ID — foreign key to AHL_MR_HEADERS_B, identifying the maintenance requirement header.
• ESTIMATED_PRICE and ACTUAL_PRICE — the quoted versus realized price for the captured work.
• ESTIMATED_COST and ACTUAL_COST — the planned versus incurred cost, enabling variance analysis.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the AHL business object layer.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) segment set for customer-specific extensions.

Common Use Cases and Queries

Snapshots are used to freeze the commercial state of MRO work so that later changes to estimates or actuals do not distort prior reporting. Typical scenarios include margin analysis by visit, drift reporting between estimated and actual cost, and auditing the scope captured at a milestone.

A representative query joining the snapshot to its parent visit is:

SELECT s.snapshot_number, s.visit_id, s.mr_id,
  s.estimated_cost, s.actual_cost,
  (s.actual_cost - s.estimated_cost) variance
FROM ahl_snapshots s
WHERE s.visit_id = :p_visit_id
ORDER BY s.creation_date;

Cost variance reporting by maintenance requirement aggregates the same columns grouped by MR_ID, while a security-scoped listing filters on SECURITY_GROUP_ID. For transaction-processing contexts, developers query by SNAPSHOT_NUMBER or SNAPSHOT_ID to retrieve a single snapshot and then navigate to the referenced visit or task.

Related Objects

Relationship metadata identifies the following parent tables, joined by the listed columns, plus the principal external referencers.

• AHL_VISITS_B — joined via AHL_SNAPSHOTS.VISIT_ID.
• AHL_VISIT_TASKS_B — joined via AHL_SNAPSHOTS.VISIT_TASK_ID.
• AHL_MR_HEADERS_B — joined via AHL_SNAPSHOTS.MR_ID.
• FND_SECURITY_GROUPS — joined via AHL_SNAPSHOTS.SECURITY_GROUP_ID.
• ASG_PUBLICATION_ITEMS — references the snapshot through SNAPSHOT_ID for publication/publishing use.
• ISC_DBI_INV_DETAIL_SNAPSHOTS, ISC_DBI_SUPPLIES_SNAPSHOTS, and ISC_DBI_SHORTFALL_SNAPSHOTS — ISC/DBI reporting objects that reference the snapshot by SNAPSHOT_ID.

Applications should retrieve and mutate snapshot records through AHL's supported business logic and concurrent programs rather than direct DML, preserving the WHO audit columns and optimistic locking integrity enforced by OBJECT_VERSION_NUMBER.