More information

Configuring Serialized Tax Receipting

Issue New Receipts Tax Receipting Process

Reprint Receipts Tax Receipting Process

Void Receipts Tax Receipting Process

Manual Receipts

Void Single Receipt

Serial Receipts Display

Formatted Printed Receipts

Journal Receipted Giving and Dues Transactions

Delete Receipted Giving and Dues Transactions;

Pledge and Pledge Payment Transactions and Serialized Tax Receipting

Serial Receipts Table Field Descriptions

Serial Receipts Payments Table Field Descriptions

Tools World

Site-Specific Notes

Serial Receipts

Access the tools to process and create Serialized Tax Receipts by using Millennium Explorer Tools>Tax Receipting. Access the data display for a constituent's Serial Receipts by using Millennium Explorer Profiles>Giving>Serial Receipts.

Some sites want to issue receipts for the donations that they receive, primarily for tax purposes. For Canadian sites, the Canada Revenue Agency (CRA) has specific requirements for tax receipts.

Millennium provides Serialized Tax Receipting to fulfill these requirements by allowing users to create serialized receipts that are separate from regular receipt numbers. The ability to store, print, export, display and void serialized tax receipt data is available through Serialized Tax Receipting. Canadian sites can use receipt data to produce tax receipts in accordance with the CRA rules.

Important!

While the system will enforce some fundamental CRA rules, it is the responsibility of the site to insure that the printed, reprinted and voided tax receipts meet all of the CRA rules. For example, it is a CRA rule that the donor name and address appear on a printed tax receipt. The system will enforce this rule by not generating receipts for any constituent that does not have an address in the system. It is also a CRA rule that a reprinted tax receipt include a message to indicate that the receipt is a duplicate. the system provides a way to enter this message on a receipt, but will not stop a user from reprinting a receipt if the message is left empty.

There are three main components to Serialized Tax Receipting.

Serialized Tax Receipting will be available to use once the necessary configuration steps have been taken. See Configuring Serialized Tax Receipting.

Serialized Tax Receipting Processes

The Serialized Tax Receipting Process automatically generates new serialized receipts for existing Giving and Dues transactions, and formats receipt data for printing, reprinting and exporting. There is also a Serialized Tax Receipting Process to automatically void one or more previously generated receipts.

Users are granted permission to access the Issue New Receipts, Reprint Receipts and Void Receipts Tax Receipting Processes through User Maintenance. Users who do not have access to these processes will not have the Tax Receipting item on the Millennium Explorer. See User Maintenance, Configuring Serial Receipts for more information about granting user access to this functionality.

Issue New Receipts Tax Receipting Process

The Issue New Receipts Tax Receipting Process automatically generates serialized receipts for one or more existing Giving and Dues transactions.

Issue New Receipts

  1. Access the Tax Receipting Issue New Receipts page by using Millennium Explorer, Tools>Tax Receipting>New.
  2. Enter the transaction Start Date and End Date. Both fields are required and the two dates cannot be more than 1 year apart. The dates entered here correspond to the Process date on the gift (giftprocdt) or dues (duesprocdt) record.
  3. Select one of the Constituent Selection options.
    1. Select All eligible transactions to generate receipts for all constituents who have at least one Gift or Dues transaction that is eligible for receipting.
    2. Select Select a single constituent to generate receipts for one constituent that has at least one Gift or Dues transaction that is eligible for receipting.
      1. Click the Select a single constituent hyperlink. The Serialized Tax Receipting ID Search page displays.
      2. Use the ID Search page to do a constituent
        • If the search returns one or more constituents who completely or partially match the search criteria, click on the ID number or name of the desired constituent.
        • If one of the listed constituents is not the desired constituent, click on the refine the query hyperlink to re-display the ID Search form. You may re-specify your search criteria, or click on the Cancel hyperlink to end the search.
        • If the search does not return a constituent who matches the criteria, the ID Search form displays. You may re-specify your search criteria, or click on the Cancel hyperlink to end the search.
      3. If you change your mind once the desired constituent is identified, click the Change hyperlink to select a different constituent.
    3. Select Select a worktable to generate receipts for constituent ID Numbers in a worktable who have at least one Gift or Dues transaction that is eligible for receipting.
      1. Click the Select a worktable hyperlink.
      2. The Load Table form displays. The worktables names that are listed are worktables previously created and saved by, or on behalf of, the user currently logged into the system.
        1. Select the worktable you want to use.

        2. Click Accept.

          Other buttons on the Load Tables form:

          Cancel will close the Load Tables form.

          Delete will delete the selected worktable. A confirmation message will be shown before the system deletes the worktable.

      3. If you change your mind once the desired worktable is identified, click the Change hyperlink to select a different worktable.

      Note: Once you make a Constituent Selection of either Select a single constituent or Select a worktable, you must click the Clear hyperlink in order to change to a different Constituent Selection option.

  4. Select one or more of the Transaction Selection options. New receipts will be generated for only the transactions that are fully applied to one or more of the following receivable (transaction) types:
  5. Select one or more Receipt Options options
  6. Select one or more Printing and Output options.

  7. Clear the Trial Run check box if you do not want review the receipts prior to final run.

    It is a best practice to do a trial run before committing to the final receipt run. Once the receipts are generated, they cannot be edited and cannot be deleted. If changes are necessary, receipts must be voided and they must be generated again.

  8. Click Run to generate the new receipts. To remove all of the process options selections that you have made (it is not necessary to do so), click Clear.
  9. To exit the Issue New Receipts page, select your next task from the Millennium Explorer.

The Issue New Receipts Progress Page

While the Issue New Receipts Tax Receipting Process is in progress, the Receipting in Progress page displays. Hyperlinks are available to open this page in a new browser window or tab, depending on your browser configuration, and to refresh this page during the process.

The Receipting in Progress page may include the following sections, at different points in the process.

Progress

After the Preprocessing step, additional Progress information is displayed.

Summary Report

The Summary Report section will display at the Ready to print Step. It will display only if you selected the Generate summary report process option.

Printing and Output

At the Ready to print step, the receipts have already been generated ( if the Trial Run process run option was not selected). Receipt rows have been written to the Serial Receipting data. The Printing and Output section displays. Here you tell the system to export the generated receipt data (if the Export data process option was selected) and to create the physical receipts so that they can be printed.

Finish

Click Finish when done. This cleans up the temporary tables that are created during processing, and returns you to the Issue New Receipts page.

Notes:

Top of Page

Reprint Receipts Tax Receipting Process

Previously generated Serialized Receipts can be reprinted. And, you can print previously generated receipts for the first time by using the Reprint Receipts process.

Manual Receipts are not available for reprinting.

Reprint Receipts

  1. Access the Reprint Receipts page by using Millennium Explorer, Tools>Tax Receipting>Reprint.

  2. Select one of the Select Receipts to Reprint options

    • Select One receipt to reprint one receipt only, and enter the desired receipt number.
    • Select Receipt range to reprint receipts within a range of receipt numbers. Enter values for both the start and end receipt numbers. The receipts selected for reprinting will have numbers that fall within the range that you have entered, and include both start and end numbers.

    • Select Receipt run to reprint receipts that were generated during a particular Issue New Receipts receipt run process. You can enter a value for the receipt run number or

      1. Click Select to choose from a list of existing receipt runs. The Please select a receipt run form displays.
      2. Click the desired receipt run.
      3. Click Select.
    • Check With receipt prefix to reprint receipts that have a specific prefix, and enter that prefix in the text box. This option is combined with one of the other Receipts to Reprint options. Receipts that are selected for reprinting must also have this prefix.

  3. Select one or more Printing and Output options

    • Select address utilization: choose an Address Utilization from the list box if you want the receipt reprint process to use an address (for export and for printing) other than the constituent's Preferred address.

      Note: If the constituent does not have an address with the chosen utilization, then the receipt run process will use the constituent's preferred address.

    • Select Include a message on reprints and enter the message that you want to be printed on the reprinted receipts (for example, 'This is a reprint of the original receipt').
    • Select Generate summary report to create a report that lists, for each constituent, the receipts, and the receipts selected transactions, that have been selected for reprinting.
    • Select Export data to generate a CSV file that contains the receipt data for the receipts that are selected for reprinting. The CSV file will be created and saved to the inetpub/wwwroot/mill/exports directory on the IIS machine.
    • Choose the Crystal format that you want the system to use to format the reprinted receipts from the Select format list box. The format that you select for reprinting does not have to be the same format that you used to print the receipts when they were generated.

  4. Clear the Trial Run check box if you do not want to review the results of the reprint process prior to the final run.

    It is a best practice to do a trial run before committing to the final reprint receipt run. The system keeps a count of the number of times a receipt is printed. Once the receipts are reprinted, this count cannot be decreased.

  5. Click Run to execute the Reprint Receipts process. To remove all of the process options selections that you have made (it is not necessary to do so), click Clear.
  6. To exit the Reprint Receipts page, select your next task from the Millennium Explorer.

