My Oracle Support Banner

R12 : Check AutoAccounting set-up (Doc ID 419027.1)

Last updated on MARCH 01, 2018

Applies to:

Oracle Receivables - Version 12.0.0 and later
Information in this document applies to any platform.

Purpose

IMPORTANT TIP:

In the past we recommended using the AutoAccounting Analyzer
. However, this analyzer was made obsolete effective March 1, 2018.
You can instead use:
  • Transaction Analyzer version 200.23 <Note 2058269.1>
  • AutoInvoice Analyzer version 200.13 <Note 1523525.1>


The AutoAccounting feature in Receivables allows users to specify how to determine the General Ledger accounts for transactions that are entered manually or imported using AutoInvoice. Receivables creates default accounts for revenue, receivable, freight, tax, unearned revenue, unbilled receivable, finance charges, bills receivables accounts, and AutoInvoice clearing (suspense) accounts using this information.

If you have not set-up AutoAccounting properly, you may hit errors during transaction creation, posting or various other activities which attempt to define the default GL accounts.

This note should be used when Receivables General Set up diagnostic (Note 419051.1 ) or Receivables AutoInvoice diagnostic (Note 419055.1 ) reports the following warning in the AutoAccounting Setup section :

Warning-Certain tables have null accounts and as such AutoAccounting will be unable to derive an account Action-See Note 419027.1 to assist in finding and resolving the records with null accounts

The above quoted Diagnostic notes will indicate per account and per table the number of records having a null account that may pose an issue. On the other hand, the SQL statements below covers all cases as it checks for all accounts that are null, but you can modify the where condition to check for specific null accounts.

Example, when searching for transaction types that have a null Revenue account, you can limit the where clause to :

 

where ((nvl(start_date, sysdate) <= sysdate)
and (nvl(end_date, sysdate) >= sysdate))
and nvl(status,'A') = 'A'
and type <> 'BR' and
gl_id_rev is null;

 

To use the select statements below, you first need to set the organization context as follows :

execute mo_global.set_policy_context('S', &orgId);

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
Purpose
Troubleshooting Steps
 Still Have Questions?
References

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