Search Results okl_process_ppd_pvt




Overview
Explore in AI Chat

Overview

OKL_PROCESS_PPD_PVT is a private PL/SQL package body in the Oracle E-Business Suite Lease and Finance Management (formerly Oracle Lease Management) module, owned by the APPS schema. The suffix _PVT designates it as an internal implementation package rather than a public API; the corresponding public-facing interface in the OKL family is exposed through the OKL_API package hierarchy and the OKL_API_ALL wrapper. The package encapsulates logic for processing PPD records — the "Payments and Payment Details" constructs used in lease contracts to represent payment structures at the asset, stream, and line level.

A significant portion of the package body is devoted to parameter validation. The internal validate_parameters procedure checks that required inputs such as the contract header ID, KLE (contract-line/asset) table, transaction date, PPD amount, PPD reason code, and payment structure table are populated and internally consistent. Custom exceptions declared in the body — missing_parameters and invalid_payment_structure — signal these conditions back to callers. This is directly relevant to the search term okl_api_all_missing_param, which is the error raised when a required argument is not supplied to a public API that ultimately delegates to this private logic. The validation distinguishes structural anomalies such as a stream level header (SLH) present without a corresponding stream level line (SLL), or a sequence that begins with an SLL and expects an SLH to follow, and raises the appropriate exception when such conditions are detected.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package:

  • APPLY_PPD — Applies the PPD (payment processing detail) changes to the lease contract based on the validated parameters. This is the entry point invoked by higher-level callers to commit PPD processing logic against the contract identified by the transaction context.

Internally, the body also contains the private validate_parameters procedure, which performs the null-checks and payment-structure consistency checks described above. Two record types, asset_rec_type and validate_rec_type, along with the associative array val_rec_tbl, are used to stage validation results across asset and contract-line combinations. Debug logging is governed by the constant G_DEBUG_ENABLED, which calls OKL_DEBUG_PUB.CHECK_LOG_ENABLED.

Tables Accessed

The package references the following tables through APPS synonyms:

  • OKL_TRX_CONTRACTS — The transaction-contract association table. The DATE_TRANSACTION_OCCURRED column provides the transaction date used in parameter validation and PPD processing.
  • PLITBLM — The Oracle standard PL/SQL table-of-varchar2 used for message handling, supporting the message count and message data out parameters returned to callers.

The package also joins against rule and header views such as OKC_K_HEADERS_V, OKC_RULES_V, and OKC_RULE_GROUPS_V to resolve contract headers, rules, and asset line identifiers during validation, though these are accessed via the OKC public views rather than directly.

Usage Notes

Because OKL_PROCESS_PPD_PVT is a private package, it is not intended for direct invocation by external callers. It is referenced by one other package, which is the typical client — likely a public API in the OKL_API_ALL or OKL_PROCESS_PPD family that performs the standard EBS API boilerplate (initializing the message list, calling the private logic, and translating raised exceptions into the standard x_return_status / x_msg_count / x_msg_data out parameters).

In practice, PPD processing is triggered from the Lease Management contract forms and from concurrent programs that recalculate or redistribute lease payments, particularly around asset rebooking (hence the KLE table and mass-rebook types referenced in the validation signature). When custom code invokes the public wrapper without supplying a mandatory argument, the validation logic raises missing_parameters, which the public layer surfaces as the okl_api_all_missing_param error. Developers troubleshooting that error should verify that the contract header ID, transaction date, PPD amount, reason code, and payment structure inputs are all non-null before diagnosing further.