Search Results purge_transaction_data

Overview

ARRX_C_TRX is an Oracle Receivables reporting package that supports the Receivables Transaction Register and related accounting extracts. In Oracle EBS 12.1.1 and 12.2.2 it belongs to the ARRX family of report-support packages that are invoked by concurrent programs to produce formally formatted, submission-ready register output. The package operates at the boundary between the Receivables transaction tables and the reporting/interface layer used by Oracle E-Business Tax and general ledger reconciliation processes. Its most visible entry point, TRANSACTION_REGISTER, accepts the full set of concurrent program parameters associated with a transaction report — reporting level, reporting entity, set of books, chart of accounts, company and account ranges, GL date ranges, currency and transaction type ranges, invoice class, transaction date ranges, and document sequence criteria — and returns the standardized errbuf and retcode out parameters expected by concurrent program submission. The package therefore serves as the report driver that validates parameters, selects qualifying transactions, and hands the result set to the reporting engine.

Key Procedures and Functions

• TRANSACTION_REGISTER — The primary report driver. It receives the concurrent program parameter list (reporting level, entity, ledger, account and date ranges, batch source, transaction type, invoice class, document sequence, and debug/SQL trace flags) and orchestrates the generation of the receivables transaction register output.
• TRANSACTION_CHECK — A companion validation routine, used to verify the reporting parameter set or the eligibility of transactions before the register is generated.
• RECEIPT_FORECAST — Produces receipt forecast output, projecting anticipated cash receipts from outstanding receivables. This is the procedure associated with the user search term "receipt_forecast" and is the reason the package is often referenced during cash forecasting and collections analysis.
• SALES_REGISTER — Generates the sales register extract, summarizing invoiced sales activity for a given reporting period and entity.
• PURGE_TRANSACTION_DATA — Removes or ages previously staged transaction register data, maintaining the temporary reporting structures used by the other procedures.

Tables Accessed

Based on the documented metadata, the package reads from and writes to the following objects through APPS synonyms:

• AR_TRANSACTIONS_REP_ITF — The Receivables transactions reporting interface table. This is the primary staging object into which qualifying transaction rows are populated for report formatting and output.
• FND_USER — The Oracle Application Object Library user table, referenced for user and responsibility context, audit stamping, or parameter validation.

No other tables are documented for this package, indicating that its transactional logic is concentrated on the AR reporting interface rather than direct manipulation of base AR tables.

Usage Notes

ARRX_C_TRX is invoked almost exclusively from Oracle Receivables concurrent programs — typically the Transaction Register and Sales Register reports — where TRANSACTION_REGISTER is called with the submitted parameter values and the standard errbuf/retcode signature. The package is not documented as being called by any other package, so it sits at the top of its call hierarchy. Custom development that needs the same output should call the package procedures directly rather than re-implementing the extraction logic, but must supply the complete positional parameter list, since the interface uses long positional signatures with many optional trailing arguments. In 12.1.1 and 12.2.2 the package is essentially unchanged and remains an APPS-owned, OTHER-classified API intended for report execution rather than open transactional integration.