Search Results oks_pm_schedules_u1

Overview

OKS.OKS_PM_SCHEDULES is a transactional table in the Oracle E-Business Suite Service (OKS) schema that stores generated schedules for preventive maintenance programs and activities. It is populated by the Preventive Maintenance Schedule form and by the concurrent program that instantiates coverage. Schedules are generated from stream levels, and for each record the table stores either a discrete schedule date (SCHEDULE_DATE) or a schedule date range (SCHEDULE_DATE_FROM and SCHEDULE_DATE_TO). Records exist only for instantiated coverage; the table does not hold data for coverage templates. These schedules are consumed downstream by the Advanced Service (AHL) module to generate unit maintenance plans.

Physically, the table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, while all four of its indexes live in APPS_TS_TX_IDX. The documented schema contains 23 columns. From a Data Vault modeling perspective, the mined relationship structure indicates a standalone classification, suggesting this object is best treated as a satellite-like record keyed by its own unique identifier rather than as a hub or link. One foreign key relationship is documented, referencing FND_SECURITY_GROUPS through SECURITY_GROUP_ID, which enforces the multi-tenant security model used throughout the EBS schema.

Key Information Stored

The surrogate primary key is ID, enforced by the unique index OKS_PM_SCHEDULES_U1. This is the only documented unique index, and it is also the primary key candidate for the table.

• ID — Unique identifier for each schedule record; the primary key and the column behind the OKS_PM_SCHEDULES_U1 index the user searched for.
• DNZ_CHR_ID — Unique identifier of the Contract Header, denormalized for query efficiency. Indexed by OKS_PM_SCHEDULES_N1.
• CLE_ID — Unique identifier of the Contract Line to which the schedule applies; the contract line is a coverage line and references OKC_K_LINES_B.ID. Indexed by OKS_PM_SCHEDULES_N2.
• ACTIVITY_LINE_ID — Identifier of the associated activity line; indexed by OKS_PM_SCHEDULES_N3.
• SCH_SEQUENCE — Chronological sequence of schedules for a given stream level.
• SCHEDULE_DATE — The date on which the PM program or activity is to be performed.
• SCHEDULE_DATE_FROM and SCHEDULE_DATE_TO — Start and end of a scheduled date range, used when a discrete date is not applicable.
• STREAM_LINE_ID — Stream line from which the schedule was generated.
• PMA_RULE_ID and PMP_RULE_ID — Rule identifiers linking the schedule to its preventive maintenance activity and program rules.
• OBJECT_VERSION_NUMBER — Optimistic locking counter, set to 1 on insert and incremented on update, used by APIs.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program context columns identifying the process that last touched the row.

The RULE_ID column is documented as obsolete and is no longer used from the 11.5.10 release onward.

Common Use Cases and Queries

Typical reporting questions center on which PM schedules exist for a given contract, contract line, or stream, and when the next service events fall. A simple lookup by the primary key index follows the pattern of the user's original search:

• Retrieve a schedule by its unique identifier: SELECT * FROM OKS.OKS_PM_SCHEDULES WHERE ID = :id;
• List all schedules for a contract header: SELECT * FROM OKS.OKS_PM_SCHEDULES WHERE DNZ_CHR_ID = :chr_id ORDER BY SCH_SEQUENCE;
• List schedules for a coverage line: SELECT * FROM OKS.OKS_PM_SCHEDULES WHERE CLE_ID = :cle_id ORDER BY SCH_SEQUENCE;
• Find activity-level schedules: SELECT * FROM OKS.OKS_PM_SCHEDULES WHERE ACTIVITY_LINE_ID = :line_id;
• Report upcoming or range-based service windows using SCHEDULE_DATE and the SCHEDULE_DATE_FROM / SCHEDULE_DATE_TO pair.

Because schedules feed AHL unit maintenance plan generation, integration and reconciliation queries frequently join OKS_PM_SCHEDULES back to contract header and line tables to confirm that every instantiated coverage line has a corresponding schedule set, and that SCH_SEQUENCE values are contiguous within each stream level.

Related Objects

• OKC_K_LINES_B — Contract lines; OKS_PM_SCHEDULES.CLE_ID references OKC_K_LINES_B.ID.
• OKC_K_HEADERS_B — Contract headers; joined through DNZ_CHR_ID, the denormalized contract header identifier.
• FND_SECURITY_GROUPS — Security group master; the only documented foreign key, via SECURITY_GROUP_ID.
• OKS_PM_SCHEDULES_U1 — The unique index on ID, the primary access path.
• OKS_PM_SCHEDULES_N1, _N2, _N3 — Non-unique indexes on DNZ_CHR_ID, CLE_ID, and ACTIVITY_LINE_ID respectively.
• AHL unit maintenance plan tables — Downstream consumers that use OKS_PM_SCHEDULES rows to generate unit maintenance plans.
• OKS Preventive Maintenance Schedule form and the coverage instantiation program — The originating UI and batch process that populate the table.