The Reprint Receipts Progress Page

While the Reprint Receipts Tax Receipting Process is in progress, the Receipting in Progress page displays. Hyperlinks are available to open this page in a new browser window or tab, depending on your browser configuration, and to refresh this page during the process.

The Receipting in Progress page may include the following sections, at different points in the process.

Progress

After the Preprocessing step, additional Progress information is displayed.

Summary Report

The Summary Report section will display at the Ready to print Step. It will display only if you selected the Generate summary report process option.

Printing and Output

At the Ready to print step, the Printing and Output section displays. Here you tell the system to export the receipt data (if the Export data process option was selected) and to re-create the physical receipts by submitting the receipt data to the selected Crystal Reports format.

Finish

Click Finish when done. This cleans up the temporary tables that are created during processing, and returns you to the Reprint Receipts page.

Notes:

Top of Page

Void Receipts Tax Receipting Process

Serialized Receipts that were generated by using the Issue New Receipts Tax Receipting Process can be voided by using the Void Receipts Tax Receipting Process. A previously generated serialized receipt can also be voided by using the Void Single Receipt component.

Once a receipt for a transaction is voided, a new receipt for the transaction can either be generated by using either the Issue New Receipt Tax Receipting Process or by adding it as a Manual Receipt to the existing transaction.

Manual Receipts cannot be voided by using the Tax Receipting Void Receipts Process.

This topic discusses using the Void Receipts Tax Receipting Process to void one receipt, or a group of receipts at one time.

Void Receipts

  1. Access the Void Receipts page by using Millennium Explorer, Tools>Tax Receipting>Void.

  2. Select one of the Select Receipts to Void options

    • Select One receipt to void a single receipt, and enter the receipt number.

    • Select Receipt range to void a group of receipts within a range of receipt numbers. Enter values for both the start and end receipt numbers. The receipts selected for voiding will have numbers that fall within the range that you have entered, and include both start and end numbers.

    • Select Receipt run to void receipts that were generated during a particular Issue New Receipts receipt run process. You can enter a value for the receipt run number or

      1. Click Select to choose from a list of existing receipt runs. The Please select a receipt run form displays.
      2. Click the desired receipt run.
      3. Click Select.

    • Check With receipt prefix to void receipts that have a specific prefix, and enter that prefix in the text box. This option is combined with one of the other Receipts to Void options. Receipts that are selected must also have this prefix.

  3. Select the Printing and Output option.

    Select Generate summary report to create a report that lists, for each constituent, the receipts, and the receipts selected transactions, that have been selected for reprinting.

  4. Clear the Trial Run flag if you do not want to review the summary report before voiding the receipts.

    It is a best practice to do a trial run before committing to the final Void receipts run. Voiding cannot be reversed.

  5. Click Run to execute the Void Receipts process. To remove all of the process options selections that you have made (it is not necessary to do so), click Clear.

    Important! After Run is clicked, there will be no opportunity to undo the Void Receipts process. It is highly recommended that you do a Trial Run first!

  6. To exit the Void Receipts page, select your next task from the Millennium Explorer.

The Void Receipts Progress Page

While the Void Receipts Tax Receipting Process is in progress, the Receipting in Progress page displays. Hyperlinks are available to open this page in a new browser window or tab, our browser configuration, and to refresh this page during the process.

The Receipting in Progress page may include the following sections, at different points in the process.

Progress

After the Preprocessing step, additional Progress information is displayed.

Summary Report

The Summary Report section will display at the Complete Step. It will display only if you selected the Generate summary report process option.

Finish

Click Finish when done. This cleans up the temporary tables that are created during processing, and returns you to the Void Receipts page.

Notes:

Top of Page

Manual Receipts

An example of a manual receipt is a door-to-door canvasser for cash gifts who will issue a handwritten receipt on the spot. These receipts could be pre-numbered, and include a carbon copy that the canvasser submits to the charity along with the donation. Receipt information can then be entered into the system at the time that the donation is entered, or it can added to the donation at a later time.

The ability to add a manual receipt to a single Gift or Dues transaction is available only to the users who have been given permission to do so. See User Maintenance, Configuring Serial Receipts for more information.

Add Manual Receipt Information to a New Gift or Dues Transaction

  1. Follow the procedures for either creating a Simple Gift Transaction, or Posting a Pledge Payment if the transaction is paying down an existing pledge, but do not click Insert.
  2. Under Special Options, check Add Manual Receipt.
  3. Click Insert. The Add Manual Receipt form displays.
  4. Enter values for the receipt Prefix and the receipt Number. The receipt Number is mandatory.

  5. Default values for the receipt Amount and Date are based on the Deductible Amount and Process Date of the transaction, but these values can be changed.

    The receipt Amount must be less than or equal to the deductible amount of the transaction.

  6. Click Insert to create the receipt. Or, click Cancel to create the transaction without creating the receipt.

Important! If you are posting a payment on a pledge that already has other payments, the manual receipt that you are adding will include this payment plus all of the other payments on the pledge that have not yet been receipted. If the sum of the payments on the pledge does not exceed the pledge's non-deductible amount, then the manual receipt cannot be added.

Add Manual Receipt Information to an Existing Gift or Dues Transaction

  1. Access the Gift or Dues display for the constituent who owns the transaction to which you want to add a receipt by using Millennium Explorer, Profiles > Giving or Profiles > Dues.
  2. Scroll, if necessary, to display the specific transaction.
  3. Point to the Edit button edit button located to the left of the transaction and click Add Manual Receipt. The Add Manual Receipt page displays.
  4. Enter values for the receipt Prefix and receipt Number, as desired. The receipt Number is mandatory.

  5. Default values for the receipt Amount and Date are based on the Amount and Process Date of the transaction, but these values can be changed.

    The receipt Amount must be less than or equal to the deductible amount of the transaction.

  6. Click Insert to create the receipt. Or, click Cancel to halt the process and return to the display.

Important! If you are posting a payment on a pledge that already has other payments, the manual receipt that you are adding will include this payment plus all of the other payments on the pledge that have not yet been receipted. If the sum of the payments on the pledge does not exceed the pledge's non-deductible amount, then the manual receipt cannot be added.

Add Manual Receipt Information to a New Joint Gift or Dues Transaction

  1. Follow the Add Manual Receipt Information to a New Gift or Dues Transaction procedure, but instead of creating a Simple Gift, you will be creating a Joint Gift (or posting a pledge payment on a Joint Pledge).
  2. After the Manual receipt is created, click on the Joint With name hyperlink to access Linked Giving Detail display for the joint side of the transaction.
  3. Follow the Add Manual Receipt Information to an Existing Gift or Dues Transaction procedure, starting with Step 3.

Edit Manual Receipt Information

Manual receipt information cannot be edited. You must void the receipt, and then add it to the existing transaction again.

Reprint a Manual Receipt

A manual receipt cannot be reprinted.

Void a Manual Receipt

  1. Access the Serial Receipts display for the constituent by using Millennium Explorer, Profiles > Giving > Serial Receipts.

  2. Scroll, if necessary to display the specific receipt.

    Tip: The Serial Receipts display will include both Manual receipt information and information about receipts that were generated by using the Issue New Receipt Tax Receipting Process. The Manual field in the receipt record's display will have a value of Yes if the receipt was added manually to a transaction.

  3. Point to the Edit button edit button located to the left of the receipt and click Void. A confirmation message displays.
  4. Click OK to void the receipt, or click Cancel to halt the process and return to the display.
Notes:

Top of Page

Void Single Receipt

