Return
to Banner Documentation Library
![]() |
|
Academic/Instructional Support | Administrative Technology Service | Help Desk | Media Center |
|
On Site Support | Technical Service | User Support Services | CCSU Homepage |
Shared
Data Entry Standards
for
Banner
(updated
4/30/02)
Table of Contents
Banner Coordinating Team Members
Document Review and Maintenance
Examples of identification numbers:
Preferred First Name Standards
Acceptable Prefixes & Prefix Abbreviations:
Acceptable Suffix Abbreviations:
Non-Person Name / Vendor Name Standards
Use of Banner Address Hierarchy
Examples of Address hierarchies:
Address Types and Custodianship
Address Unit Designator Standards
Directional Designators Standards
City, State, Zip Code and Nation Standards
Social Security Number Standard
Confidential Information Indicator
The
Banner Coordinating Team developed this manual to ensure consistency and data
integrity. All Banner Systems
Alumni/Development, Finance, Financial Aid, Human Resources, and Student share
data. The standards in this manual
address the data entry standards for that shared data. A record at the University could belong
to more than one system. For
example, the record of a person who received an undergraduate degree, who is
currently pursuing a graduate degree, and is an employee of the University would
have general person data shared by three different systems: Alumni/Development,
Student and Human Resources.
These
standards will help to reduce the creation of duplicate entries, increase valid
addresses for mailings, and create a better view of the
University.
This
manual is a standards policy reference guide; it is not meant to be a training
guide for Banner. It was created
for use by all departments and it is not Banner form specific.
|
Representative |
Department |
| Lynn Bonesio-Peterson | Registrars |
| Sally Mele | Alumni/Development |
| Richard Bishop | Financial Aid |
| Lori Paradise | Personnel |
| Lori Padua | Fiscal Affairs |
| Chris Simcik | Information Technology Services |
| Brian Wood | Accounting |
| Dawn Klimkiewicz | Information Technology Services |
| Deborah Hunt | Information Technology Services |
| Rob Rak | Information Technology Services |
| Stanley Styrczula | Information Technology Services |
| Ruben Mercado | Information Technology Services |
| Robert Hayes | Information Technology Services |
| Robert Yanckello | Information Technology Services |
The
policies and standards for Data Entry in Banner will be reviewed by the Banner
Coordinating Team as required by Banner System Upgrades or sufficient changes to
Banner validation tables or Banner processes.
The
Banner Coordinating Team meets regularly.
If you have any questions or concerns regarding these standards or how
these standards might affect existing jobs, workload or data entry, please
report them to your Banner departmental representative as soon as possible. These issues, especially those that
affect multiple departments, will be brought to the Banner Coordinating Team for
immediate discussion.
Initial
distribution of this document will be made to all individuals who currently have
access to Banner. The document will
be given to new Banner users at the same time logon Ids and passwords are
issued. The document will also be
maintained electronically.
Coordinating data entry standards training for persons granted modify
access to Banner is the responsibility of each department
manager.
Banner Users are reminded of their legal obligations to data access and disclosure.
·
Users
have the obligation to be aware of federal regulations (FERPA, etc.), State of
Connecticut regulations, and Central Connecticut State Universitys policies
applicable to data under the jurisdiction of their
offices.
·
Certain
information is the responsibility of specific or custodial departments. Disclosure of information is restricted
to these custodians or their representatives. Contact a custodian or direct
representative (for example: the Registrar or a direct representative of the
Registrar) prior to disclosure of information.
· Data is private and shall be used only for the legitimate business of Central Connecticut State University.
· The pound sign (#) is not to be used in any field with the exception of purchase order text.
·
All
data entered into a data field should be typed using title-case (mixed case)
format (uppercase and lowercase letters) using standard capitalization
rules.
·
Data
appears in the same format when printed as it was entered.
·
Before
creating or modifying any records that contain shared data, you must conduct an
ID and Name search. Please refer to
your departments procedural manual for detailed directions. All departments must conduct a thorough
search to prevent entering duplicate records. (See
Banner
Search Procedures Manual.)
·
Refer
to this policy before making a change to any shared data. The following conventions govern which
office can make changes to shared data:
|
If
the person is
|
then
.makes
the change. |
|
An
Employee other than a Student Employee |
Personnel
/ Payroll |
|
An
Employment Applicant and not a Student |
Personnel
/ Payroll |
|
A
Student |
Registrars
Office |
|
A
Student Applicant |
Admissions
Office |
|
A
Vendor |
Purchasing |
|
An
Alumnus / Donor |
Alumni
/ Development |
|
A
Corporation or Foundation |
Alumni
/ Development |
·
The
Banner System uses an identification number consisting of a unique nine-digit
number to identify each Person and each Non-Person (e.g. business, corporation,
vendor).
·
Dashes
are not permitted in the identification number.
·
The
Social Security Number (SSN) is the primary Banner identification number for a
Person. If the social security number is not available, a system-generated
number will be provided. A generated number starting with the @ symbol will be
used.
·
The
Federal Employee Identification Number (FEIN) is the primary identification
number for a Non-Person.
|
Social
Security Number (SSN) |
123456789 |
|
BANNER
System Generated Identification Number |
@00067427 |
|
Federal
Employee Identification Number (FEIN) |
740998765 |
·
Before
you create a new record in Banner for a person, conduct an ID and Name search to
make sure the person does not exist on the Banner Database. (See
Banner
Search Procedures Manual.)
·
Enter
the last, first and middle names exactly as the person has indicated. If given the full middle name, do not
change it to an initial.
· 15 characters are allowed for first names and 60 characters are allowed for last names. Contact a member of the Banner User Committee associated with your department if names contain more characters than the field allows.
·
Case. Always use normal title-case format
(uppercase/lowercase letters), and follow standard capitalization rules when
entering names.
|
Examples: |
Stanley |
|
|
Van
der Vaart |
|
|
al-Hassan |
|
|
duBois |
·
Punctuation. The following punctuation is
permitted in the name field:
|
Apostrophes |
OLeary |
|
|
Tinas
Catering |
|
Hyphens |
Cooper-Smith |
|
|
Ann-Marie |
|
Periods |
St.
John |
|
|
C. |
|
Spaces |
Mc
Donald |
|
|
Bobby
Joe |
|
|
M.
Ann |
·
The
following punctuation is not
permitted in the name field:
commas,
the
pound sign (#),
titles,
prefixes,
suffixes.
·
In
those cases where a single character is designated as the first name, enter the
single character (followed by a period) in the first name
field.
·
When
a person prefers to be addressed by a name other than her/his legal first name,
enter that name in the Preferred First Name field. (Follow the data entry
standards established for the First and Last Name fields.)
·
If
the person has not indicated a preferred first name, leave the field
blank.
·
If
given the full middle name, use the entire full middle name, do not change it to
an initial.
·
Entering
a middle initial (followed by a period) is acceptable, if only provided the
middle initial.
·
If
no middle name or middle initial exists, leave the field blank.
·
Always
use normal title-case format (uppercase/lowercase letters), and follow standard
capitalization rules when entering data.
·
Prefixes
are entered in the Identification Form in the prefix field. Do not enter prefixes in the name
fields.
·
Always
use normal title-case format (uppercase/lowercase letters), and follow standard
capitalization rules when entering a prefix.
·
Punctuation
is required in prefixes.
·
If
no prefix is provided, the default entry format is Mr. (male) or Ms.
(female).
·
Use
Miss or Mrs. only when requested, otherwise use Ms. as the
standard.
|
Abbreviation |
Description |
|
Atty. |
Attorney |
|
Br. |
Brother
(Religious) |
|
Dr. |
Doctor |
|
Fr. |
Father
(Religious) |
|
Hon. |
Honorable
elected official |
|
Miss |
Female
Single Status |
|
Ms. |
Female
Single or Married Status |
|
Mr. |
Mister |
|
Mrs. |
Female
Married Status |
|
Rabbi |
Rabbi |
|
Rep. |
Representative |
|
Rev. |
Reverend |
|
Sen. |
Senator |
|
Sr. |
Sister
(Religious) |
·
If
a prefix is not found in the list above, contact a member of the Banner User
Committee associated with your department.
·
A
prefix should never convey the same meaning as suffix. Examples:
|
Incorrect
Usage
of a prefix: |
Correct
Usage of a prefix: |
|
Dr.
Robert Yanckello Ph.D. |
Dr.
Robert Yanckello |
|
Atty.
Mary Wood Esq. |
Atty.
Mary Wood |
·
Suffixes
are entered in the Identification Form in the suffix field. Do not enter suffixes in the name
fields.
·
Enter
a suffix only when identified by the individual.
·
Always
use normal title-case format (uppercase/lowercase letters), and follow standard
capitalization rules when entering a suffix.
·
Punctuation
is required in suffixes.
·
If
no suffix is provided the field remains blank.
|
II |
The
Second |
|
III |
The
Third |
|
CPA |
Certified
Public Accountant |
|
Esq. |
Attorney |
|
JD |
Jurist
Doctor |
|
Jr. |
Junior |
|
LL.D. |
Doctor
of Laws |
|
MD |
Doctor
of Medicine |
|
MSW |
Certified
Social Worker |
|
Ph.D. |
Doctor
of Philosophy |
|
RN |
Registered
Nurse |
|
Sr. |
Senior |
·
If
a suffix is not found in the list above, contact a member of the Banner User
Committee associated with your department.
·
A
suffix should never convey the same meaning as prefix. Examples:
|
Incorrect
Usage of a suffix: |
Correct
Usage
of a suffix: |
|
Dr.
Robert Yanckello Ph.D. |
Mr. Robert
Yanckello Ph. D. |
|
Atty.
Mary Wood Esq. |
Ms. Mary
Wood Esq. |
·
Before
you create a new record in Banner for a non-person (e.g. business, corporation,
etc.), conduct an ID and Name search to make sure the organization does not
exist on the Banner Database. (See
Banner
Search Procedures Manual.)
·
Enter
the legal name, using standard capitalization rules. All information is to be
entered using title-case format (uppercase/lowercase letters).
·
The
use of all uppercase or all lowercase letters is appropriate if the business
name legally appears as such.
·
Acronyms
will not be used unless the acronym is part of the legal name of the
organization.
Examples:
IBM
CompUSA
·
Creating
an alternate name will accommodate the need for searching on two names. Example:
SNET is the corporation name and Southern New England Telephone is the alias, or
previous name.
·
Ampersand
(&) is used only when part of the legal name. Use and in all other
cases.
Examples: Baltimore & Ohio
Railroad
J. P. Morgan & Co. Inc.
·
Abbreviations
are allowed for Co., Corp., LTD. or Inc. when used after the name of a corporate
entity. Other forms of
abbreviations may be used for corporate entity when space is limited. Contact a member of the Banner
User Committee associated with your department before abbreviating any name.
·
The
legal name field is not used at Central Connecticut State
University.
·
Banner
permits multiple addresses to be entered for a person or non-person. The use of each address type is strictly
defined. Because all functional
areas share name and address data, custodial relationships are in
place.
|
Student
billing |
1BI,
2MA |
|
Grade
reports |
1MA |
|
Financial
Aid letters |
1MA |
|
Recruiting
admissions letters |
1PA,
2MA |
|
Paychecks
and W2s |
1MA |
|
Student
schedules |
1CA,
2MA |
|
If
the code is
|
|
|
then
.makes
the change. |
|
Code |
Description |
Definition
of Use |
Custodian |
|
BI |
Billing |
Billing
address of student if different from MA or PA |
Registrar |
|
BU |
Business |
Business
address of individuals employer, including department and building of
CCSU employees |
Alumni/HR |
|
B2 |
Second
Business |
Business
address of individuals second employer |
Alumni |
|
CA |
Campus
student |
|
Registrar |
|
MA |
Mailing
|
Mailing
address of individual, company or organization |
All |
|
MG |
Matching
Gift Address |
Companys
matching gift address |
Alumni |
|
PA |
Parent/Guardian |
Mailing
address of parent/guardian if different from MA |
Admissions/Alumni |
|
SB |
Spouse
Business |
Business
address of constituent spouse |
Alumni |
|
SE |
Seasonal |
Alumni/donors
who maintain two homes (i.e. snowbirds) |
Alumni |
|
VA |
Vendor
Advance |
Vendor
mailing address for travel advances |
Finance |
|
VE |
Vendor
Enclosure |
Vendor
mailing address for checks that must be accompanied by a separate
enclosure |
Finance |
|
VN |
Vendor
|
Vendor
(person or non-person) mailing address (Finance
only) |
Finance |
|
VS |
Vendor
Student |
|
Finance |
|
XX |
|
Reserved
for TGRFEED Use Only |
Registrar |
· All information is to be entered using title-case format (uppercase/lowercase letters). Never use all uppercase or all lowercase letters. Enter the address using standard capitalization rules.
·
Lines
1 and 2 can only be 30 characters long.
·
Use
only the first two lines for street
address information. Line 1 should
contain the physical street address and Line 2 should contain PO Box, Apartment
Number, Suite Number, RFD Number, etc.
This item is to be used with all address types except BU and VN.
·
Do
NOT use the third line of address information, since it may cause a conflict
with Banner label/letter generation.
Example: 100
Major Street
PO Box 200 Morgan Station
·
All
Street Designators (Road, Street, Avenue, Boulevard, Highway, etc.) and
Secondary Unit Designators (Apartment, Building, Department, etc.) must be
spelled out.
Examples:
|
Incorrect |
Correct |
|
1615
Stanley St |
1615
Stanley Street |
|
94
Hollywood Blvd |
94
Hollywood Boulevard |
·
Hyphens
and slashes may be used when needed for clarity or designated
fractions.
|
Examples: |
289-01
Montgomery Avenue |
|
|
Mid-Island
Plaza |
|
|
101
1/2 Main Street |
·
Commas,
the Pound Sign (#) and double quotes are never used.
Examples:
|
Incorrect |
Correct |
|
392
Main Street, Apartment 6 |
392
Main Street Apartment
6 |
|
R.R.
#105 |
RR
105 |
|
P.O.
Box #8 |
PO
Box 8 |
|
In
Care Of |
c/o |
·
In
Care Of should be entered as (c/o) in lower case. Do not use the percent sign (%) or spell
out (in care of).
·
If
the name of a street is a number, enter the street address as it appears.
Examples:
If
the address Sixth Street appears on an application or invoice, enter Sixth
Street.
If
the address 121st Street appears on an application or invoice, enter 121st
Street.
·
Address
Unit Designators should be spelled out if room permits.
·
Punctuation
is not used with Address Unit Designators.
|
Incorrect |
Correct |
|
Kennedy
Bldg. |
Kennedy
Building |
|
Apt.
42 |
Apartment
42 |
·
Directional
Designators should be spelled out if room permits.
·
Punctuation
is not used with Directional Designators.
|
Directional
Designation |
Abbreviation |
|
North |
N |
|
South |
S |
|
East |
E |
|
West |
W |
|
Northeast |
NE |
|
Northwest |
NW |
|
Southeast |
SE |
|
Southwest |
SW |
·
Do
not enter USA or US for any address within the United States. Leaving the field blank will result in
the nation being USA. Inputting USA as a nation will cause the nation to print
on every letter/label and will cause a problem for the Post
Office.
·
U.S.
Territories and Oversea Military Bases are included within the Zip Code
Table.
·
All
information is to be entered using title-case format (uppercase/lowercase
letters). Never use all
uppercase or all lowercase letters.
Enter the address using the standard capitalization rules.
·
Abbreviations
of city names are permitted if the full city name does not fit due to space
restrictions. Contact a member of
the Banner User committee associated with your department before abbreviating a
city name.
·
Canadian
Province and Territory abbreviations are to be entered into the State
field. Use the LIST
function.
·
This
field is required for all non-USA addresses. Use the LIST function for the
appropriate code.
·
Central
Connecticut State University will not be using the County
Code.
Examples:
Mrs. Helen K. Saunders
1010 Clear Street
Ottawa ON K1A OB1
Canada
Mr. Thomas Clark
117 Russell Drive
London WIP7HQ
England
·
The
three-digit area code must be entered for all phone
numbers.
·
Enter
the seven-digit number without inserting a hyphen.
|
Examples: |
2837300 |
|
|
5743861 |
|
|
8675309 |
·
If
an extension number is provided, enter only the digits of the extension. Do not enter EXT or X into the extension
field.
|
Examples: |
7300 |
|
|
18 |
|
|
342 |
·
For
unlisted phone numbers check off the confidential indicator on the General
Person Form.
|
If
the code is
|
|
Then
.makes
the change. |
|
Code |
Description |
Custodian |
|
BI
|
Student
Billing |
Registrar |
|
BU |
Business
Address of individual |
Alumni/HR |
|
B2 |
Second
Business Address of individual |
Alumni |
|
CA |
Campus
student |
Registrar |
|
CE |
Cellular
Address |
All |
|
EM |
Emergency
Contact |
Registrar |
|
MA |
Mailing
Address of individual or company |
All |
|
MG |
Matching
Gift Address |
Alumni |
|
PA |
Parent
Address |
Admissions/Alumni |
|
PG |
Pager |
All |
|
SB |
Spouse
Business |
Alumni |
|
SE |
Seasonal |
Alumni |
|
VA |
Vendor
Advance |
Finance |
|
VE |
Vendor
Enclosure |
Finance |
| VN | Vendor | Finance |
| VS | Vendor Student | Finance (No longer used.) |
· Future dating is "NOT" allowed in Banner.
·
There
are various methods of data entry for dates. Below are the available
methods:
The
following examples use September 24, 1999 as todays date.
-
If
todays day is entered, todays month and year will
default.
(Example: enter 24, date will default to
24-sep-1999)
-
If
todays month and day is entered, todays year will be
default
(Example: enter 1224, date will default to
24-dec-1999)
-
If
month, day and two digit year are entered, then the pivot year will
default
(If
the year is less than 28, century will be 20 if the year is greater/equal to 28,
century will be 19)
(Example: enter 122427, date will default to
24-dec-2027
enter 122428, date will default to 24-dec-1928)
·
It
is safest to enter the entire year for dates prior to 1928, so the century is
correct and not the default. If
only the last two digits are entered, all those years greater than or equal to
28 will be assigned a 19. Those
two digits less than 28 will have 20 assigned.
Examples:
45
will become 1945
14
will become 2014
·
A
value must be assigned to the Gender Code.
If the individual has not provided the information, enter the value of
unknown.
|
Male |
|
|
Female |
|
|
Unknown |
No
response provided. |
·
Enter
the entire nine-digit number, omitting dashes, in the SSN field. In most cases,
the SSN will be the same as the Identification Number. If a person has elected not to use the
SSN as the Identification Number, please enter the SSN in the required
field.
·
The
date of birth is required for all students and employees, and should be entered
for alumni when available.
·
When
the date of birth is not available, the Personnel Department will use the date
January 1, 1998 to allow for the entry of an employee record. Periodically records containing this
date will be identified and corrected.
·
Age
is calculated automatically using current date and date of
birth.
·
Use
the LIST function to select the appropriate code.
·
Citizen
type is required for all students and employees. Enter the correct
code.
|
Code |
Description |
Explanation |
|
Y |
Citizen |
Citizen
of the United States |
|
N |
Non-citizen |
Not
a citizen of the United
States |
·
The
ethnic code field is required for all students and employees. Use the List of Values to enter the code
that corresponds with the students self-identification of ethic type.
·
If
the student does not provide ethnic information, populate the field with no
reply/unknown.
·
Use
List of Values to select appropriate value.
·
Only
enter data provided by the individual.
·
Personnel
will collect and maintain this information for the purpose of assigning benefits
to individuals and their spouses.
·
Alumni/Development
will collect and maintain this information for the AD
module.
|
Code |
Description |
Explanation |
|
C |
Cohabiting |
Living
together not legally married/ Domestic
partner |
|
M |
Married |
Legally
married. |
|
D |
Divorced |
Once
married but now legally divorced. |
|
X |
Separated |
Legally
married but living apart. |
|
O |
Other |
|
|
S |
Single |
Never
legally married. |
|
W |
Widowed |
Legally
married and spouse is deceased. |
·
This
field will not be populated. This
is an optional field that may be used by some modules.
·
Central
Connecticut State University will not use this field.
·
Central
Connecticut State University will not use this field.
·
This
field is to be checked if the person requests that his/her address and/or
telephone number information not be released.
·
When
defining a population selection it is important to exclude all records with a
check mark in the confidential indicator.
·
This
information will be entered for all employees, students and
alumni.
Enter
Y if the employee/student/alumni is deceased. Enter date of death.
·
Deceased
records need to be excluded from population selection.
Creating
a Letter code in GTVLETR should start with the three-character abbreviation
representing your area. The name of
the letter should clearly define the letter type. For example:
ADM_ACCEPTANCE
ADM_REJECTION
FIA_SATISFACTORY_ACADEMIC_PROGRESS
FIA_AWARD
REC_HONORS_ACKNOWLEDGEMENT
REG_WITHDRAWAL_CONFIRMATION
Creating a paragraph name on GTVPARA should start with the three-character abbreviation representing your area. The name of the paragraph consists of a maximum of seven characters. Some examples might be:
ADM_LTR
FIA_LBL
REG_LST
The
description name of the paragraph should be used to clearly define the purpose
of the variables being gathered through the letter generation process. Some examples might
be:
Admission
Letters
Financial
Aid Labels
Registered
Student Listings