KampData Knowledge Base

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Tax Schedule ID with astrisk ======

**NOTE:** The asterisk in the Tax Schedule ID proved to be confusing and its use has been discontinued as of [[dynamiczip:install:mods:release:build74:build74|Build 74]].

Upgrading from  DynamicZip build 71 or older to [[dynamiczip:install:mods:release:build72:build72|Build 72]] or [[dynamiczip:install:mods:release:build73:build73|Build 73]] includes a modification in the tax schedule ID format. The addition of an asterisk in position 10 is used to identify the default city and county combination when more than one city and county exists in a ZIP code. Please read the information on this page to help ensure a smooth transition to the new  [[dynamiczip:glossary:zip_code_tax_schedule_id_format|Zip Code Tax Schedule ID Format]]. 

**IMPORTANT: **After completing the [[dynamiczip:faq:DynamicZip Installation Reinstallation Faq|DynamicZip installation]] you must complete the [[dynamiczip:faq:rate_and_boundary_import_checklist|Import Rate & Boundary Database Checklist]] to ensure that the new tax schedule IDs are created and your customer address records are updated. Not completing the Import Rate & Boundary Database Checklist after upgrading can result in [[dynamiczip:faq:Schedule Assigned To New Sales Faq|zero tax on new sales transactions]].

  * Please see the complete [[dynamiczip:faq:Upgrade Instructions]]. 

===== Contract Administration =====

If you are using Contract Administration, then the new tax schedules will need to be rolled out to your existing contracts. Failing to do so can result in invoices created out of Contract Administration having incorrect or zero tax amounts. Please see the following instructions.

  - You must complete the Import Rate & Boundary Database Checklist to update your tax schedules and customers before you can roll out the new tax schedules out to the contracts. **NOTE: **The two SQL queries below should be run against __both__ the SVC00600 table and the SVC00601 table.
  - The following SQL statement can help you find the contracts that have a tax schedule ID mismatch with the customer address cards.<code>SELECT SVC00600.CONTNBR, SVC00600.CUSTNMBR 
,SVC00600.TAXSCHID AS 'Contract Tax ID'
,RM00102.TAXSCHID AS 'Customer Tax ID'
FROM SVC00600 AS SVC00600
JOIN RM00102 AS RM00102
ON SVC00600.CUSTNMBR = RM00102.CUSTNMBRAND 
AND SVC00600.ADRSCODE = RM00102.ADRSCODE
WHERE SVC00600.TAXSCHID != RM00102.TAXSCHID 
AND SVC00600.CONSTS = 2</code>
  - Run the next SQL statement to update Contract Administration with the new tax schedules. <code>UPDATE SVC00600 set SVC00600.TAXSCHID = RM00102.TAXSCHID
FROM SVC00600 SVC00600
JOIN RM00102 RM00102
ON SVC00600.CUSTNMBR = RM00102.CUSTNMBR
AND SVC00600.ADRSCODE = RM00102.ADRSCODE
WHERE SVC00600.TAXSCHID != RM00102.TAXSCHID
AND SVC00600.CONSTS = 2</code>

----

[[dynamiczip:faq:new_install_instructions|Installation & Setup]] \\
[[dynamiczip:install:mods:modifications|Modifications]] \\
[[dynamiczip:faq:Frequently Asked Questions]] 

\\