Results for “mr_status_code”

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

Overview

OKX_PM_PROGRAMS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Contracts Integration module (OKX). It exposes preventive maintenance program records sourced from the Oracle Enterprise Asset Management (EAM) maintenance header layer, presenting them in a flattened structure suited to contract and service integration reporting. The view is defined in both Oracle EBS 12.1.1 and 12.2.2 and carries a VALID status. Its documented purpose is to provide a consolidated presentation of preventive maintenance programs — that is, the master definitions that govern scheduled maintenance work — so that downstream contract, purchasing, and service processes can reference them without querying the maintenance schema directly.

The view is a thin projection over the maintenance header view AHL_MR_HEADERS_V, filtered with a single predicate restricting rows to TYPE_CODE = 'PROGRAM'. Because it retains the column semantics of the underlying maintenance header view while renaming identifiers for generic integration use, it functions as a purpose-built interface layer between EAM maintenance definitions and the OKX contracts integration stack.

Underlying Base Objects

The documented metadata identifies the referenced base objects as AHL_MR_HEADERS_B (SYNONYM), AHL_MR_HEADERS_TL (SYNONYM), FND_LOOKUP_VALUES (SYNONYM), and the FND_PROFILE package. These are reached indirectly: the view text selects from AHL_MR_HEADERS_V rather than from the base tables directly, so the base maintenance header tables and the lookup/profile mechanisms are resolved through that intermediate view.

• AHL_MR_HEADERS_B — the base maintenance requirement header table storing program-level attributes such as type code, status code, and effective dates.
• AHL_MR_HEADERS_TL — the translation table supplying the language-dependent TITLE and DESCRIPTION values.
• FND_LOOKUP_VALUES — resolves coded values such as TYPE_CODE, TYPE, MR_STATUS_CODE, and STATUS into their display meanings.
• FND_PROFILE — supplies session and site profile context, notably language and security-related settings, used during lookup resolution.

No DML is supported; the view is read-only and inherits the query-only nature of its source.

Key Columns

• ID1 — mapped from MR_HEADER_ID, the surrogate key of the maintenance program record. It is the primary join key for downstream integration.
• ID2 — a constant literal '#', retained as a placeholder identifier column in the integration contract.
• NAME — the program title, sourced from TITLE in the underlying translation layer.
• DESCRIPTION — the descriptive text associated with the program.
• TYPE_CODE — the coded type, always 'PROGRAM' for rows returned by this view.
• TYPE — the decoded, display-ready form of TYPE_CODE.
• EFFECTIVE_FROM / EFFECTIVE_TO — the date range within which the program is valid.
• MR_STATUS_CODE — the coded status of the maintenance header.
• STATUS — the decoded status value suitable for reporting.

Common Use Cases and Queries

The view is typically consumed when preventive maintenance programs must be listed alongside contract or service data, when validating that a referenced program is active within a given period, or when extracting program definitions for integration into external scheduling or contract systems.

Listing all currently active programs by effective date:

• SELECT id1, name, type, effective_from, effective_to, status FROM okx_pm_programs_v WHERE mr_status_code = 'ACTIVE' ORDER BY name;

Joining a program to its contract or service reference to confirm validity across a specific window:

• SELECT p.id1, p.name, p.status FROM okx_pm_programs_v p WHERE SYSDATE BETWEEN p.effective_from AND NVL(p.effective_to, SYSDATE);

Because the view filters to TYPE_CODE = 'PROGRAM', no additional type predicate is required. Queries should be schema-qualified (APPS.OKX_PM_PROGRAMS_V) when executed outside the APPS context, and access should be granted through the standard OKX responsibility.