My Oracle Support Banner

WS: 03/04/42/43: Troubleshooting Vertex L Series Issues Related to Sales and Purchase Order Processing (Doc ID 1568403.1)

Last updated on MARCH 12, 2021

Applies to:

JD Edwards World Sales Order Management - Version A7.3 cume 4 and later
JD Edwards World Procurement - Version A7.3 cume 4 and later
Information in this document applies to any platform.

Purpose

 To describe how to correct issue which may result while processing sales and purchase orders with the use of Vertex taxation.

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
  Troubleshooting errors on Customer Master
 Issue 1:  Error 011E 
 Issue 2 :  VERTEX, finding a GeoCode based on township
 Issue 3:  Vertex Error 4995 – Possible Geocode Match in Customer Master (V01053) 
 Issue 4:  F15 on Customer Master fails to return a GeoCode
 Issue 5:  F15 on Customer Master P01053 Brings in Invalid Expired Vertex Geocode
 Issue 6:  Using Vertex 5.0.01 to calculate tax on sales order results in Sales Tax instead of Use Tax based on the Florida origin and Missouri destination.
 Issue 7:  Vertex tax for District Doubled with Exempt Customer and Intrastate Sale
 Issue 8: Vertex TDM for Product Exemption Not Working
 Issue 9:  Vertex - GeoCode for Puerto Rico
 Issue 10:  Vertex Geocode Pop-up Blank
 Issue 11:  Running A73 Cume 09 with the following SARS: 4503801, copy module I73VTN, and 5643427.
 Issue 12:  Vertex 3.6 has a rounding problem. Total amount calculated at invoice and at sales update is different than the amount written to VTSREG by $.01. Example, NC GeoCode 34-021-0040, 7%, is a total of 4.5% state and 2.5% county. Here's what happens
 Issue 13:  Level Check on Sales Order Entry with Vertex 4.2.01
 Issue 14:  Invoice Reprint uses the current tax rate instead the original tax rate. 
 Issue 15:  Running A73 Cume 09 with the following SARS: 4503801, copy module I73VTN, and 5643427.
 Issue 16:  Vertex Not Calculating Taxes
 Issue 17: Vertex: Error 0267 (Item Invalid) at Sales Update (P42800)
 Issue 18: Error 057B when using Vertex to enter a sales order header that contains a Vertex GEOcode
 Issue 19:  Vertex Override with Customer Table not being recognized
 Issue 20: Vertex: No tax calculation for fractional quantities.  Using Vertex. When entering a fractional order quantity on a sales order, the system is not calculating any tax on the order
 Issue 21:  Vertex and Data Decimal Error on X4008C.  Running A7.3 C9 and upgraded from the 3.5 release of Vertex to the 4.0 release. Since upgrade, receiving a data decimal error on the X4008C
 Issue 22: P4311 Data Decimal Error on Statement BT005500 with Vertex
 Issue 23:  When you tried to create a Sales Tax Return from the Q Series menu in Vertex, you got error message CPF3137 (no authority to clear, initialize, or copy member). The error is at statement number 2400 on the VTS600CL2.
 Issue 24:  Vertex 3.6.02 positive tax amount on negative extended amount.
 Issue 25:  After upgrade to service pack 15, client has lost some records from the VTSREG file.
 Issue 26:  Oprion 7 on G731 doesn’t do anything.
 Issue 27:  Function key F15 to assign a GeoCode in customer master or supplier master doesn’t work.
 Issue 28:  The Vertex tax calculation is different from the World tax calculation
 Sales Order Entry Errors:
 Issue 1:  Error 057B - Vertex GeoCodes Inconsistent.
 Issue 2:  Error 0272 - Tax Area Invalid.
 Issue 3:  Sales Order is Incorrectly Taxed with Vertex Exemption TDM and exemption certificate number.
 Sales Update Errors:
 Issue 1:  Error 0267 - Item Number Invalid.
 Issue 2:  Error 012M - Taxable Amount Must Be Entered.
 Customer/Supplier Master Errors:
 Issue 1:  Error 4995 – warning - possible match.
 Issue 2:  Error 4999 – Tax explanation for Vertex Tax Area Invalid.
 Issue 3:  TDM exemption is not working:
 Issue 4:  The JDE system has the Calculate Sales Order Taxes Summary (P0021) flag turned on with Vertex L Series set up. The system does not appear to tax correctly at the order level with this set up.
References

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