Existing serialized receipts can be voided one at a time by using the Serialized Tax Receipting Void Single Receipt component. Both Manual Receipts and receipts that were generated by using the Issue New Receipt Tax Receipting Process can be voided by using this component. Receipts that were generated by using the Issue New Receipts Tax Receipting Process can also be voided one at a time or in groups by using the Void Receipts Tax Receipting Process. This topic discusses voiding receipts one at a time by using the Void Single Receipt component.

Once a receipt for a transaction is voided, a new receipt for the transaction can either be generated by using either the Issue New Receipt Tax Receipting Process or by adding it as a Manual Receipt to the transaction.

The ability to utilize the Void Single Receipt component is available only to the users who have been given permission to do so. See User Maintenance, Configuring Serial Receipts for more information.

Void a Single Receipt

  1. Access the Serial Receipts display for the constituent by using Millennium Explorer, Profiles > Giving > Serial Receipts.
  2. Scroll, if necessary to display the specific receipt.
  3. Point to the Edit button edit button located to the left of the receipt and click Void. A confirmation message displays.
  4. Click OK to void the receipt, or click Cancel to halt the process and return to the Serial Receipts display.

Serial Receipts Display

Access the Serial Receipts display for a constituent by using Millennium Explorer Profiles>Giving>Serial Receipts.

Serial Receipts will display a constituent's serialized receipts and voided receipts. The data can be displayed in Long, Short, or Mini Display mode. The long display shows the transactions that are included in the receipts, including the date, amount, and the transaction type. What fields display, and their labels, can be customized for each of these display modes for each of these data tables via the Profiles version of the Custom Display Designer.

The Serial Receipts Header menu contains items to sort and filter the constituent's receipts, change the page display, and a link to Help. The menu for each Serial Receipt row contains items to void the receipt (for non-voided receipts) and a link to help.

Top of Page

Formatted Printed Receipts

Printed receipts are formatted by using Crystal Reports. The formats are located in the inetpub/wwwroot/mill/Windows/serialreceipt directory on the IIS machine. In addition to the existing formats, sites can create their own custom receipt formats. Save custom formats to this same directory and they can be available to select in the Select Formats list box when Issuing New Receipts and Reprinting Receipts.

Millennium includes the following four standard Receipt formats:

For the standard receipt formats, the temporary table that is generated during the receipt process supplies variable data such as constituent name and address, receipt amount, and details about Giving in Kind or Quids, if applicable. See Serial Receipt Worktable Layout for details about the structure of this table.

The following table details what static data is hard-coded on the formats, and what static data is passed to the formats either through parameters or other programmatic means. (STR = Serialized Tax Receipting)

Data

Displayed on Formats by

Crystal Parameter Name

Millennium Details

This is an official receipt statement.

Hard coded on formats

n/a

n/a

Logo (only appears on SerialReceiptSingleDonation)

Link to a jpg file

n/a

SerialReceiptLOGO.jpg is included in the inetpub\wwwroot\mill\windows\serialreceipt folder. It is sized 4.66 x 1.56 inches. The picture is the word ’LOGO’. A site can replace it with own LOGO jpg, keeping the same name, and same dimensions.

Charity Name

Crystal parameter

tax charity name

As entered on the System Options (STR) Setup page, Organization Name

Charity Address

Crystal parameter

tax charity address

As entered on the System Options (STR) Setup page, Organization Address

Charity, Phone, Fax, Web

Crystal parameter

tax charity phonefaxweb

As entered on the System Options (STR) Setup page, Organization Phone, Fax, Internet

Registration Number

Crystal parameter

tax charity registration

As entered on the System Options (STR) Setup page, Registration Number

Receipt Issued Location

Crystal parameter

tax charity location

As entered on the System Options (STR) Setup page, Location Receipt Issued

Name of an individual authorized by the charity to acknowledge donations

Crystal parameter

tax charity authorizer

As entered on the System Options (STR) Setup page, Name to appear under signature

Signature of an individual authorized by the charity to acknowledge donations

Link to a jpg file

n/a

SerialReceiptSignature.jpg is included in the inetpub\wwwroot\mill\windows\serialreceipt folder. It is sized 2.42 x .76 inches. The picture is ’empty'. A site can replace with its own signature jpg, keeping the same name, and same dimensions, or continue to use the empty one if they wish to hand-sign the receipts.

Name of Canada Revenue Agency

Crystal parameter

tax charity agency

As entered on the System Options (STR) Setup page, Federal Agency’s name

Web Address of Canada Revenue Agency

Crystal parameter

tax charity website

As entered on the System Options (STR) Setup page, Federal Agency’s website

Top of Page

Configuring Serialized Tax Receipting

Millennium system administrators or the database administrator must complete the following steps to configure Serialized Receipts:

Serialize Tax Receipting Options

Enable Serialized Tax Receipting, specify default receipt options, and enter the static information that will be printed on every receipt on the System Options page. For more information, see System Options, Serialized Tax Receipting.

User Security

Configure user security for every user that needs to access the Serialized Tax Receipting components. For more information, see Configuring User Security for Serial Receipts.

Customize Display and Maintenance Forms

Display and maintenance forms can be changed to add fields that are not included on the standard forms, to remove standard, but not required fields, to change labels, and to change the placement of the fields on the forms. Customizing the Serialized display forms is not a required configuration. Add the Default Issue Serialized Receipt flag to the Basic Data maintenance form or to the Giving and Dues maintenance forms if you want transactions to be eligible for selection by the Issue New Receipt Tax Receipting Process. You may, of course, add the flag to both the Basic Data and Giving/Dues forms to allow for maximum flexibility during data entry.

Refer to the Custom Display Designer topic for complete instructions on customizing display and maintenance forms.

Customize Serial Receipts Display Forms

  1. Access the Profiles version of the Custom Display Designer by using Millennium Explorer, Tools>Display Design>Profiles.
  2. Click the Profiles menu. Point to Giving. Click Serialized Receipts if customizing the receipt information display. Click Serialized Payments if customizing the display of the transactions that are included on the receipt.
  3. Click Display Type and click on the desired Display Type menu item (for example, Long or Short).
  4. Utilize the Custom Display Designer's editing tools to make your customizations.
  5. Click Save to save and apply your changes.

Add the Default Issue Receipt Flag to the Basic Data Display and Maintenance Forms

  1. Access the Profiles version of the Custom Display Designer by using Millennium Explorer, Tools>Display Design>Profiles.
  2. Click the Profiles menu. Point to Biographical. Point to Basic Data. Click Individual.
  3. Click Display Type and click on the desired Display Type menu item (for example, Long, Maintenance, Short).
  4. Utilize the Custom Display Designer's editing tools to make your customizations.
  5. Click Save to save and apply your changes.
  6. Add the flag to the display and maintenance forms for Corporation and Foundation Type Basic Data forms by repeating the steps, but instead click on the Corporation or Foundation menu items on Step 2.

Add the Issue Serialized Receipt Flag to the Giving and Dues Display and Maintenance Forms

  1. Access the Profiles version of the Custom Display Designer by using Millennium Explorer, Tools>Display Design>Profiles.
  2. Click the Profiles menu. Point to Giving. Click the menu item that represents the form on which you are adding the flag. For example, click Main Insert to add the flag to the Main Insert form. Click Payment to add the flag to the Payment display and maintenance forms.
  3. Click Display Type and click on the desired Display Type menu item (for example, Long or Short).
  4. Utilize the Custom Display Designer's editing tools to make your customizations.
  5. Click Save to save and apply your changes.
  6. Add the flag to the Dues Display and Maintenance Forms by repeating the steps, but instead point to Dues on Step 2.

An Millennium user with the correct permissions to view and maintain Basic Data data completes this step.

Assign a Default Receipt Issue Flag to Constituents

This flag will determine the default value of the Issue Serialized Receipt Flag every time a new Gift or Dues transaction is entered. This is not a necessary configuration. If a default Issue Serialized Receipt flag is not assigned, then the value of the flag on each new Gift or Dues transaction will default to No. When inserting a transaction or updating an existing transaction, you can change the default value of the Issue Serialized Receipt flag.

  1. Access the Basic Data display for the constituent.
  2. Point to the Edit button edit button located at the start of the record (not the Header) and click on Update/Delete.
  3. Navigate to the Issue Serialized Receipt field and select No, Yes, or Hold from the list box.
  4. Click Update to save your changes.

Top of Page

