Converting Contributor Relations Data
This section lists prerequisites and discusses how to:
Populate tables for Contributor Relations.
Create accumulated records for gift and pledge inquiry.
Contributor Relations uses data from some of the other Campus Solutions applications. For this reason, you must set up Student Financials item types and related general ledger information as well as Human Resources departments before you can convert some of the contributor relations information.
At a minimum for Contributor Relations, set up these tables.
Organization Structure Tables
Populate these tables for organization structure:
Campus Community and Constituent Tables
Populate these tables for Campus Community and constituent data:
DISABILITY: required for PERS_DATA_EFFDT and PERSONAL_DATA to function properly.
DIVERSITY: required for PERS_DATA_EFFDT and PERSONAL_DATA to function properly.
ADDRESSES: to display or convert any address information, including that on PERSONAL_DATA.
AV_LEGACY_DEG: to convert alumni degree records if you do not want to create all previously existing academic structures in the student records tables.
Otherwise, all of the Student Careers and Plans and Student Degrees tables listed in the Converting Student Records Data section are required for tracking academic data.
Note: The EXT_ORG_ID field should be left blank for PeopleSoft data. This field is used to store data for external organizations. When dealing with an organization, you would leave EMPLID blank and load the EXT_ORG_ID for the organization.
Populate these tables for gifts:
AV_TRIBUTE_DTL: optional (In Honor Of or In Memory Of).
Populate these tables for pledge data:
AV_PLDG_SCHD: required for active pledges but optional for complete pledges.
AV_TRIBUTE_DTL: optional (In Honor Of or In Memory Of).
Populate all key fields, plus all other fields you can populate. The SESS_STATUS = O for trial runs but should ultimately be set to P for posted. The user ID is important here as it dictates security. (They can all have the same user ID, such as PS.) The ACKN_FLG field should be set to Y.
Populate all key fields, plus all other fields you can populate. The FISCAL_YEAR (CCYY) should be populated. The SESSION_NO should start with one and increment by one for every group of 100 records, if the organization chooses to abide by the recommendation of 100 records per session. The SEQ_NO should be 1 for historical data, provided these are all just gifts and not adjustments. The sequence is one for the original gift and increments (by two within the AV_GIFT_DTL table—for example 1, 3, and 5), with each adjustment made to the original gift. The SEQ_NO in the AV_ADJ_GIFT_DTL table increments with even numbers by two to indicate the offsetting record to the related AV_GIFT_DTL record. The ACKN_FLG field should be set to Y.
Note: If you don't want historical gifts to get an acknowledgement, then set the AV_SESSION_TBL. ACKN_FLG field to Y.
Populate all key fields, plus all other fields you can populate. This is not a setup table, but an allocation of the gift detail record to one or more designations.
Note: Amounts can default to the gift amount if there is only one designation or recognition per gift. If there is more than one designation or recognition per gift, then the amount fields need to be populated with actual amounts or percentages.
Populate all key fields, plus all other fields that you can populate. RCG_PCT_AMT and RCG_APPLIED should be mapped to gift amount (if there is only one recognition per gift). The RECOGNITION_TYPE = H for hard credit. For soft credit, there are different types (such as vehicle credit) that are defined by the institution. No soft credit Values are: delivered. RECOGNITION_TYPE is a setup value, with H being a delivered, required value.
Populate all key fields, plus all other fields that you can populate. RCG_DES_AMT and CHARITABLE_AMT should be mapped to gift amount (if there is only one recognition or designation per gift). For Soft Credit CHARITABLE_AMT = 0.
Note: For converted active pledges to have pledge payments made against them, the AV_SESSION_TBL.SESS_STATUS field for the pledge session must be set to P.
In Contributor Relations, the system runs Giving Profile and Commitment Summary online reports based on summary accumulator records rather than detailed transaction records. For the proper information to appear on these reports, you must initialize the summary accumulator records for all constituents and all gifts and pledges in the system. Contributor Relations delivers a Constituent Accumulator Initialization Application Engine process (AV_ACC) to perform this task. To access the process, selectWhen initialized, incremental accumulations take place for affected constituents during the Constituent Accumulator process. You can run this process either by itself or along with the GL Interface job.
The Constituent Accumulator Initialization process is a resource-intensive process that requires an extended background processing window. The process deletes and recalculates all data from the accumulator records (PS_AV_CNST_ACC, PS_AV_CNST_ACC_DES, and PS_AV_CNST_ACC_FY). If all transactions contained within in-process sessions are first completed (their session status changes to Posted), do not select the Search for unposted Pledge Payments and Search for unposted Matching Gifts options. This improves the performance of the initialization process.
Note: If you do not complete the initialization process, the system does not complete the information displayed online on the Giving Profile and Commitment Summary pages.
If additional groups of constituents are required to allow the process to complete within the particular background processing window, the records in the PS_AV_ACCUM_INIT table can be modified to include more, smaller groups. Remember, however, that additional occurrences of the temporary tables used by the AV_ACC Application Engine process are required if you run more than the delivered five processes at any one time.