Search Results dist_by

Overview

ARRX_TX is a PL/SQL package body owned by APPS in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified under the ETRM repository as an "OTHER" API type, meaning it is not published as a general-purpose public interface but instead supports internal report generation logic for the Receivables (AR) module. The package's primary responsibility is to drive the "AR Transaction RX Report," a reporting utility that extracts, formats, and forecast-renders receivable transaction data. It also supports a sales-oriented reporting variant. The package encapsulates the report trigger logic (BEFORE_REPORT, BIND, AFTER_FETCH) that BI Publisher and Oracle Reports source files invoke at runtime, along with validation helpers and lookup procedures for last-updated audit columns. Because of the RX naming and FA_RX_UTIL_PKG debug calls, it belongs to the same reporting infrastructure family used by Oracle's standard Receivables reporting suites.

Key Procedures and Functions

The package exposes 19 documented procedures and functions, organized around three reporting entry points and their supporting triggers:

• ARTX_REP — The main AR Transaction RX report driver. It accepts a broad set of filtering parameters (completion and posting flags, GL and transaction date ranges, transaction type/class ranges, balancing segment, bill-to customer name and number ranges, currency, payment method, document sequence name and number range, reporting level and entity, account ranges, batch source, and transaction class) and returns retcode and errbuf for concurrent program integration.
• BEFORE_REPORT, BIND, AFTER_FETCH — Standard report life-cycle triggers that initialize globals, bind query parameters, and post-process fetched rows respectively.
• ARTX_REP_CHECK and CHECK_BEFORE_REPORT, CHECK_BIND, CHECK_AFTER_FETCH — Validation counterparts that verify report parameters and pre/post conditions before the main execution path.
• ARTX_REP_FORECAST and FORECAST_BEFORE_REPORT, FORECAST_BIND — A forecasting variant that projects receivable transaction data forward using the same parameter model.
• ARTX_SALES_REP and SALES_BEFORE_REPORT, SALES_BIND, SALES_AFTER_FETCH — A sales-focused reporting entry point with its own trigger set.
• GET_CONS_BILL_NUMBER — Retrieves consolidated billing numbers, most likely for grouping transactions in the report output.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, WHERE_LAST_UPDATE — Utility functions that supply the standard audit columns and a WHERE-clause fragment for last-update filtering.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• RA_CUSTOMER_TRX — The primary transaction header table, supplying the core report rows.
• RA_CUSTOMER_TRX_LINES — Line-level transaction detail.
• RA_CUST_TRX_LINE_GL_DIST — Distribution records used to satisfy GL date and balancing segment filters.
• AR_PAYMENT_SCHEDULES — Payment schedule data supporting completed and posted flag evaluation.
• AR_CONS_INV — Consolidated invoice information used with GET_CONS_BILL_NUMBER.
• AR_SYSTEM_PARAMETERS_ALL — Organization and system configuration defaults.
• DBMS_SQL and DUAL — Dynamic SQL execution and singleton lookup support.

Usage Notes

ARRX_TX is normally invoked indirectly through its associated concurrent programs and Oracle Reports/BI Publisher report definitions rather than called directly from custom code. Report definitions reference the ARTX_REP, ARTX_REP_FORECAST, and ARTX_SALES_REP entry points, passing the parameter set captured in the standard AR reporting submission form. The package is referenced by one other package documented in ETRM, indicating a small internal call graph. Customizations that require the same filter set or audit-column logic may call the utility functions (LAST_UPDATED_BY, LAST_UPDATE_DATE, WHERE_LAST_UPDATE), but modifications to the report drivers themselves are not supported and are overwritten by patching.