Journal Receipted Giving and Dues Transactions

Delete Receipted Giving and Dues Transactions

Pledge and Pledge Payment Transactions and Serialized Tax Receipting

Top of Page

Serial Receipts Table Field Descriptions

A row is created in the serialreceipt data table for every receipt that is generated by an Issue New Receipt Process receipt run.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: Each time that the Issue New Receipt Process is run, one row will created in the serialreceipt_run system table. The row in the serialreceipt_run system table is the way to link together all of the rows in the serialreceipt data table that are created in one run. Refer to the System Tables topic for more information about the serialreceipt_run system table.

Field Name

Field Label

 Lookup Table

Type SQL/Oracle

Length

[Default]

{Check}

 Description

sreckey

none

number/numeric

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)

srecid

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. This is automatically entered by the system. (system field)

srecdoc

none

char

1

['N']

 

This field holds a Y/N flag to indicate the existence of a linked document for this row. (system field)

srecdate

none

datetime/date

 

[getdate()]

 

The date that this row was last updated. This field is automatically entered by the system. (system field)

srecuserid

none

varchar/varchar2

30

[suser_sname()]

 

The User ID of the operator who last edited this row. It is automatically entered by the system. (system field)

srecugroup

none

char

1

 

 

This field holds the Group letter that was associated with the User ID of the operator who last edited this row. (system field)

srecprefix

Prefix

none

char

4

 

 

Receipt prefix

srecnumber

Number

none

char

10

 

 

Receipt number

srecamount

Amount

none

money/number

(19,4)/(16,2)

[0]

 

Receipt amount

srectotal

none

money/number

(19,4)/(16,2)

[0]

Payments total

srecnonttl

none

money/number

(19,4)/(16,2)

[0]

 

Non-receiptable payments total

srecmindte

none

datetime/date

 

 

 

Minimum donation date of payments

srecmaxdte

none

datetime/date

 

 

 

Maximum donation date of payments

srecyear

none

char

4

 

 

Donation year of payments

sreccount

none

numeric/number

8,0

[0]

 

Payments count (system field)

srecgendte

none

datetime/date

 

 

 

Receipt generated date (system field)

srecprntdt

none

datetime/date

 

 

 

Most recent reprint date (system field)

srecprntct

Print Count

none

numeric/number

8,0

[0]

 

Receipt print count (system field)

srecvoid

Void

none

char

1

 

 

Void flag (system field)

srecrunnmb

Run Number

none

numeric/number

4,0

 

 

Receipt run number (system field)

srecmanual

Manual

none

char

1

 

 

Manual receipt flag (system field)

srecsource

source_types

char

6

 

 

Indicates the source of the information contained in this data row.

srecfnum

none

char

2

['43']

{'43'}

The table number of the current table (system field)

sreccrdate

Create Date

none

datetime/date

 

[getdate()]

 

Indicated the date that this constituent's row was created in the system. This field is automatically entered by the system and may reflect the date of conversion if your prior system did not maintain this data. (system field)

sreccruser

none

varchar/varchar2

30

[suser_sname()]

 

The User ID of the operator who created the row. (system field)

sreccomm

none

varchar/varchar2

4000

 

 

A free text Comment that may be entered and displayed with this row only.

srecdate1

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate2

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecmny1

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.

srecmny2

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.

srecnum1

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.

srecnum2

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.

srecyesno

none

char

1

[N]

{'Y' or 'N'}

This custom field may be defined and used by your institution to flag this data row for any purpose.

sreclook1

receipts_lookup1

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.

sreclook2

receipts_lookup2

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.

sreclook3

receipts_lookup3

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.

srectext

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.

srecdate3

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate4

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate5

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate6

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate7

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate8

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdate9

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdte10

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdte11

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecdte12

none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

srecmny3

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.

srecmny4

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.

srecmny5

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.

srecmny6

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.

srecmny7

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.

srecmny8

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.

srecmny9

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.

srecmny10

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.

srecmny11

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.

srecmny12

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.

srecnum3

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.

srecnum4

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.

srecnum5

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.

srecnum6

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.

srecnum7

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.

srecnum8

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.

srecnum9

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.

srecnum10

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.

srecnum11

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.

srecnum12

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.

srecchk1

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk2

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk3

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk4

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk5

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk6

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk7

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk8

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk9

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srecchk10

none

char

1

[N]

{"Y" or "N"}

This custom field may be defined and used by your institution to flag this data row for any purpose.

srectxt1

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.

srectxt2

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.

srectxt3

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.

srectxt4

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.

srectxt5

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.

Basic Data

The Basic Data row is the fundamental information associated with a constituent. Every constituent will have one and only one Basic Data row. The creation of that row is the action that defines a constituent on the system. The information that is displayed from Basic Data will vary depending on whether the constituent is an Individual, a Corporation, or an Organization. Therefore, there are three standard "versions" of the Basic Data row. While all Basic Data table rows contain the same set of data columns, some of those fields will be used by all three types, some by two of the three, and some by only one type of constituent.

For example, the Basic Data includes a field for marital status. That field will be unused in Basic Data rows belonging to corporations or foundations. It will not appear in the data maintenance forms (standard) or in the display (standard) of the Basic Data for those constituents.

These variations are controlled by the Group field from the Constituent Type lookup table entry that you choose for the data row. Once the Basic Data row is created, if the Constituency Type is edited in a way that changes the constituent from a person to a corporation or other (based on the information in the Group field of the entries in the Constituent Type lookup table), or vice versa, the system will automatically edit the Basic Data row and remove the data from fields that do not apply to the new Constituent Type.

If the type is changed from Person to Corporation or Other, those fields are: coresex, coremaritl, corechflag, corechnum, corebirthd, coressnum, coreparpyr, coreparsch, coreprefyr, coreprfsch, coreethnic, corebcntry, coregrnpyr, corebrthyr, corebrthmn, corebrthdy.

If the type is changed from Corporation or Other to Person, those fields are: coreindust (Corporation only), corefntype (Foundation/Organization Only), coretotemp, corekwnemp, corealmemp, corerlkey1, corerlkey2, corecorpid, coreallsub, corekwnsub, corepropm1, corepropd1, corepropm2, corepropd2, corepropm3, corepropd3, coremduem1, coremdued1, coremduem2, coremdued2, coremduem3, coremdued3, coremduem4, coremdued4, coremnamt1, coremxamt1, coremrat1, coremnamt2, coremrat2, coremnamt3, coremxamt3, coremrat3, matchcomm, coremtchid.

Note: Millennium system administrators or the database administrator can configure audit logging for the Basic Data table. For more information, see Audit Log.

Basic Data - Individuals

In general, the Basic Data row for Individuals contains fields for which there is but one set of information per constituent, such as birthdate, gender, marital status, birth country, etc. In addition, while the Education table may hold several rows of information about actual attendance and degrees held, the Basic Data holds information about the year and school that the constituents prefer as their primary association, either for themselves or for their children.

You may associate any number of Citizenship rows with a Basic Data row belonging to an Individual. These may be used to track information on nationality, citizenship, passports, visas, etc.

You may attach, or link, multiple Attribute rows to a Basic Data row. These Attributes will always display with the Basic Data row to which they are attached. And if the Display Linked Attributes in the Attribute Display User Option is checked, they will also display with the constituent's other attributes. These linked Attributes might be used to record additional constituency types that apply to the constituent (an alum who is also a parent, for example).

You may also attach one photo to a constituent's basic data form (see Attachments).

The Data Maintenance, Link New to Existing and Data Maintenance, Link Existing to Existing topics discuss the creation and maintenance of linked Attributes in more detail.

An individual's Marital Status field is automatically updated when certain other data is entered in Millennium.

Basic Data - Corporations

The Basic Data for corporations includes information relevant to the corporate constituent. Information can be maintained about the parent corporation, subsidiaries, number of employees, proposal deadlines, and matching information.

When inputting a parent corporation, the system automatically creates the appropriate parent corporation/subsidiary relationship for the parent corporation and the subsidiary. In doing this, the system links the parent corporation and subsidiary Basic Data rows. On the subsidiary's Basic Data display, the name of the parent corporation appears as a hyperlink and executing that jump takes you to the Basic Data for the parent corporation. If a parent corporation name on an existing Basic Data row is removed, then the system will automatically delete the relevant parent corporation/subsidiary relationship.

