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

Version management

Difference between version and

At line 57 added one line
At line 61 added one line
At line 70 added one line
At line 78 added one line
At line 78 changed 4 lines
- existing School District Code and Name will be compared to Symmetry School Code and Name
- School District Code Format is: SSSSSS - 6 digits School code
- 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
*existing School District Code and Name will be compared to Symmetry School Code and Name
*School District Code Format is: SSSSSS - 6 digits School code
*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
At line 83 changed 6 lines
IDMN - Define Municipalities (P2K_CM_MUNICIPALITIES)
- 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
;IDMN:
*Define Municipalities (P2K_CM_MUNICIPALITIES)
*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
At line 90 changed 6 lines
IDZR - Maintain ZIP Ranges (P2K_CM_ZIP_RANGES)
- 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
;IDZR:
*Maintain ZIP Ranges (P2K_CM_ZIP_RANGES)
*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
At line 97 changed 5 lines
IDTX - Define Tax Jurisdictions (P2K_CM_TAX_JURISDICTIONS)
- IDTX screen is used to store the combination of State, County, City, School, Municipality for Taxation
- IDTX may or may not store all permutations of Tax Jurisdictions, depending on the value selected for the Create Jurisdictions parameter
- 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
;IDTX:
*Define Tax Jurisdictions (P2K_CM_TAX_JURISDICTIONS)
*IDTX screen is used to store the combination of State, County, City, School, Municipality for Taxation
*IDTX may or may not store all permutations of Tax Jurisdictions, depending on the value selected for the Create Jurisdictions parameter
*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
At line 103 removed one line
At line 107 changed one line
- if user is converting from Vertex Taxation to Symmetry Taxation in the Payroll Module, user MUST run UDGNIS with ‘Vertex Conversion’ = ‘Y’ for the first time
*if user is converting from Vertex Taxation to Symmetry Taxation in the Payroll Module, user MUST run UDGNIS with ‘Vertex Conversion’ = ‘Y’ for the first time
At line 109 changed one line
- after UDGNIS is run with ‘Vertex Conversion’ = ‘Y’, all related Vertex Geographic Data Base Tables are converted, after the conversion, user MUST review UDGNIS exception report and manually fix any IDTX entries that cannot be converted
*after UDGNIS is run with ‘Vertex Conversion’ = ‘Y’, all related Vertex Geographic Data Base Tables are converted, after the conversion, user MUST review UDGNIS exception report and manually fix any IDTX entries that cannot be converted
At line 111 changed one line
- IDCN County Code format is changed from Vertex Format ‘XX-XXX-0000’ to Symmetry Format ‘XX-XXX’, the Alternate County Code will store the previous Vertex County Code for reference
*IDCN County Code format is changed from Vertex Format ‘XX-XXX-0000’ to Symmetry Format ‘XX-XXX’, the Alternate County Code will store the previous Vertex County Code for reference
At line 113 changed one line
- Vertex does not use IDCI City Code, no conversion is needed for City Codes
*Vertex does not use IDCI City Code, no conversion is needed for City Codes
At line 115 changed one line
- Vertex does not use IDMN Municipality Code, no conversion is needed for Municipality Codes
*Vertex does not use IDMN Municipality Code, no conversion is needed for Municipality Codes
At line 117 changed one line
- IDSD School Districts code are checked, if the Vertex School District has not been used in the System, this Vertex School District Code will be removed
*IDSD School Districts code are checked, if the Vertex School District has not been used in the System, this Vertex School District Code will be removed
At line 119 changed one line
- the Vertex School District Name is used to look for a close match from Symmetry and update the existing School District entry with the Symmetry School District Code and Name, along with the applicable County Code of the School District
*the Vertex School District Name is used to look for a close match from Symmetry and update the existing School District entry with the Symmetry School District Code and Name, along with the applicable County Code of the School District
At line 121 changed one line
- for Vertex IDTX Tax Jurisdiction entry that has not been used in the System, if the parameter Remove Jurisdiction was set to Yes, this IDTX entry will be removed. If the parameter was set to No, the tax jurisdiction will remain.
*for Vertex IDTX Tax Jurisdiction entry that has not been used in the System, if the parameter Remove Jurisdiction was set to Yes, this IDTX entry will be removed. If the parameter was set to No, the tax jurisdiction will remain.
At line 123 changed one line
- for Vertex IDTX Tax Jurisdiction entry that has been used in the System, this IDTX entry will try to be converted to Symmetry Format
*for Vertex IDTX Tax Jurisdiction entry that has been used in the System, this IDTX entry will try to be converted to Symmetry Format
At line 125 changed one line
- the IDTX Jurisdiction name is used to look for a close match from Symmetry
*the IDTX Jurisdiction name is used to look for a close match from Symmetry
At line 127 changed one line
- IDTX Vertex GEO Code format is changed from ‘XX-XXX-XXXX’ to Symmetry Format ‘AA-BBB-CCCCCCC’, the old Vertex GEO Code will be stored in the Vtx GEO Code for reference
*IDTX Vertex GEO Code format is changed from ‘XX-XXX-XXXX’ to Symmetry Format ‘AA-BBB-CCCCCCC’, the old Vertex GEO Code will be stored in the Vtx GEO Code for reference
At line 129 changed one line
- if Symmetry has an exact match of the Jurisdiction Name, then this IDTX entry will be updated with the new GNIS Code in format of ‘AA-BBB-CCCCCCC’, along with the County dcn_id and City dci_id
*if Symmetry has an exact match of the Jurisdiction Name, then this IDTX entry will be updated with the new GNIS Code in format of ‘AA-BBB-CCCCCCC’, along with the County dcn_id and City dci_id
At line 131 changed one line
- if Symmetry has no exact match for the Jurisdiction Name, then an exception message will be displayed, a Suggested County and City Name may be displayed, user MUST manually convert this IDTX entry after UDGNIS is run
*if Symmetry has no exact match for the Jurisdiction Name, then an exception message will be displayed, a Suggested County and City Name may be displayed, user MUST manually convert this IDTX entry after UDGNIS is run
At line 133 changed one line
- after Vertex GEO entries are cleaned up from IDTX, the user MUST review the UDGNIS Exception Report and manually fix the IDTX entries that cannot be converted
*after Vertex GEO entries are cleaned up from IDTX, the user MUST review the UDGNIS Exception Report and manually fix the IDTX entries that cannot be converted
At line 135 changed one line
- symmetry may not be able to convert a Vertex Jurisdiction if the name is not a valid town name as considered by the US Postal Service. Symmetry uses Zip Codes within their GNIS filter mechanism to determine the appropriate County, City, Feature id combination, if the town name is not valid then it will not be able to generate the correct combination.
*symmetry may not be able to convert a Vertex Jurisdiction if the name is not a valid town name as considered by the US Postal Service. Symmetry uses Zip Codes within their GNIS filter mechanism to determine the appropriate County, City, Feature id combination, if the town name is not valid then it will not be able to generate the correct combination.
At line 142 changed one line
1) In IDTX, copy the Vertex GEO Code into the Vtx Geo Code field. This is needed so that when UPCALC is run using Vertex, UPCALC knows to use the Vertex GEO Code rather than the GNIS code.
#In IDTX, copy the Vertex GEO Code into the Vtx Geo Code field. This is needed so that when UPCALC is run using Vertex, UPCALC knows to use the Vertex GEO Code rather than the GNIS code.
#Using the fields on the right hand side, select the correct County and City. This will create the appropriate GNIS Geo Code. The name defined in the Jurisdiction field will be replaced with the City name.
At line 144 removed 2 lines
2) Using the fields on the right hand side, select the correct County and City. This will create the appropriate GNIS Geo Code. The name defined in the Jurisdiction field will be replaced with the City name.
At line 154 added 2 lines
*if ‘Create File’ = Yes, each State will generate one .csv File to contain the Geographic Information for the State
*The following is a sample.csv file for Pennsylvania:
At line 157 added 3 lines
;STATE LEVEL:
*at State Level, the FIPS code is retrieved, e.g PA FIPS code is 42
*then all counties will be retrieved for this State, e.g. PA has 67 Counties
At line 151 removed 9 lines
- if ‘Create File’ = Yes, each State will generate one .csv File to contain the Geographic Information for the State
- The following is a sample.csv file for Pennsylvania:
STATE LEVEL
- at State Level, the FIPS code is retrieved, e.g PA FIPS code is 42
- then all counties will be retrieved for this State, e.g. PA has 67 Counties