In this Document

APPLIES TO:

SYMPTOMS

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

When Creating transactions via AutoInvoice, or the Transactions Form or APIs or via a hook-up into Receivables, you get the Error: 

Please correct the revenue account assignment 

This can occur in:
Oracle Receivables Transaction Workbench
Oracle Receivables: AutoInvoice Import
Oracle Receivables: Invoice API's
Oracle Projects: Project Billing Generate Draft Invoices or Revenue

CAUSE

Numerous

SOLUTION

 
There are multiple causes for this error to be raised, the following guides you through the various things you can check/use to address this error:

1. Check AutoAccounting Setup

If you are getting the error in AutoInvoice, try creating a manual transaction and use the same GL account segments. As you enter each GL account segment in the transaction form, if validation logic fails, the form will raise an error. This will help you in identifying which segments have issues and will assist you in resolving the problem.

For this particualr error message, the GL account in error will be displayed, and a particular segment will be missing. Let's take the following as an example: 

Please correct the revenue account assignment (03-0000000--0000-00000-0000-0000)

A close look at the accounting segments shows the 3rd segment is missing.

Responsibility: Receivables Manager
Navigation: Setup > Transactions > AutoAccounting
Then query up for Type = Revenue, and review the source for each of the segments. For this example, the 3rd segment is raising the error, so pay attention to where the 3rd segment is sourced from.

Depending on what the source is for the failing segment, you can use the following steps to investigate/troubleshoot further.

a) If Segments Source = Salesreps

When a segment of the GL account has to be derived from the GL accounts associated with the Salesrep, then it is pertinent that you associate a Salesrep to your transactions. Check whether the following has been set-up correctly:

• Transaction Source

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Query up the transaction source used for your AutoInvoice import batch, and navigate to the AutoInvoice Options tab, and ensure that the checkbox for Allow Salescredit is checked.



Next check the Sales Credit Validation tab, verify what you have setup for Salesperson, how you set it up here impacts what AutoInvoice will expect to see in the RA_INTERFACE_LINES_ALL table (discussed below)

• System Options

Responsibility: Receivables Manager
Navigation: Setup > System > System Options

Navigate to the Miscellaneous tab and check if the Require Salesperson checkbox is checked.



The combination of the above settings determines the behavior re. Salescredits data in AutoInvoice.

Note: Regardless of the combination of settings you define below, if you pass data in RA_INTERFACE_SALESCREDITS_ALL, then AutoInvoice will validate that the data you provided is valid.

Allow Salescredit field (In Transaction Source)	Require Salesperson (in System Options)	Requirement of Salescredit information
Checked	Checked	Mandatory
Checked	Not Checked	Optional
Not Checked	Checked	Mandatory
Not Checked	Not Checked	Any data entered will be ignored

• GL account associated to Salesrep

Responsibility: CRM Resource manager
Navigation: Maintain Resources > Resources

Ensure that Freight, Receivables and Revenue Accounts associated to the Salesrep have been setup completely. 

• Data in RA_INTERFACE_SALESCREDITS_ALL 

When you have defined AutoAccounting such that some GL account segments are sourced from Salesreps, make sure that you populate the table RA_INTERFACE_SALESCREDITS for each line in RA_INTERFACE_LINES_ALL so that the proper accounting can be derived, and ensure that the values in INTERFACE_LINE_CONTEXT + INTERFACE_LINE_ATTRIBUTE1-15 match up.

This is required when you source segments from Salesreps and is necessary even if your system option Require Salesreps is set to No.

• Data in RA_INTERFACE_LINES_ALL

If your source is Salesreps, and your Transaction Source setup for Salesperson is:

• Number, then you should be populating RA_INTERFACE_LINES_ALL.PRIMARY_SALESREP_NUMBER
• Id, then you should be populating RA_INTERFACE_LINES_ALL.PRIMARY_SALESREP_ID

