Results for “optional_yn”

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

Overview

OKC_RG_ROLE_DEFS is a Contracts Core (OKC) table that defines which roles may act as either the subject or the object of a rule group attached to a specific contract subclass. In the Oracle E-Business Suite 12.1.1 and 12.2.2 Contracts Core data model, rule groups are the mechanism by which contract terms, clauses, and conditional processing are bound to subclasses; OKC_RG_ROLE_DEFS provides the role-level scoping that determines which party roles participate in those rules. Records in this table constitute the operational bridge between a subclass-level rule group definition and the individual contract roles that are permitted to serve as its subject or object.

Under a heuristic Data Vault classification mined from its foreign key structure, this object is satellite-leaning. It carries descriptive attributes (role designation, optionality, access level, and DFF columns) that qualify a parent rule group assignment, rather than acting as a standalone hub of business keys or a pure many-to-many link. Modelers should treat it as a dependent satellite keyed to the subclass rule group and subclass role combinations.

Key Information Stored

The table is documented with 30 physical columns in the 12.2.2 schema. Its most significant attributes include:

• ID — the surrogate primary key, enforced by OKC_RG_ROLE_DEFS_PK. Also participates in unique index OKC_RG_ROLE_DEFS_U1 (ID, ZD_EDITION_NAME), which supports the editioning model in 12.2.2.
• SRD_ID — foreign key to OKC_SUBCLASS_RG_DEFS; identifies the subclass rule group definition that this role entry qualifies.
• SRE_ID — foreign key to OKC_SUBCLASS_ROLES; identifies the contract role being scoped to the rule group.
• SUBJECT_OBJECT_FLAG — indicates whether the role functions as the subject or the object within the rule group's evaluation context.
• OPTIONAL_YN — controls whether the role assignment is mandatory or optional for the rule group.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-org/security partitioning.
• ACCESS_LEVEL — governs the accessibility of the record within the access control model.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) segment columns.
• ZD_EDITION_NAME — the editioning column supporting the 12.2.2 Edition-Based Redefinition architecture.

The business-key candidate is documented through OKC_RG_ROLE_DEFS_U2 (SRD_ID, SRE_ID, ZD_EDITION_NAME), confirming that a given rule group and role combination must be unique per edition.

Common Use Cases and Queries

Reporting and diagnostics on rule group role configurations typically join this table to its parent definitions. A representative query retrieves the roles tied to a subclass rule group:

• List all roles for a rule group: SELECT r.SRD_ID, r.SRE_ID, r.SUBJECT_OBJECT_FLAG, r.OPTIONAL_YN FROM OKC_RG_ROLE_DEFS r WHERE r.SRD_ID = :srd_id.
• Distinguish subject versus object roles: filter on SUBJECT_OBJECT_FLAG to report which roles drive rule subject evaluation versus those acting as objects.
• Identify optional role assignments: WHERE OPTIONAL_YN = 'Y' to audit non-mandatory role scoping.
• Reconcile subclass-level rule configuration against the role master by joining OKC_SUBCLASS_ROLES on SRE_ID.
• Security-partitioned extracts restrict output by SECURITY_GROUP_ID and ACCESS_LEVEL for org-specific reporting.

Because rule evaluation drives contract clause and term generation, discrepancies in this table commonly explain unexpected rule behavior, missing subject roles, or improperly scoped contract conditions.

Related Objects

• OKC_SUBCLASS_RG_DEFS — parent rule group definition; joined via OKC_RG_ROLE_DEFS.SRD_ID.
• OKC_SUBCLASS_ROLES — role master for the subclass; joined via OKC_RG_ROLE_DEFS.SRE_ID.
• OKC_RG_PARTY_ROLES — child table referencing this table via OKC_RG_PARTY_ROLES.RRD_ID; holds party role assignments tied to these rule group role definitions.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security partitioning.
• OKC_RG_ROLE_DEFS_PK / OKC_RG_ROLE_DEFS_U1 / OKC_RG_ROLE_DEFS_U2 — the primary and unique indexes governing identity and editioning uniqueness.