Search Results dm_reversal_amount_chk

Overview

ARP_TRX_COMPLETE_CHK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Within the Receivables (AR) module it acts as a transaction completion validation utility whose principal responsibility is to determine whether a receivable transaction is complete and eligible for posting to the General Ledger. The package centralises the completion-checking logic that would otherwise be duplicated across the many Receivables processes that must confirm a transaction's readiness before downstream accounting activity can proceed. Its metadata classification is OTHER, indicating that it is an internal utility package rather than a published public API; nonetheless it sits on a critical path because several core Receivables packages depend on it.

Key Procedures and Functions

The documented package exposes five procedures and functions. Their names and purposes are as follows; no parameter signatures are published in the metadata, and none should be assumed.

• DO_COMPLETION_CHECKING — the primary entry point that evaluates a transaction against the completion criteria and returns the outcome of that evaluation to the calling process. It is the routine invoked by external packages such as ARP_TRX_VALIDATE.
• CHECK_TAX_AND_ACCOUNTING — verifies that tax calculation and accounting distribution data associated with the transaction are present and internally consistent, forming part of the overall completeness determination.
• DM_REVERSAL_AMOUNT_CHK — validates reversal amount figures, principally in the context of adjustments and post-query processing where reversal values must reconcile against the original transaction.
• INIT — performs package-level initialisation, establishing session state and cached values used by the remaining routines.

Tables Accessed

The package reads and, where applicable, writes the following documented tables through APPS synonyms. Core transaction data is drawn from RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_LINE_GL_DIST, RA_CUST_TRX_LINE_SALESREPS and RA_CUST_TRX_TYPES, which supply the header, line, distribution, salesperson and transaction-type context required to judge completeness. AR_SYSTEM_PARAMETERS and RA_TERMS provide system-level and payment-term configuration that influence the evaluation. AR_ADJUSTMENTS and AR_CASH_RECEIPTS are consulted so that adjustments and receipts affecting the transaction are accounted for. Tax completeness is assessed against ZX_LINES, ZX_FORMULA_B and ZX_RATES_B. DBMS_SQL is used for dynamic SQL operations. The dependency metadata further confirms a direct reference to RA_CUSTOMER_TRX.

Usage Notes

ARP_TRX_COMPLETE_CHK is not intended for standalone invocation by end users. It is referenced by six other packages: ARP_CACHE_UTIL, ARP_PROCESS_HEADER_POST_COMMIT, ARP_TRX_VALIDATE, AR_INVOICE_TABLE_HANDLER, AR_TRANSACTION_GRP and IGI_EXP_UTILS, and is additionally self-referenced. These callers span transaction validation, group processing, post-commit header processing, cache management and the public invoice table handler, indicating that completion checking is exercised during both interactive transaction entry and batch posting workflows. Custom code should invoke the supported public APIs (for example AR_INVOICE_API_PUB) rather than calling this internal package directly, since its interface is not published and may change between patch levels. When troubleshooting transactions that fail to post, DBMS_OUTPUT tracing through the calling validation routines is the most reliable means of observing this package's behaviour.