Results for “down_time”

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

Overview

OKX_PM_ACTIVITIES_V is a read-only database view owned by the APPS schema and registered under the OKX – Contracts Integration product family. Its documented purpose is to serve as the source for all activities associated with a preventive maintenance program. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 technical stacks, the view acts as a curated, join-ready projection of maintenance activity data originating from the Enterprise Asset Management (eAM) tables, exposed in a form suitable for contracts integration, reporting, and external interfaces.

The object carries a VALID status and is treated as an Oracle Proprietary, Confidential reference object. Because it is a view rather than a base table, it stores no data of its own; every row is derived at query time from the underlying maintenance management tables and lookups. This makes it a low-impact consumption point for downstream OKX-related extraction and integration flows.

Underlying Base Objects

The documented view definition joins AHL_MR_RELATIONSHIPS_APP_V (aliased AMR) to AHL_MR_HEADERS_V (aliased ACT) on the relationship between program and activity. These deployed views resolve to base tables documented in the 12.2.2 metadata as AHL_MR_HEADERS_B, AHL_MR_HEADERS_TL, AHL_MR_RELATIONSHIPS, and the FND_LOOKUP_VALUES synonym, with FND_PROFILE referenced as a package. In this schema:

• AHL_MR_HEADERS_B / AHL_MR_HEADERS_TL — the base and translation tables holding maintenance requirement (MR) header records, including titles and descriptions.
• AHL_MR_RELATIONSHIPS — the relationship table that links a preventive maintenance program header to its associated activity headers.
• FND_LOOKUP_VALUES — supplies decoded lookup meanings such as status text.
• FND_PROFILE — the profile option package, used for standard security and multi-org context resolution.

The join filters activity headers by TYPE_CODE = 'ACTIVITY', ensuring only true activities — not program headers — are surfaced.

Key Columns

The view exposes the following documented columns:

• ID1 (MR_HEADER_ID) — the activity header identifier; with ID2 it forms the composite key ('#' as ID2).
• NAME / DESCRIPTION — the activity title and description from the header (translated) records.
• TYPE_CODE / TYPE — the activity type code and its decoded value.
• EFFECTIVE_FROM / EFFECTIVE_TO — the date range during which the activity is valid.
• MR_STATUS_CODE / STATUS — raw status code and its display status.
• DOWN_TIME — the downtime associated with performing the activity.
• UOM — the unit of measure for downtime.
• PROGRAM_ID (MR_HEADER_ID from AMR) — the owning preventive maintenance program identifier, used to group activities by program.

Common Use Cases and Queries

Typical usages include listing all activities for a given preventive maintenance program, populating contracts integration payloads, and validating effective-dated activity definitions.

• Activities for a specific program:

  SELECT name, description, effective_from, effective_to, status
  FROM   apps.okx_pm_activities_v
  WHERE  program_id = :p_program_id;

• Currently effective activities:

  SELECT name, program_id, down_time, uom
  FROM   apps.okx_pm_activities_v
  WHERE  SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE + 1);

• Activity count by program:

  SELECT program_id, COUNT(*) activity_count
  FROM   apps.okx_pm_activities_v
  GROUP  BY program_id;

Because the view fans out through relationship joins, queries should always filter on PROGRAM_ID or the composite key to avoid redundant relationships.