Search Results get_rule_information

Overview

OKL_RULE_APIS_PVT is a private PL/SQL package body in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, owned by the APPS schema and classified as a private (PVT) application programming interface. Its purpose is to encapsulate the internal logic that retrieves, evaluates, and formats contract rule information for lease and financing contracts. In ETRM terminology, "rules" are configurable business conditions and validation groups attached to contract headers and lines; they drive defaulting, validation, and eligibility behavior during contract authoring. This package serves as the back-end implementation layer behind the public rule APIs, shielding callers from the underlying queries against OKC rule group views, descriptive flexfield (DFF) metadata, and JTF object registrations.

The package header comment identifies one of its central procedures, Get_Contract_Rgs, as the routine that returns contract rule groups for a contract header (chr_id) or contract line (cle_id). The exported private interface comprises seven documented procedures and functions, and the package is referenced by fifteen other packages across the OKL application, indicating it is a foundational utility in the contract rule subsystem rather than an end-user entry point.

Key Procedures and Functions

• GET_CONTRACT_RGS — Returns the rule groups associated with a contract. When a chr_id is supplied, header-level rule groups are returned; when only a cle_id (or a cle_id together with a dnz_chr_id) is supplied, line-level rule groups are fetched. Results are returned through a rule group table type together with a count.
• GET_CONTRACT_RULES — Retrieves the individual rules belonging to contract rule groups, providing the detail rows that underpin rule evaluation.
• GET_RULE_INFORMATION — This is the procedure most commonly sought by developers searching for rule details. It assembles and returns the defining information for a given rule, including its code, associated flexfield or validation metadata, and display characteristics, so that downstream logic can interpret the rule consistently.
• GET_JTOT_OBJECT — Resolves the JTF object token (JTOT_OBJECT_CODE) registered for a rule, linking rule definitions to the JTF object model used for DFF and extensibility support.
• GET_RULE_DISP_VALUE — Derives the display value for a rule, converting stored rule identifiers into the human-readable values presented in the user interface.
• GET_RULE_SEGMENT_VALUE — Returns the segment-level value for a rule, supporting rules whose conditions are expressed against individual key flexfield segments.

Tables Accessed

The package reads metadata from several data dictionary and flexfield tables via APPS synonyms:

• FND_FLEX_VALIDATION_TABLES and FND_FLEX_VALUE_SETS — used to resolve flexfield value sets and their validation tables so that rule segment values can be validated and displayed correctly.
• OKC_K_LINES_B — the contract line base table, queried to obtain line-level context when rule groups are fetched for a cle_id.
• DBA_TAB_COLUMNS, USER_TAB_COLUMNS, and USER_SYNONYMS — dictionary views used for dynamic column and synonym resolution supporting the DFF fetch logic referenced by the global message constants (OKL_LLA_DFF_FETCH, OKL_LLA_DFF_TABLE_QUERY, OKL_LLA_DFF_VSET_QUERY, OKL_LLA_JTF_OBJ_QUERY).
• DUAL and PLITBLM — utility references for scalar evaluation and PL/SQL table manipulation.

Usage Notes

Because this is a PVT package, it is not intended for direct invocation by external integrations. It is called from within the OKL application by the public rule APIs, contract authoring forms, and the contract validation and defaulting engine. Developers investigating the "get_rule_information" search term should note that GET_RULE_INFORMATION is the internal routine that supplies rule definition data to higher-level APIs. The package is referenced by fifteen other packages, so changes to its signatures or cursor logic can have broad impact across contract rule processing. The version header (120.5) reflects the released code level for the 12.1.1 and 12.2.2 code lines; in 12.2.2 the object resides in the same APPS schema and remains a private implementation detail of the ETRM rule framework.