Search Results arp_run




Overview
Explore in AI Chat

Overview

ARP_RUN is a public PL/SQL package in the APPS schema that supports the Oracle Receivables revenue recognition and multicurrency posting processes. It is defined with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling user rather than the defining schema, and it is classified in the ETRM as an "OTHER" API rather than a standard open interface. The package header dates to Release 11i ($Header: ARTERRPS.pls 115.11) and remains documented through 12.1.1 and 12.2.2. It does not expose a formal public API contract for third-party integration; instead it provides the server-side entry points invoked by Receivables' own concurrent programs, forms, and internal processing logic. Its central business purpose is to launch and coordinate revenue recognition, including the worker-based distribution of revenue recognition workloads, and to support the submission of multicurrency (MRC) accounting postings to the general ledger.

Key Procedures and Functions

The documented metadata exposes four procedures.

  • REVENUE_RECOGNITION — Executes revenue recognition for a specific worker instance. It accepts a worker number and a report mode, and is scoped to an operating unit via an organization identifier. It constitutes the per-worker unit of work for the parallel revenue recognition process.
  • REV_REC_MASTER — Serves as the master (parent) driver for revenue recognition. It takes a report mode and worker-control parameters — maximum number of workers, polling interval, and a maximum wait threshold — together with an organization identifier. It spawns and monitors the worker sessions that invoke REVENUE_RECOGNITION, providing the concurrency and throttling logic for the overall run.
  • BUILD_CREDIT_DISTRIBUTIONS — Constructs credit distributions for a customer transaction. It accepts the current transaction identifier and a previous transaction identifier, which supports processing scenarios in which distributions reference an originating or prior transaction, such as credit memos applied against an earlier invoice.
  • SUBMIT_MRC_POSTING — Submits multicurrency accounting postings to the general ledger. Its inputs identify the primary set of books, the GL date range (start, end, and posted date), summary and journal-import behavior, the number of posting days per cycle, a posting control identifier, a debug flag, and the operating unit. It returns a status code for the submission.

Tables Accessed

The package references four documented objects through APPS synonyms.

  • AR_SYSTEM_PARAMETERS — Provides Receivables system option values, including operating unit and revenue recognition configuration settings that govern processing behavior.
  • RA_CUSTOMER_TRX — The transaction header table, read and updated as revenue recognition and posting eligibility are evaluated for invoices, debit memos, credit memos, and on-account credits.
  • RA_CUSTOMER_TRX_LINES — The transaction line table, the source of the revenue and distribution amounts that drive recognition and credit distribution construction.
  • DBMS_AQ — The Oracle Advanced Queuing package, used to enqueue and dequeue work items, consistent with the worker/master concurrency model implemented by REV_REC_MASTER and REVENUE_RECOGNITION.
  • PLITBLM — The Oracle Applications PL/SQL table management utility, referenced for internal collection handling within the package.

Usage Notes

ARP_RUN is not intended for direct invocation by external applications; the ETRM records zero other packages referencing it, which indicates it is a leaf-level implementation package rather than a shared library. It is invoked internally by Oracle Receivables — principally by the revenue recognition concurrent programs (master and worker phases) and by the multicurrency posting submission path — and can be called from custom concurrent programs or form-based logic when an implementation must reproduce standard revenue recognition or MRC posting behavior. The p_report_mode parameter appearing on both REVENUE_RECOGNITION and REV_REC_MASTER controls report output behavior for the recognition run, for example summary versus detail reporting; in REV_REC_MASTER it defaults to 'S'. Because the package lacks the naming conventions and error-handling contract of a documented open API, custom callers should treat these procedures as internal interfaces subject to change between patch levels, and should validate that the operating unit and report mode values passed match the Receivables system option setup for the target organization.