When an Employment row is created for an individual that identifies a constituent corporation as the employer, the Known Employees field in the corporation's row is updated. In addition, if the CAE Category is 'A' (Alumni) on the Basic Data row for the individual, then the Alumni Employee field will also be incremented in the Basic Data row belonging to the corporation. Note that "Known Employees" refers to those employees who also have a constituent row in Millennium and therefore are "known" to the system. Alumni Employees are the subset of the Known Employees who are categorized as Alumni by their CAE Category.

Matching Information

Information about a corporation's matching policies is maintained in the Basic Data row. When the information is present and another constituent identifies the corporation as an employer, this matching information is available for use in determining whether to prompt for the creation of a matching giving transaction, and the calculation of the default amount for such a transaction.

Matching information may be handled in one of the following ways:

If a link is established either via the Match Through or the CorrectGM option, AND the Pull Matching Ratios from the Corporation system option is set to No, edits that are made to the matching entity's matching information will automatically be carried over to the original constituent's Basic Data. If the Pull Matching Ratios from the Corporation system option is set to Yes, edits that are made to the matching entity's matching information will not carry over to the original constituent's Basic Data.

Up to three matching gift ratios for different gift size ranges can be maintained, along with free text data on matching guidelines. These gift ranges and the associated ratios are used to calculate a default amount for the insert form for a matching pledge based on an employee's donation. That calculation is based solely on the gift size ranges of the ratios and the amount of the original donation - not on the multitude of other possible matching policies that the corporation may have in effect. The gift size ranges must be distinct, not overlapping, except for the amounts that are the 'boundaries' for the ranges. For instance, the first range might be $0 - $1000, the second range $1000 - $5000, and the third range $5000 - $10,000. If other factors (such as the donor's employment level or the purpose of the donation) affect the expected amount of the matching pledge, the default amount should be edited when the matching pledge transaction is created.

Basic Data for corporations also includes fields to maintain up to four dates to show when a corporation pays matching gifts. There are also four fields to indicate up to four different proposal deadlines.

Basic Data - Organizations

The Basic Data for an Organization includes information relevant to a variety of kinds of organizations. Information can be maintained about a parent corporation, subsidiaries, number of employees, and proposal deadlines. Current financial data such as total assets, expenditures, and grants can be documented.

When inputting the corporation of a corporate foundation, the system automatically creates the appropriate parent corporation/foundation relationship on the parent corporation and foundation rows. In doing this, the system links the two rows through this relationship. A click of the left mouse button on the parent corporation name hyperlink will take you to the Basic Data for the parent corporation.

When an Employment row is created for an individual that identifies a constituent foundation as the employer, the Known Employees field in the foundation's row is updated. In addition, if the CAE Category is 'A' (Alumni) on the Basic Data row for the individual, then the Alumni Employee field will also be incremented in the Basic Data row belonging to the foundation. Note that "Known Employees" refers to those employees who also have a constituent row in Millennium and therefore are "known" to the system. Alumni Employees are the subset of the Known Employees who are categorized as Alumni by their CAE Category.

Matching Information

Information about a foundation's matching policies is maintained in the Basic Data row. When the information is present and another constituent identifies the foundation as an employer, this matching information is available for use in determining whether to prompt for the creation of a matching giving transaction, and the calculation of the default amount for such a transaction.

Matching information may be handled in one of the following ways:

If a link is established either via the Match Through or the CorrectGM option, AND the Pull Matching Ratios from the Corporation system option is set to No, edits that are made to the matching entity's matching information will automatically be carried over to the original constituent's Basic Data. If the Pull Matching Ratios from the Corporation system option is set to Yes, edits that are made to the matching entity's matching information will not carry over to the original constituent's Basic Data.

Up to three matching gift ratios for different gift size ranges can be maintained, along with free text data on matching guidelines. These gift ranges and the associated ratios are used to calculate a default amount for the insert form for a matching pledge based on an employee's donation. That calculation is based solely on the ratio gift size ranges and the amount of the original donation - not on the multitude of other possible matching policies that the corporation may have in effect. The gift size ranges must be distinct, not overlapping, except for the amounts that are the 'boundaries' for the ranges. For instance, the first range might be $0 - $1000, the second range $1000 - $5000, and the third range $5000 - $10,000. If other factors (such as the donor's employment level or the purpose of the donation) affect the expected amount of the matching pledge, the default amount should be edited when the matching pledge transaction is created.

Basic Data for foundations also includes fields to maintain up to four dates to show when a foundation pays matching gifts. There are also four fields to indicate up to four different proposal deadlines.

CAE Category

When a Basic Data row is inserted, Millennium automatically populates the CAE Category field with the CAE that is associated with the Constituent Type that you have entered. This association is determined by the value of the table_cfae field in the Constituent Types (constituent_types) lookup table. And, if a Basic Data row is updated, and that update includes a change to the Constituent Type, Millennium will automatically update the CAE Category to the CAE that is associated with the Constituent Type via this table_cfae field.

For example, a Constituent Type of Alumni is associated with a CAE of 'Alumni'. If you insert a new constituent, with a Constituent Type of Alumni, into the database, the CAE field will auto-populate with 'Alumni'. In another example, a Constituent Type of Major Donor is associated with a CAE type of <blank>. If you update a record for a constituent with a Type of Individual and change her Constituent Type to Major Donor, the CAE field will auto-populate with a <blank>.

This behavior occurs automatically even if you have entered contradictory information for the CAE Category in the insert or update form. You may, however, override the automatic entry of the CAE Category by editing the Basic Data row once it has been created or updated. When you manually edit this field, the system will accept your inputted CAE in preference to the CAE that is associated with the Constituent Type lookup entry.

Display Death with Basic Data

If the Display Death with Basic Data system option is activated at your organization, then a constituent's Death record displays with Basic Data. If a constituent does not have a Death record, then the Death section header will not show. The Edit button edit button menu to the left of a constituents Basic Data record lists the Link > Death and Link > Death via Default items for you to use to create a new Death record for a constituent. For more information, see the System Options and Death topics.

Basic Data Field Descriptions

Basic Data is stored in the corebio 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. In addition, the Description will indicate whether the field is part of the default display for Individuals (I), Corporations (C), and/or Organizations (O). If you want to override these default settings, you must customize your display definition.

Field Name

Field Label

 Lookup Table

Type SQL/Oracle

Length

[Default]

{Check}

Description

Utilized by Basic Data rows belonging to Individuals (I), Corporations (C), and/or Organizations (O).

corekey

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 column)

I,C,O

coreid

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 column)

I,C,O

coredoc

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 column)

I,C,O

coredate

no label

 none

datetime/date

 

[getdate()]

 

The date that this Core row was last updated. This field is automatically entered by the system.(System column)

I,C,O

coreuserid

no label

 none

varchar/varchar2

30

[suser_sname]

 

The User ID of the operator that last edited this Core row. It is automatically entered by the system.(System column)

I,C,O

coreugroup

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 column)

I,C,O

coreconst

Constituent Type

 Constituent Types

char

6

[' ']

 

