Search Results validate_rg_mode_pty_role

Overview

OKC_RULE_PUB is the public API package for the Oracle E-Business Suite Contracts (OKC) rules engine, distributed in the APPS schema as an AUTHID CURRENT_USER package (header source OKCPRULS.pls). It exposes the externally supported interface for creating, maintaining, validating, and logically deleting contract rule definitions and the associated rule configuration entities used by Oracle Contracts and its integrated modules. Application logic for these operations resides in the private package OKC_RULE_PVT; OKC_RULE_PUB re-declares the private record and table subtype definitions (rulv, rgpv, rmpv, ctiv, rilv) and wraps the private entry points, adding standard concurrent-processing safeguards such as row locking, validation, message-stack handling, and error constants inherited from OKC_API. In the ETRM 12.2.2 repository the package is classified as a PUB API and is referenced by 28 other packages, which confirms its role as a shared integration point rather than a form-only utility.

Key Procedures and Functions

The package documents 79 procedures and functions. The principal groups are:

• Rule maintenance: CREATE_RULE, UPDATE_RULE, VALIDATE_RULE, DELETE_RULE, and LOCK_RULE manage rows in the contract rule definition, enforcing attribute validation and optimistic locking before any DML is applied.
• Rule group maintenance: CREATE_RULE_GROUP, UPDATE_RULE_GROUP, DELETE_RULE_GROUP, LOCK_RULE_GROUP, and VALIDATE_RULE_GROUP perform the equivalent lifecycle operations for rule groups that organize rule definitions.
• Rule group mode, party, and role assignments: CREATE_RG_MODE_PTY_ROLE, UPDATE_RG_MODE_PTY_ROLE, DELETE_RG_MODE_PTY_ROLE, LOCK_RG_MODE_PTY_ROLE, and VALIDATE_RG_MODE_PTY_ROLE maintain the association between a rule group, its operating mode, the responsible party, and the party role. DELETE_RG_MODE_PTY_ROLE, the procedure targeted by the search term, logically removes one such assignment after validating that the referenced rule group context remains consistent.
• Cover time maintenance: CREATE_COVER_TIME, UPDATE_COVER_TIME, DELETE_COVER_TIME, LOCK_COVER_TIME, and VALIDATE_COVER_TIME manage coverage time windows attached to contract rules.

Each family follows the same pattern: a lock routine secures the row for update, a validate routine checks mandatory and reference values, and the create/update/delete routines raise the standard OKC_API messages (for example G_RECORD_LOGICALLY_DELETED, G_REQUIRED_VALUE, or G_UNEXPECTED_ERROR) on the message stack for the calling form or program to display.

Tables Accessed

The package operates on the rule tables through APPS synonyms, principally OKC_RULE_DEFS_B for the rule definition header, and OKC_K_LINES_B where contract line context is required. Validation of descriptive flexfield definitions and value sets is performed against FND_DESCR_FLEX_CONTEXTS and FND_FLEX_VALIDATION_TABLES. DBMS_TRANSACTION is used for savepoint and read-consistency handling, and PLITBLM supports the standard EBS table-handler pattern for array DML. All DML is subject to the WHO columns and logical-delete conventions enforced by OKC_API.

Usage Notes

OKC_RULE_PUB is normally invoked from the Contracts setup and authoring forms, from concurrent programs that seed or migrate rule configuration, and from custom PL/SQL that must modify rules without bypassing validation and locking. Callers initialize the global record structures, invoke the LOCK routine for the target row, the VALIDATE routine for the changed attributes, and then the CREATE, UPDATE, or DELETE routine, checking the returned status and reading the message stack. Direct DML against the underlying OKC rule tables is not supported; the public API is the sanctioned integration path and its behavior is consistent across EBS 12.1.1 and 12.2.2.