More information

Profiles Lookup Tables E - R

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

E

Ethnic Groups

Table Name: ethnic_groups

Used by the Ethnic field in the Basic Data Table to indicate an ethnic group for this constituent. This field may be useful in measuring the success of goals to involve people of various ethnic or racial groups in the organization's programs and leadership.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

F

Financial Types

Table Name: financial_types

This lookup table is used by the Type field in the Financial table to describe the nature of the Financial information in that row.

Typical entries include:

Code	Value
a	Assets
ex	Expenditures
gr	Grants
net	Net Worth
sale	Total Sales
prof	Total Profit
con	Contributions
sal	Salary
ret	Retirement
real	Real Estate
bon	Bonuses
in	Investments
pp	Personal Prop.

Required Entries

Organizations who use Prospect Link to import WealthEngine data into constituent records must have these codes and values in the table. You may add any additional entries, but do not change these codes and values.

Code	Value	Notes
we-f1	Actual Value of Income	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f2	Actual Value of Income used in Calculation
we-f3	Pension Value	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f4	Pension Value used in Calculation
we-f5	Total Sales and Holdings	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f6	Total Sales and Holdings used in Calculation
we-f7	Total Giving	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f8	Political Giving Plus Lifetime Giving to your Org used in Calc
we-f9	Real Estate Value	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f10	Real Estate Value used in Calculation
we-f11	Market Guide Compensation	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f12	Company Value
we-f13	Total Charitable Donations
we-f14	Total Federal Contribution	WealthEngine no longer provides this wealth attribute (as of FindWealth8).
we-f15	Total Asset
we-f16	Net Worth
we-f17	Liquidity
we-f18	Estimated Annual Donation
we-f19	Income
we-f20	Real Estate Total Value
we-f21	Direct Stock Holdings
we-f22	Total Stock Value
we-f23	Charitable Donations
we-f24	Political Donations
we-f25	Pension

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Font Names

Table Name: font_names

These lookup table entries are provided for use in the Appearance settings for each user. If additional fonts are desired, they must be installed on the client machine, AND entered in this lookup table, exactly as the font name is shown on the client machines. This table does not use Codes.

Value
<blank>
Arial
Comic Sans MS
Courier
Courier New
Garamond
Letter Gothic
Lucida Console
Lucida Sans Unicode
Microsoft Sans Serif
Tahoma
Times New Roman
Verdana

Table Layout

This lookup table varies slightly from the standard layout. See Font Names Layout.

Foundation Types

Table Name: foundation_types

If a Constituent has a Constituent Type of Foundation, then the display of the Basic Data table includes a field for the Foundation Type. That field uses the entries in the Foundation Types lookup table to indicate the type of foundation for this constituent (family, matching, etc.)

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

G

Gift Batch Number

Table Name: gift_batch_number

Used by the Batch Number field in the Gift Transaction Table to assign a batch number to a group of transactions to process together. Note that the Group field in each entry in the Gift Batch lookup table should be designated as "open" or "closed" to indicate the status of each batch. Rows in the Gift Transaction Table which include a Gift Batch Number with a Type of "closed" cannot be edited or deleted without particular security for those functions. Values in this lookup table may be up to ten characters long, and there are no table 'Codes'.

The Gift Batch Numbers and Dues Batch Numbers lookup tables are maintained outside the standard methods for performing Lookup Table Maintenance. These two tables are maintained via the Batch Control item under Tools in the Millennium Explorer.

Table Layout

This lookup table varies slightly from the standard layout. See Gift Batch Number Lookup Table Layout.

Gift in Kind

Table Name: giftinkind

Used by the Type field in the Gift in Kind table. When a Gift or Dues Transaction is created using a Tender of Gift in Kind, the system automatically prompts for the entry of additional information concerning that gift in a secondary table. Within that secondary table (Gift in Kind) the Type field uses this lookup table to further classify the primary gift or dues transaction.

This allows you to distinguish a donation of an attorney's expertise, from a volunteer's time, from a manufacturer's product, from a constituent's art work, etc.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Gift Types

Table Name: gift_types

Used by the Type field in the Gift Transaction table to describe the type of transaction (Gift Transaction, Honor Transaction, Credit Void, etc.) This is a standard Millennium lookup table and it should not be changed or added to since many of the internal processes depend on the entry in this field.

Required Entries