The Constituent Type field is used to classify constituents according to the standards or needs of your institution. You may have a need to categorize your constituents in a way other than the more rigid categories established by the CAE. This lookup table and field allow you to do so. (for example, Alumni, Friend, Individual, Patient, Foundation, Corporation, Religious Organization, etc.). (Don't confuse this field with the CAE Category.).

I,C,O

coresex

Gender

 none

char

1

 

{'C' or 'M' or 'F' or 'X' or ' '}

Indicates the gender of this constituent. The field may be left blank, it may be M for male, F for female, X for non-binary, or C to indicate that this row is a combined row for a spousal pair.
Note that gender information is one of the considerations when System-generated Names are created. If this information is not available when spouse combined name forms are created, results may vary.

I

coremaritl

Marital Status

 Marital Status

char

6

[' ']

 

Indicates the marital status of this constituent. If this field is set to Married and then a Death data row is entered for the constituent, this field is automatically set to Deceased Spouse, and if there is a constituent spouse, this field is set to Surviving Spouse. If a non-constituent spousal Relationship is changed to Deceased Spouse/Surviving Spouse, the Marital Status is also changed accordingly. If a spousal

I

corechflag

 

 none

char

2

 

{'>=' or '=' or ' '}

Indicates your certainty of the information in the corechnum field. This field may be blank, it may be "=" or it may be ">=" (to indicate that you know that the constituent has at least the number of children indicated in corechnum, but you are not confident that is the exact number of children).

I

corechnum

 

 none

char

2

 

 

Indicates the number of children that you know the constituent to have.

I

corebirthd

Birthday

 none

datetime/date

 

 

 

Indicates the birth date of this constituent.

Note that each institution may choose to use this field OR the separate month, day and year fields (corebrthmn, corebrthdy, corebrthyr) and edit their display and data maintenance definitions accordingly. Using one option will not automatically populate the field(s) for the other option.

I

coressnum

Social Security Number

 none

char/

240

 

 

 Indicates the value of the Social Security Number of this constituent. Value will be stored in this data row encrypted, but displayed as unencrypted. Field only accepts numeric entries.

corealtid

Alternate ID Number

 none

char

20

 

 

An alternate ID for this constituent. Often used if the constituent resides on another database within the institution.

I,C,O

coreparpyr

Parent Year

 none

char

4

 

 

Indicates the year that this constituent's youngest child will graduate from the institution. This is a four-digit year between 1600 and 2200.

I

coreparsch

Parent School

 Schools

char

6

[' ']

 

Indicates the school within your institution from which this constituent's youngest child will graduate.

I

coreprefyr

Preferred Year

 none

char

4

 

 

Indicates the class with which this constituent prefers to be associated. This is a four-digit year between 1600 and 2200.

I

coreprfsch

Preferred School

 Schools

char

6

[' ']

 

Indicates the school within the institution which this constituent prefers to be associated.

I

coreethnic

Ethnic Group

 Ethnic Groups

char

6

[' ']

 

Indicates the ethnic group with which this constituent is to be associated.

I

coreindust

Industry

 Industries

char

6

[' ']

 

Indicates the industry with which this corporation is affiliated.

C

corefntype

Type

 Foundation Types

char

6

[' ']

 

Indicates the type of foundation or organization represented in this row.

O

coretotemp

Total Employees

 none

numeric/number

10,0

[0]

 

Indicates the total number of employees for the corporation.

C,O

corekwnemp

Known Employees

 none

numeric/number

10,0

[0]

 

Indicates the total number of employees of this corporation who have a constituent row in Millennium (and thus are "known" to the system.). This field is automatically updated when a Jobs row is created for a constituent that indicates an employment link between that individual and this corporation. (System column)

C,O

corealmemp

Alumni Employees

 none

numeric/number

10,0

[0]

 

Indicates the total number of alumni employees. This field is automatically updated when a Jobs row is created for a constituent that indicates an employment link between that individual and this corporation and the individual has a CAE Category of A (Alumni). (System column)

C,O

corerlkey1

non-displaying

 none

numeric/number

13,0

[0]

 

If the corecorpid field includes the ID Number of a parent company, then this field will hold a copy of the key field from one half of the Relationship row that records that relationship.

C,O (System column)

corerlkey2

non-displaying

 none

numeric/number

13,0

[0]

 

If the corecorpid field includes the ID Number of a parent company, then this field will hold a copy of the key field from the other half of the Relationship row that records that relationship. (System column)

C,O

corecorpid

Parent Corporation

 none

char

10

 

 

This field displays the name of the parent corporation. During data entry the name or the ID number may be entered.

C,O

coreallsub

Subsidiaries

 none

numeric/number

10,0

[0]

 

Indicates the total number of subsidiaries this constituent parent corporation has.

C,O

corekwnsub

Known Subsidiaries

 none

numeric/number

10,0

[0]

 

Indicates the number of subsidiaries who are also constituents (and therefore "known" to the system) for this corporation. (System column)

C,O

corepropm1

Proposal Deadlines

 none

char

2

 

 

Indicates the first proposal deadline month.

C,O

corepropd1

Proposal Deadlines

 none

char

2

 

 

Indicates the first proposal deadline day.

C,O

corepropm2

Proposal Deadlines

 none

char

2

 

 

Indicates the second proposal deadline month.

C,O

corepropd2

Proposal Deadlines

 none

char

2

 

 

Indicates the second proposal deadline day.

C,O

corepropm3

Proposal Deadlines

 none

char

2

 

 

Indicates the third proposal deadline month.

C,O

corepropd3

Proposal Deadlines

 none

char

2

 

 

Indicates the third proposal deadline day.

C,O

corepropm4

Proposal Deadlines

 none

char

2

 

 

Indicates the fourth proposal deadline month.

C,O

corepropd4

Proposal Deadlines

 none

char

2

 

 

Indicates the fourth proposal deadline day.

C,O

corecrdate

Create Date

 none

datetime/date

 

[getdate]

 

Indicates the date that this constituent's row was created on the system. This field is automatically entered by the system and may reflect the date of conversion if your prior system did not maintain this data. (System column)

I,C,O

corecfae

CAE Category

 CAE Categories

char

6

[' ']

 

Indicates the category for this constituent as defined by the CAE. When a new basic data row is inserted, the triggers will automatically populate this field with contents of the table_cfae field of the constituent_types table. If a basic data row is updated, and that update includes a change in coreconst (Constituent Type), the update triggers will automatically change the value of corecfae. Override this behavior by editing the data row after insert or after update, and manually entering a corecfae code

I,C,O

coresource

Source

 Source

char

6

[' ']

 

Indicates the source of the information contained in the Basic Data row.

I,C,O

coremduem1

Matching Due Dates

 none

char

2

 

 

Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremdued1

Matching Due Dates

 none

char

2

 

 

Indicates the day from the first of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremduem2

Matching Due Dates

 none

char

2

 

 

Indicates the month from the second of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremdued2

Matching Due Dates

 none

char

2

 

 

Indicates the day from the second of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremduem3

Matching Due Dates

 none

char

2

 

 

Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremdued3

Matching Due Dates

 none

char

2

 

 

Indicates the day from the third of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremduem4

Matching Due Dates

 none

char

2

 

 

Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms.

C,O

coremdued4

Matching Due Dates

 none

char

2

 

 

Indicates the day from the fourth of four dates this company may use as a deadline for accepting matching gift forms.

C,O

corerest

Default Account

 Chart of Accounts

char

6

[' ']

 

The Default Account Number field allows you to identify an account number that will automatically be filled into the Insert form for gift or dues transactions for this constituent, when used in connection with the Default form creation of transactions. If you enter the word, "default" in the Account Number field of the Gift or Dues Default form, the transaction will be created, using the Default Account Number field in Basic Data as the Account Number for the Transaction.

You may ignore this account number when creating gifts or dues transactions by using the Insert rather than the Default form or by entering an account rather than the word, "default" in the Default definition.

When an account is entered for this field, the Account name from the lookup table is also copied to the coreacctnm field and it is that data that is shown in the display of Basic Data.

I,C,O

corettlbar

Title Bar

 none

char

60

 

 

The Title Bar field is a free text field of up to sixty characters. The text in this field will display in the title bar after the name. Some possible uses for this field might be to designate a Top Prospect, VIP or to remind operators Do Not Release Info. This field is simply free text and it is not the same as linking rows or entering data that will automate any other features.

I,C,O

corepoint

non-displaying

 none

numeric/number

10,0

 

 

 This system-assigned field is no longer used or supported. (System column)

coremnamt1

Min. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the minimum gift amount that this company will match for the first of three possible, distinct ratio range amounts

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremxamt1

Max. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the maximum gift amount that this company will match for the first of three possible, distinct ratio range amounts.

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremrat1

1st Match Ratio

 none

char

3

 

 

Indicates the first of a set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge.

If you are entering fewer than three ratios, you must use the first (the top field box) first.

 

If an Employment row identifies this constituent as the employer, AND if this coremratl field shows a matching ratio, the Employment row is automatically updated to set the jobsmflag field (Matching Company?) to Y.

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremnamt2

Min. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the minimum gift amount that this company will match for the second of three possible ratios.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

I,C,O

coremxamt2

Max. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the maximum gift amount that this company will match for the second of three possible ratios.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

I,C,O

coremrat2

2nd Match Ratio

 none

char

3

 

 

Indicates the second set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge.

 

If you are entering fewer than three ratios, you must use the first (the top field box) first.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremnamt3

Min. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the minimum gift amount that this company will match for the third of three possible, distinct ratios.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremxamt3

Max. Match Amount

 none

money/number

(19,4)/(16,2)

[0]

 

Indicates the minimum gift amount that this company will match for the third of three possible, distinct ratios.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

coremrat3

3rd Match Ratio

 none

char

3

 

 

Indicates the third set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge.

 

If you are entering fewer than three ratios, you must use the first (the top field box) first.

 

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM.

C,O

corelattr

non-displaying

 none

char

1

 

{'N' or 'Y'}

A flag to indicate whether or not this row has attached Attribute rows. (System column)

I,C,O

corebcntry

Birth Nation

 Countries

char

6

[0]

 

Indicates the country of birth for the constituent.

I

coretbltyp

non-displaying

 Table Groups

char

6

[0]

 

This is a copy of the Group field from the Constituent Type Lookup table entry that was chosen for the coreconst field. It signals the system for the appropriate use of the Individual, Corporation or Organizational form of the Basic Data page. It is automatically assigned by the system. (System column).

I,C,O

coreanon

non-displaying

 none

char

1

['N']

{'N' or 'Y'}

 This field is reserved for future use by Millennium. (System column)

corefnum

non-displaying

 none

char

2

['00']

{'00'}

The table number of the current table. (System column)

I,C,O

corecomm

not labeled

 none

varchar/varchar2

4000

 

 

A free text Comment that may be entered and displayed with this Basic Data row only.

I,C,O

matchcomm

Matching Guidelines

 none

varchar/varchar2

255

 

 

A free text Comment, used for additional details about a corporation or organization's matching gift policies.

C,O

coreactive

Active

 none

char

1

['Y']

{'N' or 'Y'}

This flag indicates whether the Basic Data row belongs to an "active" constituent.

I,C,O

corequidm

Match Quid

 none

char

1

['N']

{'Y' or 'N'}

If the constituent is a matching gift company, this flag indicates whether they will or will not match the quid pro quo portion of the original constituent's gift.

C,O

coregrnpyr

Parent Year

 none

char

4

 

 

Indicates the year that this constituent's youngest grandchild will graduate from the institution. This is a four-digit year between 1600 and 2200.

I

coreacctnm

Default Account

 Chart of Accounts

varchar/varchar2

80

 

 

This field holds a copy of the Account Name for the Default Account (corerest).

I,C,O

coredate1

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate2

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coremny1

 

 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.

I,C,O

coremny2

 

 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.

I,C,O

corenum1

 

 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.

This field is available for Profile Searches.

I,C,O

corenum2

 

 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.

I,C,O

coreyesno

 

 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.

I,C,O

corelook1

 

 Corebio Lookup1

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.

I,C,O

corelook2

 

 Corebio Lookup2

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.

I,C,O

corelook3

 

 Corebio Lookup3

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.

I,C,O

coretext

 

 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.

I,C,O

corepublsh

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 Basic Data table are set to 'Published by Consent'. Otherwise, the corepub00 field flag in the Basic Data table will be used.

I,C,O

coremtchid

Match Through

 none

char

10

 

 

If the constituent is a Corporation or Foundation that matches donations made by its employees or others, but if the matching funds are actually administered and delivered by another entity (such as a foundation created specifically for such a purpose), this field is used to hold a copy of the ID Number of that entity - also a constituent. If thePull Match Ratios from the Corporation system option is set to No, then the matching information from the 'Match Through' constituent is automatically copied to the corresponding fields for the original constituent. The following fields will be copied: coremrat1, coremxamt1, coremnamt1, coremduem1 coremdued1, coremrat2, coremxamt2, coremnamt2, coremduem2, coremdued2, coremrat3, coremxamt3, coremnamt3, coremduem3, coremdued3, coremduem4, coremdued4, corequidm, corespmfl, coreretmfl, matchcomm, corempkey.

Note that if your institution uses the optional Millennium component CorrectGM, and if the constituent you identify in this field as the Match Through entity already has a link to an entity in the Match Parent table, that same linkage will be established for the initial constituent using the corempkey field.

During giving data entry if you have activated the option to have the system suggest matching pledge or match potential transactions, and if the coremtchid field is populated in the Basic Data for the matching employer, the insert form for the Match Pledge or Match Potential will automatically show the Match Through ID as the source of the pledge or potential, rather than the actual employer.

C, O

coreuserec

User Name

 none

char

30

 

 

If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the constituent's user name for logging onto your institution's member website.

I, C, O

corepwdec

Password

 none

char

240

 

 

If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the encrypted value of the constituent's password for logging onto your institution's member website.

I, C, O

corepub00

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Basic Data information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Basic Data information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub01

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Name information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Name information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub02

 

 none

char

1

['2']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Address information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Address information for all constituents via the eDirectory under Options for Publishing Tables.)

 

