Search Results program_id1

Overview

APPS.OKS_PM_PROGRAM_V is a service-contract program view in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents configuration data for service programs — the entitlement rules that determine which services a customer is eligible for, whether confirmation is required before delivery, and whether a schedule of visits or deliverables exists. The view is a denormalized projection over the OKC rule framework, joining rule group headers to their individual rule lines so that program-level attributes are exposed in a single, query-friendly structure.

The view is defined by a fixed filter on the rule group code RGD_CODE = 'SVC_K', meaning it returns only those rule groups classified as service programs, and on RULE_INFORMATION_CATEGORY = 'PMP' (Program Management Program), which restricts the rule lines to the attribute set that carries program-specific information. Because the underlying objects are the transactional rule tables, the view reflects current committed data and does not introduce its own storage. It is typically consumed by service contract reporting, order-capture validation logic, and integration interfaces that need to evaluate program entitlement without navigating the full OKC rule model.

Underlying Base Objects

The documented definition references two base objects, both exposed in APPS as synonyms:

• OKC_RULE_GROUPS_B — the rule group header table, aliased RGP. It supplies the group identifiers ID, CLE_ID (contract line entity), and DNZ_CHR_ID (the owning contract or document header).
• OKC_RULES_B — the rule line table, aliased RULES. It supplies the rule identifiers, the object version number, the two rule information attributes, and the standard WHO audit columns.

The join is rules.rgp_id = rgp.id, an inner join that keeps only rules belonging to a qualifying group. Rows carry ROWID as ROW_ID, a construct common in EBS views to support updateable, key-preserved projections for forms-based or programmatic maintenance.

Key Columns

• PROGRAM_RULE_ID (rules.id) — primary identifier of the individual program rule line.
• PROGRAM_ID1, PROGRAM_ID2 (rules.object1_id1, rules.object1_id2) — the two-part foreign key to the program object being configured, typically the program header and version or line reference.
• CLE_ID (rgp.cle_id) — the contract line to which the rule group is attached, useful for isolating programs by contract structure.
• DNZ_CHR_ID (rgp.dnz_chr_id) — the contract or document header identifier, enabling joins to contract headers for customer and status lookups.
• CONFIRMATION_REQUIRED (rules.rule_information1) — flag indicating whether the customer must confirm the program before it is applied.
• SCHEDULE_EXISTS (rules.rule_information2) — flag indicating whether a service schedule is defined for the program.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from OKC_RULES_B.

Common Use Cases and Queries

The view is most often queried to report or validate service program entitlement per contract, and to join program data to contract headers and customers.

List all programs for a given contract header:

SELECT program_rule_id, program_id1, program_id2,
       confirmation_required, schedule_exists
FROM   apps.oks_pm_program_v
WHERE  dnz_chr_id = :p_contract_id;

Identify programs requiring confirmation:

SELECT p.program_rule_id, p.dnz_chr_id, p.cle_id
FROM   apps.oks_pm_program_v p
WHERE  p.confirmation_required = 'Y';

Join to the contract header for customer context:

SELECT p.program_rule_id, h.customer_id, p.confirmation_required
FROM   apps.oks_pm_program_v p,
       apps.okc_k_headers_b h
WHERE  p.dnz_chr_id = h.id;

Because the view exposes ROW_ID and OBJECT_VERSION_NUMBER, it is also suitable for tier-two maintenance screens. For bulk integration loads, restrict extracts by LAST_UPDATE_DATE to capture incremental changes efficiently.