Because Millennium uses these codes to trigger calculations, you must not edit, delete or add to the entries in this lookup table. Note that these codes and values are the same as those used in the Dues Type lookup table except for Gift Transaction, Gift Journal and Gift Void, and Sustainer Pledge, Sustainer Pledge Journal and Sustainer Pledge Void (Sustainer Pledge functions are available via Giving, only).

During data entry, only eight of these lookup table entries may be manually entered by the operator, and those should be flagged as active. All others must be generated by the system and therefore must be flagged as inactive for data entry purposes. All types (active or inactive) are available for criteria selection purposes in the Millennium Reporter.

Code	Value	Active/Inactive?
a	Match Credit Transaction	inactive
aj	Match Credit Journal	inactive
av	Match Credit Void	inactive
b	Bequest Transaction	active
bj	Bequest Journal	inactive
bv	Bequest Void	inactive
c	Credit Transaction	active
cj	Credit Journal	inactive
cv	Credit Void	inactive
e	Expectancy Transaction	active
ej	Expectancy Journal	inactive
ev	Expectancy Void	inactive
g	Gift Transaction	active
gj	Gift Journal	inactive
gv	Gift Void	inactive
h	Honor Transaction	active
hj	Honor Journal	inactive
hv	Honor Void	inactive
mp	Match Pledge Transaction	inactive
mj	Match Pledge Journal	inactive
mv	Match Pledge Void	inactive
o	Match Potential Transaction	inactive
oj	Match Potential Journal	inactive
ov	Match Potential Void	inactive
p	Pledge Transaction	active
pj	Pledge Journal	inactive
pv	Pledge Void	inactive
r	Pledge Credit Transaction	inactive
rj	Pledge Credit Journal	inactive
rv	Pledge Credit Void	inactive
sp	Sustainer Pledge Transaction	active
spj	Sustainer Pledge Journal	inactive
spv	Sustainer Pledge Void	inactive
t	Pledge Potential Transaction	active
tj	Pledge Potential Journal	inactive
tv	Pledge Potential Void	inactive
y	Pledge Payment Transaction	inactive
yj	Pledge Payment Journal	inactive
yv	Pledge Payment Void	inactive
z	Cumulative Transaction	inactive
zj	Cumulative Journal	inactive
zv	Cumulative Void	inactive
w	Write Off	inactive

Major Gift Display

Millennium Drive provides an improved user experience for viewing Millennium data. Data is gathered from Biographical, Giving, Prospect Management, and from the Events world, and presented for viewing and analysis in a variety of ways.

Touch Points is a Constituents page in Millennium Drive. It is a timeline graph and listing of a constituent's interactions with your organization (touches) and of his or her major life events. The information that displays on the Touch Points page is pulled from different data tables. The system determines what data records to display based on the value of a Major Gift Display field in lookup tables. To display a Gift transaction in Millennium DriveTouch Points, it must have a Gift Type with the Major Gift Display field set to Y.

Table Layout

This lookup table varies from the standard lookup table layout. See Gift Types.

Top of Page

I

Industries

Table Name: industries

Used by the Industry field in the Jobs Table to indicate the industry in which this constituent is employed, and also by the Basic Data Table for Corporations or Foundations to describe the type of industry with which it is affiliated. You may want to establish values for this lookup table which correspond to the Department of Commerce's Standard Industry Codes (SIC).

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Institutions

Table Name: institutions

Used by the Institute field in the School table to indicate the school, college, university, or other institution with which the information in this school row is associated.

Table Layout

This lookup table varies slightly from the standard lookup table layout. See Institutions Layout.

Instrument

Table Name: instrument

Used by the Instrument field in the Proposal or Planned Gift Table to identify the type of planned gift instrument being proposed. Types of instruments which might be identified include unitrusts, annuity trusts, bequests, insurance policies, etc.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Internet Address Type

Table Name: internetaddress_type

Used by the Type field in the Internet Address Table to identify the type of internet address. Examples might include home email (email), business email (bemail), web address (www). When an Internet address is displayed, and the type code contains 'email' or 'www' (for example, 'emaila', 'bemail', 'wwwb'), it appears as hyperlink text. When the hyperlink is executed, the software will either automatically launch your mail messaging system with the email address in place, or it will automatically access the constituent's website.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

J

Job Descriptors

Table Name: job_descriptors

