This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
37 26-Nov-2021 10:22 10 KB rforbes to previous
36 26-Nov-2021 10:22 10 KB rforbes to previous | to last
35 26-Nov-2021 10:22 11 KB rforbes to previous | to last
34 26-Nov-2021 10:22 11 KB rforbes to previous | to last
33 26-Nov-2021 10:22 12 KB rforbes to previous | to last
32 26-Nov-2021 10:22 16 KB jescott to previous | to last
31 26-Nov-2021 10:22 15 KB jmyers to previous | to last
30 26-Nov-2021 10:22 15 KB jmyers to previous | to last
29 26-Nov-2021 10:22 15 KB jmyers to previous | to last
28 26-Nov-2021 10:22 15 KB jmyers to previous | to last
27 26-Nov-2021 10:22 15 KB jmyers to previous | to last
26 26-Nov-2021 10:22 15 KB jmyers to previous | to last
25 26-Nov-2021 10:22 15 KB jmyers to previous | to last
24 26-Nov-2021 10:22 15 KB jmyers to previous | to last
23 26-Nov-2021 10:22 15 KB jmyers to previous | to last
22 26-Nov-2021 10:22 15 KB jmyers to previous | to last
21 26-Nov-2021 10:22 15 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
US Load GNIS Locations
US Load GNIS Locations

Version management

Difference between version and