'2' = 'Do Not Hide'

'1' = 'Hide the Phone Number'

'0' = 'Hide'

 

I, C, O

corepub03

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Attribute information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Attribute information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub04

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Relation information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Relation information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub05

(not currently available for use)

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Giving information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Giving information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub06

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Employment information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Employment information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub07

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Education information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Education information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub08

(not currently available for use)

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Dues information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Dues information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub26

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Phone information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Phone information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub28

(not currently available for use)

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Membership information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Membership information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corejoint

(not currently available for use)

 none

char

1

['N']

{Not Null}

This field acts as a flag to indicate that any transactions that are created for this constituent should always, automatically be set to activate the Joint with Spouse option.

I

corespcrd

(not currently available for use)

 none

char

1

['N']

{Not Null}

This field acts as a flag to indicate that any transactions that are created for this constituent should always, automatically be set to activate the Credit for Spouse option.

I

coreothcrd

(not currently available for use)

 none

char

1

['N']

{Not Null}

If the constituent has any Relationship rows which have the Credit for Other (relothcrd) flag set to 'Y', the system will automatically set this flag to Y. (System column)

I,C,O

coreretmfl

 

 none

char

1

['N']

{Not Null}

If this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to flag whether they will do so for retired employees, as well as active employees.

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. (System column)

C, O

corespmfl

 

 none

char

1

['N']

{Not Null}

If this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to flag whether they will do so for gifts made by the spouse of employees.

If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. (System column)

C, O

corempkey

non-displaying

 none

numeric/number

(13,0)

 

{null}

If your institution uses the optional, Correct GM component of Millennium, and if this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to track the link to a corresponding row in the Match Parent table with a copy of the key field from that table. When such a link is established, AND if the Pull Matching Ratios from the Corporation system option is set to No, the system automatically copies data from the Match Parent table into the coremnamt1, coremxamt1, coremnamt2, coremxamt2, coremnamt3, coremxamt3, coremrat1, coremrat2, coremrat3, coreretmfl, and corespmfl columns. When the Match Parent table is periodically updated (a regular function of the CorrectGM component) those same fields will also be updated on the basis of this linkage IF the Pull Matching Ratios from the Corporation system option is set to No. (System column)

C, O

corebrthyr

 

 none

char

4

 

{null}

This field, along with corebrthmn and corebrthdy, provide an alternative to the use of the corebirthd field. This is a four-digit year between 1600 and 2200.

Your institution has the option to modify the display and maintenance definitions of the Basic Data row and replace the corebirthd (a true datetime/date field which includes all three pieces of the date) with all or some of the fields corebrthyr, corebrthmn, and corebrthdy which store the three pieces of information in separate columns. Using one option will not automatically populate the field(s) for the other option.

I

corebrthmn

 

 none

char

2

 

{null}

 See corebrthyr.

corebrthdy

 

 none

char

2

 

{null}

 See corebrthyr.

corehintec

 

 none

varchar

60

 

{null}

If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store a constituent's hint question. This would usually be a question provided by the constituent, along with an answer (coreanswec), used to verify the identity of the constituent before e-mailing a forgotten password for logging onto your website (corepwdec). (System column)

I, C, O

coreanswec

 

 none

varchar

20

 

{null}

If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store a constituent's answer to a hint question (corehintec). This is used to verify the identity of the constituent before e-mailing a forgotten password for logging onto your website (corepwdec). (System column)

I, C, O

coreupkey

non-displaying

 none

numeric/number

