E1: 76A: Credit Note Invoice Process Applies Incorrect Tax Rate
(Doc ID 2969607.1)
Last updated on APRIL 01, 2024
Applies to:
JD Edwards EnterpriseOne Sales Order Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
With AR localization ON, a credit memo is raised against a specific line of an invoiced sales order. When the credit memo is invoiced, the tax value written to the F76A18 table is based on the current configuration of the Tax Group, not the configuration that was in place at the time the specific line was created in the sales order.
STEPS TO DUPLICATE:
- Activate AR localization; configure a Tax Group to use a VAT/IVA rate and several Percepcion rates from the 76A/TC UDC. Important: one of the Percepcion rates should be present in the Tax Group P76A15 from the start, but should NOT have a tax value defined for it in the P76A10 application. The remaining Percepcion rates do have a tax value. Note the sum of the combined tax percentages, for example 30%.
- Raise an order for 2 lines of the same item; set the P4210 to display the Order Acceptance form and note that the tax value presented in this form is the correct percentage (30% or whatever combined tax percentage is in effect).
- Run the R42565/R76A565 invoice process over line 1.000 of the sales order ONLY and confirm that the correct tax value is written to the F76A18 table.
- Now configure the ‘undefined’ Percepcion rate with a tax value in the P76A10 application. For example, 5%.
- Invoice Line 2.000 of the order – the R76A566 PDF and the F76A18 show the correct tax amount (eg, 35% or whatever has been configured).
- Run both sales order lines through Sales Update R42800.
- With P4210, raise a Credit Memo against Line 1.000 of the sales order – the Order Acceptance form shows the current tax rate (eg 35%) is used, and the same value is seen in the Invoice PDF and the F76A18 table.
- The tax percentage calculated on the Credit Order line is incorrect – Line 1.000 was created with a combined tax rate of 30%, not the (current) 35%.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |