My Oracle Support Banner

Understanding and Troubleshooting Event-Based Revenue Management (Doc ID 1130963.1)

Last updated on JULY 19, 2021

Applies to:

Oracle Receivables - Version 12.0.1 to 12.1.1 [Release 12.0 to 12.1]
Oracle Receivables - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Executable:RAXMTR - Autoinvoice Master Program
Executable:RAXTRX - Autoinvoice Import Program
Executable:ARREVSWP - Revenue Contingency Analyzer
ConcurrentProgram:ARVRVMGX - Revenue Management Exceptions Report


Oracle Receivables (AR): AutoInvoice Information Center > Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 > Note 1130963.1

Oracle Receivables (AR): Transactions Workbench Information Center > Note 1130963.1

Oracle Receivables provides multiple methods by which revenue can be recognized for an invoice:

Information provided here includes an overview of Event-Based Revenue Management, setup requirements, and methods by which users can invoke the feature and troubleshooting tips.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 1. Overview of Event-Based Revenue Management
 2. Setup Requirements
    a. Revenue Policy
    b. Revenue Contingencies
         i. Create Revenue Contingencies
         ii. Assign the Revenue Contingency
    c. Enabling Event-Based Revenue Management
    d. Monitoring Contingencies with the Revenue Contingency Analyzer
 3. Using Event-Based Revenue Management in the Transactions workbench 
 4. Using Event-Based Revenue Management in AutoInvoice
    a. Example #1: Interface data for an invoice with the seeded Extended Payment Term contingency. 
    b. Example #2: Interface data for an invoice with a User-Defined Expiration Date contingency which uses an Event Attribute
    c. Example #3: Interface data for an invoice with a Seeded Contingency Forfeitures which does not use an Event Attribute
 5. Underlying Tables, Seed Data and Code
    a. Tables
    b. Seeded Contingencies and Removal Events
    c. Event-Based Revenue Recognition Code
 6. Various Examples of Setup for Event-Based Revenue Management
 7. Troubleshooting
    a. Missing data in Deferred Revenue Audit Trail Report and Revenue Management Exceptions Report
    b. Invoices are Deferring Revenue unexpectedly
    c. Passing data in AR_INTERFACE_CONTS_ALL causes Validation errors
    d. Passing data in AR_INTERFACE_CONTS_ALL for Refund does not create contingencies
 8. Patching
 9. Still Have Questions?
 Still Have Questions?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.