Used by the Descriptor 1 field in the Jobs Table to provide an additional description of the constituent's job. The Title field in the Employment Table is used to maintain, in free text form, an individual's title, as he or she has given it to you. Because of the unlimited possibilities, this field is not a good basis for selection. By contrast, the Jobs Descriptors Lookup table can be a standardized listing which the institution uses to describe a person's job title and to use for report selection. An example might be an individual whose job title is "Chief Operating Officer and General Counsel" but whose Job Descriptor could be "COO" or "General Counsel."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Job Descriptors2

Table Name: job_descriptors2

Used by the Descriptor 2 field in the Jobs Table to provide an additional description of the constituent's job. The Title field in the Employment Table is used to maintain, in free text form, an individual's title, as he or she has given it to you. Because of the unlimited possibilities, this field is not a good basis for selection. By contrast, the Jobs Descriptors 2 Lookup table can be a standardized listing which the institution uses to describe a person's job title or for any other purpose desired by your institution. An example might be an individual whose job title is "Chief Operating Officer and General Counsel" but whose Job Descriptors could be "COO" or "General Counsel."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Job Descriptors3

Table Name: job_descriptors3

Used by the Descriptor 3 field in the Jobs Table to provide an additional description of the constituent's job. The Title field in the Employment Table is used to maintain, in free text form, an individual's title, as he or she has given it to you. Because of the unlimited possibilities, this field is not a good basis for selection. By contrast, the Jobs Descriptors Lookup 3 table may be any standardized listing which the institution wants to use to describe a person's job title and to use for report selection. An example might be an individual whose job title is "Chief Operating Officer and General Counsel" but whose Job Descriptors could be "COO" or "General Counsel."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Job Status

Table Name: job_status

Used by the Status field in the Jobs Table to indicate the status of this employment (active, retired, etc.) Millennium allows you to maintain a record of a constituent's employment history. Changing the Status in an Employment row triggers certain automatic changes in other rows. For example, changing the Status from active to retired changes the Relationship row (from Employer - Employee to Former Employer -Former Employee), the matching gift company link and the count of known employees for the company.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value
act	Active
no	No Longer at This Position
ret	Retired

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

L

Language Preference

Table Name: language_preference

Used by the Language Preference field in the Basic Data table, this option allows you to select the preferred language of each constituent.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Locators

Table Name: locators

Used by the Locator field in the Address Table to describe the status of an address (good, lost, omit, returned, etc.) A good address is one that is presumed to be current and valid. An omit address is one that, while current and valid, is not to be used for mailings. A returned address is one that has been returned by the post office as no longer valid but which you have not yet determined to be lost. A lost address is not valid and may be considered the last known address. A former address is one that is known to be no longer valid, but which you want to retain in the Address table for historical purposes. If you use the Update Address function on an Address row, the system will change the Locator for that row to former and prompt for the creation of a new Address row with a Locator of good.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value
g	Good
d	Deceased
form	Former
l	Lost
o	Omit
r	Returned

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

M

Marital Status

Table Name: marital_status

Used by the Marital field in the Basic Data Table to describe the marital status of the constituent.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value
ds	Deceased Spouse
m	Married
ss	Surviving Spouse
d	Divorced
dvsp	Divorced Spouse

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Memory Descriptors

Table Name: memory_descriptors

Used by certain Summary rows in the Summaries table to list valid textual entries. These are used to specify giving clubs or levels for this constituent. The Memory Descriptors are assigned to one of the Summary rows using the Millennium Reporter in combination with the Summary utility.

During the procedures for defining and assigning the information for Summary rows, a label name for the row is selected from the Memory Names lookup table. If that lookup table entry has a Group designation of desc, then the Memory Descriptors lookup table is made available for use as the "data" for that row.

For example, if you were to choose an entry such as Giving Club from the Memory Names table (and that entry had desc as its Group) then the utility may use the entries in the Memory Descriptors lookup table, (such as, Bronze Associates, Silver Associates, Gold Associates, or Platinum Associates) and assign the appropriate one to the Summary row, along with the label from the Memory Names lookup table.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Memory Names

Table Name: memory_names

This lookup table defines the labels for the various Summary rows as they are displayed in the Profiles. Summary rows may store summary numerical gift information, as defined by your institution, or textual information describing giving clubs or levels. The information that follows each of the Summary labels is calculated or determined using the Millennium Reporter and the Summaries or Years utilities.

