Search Results std_template_yn

Overview

OKC_RULES_V is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC — Contracts Core product module. It exposes contracting rule definitions and serves as the primary read interface over the rules base table. In EBS 12.1.1 and 12.2.2 the object carries a VALID status, confirming it is a supported, non-obsolete component of the Contracts Core data model. Although the underlying storage object is a "_B" (base) table, OKC_RULES_V is not a translation view in the conventional _B/_TL sense; it is a projection view that flattens the base table into a reporting-friendly form, including a constant SFWT_FLAG column set to 'N' and a NULL TEXT placeholder column.

Because Contracts Core rules drive validation, behavior, and attribute derivation at runtime, this view is the standard entry point for extracting rule metadata for reporting, integration, and troubleshooting. Oracle's ETRM documentation identifies it as the reporting surrogate for the base table, which means most custom SQL should target the view rather than the table directly.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, OKC_RULES_V is defined over a single base object: OKC_RULES_B, referenced through a SYNONYM. The view text confirms a one-to-one projection — every column is sourced from the alias RULB, which is OKC_RULES_B, with no joins to other tables. The only computed elements are the literal 'N' for SFWT_FLAG and a hard-coded NULL for TEXT. Because the view is a straight projection, row counts match the base table exactly, and no aggregation or filtering is applied.

Key Columns

• ID / ROW_ID — Surrogate and ROWID identifiers for each rule row; ROW_ID supports direct row addressing.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Contracts Core framework.
• OBJECT1_ID1, OBJECT2_ID1, OBJECT3_ID1 (and the parallel _ID2 columns) — Foreign-key references identifying the rule's subject and target entities.
• JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, JTOT_OBJECT3_CODE — Object type codes that classify the objects referenced by the ID columns.
• DNZ_CHR_ID — Contract (header) identifier to which the rule belongs.
• RGP_ID — Reference to the rule group, positioning the rule within its logical set.
• PRIORITY — Execution precedence for rule evaluation.
• STD_TEMPLATE_YN, WARN_YN — Flags indicating whether the rule is a standard template and whether it raises only a warning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — DFF (descriptive flexfield) columns for customer-defined rule attributes.
• RULE_INFORMATION_CATEGORY and RULE_INFORMATION1–13 — Additional rule-parameter flexfield values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes listing all rules for a contract, auditing template rules by priority, and reporting DFF attribute assignments. Because the view is unfiltered, always constrain by DNZ_CHR_ID or RGP_ID to avoid full scans.

The following query lists rule identifiers, priority, and source object types for a given contract:

SELECT ID, DNZ_CHR_ID, RGP_ID, PRIORITY,
       JTOT_OBJECT1_CODE, OBJECT1_ID1,
       STD_TEMPLATE_YN, WARN_YN
FROM   OKC_RULES_V
WHERE  DNZ_CHR_ID = :contract_id
ORDER  BY PRIORITY;

To audit warning-only template rules:

SELECT ID, RGP_ID, PRIORITY, COMMENTS
FROM   OKC_RULES_V
WHERE  STD_TEMPLATE_YN = 'Y'
AND    WARN_YN = 'Y';