• Script to find incomplete Salesrep setup for AutoAccounting
  The following script will pick up all Salesreps that do not have all the GL accounts setup, this could assist you in proactively setting these up to avoid issues in AutoInvoice.
  
  SELECT NAME,
         SALESREP_NUMBER,
         SALESREP_ID,
         PERSON_ID,
         STATUS,
         NVL(TO_CHAR(GL_ID_REV), 'NULL REV') GL_ID_REV,
         NVL(TO_CHAR(GL_ID_REC), 'NULL REC') GL_ID_REC,
         NVL(TO_CHAR(GL_ID_FREIGHT),'NULL FREIGHT') GL_ID_FREIGHT
  FROM   JTF_RS_SRP_VL
  WHERE  STATUS = 'A'
  AND    ((NVL(START_DATE_ACTIVE, sysdate) <= sysdate) AND
          (NVL(END_DATE_ACTIVE, sysdate) >= sysdate))
  AND    (GL_ID_REC IS NULL OR
          GL_ID_REV IS NULL OR
          GL_ID_FREIGHT IS NULL)
  AND EXISTS 
  (SELECT 'x' 
   FROM   RA_ACCOUNT_DEFAULTS_ALL a, 
          RA_ACCOUNT_DEFAULT_SEGMENTS s
   WHERE  s.GL_DEFAULT_ID = a.GL_DEFAULT_ID 
   AND    s.CONSTANT is null 
   AND    s.TABLE_NAME = 'RA_SALESREPS');
    
  
  
  
• Projects Users:  Set up a Credit Receiver on a project so that the RA_INTERFACE_SALESCREDITS_ALL table is populated by the 'Interface Invoices to Receivables' process. This may require that the 'No Sales Credit' salesperson be setup as an employee.  Setting this up will allow you to bypass the mandatory salesrep validation when none exists.  To complete this setup, go into the Receivables responsibility: NAV Setup/Transactions/Sources. 
  Query your batch source. Go to tab AutoInvoice options. Mark allow salescredit.

b) If Segment Source =  Standard Lines

When your GL account segments are source from Standard lines, it is pertinent to associate either an Inventory Item or a Memo line to your transaction, so that AutoAccounting can derive the GL account segments. Check whether the following have been setup correctly:

• Transaction Source

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Query up the transaction source used for your AutoInvoice import batch, and navigate to the Other Information tab, how you set up Memo Line Rule and/or Inventory Item here impacts what AutoInvoice will expect to see in RA_INTERFACE_LINES_ALL table (discussed below).

• GL account associated to Inventory Item or Memo Line

For an Inventory Item

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Items > Define items

Query the item and in the Invoicing Tab check the value in the Sales Account field.



For a Memo Line

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Memo Lines

Make sure that the Revenue Account is populated. 

• Data in RA_INTERFACE_LINES_ALL

• If your source is Memo Line, and your Transaction Source setup for Memo Line Rule is:
• Value, then you should be populating RA_INTERFACE_LINES_ALL.MEMO_LINE_NAME
• Id, then you should be populating RA_INTERFACE_LINES_ALL.MEMO_LINE_ID

• if your source is an Inventory Item, and your Transaction Source setup for Inventory Item is:
• Segment, then you should be populating RA_INTERFACE_LINES_ALL.MTL_SYSTEM_ITEMS_SEG1-20 (as appropriate)
• Id, then you should be populating RA_INTERFACE_LINES_ALL.INVENTORY_ITEM_ID

