Search Results offset_uom




Overview

OKS_PM_STREAM_LEVELS is a Service Contracts (OKS) module table that stores schedule stream level definitions used by the preventive maintenance (PM) scheduling engine. Each row represents one recurrence level or iteration within a stream of scheduled service activities, capturing the timing, frequency, and sequencing attributes that Oracle Service Contracts applies when generating and rolling forward preventive maintenance visits against a contract line or covered service.

The table carries 27 documented columns and is owned by the OKS schema. Its primary key is OKS_PM_STREAM_LEVELS_PK, defined on the ID column, with a supporting unique index OKS_PM_STREAM_LEVELS_U1 also on ID. A foreign key reference from SECURITY_GROUP_ID to FND_SECURITY_GROUPS anchors the table within Oracle's multi-tenant security (MOAC) model, restricting visibility of stream-level rows based on the operating unit context in which they were created.

The heuristic Data Vault classification mined from the foreign key structure is standalone. In modeling terms, this suggests the table behaves as an independent entity rather than as a pure link or satellite, though in practice the presence of transactional audit columns and scheduling attributes means it also functions as a satellite-like store of descriptive state attached to the broader stream/activity hierarchy.

Key Information Stored

The most operationally significant columns include:

  • ID — the surrogate primary key, populated from the OKS_PM_STREAM_LEVELS_PK sequence; also the sole business-key candidate per the unique index.
  • CLE_ID — the contract line identifier to which the stream level is attached.
  • DNZ_CHR_ID — the denormalized contract header identifier, enabling direct joins back to the contract without traversing the line.
  • ACTIVITY_LINE_ID — the parent service activity line for the scheduled occurrence.
  • SEQUENCE_NUMBER — ordering of the level within the stream.
  • NUMBER_OF_OCCURENCES — how many times the level repeats.
  • START_DATE and END_DATE — the effective window for the level.
  • FREQUENCY and FREQUENCY_UOM — recurrence interval and its unit of measure.
  • OFFSET_DURATION and OFFSET_UOM — delay applied before the level fires.
  • AUTOSCHEDULE_YN — flag indicating whether occurrences are auto-generated.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit and optimistic-locking columns.
  • SECURITY_GROUP_ID — MOAC operating unit security reference to FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical usage centers on troubleshooting preventive maintenance schedules and reporting on contract coverage cadence. A common query retrieves all levels for a given contract line:

  • SELECT id, cle_id, sequence_number, frequency, frequency_uom, start_date, end_date FROM oks_pm_stream_levels WHERE cle_id = :cle_id ORDER BY sequence_number;
  • Reconciliation reporting joins DNZ_CHR_ID to the contract header to aggregate occurrences per contract.
  • Diagnostic queries filter on AUTOSCHEDULE_YN = 'Y' to verify which streams are expected to generate automatic visits.
  • Offset and frequency analysis helps validate that schedule generation matches contractual maintenance intervals.

Analysts should always filter by SECURITY_GROUP_ID in multi-org deployments to respect data access policies.

Related Objects

  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for MOAC enforcement.
  • OKS_PM_STREAM_LEVELS parent contract structures recoverable through CLE_ID and DNZ_CHR_ID joins to OKS contract line and header tables.
  • OKS_ACTIVITY_LINES (or equivalent activity line entity) via ACTIVITY_LINE_ID.
  • OKS_PM_SCHEDULES — the downstream generation of actual scheduled occurrences derived from these levels.
  • OKS_K_HEADERS and OKS_K_LINES — contract header and line tables reconciled through DNZ_CHR_ID and CLE_ID respectively.

Together these relationships position OKS_PM_STREAM_LEVELS as the definitional layer between contract commitments and the concrete preventive maintenance visits generated by the scheduling engine.