The Memory Names lookup table uses the Group field to signal the system as to the nature of the "data" that will be displayed with that Memory Name. There are four kinds of data that may be displayed. The table below shows the four kinds of data, the Group that signals each, and an example of the way in which that data is formatted. In addition, the Group indicates whether the memamount or the memdescrp field from the Summary row is to be displayed.

Nature of the Information	Group	Example	Formatting	Column to Display
count	(blank)	number of transactions	1,997	memamount
dollar amount	$	total giving amount	$1997.00	memamount
year	no	year of first gift	1997	memamount
description	desc	giving club	Patron's Club	memdescrp

Major Gift Display

Touch Points is a Constituents page in Millennium Drive. It is a timeline graph and listing of a constituent's interactions with your organization (touches) and of his or her major life events. The information that displays on the Touch Points page is pulled from different data tables. The system determines what data records to display based on the value of a Major Gift Display field in lookup tables. To display a Summary record in Millennium DriveTouch Points, it must have a Memory Name with the Major Gift Display field set to Y.

Required Entries

You may add entries to this lookup table but should not change these codes.

Organizations that use Millennium Drive and want to easily display total giving, consecutive number of years given, largest gift and total giving year to date for a constituent on the Millennium Drive Constituent Summary page must create Summaries with these memory name codes. These Summaries would also display in Millennium DriveTouch Points because the Major Gift Display fields for these entries are set to Y.

Note: Standard reports exist in the Financial Reports library to help you create these summaries.

You can add entries to this lookup table, but do not change the codes. You may want to change the values, especially if you use the same values for different codes in your Memory Names table.

Code	Value	Major Gift Display
abila1	Total Giving	Y
abila2	Consecutive Years Giving	Y
abila3	Largest Gift	Y
abila4	Total Giving Year to Date	Y

Table Layout

This lookup table varies from the standard lookup table layout. See Memory Names.

Top of Page

N

Name Types

Table Name: name_types

Used by the Name Type field in the Names Table to indicate the type of name this row represents. In addition, when other data rows hold a copy of a constituent name, the name type is automatically copied to that data row, to be used as a means of identifying the name type. Those data rows are: Correspondence, Coverage, Event Guest, Event Solicitor, Event Registration, Honoree, Membership, Organizer, Relationships, Solicitor, and Speaker. Remember that a constituent may have multiple names recorded in the Names Table and that this lookup table categorizes those names. Some Name Types might be:

Preferred Name

Throughout Millennium, when a constituent name is used, the system will use the 'first found' Name row, unless the situation requires a different, specific type of name. When using the standard Name Type entries, this will be the Preferred Name and each constituent should have a single Name data row designated with that type. This is the name the report writer will use in all reports unless another name type is specified. It is also the name that appears in the title bar to identify the constituent currently being accessed. In the Name Type lookup table, it has the Code: 'a'. If you have reassigned the Value associated with the Code 'a' in the Name Type lookup table, or if you have created Name Types using a Code that precedes 'a' (this would include uppercase characters), those name types will be the first found name row.

Maiden Name

Maiden Name types are especially useful when they are assigned a name lookup equal to Y (Yes). This allows the constituent's row to be accessed from either their preferred name or maiden name.

Personal Salutations

Correspondence is often mailed to constituents from various directors and staff members. The names screen is the perfect place to record the personal salutations of these staff members. Each staff member should be assigned a name type, for example, Vice President's Salutation, Director of Development Salutation, Annual Fund Director Salutation, etc. and the salutations appropriately recorded for each. The report writer can be instructed to use a specific name type when printing the letter. If the salutation is the same as the default salutation generated by the system, for example, Mr. Smith, there is no need to input a special salutation.

Combined Spouse Names

Generally, if you want to use a combined spouse name in reporting situations, you would choose the appropriate spouse option on the report form. When you do so, the system will use the data in the combined name field in the Name row of the type you also specify in the report options. This is the preferred technique.
There is one alternative to this behavior that is available for use in a very specific situation in reporting. When a constituent spouse couple have a very particular form of their names that they prefer to use in ALL situations, you may create a Name row belonging to either one of them, with a Name Type of: Combined Name, (Code: comb). The Millennium Reporter will use it as an override instead of any other system-generated name, when using combining spouse names. If the combined name type is present for either spouse and the combine name options on the report form are set to use a combined name, the report writer will use it instead of the data in any other Name row. If a combined name type row is not found, the system will use the combined name field from the Name row of the specified type.