At line 35 changed one line
*The file name will be suffixed with the State code; you may attach the mex id of the run to the file name.\\e.g. File Name: cathy_gnis_mex\\- ‘mex’ will be replaced with the execution ID, then suffix with the State code
*The file name will be suffixed with the State code; you may attach the mex id of the run to the file name.\\e.g. File Name: cathy_gnis_mex 'mex' will be replaced with the execution ID, then suffix with the State code
At line 37 changed 2 lines
*If the ‘Print Detail’ toggle is set to <<Yes>>, UDGNIS will list the detail entries that are processed for each level: Country, States, Counties, Cities, Schools, Municipalities, Tax Jurisdictions.
*If you have converted from Vertex Taxation to Symmetry Taxation for the Payroll Module, you MUST run UDGNIS with the ‘Vertex Conversion’ toggle set to <<Yes>> for the first time. Please read [Vertex Conversion|US Load GNIS Locations#section-US+Load+GNIS+Locations-VertexConversion] below.
*If the 'Print Detail' toggle is set to <<Yes>>, UDGNIS will list the detail entries that are processed for each level: Country, States, Counties, Cities, Schools, Municipalities, Tax Jurisdictions.
*If you have converted from Vertex Taxation to Symmetry Taxation for the Payroll Module, you MUST run UDGNIS with the 'Vertex Conversion' toggle set to <<Yes>> for the first time. Please read [Vertex Conversion|US Load GNIS Locations#section-US+Load+GNIS+Locations-VertexConversion] below.
At line 56 changed one line
*‘ISO Alpha 2’ and ‘ISO Alpha 3’ will be updated if these are not set up
*'ISO Alpha 2' and 'ISO Alpha 3' will be updated if these are not set up
At line 65 changed one line
*existing County Code and County Name will be compared to Symmetry County Code and County Name
*Existing County Code and County Name will be compared to Symmetry County Code and County Name
At line 75 changed 3 lines
*City Code Format is: CCCCCCC - 7 digits City code
*For each county from IDCN, UDGNIS retrieves all City Codes that are for each county
*This helps the user to enter the correct combination of City with the related County for Tax calculation
*City Code format is: CCCCCCC - 7 digits City code
*For each county from IDCN, UDGNIS retrieves all City Codes for that county
*This helps you enter the correct combination of City with the related County for tax calculation
At line 82 changed one line
*existing School District Code and Name will be compared to Symmetry School Code and Name
*Existing School District Code and Name will be compared to Symmetry School Code and Name
At line 84 changed 2 lines
*for Each County from IDCN, UDGNIS retrieves all School District Codes that are for each County
*this helps the user to enter the correct combination of School with the related County for Tax calculation
*For each County from IDCN, UDGNIS retrieves all School District Codes for that county
*This helps you enter the correct combination of School with the related County for tax calculation
At line 89 changed 5 lines
*new Municipalities will be loaded
*existing Municipality Code and Name will be compared to Symmetry Municipality Code and Name
*Municipality Code Format is: MMMMMMM - 7 digits Municipality code
*for each County from IDCN, UDGNIS retrieves all Municipality Codes that are for each County
*this helps the user to enter the correct combination of Municipality with the related County
*New Municipalities will be loaded
*Existing Municipality Code and Name will be compared to Symmetry Municipality Code and Name
*Municipality Code Format is:MMMMMMM - 7 digits Municipality code
*For each County from IDCN, UDGNIS retrieves all Municipality Codes for that county
*This helps you enter the correct combination of Municipality with the related County
At line 97 changed 5 lines
*new ZIP codes will be loaded
*existing ZIP Code and Description will be compared to Symmetry ZIP Code and City Name
*for Each County from IDCN, UDGNIS retrieves all ZIP Codes that are for each County
*the applicable City code within each County are provided for each ZIP code
*this helps the user to enter the correct combination of ZIP code with the related County for Tax calculation
*New ZIP codes will be loaded
*Existing ZIP Code and Description will be compared to Symmetry ZIP Code and City Name
*For each County from IDCN, UDGNIS retrieves all ZIP Codes for that county
*The applicable City code within each County are provided for each ZIP code
*This helps you enter the correct combination of ZIP code with the related County for Tax calculation
At line 107 changed 2 lines
*If the UDGNIS was run with the parameter Create Jurisdictions = Yes, the system will load in cities into IDTX creating Tax Jurisdictions for all cities for the states selected in the UDGNIS. The user would then have to manually enter Municipality and School District for Pennsylvania and Ohio.
*If UDGNIS was run with the parameter Create Jurisdictions = No, the user will need to enter the IDTX entry using the ‘Tax Jurisdiction Editor Dialog Box’ provided by the system on the applicable screen
*If the UDGNIS was run with the Create Jurisdictions toggle set to <<Yes>>, the system will load cities into IDTX, creating Tax Jurisdictions for all cities within the states selected in the UDGNIS. You then have to manually enter Municipality and School District for Pennsylvania and Ohio.
*If UDGNIS was run with the Create Jurisdictions toggle set to <<No>>, you will need to enter the IDTX entry using the 'Tax Jurisdiction Editor Dialog Box' provided by the system on the applicable screen.
At line 183 removed 4 lines
At line 189 changed 3 lines
- During Vertex Conversion, if the IDTX Vertex GEO Code entries cannot find an exact match from Symmetry, a WARNING Message will be displayed
- user MUST manually go into IDTX screen to modify the Vertex GEO Code with Description to the Symmetry Format
- e.g the following is an example of UDGNIS Message Displays after Vertex Conversion:
*During Vertex Conversion, if the IDTX Vertex GEO Code entries cannot find an exact match from Symmetry, a WARNING Message will be displayed
*user MUST manually go into IDTX screen to modify the Vertex GEO Code with Description to the Symmetry Format
*e.g the following is an example of UDGNIS Message Displays after Vertex Conversion:
At line 197 changed 5 lines
- user should review the UDGNIS Messages and the Output File for the Vertex IDTX GEO Codes displayed
- if there is an exact match with the Jurisdiction Description, IDTX will be converted
- if there is no match, a partial search will be performed to help the user to manually enter on IDTX screen
- if there is no partial match, the user must manually convert the Vertex GEO Code on IDTX screen
- UDGNIS will remove the unused old Vertex IDTX entries, after UDGNIS is run, user MUST manually convert the left over IDTX Vertex entries because these entries are being used in the system by Payroll
*user should review the UDGNIS Messages and the Output File for the Vertex IDTX GEO Codes displayed
*if there is an exact match with the Jurisdiction Description, IDTX will be converted
*if there is no match, a partial search will be performed to help the user to manually enter on IDTX screen
*if there is no partial match, the user must manually convert the Vertex GEO Code on IDTX screen
*UDGNIS will remove the unused old Vertex IDTX entries, after UDGNIS is run, user MUST manually convert the left over IDTX Vertex entries because these entries are being used in the system by Payroll
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop