Results for “all_jobs_complete”

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

Overview

APPS.AHL_MR_INSTANCES_V is a reporting view in the Oracle E-Business Suite Maintenance Management module (eTRM / Enterprise Asset Management). It consolidates maintenance work order (MR) header data, unit effectivity instances, visit scheduling, work order execution status, and quality assurance assignments into a single denormalized query source. The view presents one row per unit effectivity instance associated with a maintenance visit task of type SUMMARY or UNASSOCIATED, enriched with organizational, departmental, and status information.

Its principal role is to serve as the data source for maintenance instance inquiry screens, status dashboards, and downstream reporting. Because it resolves the maintenance status dynamically via AHL_COMPLETIONS_PVT.get_mr_status, it reflects the current lifecycle state of each maintenance requirement rather than a stored snapshot.

Underlying Base Objects

The view is defined over several core eTRM and supply chain objects. AHL_UE_DEFERRAL_DETAILS_V supplies the unit effectivity and deferral detail rows that form the driving set. WIP_DISCRETE_JOBS joins the associated work order by wip_entity_id to retrieve scheduled start and completion dates. AHL_WORKORDERS links the visit task to actual execution dates, while AHL_VISITS_B and AHL_VISIT_TASKS_B provide visit numbering, timing, organization, and department context.

FND_LOOKUP_VALUES_VL supplies the maintenance requirement status code and meaning from the AHL_PRD_MR_STATUS lookup type, resolved through AHL_COMPLETIONS_PVT. ORG_ORGANIZATION_DEFINITIONS (filtered by MO_GLOBAL.get_current_org_id) provides organization security and naming. BOM_DEPARTMENTS contributes department descriptions. CS_INCIDENTS_ALL_VL and CS_INCIDENT_TYPES_VL supply incident-based titles where no MR header exists, and AHL_UTILITY_PVT.get_unit_name resolves the human-readable asset name. Supporting packages include FND_GLOBAL, FND_PROFILE, HR_GENERAL, and HR_SECURITY for context and security.

Key Columns

• unit_effectivity_id — primary identifier of the unit effectivity instance, linking the maintenance requirement to a specific asset instance.
• Mr_header_id / Cs_incident_id — mutually exclusive identifiers; the view uses DECODE so that MR-based rows show the MR title and description, while incident-based rows fall back to the incident title and summary.
• Lookup_code / Meaning — the maintenance requirement status (for example, ALL_JOBS_CLOSED, ALL_JOBS_COMPLETE, ACCOMPLISHED) and its display meaning.
• Visit_id / Visit_number / Start_date_time — visit scheduling identifiers and start timing.
• Organization_id / Organization_name / Department_id / Description — organizational and departmental context derived from ORG_ORGANIZATION_DEFINITIONS and BOM_DEPARTMENTS.
• actual_start_date / actual_end_date — exposed only when the status is ACCOMPLISHED, ALL_JOBS_COMPLETE, or ALL_JOBS_CLOSED; otherwise NULL.
• scheduled_start_date / scheduled_completion_date — planned dates from WIP_DISCRETE_JOBS.
• Qa_inspection_type_code / Qa_Plan_id / Qa_Collection_id — quality assurance attributes associated with the instance.
• Instance_number and the utility-derived unit name — human-readable asset identification.

Common Use Cases and Queries

A frequent requirement is identifying maintenance instances whose work orders have reached a terminal status — precisely the scenario behind the search term "all_jobs_closed." The following query lists closed instances with their actual completion dates:

SELECT Mr_header_id, Instance_number, Lookup_code, actual_end_date, Organization_name
FROM APPS.AHL_MR_INSTANCES_V
WHERE Lookup_code = 'ALL_JOBS_CLOSED';

Other common patterns include filtering all open work for an organization, validating scheduled versus actual date variance for a visit, and joining to AHL_MR_HEADERS_B to reconcile header-level detail. Because the view relies on MO_GLOBAL.get_current_org_id and HR security, it returns only rows visible to the invoking responsibility, making it suitable for multi-org reporting without additional org predicates.