Combined Salutation

Generally, if you want to use a combined spouse salutation name in reporting situations, you would choose the appropriate spouse option on the report form. When you do so, the system will use the data in the combined salutation name field in the Name row of the type you also specify in the report options. This is the preferred technique.
There is one alternative to this behavior that is available for use in a very specific situation in reporting. When a constituent spouse couple have a very particular form of their names that they prefer to use in ALL salutation situations, you may create a Name row belonging to either one of them, with a Name Type of: Combined Salutation Name, (Code: csal). The Millennium Reporter will use it as an override instead of any other system-generated name, when using combined salutation spouse names. If the combined salutation name type is present for either spouse and the combine name options on the report form are set to use a combined name, the report writer will use it instead of the data in any other Name row. If a combined salutation name type row is not found, the system will use the combined salutation name field from the Name row of the specified type.

Non-Constituent Spouse

When you want to keep track of the name of the spouse of a constituent without creating a Basic Data row for that spouse, you may do so by creating a name row with a Type Code of: "sp". This will indicate that this name row is being used to hold the name of the constituent's non - constituent spouse. If you add a name row to an individual with this Name Type, the Marital Status field in the Basic Data row will be updated to "Married". Don't confuse this Name Type with the Relationship Type, "sp" - "Spouse" even though they both use the same codes and values in their lookup table entry.

Contact Name

If the constituent is a corporation or other organization, you may want to keep track of the name of the contact person within that organization. In this case, a name row belonging to the Corporation may be created with the Name Type, Contact Name, "con", and showing the name of the individual. This standard type is used by certain of the standard report templates to produce a listing of corporations, the names of the contacts within them, and address and phone information.

Husband Preferred and Wife Preferred

If your institution uses the practice of creating one constituent on the system to track a spouse couple, (Gender = C), then the standard Name Types, Husband Preferred and Wife Preferred may be used to track the names of each of the spouses. If two Name rows are created using these two Types and if the constituent is a couple, then the system will automatically generate a third Name row with a Type of Preferred, and constructed from the information in the Husband Preferred and Wife Preferred Name rows.

Event Name

If your institution uses the Events module of Millennium, you may choose to define a name for the system to use as a default for the Name Tag Line 1 in the insert form for the Event Guest data row. If such a row exists, the formatted name from the name row is used. If no such name row exists, the system will use the Preferred Name.

Required Entries

You may add entries to this lookup table but should not change these codes and values. Note that if you create additional entries with a Code that precedes 'a' (which would include uppercase characters), then the Preferred Name will not be the 'first found' name for reporting or for the header in the constituent display.

Code	Value
a	Preferred
comb	Combined Mailing Name (IF USED)
con	Contact Name
csal	Combined Salutation Name (IF USED)
event	Event Name (Used as the default information for an Event Guest Name Tag.)
ha	Husband Preferred
sp	Spouse Name (Used for a non-constituent spouse name). Do not confuse this Name Type with the Spouse Relationship Type which also uses the Code, "sp"
wa	Wife Preferred

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

O

Occupations

Table Name: occupations

Used by the Occupations field in the Jobs Table to describe the occupation of the constituent. Occupations recorded here are for general classification purposes and are usually defined broadly, such as attorney, banker, teacher, plumber, etc. The Occupation is usually more general than the Job Descriptor. When those two fields are used in conjunction with the Industries lookup table, it is possible to distinguish an attorney (Occupation) who works as a professor (Job Descriptor) for a law school (Industry), from an attorney who acts as a patent researcher for a pharmaceutical company.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

P

Phone Types

Table Name: phone_type

Used by the Type field in the Phone Table to indicate the type of phone number. Examples might include: cellular, pager.

Required Entries

In order to use the Millennium Address function of Update/Archive for an address with one or more linked phone number rows, then for every entry that you create in this lookup table, you must also create a corresponding entry that is the 'Former' version. The Code for the 'former' entries must be the same as the original, but ending in 'f'. For example, these entries:

Code	Value
cell	Cellular Phone
page	Pager

must have these corresponding entries:

Code	Value
cellf	Former Cellular Phone
pagef	Former Pager

