Results for “sch_sequence”

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

Overview

OKS_PM_SCHEDULES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKS – Service Contracts module. Its documented purpose is to support the Preventive Maintenance (PM) schedule form, presenting the schedule records that drive planned service activities against a contract. The view is classified as VALID in both ETRM 12.1.1 and 12.2.2, and is exposed to reporting, integration, and extension layers through the standard APPS synonym. Because the view reproduces the base table columns with no joining or aggregation logic, it serves primarily as a stable, form-facing presentation layer rather than as a transformed reporting structure. Users searching on schedule_date are typically seeking the planned execution date of a PM schedule and the range boundaries that accompany it.

Underlying Base Objects

The view is defined over a single documented base object: OKS_PM_SCHEDULES, referenced in the view text through the alias PMS and exposed as a synonym. The definition is a straightforward projection of the base table, selecting ROWID as ROW_ID together with the complete set of operational and who-columns. No joins, unions, or filters are applied, so the view carries one row per PM schedule record held in the underlying table. All DML performed by the PM schedule form against this view resolves directly to OKS_PM_SCHEDULES, and the presence of OBJECT_VERSION_NUMBER confirms that the underlying entity is enabled for optimistic locking through the standard EBS framework.

Key Columns

• ID – Primary identifier of the PM schedule record.
• RULE_ID / PMA_RULE_ID / PMP_RULE_ID – References to the governing PM rules, including the PMA and PMP rule identifiers that determine schedule generation behaviour.
• DNZ_CHR_ID – The contract header identifier, linking the schedule to its service contract.
• CLE_ID – Contract line identifier associated with the schedule.
• SCH_SEQUENCE – Sequence number controlling the ordering of schedule entries within a rule or line.
• SCHEDULE_DATE – The planned date of the PM occurrence; this is the column most frequently used in date-range reporting.
• SCHEDULE_DATE_FROM / SCHEDULE_DATE_TO – The tolerance window bounding the schedule date, defining the acceptable interval in which the PM activity may be performed.
• ACTIVITY_LINE_ID / STREAM_LINE_ID – Links to the activity and stream lines that carry the billable or serviceable detail.
• OBJECT_VERSION_NUMBER – Optimistic locking token used by the form to detect concurrent updates.
• Standard EBS audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the concurrent program columns PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, plus SECURITY_GROUP_ID.

Common Use Cases and Queries

The principal use case is date-driven reporting on preventive maintenance commitments, such as identifying all schedules falling due within a given period, or reconciling PM schedules against contract lines and rule definitions. The view is also a convenient integration source for external scheduling systems that consume planned maintenance dates without needing to address the base table directly.

Example query listing upcoming PM schedules for a contract:

SELECT id, dnz_chr_id, cle_id, sch_sequence,
       schedule_date, schedule_date_from, schedule_date_to
FROM   apps.oks_pm_schedules_v
WHERE  schedule_date BETWEEN :p_from_date AND :p_to_date
AND    dnz_chr_id = :p_contract_id
ORDER  BY schedule_date, sch_sequence;

Example query focusing solely on the requested column, returning the schedule date for a given rule:

SELECT id, rule_id, schedule_date, object_version_number
FROM   apps.oks_pm_schedules_v
WHERE  rule_id = :p_rule_id;

Because the view is a direct projection, the DATE and DATE_FROM/DATE_TO columns retain the base table's data type and can be compared with standard Oracle date arithmetic without conversion. Filtering on SCHEDULE_DATE is index-assisted only where the underlying OKS_PM_SCHEDULES table provides a supporting index; for high-volume extracts, joining to OKS_PM_RULES or the contract header tables remains the recommended pattern.