13, 0

 

 

 This field holds the Timekey of the pending data row that may be updated from the corebio_pending table.

corepend

Pending

 none

char

1

['N']

{Not Null}

 This field is a flag to indicate that this data row has linked information in the 'pending' Corebio 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 column)

core1passw

 

 none

char

1

['N']

{Not Null}

 This field is a flag to indicate that the user must change their password the next time the log in.

coreltmout

 

 none

datetime/date

[getdate]

 

{null}

 This field holds the date and time the 20 minute lockout started. After 20 minutes from this date and time the user can attempt their login again.

corestmout

 

 none

datetime/date

[getdate]

 

{null}

 This field holds the last date and time the user was actively logged in.

coreattmpt

 

 none

numeric/number

3, 0

['0']

{Not Null}

 This field holds the number of successive invalid log ins a user has attempted. After the third attempt the user will be locked out for 20 minutes.

corepub09

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Comments information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the Comments information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub81

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's email (via internetaddress table) information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the email (via internetaddress table) information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

corepub69

 

 none

char

1

['N']

{Not Null}

If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's custombio information may or may not be used for publication on your institution's website.

(Note that your institution will need to set the custombio information for all constituents via the eDirectory under Options for Publishing Tables.)

I, C, O

coredate3

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate4

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate5

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate6

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate7

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate8

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredate9

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredte10

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredte11

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coredte12

 

 none

datetime/date

 

 

 

This custom field may be defined and used by your institution to track any date information associated with this data row.

I,C,O

coremny3

 

 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.

I,C,O

coremny4

 

 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.

I,C,O

coremny5

 

 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.

I,C,O

coremny6

 

 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.

I,C,O

coremny7

 

 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.

I,C,O

coremny8

 

 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.

I,C,O

coremny9

 

 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.

I,C,O

coremny10

 

 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.

I,C,O

coremny11

 

 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.

I,C,O

coremny12

 

 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.

I,C,O

corenum3

 

 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.

I,C,O

corenum4

 

 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.

I,C,O

corenum5

 

 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.

I,C,O

corenum6

 

 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.

I,C,O

corenum7

 

 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.

I,C,O

corenum8

 

 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.

I,C,O

corenum9

 

 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.

I,C,O

corenum10

 

 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.

I,C,O

corenum11

 

 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.

I,C,O

corenum12

 

 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.

I,C,O

corechk1

 

 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.

I,C,O

corechk2

 

 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.

I,C,O

corechk3

 

 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.

I,C,O

corechk4

 

 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.

I,C,O

corechk5

 

 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.

I,C,O

corechk6

 

 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.

I,C,O

corechk7

 

 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.

I,C,O

corechk8

 

 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.

I,C,O

corechk9

 

 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.

I,C,O

corechk10

 

 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.

I,C,O

coretxt1

 

 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.

I,C,O

coretxt2

 

 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.

I,C,O

coretxt3

 

 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.

I,C,O

coretxt4

 

 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.

I,C,O

coretxt5

 

 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.

I,C,O

corelook4

 

 Corebio Lookup4

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.

I,C,O

corelook5

 

 Corebio Lookup5

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.

I,C,O

corelook6

 

 Corebio Lookup6

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.

I,C,O

coreocdin

 

 none

datetime/date

 

 

 

 Indicates the date and time the constituent last logged on to the Online Constituent Directory.

corealtid2

Alternate ID 2

 none

char

20

 

 

An alternate ID for this constituent.

I,C,O

corealtid3

Alternate ID 3

 none

char

10

 

 

An alternate ID for this constituent.

I,C,O

corealtid4

Alternate ID 4

 none

char

10

 

 

An alternate ID for this constituent.

I,C,O

corealtid5

Alternate ID 5

 none

char

20

 

 

An alternate ID for this constituent.

I,C,O

coreadesrc

non-displaying

 ade_source

char

30

If this row is created or updated from data that originally came from the corebio_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.

 
coreuserip none

char

40

If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the IP Address of the computer that the constituent used to log on to your institution's member website.

 
corephoto     <placeholder>

coreyercpt

Year-end receipts?

 

 none

char

1

 Selecting this option results in the constituent receiving one single tax receipt at the end of the year. Leave blank to issue tax receipts throughout the year as payments are received.

corecolsta

Collection Status

 

 none

char

6

This field is used by your institution to identify and categorize constituents who are delinquent with payments and/or outstanding pledges.

 

coredefdiv

Default Division Name

 

 campaign_division

char

12

 This field places your donors into categories that you have customized to suit your organization. Some examples are geography, demographics and giving history. When the data row is displayed, the value associated with this field is what you will be shown.

coreisrcpt

Issue Serialized Receipt

 

 none

char

1

 Select this option to indicate that a constituent should receive a serialized tax receipt for gifts, pledge payments, and dues transactions. Valid values are Y (Yes), N (No), and H (Hold).

corelang

Language Preference

 

 language_preference

char

6

 Indicates the preferred language of the constituent.

corestatdt

non-displaying

 

 none datetime This field is maintained by the system, and records the date the constituent's corestatus was last changed.

corestatus

Constituent Status

 

 none

char

6

This field is used by your institution to give a constituent an Active or Inactive status (such as Active, Inactive - deceased, Inactive - moved, Inactive - removed by request).

I,C,O

 

coreddivnm

Default Division Name

 campaign_division

varchar

120

 This field is maintained by the system, and contains the value corresponding to the selected coredefdiv code.

Custom Fields

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.

Indices - serialreceipt

Index Primary Foreign Unique Fields Sort

serialreceipt02

 

 

 

srecid

ASC

serialreceipt03

 

 

 

srecprefix

ASC

serialreceipt04

 

 

 

srecnumber

ASC

serialreceipt05

 

 

 

srecrunnmb

ASC

Top of Page

Serial Receipts Payments Table Field Descriptions

The serialreceipt_payment table is a linking table that links one or more transactions to a receipt in the serialreceipt table. It also stores information that will make reporting easier.

Field Name

Field Label

 Lookup Table

Type SQL/Oracle

Length

[Default]

{Check}

 Description
spaykey none

numeric/numeric

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)
spayid 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 the all other tables which also belong to the same constituent. This is automatically entered by the system. (system field)
spaydoc none

char

1

 

 

 This field holds a Y/N flag to indicate the existence of a linked document for this row. (system field)
spaydate none

datetime/date

[getdate()]

 

 The date that this row was last updated. This field is automatically entered by the system. (system field)
spayuserid none

varchar/varchar2

30

[suser_sname()]

 

 The User ID of the operator who last edited this row. It is automatically entered by the system. (system field)
spayugroup none

char

1

 

 

 This field holds the Group letter that was associated with the User ID of the operator who last edited this row. (system field)
spaylnkfil none

char

2

 

 

 File number gifts/dues (system field)
spaylnkkey none

numeric/number

13,0

 

 

 Giving/dues key (system field)

spaytype

Type

 none

char

6

 

 

 Receivable type (system field)
spayrctky none

numeric/number

13,0

 

 

 Receipt key (system field)
spayrctnm none

char

10

 

 

 Receipt number (system field)

spayamount

Amount

 none

money/number

(19,4)/(16,2)

 

 

 Payment amount (system field)
spayrctamt none

money/number

(19,4)/(16,2)

 

 

 Receiptable amount (system field)
spaynonrct none

money/number

(19,4)/(16,2)

 

 

 Non-receiptable amount (system field)
spayjrnlfl none

char

1

 

 

 Journal flag (system field)
spaysource source_types

char

6

 

 

 Indicated the source of the information contained in this data row.
spayfnum none

char

2

['44']

{'44'}

 (system field)

spaycrdate

Create Date

 none

datetime/date

 

[getdate()]

 

 (system field)
spaycruser none

varchar/varchar2

30

[suser_sname()]

 

 (system field)
spaycomm none

varchar/varchar2

4000

 

 

 A free text Comment that may be entered and displayed with this row only.
spaypaykey none

numeric/number

13,0

 

 

 Payment key (system field)

Indices- serialreceipt_payment

Index Primary Foreign Unique Fields Sort

serialreceipt_payment02

 

 

 

spayid

ASC

serialreceipt_payment03

 

 

 

spayrctky

ASC

serialreceipt_payment04

 

 

 

spaylnkfil, spaylnkkey

ASC

Top of Page