The Phone Numbers data table also uses the following Types. When a Phone Number whose Type contains either 'email' or 'www' (for example, 'emaila', 'bemail', 'wwwb') is displayed, it appears as hyperlink text. When the hyperlink is executed, the software will either automatically launch your mail messaging system with the email address in place, or it will automatically access the constituent's website.

Code	Value
email	email
www	Internet

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Phone Restrictions

Table Name: phone_restrictions

The Phone Restrictions lookup table is used by the Restrictions fields that are associated with each phone number field in both the Address and Phone Numbers tables. These Restrictions might be used to designate a number as Non-published, Unlisted, Evening Only, Evening and Weekends, etc.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Places

Table Name: places

Used by the Place field in the Address Table, the Death table, and in the ZIP Code lookup table to identify the postal code for the state or province. This lookup table provides uniformity of state names and abbreviations to enable accurate searching and reporting.

During data maintenance, the system will ensure that the entry that you choose from this lookup table conforms to the US ZIP Code lookup table under the following circumstances:

If the Country lookup table entry that is specified in the Address row has a Group that is anything other than for (foreign), (this would include a blank), the system assumes that the Address is a US Address. As such, the Places entry will be expected to conform to the standard ZIP Code lookup table (which provides a link between the ZIP Codes and the Places). In these circumstances, the system will automatically enter or edit the Places field based on the ZIP Code.

If the Country that is specified in the Address row has a Group of for, then the system will accept any entry that you select from the Places table for that field in the Address row.

Required Entries

This lookup table requires that a blank entry be present, in addition to the following requirements.

All states and territories, possessions, etc. of the U.S. use their two-letter postal abbreviation for their codes and state or territory name as their value.
For example:

Code	Value
AL	Alabama
AK	Alaska

WY	Wyoming
GU	Guam
PW	Palau
FM	Fed States of Micronesia
MH	Marshall Islands
MP	Northern Mariana Islands

The codes and values for the Canadian subdivisions should be as follows:

Code	Value
AB	Alberta
BC	British Columbia
LB	Labrador
MB	Manitoba
NB	New Brunswick
NF	Newfoundland
NT	Northwest Territories
NS	Nova Scotia
ON	Ontario
PE	Prince Edward Island
PQ	Quebec
SK	Saskatchewan
YT	Yukon

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Plan Gift Type

Table Name: plan_gift_type

Used by the Type field in the Planned Gift or Proposal table to describe the type of planned gift the donor is interested in making. Generally this would be "Lifetime" or "Testamentary."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Pledge Types

Table Name: pledge_types

Used by the Pledge Type field in the Gift Transaction and Dues Transaction Tables to describe the frequency of reminders for a pledge. For example, pledge reminders may be monthly, quarterly, etc. and they may be billed or not billed.

Required Entries

Because Millennium uses these codes to compute pledge reminders, you should not edit, delete or add to the entries in this lookup table.

Code	Value
a	Annual
an	Annual No Bill
b	Bi-Monthly
bn	Bi-Monthly No Bill
m	Monthly
mn	Monthly No Bill
q	Quarterly
qn	Quarterly No Bill
s	Semi-Annual
sn	Semi-Annual No Bill
sm	Semi-Monthly
smn	Semi-Monthly No Bill
z	Special
zn	Special No Bill

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Priority

Table Name: priority

Used by the Priority field in the Tasks table to define the priority of this Task. This field is primarily intended for use by development officers in organizing and scheduling their work.

Required Entries

If certain conditions are met and settings are chosen, A user's Microsoft Outlook Tasks and Calendar can be updated when Tasks are entered in Millennium, and visa-versa. The following lookup table entries are required to facilitate the correct mapping between Millennium's task priority and Outlook's Priority. If other codes are used, then Millennium will set the Outlook priority to Normal when updating Outlook with Millennium data. However, if codes other than these are found in Millennium's task priority field, then Outlook will not overwrite the Millennium task priority field with the Priority as set in Outlook.

You may add entries to this lookup table but should not change these codes and values.

Code	Value
0	Low
1	Normal
2	High

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Proposal/Planned Gift Rating

Table Name: plangift_rating

The Proposal table and the Planned Gift table may have attached secondary table rows from the secondary PG Rating (pgrating) data table. Those PG Rating rows include a Rating field which is driven by this lookup table. That field is used to indicate an assessment of the donor's potential for this planned gift. The system or scheme used is defined by your institution but might be such things as: "low, medium or high", or "10% - 100%", Ratings of "1 - 5", or "ready to give, not likely to give, etc."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Proposal/Planned Gift Status

