Search Results lock_cover_time

Overview

OKC_RULE_PVT is a private (PVT classification) PL/SQL package in the APPS schema that implements the low-level business logic for the rule and rule group entities within Oracle Contracts (OKC), part of the Oracle E-Business Suite Advanced Procurement and Contracts family. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking session rather than the definer, which is typical of generated entity-handler code produced by the Oracle Application Object Library entity object framework.

Rather than exposing a public API surface, OKC_RULE_PVT acts as the internal engine behind the corresponding public packages (notably OKC_RULE_PUB and OKC_RULE_GROUP_PUB). It encapsulates the insert, update, delete, lock, and validation behaviour for contract rules, rule groups, rule-group mode/party-role associations, and cover times. Its role is to centralise record-level validation, concurrency checking, and DML for the underlying base tables so that callers operate against a consistent, reusable interface.

Key Procedures and Functions

The documented 26 subprograms follow a consistent CRUD-plus-lock-plus-validate pattern across five logical entities:

• Rules — CREATE_RULE, UPDATE_RULE, DELETE_RULE, LOCK_RULE, and VALIDATE_RULE manage individual contract rules, including the lock-check that detects concurrent modification and the validation that enforces the rule's business constraints.
• Rule Groups — CREATE_RULE_GROUP, UPDATE_RULE_GROUP, DELETE_RULE_GROUP, LOCK_RULE_GROUP, and VALIDATE_RULE_GROUP provide the equivalent lifecycle for grouping rules together.
• Rule Group Mode / Party Role — 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, an applicable mode, and a party role.
• Cover Time — CREATE_COVER_TIME, UPDATE_COVER_TIME, DELETE_COVER_TIME, LOCK_COVER_TIME, and VALIDATE_COVER_TIME handle the cover-time definition attached to rules. This is the entity referenced by the search term validate_cover_time: the procedure performs server-side validation of a cover-time record, returning the standard FND message tokens on failure.

The package also declares global message constants (such as G_REQUIRED_VALUE, G_INVALID_VALUE, G_RECORD_LOGICALLY_DELETED, and G_UNEXPECTED_ERROR) inherited from OKC_API, and defines record/table subtype aliases (rulv, rgpv, rmpv, ctiv, rilv) sourced from sibling private packages to standardise the data structures passed between these routines.

Tables Accessed

The package reads and writes the following base tables via APPS synonyms:

• OKC_RULES_B — the base table holding contract rule definitions; the target of the rule CRUD operations.
• OKC_RULE_DEFS_B — stores rule definition details referenced during rule creation and validation.
• OKC_RULE_GROUPS_B — the base table for rule groups, accessed by the rule-group operations.
• OKC_K_HEADERS_B — the contract header table, providing the owning contract context for rules, groups, and cover times.
• PLITBLM — a framework helper table used in conjunction with the generated entity-handler logic.

Usage Notes

Because OKC_RULE_PVT is classified as a private package, it is not intended for direct invocation by end users or customer extensions. It is normally called through the corresponding public packages (OKC_RULE_PUB and related APIs), which wrap the private routines with the appropriate security and error-handling layers. In the standard application flow, the Contracts forms (for example, the contract authoring and rule maintenance forms) and any concurrent programs that process rules or cover times drive the public API, which in turn delegates to these private procedures. The package is referenced by two other packages in the documented metadata, confirming its role as a shared internal dependency. Custom code should avoid calling OKC_RULE_PVT directly; developers requiring rule or cover-time logic should use the supported public API instead, since private signatures are subject to change between releases and are not covered by Oracle's public API compatibility guarantees.