Results for “oks_pm_stream_levels_u1”

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

Overview

OKS.OKS_PM_STREAM_LEVELS is a transactional table in the Oracle E-Business Suite Service (OKS) schema that stores stream level definitions for preventive maintenance programs and activities. Preventive maintenance in Oracle Service Contracts and Depot Repair is driven by a coverage model in which a program (or activity within a program) is decomposed into one or more streams. Each stream level row defines the cadence and sequencing rules from which individual service schedules are generated.

The table is populated by the Preventive Maintenance Schedule form and by the concurrent program that instantiates coverage. Stream levels are the mechanism that drives schedule generation; during coverage instantiation the start and end dates are written to the row, which is why START_DATE and END_DATE are meaningful only for instantiated coverage and not for the template-level definition. The AUTOSCHEDULE_YN flag determines whether the resulting schedule is generated automatically ('Y') or defined manually ('N'). The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as standalone, and the FK structure supports a heuristic hub or satellite classification rather than a link; the absence of relationships to other business entities beyond the security group reference suggests the table is best modeled as a satellite attached to a preventive maintenance hub keyed by ID.

Key Information Stored

The table contains 27 documented columns. The most significant are:

• ID — surrogate primary key, enforced by the unique index OKS_PM_STREAM_LEVELS_U1 and the primary key constraint OKS_PM_STREAM_LEVELS_PK.
• CLE_ID — coverage/contract line element identifier that anchors the stream level; indexed by OKS_PM_STREAM_LEVELS_N2.
• DNZ_CHR_ID — denial/characteristic reference used in the preventive maintenance denormalization model; indexed by OKS_PM_STREAM_LEVELS_N1.
• ACTIVITY_LINE_ID — the program activity line to which the stream level belongs; indexed by OKS_PM_STREAM_LEVELS_N3.
• SEQUENCE_NUMBER — ordering of stream levels within the program.
• NUMBER_OF_OCCURENCES — the count of occurrences to generate for the stream.
• START_DATE and END_DATE — the effective window, applicable only once coverage is instantiated.
• FREQUENCY and FREQUENCY_UOM — the interval quantity and unit of measure governing schedule recurrence.
• OFFSET_DURATION and OFFSET_UOM — the lead/lag applied before the first generated occurrence.
• AUTOSCHEDULE_YN — controls automatic versus manual schedule definition.
• OBJECT_VERSION_NUMBER — optimistic locking column maintained by the ORM layer.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization data security.
• ORIG_SYSTEM_ID1, ORIG_SYSTEM_REFERENCE1, ORIG_SYSTEM_SOURCE_CODE — source-system lineage for data migrated from external or legacy systems.

Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, together with the concurrent program columns PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID, complete the standard EBS WHO and program metadata.

Common Use Cases and Queries

The most frequent access path is retrieval of stream levels for a given activity line or coverage element, for example to reconstruct the preventive maintenance schedule for a service contract line. A representative query is:

• SELECT id, activity_line_id, sequence_number, frequency, frequency_uom, autoschedule_yn FROM oks.oks_pm_stream_levels WHERE activity_line_id = :p_activity_line_id ORDER BY sequence_number;
• SELECT id, cle_id, start_date, end_date, number_of_occurences FROM oks.oks_pm_stream_levels WHERE cle_id = :p_cle_id;
• Reporting on automatic versus manual scheduling: SELECT autoschedule_yn, COUNT(*) FROM oks.oks_pm_stream_levels GROUP BY autoschedule_yn;
• Reconciling migrated data via ORIG_SYSTEM_REFERENCE1 and ORIG_SYSTEM_SOURCE_CODE against the source system.

Typical scenarios include troubleshooting why a preventive maintenance schedule was not generated (inspect START_DATE, END_DATE, and AUTOSCHEDULE_YN), auditing frequency drift after a program change, and building reconciliation reports between the stream level template and instantiated coverage.

Related Objects

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; the sole documented foreign key relationship.
• The preventive maintenance program and activity tables in the OKS schema that own ACTIVITY_LINE_ID and DNZ_CHR_ID; these are the natural parent entities for the stream level rows.
• The coverage instantiation concurrent program in OKS, which inserts rows and populates START_DATE and END_DATE.
• The Preventive Maintenance Schedule form, the primary user-facing maintenance point for this table.
• The coverage and coverage line element tables in OKS, joined through CLE_ID.

Because the table is classified as standalone within the documented FK structure, integrators should treat ID as the authoritative object identifier and rely on the three non-unique indexes on DNZ_CHR_ID, CLE_ID, and ACTIVITY_LINE_ID for the principal join and filter predicates.