Table Name: plangift_status

The Proposal table and the Planned Gift table may have attached secondary table rows from the PG Rating (pgrating) table. These PG Rating rows include a Rating Status field which is driven by this lookup table. This field is used to describe the stage of evaluation or the stage of solicitation for this Rating. These categories are defined by your institution but might include categories such as: "Under Evaluation, Rating in Progress, Solicitation in Progress, Awaiting Donor Response."

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

Q

Quid Pro Quo Items

Table Name: quid_pro_quo_items

To conform to IRS requirements, you may maintain information concerning quid pro quo items that your constituents may receive in return for a gift or a certain level of giving. The Items field in that table uses the Quid Pro Quo lookup table. The Amount 1 field in the lookup table is used for the value of the Quid Pro Quo item. When an Item is chosen during data entry, the value (the Amount 1 column) is automatically copied to the Quid Pro Quo row.

Important! System-Generated 80/20 QuidPro (code = q8020) is an entry that is used by the system. Do not set this item to Active to make it available for data maintenance purposes!

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Top of Page

R

Rating Companies

Table Name: rating_companies

These lookup table entries are used by the Company field within the Demographic row to identify a third party consulting company that provided the Rating information shown in the row.

Required Entries

Sites who utilize WealthEngine's Prospect Link functionality must have this code and value in the table. You may add any additional entries, but do not change this code and value.

Code	Value
we	WealthEngine

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Rating Status

Table Name: rating_status

Used by the Rating Status field in the Rating table (attached to a Tracking row) to describe the degree of research that went into a particular Donor Rating. This information can help you determine an appropriate degree of confidence in the evaluation.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Reference Name

Table Name: reference_name

Used by the Reference field in the Media Table to identify the name of the publication that contains a mention of, or an article about the constituent, or an article by the constituent. Examples might be: Alumni Magazine, NY Times, Fortune Magazine, etc.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Reference Type

Table Name: reference_type

Used by the Reference Type field in the Media Table to describe the kind of reference to the constituent made by the publication (obituary, personal, business, etc.)

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Regions

Table Name: regions

Used by the Region field in the ZIP Code Lookup table and the Region field in the Countries lookup table. When a ZIP Code entry is selected for a USA Address row, the Region that is associated with that ZIP Code is automatically entered into the Region field in the Address row. When a non-USA Country is selected for an Address row, the Region that is associated with that country is automatically entered into the Region field in the Address row. Districts, Regions, Territories, and Zones are used to group constituents by geographic area as defined by your institution. This may follow any scheme that you want but would probably be a broader category than a city or state.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Relation Pairs

Table Name: relation_pairs

Used by the Is A and Whose fields in the Relation table to determine what relationship types are acceptable for use with other relationship types. Jane Doe Is A Mother Whose Son is John Doe would be an acceptable relationship, but Jane Doe Is A Mother Whose Company is John Doe probably would not. You will only define one side of the appropriate relationship pair. For example, once you enter the Mother and Son relationship into the table, you will not be able to then enter Son and Mother. Millennium will use the acceptable_relationships View to show both sides of the relation pair during data entry.

Required Entries

Is A Code	Is A Value	Whose Code	Whose Value
pmdir	Prospect Manager Director	pmsrd	Prospect Manager Secondary Director
pmdir	Prospect Manager Director	pmasst	Prospect Manager Assistant
pmdir	Prospect Manager Director	pmres	Prospect Manager Researcher
pmdir	Prospect Manager Director	pm	Prospect Manager
pmdir	Prospect Manager Director	pms	Secondary Prospect Manager
pmsrd	Prospect Manager Secondary Director	pmasst	Prospect Manager Assistant
pmsrd	Prospect Manager Secondary Director	pmres	Prospect Manager Researcher
pmsrd	Prospect Manager Secondary Director	pm	Prospect Manager
pmsrd	Prospect Manager Secondary Director	pms	Secondary Prospect Manager
pm	Prospect Manager	pmasst	Prospect Manager Assistant
pm	Prospect Manager	pmres	Prospect Manager Researcher
pm	Prospect Manager	p	Prospect
pm	Prospect Manager	pp	Potential Prospect
pms	Secondary Prospect Manager	pmasst	Prospect Manager Assistant
pms	Secondary Prospect Manager	pmres	Prospect Manager Researcher
pms	Secondary Prospect Manager	p	Prospect
pms	Secondary Prospect Manager	pp	Potential Prospect

