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

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
2 26-Nov-2021 10:22 4 KB jmyers to previous
1 26-Nov-2021 10:22 2 KB jmyers to last

Page References

Incoming links Outgoing links
UDGNIS
UDGNIS

Version management

Difference between version and

At line 4 changed one line
!!Processing Information
!!UDGNIS - Load GNIS Codes
At line 6 changed one line
This function provides the ability to load Geo Codes and Zip Ranges that will facilitate the defaulting of the Jurisdiction by Zip Code. The process developed is based on the [Geographic Coding |GEO_CODE] System provided by [Vertex|VERTEX].
!UDGNIS - Selection Criteria
[US_Load_UDGNIS Locations_01.JPG]
%%warning IMPORTANT: UDGNIS is a high volume process to load all Counties, Cities, School, Municipalities, ZIP codes into [IDCN], [IDCI], [IDSD], [IDMN], [IDZR] for each state from Symmetry database. Each state may take from 1 to 10 minutes. To load all states, the process may take 2 to 3 hours, therefore, you may schedule UDGNIS to be run at night if necessary.%%
At line 8 changed 13 lines
!1. Loading the MATCHMST file
Before to execute this function you need to have loaded the [P2K_CM_LOADED_GEOCODES] table from the Vertex [MATCHMST] file. Currently this data is loaded using the [SQL Loader|SQLLDR] tool provided with the data base. A control file has been provided for this functionality in the RUNTIME directory: __[GEOCODER.CTL|UDTX/geocoder.ctl]__. To execute SQL Loader and populate this interim table with the data from Vertex, you would type in a command like:
{{{sqlldr p2k/pass@database control=GEOCODER}}}
You must ensure, of course, that the GEOCODER.CTL file is referencing the correct directory path and file name for the MATCHMST file. This will then load the over 70,000 GEO Code records into the table.
!2. Loading into the Data base Structures
Executing the UDTX function as noted below will take the vertex supplied data and populate (either inserting or updating) [P2K_CM_STATE_PROVINCES], [P2K_CM_TAX_JURISDICTIONS], [P2K_CM_COUNTIES] and [P2K_CM_ZIP_RANGES] tables. Note that any of GEO Code records that should be deleted will not be handled by this process. You should refer to your Vertex subscription documentation to delete these records (as applicable) manually through the [IDTX] screen.
|Country|This mandatory field allows you to enter the Country Code used to filter the list of states.
|State|You may use this field to enter list of states to be processed to load GNIS codes.\\ \\When setting up a new data base environment, if there is no State for lookup, UDGNIS will automatically load in all [IDSP] states when UDGNIS is run in non-Trial mode.\\ \\If the list of states are not entered, then all states will be processed.
|Load Symmetry GNIS|Optional, [Yes or No|X_YES_NO] lexicon available\\This is an optional field, with a default of <<No>>.\\If <<Yes>>, UDGNIS will load from the Symmetry database for the specified states.\\ \\If you have already loaded from the Symmetry database, then you can re-run UDGNIS to load in [IDTX] Tax Jurisdictions from IDCN, IDCI without re-loading from Symmetry database, therefore you can enter <<No>> to this prompt.
|Remove Jurisdictions|Optional, [Yes or No|X_YES_NO] lexicon available\\If Yes, UDGNIS will remove all tax jurisdictions for the specified states from IDTX that have not been used in the system.
|Create Jurisdictions|Optional, [Yes or No|X_YES_NO] lexicon available\\If <<Yes>>,UDGNIS will generate tax jurisdictions for the specified states on IDTX according to IDCI cities.\\ \\You have two options to create IDTX Tax Jurisdictions:\\1) manually enter on IDTX\\2) enter <<Yes>> to this prompt to load in all Tax Jurisdictions for IDCI Cities
|Trial|Optional, [Yes or No|X_YES_NO] lexicon available\\You may choose to run the report in a trial mode to see results <Yes> or in update mode <No>.\\In Non-Trial mode, IDSP, IDCN, IDCI, IDSD, IDMN, IDZR, IDTX are updated.
|Create File|Optional, [Yes or No|X_YES_NO] lexicon available\\This field is used to generate a .csv file with the applicable geographic information.
|Print Detail|Optional, [Yes or No|X_YES_NO] lexicon available\\This field is used to show detail dump of the geographic information\\If <<Yes>>, the report size may be quite large, therefore, you should select <<No>>, unless for Tracing.
|Vertex Conversion|Optional, [Yes or No|X_YES_NO] lexicon available\\This toggle is used to convert IDTX entries from Vertex Format to Symmetry Format\\The old Vertex IDTX GEO entries that are not being used will be removed\\The old Vertex IDTX GEO entries that are being used will be converted to Symmetry GNIS format
|Directory Name|if Create File = 'Y', user must enter a valid Directory Name for the .csv file
|File Name|if Create File = 'Y', user must enter a File Name for the .csv file
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.\\You should run with Exception Level except for Tracing\\In 'Utility Trace', the report may be quite large
|User Comments |Optional, Text \\This field holds the user-supplied comment which will appear in the header of all pages of the report. This is useful during testing phases to identify similar reports from each other.
This page (revision-2) was last changed on 26-Nov-2021 10:22 by jmyersTop