Search Results offset_duration




Overview
Explore in AI Chat

Overview

OKS_PM_STREAM_LEVELS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKS (Service Contracts) product family. It exposes the contents of the OKS_PM_STREAM_LEVELS base table, which stores preventive maintenance (PM) stream level definitions used by the Service Contracts scheduling engine. A stream level represents a distinct tier within a preventive maintenance program — for example, a sequence of scheduled service events generated for a contract line — and each row captures the timing, recurrence, and scheduling behavior for that tier. The view provides a stable, denormalized read interface so that reports, concurrent programs, and external integrations can query stream level definitions without directly referencing the base table. Because the view is defined with a simple projection over a single synonym and includes ROWID as ROW_ID, it is also usable for certain update-through-view operations and for row-level identification in data migration scripts. Applications and customers commonly search this object when investigating the OFFSET_DURATION column, which controls the lag applied before a scheduled occurrence within a stream level.

Underlying Base Objects

The view is defined entirely over a single referenced object: the synonym OKS_PM_STREAM_LEVELS, which resolves to the APPS.OKS_PM_STREAM_LEVELS table. The view text is a direct SELECT of all significant columns from that synonym, aliased as PML, with no joins, filters, or aggregations applied. Consequently, the view is a one-to-one representation of the base table; row counts and cardinality match exactly, and all DML performed against the base table is immediately visible through the view. There are no dependent views, outer joins, or security predicates embedded in the view definition itself, although standard EBS multi-org and security-group semantics apply through the SECURITY_GROUP_ID column. This simplicity means the view imposes no measurable overhead relative to querying the base table, making it a safe substitute in custom code and ad hoc reporting.

Key Columns

  • ID — Primary key of the stream level row. Used to join to child scheduling and occurrence records.
  • CLE_ID — Identifier of the contract line or entitlement element with which the stream level is associated.
  • DNZ_CHR_ID — Denormalized contract header identifier, useful for filtering by contract without an additional join.
  • ACTIVITY_LINE_ID — Links the stream level to a specific activity or task line in the contract.
  • SEQUENCE_NUMBER — Ordering of the stream level within its parent stream, determining the tier in which occurrences are generated.
  • NUMBER_OF_OCCURENCES — Count of scheduled occurrences to generate for the level.
  • START_DATE / END_DATE — Effective window within which occurrences for the level are scheduled.
  • FREQUENCY / FREQUENCY_UOM — Recurrence interval and its unit of measure (for example, days, weeks, months) for repeated occurrences.
  • OFFSET_DURATION / OFFSET_UOM — The offset applied relative to a reference point before the first or subsequent occurrence is scheduled, together with its unit of measure. This pair is central to the search term that surfaced this view.
  • AUTOSCHEDULE_YN — Flag indicating whether occurrences are scheduled automatically by the concurrent program.
  • OBJECT_VERSION_NUMBER — Optimistic locking token used by the Oracle Application Framework.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, and SECURITY_GROUP_ID, which support auditing and concurrent program traceability.

Common Use Cases and Queries

Typical scenarios include auditing preventive maintenance schedules for a contract, validating offset and frequency configuration after implementation, and extracting stream level data into data warehouses or integration staging tables. The view is frequently joined to contract header and line tables through CLE_ID or DNZ_CHR_ID, and to occurrence tables through ID.

Example: locating stream levels that use a specific offset unit of measure.

  • SELECT cle_id, dnz_chr_id, sequence_number, frequency, frequency_uom, offset_duration, offset_uom, autoschedule_yn FROM oks_pm_stream_levels_v WHERE offset_uom = 'DAY' ORDER BY dnz_chr_id, sequence_number;

Example: listing all stream levels for a particular contract that are configured for automatic scheduling.

  • SELECT id, sequence_number, start_date, end_date, number_of_occurences FROM oks_pm_stream_levels_v WHERE dnz_chr_id = :contract_id AND autoschedule_yn = 'Y';

Because the view contains no joins, it can be used directly in Fast Formula lookups, BI Publisher data models, and custom concurrent programs without concern for the performance penalties associated with more complex service contracts views.