Phone Numbers
The Phone Numbers table is a secondary table designed to hold a constituent's phone, FAX, email, pager, web page address or other information. This can be information that is in addition to the phone information already stored in a certain address row, in which case the Phone Number row will link to the address with which it is associated and be considered a secondary data row. Or, it can be additional information not associated with any particular address at all and therefore be considered an associated data row.
The Phone Numbers table is associated with the Address table for display purposes. This means that to view or access the information in the Phone Numbers rows, you must access the Address information first, using the Millennium Explorer.
A Phone Number rows that is not linked to a particular address will be shown below the display of all Address rows belonging to a constituent.
A Phone Number row linked to a particular address will display as a linked secondary row, immediately following the display of the particular address itself.
The nature of the information in each row is defined by the Type column, which is driven by the Phone Type (phone_type) lookup table. A Phone Number whose type code contains 'email' or 'www' displays 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 web site.
Although the Phone Numbers table will hold email and web page addresses, your institution may choose to use the Internet Address table instead to store those email and web page addresses that are not linked to any particular address row.
An Administrator can remove the Phone Numbers table from the Millennium Explorer if not used. See Table Options for more information.
Millennium system administrators or the database administrator can configure audit logging for the Phone Numbers data table. For more information, see Audit Log.
Linked Phone Numbers
When an Phone Number row exists for a constituent, you may create a linked Phone row belonging to the spouse or another constituent. This type of linked row will be a copy of the first constituent's row. You may also link an existing Phone Number row to a Phone Number row that also already exists for the spouse or another constituent; when you do so, the Phone Number row for the second constituent will be overwritten with the first constituent's Phone Number row information. A Phone Number row can be linked to Phone Number rows for multiple constituents; that is to say, the Phone-to-Phone link does not have to be one-to-one, it can be one-to-many!
Because the Phone Number rows are linked, any edits that are made via one constituent's row will automatically be applied to the other constituents' Phone Number rows as well. This is true whether subsequent edits are made via the original constituent or the other constituents' data row.
If one of the linked Phone Number rows is deleted, the others are not automatically deleted.
Linked rows may be unlinked. This allows you to perform edits to one without affecting the other(s).
A Phone Number row may be linked to a particular Address The Phone Number then displays with the Address row to which it is linked. A Phone Number that is linked to an Address row can also be linked to Phone Number rows that belong to the spouse and other constituents.
If a Phone Number row linked to a particular Address is deleted, the Phone Number rows that link to the deleted Phone Number row will not be automatically deleted.
If the Address to which a Phone Number row is linked is deleted, the Phone Number row will be deleted as well. The Phone Number rows that link to the Phone Number row that linked to the deleted Address row will not be deleted.
The following topics discuss the creation, display, and maintenance of linked Phone Number rows.
Data Maintenance, Link New to Existing
Data Maintenance, Link to Existing to Existing
Data Maintenance, How to Link New to Existing
Data Maintenance, How to Link Existing to Existing
A Phone Number row that links to a particular Address can be inserted at the same time that the Address is created by using the Insert + Phone button on the Address Insert form. See Address, Insert + Phone for more details.
A Phone Number row that links to a particular Address can be updated/archived at the same time that the Address is updated/archived by using the Update + Phone button on the Address Maintenance form. See Address, Update + Phone for more details.
Update Phone Numbers
Phone Number rows that are linked to a particular Address will be automatically updated/archived when the Address row to which they are linked is updated/archived. See Address, Update/Archive Phone Numbers for more details. It is important that each phone type entered in the phone_type lookup table must have a corresponding 'former' version of that type also entered in the phone_type lookup table in order for this to function correctly. This functionality is available only for phone numbers that are linked to an address row.
A Phone Number linked to a particular address row can be updated or deleted,but not archived, directly from the address row to which it is linked by using the Update + Phone button on the Address row's Data Maintenance (Update) form. See Address, Update + Phone for more details.
A Phone Number row (linked or unlinked) can also be updated (or deleted) via the context menu accessed via the Edit button located directly to the left of the Phone number row that you want to update.
Phone Utilizations
The Utilization portion of the Data Maintenance form shows check boxes for up to twenty Utilization codes. You may define these codes as you want using the Address Utilization lookup table. Any entries in that lookup table that have not been redefined at your institution will display as Utilization 9, Utilization 10 and so forth.
All twenty Utilizations are included on the Data Maintenance form for the Phone Number data table. The Long Display form will show the label 'Utilizations:', and then list the labels for all Utilizations that are checked (that is to say, set to 'Y'). If you want to add one or more, but not all, of the Utilizations to a different Display form (for example, Short, or Mini), do so via the Custom Display Designer by selecting phnmc1, phnmc2, and so forth, from the Customizer's Data Column List Box. But, be aware that the labels for these codes will no longer be automatically derived from the address_utilization lookup table, but from the data column's alias in Millennium's fieldlst system table.
Phone Numbers Field Descriptions
Phone Number data is stored in the phone data table The following fields are included. The field labels and non-displaying designations that are listed here are those that the system uses by default. If you want to override these default settings, you must customize your display definition.
Note: Custom fields are included in the data table, and are available for any purpose that you want to define. These fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms.
Field Name Field Label |
Lookup Table |
Type SQL/Oracle Length [Default] {Check} |
Description |
---|---|---|---|
phnkey non-displaying |
none |
numeric/number 13,0
|
The primary key field for all rows in all tables. This field holds a permanent "time stamp" of the precise time and date the row was created. This uniquely identifies a row within the table. (system field) |
phnid non-displaying |
none |
char 10
|
This field holds the ID number of the constituent who owns this row, providing a link between this row and all others in all other tables which also belong to the same constituent. (system field) |
phndoc non-displaying |
none |
char 1 ['N']
|
This field holds a Y/N flag to indicate the existence of a linked document for this row. (system field) |
phndate no label |
none |
datetime/date
[getdate()]
|
The date that this Roving Phone Numbers row was last updated. This field is automatically entered by the system. (system field) |
phnuserid no label |
none |
varchar/varchar2 30 [suser_sname()]
|
The User ID of the operator that last edited this Roving Phone Numbers row. It is automatically entered by the system. (system field) |
phnugroup non-displaying |
none |
char 1 ['Z']
|
This field holds the Group letter that was associated with the User ID of the operator who last edited this row. (system field) |
phnnumber Phone # |
none |
char 70
|
This field holds a complete phone number, email address, pager number, FAX number or other type of "number" that you want to store in this row. |
phntype no label |
char 6 [' ']
|
The kind of "number" represented by the information in this row. |
|
phnrest Restriction |
char 6 [' ']
|
The restriction (if any) that applies to this phone number, such as, "Do not call after 8 pm," "No solicitation calls," etc. |
|
phntzone Time Zone |
none |
char 3
|
The Time Zone associated with this "number". |
phnsource Source |
Source |
char 6 [' ']
|
The source for the information in this row. |
phnpoint non-displaying |
none |
numeric/number 10,0
|
This system-assigned field is no longer used or supported. (system field) |
phnfnum non-displaying |
none |
char 2 ['26'] {'26'} |
The file (table) number for the Roving Phone Numbers table. (system field) |
phncrdate non-displaying |
none |
datetime/date
[getdate()]
|
The date that the row was created. (system field) |
phncomm no label |
none |
varchar/varchar2 4000
|
A free text Comment that may be entered and displayed with this row only. |
phndate1
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate2
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phnmny1
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny2
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnnum1
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum2
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnyesno
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnlook1
|
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
phnlook2
|
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
phnlook3
|
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
phntext
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phnpend Pending |
none |
char 1 ['N'] {not null} |
This field is a flag to indicate that this data row has linked information in the 'pending' Phone Numbers table as a result of data entry by the constituent via the Online Constituent Directory. That linked info is pending incorporation into this data row. (system field) |
phnpubfl Publish |
none
|
char 1 ['N'] {not null} |
This field is a flag to indicate whether this data row will or will not be available for online publishing. This flag will be applicable when the Options for Publishing Data for the Phone table are set to 'Published by Consent'. Otherwise, the corepub26 column flag in the Basic Data table will be used. |
phnupkey non-displaying |
none |
numeric/number 13,0
|
This field holds the Timekey of the pending data row that may be updated from the phone_pending table. |
phnaddrkey non-displaying |
none |
numeric/number 13,0
|
If a phone number is linked to an address, this field holds the Timekey of the Address row to which it is linked. |
phnlnkphn |
none |
numeric/number 13, 0
|
If this phone number is linked to another phone number, then this field signals that fact to the system. This field in the row belonging to the first constituent (primary) holds a copy of this row's Timekey. This field in the rows belonging to the secondary constituent(s) holds a copy of the Timekey from the first constituent's phone row. |
phndncflg Do Not Call |
none |
char 1
|
This field is a flag to be used with Correct Call to indicate "Do Not Call". All sites can view this column, but it will only be used and updated by Correct Call. (system field) |
Mailcode 1 |
char 1 ['N'] {'N' or 'Y'} |
Indicates when a particular type of call should be made to this phone number. More than one utilization may be assigned to the same phone number. Millennium will use the phnmc1 field to flag this number as the preferred phone number. |
|
phnmc2 Mailcode 2 |
char 1 ['N'] {'N' or 'Y'} |
Indicates when a particular type of call should be made to this phone number. More than one utilization may be assigned to the same phone number. |
|
phnmc3 Mailcode 3 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc4 Mailcode 4 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc5 Mailcode 5 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc6 Mailcode 6 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc7 Mailcode 7 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc8 Mailcode 8 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc9 Mailcode 9 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc10 Mailcode 10 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc11 Mailcode 11 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc12 Mailcode 12 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc13 Mailcode 13 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc14 Mailcode 14 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc15 Mailcode 15 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc16 Mailcode 16 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc17 Mailcode 17 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc18 Mailcode 18 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc19 Mailcode 19 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
phnmc20 Mailcode 20 |
char 1 ['N'] {'N' or 'Y'} |
see phnmc2 description. |
|
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate4
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate5
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate6
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate7
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate8
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndate9
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndte10
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndte11
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phndte12
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
phnmny3
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny4
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny5
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny6
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny7
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny8
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny9
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny10
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny11
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnmny12
|
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
phnnum3
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum4
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum5
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum6
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum7
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum8
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum9
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum10
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum11
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnnum12
|
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
phnchk1
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk2
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk3
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk4
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk5
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk6
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk7
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk8
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk9
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phnchk10
|
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
phntxt1
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phntxt2
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phntxt3
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phntxt4
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phntxt5
|
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
phnadesrc non-displaying |
char 30
|
If this row is created or updated from data that originally came from the phone_pending table, then this field will hold information about the data's import source. Data from the Online Constituent Directory will have a source of Online Directory. Data from Soft Edit users will have a source of Soft Edit. Data whose import source is the ADE Import Tool can be assigned a value (other than Online Directory or Soft Edit) from the ade_source lookup table by the user who executes the utility, or the source can be blank. |
Indices - Phone Numbers
Index | Primary | Foreign | Unique | Fields | Sort |
pk_phone |
Y |
|
Y |
phnkey |
ASC |
phone02 |
|
Y |
|
phnid |
ASC |
phone03 |
|
Y |
|
phnrest |
ASC |
phone04 |
|
|
|
phnnumber |
ASC |