 |
1· |
When we get a flat file from college boards, before we put this file into Banner, would we be able to see what type of address errors it has, would we be able to de-dup it, and would we be able to re-format the flat file from college boards into a file layout we want? |
| |
Yes, there are several ways to do this. If you load it into the Banner staging table, then you can run the batch verification against that before the addresses are loaded into SPRADDR. From the staging table, you can also dedupe the records.
If they provide a flat text file, you could load into excel first and organize the columns appropriately. Perhaps we can discuss your current and "ideal" process and we can suggest some process improvements.
|
 |
2· |
Is there syntax checking? For instance if an address has "STREET", would CLEAN_Address change it to "ST"? |
| |
Yes, we call this standardization, which matches the USPS® CASS™ standardization guidelines. We do have a parameter in the customization package to use the full name for street suffixes instead of the abbreviation.
|
 |
3· |
Can a rule be set-up to check only certain types of addresses? We have MA, mailing address; BK, bulk mailing, FM, formal address. Users may or may not want all of these different address types checked. |
| |
The address types can be configured ON or OFF for address verification so you can choose what to do with each address. You can even bypass certain address types completely, such as Campus Addresses. This is done in the customization package where you have pre- and post- verification user exit routines to fine tune your business rules.
|
 |
4· |
When CLEAN_Address finds a 'bad' address, does it update the address in the spraddr or is there a report which lists all the bad addresses and then the user cleans them up? |
| |
Addresses that are not deliverable or able to be coded remain the same without changes. The address error code and verification date is stored on the record so you can easily report off of it. We provide pre-defined reports for this against the SPRADDR table.
|
 |
5· |
We have been on Banner for a long time and the university has never done anything like this; so we would really like to run this in batch processing. Any ideas of how long something like this would run for the first time? |
| |
The batch engine processes addresses around 500K-700K per hour, so it would take about 45 minutes for 320K addresses.
|
 |
6· |
Can you break it out and do several runs based upon last names? i.e. run a batch jobs for last names which fall in A-C and then another run for last names which fall in D-F. |
| |
We don't have parameters for last names, however you could customize the batch update for this parameter, although the processing time really isn't that long so maybe that's not an issue.
|
 |
7· |
Is it possible to run a 'test' on our development system just to see how many bad addresses we have? For example of the 319,000 active records we have, 20,000 have a bad address. Is this possible in non-update and update mode? |
| |
Yes, this is already included in the batch procedure. Setting the fb_update parameter to 'FALSE' will just verify and display summary results in SQL Plus with DBMS output turned on. Don't be surprised if you see between 15-22% of addresses with error (45K-60K addresses). This is what we typically see.
|
 |
8· |
Some of our ZIP Codes™ are 5 digits and some are 9 digits. Would there be a problem if the verification was set to 5? |
| |
The current default is to update the ZIP Code™ field with the full 9 digit ZIP + 4®. There is an option in the user exit package to force only the 5-digit ZIP Code® to be stored.
|
 |
9· |
When you run the CLEAN_Address process, does it make the old address inactive and put in the new record? |
| |
The current default is to update the existing record in batch mode, however this again is another great enhancement we will put in the interface. Since the address isn't really "changing", but being corrected, you may not want to "double-up" most of the addresses, but it can definitely be a configurable parameter.
|
 |
10· |
Can you set the number of address lines to 2 instead of checking 3 lines? |
| |
Yes, this would be easy to change in the script. However, if only 2 lines are specified on input, only 2 lines will be returned as well.
|
 |