Search Results validate_territory

Overview

OKL_EC_EVALUATE_PVT is a private PL/SQL package that forms part of the Oracle Lease and Finance Management (OKL) evaluation engine within Oracle E-Business Suite. Its principal business function is to evaluate eligibility criteria defined for lease and finance transactions. The package compares transaction data against configured criterion sets and criterion values, applies adjustment factors, and returns eligibility decisions together with user-facing messages. As a PVT (private) package, it is not intended for direct invocation by external consumers; it is called by other OKL packages that expose the public evaluation APIs.

The package body source shows a supporting utility routine, get_lookup_meaning, which resolves a lookup code to its meaning using FND_LOOKUPS, and a helper, set_fnd_message, which populates FND_MESSAGE message names and tokens and returns the formatted message text. These utilities indicate that eligibility evaluation results are surfaced to end users through Oracle Application Object Library messaging, and that debug tracing is controlled via the OKL debug framework (OKL_DEBUG_PUB) writing to FND_LOG_MESSAGES at procedure and statement level.

Key Procedures and Functions

• VALIDATE — The central eligibility validation routine. It evaluates the applicable criterion set and criterion values for the transaction under consideration and determines whether the transaction satisfies those criteria.
• GET_ADJUSTMENT_FACTOR — Returns the adjustment factor associated with the criterion or criterion set configuration, allowing the evaluated result to be weighted or adjusted in accordance with defined business rules.
• COMPARE_ELIGIBILITY_CRITERIA — Performs the comparison between the transaction's actual attribute values and the configured eligibility criteria, determining whether each criterion is met and contributing to the overall eligibility outcome.

The package body additionally contains internal utilities for lookup meaning resolution and FND message construction, which support the message text returned by the documented procedures. The user search term validate_territory most closely relates to the VALIDATE procedure: territory is one of the attributes commonly evaluated as part of eligibility criteria, and validation of the territory value is performed within the criterion comparison flow rather than through a separately documented procedure.

Tables Accessed

• OKL_FE_CRITERIA — Stores the eligibility criteria definitions evaluated by the package.
• OKL_FE_CRITERIA_SET — Stores criterion sets that group related criteria for a given evaluation context.
• OKL_FE_CRITERION_VALUES — Stores the permitted or expected values for each criterion, used in the comparison performed by COMPARE_ELIGIBILITY_CRITERIA.
• FND_LOG_MESSAGES — Receives debug log entries when OKL debug logging is enabled.
• PLITBLM — Referenced as an internal table used in the evaluation logic.

The package also reads FND_LOOKUPS to resolve lookup meanings used in messages and comparisons. Together these tables supply the configuration data against which transactions are evaluated and the diagnostic data recorded during execution.

Usage Notes

OKL_EC_EVALUATE_PVT is referenced by five other packages and is invoked indirectly through the OKL public evaluation APIs rather than being called directly from forms or concurrent programs. Typical invocation occurs when a lease or finance transaction requires eligibility determination — for example, when qualifying a contract against territory, product, or customer-related criteria maintained in the OKL_FE_CRITERIA tables. Because the procedures are private, customizations should target the calling public APIs; direct calls risk incompatibility across patch levels. Debug output can be enabled through the OKL debug framework to write trace records into FND_LOG_MESSAGES, which is useful when diagnosing unexpected eligibility results or missing message text. The source header indicates version 120.3, dated 2005; the package remains available in both 12.1.1 and 12.2.2 environments.