Search Results arp_process_recur




Overview
Explore in AI Chat

Overview

ARP_PROCESS_RECUR is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Oracle Receivables recurring transactions infrastructure and is responsible for processing recurring invoice batches generated against recurring transaction rules. Recurring transactions in Receivables allow a billing pattern to be defined once and applied repeatedly over a defined schedule; ARP_PROCESS_RECUR supplies the runtime logic that evaluates due dates, derives transaction amounts and numbering, stages summarized recurring lines in interim tables, and submits the concurrent request that ultimately creates the invoices. The package records a status of VALID, and ETRM classifies it as an OTHER API. It is a supporting internal package rather than a formally published public API, and it is referenced by one other database object. Its dependency list includes ARP_RECUR_PKG, ARP_CTL_SUM_PKG, ARP_TRX_VALIDATE, ARP_UTIL, ARPT_SQL_FUNC_UTIL, FND_REQUEST, RA_BATCH_SOURCES and RA_RECUR_INTERIM, indicating close coupling with the rest of the Receivables recurring and transaction validation code base.

Key Procedures and Functions

The documented package exposes five program units, each contributing to the preparation and submission of recurring invoice processing:

  • CREATE_INV_CONC_REQ — Submits the concurrent request responsible for the actual generation of recurring invoices. It provides the bridge between the recurring rules staged by this package and the standard Receivables invoice generation program executed through FND_REQUEST.
  • GET_DUE_DATE — Determines the appropriate due date for a recurring transaction line, applying the recurring rule's payment terms and scheduling logic so that generated invoices carry correct due dates.
  • GET_AUTO_TRX_NUMBERING_FLAG — Returns the flag indicating whether automatic transaction numbering applies, allowing the process to decide whether document numbers are assigned by the system or supplied explicitly.
  • INSERT_RECUR — Inserts recurring transaction data into the interim staging structure used during processing, effectively populating the working set that feeds invoice creation.
  • GET_TRANSACTION_AMOUNT — Derives the transaction amount for a recurring line, applying the amount basis defined on the recurring rule.

Tables Accessed

Two underlying tables are documented, accessed through APPS synonyms:

  • RA_BATCH_SOURCES — Read to resolve batch source attributes used when the recurring lines are converted into invoices, ensuring the generated transactions inherit correct batch source behavior and accounting defaults.
  • RA_RECUR_INTERIM — The interim table into which recurring lines are staged via INSERT_RECUR before final processing, and from which the invoice generation request reads its working set.

Usage Notes

ARP_PROCESS_RECUR is normally invoked indirectly rather than called from custom code. It executes when recurring transactions are processed from the Receivables responsibility, either as part of the recurring batch workflow or through a scheduled concurrent program that submits the recurring invoice generation request. Because the package is documented as an OTHER API and is not referenced by any database object, Oracle does not publish it as a supported extension point, and direct calls from custom PL/SQL carry upgrade risk across 12.1.1 and 12.2.2. Customizations should generally target the standard recurring transaction forms and concurrent programs instead, treating ARP_PROCESS_RECUR as internal implementation logic. When diagnosing recurring billing issues, DBAs and developers typically enable logging around this package and FND_REQUEST to trace due date, amount, and numbering derivation before invoice creation.