Search Results arrx_c_adj




Overview

ARRX_C_ADJ is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite Release 12. Its name follows the Receivables "ARRX" naming convention, indicating a component of the Oracle Advanced Collections (formerly iReceivables/Collections) module rather than core Receivables transaction processing. The package has a documented status of VALID in both the 12.1.1 and 12.2.2 releases, confirming that its compiled specification and body are present and usable in the database. The ETRM classification for the package is OTHER, meaning it is not exposed as a formal public API such as the AR_ADJUSTMENTS_API family, but rather serves as contained, internal processing logic.

The business function implied by the package name and its single documented procedure, ADJUSTMENT_REGISTER, is the registration and recording of adjustments within the collections domain. In this context, adjustments are typically write-offs, small-balance write-offs, or collection-related balance corrections applied to delinquent customer accounts. The package encapsulates the logic required to register such adjustments so that the collections application can reflect a reduction or correction of an outstanding receivable without directly invoking the full Receivables adjustment API.

Key Procedures and Functions

The ETRM documentation lists exactly one documented procedure or function for APPS.ARRX_C_ADJ:

  • ADJUSTMENT_REGISTER — The procedure responsible for registering an adjustment within the collections processing flow. Its purpose is to record adjustment activity against a customer account or related collections object so that the adjustment becomes visible to subsequent collections processing and reporting. Because the ETRM metadata does not publish a parameter list for this procedure, no signature or argument names should be assumed; callers that need the exact interface must inspect the compiled specification, for example via a database object browser or the ARRX_C_ADJ specification source in the APPS schema. The procedure is the sole documented entry point of the package, indicating that ARRX_C_ADJ is a narrowly scoped utility rather than a general-purpose adjustment library.

Tables Accessed

The documented metadata for ARRX_C_ADJ includes a tables-referenced section with no explicit table entries listed, and no base tables are recorded as accessed via APPS synonyms. This is a notable characteristic of the package entry: the ETRM record does not surface a table dependency list. In practice, a procedure named ADJUSTMENT_REGISTER would be expected to insert or update adjustment-related rows in the collections and Receivables data model, but because the documentation does not enumerate any tables, no specific objects should be asserted. The dependency information that is documented shows only references to the SYS schema and the STANDARD package, which is a standard artifact of PL/SQL compilation and does not reflect business-level table usage. Consultants should therefore determine the actual table footprint by examining the package body source directly.

Usage Notes

ARRX_C_ADJ is not referenced by any other documented package, and it does not itself appear to call other application packages according to the ETRM dependency listing. It is likely invoked either from an Oracle Forms-based collections screen or from a concurrent program that performs batch adjustment registration, such as during delinquency processing or strategy-driven collection activities. Because it is classified as OTHER rather than a supported public API, customizations should avoid calling ARRX_C_ADJ directly where a supported Receivables API exists; doing so risks breakage on upgrade between 12.1.1 and 12.2.2.

Where the package is used, the typical invocation pattern is internal to the Advanced Collections application, with the calling form or program supplying the account and adjustment context expected by ADJUSTMENT_REGISTER. Developers investigating unexpected adjustments, missing write-offs, or error messages originating from this package should review the ARRX_C_ADJ specification and body in the APPS schema, since the published ETRM metadata intentionally limits itself to dependency and object-status information rather than procedural detail.