Search Results oks_pm_activities_pk

Overview

OKS_PM_ACTIVITIES is a Service Contracts (OKS) module table that stores Preventive Maintenance (PM) activity definitions associated with contract coverage lines. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the persistence layer for the activities that drive scheduled preventive maintenance programs on covered customer assets. Each row represents an activity record tied to a coverage line (CLE_ID) and a service contract (DNZ_CHR_ID), and carries flags that determine selection behavior, confirmation requirements, and scheduling status.

From a heuristic Data Vault classification (mined from its foreign-key structure), the table is classified as standalone. This indicates that, structurally, it does not participate in a dense web of parent dependencies; the only documented foreign key path is to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. A Data Vault modeler would therefore suggest treating OKS_PM_ACTIVITIES as a self-contained record set rather than a central hub or an interpolated link, with most of its meaningful business attributes retained at row level.

Key Information Stored

The table contains 21 documented columns. The most operationally significant are:

• ID — Surrogate primary key, enforced by OKS_PM_ACTIVITIES_PK and reinforced by the unique index OKS_PM_ACTIVITIES_U1. This is the technical identifier used for referential joins within the OKS schema.
• CLE_ID — Coverage line identifier; the parent coverage record under which the PM activity is defined.
• DNZ_CHR_ID — Service contract identifier; associates the activity with the governing contract header.
• ACTIVITY_ID — Business activity identifier used to resolve the underlying maintenance activity definition.
• SELECT_YN — Indicates whether the activity is selected for the coverage line.
• CONF_REQ_YN — Flag indicating whether confirmation is required when the activity is performed.
• SCH_EXISTS_YN — Indicates whether a schedule already exists for this activity.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context columns, used to trace which program created or last updated the row.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF framework to detect concurrent updates.
• SECURITY_GROUP_ID — Multi-tenant/security partition reference to FND_SECURITY_GROUPS.
• ORIG_SYSTEM_ID1, ORIG_SYSTEM_REFERENCE1, ORIG_SYSTEM_SOURCE_CODE — Origin system identifiers used for data migration and cross-system reconciliation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The business-key candidate is ID, as reflected in the unique index OKS_PM_ACTIVITIES_U1; other columns are descriptive or reference attributes rather than alternate keys.

Common Use Cases and Queries

Typical reporting scenarios include listing all PM activities for a given service contract, identifying activities awaiting scheduling, and auditing confirmation requirements across coverage lines.

• Enumerate activities for a contract: SELECT ID, CLE_ID, ACTIVITY_ID, SELECT_YN, CONF_REQ_YN, SCH_EXISTS_YN FROM OKS.OKS_PM_ACTIVITIES WHERE DNZ_CHR_ID = :contract_id;
• Find activities lacking schedules: SELECT * FROM OKS.OKS_PM_ACTIVITIES WHERE SCH_EXISTS_YN = 'N' AND SELECT_YN = 'Y';
• Trace concurrent program provenance: SELECT ID, PROGRAM_ID, REQUEST_ID, PROGRAM_UPDATE_DATE FROM OKS.OKS_PM_ACTIVITIES WHERE PROGRAM_APPLICATION_ID = :app_id;
• Audit recent changes: order by LAST_UPDATE_DATE and filter by LAST_UPDATED_BY.

These queries support preventive maintenance dashboards, contract coverage audits, and reconciliation of migrated activity data using the ORIG_SYSTEM_* columns.

Related Objects

• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID; the only documented foreign-key relationship.
• OKS_COVERAGE_LINES (referenced conceptually via CLE_ID) — Parent coverage line for each activity.
• OKS_CONTRACTS / contract header structures (referenced via DNZ_CHR_ID) — Governing service contract.
• OKS_PM_SCHEDULES — Downstream schedule records derived from activities.
• OKS_ACTIVITIES — Business activity definitions resolved through ACTIVITY_ID.
• FND_CONCURRENT_REQUESTS — Resolves REQUEST_ID for program diagnostics.

Together these objects form the preventive maintenance layer within Oracle Service Contracts, with OKS_PM_ACTIVITIES serving as the central activity-to-coverage association store.