Search Results g_missing_contract

Overview

OKL_DEAL_PAYMENTS_PVT is a private PL/SQL package body in the Oracle EBS Lease and Finance Management (OKL) application, owned by the APPS schema. Its API classification is PVT, indicating it is a private implementation package intended for internal use by the OKL module rather than for direct external invocation by customer code. The package provides the foundational logic that supports the creation and loading of payment headers and related descriptive data on lease and financing deals. Because it is a private package, its procedures are typically called by sibling public packages (for example, deal or contract wallet APIs) during transaction processing rather than being exposed through a public API surface.

The package begins with a substantial block of global constants that reveal its function. It defines standard error and message tokens such as G_INVALID_CRITERIA, G_UNEXPECTED_ERROR, G_REQUIRED_VALUE, and G_SQLERRM_TOKEN, along with the OKL application name reference carried over from OKL_API. These constants support consistent error raising and message-token substitution throughout the package. Notably, the constant G_MISSING_CONTRACT maps to the message name 'OKL_LLA_CONTRACT_NOT_FOUND', and the token G_CONTRACT_ID_TOKEN is bound to 'CONTRACT_ID'. This directly ties the package to contract-dependent validations, ensuring that any procedure requiring a contract identifier raises a meaningful error when the contract cannot be located.

Key Procedures and Functions

The documented public surface of the package body consists of three program units:

• GET_FEE_SERVICE_NAME — Returns a descriptive service name for a fee, likely resolving a system item or service description against the appropriate translation tables. It is used when generating or displaying payment line descriptions for fees on a lease or financing deal.
• GET_ASSET_NUMBER — Retrieves the asset number associated with a given deal item or contract line. This function supports descriptive output of the leased asset and is dependent on the item and contract-line tables documented below.
• LOAD_PAYMENT_HEADER — The principal procedure in the package, responsible for loading or constructing a payment header record for a deal. It serves as the coordinating routine that pulls together fee and asset description data and applies the contract-validation logic implied by G_MISSING_CONTRACT.

The metadata does not expose parameter lists for these units; their behaviour should be inferred from the naming convention and from the tables each is documented to reference.

Tables Accessed

The package accesses five APPS-synonym tables, each primarily for descriptive lookup:

• MTL_SYSTEM_ITEMS_TL — Provides translated item descriptions, used by GET_FEE_SERVICE_NAME to resolve fee service names.
• OKC_K_ITEMS — Stores contract line items, required to associate asset and fee data with the correct contract line.
• OKC_K_LINES_B — The base contract-lines table, supplying the link between a contract line and its associated items.
• OKC_K_LINES_TL — The translated contract-line table, providing language-specific line descriptions.
• OKL_STRM_TYPE_TL — Lease stream type descriptions, used to label payment streams on the payment header.

No documented write operations are exposed, suggesting the package is largely a read-and-assemble utility for downstream deal payment processing.

Usage Notes

Because OKL_DEAL_PAYMENTS_PVT is a private package (G_API_TYPE = '_PVT', G_SCOPE = '_PVT', API version 1.0), it is not intended for direct invocation by end users, forms, or concurrent programs. It is instead called internally by OKL deal and contract wallet processing code. The G_MISSING_CONTRACT message and G_CONTRACT_ID_TOKEN constant confirm that any calling context must supply a valid contract identifier; source code that invokes this package must be prepared to handle the OKL_LLA_CONTRACT_NOT_FOUND message when the contract lookup fails. The package is referenced by zero other documented packages in the ETRM metadata, reinforcing its role as a supporting utility rather than a widely reused component.

The header line (OKLRDPYB.pls 120.0, dated 2007/05/04) indicates this code is shared across EBS 12.1.1 and 12.2.2 with no substantive changes in the documented version. Customisations should avoid depending on the package directly; instead, custom code that needs equivalent behaviour should call the corresponding public OKL API, or wrap the private package with awareness that its signature is not guaranteed stable across patches.