Search Results get_lookup_desc

Overview

APPS.AR_LATE_CHARGE_PKG is the core PL/SQL package body responsible for Oracle Receivables late charge (interest) processing in Oracle E-Business Suite 12.1.1 and 12.2.2. Late charges are the interest amounts assessed against overdue customer balances. This package calculates those charges, generates the corresponding interest invoice or adjustment transactions, and orchestrates the concurrent submission and monitoring of that work. The package body header ($Header: ARLCDOCB.pls 120.25.12020000.3) reflects a long-lived, actively patched component of the Receivables interest feature set.

The package is tuned for volume: a bulk fetch row limit (g_bulk_fetch_rows := 10000) supports array-based processing, and the body declares extensive DBMS_SQL index-by tables for invoice headers, lines, payment schedules, currency, exchange rate, salesrep, and GL distribution attributes. These collections allow the package to accumulate late charge invoice data in memory before passing it to the Receivables Invoice API. Function reference items such as g_func_curr, g_interest_batch_id, g_object_version_number, g_org_id, g_BATCH_SOURCE_ID, and g_int_cal_date carry working state across the calculation, and the package is instrumented through FND_PROFILE.value('AFLOG_ENABLED'), enabling standard EBS debug logging.

Key Procedures and Functions

• GET_LOOKUP_DESC — Retrieves the description for a lookup code, the utility most commonly sought by users searching this package. It resolves lookup values used during late charge processing.
• PHRASE — Returns a message or phrase string, typically used to build user-facing or log text.
• EMPTY_VAR_IV — Empties the package-level invoice collection variables, resetting state between processing runs.
• INV_TO_INV_API_INTERFACE — Maps the in-memory late charge data into the Receivables Invoice API interface structures.
• CALL_INVOICE_API — Invokes the Receivables Invoice API to create the late charge transaction.
• CREATE_CHARGE_INV_DM — Creates the late charge invoice in direct/deferred mode.
• CREATE_CHARGE_ADJ — Creates an adjustment-based late charge where an adjustment is the appropriate transaction type.
• CREATE_LATE_CHARGE_CHILD, SUBMIT_LATE_CHARGE_CHILD, WAIT_FOR_END_SUBREQ, GET_STATUS_FOR_SUB_PROCESS — Handle child concurrent request creation, submission, waiting, and status retrieval for the multi-request late charge workflow.
• CREATE_LATE_CHARGE — The primary driver that coordinates the overall late charge run.
• CREATE_LATE_CHARGE_PER_WORKER, ORDONANCER_PER_WORKER, CREATE_LATE_CHARGE_BY_WORKER, SUBMIT_LATE_CHARGE_WORKER — Implement the worker-based parallel processing model, distributing late charge calculation and creation across concurrent workers.

Tables Accessed

The package reads and writes the core Receivables interest tables — AR_INTEREST_HEADERS, AR_INTEREST_HEADERS_ALL, AR_INTEREST_LINES, AR_INTEREST_BATCHES, and AR_INTEREST_BATCHES_ALL — which store the calculated interest headers, detail lines, and batch grouping. AR_PAYMENT_SCHEDULES supplies the overdue balances and due dates that drive the interest calculation. AR_ADJUSTMENTS and AR_CASH_RECEIPTS support adjustment-based charges and payment reconciliation. AR_RECEIVABLES_TRX and AR_SYSTEM_PARAMETERS provide transaction type definitions and system-level configuration. AR_SUBMISSION_CTRL_GT supports the concurrent submission control flow, while AR_INV_API_HEADERS_GT, AR_INV_API_LINES_GT, and AR_INV_API_DIST_GT are the interface tables that feed the Receivables Invoice API. AR_LATE_CHARGE_DOC_GT serves as a global temporary staging table for the late charge document data.

Usage Notes

AR_LATE_CHARGE_PKG is normally invoked by the Receivables late charge concurrent program, which submits worker requests that this package manages. The package is also called from Oracle Forms-based interest and late charge setup screens and can be referenced from custom code; ETRM records it as being referenced by two other packages, indicating an integration surface for extensions. Implementers searching for GET_LOOKUP_DESC should note that it is an internal helper resolving lookup descriptions, not a standalone public API. Because it is an "OTHER" classification package, direct calls should respect its parameters, the FND_PROFILE debug flag, and the collection-table state; all calls run under APPS with the appropriate org and security context set.