Search Results delete_line_conts

Overview

APPS.AR_REVENUE_MANAGEMENT_PVT is a private (PVT) PL/SQL package in Oracle E-Business Suite Receivables (AR) that implements the revenue management and revenue recognition engine used to support ASC 605 / SOP 97-2 style revenue deferral and contingency processing. Its header (ARXRVMGS.pls, version 120.23) indicates the package has been stable since the 11i/R12.1 era and remains present through 12.2.2. The package encapsulates the business rules for determining whether revenue may be recognized, whether an invoice line is collectible, and whether a transaction qualifies for revenue deferral treatment. It provides the procedural core invoked by the Revenue Management process, the Revenue Contingency Analyzer, and supporting concurrent programs. Because it is classified as PVT, it is not a public API and Oracle does not guarantee backward compatibility; it is intended for internal use by Oracle application code and by advanced extensions at the customer's own risk.

Key Procedures and Functions

The package exposes 18 documented procedures and functions. The key entry points and their purposes are:

• REVENUE_MANAGEMENT_ENABLED — Determines whether revenue management functionality is active for the current operating unit/system parameters configuration.
• CASH_BASED — Evaluates whether cash-basis revenue recognition applies to a given transaction or line.
• ACCEPTANCE_ALLOWED — Returns whether acceptance-based revenue recognition is permitted for the transaction.
• CREDITWORTHY — Assesses customer creditworthiness as a precondition for revenue recognition.
• LINE_COLLECTIBLE / TXN_COLLECTIBLE / LINE_COLLECTIBILITY — Determine collectibility at line, transaction, and combined levels; collectibility is a gating factor for recognizing revenue on contingencies.
• RECEIPT_ANALYZER — Analyzes receipt applications against receivable transactions to identify collections that release revenue contingencies, driving the revenue recognition outcome. This is the procedure most directly associated with the "receipt_analyzer" search term.
• REVENUE_SYNCHRONIZER — Synchronizes revenue records with transaction and contingency data.
• PERIODIC_SWEEPER — Runs periodic housekeeping to process deferred revenue and clear temporary working tables.
• PROCESS_EVENT — Handles workflow event processing tied to revenue deferral (e.g., the noncollectible invoice event) declared via c_revenue_deferral_event.
• UPDATE_LINE_CONTS / DELETE_LINE_CONTS / DELETE_FAILED_ROWS / DELETE_REJECTED_ROWS — Maintain contingency and interface staging records, including cleanup of error and rejected rows.
• GET_LINE_ID — Returns the line identifier used to correlate revenue management operations.

Tables Accessed

The package references these APPS synonyms: RA_CUSTOMER_TRX_LINES (invoice lines driving revenue), WF_EVENTS (workflow event subscriptions), AR_ADJUSTMENTS (adjustments affecting collectibility), AR_DEFERRAL_REASONS, AR_DEFERRED_LINES (deferral tracking), AR_LINE_CONTS and AR_LINE_CONTS_ALL (line contingencies), AR_INTERFACE_CONTS (contingency interface), AR_RDR_PARAMETERS_GT (revenue deferral report parameters), AR_RECEIVABLE_APPLICATIONS (receipt application matching for RECEIPT_ANALYZER), AR_REVIEWED_LINES_GT, AR_SYSTEM_PARAMETERS, AR_TRX_CONTINGENCIES_GT, AR_TRX_ERRORS_GT, and AR_TRX_HEADER_GT. The global temporary tables (GT) are used to stage transaction, contingency, error, and parameter data during concurrent processing.

Usage Notes

This package is invoked internally by the Revenue Management concurrent programs, the Revenue Contingencies window, and the Receivables transaction workbench when revenue deferral is enabled. It should not be called directly from custom code because it lacks documented parameter interfaces and is subject to change without notice. If custom logic must interact with revenue management, the supported public APIs in AR_REVENUE_ADJUSTMENT_API and AR_RECEIPT_API should be used instead. The RECEIPT_ANALYZER path, in particular, is executed during collections processing to evaluate whether receipt applications satisfy collectibility contingencies and thereby allow revenue to be earned.