Table Layout

The set of fields that are used in the relation_pairs lookup table (the table layout) differs from any other lookup table. The fields are described in Relation Pairs Layout.

Relations Status

Table Name: relations_status

Used by the Status field in the Relations Table to describe the admissions recruitment status for a non-constituent relationship. This field is generally used for tracking the admissions process for a constituent's child.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Relationships

Table Name: relationships

Used by both the Is A and by the Whose fields in the Relations Table to describe the relationship between two constituents. Examples are: John Doe Is A Spouse Whose Spouse is Jane Doe, or John Doe Is A Father Whose Daughter is Mary Doe or John Doe Is An Employer Whose Employee is Tom Smith. Entries in the Relationships lookup table may be grouped by using the Group field (which is driven by the Table Groups lookup table) in the lookup table row. Some possible groupings might be, Family, Business, Fund Raising, etc.

Several entries in this table trigger automatic functions within Millennium, and therefore should not be changed.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value	table_pm
boss	Employer
ch	Child
cm	Not Spouse Combine Mailing
compny	Company
daug	Daughter
dsp	Deceased Spouse
dvsp	Divorced Spouse
emp	Employee
fath	Father
fbos	Former Employer
femp	Former Employee
gsol	Gift Solicitor
lp	Life Partner
lpnm	Separate Mailing Address Life Partner
mcmpny	Match Through Company
moth	Mother
p	Prospect	p
pc	Parent Corporation
pm	Prospect Manager	pm
pmasst	Prospect Manager Assistant	asst
pmdir	Prospect Manager Director	dir
pms	Secondary Prospect Manager	pm
pmsrd	Prospect Manager Secondary Director	dir
pmres	Prospect Manager Researcher	asst
pp	Potential Prospect	p
remp	Retired Employee
son	Son
sp	Spouse
spnm	Separate Mailing Address Spouse
ssp	Surviving Spouse
sub	Subsidiary

Major Gift Display

Touch Points is a Constituents page in Millennium Drive. It is a timeline graph and listing of a constituent's interactions with your organization (touches) and of his or her major life events. The information that displays on the Touch Points page is pulled from different data tables. The system determines what data records to display based on the value of a Major Gift Display field in lookup tables. To display a Relationship record on Touch Points, it must have an Is a with the Major Gift Display field set to Y and the Group that the Is a belongs to has the Major Gift Display field set to Y. And, it must have a Whose with the Major Gift Display field set to Y and the Group that the Whose belongs to has the Major Gift Display field set to Y.

Table Layout

This lookup table varies slightly from the standard layout. See Relationships Lookup Table Layout.

Research Level

Table Name: research_level

Used by the Research Level field in the Tracking table to define the quality and quantity of research information compiled by the research staff. You might establish a system of phases of research in such a way that Phase 1 means that research has been done using the Alumni Magazine, Who's Who and Dun & Bradstreet. Phase 2 might mean that in addition to Phase 1, SEC Filings and Foundation Source books have been researched. Phase 3 might indicate that in addition to Phase 1 and 2, property records have been researched for real estate holdings or liens. Alternately, you might establish numerical ratings from one to ten to describe the amount of research that has been done.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Resource Name

Table Name: resource_name

Used by the Resource field in the Research Sources table to identify a particular publication. Generally, an institution will identify a standard set of resources (reference publications, databases, listings, etc.) that it targets for research. Each row in the Resource Name table contains information concerning one of those sources, indicating such information as the scheduled completion date, whether information was found, the person assigned to perform the research, etc.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Response Method

Table Name: response_method

Used by the Response Method field in the Correspondence table to describe the way in which the constituent delivered a response to a piece of correspondence from your institution. For example: phone call, email, personal letter, response card, etc.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value
email	Email
text	Text Message

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Response Type

Table Name: response_type

Used by the Response field in the Correspondence table to describe the basic content of the constituent's response to a piece of correspondence from your institution. For example: will attend, will not attend, contact again later.

Table Layout

This lookup table conforms to the Standard Lookup Table Layout.

Required Entries

You may add entries to this lookup table but should not change these codes and values.

Code	Value
	<blank>
reg	Registered
unsub	Unsubscribe

Top of Page