Last updated on JULY 28, 2017
Applies to:Oracle Receivables - Version 12.0.0 and later
Information in this document applies to any platform.
When creating an Adjustment using a Receivable Activity that is defined to use a Tax Rate Code the process fails with:
APP-AR-96024: Account Generator is unable to derive information
Further investigation of the setup shows that there are 2 records defined using the same Tax Rate Code, one with a Tax Jurisdiction Code and the other without. It is the Tax Rate Code without the Tax Jurisdiction Code that is associated to the Receivable Activity.
Per <Bug 9191297> Receivable Activities for Adjustment cannot be associated to a Tax Jurisdiction Code, the explanation from Dev is as follows:
Tax Jurisdiction Code is a Internal EBtax setup and can be derived only when
EBTax processing happens.
When creating an adjustment the tax code LOV is there in the Receivables
form, and tax calculation is not called at this point.
There is no way Receivables can derive the applicable Tax Jurisdiction Code.
Only when the Adjustment is passed to tax can tax rate codes with
Jurisdiction codes be used.
When an Adjustment is created for which Receivables prorates the tax amount
themselves, and does not call tax at all, there is no way Receivables can
derive the tax jurisdiction Code and use it accordingly.
In the case reported here however, the tax rate code used for the Receivable Activity does NOT have a Tax Jurisdiction code and yet it is failing. It appears that the presence of 2 records with the same name is confusing the code.
Following illustrates the setup:
Set up two tax rate codes with same name, one has Tax Jurisdiction Code and the other doesn't have tax Jurisdiction Code.
Record Tax rate code Tax Jurisdiction Code Tax
------ --------------- --------------------- ----------------
1 XXXX_JP_STCC_AR NULL XXXX_JP_STCC_TAX
2 XXXX_JP_STCC_AR XXXX_JUR XXXX_JP_STCC_AR
Record #1 (without Tax Jurisdiction Code) is related to "Adjustment" in the Receivable Activity, and yet the process fails. The debug log shows that the incorrect tax_rate_id was selected (i.e. Record 2) and as a result CCID wasn't derived correctly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms