Search Results insert_on_acc_cm_request

Overview

The OKL_CREDIT_MEMO_PVT package is a private (PVT) PL/SQL API within the Oracle E-Business Suite Oracle Lease and Finance Management (OKL) module. It provides the internal processing logic required to create and submit credit memo requests against lease and finance contracts. Credit memos are used to issue monetary credits to a customer's account, adjusting receivable balances arising from lease transactions. The package encapsulates the record structures, constants, and procedural logic that support downstream invoicing and accounts receivable integration through the OKL_TRX_AR_INVOICES_PUB public API. Because the package is classified as private, it is not intended for direct external invocation; it functions as a supporting layer consumed by other OKL packages and the credit memo submission flow.

Key Procedures and Functions

The ETRM metadata documents two procedures within OKL_CREDIT_MEMO_PVT, with a structured record type defined to carry credit memo attribute data.

• INSERT_REQUEST — Creates and registers a credit memo request. It accepts parameters describing the credit amount, credit style, description, credit date, transaction type, and the lease or contract identifier against which the credit is applied. Bug fix references in the source (for example, Bug 5897792) added the transaction_source and source_trx_number parameters, enabling the credit memo to be tied back to an originating transaction for traceability. The procedure validates and stages the request record for downstream processing.
• INSERT_ON_ACC_CM_REQUEST — Handles on-account credit memo requests, where the credit is posted directly to the customer's account rather than against a specific transaction line. This aligns with the user's search term "insert_on_acc_cm_request." It reuses the shared credit_rec structure and depends on the table of records (credit_tbl) to pass multiple credit lines for processing.
• Supporting data structures — The package declares the credit_rec record (lsm_id, transaction_source, source_trx_number, credit_amount, credit_sty_id, credit_try_name, credit_desc, credit_date, currency_code) and the credit_tbl collection type, plus subtypes aligned to OKL_TRX_AR_INVOICES_PUB record and table types. These structures standardize the data passed to the AR invoice interface.

Tables Accessed

Via APPS synonyms, the package reads and writes the following documented tables:

• OKL_TRX_AR_INVOICES_B, OKL_TXL_AR_INV_LNS_B, OKL_TXD_AR_LN_DTLS_B — Header, line, and line-detail storage for AR invoices generated from lease transactions; the credit memo ultimately feeds these.
• OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B, OKC_RULES_B — Contract core tables supplying contract, line, style, and rule context for the credit.
• OKL_K_HEADERS, OKL_TRX_TYPES_TL — Lease header and transaction type lookups used to resolve transaction type and descriptive data.
• HZ_CUSTOMER_PROFILES — Customer account profile data used to determine the correct receivable account and currency context.
• PLITBLM — A standard PL/SQL message/logging table used for transaction and error tracking.

Usage Notes

OKL_CREDIT_MEMO_PVT is invoked indirectly rather than by end users. It is referenced by two other packages, which act as its callers and drive the credit memo creation flow. Typical invocation paths include the Oracle Lease Management credit memo submission forms and concurrent programs that post credits to Accounts Receivable. Because the package is private, customizations should call the corresponding public API rather than this private package directly. When developing extensions, developers should preserve the credit_rec and credit_tbl structure contracts, respect the OKL_UNEXPECTED_ERROR and error-token constants for consistent exception handling, and confirm that any transaction_source and source_trx_number values are supplied where traceability to an originating transaction is required.