• Script to find incomplete Memo Line or Inventory Item setup for AutoAccounting
  The following script will pick up Memo Lines that do not have all the Revenue account setup, this could assist you in proactively setting these up to avoid issues in AutoInvoice.
  
  SELECT T.NAME, B.MEMO_LINE_ID, 
         NVL(TO_CHAR(b.GL_ID_REV),'NULL REV') GL_ID_REV 
  FROM   AR_MEMO_LINES_ALL_TL T, 
         AR_MEMO_LINES_ALL_B B 
  WHERE  b.MEMO_LINE_ID = t.MEMO_LINE_ID
  AND    ((nvl(b.END_DATE, sysdate) >=sysdate) AND
          (nvl(b.START_DATE,sysdate) <=sysdate))
  AND    b.GL_ID_REV IS NULL
  AND EXISTS
  (SELECT 'x'
   FROM   RA_ACCOUNT_DEFAULTS_ALL a,
          RA_ACCOUNT_DEFAULT_SEGMENTS s
   WHERE  s.GL_DEFAULT_ID = a.GL_DEFAULT_ID
   AND    s.CONSTANT is null
   AND    s.TABLE_NAME = 'RA_STD_TRX_LINES');
    
  
  The following script will pick up Inventory Items from organizations involved in Order Management that do not have the Sales Account setup, this could assist you in proactively setting these up to avoid issues in AutoInvoice.
  
  SELECT ORGANIZATION_ID, DESCRIPTION, INVENTORY_ITEM_ID,
         NVL(TO_CHAR(SALES_ACCOUNT),'NULL SALES ACCOUNT')
  FROM   MTL_SYSTEM_ITEMS
  WHERE  ((nvl(END_DATE_ACTIVE, sysdate) >=sysdate) AND
          (nvl(START_DATE_ACTIVE,sysdate) <=sysdate))
  AND    ORGANIZATION_ID IN 
        (SELECT MASTER_ORGANIZATION_ID
         FROM   OE_SYSTEM_PARAMETERS_ALL)
         AND    SALES_ACCOUNT IS NULL
         AND    EXISTS
               (SELECT 'x'
                FROM   RA_ACCOUNT_DEFAULTS_ALL a,
                       RA_ACCOUNT_DEFAULT_SEGMENTS s
                WHERE  s.GL_DEFAULT_ID = a.GL_DEFAULT_ID
                AND    s.CONSTANT is null
                AND    s.TABLE_NAME = 'RA_STD_TRX_LINES')
  ORDER BY 1;
    
  

c) If Segment Source = Transaction Types

When a segment of the GL account has to be derived from the GL accounts associated with the Transaction Type, then it is pertinent that you associate the correct Transaction Type to your transactions, and that the GL accounts for the transaction type are defined. Check whether the following has been set-up correctly:

• Transaction Sources

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Query up the transaction source used for your AutoInvoice import batch, and navigate to the Other Information tab, and your setup for Transaction Type. How you have it setup here impacts what AutoInvoice will expect to see in RA_INTERFACE_LINES_ALL (discussed below)

• Transaction Type

Ensure that you have populated the GL accounts associated to the Transaction Type you are using in your Interface table.

• Data in RA_INTERFACE_LINES_ALL

If your Transaction Source setup for Transaction Type is:

• Value, then you should be populating RA_INTERFACE_LINES_ALL.CUST_TRX_TYPE_NAME
• Id, then you should be populating RA_INTERFACE_LINES_ALL.CUST_TRX_TYPE_ID

• Script to find incomplete Transaction type setup for AutoAccounting

The following script will pick up transaction types that do not have all the GL accounts setup. If you have some AutoAccounting defined to source from Transaction Types, then the incomplete GL account setup could cause issues - this script could assist you in proactively setting these up to avoid issues in AutoInvoice.

SELECT ORG_ID, NAME, CUST_TRX_TYPE_ID, TYPE,
       STATUS, POST_TO_GL, ACCOUNTING_AFFECT_FLAG,
       NVL(TO_CHAR(GL_ID_REC), 'NULL REC') gl_id_rec,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_REV), 'NULL REV')) gl_id_rev,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_FREIGHT), 'NULL FREIGHT')) 
              gl_id_freight,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_CLEARING), 'NULL CLEARING'))
              gl_id_clearing,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_TAX), 'NULL TAX')) gl_id_tax,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_UNBILLED), 'NULL UNBILL'))
              gl_id_unbilled,
       DECODE(type,'BR','NOT APPLICABLE',
              NVL(TO_CHAR(GL_ID_UNEARNED), 'NULL UNEARN')) 
              gl_id_unearned,
       DECODE(type,'BR',NVL(TO_CHAR(GL_ID_UNPAID_REC),
              'NULL UNPAIDREC'),'NOT APPLICABLE') gl_id_unpaidrec,
       DECODE(type,'BR',NVL(TO_CHAR(GL_ID_REMITTANCE),
              'NULL REMITTANCE'),'NOT APPLICABLE') gl_id_remittance,
       DECODE(type,'BR',NVL(TO_CHAR(GL_ID_FACTOR), 'NULL FACTOR'),
              'NOT APPLICABLE') gl_id_factor,
       START_DATE, END_DATE
