My Oracle Support Banner

E1: 73: Tax Records Not Written to Vertex Register or Written to the Taxes Table (F0018) Rather Than the Vertex Tax Register (Doc ID 1448827.1)

Last updated on JULY 08, 2019

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version XE to 9.1 [Release XE to 9.1]
Information in this document applies to any platform.

Symptoms

Customers installing Vertex Sales Tax Q Series or upgrading to a new release of Vertex Sales Tax Q Series may not see records written to the Vertex Tax Register.  Customers have verified all setup for Vertex Sales Tax Q Series. Taxable transactions process and save successfully in JD Edwards EnterpriseOne.

Records containing Vertex GeoCodes unexpectedly write to the Taxes table (F0018) instead of the Vertex Tax Register when the Update Tax File processing option is active on the General Ledger Post (R09801) version. When Vertex is active, transactions taxed by Vertex do not write to F0018.

A review of the Vertex log shows that the RegFileInd value is 0 for transactions that should write to the Vertex Register.  The RegPreGen file is used to generate the Vertex Register. When the RegFileInd value is 0 transactions do not write to the RegPreGen file and therefore cannot write to the Vertex Register. 

Vertex log entries are written when EnterpriseOne communicates with Vertex.  For example, when reviewing the Vertex log for a sales invoice containing a Vertex GeoCode with tax explanation code S note the RegFileInd = 0.  Next, review the Vertex log for the same sales order processing through sales update and note the RegFileInd = 1.

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

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