Search Results program_id1

Overview

OKS_PM_PROGRAM_V is an Oracle E-Business Suite view owned by the APPS schema within the Service Contracts (OKS) module. Its stated purpose, per the ETRM metadata, is to supply the Preventive Maintenance (PM) schedule form with PM program rule information. The view acts as a denormalized presentation layer over the Contracts Core rule tables OKC_RULE_GROUPS_B and OKC_RULES_B, exposing rule records that belong to the PM program category in a column layout directly consumable by the corresponding Oracle Forms block.

Because it is a view rather than a table, it holds no data of its own; it is compiled against the underlying rule and rule-group structures and is marked VALID in the dictionary. It is documented in both ETRM 12.1.1 and 12.2.2, and its definition is identical across those releases. Its practical role in EBS reporting and integration is to provide a stable, single-object access point for PM program rules, allowing reports, forms, and interfaces to retrieve program identifiers and confirmation/scheduling flags without joining the Contracts Core rule tables themselves.

Underlying Base Objects

The view is defined over two synonym base objects, both documented in the metadata as referenced objects:

• OKC_RULES_B — aliased as RULES, this is the Contracts Core rules base table. Every row in the view corresponds to one rule row filtered by RULE_INFORMATION_CATEGORY = 'PMP' and joined to a qualifying rule group.
• OKC_RULE_GROUPS_B — aliased as RGP, the rule-groups base table. The join is RULES.RGP_ID = RGP.ID, and the group is restricted by the literal predicate RGP.RGD_CODE = 'SVC_K'.

The view therefore presents a constrained projection: only PMP-category rules attached to rule groups whose group code is SVC_K. It also exposes the internal row identifier (RULES.ROWID as ROW_ID) and the object version number, supporting forms-based concurrent update checking.

Key Columns

• ROW_ID — the ROWID of the underlying OKC_RULES_B row; used by the form for row identity.
• PROGRAM_RULE_ID — RULES.ID, the primary key of the underlying rule record.
• OBJECT_VERSION_NUMBER — optimistic locking column propagated from the rule.
• CONFIRMATION_REQUIRED — RULE_INFORMATION1, indicating whether confirmation is required for the PM program rule.
• SCHEDULE_EXISTS — RULE_INFORMATION2, indicating whether a schedule already exists.
• PROGRAM_ID1 — OBJECT1_ID1, first program identifier.
• PROGRAM_ID2 — OBJECT1_ID2, the second program identifier. This column is the target of the user's search term "program_id2" and typically carries the PM program reference used to link the rule to the corresponding program definition.
• CLE_ID — from the rule group, the contract line/entity identifier context for the rule.
• DNZ_CHR_ID — the denormalized contract header identifier associated with the rule group.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, all sourced from OKC_RULES_B.

Common Use Cases and Queries

The principal consumer is the PM schedule form, which queries the view by program rule or by PROGRAM_ID2 to populate PM program rule information. Reporting and interface routines use the same columns to extract confirmation and schedule flags for a given program.

Retrieving the PM rules for a specific second program identifier:

• SELECT PROGRAM_RULE_ID, PROGRAM_ID1, PROGRAM_ID2, CONFIRMATION_REQUIRED, SCHEDULE_EXISTS FROM OKS_PM_PROGRAM_V WHERE PROGRAM_ID2 = :program_id2;
• SELECT PROGRAM_RULE_ID, CLE_ID, DNZ_CHR_ID, CONFIRMATION_REQUIRED FROM OKS_PM_PROGRAM_V WHERE CLE_ID = :cle_id;
• SELECT COUNT(*) FROM OKS_PM_PROGRAM_V WHERE SCHEDULE_EXISTS = 'Y';

Because the view already restricts to SVC_K rule groups in the PMP information category, callers do not need to replicate those predicates, which reduces the risk of omitting the category filter in custom code.