Results 1 to 4 of 4

Thread: Vertex Q series version 8 - Anyone using it?

  1. #1

    Vertex Q series version 8 - Anyone using it?

    Hello All,

    There is a regulatory change coming Dec 1 in Colorado that requires all transactions to look like they are in state so Sales tax is collected, not Use tax. We are currently on version 5. Vertex opted to make the necessary change only in version 8 which came out earlier this year. Oracle has not certified version 8 and doesn't have firm plans to do so. In order to use version 5, we need JDE to send the Ship From geocode and Order Acceptance geocode not from Ohio where we are, but as a Colorado geocode. It could be the same as the Ship To geocode or just any geocode from CO.

    I opened a SR with Oracle and they have not yet provided a solution. We are hearing that California and, potentially, other states are going to follow this change.

    So, it seems like the options are Oracle certifying it, providing a POC/paper fix or we run version 8 uncertified with Oracle Support.

    Any thoughts or recommendations you have would be greatly appreciated.

    Jer
    Current: E1 9.2, TR 9.2.2.5, Win2012 R2, SQL Server 2014 R2, Weblogic, OneView, Embedded BIP
    Upgrade: E1 9.1, TR 9.1.4.4, Win2008 R2, SQL Server 2008 R2, WebLogic, OneView, Embedded BIP
    Original: E1 8.0, SP 24.1.2, Win2003, SQL Server 2005 SP3, all fat client

  2. #2
    Senior Member
    Join Date
    Mar 2004
    Location
    Fort Worth, Texas
    Posts
    1,559
    I would think Oracle would provide a solution at some point. Having said that our organization has had some tax situations that were not handled correctly by out of the box JDE/Vertex and we modified the tax calculator (mainly X00TAX). If you have someone that knows jde/tax/vertex and a competent JDE/C developer the mods can often be pretty trivial. In out situation we had to do something very similar to what you describe but for us it was based on Order Type (DCTO) which vertex and out of the box JDE configuration didn't really handle.
    Brian Oster
    Application Development Manager
    E1: 9.0 (TR9.1.5.1) / 9.2 (TR9.2.2.2)
    JAS/BSSV: Weblogic 12.1.2 / Weblogic 12.2
    ES: Win2008 / Win2016
    DB: MSSQL 2014 / 2016
    WebDev Client: Win7Pro / Win10Pro

  3. #3
    Hello Brian,

    Thank you for the reply. We have a little bit of C skills and a little bit of Vertex knowledge. That is to say, we don't have anyone that does C work regularly or in depth and we don't have deep experience working with Vertex business functions. We do understand the architecture and how geocodes work.

    My hope was that even if Oracle won't provide a formal POC, I can push for a list of objects/integrations where the geocodes are sent to TDM and we would take a crack at a fix. Should be simple, I think. If ship to geocode is a 21 (whatever CO state code is) set ship from and order acceptance geocodes = shipto geocode

    However, your post gave me another option - hire a C and Vertex guru to make a fix for us.

    Jer
    Last edited by JMast; 08-16-2019 at 07:27 AM.
    Current: E1 9.2, TR 9.2.2.5, Win2012 R2, SQL Server 2014 R2, Weblogic, OneView, Embedded BIP
    Upgrade: E1 9.1, TR 9.1.4.4, Win2008 R2, SQL Server 2008 R2, WebLogic, OneView, Embedded BIP
    Original: E1 8.0, SP 24.1.2, Win2003, SQL Server 2005 SP3, all fat client

  4. #4
    Senior Member
    Join Date
    Mar 2004
    Location
    Fort Worth, Texas
    Posts
    1,559
    Well, if you have a little C experience that might be enough. X00TAX is where the vertex calls are made and you might be able to figure out how to change what is passed to vertex w/o too much trouble.
    Brian Oster
    Application Development Manager
    E1: 9.0 (TR9.1.5.1) / 9.2 (TR9.2.2.2)
    JAS/BSSV: Weblogic 12.1.2 / Weblogic 12.2
    ES: Win2008 / Win2016
    DB: MSSQL 2014 / 2016
    WebDev Client: Win7Pro / Win10Pro

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.