Search Results oks_pm_schedules




Overview
Explore in AI Chat

Overview

OKS_PM_SCHEDULES is a Service Contracts (OKS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the schedule details of a Preventive Maintenance (PM) program that is attached to a coverage. In practical terms, the table records the individual dated occurrences generated for a PM program, capturing when each occurrence falls due and how it links back to the owning service contract line, coverage, and PM rule set. This makes it a transactional detail table sitting beneath the preventive maintenance rule definitions in the Service Contracts schema, owned by the OKS schema and validated as VALID.

The ETRM metadata offers a heuristic Data Vault classification of standalone, derived from its foreign-key structure. As a modeling suggestion, this indicates the table is not modelled as a classic hub or link with broad multi-parent integration; it behaves more like a detail or satellite-style record keyed by its own surrogate identifier, with only a limited outbound reference to FND_SECURITY_GROUPS. Any Data Vault design should therefore treat OKS_PM_SCHEDULES as a dependent detail set rather than a central integration point.

Key Information Stored

The documented physical schema contains 23 columns. The primary key is OKS_PM_SCHEDULES_PK on the ID column, and there is a unique index OKS_PM_SCHEDULES_U1 also on ID, making ID the surrogate primary key and the confirmed business-key candidate. The most significant columns include:

Common Use Cases and Queries

Typical usage centres on reporting and validating PM schedules attached to service contracts. A frequently used pattern joins schedule rows back to the coverage or contract identifier and filters by effective date window:

  • Listing all schedules for a coverage: SELECT id, cle_id, sch_sequence, schedule_date FROM oks_pm_schedules WHERE cle_id = :cle_id ORDER BY sch_sequence;
  • Finding schedules due within a date range: filter on SCHEDULE_DATE between SCHEDULE_DATE_FROM and SCHEDULE_DATE_TO or on a specific window.
  • Auditing schedule generation by concurrent request using REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.
  • Security-scoped extracts filtering on SECURITY_GROUP_ID to restrict results to the caller's security group.

These queries support preventive maintenance planning reports, contract billing verification, and reconciliation between generated PM visits and the underlying coverage.

Related Objects

The documented foreign key indicates the following primary relationship, along with the natural business joins implied by the rule and coverage identifiers:

  • FND_SECURITY_GROUPS — joined via OKS_PM_SCHEDULES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • OKS_PM_RULES / PM rule definition tables — joined via RULE_ID, PMA_RULE_ID, and PMP_RULE_ID to retrieve the governing PM program rules.
  • OKS_COVERAGES (coverage headers/lines) — joined via CLE_ID to resolve the owning coverage.
  • Service contract header/line tables — linked through DNZ_CHR_ID and the activity/stream line identifiers.
  • OKS_ACTIVITY_LINES and stream line tables — joined via ACTIVITY_LINE_ID and STREAM_LINE_ID.

Because the metadata classifies the table as standalone, no additional documented parent relationships exist beyond the security group reference; related objects above reflect the business-key joins implied by the column set.