FROM   RA_CUST_TRX_TYPES_ALL
WHERE  ((NVL(START_DATE, sysdate) <= sysdate)
         AND (NVL(END_DATE, sysdate) >= sysdate))
AND    NVL(STATUS,'A') = 'A'
AND    ((TYPE = 'BR' AND
        (GL_ID_REC IS NULL OR 
         GL_ID_UNPAID_REC IS NULL OR
         GL_ID_REMITTANCE IS NULL OR
         GL_ID_FACTOR IS NULL))
        OR
        (TYPE <> 'BR' AND
        (GL_ID_REC IS NULL OR
         GL_ID_REV IS NULL OR
         GL_ID_FREIGHT IS NULL OR
         GL_ID_CLEARING IS NULL OR
         GL_ID_TAX IS NULL OR
         GL_ID_UNBILLED IS NULL OR
         GL_ID_UNEARNED IS NULL)))
AND EXISTS 
(SELECT 'x'
 FROM   RA_ACCOUNT_DEFAULTS_ALL a,
        RA_ACCOUNT_DEFAULT_SEGMENTS s
  WHERE s.GL_DEFAULT_ID = a.GL_DEFAULT_ID
  AND   s.CONSTANT is null
  AND   s.TABLE_NAME = 'RA_CUST_TRX_TYPES')
 ORDER BY 1;

d) If Segment Source = Sites

• Transaction Sources

Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources

Query up the transaction source used for your AutoInvoice import batch, and navigate to the Customer Information tab, and check how you have setup Bill To Address and Bill To Customer, how you have it setup here impacts what AutoInvoice will expect to see in RA_INTERFACE_LINES_ALL (discussed below)

 

• Customer Site
  Ensure that you have populated the Accounts associated at the Bill To Site level. 
  
  
  

• Check that the Site you are using is associated to the same Operating Unit (ORG_ID) as the transaction you are interfacing.
  
  Responsibility: Receivables Manager
  Navigation: Customers > Customers
  
  Query up the customer record, drill down to the Account Level and then to the Site Level and ensure the Site is linked to the right operating Unit.
  
  
  
• Data in RA_INTERFACE_LINES_ALL

• If your Transaction Source setup for Bill To Customer is:
• Value, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUSTOMER_REF
• Id, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUSTOMER_ID
  
  
• If your Transaction Source setup for Bill To Address is:
• Value, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_REF
• Id, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_ID

• Script to find incomplete Site setup for AutoAccounting

The following script will pick up Customer Sites that do not have all the GL accounts setup at the Bill To Site. 

You can limit the rows returned by filtering adding a condition on party_name, or just checking for a particular GL account, or by processing in batches using a condition like: 
and rownum < 300 

This could assist you in proactively setting these up to avoid issues in AutoInvoice.

