Results for “update_pymt_start_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_LA_PAYMENTS_PVT is a private PL/SQL package in the APPS schema within Oracle Lease and Finance Management (OLFM), part of the Oracle E-Business Suite. The package encapsulates the payment-level business logic used by the Lease and Finance Management stream generation and contract management engines. Its role is to compute, validate, insert, update, and delete individual payment line records associated with a contract's payment stream, including handling variable interest schedules, order sequencing, and derived start and end dates for each payment.

The package is classified as a private API (PVT). It is not published for direct external calls; instead it forms the internal engine behind the public stream APIs and the payment views exposed to the application. It is called by OKL_LA_STREAM_PVT, the contract-level private packages (OKL_CONTRACT_PVT, OKL_CONTRACT_LINE_ITEM_PVT, OKL_CONTRACT_TOP_LINE_PVT), termination processing (OKL_AM_CNTRCT_LN_TRMNT_PVT), fee maintenance (OKL_MAINTAIN_FEE_PVT), quote-to-contract conversion, and the open interface. It also backs the OKL_LA_PAYMENTS_UV and OKL_CS_FEE_PAYMENTS_UV views, and the OKL_LA_PAYMENTS_PVT_W wrapper package used for OAF-based UI calls.

Key Procedures and Functions

• PROCESS_PAYMENT — Core routine that drives creation or regeneration of a payment record within a payment stream, applying the contract's rules and stream type to derive the payment attributes.
• CALCULATE_DETAILS — Computes the numerical details of a payment (amounts and schedule attributes) based on stream type, rate parameters, and contract rules.
• DELETE_PAYMENT — Removes a payment record and its dependent detail rows, typically invoked when a contract line or stream is restructured or terminated.
• VARIABLE_INTEREST_SCHEDULE — Builds the schedule of variable interest payments, referencing rate parameters stored against the contract header.
• UPDATE_PYMT_START_DATE — Adjusts the start date of a payment row when contract dates or billing cycles change.
• GET_DISPLAY_END_DATE — Derives the end date presented for a payment (as distinct from the stored internal end date), supporting UI display in the payment stream.
• GET_START_DAY — Returns the start day used to anchor the payment's period, honouring billing-day and calendar conventions.
• GET_ORDER_SEQUENCE — Returns the ordering sequence for a payment within its stream, used to present payments in the correct chronological or logical order.

Tables Accessed

The package reads and writes contract and stream data through APPS synonyms. Header and line definitions come from OKC_K_HEADERS_B, OKC_K_LINES_B, OKC_K_ITEMS, OKC_LINE_STYLES_B, OKC_RULES_B, OKC_RULE_GROUPS_B, OKC_STATUSES_B, and OKC_RULES_V. OLFM-specific tables include OKL_K_HEADERS, OKL_K_LINES, OKL_K_RATE_PARAMS, OKL_STRM_TYPE_B (and OKL_STRMTYP_SOURCE_V), and OKL_BOOK_CONTROLLER_TRX for accounting interaction. PLITBLM and V$PARAMETER are used for instance-level and date-format utilities. OKL_API and OKC_API provide error handling and message utilities.

Usage Notes

OKL_LA_PAYMENTS_PVT is invoked indirectly by end users through the Lease Management payment stream and contract forms, and by concurrent programs that generate or regenerate payment schedules — including stream generation, fee assessment, and contract termination. It should not be called directly from custom code; integrations should use OKL_LA_STREAM_PVT, OKL_CONTRACT_PVT, or the supported public APIs (OKL_RULE_PUB, OKL_API). Custom clients needing payment data may query the OKL_LA_PAYMENTS_UV view. All calls run within the caller's transaction, so rollback and savepoint behaviour follows the invoking process.