Search Results create_rule_group

Overview

The APPS.OKL_VP_RULE_PUB package body is a public PL/SQL API within the Oracle Lease and Finance Management (OLFM) module of Oracle E-Business Suite, part of the ETRM (Enterprise Transaction and Relationship Management) application family. It manages rule groups associated with the OKL (Leasing) validation and pricing rule framework. In the OKL data model, a rule group (stored in the OKL_RGPV table and related entities) associates rule definitions with contracts, characteristics, and pricing attributes, forming the configuration backbone that drives lease pricing, validation, and processing behavior. This package exposes a controlled, public interface through which forms, concurrent programs, and custom extensions can create, maintain, and remove rule groups without directly manipulating the underlying base tables. Because it is classified as a PUB API, it is intended as a supported integration point: Oracle preserves the signature and behaviour of public APIs across patch levels, making it safe for customer extension code to call. The header annotation G_GEN_COMMENTS VARCHAR2(1) := 'T' indicates the package participates in standard ETRM comment-generation conventions.

Key Procedures and Functions

The documented public interface comprises the following units:

• CREATE_RULE_GROUP — Creates a new rule group record. This is the entry point most commonly referenced when users search for "create_rule_group" in the OLFM schema. It inserts a new rule group row, populating the identifying and descriptive attributes and stamping the standard WHO columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) as well as the object_version_number used for optimistic locking.
• UPDATE_RULE_GROUP — Modifies the attributes of an existing rule group, including its associated rule definition code, contract line, characteristic, and denormalised characteristic references, along with the flexible attribute columns (attribute_category and attribute1 through attributeN).
• DELETE_RULE_GROUP — Removes a rule group, handling the deletion consistent with the referential rules of the underlying rule-group tables.

Internally, the package body also contains a MIGRATE_RGPV helper (visible in the source excerpt) that merges record-type values from a source record into a target structure, copying ID, WHO audit columns, and the rule-group payload fields such as rgd_code, sat_code, rgp_type, cle_id, chr_id, dnz_chr_id, parent_rgp_id, sfwt_flag, and the descriptive attribute columns. This utility supports the public procedures but is not itself a documented interface.

Tables Accessed

Per the ETRM metadata, the package references PLITBLM via an APPS synonym. PLITBLM is the standard EBS PL/SQL API table that persists message and diagnostic information for a session, and its presence signals that the API performs logging and error-message handling consistent with the EBS API framework. While the documented reference list is limited, the rule-group operations logically read and write the OKL rule-group base table (OKL_RGPV) and its associated rule-definition and characteristic entities reflected in the record structure above (rgd_code, sat_code, chr_id, dnz_chr_id, cle_id).

Usage Notes

This package is typically invoked from OLFM setup and contract-administration forms when users define or change pricing and validation rules, and from concurrent programs that mass-create or migrate rule-group data. Three other packages in the schema reference OKL_VP_RULE_PUB, confirming it sits beneath higher-level APIs that delegate rule-group maintenance to it. Custom code should call the public procedures rather than DML against base tables, relying on the package to apply record validation, WHO auditing, and object-version management. Callers should expect the standard EBS API semantics — a persistent result or message is surfaced via the PLITBLM logging mechanism, and the API should be invoked within a transaction that the caller commits or rolls back. Because the API classification is PUB, it remains a supported integration surface across EBS 12.1.1 and 12.2.2.