SELECT cust_acct.ACCOUNT_NUMBER customer_number,
       substr(party.PARTY_NAME,1,30) customer_name,
       substr(loc.ADDRESS1,1,30) address,
       site_uses.CUST_ACCT_SITE_ID address_id,
       site_uses.LOCATION, site_uses.SITE_USE_ID,
       site_uses.SITE_USE_CODE,
       nvl(to_char(site_uses.GL_ID_REC), 'NULL REC')
       gl_id_rec,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO',nvl(to_char(site_uses.GL_ID_REV),
              'NULL REV'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_rev,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO',  
              nvl(to_char(site_uses.GL_ID_FREIGHT), 
              'NULL FREIGHT'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_freight,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO',
              nvl(to_char(site_uses.GL_ID_CLEARING), 
              'NULL CLEARING'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_clearing,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 
              nvl(to_char(site_uses.GL_ID_TAX), 
              'NULL TAX'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_tax,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 
              nvl(to_char(site_uses.GL_ID_UNBILLED), 
              'NULL UNBILL'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_unbill,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 
              nvl(to_char(site_uses.GL_ID_UNEARNED), 
              'NULL UNEARN'),
              'DRAWEE' , 'NOT APPLICABLE') gl_id_unearn,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 'NOT APPLICABLE',
              'DRAWEE', 
              nvl(to_char(site_uses.GL_ID_UNPAID_REC), 
              'NULL UNPAID REC')) gl_id_unpaidrec,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 'NOT APPLICABLE',
              'DRAWEE' ,
              nvl(to_char(site_uses.GL_ID_REMITTANCE),
              'NULL REMITTANCE')) gl_id_remittance,
       decode(site_uses.SITE_USE_CODE,
              'BILL_TO', 'NOT APPLICABLE',
              'DRAWEE' ,
              nvl(to_char(site_uses.GL_ID_FACTOR), 
              'NULL FACTOR')) gl_id_factor
FROM   HZ_PARTIES PARTY,
       HZ_PARTY_SITES PARTY_SITE,
       HZ_CUST_ACCOUNTS_ALL CUST_ACCT,
       HZ_LOCATIONS LOC,
       HZ_CUST_ACCT_SITES_ALL ACCT_SITES,
       HZ_CUST_SITE_USES_ALL SITE_USES
WHERE  party_site.LOCATION_ID = loc.LOCATION_ID
AND    party.PARTY_ID = cust_acct.PARTY_ID
AND    cust_acct.CUST_ACCOUNT_ID = 
       acct_sites.CUST_ACCOUNT_ID
AND    acct_sites.CUST_ACCT_SITE_ID =  
       site_uses.CUST_ACCT_SITE_ID
AND    party_site.PARTY_SITE_ID = acct_sites.PARTY_SITE_ID
AND    site_uses.SITE_USE_CODE in ('BILL_TO' ,'DRAWEE')
AND    site_uses.STATUS = 'A'
AND    ((site_uses.SITE_USE_CODE = 'BILL_TO' AND
        (site_uses.GL_ID_REC IS NULL OR
         site_uses.GL_ID_REV IS NULL OR
         site_uses.GL_ID_FREIGHT IS NULL OR
         site_uses.GL_ID_CLEARING IS NULL OR
         site_uses.GL_ID_TAX IS NULL OR
         site_uses.GL_ID_UNBILLED IS NULL OR 
         site_uses.GL_ID_UNEARNED IS NULL))
        OR
        (site_uses.SITE_USE_CODE = 'DRAWEE' AND
        (site_uses.GL_ID_REC IS NULL OR
         site_uses.GL_ID_UNPAID_REC IS NULL OR
         site_uses.GL_ID_REMITTANCE IS NULL OR
         site_uses.GL_ID_FACTOR IS NULL)))
AND EXISTS
(SELECT 'x'
 FROM   RA_ACCOUNT_DEFAULTS_ALL a,
        RA_ACCOUNT_DEFAULT_SEGMENTS s
 WHERE  s.GL_DEFAULT_ID = a.GL_DEFAULT_ID
 AND    s.CONSTANT is null
 AND    s.TABLE_NAME = 'RA_SITE_USES');

2. Validate the Shipping Inventory Organization

If the Shipping and Selling organizations are different, with each belonging to a different Set of Books each set up with a different Chart of Accounts, you may get an error such as the following, even when your AutoAccounting setup is complete.

Please complete your tax accounting flexfield or

Please correct the revenue account assignment

This issue is manifested because the Chart of Accounts for each set of books has a different number of segments, for example:

• Selling Organization GL accounts has 13 segments
• Shipping Organization GL accounts has 7 segments

Current functionality was not designed to handle this scenario. An enhancement request has been logged for this issue, via Bug 2432013.

3. If you are passing Data in RA_INTERFACE_DISTRIBUTIONS_ALL

If you are passing the distributions in RA_INTERFACE_DISTRIBUTIONS_ALL, adn get the following errors:

EXCEPTION: arp_auto_accounting.do_autoaccounting_internal()
ORA-20000: APP-15482: Please correct the receivable account assignment

Things to check:

• If you want AutoAccounting to determine your general ledger accounts you must not enter values in RA_INTERFACE_DISTRIBUTIONS_ALL.
• If you want to bypass AutoAccounting, then you need to provide complete information in the distribution table for the ACCOUNT_CLASS distributions you intend to provide.
• If you are in a multi-org instance, ensure that you have included the ORG_ID value in the distributions you pass, and that the value is consistent across the interface tables.
• Check that the INTERFACE_LINE_CONTEXT + INTERFACE_LINE_ATTRIBUTE* values you provide in the RA_INTERFACE_DISTRIBUTIONS_ALL table match the values in the corresponding rows in RA_INTERFACE_LINES_ALL, so that AutoInvoice can match up the transaction to its proper distributions.

4. Check the profile option: AR: Use Invoice Accounting for Credit Memos

If you are importing Credit Memos, and you encounter the error: Please correct the revenue account assignment, verify whether you would like the credit memo to use the same GL accounts of the Invoice it is crediting. If yes, then check your setting for the profile option: AR: Use Invoice Accounting for Credit Memos. If the setting is:

• Yes, Receivables does not use AutoAccounting to create the default values for these accounts. Instead, credit entries are created using the GL accounts of the invoice or debit memo you are crediting.
• No, Receivables will generate GL accounts for the credit memo based on the AutoAccounting setup

5. Check if the GL account exists and is active

Once all the segments of your GL account have been derived by AutoAccounting, check if it exists and is active.

Responsibility: Receivables Manager
Navigation: Setup > Financials > Accounting > GL accounts

Query for Account = the GL account segments, for example: Query for 03-100-1324-0000-000. 

The form will display whether the GL account exists, if it is enabled and active.

Alternatively, if you want to check whether a particular code_combination_id (ccid) value refers to a valid and active GL account, you can run the following:

6. Verify Accounting Flexfield setting for Enabled and Allow Dynamic Inserts

Considering AutoAccounting will derive and build GL accounts on the demand, you should check whether you allow the Accounting Flexfield to do dynamic inserts.

If your business process allows dynamic creation of new code combinations, set the checkbox to Yes. 

Responsibility: Receivables Manager
Navigation: Setup > Financials > Flexfields > Key > Segments.

• Query on Flexfield Title Accounting Flexfield
• Locate the record for the Accounting Flexfield Structure you are using
• check the Enabled and Allow Dynamic Inserts checkbox

If your business does not allow dynamic inserts, then you need to review why AutoAccounting attempted to generate a code combination that you have not yet set up. If you verify, that the new code combination is valid you need to create the code combination manually to avoid the error next time the same code combination is derived.

Responsibility: Receivables Manager
Navigation: Setup > Financials > Accounting > GL Accounts

7. Verify whether the GL account does not violate any cross-validation rules of the segments.

Responsibility: System Administrator 
Navigation: Application > Flexfield > Key > CrossValidation 

Query for Title = Accounting Flexfield Structure = Provide the Structure you are using 
Then review the rules and see if the GL Account you are using has segments which fall into the ranges excluded.

8. Check for Possible Known Bugs

When setup has been ruled out as a possible root cause, it is often good to investigate bugs to see if any problems have been reported with this error. It is not uncommon for a bug in AutoInvoice to present with an Autoaccounting error. This occurs whenever AutoInvoice cannot derive data for one of the sources used by your AutoAccounting setup. For example, if your AutoAccounting uses the SalesRep but a bug is preventing the system from finding the salesrep, the problem could show up as an error in deriving the account. 

The table below lists bugs that have been reported as of the last update date for this note which cause this symptom.

9. Use the AutoInvoice Post-Process Validation Report

There is a new AutoInvoice Validation Report that provides more details including recommendations and action items you can follow to fix AutoInvoice Import Validation Errors. Read more about this new report in Note 1523525.1

Still Have Questions?

REFERENCES