The following types and codes are not fixed and therefore must be set up.
| Type | Fixed Code? | Description |
|---|---|---|
| ACK_LETTER | N | The types of acknowledgement letters. For example, New Donor Thank You or Pledge Payment Receipt Acknowledgement. This code is used on the Simple Gift Entry screen. |
| ACK_LETTER_SIGNOR | N | If an organization wants to create a merged letter that includes a particular signor at the organization, they would setup the signor(s) as a code value for ACK_LETTER_SIGNOR. This code is used on the Simple Gift Entry screen. |
| APPEAL_ACTIVITY | N | The method by which the appeal activity occurred. For example, Email, Mailing, Phone, Telethon. This code is used on the Appeal Definition and Maintenance screen. |
| APPEAL_CLASS | N | The classification of the appeal. For example, Email, Follow-up, Initial Appeal, or Phone. This field displays on the Appeal Definition and Maintenance screen. |
| ASSET_TYPE | N | The type of asset. For example, Annuity, Car, Fixed Asset, Gift, Land, Miscellaneous, Pledge, or Property. This code is used on the Planned Giving screen. |
| CAMPAIGN_CLASS | N | The classification of the campaign. This class code can be used for reporting purposes. For example, Building Campaign, Endowment Campaign, General Campaign, or Scholarship Campaign. This code is used on the Campaign Definition and Maintenance screen. |
| CAPABILITY | N | Capability is a value that represents a donor's capability to give. This value, along with an estimate of a donor's inclination to give, represents an organization's best judgement on how likely a prospect/donor is to make a donation. For example, ‘EXCELLENT’. This code is used on the Donor360® screen. |
| CAPABILITY_SCORE | N | Capability Score is similar to Capability. It is the numeric value for the amount of money that a donor is willing to donate to your organization. This score is assigned by a solicitor or fund development manager to the prospect/donor. It populates the Assigned Capability Score and Calculated Capability Score fields on the Prospect Moves Management Screen. This is generally represented by a numerical value, such as ‘$10,000’ or ‘$20,000’. This code is used on the Donor360 screen. |
| CREDIT_ROLE | N | A user-defined code that can be used to define additional roles, particularly for soft-credit records. For example, Volunteer and Solicitor. This code is used on the screens from which you can view hard and soft credits, including Donor360 and the Donation Entry screens. |
| CREDIT_TYPE | Y | A system-defined code that identifies whether the hard or soft credit record was created for a donor, ship-to customer, solicitor, employer, tribute customer, or bill-to customer. This code is used on the screens from which you can view hard and soft credits, including Donor360 and the Donation Entry screens. |
| CUSRELATION | N | If constituents are defined as related-customers on a fundraising gift product, this code identifies the role of the constituent. For example, author or vendor. This code is used on the Gift Setup screen. |
| DONOR_CLASS | N | The general classification of the donor. For example, Big Contributor, Corporate, Platinum, or Small Contributor. This field displays on the Prospect Maintenance screen. If a donor has requested that they not be solicited anymore for donations, you can use this field to create a "Do Not Solicit" Donor Class code. This code is used on the Donor360 screen. |
| DONOR_GIVING_CLASS | Y | A system-defined code that identifies whether a constituent is a prospect (meaning they have never made a donation), current donor, current major donor, past donor, or past major donor. What qualifies as a major donor and what time period qualifies as past is identified in the following Org-Unit Parameters: MAJOR_DONOR_THRESHOLD_AMOUNT and DONOR_TIMEFRAME_CODE. In addition, whether soft credits, unpaid pledges, or planned giving amounts are included in Donor Class calculations is defined by the following Org-Unit Parameters: INCLUDE_SOFT_CREDITS_IN_DONOR_CLASS_FLAG, INCLUDE_PLEDGES_IN_DONOR_CLASS_FLAG, and INCLUDE_PLANNED_GIVING_IN_DONOR_CLASS_FLAG. This field is kept current by triggers and the FND710 batch process. This code is used on the Donor360 screen. |
| DONOR_GIVING_STATUS | Y | A system-defined code that identifies whether a donor has never donated (NEVER), is a first time donor (FIRST_TIME) is a renewal donor (gave last year and this year), is a LYBUNT donor (last year but unfortunately not this year), or SYBUNT donor (some year but unfortunately not this year). This field is kept current by triggers and the FND710 batch process. This code is used on the Donor360 screen. |
| DONOR_TIMEFRAME | Y | A system-defined code that identifies the time frame since a donor's last donation that differentiates a current donor from a past donor. Valid values include CALENDAR_YEAR, FISCAL_YEAR, or LAST_12_MONTHS. This code is used on the Org Unit Setup screen. |
| EXPENSE_CLASS | N | The classification of the expense. For example, Direct Mail or Printer. This code is used on the Fundraising Expenses screen. |
| FULFILL_STATUS | Y | Typically this value is set to Active ("A"). It is only used for pledges to define if the pledge was cancelled ("C" - all of the money applied to the pledge is refunded) or terminated ("T" - the money paid to date is kept and the pledge amount is updated to whatever has been paid to date and no more payments will be applied to the pledge). This code is used on the Order Entry screen. |
| FUND_CLASS | N | The classification of the fund. This code can be used for classifying funds for reporting purposes. For example, Academic Fund, Endowment Fund, General Fund, PAC Fund, or Scholarship Fund. This code is used on the Fund Definition and Maintenance screen. |
| FUNDING_DISINTEREST | N | Funding Disinterest represents causes that a donor has specifically identified that they are not interested in funding. This code is used on the Donor360 screen. |
| FUNDING_INTEREST | N | Funding Interest represents causes that a donor is specifically identified that they are interested in funding. This code is used on the Donor360 screen. |
| GIFT_FREQUENCY | N | This code identifies how frequently a recurring gift donor's credit card will be charged. Valid values include MONTHLY, QUARTERLY, SEMI-ANNUALLY, and YEARLY. Although this code is not fixed, you should not add any additional codes. The No. of Months (Option 1) represents the number of months between credit card payments. This code is used on the Donation Entry screen when a recurring gift is created. |
| GRANT_HARD_CREDIT | Y | A system-defined code that identifies whether the hard credit should go to the bill-to customer or ship-to customer for donations. This is set to Bill-To by default in base Personify. Note that fundraising donations given via a membership donation product can be defined to give the hard credit to a different customer than defined here by the MBR_DONATION_HARD_CREDIT system type. This code is used on the Org-Unit Setup screen. |
| GRANT_SOFT_CREDIT | Y | A system-defined code that identifies whether the soft credit should go to the bill-to customer or ship-to customer for donations. This is set to Ship-To by default in base Personify. Note that fundraising donations given via a membership donation product can be defined to give the soft credit to a different customer than defined here by the MBR_DONATION_SOFT_CREDIT system type. This code is used on the Org-Unit Setup screen. |
| INCLINATION | N | Inclination is a value that represents a donor's perceived inclination to give. This value, along with an estimate of a donor's capability to give, represents an organization's best judgement on how likely a prospect/donor is to make a donation. Examples include ‘Hot’ or ‘Cold’. This code is used on the Donor360 screen. |
| INCOME_LEVEL | N | The range of income the donor earns in a fiscal year. For example, Under $100,000, Under $200,000, Under $400,000, under $50,000, or under $75,000. This code is used on the Donor360 screen. |
| INCOME_SOURCE | N | The source of the income range or level. For example, Census or Survey. This code is used on the Donor360 screen. |
| LETTER_TYPE | N | This is used in the Standard Letters Setup to specifically define these codes as Hard or Soft to filter the fundraising view for the merge letter. |
| LINE_STATUS | Y | Identifies the status of a donation order line. Valid values include Proforma (P), Active (A), and Cancelled (C). This code is used on the Order Entry screen. |
| MATCHING_GIFT_CREATION | Y | If the organization wants to have matching gifts created automatically for employers when an employee creates a donations, this code identifies when a matching gift is created on order (ON_ORDER) or on payment (ON_PAYMENT). This code is used on the Org-Unit Setup screen. |
| MATCHING_GIFT_PLAN_TYPE | Y | A system-defined code that identifies the donors whose donations will be matched. Currently, only employee matching gift plans are implemented. This code is used when the matching gift plan is defined. |
| MBR_DONATION_HARD_CREDIT | Y | A system-defined code that identifies whether the hard credit should go to the bill-to customer or ship-to customer for donations made via a membership donation product. This is set to Ship-To by default in base Personify. Note that regular fundraising donations can be defined to give the hard credit to a different customer than defined here by the GRANT_HARD_CREDIT system type. This code is used on the Org-Unit Setup screen. |
| MBR_DONATION_SOFT_CREDIT | Y | A system-defined code that identifies whether the soft credit should go to the bill-to customer or ship-to customer for donations made via a membership donation product. This is set to Bill-To by default in base Personify. Note that regular fundraising donations can be defined to give the soft credit to a different customer than defined here by the GRANT_SOFT_CREDIT system type. This code is used on the Org-Unit Setup screen. |
| NON_PLEDGE_CREDIT | Y | A system-defined code that identifies whether the hard credit for a non-pledge donation should be granted when the order is created (activated) or when a payment is made. By default, this is set to ORDCREATION. This code is used on the Org-Unit Setup screen. |
| PAYOUT_FREQUENCY | N | The frequency of the payout. For example, Monthly, Quarterly, Semiannually, or Yearly. This code is used on the Planned Giving screen. |
| PLAN_STATUS | N | The status of the plan. For example, Active, Pending, or Rejected. This code is used on the Planned Giving screen. |
| PLAN_TYPE | N | The type of plan. For example, Charitable Gift Annuity, Charitable Lead Annuity Trust, Charitable Lead Unitrust, Charitable Remainder Annuity Trust, Charitable Remainder Unitrust, Life Estate Agreement, or Pooled Income Fund. This code is used on the Planned Giving screen. |
| PLEDGE_CREDIT | Y | A system-defined code that identifies whether the hard credit for a pledge donation should be granted when the order is created (activated) or when a payment is made. By default, this is set to PAYMENT. This code is used on the Org-Unit Setup screen. |
| PROCESSING_STATUS | N | When donation receipts are entered through the Rapid Donation Receipt Entry screen, the system sets the status to identify how the receipt was applied, as well as whether the receipt has been finalized. Valid values include PENDING, PROCESSED, FAILED, AUTHORIZED, GIFT_CREATED, PLEDGE_CREATED, PLEDGE_PYMT, PYMT_MULTIPLE_PLEDGES, UNAPPLIED_RECEIPT, and PLEDGE_PYMT_AND_UAR. |
| PRODUCT_CLASS | N | Used to classify any gift (master or sub-product). The only gift class available for fundraising is “Donation.” This field displays on the Gift Code Maintenance screen. This code is used on the Gift Code Maintenance screen. |
| PRODUCT_TYPE | Y | A system-defined code that identifies the type of fundraising donation. Valid values include, CASH, PLEDGE, ASSET, INKIND, MATCHING_GIFT, PLANNEDGIVING, and STOCK. A product type of MEMO is also supported, which is used to record a "gift" without creating any financial transactions. This code is used on the Gift Code Maintenance screen. |
| PROPOSAL_STATUS | N | The status of the proposal. For example, Accepted, Pending, or Rejected. This code is used on the Proposal Maintenance screen. |
| RATE | N | The established rate determines the pricing for the Rate Structure selected. For example, Standard. This code is used on the Gift Code Maintenance screen. |
| RECORD_TYPE | Y | A system-defined code that identifies why a fund credit record was created. Valid values include, Fundraising Order (O), Payment (P), Adjustment (A), Writeoff (W), Donation made through a Membership product (DONATION), and Manual credit (MANUAL). This code is used on the Simple Gift Entry, Flexible Gift Entry, Order Entry, and Donor360 screens. |
| RECURRING_GIFT_STATUS | Y | A system-defined code that identifies the status of a recurring gift order line. Valid values include Active, Cancelled, Renewed, Rejected, and In Process. If an order line has a recurring gift status of renewed, it means it has already been paid and the next recurring gift order line has been created. If the status is rejected, it means the credit card payment could not be successfully processed. If the status is in process, it means the credit card is in the process of being settled by CCP610. This code is used on the Simple Gift Entry, Flexible Gift Entry, and Order Entry screens. |
| RELATION_STATUS | Y | If constituents are assigned to fundraising gift products, this system-defined code that identifies their status. Valid values include Assigned, Confirmed, and Invited. This code is used on the Gift Code Maintenance screen for related customers. |
| REVENUE_RECOG_METHOD | Y | A system-defined code that identifies when revenue is recognized on fundraising gifts. The only code supported is INVOICE. This code is used on the Gift Code Maintenance for GL Account setup. |
| SOLICITOR_ROLE | N | The classification of the solicitor that is used for reporting and grouping teams. For example, Manager or Solicitor. This code is used on the Solicitation Team Maintenance screen. |
| TASK_STATUS | Y | A system-defined code that identifies the status of a moves management task. The Option 1 column identifies whether the task status means that the task is completed. Option 1 is set to Y for SUCCESSFUL and UNSUCCESSFUL task status codes. When a task status marks a status as completed, the system will then calculate the due date for the next task based on task priority. This code is used on the Prospect Moves Management Plan screen. |
| TASK_TYPE | N | A user-defined code that allows organizations to categorize tasks assigned to prospect moves plans. This code is used on the Prospect Moves Management Plan screen. |
| TEAM_CLASS | N | The classification of the team that is used for reporting and grouping teams. For example, Main Team or Secondary Team. This code is used on the Solicitation Team Maintenance screen. |
| TRIBUTE_TYPE | N | A user-defined code (as of 7.4.1SP1) that allows organizations and donors to categorize the type of tribute for which a donation is being made. A tribute type can be assigned to a donation on the Donation Entry screens, and a tribute type can also be assigned to a Fund, Campaign or Appeal and to a Matching Gift Plan. Example tribute types include IN_MEMORY_OF, IN_HONOR_OF and IN_SUPPORT_OF. |
| COMM_LOCATION | N | This CUS system
type has three new codes for the Donor360 screen that when selected
with the Web communication type, will display the icon for each
social network site.
|
| CONSTITUENT_ROLE | N | This CUS type
is used for Constituent Roles that are maintained on all the individual
and company maintenance screens.
|