Results for “dist_ccid”

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

Overview

ARRX_ADJ is an Oracle E-Business Suite PL/SQL package owned by APPS that supports the Adjustments Report within Oracle Receivables. Its central role is to drive the report data engine behind the Receivables adjustments reporting concurrent program, retrieving adjustment activity across invoices, receipts, and related receivables transactions and presenting summarized or detailed output for a specified reporting entity and period.

The package is one component of the ARRX family of reporting packages, which supply the query, binding, and formatting logic used by Oracle Reports executables in Receivables. It is classified as OTHER in the ETRM metadata, indicating it is not a public, customer-facing API but an internal report-support package. The documented header revision ($Header: ARRXADJS.pls 120.6, dated 2005) reflects a stable, long-lived implementation carried forward across releases, including 12.1.1 and 12.2.2.

A distinctive feature of ARRX_ADJ is its use of a single, wide parameter signature for the main report procedure. This signature exposes filters for the reporting level and entity, ledger and chart of accounts context, company segment ranges, GL and transaction and due date ranges, currency ranges, invoice type ranges, adjustment type ranges, and document sequence criteria. The document sequence filters — p_doc_seq_name together with the low and high sequence values — allow the report to be restricted to a named document sequence, which is the element most commonly sought when users inspect this package for sequence-related reporting behavior.

Key Procedures and Functions

• ARADJ_REP — the principal driver procedure. It accepts the full report parameter set, including request_id and standard report request parameters such as retcode and errbuf, executes the adjustment query, and produces the report output.
• ARADJ_BEFORE_REPORT — initialization hook invoked before the report data set is produced, typically used to prepare package state or temporary data.
• ARADJ_BIND — binds the query's dynamic SQL parameters to the report cursor, using an integer cursor handle as its argument so that the report's dynamic SQL statement is populated with the selected filter values.
• ARADJ_AFTER_FETCH — post-fetch processing hook, invoked after rows are retrieved to apply any remaining report-time transformations.
• DIST_DETAILS — a function that eliminates reporting details from the AR_DISTRIBUTIONS table, resolving the reporting context for a given adjustment, chart of accounts, and reporting entity and returning a numeric result.
• DIST_CCID — a companion function that returns the accounting flexfield code combination identifier (CCID) for a distribution, given the adjustment, chart of accounts, and reporting entity identifiers.

Tables Accessed

• AR_SYSTEM_PARAMETERS and AR_SYSTEM_PARAMETERS_ALL — read to obtain Receivables system options and organization-level settings that govern report behavior and reporting context.
• GL_LEDGERS — accessed to resolve ledger and chart of accounts information aligned with the p_sob_id and p_coa_id parameters.
• DBMS_SQL — the Oracle-supplied dynamic SQL package, referenced because the report builds and executes its query dynamically, with parameter binding handled through ARADJ_BIND. Adjustment and distribution data are read through the AR_DISTRIBUTIONS construct referenced by the DIST_DETAILS and DIST_CCID functions.

Usage Notes

ARRX_ADJ is invoked indirectly rather than directly. Its normal entry point is the Receivables Adjustments Report concurrent program, which supplies the full parameter list — including p_doc_seq_name, p_doc_seq_low, and p_doc_seq_high when a document sequence filter is entered — and calls ARADJ_REP. The before-report, bind, and after-fetch hooks are driven by the report's PL/SQL execution framework in support of the dynamic query.

Because the package is classified as OTHER and is not a documented public API, custom development should not call it directly; customizations requiring adjustment reporting data should use supported Receivables views and APIs instead. When troubleshooting, note that the report's parameter record definition defines p_doc_seq_name with a narrower length than the procedure argument, and that the package is referenced by one other package within the ARRX reporting group, so changes to shared state can affect more than one report.