Search Results lock_option_val_rules

Overview

OKL_OPTION_RULES_PUB is the public (PUB) API package for Oracle Enterprise Asset Management and Lease Management contract option rules within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It belongs to the Oracle Knowledge (OKL) product family, which underpins the ETRM (Enterprise Trade and Revenue Management) leasing and contract module. The package exposes the supported, outward-facing interface through which forms, concurrent programs, and custom code create, maintain, validate, and delete option rules and their associated validation rules on contract and lease documents.

The package body follows the standard EBS PL/SQL API architecture. It maintains a private partner package, OKL_OPTION_RULES_PVT, which performs the actual complex-entity processing. The public procedures declared here act as thin wrappers: they set up the API context via FND_API and OKC_API, establish a SAVEPOINT, invoke the corresponding private procedure, evaluate the returned status, and either commit progress or roll back to the savepoint while propagating messages through FND_MSG_PUB. Status codes follow the FND_API conventions (G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXPECTED_ERROR) and raise G_EXC_ERROR or G_EXC_UNEXPECTED_ERROR accordingly. This layered design isolates callers from internal implementation details and preserves a stable public contract across patches and upgrades.

Key Procedures and Functions

The documented interface comprises twenty-three procedures and functions organized into two functional groups: option rules and option validation rules.

• CREATE_OPTION_RULES — Creates a new option rule together with its associated option validation detail records as a single logical transaction.
• UPDATE_OPTION_RULES — Modifies an existing option rule and its dependent validation detail rows.
• VALIDATE_OPTION_RULES — Performs business-rule validation against an option rule structure without persisting changes, enabling callers to pre-check data integrity.
• LOCK_OPTION_RULES — Acquires a logical lock on an option rule record, typically used to enforce concurrency control before an update or delete.
• DELETE_OPTION_RULES — Removes an option rule and its associated child records.
• CREATE_OPTION_VAL_RULES — Creates an option validation rule, the subordinate rule set that governs acceptable option values.
• LOCK_OPTION_VAL_RULES — Obtains a concurrency lock on an option validation rule prior to modification or removal.
• UPDATE_OPTION_VAL_RULES — Modifies the definition of an existing option validation rule.
• DELETE_OPTION_VAL_RULES — Deletes an option validation rule; this is the procedure most closely associated with the user search term "delete_option_val_rules."
• VALIDATE_OPTION_VAL_RULES — Validates an option validation rule's definition and dependencies without committing data.

All routines return standard API status indicators and message information through their OUT parameters, and each participates in the savepoint/rollback pattern described above.

Tables Accessed

The documented ETRM metadata records the table PLITBLM as the table referenced through an APPS synonym. PLITBLM is a standard Oracle EBS temporary/interim storage table used to hold PL/SQL output or error information, and it is referenced by many OKL and OKC API packages for diagnostic and message-handling purposes. Because the public package delegates substantive data manipulation to OKL_OPTION_RULES_PVT, the option rule and option validation rule base tables are read and written indirectly rather than by the public body itself. Callers should treat the private package as the authoritative source for detailed table-level data access behavior.

Usage Notes

OKL_OPTION_RULES_PUB is invoked from Oracle Forms that maintain lease and contract option definitions, and from concurrent programs that process option rules in batch. It is also the supported entry point for custom extensions that must create, update, or delete option rules programmatically. The ETRM metadata indicates the package is referenced by four other packages, confirming its role as a shared service within the OKL module.

Callers should initialize the API layer (for example, by setting the initialization message list parameter and providing a compatible API version), inspect x_return_status before proceeding, and retrieve messages through FND_MSG_PUB. Direct DML against the underlying option rule tables is not supported because it bypasses the validations, locking logic, and complex-entity processing implemented in OKL_OPTION_RULES_PVT. Use DELETE_OPTION_VAL_RULES to remove validation rules, and DELETE_OPTION_RULES when the parent option rule and its children must be removed together.