Monday Aug 11, 2014

Receivables: Autoaccounting Analyzer now available

Oracle Receivables has just launched our latest Analyzer, the AutoAccounting Analyzer.  This new analyzer is a self-service health-check script that reviews the current configurations and settings for your AutoAccounting set-up and provides feedback and recommendations to address errors you are encountering.  Your data is NOT altered in any way when you run the Analyzer.  It does not perform INSERTS, UPDATES or DELETES.

So how does it work?  When creating a transaction via the Transaction Form or via AutoInvoice, and AutoAccounting raises errors, this Analyzer could assist you in identifying the cause and how to fix it.  This list shows sample error messages, you may get variations of the error messages below:

  • Please complete the offset account assignments
  • Please correct the receivables account assignment
  • Please correct the revenue account assignment
  • APP-AR-42536 This transaction is associated with at least one invalid or end-dated GL Account.

Currently the AutoAccounting Analyzer handles issues with the following AutoAccounting Types, values in () are what you would enter as p_account_type_in parameter when running the Analyzer:

  • Revenue (REV)
  • Receivable (REC)
  • Unearned Revenue (OFFSET)
  • Unbilled Receivable (OFFSET)
  • AutoInvoice Clearing (OFFSET)

How do you download and use this Analyzer?  The AutoAccounting Analyzer can be run via SQL*Plus or as a Concurrent Request.  For step by step details on how to download and run see DocID: 1904785.1 Oracle Receivables AutoAccounting Analyzer

The note includes two short videos on how to install the Analyzer as well as how to use the Output of the Analyzer.

Below is a small portion of the sample output.

Monday Jan 06, 2014

Webcast: Understand & Resolve AutoInvoice Validation Errors With The AutoInvoice Post-Process Validation Report


ADVISOR WEBCAST:  Understand & Resolve AutoInvoice Validation Errors With The AutoInvoice Post-Process Validation Report

Date:  January 15, 2014 at 11:00 am ET, 10:00 am CT, 9:00 am MT, 8:00 am PT

AutoInvoice validates interfaced data and rejects any invalid data. The AutoInvoice Post-Process (AIPP) Validation Report can be used to understand and rectify these validation errors. Join us to learn how to get the most from this feature packed tool! This one-hour session is recommended for technical and functional users of Oracle Receivables who use AutoInvoice to interface data from legacy or other Oracle Applications.

Topics will include:

  • Installing the AutoInvoice Post-Process Validation Report
  • Running the AIPP Validation Report
  • Maximizing efficiency using AIPP


For more details and how to register see Doc ID 1603525.1.

Monday Apr 08, 2013

Resolving Autoinvoice Date Issues

We get lots of questions about Autoinvoice and in this blog entry we'd like to offer some advice and help to try and take some of the mystery out of Autoinvoice Dates. 

There are just so many dates and so many ways to derive all the dates!  Receivables Transactions have General Ledger (GL) Date, Transaction Date, Ship Date, Sales Order Date, and Rule Start dates to name a few.  There are also several ways to get your dates, with Autoinvoice you can enter your GL Date and Transaction Date in the columns of RA_INTERFACE_LINES_ALL table or you can allow the AutoInvoice process to derive the dates.

If the dates are not provided in the interface tables they will be derived based on your setups.  Date Derivation of the General Ledger date and Transaction date during the process of AutoInvoice depends on the following date columns in the RA_INTERFACE_LINES_ALL table:


AutoInvoice determines the General Ledger date for invoices using the following criteria:

  • Does a GL date exist for this invoice in the interface table?
  • Does the invoice use rules?
  • What is the setting of the Derive Date option for this Transaction Batch Source (Yes or No)?   (Receivables Responsibility > Setup > Transaction > Sources)
  • What is the setting of the GL Date in a Closed Period option for this Transaction Batch Source (Adjust or Reject)?  (Receivables Responsibility > Setup > Transaction > Sources)

If you elected to derive the rule start date, AutoInvoice first uses the ship date in the interface table. If the ship date does not exist, AutoInvoice uses the sales order date. If the sales order date does not exist, AutoInvoice uses the date you entered in the Run AutoInvoice window.  The following diagram illustrates this process.

For more examples and diagrams see the 'Determining Dates' section of our  Oracle Receivables User Guide.

Wednesday May 23, 2012

Knowledge Focus: How To Setup AutoInvoice For Optimal Performance - DocID: 1083467.1

The objective of this document is to provide step by step instructions on the setups required in Receivables (AR) in order for AutoInvoice to perform at an optimal level.

Learn more here:   Doc ID: 1083467.1

This document assumes that you have already set up the Receivables application and that you are able to successfully import transactions using AutoInvoice with no errors. Please review Note 1067402.1,  AutoInvoice Setup for Release 12: A Case Study Using a Simple Script,  for more details.

This document also assumes that you have run the Oracle Receivables AutoInvoice Setup Test and have this information readily available. The table below shows the Application Release and applicable note that you can follow to get the diagnostic results.


Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected



« August 2016