banner advancement release guide · enter gift details, recognition items, solicitation...

What can we help you achieve?

Banner AdvancementRelease Guide

Release 8.1December 2008

Notice of Rights

Copyright © SunGard Higher Education 2008. This document is proprietary and confidential information of SunGard Higher Education Inc. and is not to be copied, reproduced, lent, displayed or distributed, nor used for any purpose other than that for which it is specifically provided without the express written permission of SunGard Higher Education Inc.

SunGard Higher Education

4 Country View RoadMalvern, Pennsylvania 19355United States of America(800) 522 - 4827

Customer Support Center Website

http://connect.sungardhe.com

Documentation Feedback

http://education.sungardhe.com/survey/documentation.html

Distribution Services E-mail Address

[email protected]

Other Services

In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization's own choosing.

Trademark

Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.

Revision History Log

Publication Date SummaryDecember 2008 New version that supports 8.1 Banner Advancement software

http://connect.sungardhe.com

http://education.sungardhe.com/survey/documentation.html

Contents

Banner Advancement 8.1Release Guide

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Section 1 Gift Mass Entry - Functional

Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Default gift information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Individual gift information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Gift details and giving history details . . . . . . . . . . . . . . . . . . . . . . . .10

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Enter mass gifts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Add or change information for individual gifts. . . . . . . . . . . . . . . . . . . .12

Balance gift amount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Save pending gift transactions . . . . . . . . . . . . . . . . . . . . . . . . . . .13

New form - Gift Mass Entry Form (AGAGMAS) . . . . . . . . . . . . . . . . .14

Gift Defaults window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Gift Defaults block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Benefits Information block. . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Solicitation Information block . . . . . . . . . . . . . . . . . . . . . . . . . . .16Campaigns and Designations block. . . . . . . . . . . . . . . . . . . . . . . .17

IDs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18IDs block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Gift Detail block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Campaigns/Designations block . . . . . . . . . . . . . . . . . . . . . . . . . .21Solicitation block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Benefits block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Changed menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

December 2008 Banner Advancement 8.1 3Release Guide

Contents

Section 2 Enhanced Proposal Processing - Functional

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Create a new proposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Enter project results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Changed forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Prospect Contacts Form (AMACONT) . . . . . . . . . . . . . . . . . . . . . . .29

Advancement Prospect Information Form (AMAINFO) . . . . . . . . . . . . . . .29

Prospect Proposal Form (AMAPROP) . . . . . . . . . . . . . . . . . . . . . . .30Key block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Proposals window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Proposal Change History window . . . . . . . . . . . . . . . . . . . . . . . . .36Project Change History window . . . . . . . . . . . . . . . . . . . . . . . . . .38

Moves by Prospect Form (AMAPROS) . . . . . . . . . . . . . . . . . . . . . . .40

Contact Mass Entry Form (APACMAS) . . . . . . . . . . . . . . . . . . . . . . .40

Prospect Status Validation Form (ATVPRST). . . . . . . . . . . . . . . . . . . .41

Section 3 Enhanced Processing of Third-Party Gifts - Functional

Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Step 1 Define third-party processor . . . . . . . . . . . . . . . . . . . . . . . . .43Step 2 Define data load file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Step 3 Review fields available for data load . . . . . . . . . . . . . . . . . . . .45Step 4 Map incoming code values to Banner values . . . . . . . . . . . . . . . .45Step 5 Review Banner data fields that can be loaded . . . . . . . . . . . . . . .45Step 6 Define format of data load file . . . . . . . . . . . . . . . . . . . . . . . .45

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Load gift records to temporary table . . . . . . . . . . . . . . . . . . . . . . . .50

Review gift records and load to baseline tables . . . . . . . . . . . . . . . . . .50

Changed forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Gift Form (AGAGIFT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Review External Gifts Form (AGAWGIF) . . . . . . . . . . . . . . . . . . . . . .51

New process - External Gift Load Process (AGPEXGF) . . . . . . . . . . . .52

4 Banner Advancement 8.1 December 2008Release GuideContents

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Output report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Processing tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57File load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Header record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Date format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Seed data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Section 4 Miscellaneous Enhancements - Functional

Changed form - Review External Gifts Form (AGAWGIF) . . . . . . . . . . . .59

Section 5 Gift Mass Entry - Technical

New table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Changed table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Changed package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

New API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Section 6 Enhanced Proposal Processing - Technical

New tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

AMBPRPH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

AMRPRPH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

AMRPRRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Changed tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

AMBPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

AMRCONT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

AMRPROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

ATVPRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Changed packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

New APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

December 2008 Banner Advancement 8.1 5Release Guide

Contents

Project History (ab_project_history). . . . . . . . . . . . . . . . . . . . . . . . .65

Project Results (ab_project_results) . . . . . . . . . . . . . . . . . . . . . . . .65

Proposal History (ab_proposal_history). . . . . . . . . . . . . . . . . . . . . . .66

Changed libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Section 7 Enhanced Processing of Third-Party Gifts - Technical

New tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

AGTGHDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

AGTGHLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Changed tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

AGBGHLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

AGBGIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Changed package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Section 8 Problem Resolutions

Summary of problem resolutions . . . . . . . . . . . . . . . . . . . . . . . .69

6 Banner Advancement 8.1 December 2008Release GuideContents

Decemb

Introduction

This release guide describes the enhancements and problem resolutions in the Banner Advancement 8.1 release. This document provides detailed information about the following enhancements:

• Mass entry of similar, one-time gifts from various donors

• Enhanced proposal processing

• Enhanced processing of gift details provided by third-party processors

Problem resolutions are summarized at the end of this release guide.The detailed description, impact, and resolution information for each problem resolution are delivered in a separate file named advanc80100resolutions.txt.

er 2008 Banner Advancement 8.1 7Release Guide

8
Banner Advancement 8.1 December 2008Release Guide

Decemb

1 Gift Mass Entry - Functional

This enhancement includes a new form that allows you to quickly enter a group of similar, one-time gifts received from various donors. The Gift Mass Entry Form (AGAGMAS) supports the entry of high volume gifts associated with fund raising events such as reunions, annual appeals, and radio and television funding drives. The enhancement streamlines the user experience by tracking recognition items that might affect the tax deductible amount of gifts.

Process flow

A group of gifts is processed as follows:

1. Default information is entered for the group of gifts.

2. Individual gifts are entered. If necessary, the default information can be changed for individual gifts.

3. Gift details and giving history are updated.

Default gift information

To minimize repetitive data entry, the Gift Defaults window of AGAGMAS is used to enter gift details, recognition items, solicitation information, and campaign/designation combinations that apply to a group of gifts. As a minimum, the following gift defaults are required:

• Gift date

• Gift type

• At least one campaign/designation combination

You can choose to populate fields on this window with gift defaults defined for your ID on the Pledge/Gift Default Form (AGAPDEF).


Gift Mass Entry - Functional

10

Individual gift information

Information for individual gifts is entered on the IDs window of AGAGMAS. Once a donor ID and gift amount are entered, a gift is created and a gift number is automatically assigned. Default information for each gift is identified on the Gift Defaults window, but you can use the tabs at the bottom of the IDs window to change this information for individual gifts.

Gift details and giving history details

Once all gifts are entered in a session, gift details are loaded to Banner tables and giving history details are updated by selecting Exit (load gifts and return to main menu) or Rollback (load gifts and return to Gift Defaults window). The following processing occurs:

• Gift credit for an ID is split on detail records and history records if the ID has cross reference codes (for example, parent or child relationship) and split gift rules apply to the ID.

• Gift acknowledgement rules defined on the Pledge/Gift Acknowledgement Rules Form (AGAACKR) are enforced. Rules for duplicate processing on the Letter Code Validation Form (GTVLETR) are followed.

• Matching gifts are generated for gifts with matching employers. Matching gifts are split appropriately.

• Gifts are sent to cashiering for finance processing.

Gift details are displayed on the following forms:

Giving history details are displayed on the following forms:

Tasks

Gift mass processing includes the following tasks.

AGCGIFT Gift List FormAGCGMLT Gift Hard Credit ID List FormAGCGMMO Gift Soft Credit ID List Form

APACHIS Giving History by Campaign FormAPACOMB Combined Giving History FormAPADHIS Giving History by Designation FormAPAGHIS Giving History Summary Form

Banner Advancement 8.1 December 2008Release GuideGift Mass Entry - Functional

Decemb

Enter mass gifts

Use the following steps to enter a group of gifts.

1. Access the Gift Mass Entry Form (AGAGMAS).

2. (optional) If you want to copy gift defaults from the Pledge/Gift Default Form (AGAPDEF), click Copy Gift Defaults .

NoteYou can select Gift Defaults from the Options menu to see the defaults defined on AGAPDEF for the current user.

3. Enter information that applies to all gifts in the group. The following fields are required:

Gift DateGift TypeCampaign (at least one)Designation (at least one)

NoteYou can select Campaign Detail from the Options menu to see campaign details on the Campaign Detail Form (AFACAMP).

Once the required data is entered, the IDs tab is enabled.

4. Select the IDs tab.

5. Enter the ID and gift amount.

6. Select Next Item or tab to the Gift Number field. A gift number is automatically assigned.

7. (optional) If you need to add or change gift details, campaign/designation combinations, solicitation information, or benefits information, see “Add or change information for individual gifts” on page 12.

8. Once the gift is entered, select Next Record or click the next row.

9. Repeat steps 5 through 8 to enter each gift.

10. When all gifts are entered, select Exit or Rollback to finalize gift entry for this group and update giving history.



12

Add or change information for individual gifts

Information that applies to all gifts in the group comes from the Gift Defaults window. You can overwrite these defaults or add information for individual gifts. Use the following steps to add or change information for an individual gift.

1. Enter the ID and gift amount on the IDs window of AGAGMAS.

NoteOnce you enter an ID, gift transaction information is created. If you need to exit the form or start over, you must remove the record.

2. Select Next Item or tab to the Gift Number field.

A gift number is automatically assigned. The tabs at the bottom of the window are enabled.

3. To add or change gift details:

3.1. Select the Gift Detail tab.

3.2. Add or change gift details.

3.3. Select Save to save the changes.

4. To add or change campaign/designation combinations:

4.1. Select the Campaigns/Designations tab.

4.2. Add or change campaign/designation combinations.

4.3. Save.

If the sum of the detail amounts in this block does not equal the total gift amount entered in the IDs block, an error message is displayed. Change the detail amounts, or select Auto Balance to automatically update the total gift amount in the IDs block so it equals the sum of the detail amounts.

5. To add or change solicitation information:

5.1. Select the Solicitation tab.

5.2. Add or change solicitation information.

5.3. Save.


Decemb

6. To add or change benefits information:

6.1. Select the Benefits tab.

6.2. Add or change benefits information.

6.3. Save.

7. When all changes are entered, select Exit or Rollback to update giving history.

Balance gift amount

Before a gift can be saved, the total gift amount must equal the sum of the detail amounts distributed to campaigns and designations. A message is displayed if the amounts are out of balance. You can select Auto Balance or Manual Balance to balance the gift amount:

Save pending gift transactions

If your Banner session aborts before giving history details are updated, the IDs window is displayed with a message the next time you access AGAGMAS. You must complete the pending transactions on the IDs window before you can enter new gifts. Use the following steps to complete the pending transactions.

1. Review the pending transactions on the IDs window of AGAGMAS.

2. If you need to change gift details, campaign/designation combinations, solicitation information, or benefits information for the displayed gifts, see “Add or change information for individual gifts” on page 12.

3. If you need to delete a pending transaction:

3.1. Select the record.

3.2. Select Remove Record.

4. After all changes are made, select Exit or Rollback to update giving history.

Auto Balance The total gift amount in the IDs block is automatically updated to equal the total of the detail amounts.

Manual Balance You must manually update the detail amounts in the Campaigns/Designations block so their sum equals the total gift amount in the IDs block.



14

New form - Gift Mass Entry Form (AGAGMAS)

AGAGMAS is used to quickly enter a group of similar, one-time gifts received from various donors. The form supports the entry of high volume gifts associated with fund raising events such as reunions, annual appeals, and radio and television funding drives. The form streamlines the user experience by tracking recognition items that might affect the tax deductible amount of gifts.

Gift Defaults window

This window is used to enter default information that applies to a group of gifts. Entering defaults for a group of gifts minimizes repetitive entries for individual gifts in the group. You can enter gift details, recognition items, solicitation information, and campaign/designation combinations that apply to the group of gifts. As a minimum, the following gift defaults are required:

• Gift date

• Gift type


Although the information entered in this window applies to all gifts in the group, you can change information for individual gifts, if necessary, on the IDs window.

To help you enter defaults in the Gift Defaults window, you can use the Options menu as follows:

Gift Defaults block

This block is used to enter defaults that apply to all gifts in the group.

Option

Campaign Detail (AFACAMP) Displays campaign details

Gift Defaults (AGAPDEF) Displays gift defaults defined for the current user

Institution Rules (AGASPRL) Displays institution rules for splitting gifts for IDs that have cross reference codes (relationships such as parent or child)


Decemb

Field Description

Copy Gift Defaults Button used to populate the default field values with the current user’s defaults from the Pledge/Gift Default Form (AGAPDEF).

Note: You can select Gift Defaults (AGAPDEF) from the Options menu to review the gift defaults defined for the current user.

Gift Date Date associated with gifts in the group. The default is the current date, but it can be changed. Required.

Fiscal Year Fiscal year associated with gifts in the group. The default is based on the gift date. Fiscal year is automatically updated if a change to the gift date changes the fiscal year. Display only.

Gift Type Gift type and description for gifts in the group. Required.

The Advancement to Finance Feed Process (ADPFEED) uses the gift type to relate gift transactions.

The description default comes from the Gift/Payment Type Validation Form (ATVGIFT). You can change the description on AGAGMAS to record more specific information about the type of gifts being received.

The gift type or description can be adjusted on the Pledge/Gift Adjustment Form (AGAADJS) after individual gifts are entered and saved. An audit trail is maintained and displayed on the Gift Adjustment List Form (AGCGADJ).

List - Gift/Payment Type Validation Codes (ATVGIFT)

Match Form Received Check box that indicates whether matching gift forms were received for gifts in the group. Optional.

This field is informational only and is not used by the Expected MG Allocations Report (AXPMATG) and the Matching Gift Allocations Report (AGPMATG).

selected Form received

cleared Form not received



16

Benefits Information block

This block is used to identify a benefit or premium associated with all gifts in the group. A benefit might affect the tax deductible amount of the gifts. This information is used to reconcile revenue for quid pro quo gifts.

Solicitation Information block

This block is used to identify solicitation information for all gifts in the group.

Gift Class 1Gift Class 2Gift Class 3

Gift classifications for gifts in the group. This is an optional means of relating gift transactions. Up to three gift classes can be assigned to the group of gifts. Optional.

List - Gift Classification Code Validation (ATVGCLS)

Vehicle Gift vehicle code for gifts in the group. Optional.

List - Pledge/Gift Vehicle Code Validation (ATVPGVE)

Field Description

Benefit Code Benefit or premium that donors received for gifts in the group. Optional.

List - Benefits/Premiums Validation Codes (ATVDCPR/ATVAUXL)

Auxiliary Code Auxiliary code associated with the benefit code. The default comes from the Auxiliary Code Validation Form (ATVAUXL). Display only.

This code determines which records are included on the VSE Report (ADPVSER).

Field Description


Decemb

Campaigns and Designations block

This block is used to apply all gifts in the group to one or more campaign/designation combinations. At least one campaign/designation combination must be entered for the group. An unlimited number of campaign/designation combinations can be entered. You can credit a single campaign/designation, a single campaign with multiple designations, or multiple campaigns and multiple designations.

NoteEach campaign/designation combination must be previously defined on the Campaign Header Form (AFACAMP). You can select Campaign Header (AFACAMP) from the Options menu to display valid combinations.

Field Description

Solicitation Method of solicitation for gifts in the group. Optional.

List - Solicitation Type Code Validation (ATVSOLC)

Organization Solicitation organization credited with gifts in the group. Optional.

List - Solicitor Organizations

ID ID of the solicitor credited with gifts in the group. Optional.

List - Solicitors for Organization

Duplicate Record - Solicitation Selections for Organization

Field Description

Campaign Campaign to which gifts in the group are applied. Required.

Count Hits - Campaign List Form (AFCCAMP)

Designation Designation to which gifts in the group are applied. Required.

Note: A warning message is displayed if the designation is inactive for the campaign.

List - Campaign Detail Form (AFACAMP)

Count Hits - Default designation



18

IDs window

This window is used to enter individual gifts. Once you enter the donor ID and gift amount, you must tab to the Gift Number field to automatically assign a gift number. Default values from the Gift Defaults window are then displayed for the gift. You can use the tabs at the bottom of the IDs window to change information for an individual gift.

Once all gifts in the group are entered, you must select Exit (update giving history and return to main menu) or Rollback (update giving history and return to Gift Defaults window).

IDs block

This block is used to enter each gift in the group.

NoteOnce you enter an ID, partial transaction information is created. If you need to exit the form or start over, you must remove the record.

Amount Amount applied to the campaign/designation combination for gifts in the group. Optional.

Note: A balancing error will occur on the IDs window if an individual gift is entered with an amount that does not equal the total of all campaign/designation amounts entered in this block. If a balancing error occurs, the gift details or total gift amount must be adjusted on the IDs window.

Field Description

ID ID associated with the gift. Required.

List - Advancement Individual Search Form (AOAIDEN)

Count Hits - Advancement Organization Search Form (AOACOMP)

Field Description


Decemb

Gift Detail block

This block is used to add or change details for the gift selected in the IDs block. Default gift details come from the Gift Defaults window but can be changed.

Gift Amount Total amount of the donor’s gift. Required.

Once you enter an amount, the amount in this field cannot be manually adjusted. If the amount needs to be adjusted, you must adjust the gift amount on the Campaigns/Designations tab and save the change.

Before a gift can be saved, this gift amount must equal the sum of the detail amounts distributed to campaigns and designations. A message is displayed if the amounts are out of balance. You can select Auto Balance or Manual Balance to balance the gift amount:

• Auto Balance - The total gift amount is automatically updated to equal the sum of the detail amounts.

• Manual Balance - You must manually update the detail amounts so their sum equals the total gift amount.

Benefit Radio group that indicates the status of the benefit or premium associated with this group. Display only.

Accept The donor accepted the benefit. This value is initially selected if benefit information is entered on the Gift Defaults window.

Reject The donor did not accept the benefit.

Not Applicable The gift does not have a benefit. This value is initially selected if benefit information is not entered on the Gift Defaults window.

Multiple The gift has multiple benefits.

The benefit status of a gift can be changed on the Benefits tab.

Gift Number Gift number automatically assigned to the gift. Display only.

Total Total amount of the gifts entered in this group. Display only.

Field Description



20

Field Description

Gift Type Gift type and description for the gift. The defaults come from the Gift Defaults window, but they can be changed. Required.

The Advancement to Finance Feed Process (ADPFEED) uses the gift type to relate gift transactions.

The default description comes from the Gift/Payment Type Validation Form (ATVGIFT). You can change the description on AGAGMAS to record more specific information about the type of gift being received.

The gift type or description can be adjusted on the Pledge/Gift Adjustment Form (AGAADJS) after the gift is entered and saved. An audit trail is maintained and displayed on the Gift Adjustment List Form (AGCGADJ).

List - Gift/Payment Type Validation Codes (ATVGIFT)

Gift Date Date associated with the gift. The default comes from the Gift Defaults window, but it can be changed. Required.

Fiscal Year Fiscal year associated with the gift. The default is based on gift date. It is automatically updated if a change to the gift date changes the fiscal year. Display only.

Match Form Received Check box that indicates whether a matching gift form was received for the gift. The default comes from the Gift Defaults window, but it can be changed. Optional.

This field is informational only and is not used by the Expected MG Allocations Report (AXPMATG) and the Matching Gift Allocations Report (AGPMATG).

selected Form received

cleared Form not received

Gift Class 1Gift Class 2Gift Class 3

Gift classifications for the gift. This is an optional means of relating gift transactions. Up to three gift classes can be assigned to the gift. The default comes from the Gift Defaults window, but it can be changed.Optional.

List - Gift Classification Code Validation (ATVGCLS)


Decemb

Campaigns/Designations block

This block is used to apply one or more campaign/designation combinations to the gift selected in the IDs block. Default campaign/designation combinations come from the Gift Defaults window, but they can be changed.

At least one campaign/designation combination must be entered for a gift. An unlimited number of campaign/designation combinations can be entered. You can credit a single campaign/designation, a single campaign with multiple designations, or multiple campaigns and multiple designations.

Before you can continue to another gift, the sum of the detail amounts distributed to campaigns and designations in this block must equal the gift amount entered in the IDs block.

.

Vehicle Gift vehicle code for the gift. The default comes from the Gift Defaults window, but it can be changed. Optional.

List - Pledge/Gift Vehicle Code Validation (ATVPGVE)

Comment Free-form comment. Select Edit to view the entire comment (300 characters). Optional.

Field Description

Detail Amount Amount of the gift applied to the campaign/designation combination. The default comes from the Gift Defaults window, but it can be changed. Required.

Campaign Campaign to which all or part of the gift is applied. The default comes from the Gift Defaults window, but it can be changed. Required.

Count Hits - Campaign List Form (AFCCAMP)

Field Description



22

Solicitation block

This block is used to maintain solicitation information for the gift selected in the IDs block. Default information comes from the Gift Defaults window, but it can be changed.

Designation Designation to which all or part of the gift is applied. The default comes from the Gift Defaults window, but it can be changed. Required.

Note: A warning message is displayed if the designation is inactive for the campaign.

Count Hits - Campaign Detail Form (AFACAMP)

List - Designation List Form (ADCDESG)

Total Total amount distributed to all campaigns and designations for this gift. Display only.

This total must equal the total gift amount in the IDs block. A message is displayed if the amounts are out of balance. You can select Auto Balance or Manual Balance to balance the gift amount:

• Auto Balance - The total gift amount in the IDs block is automatically updated to equal the total of the detail amounts.

• Manual Balance - You must manually update the detail amounts so their sum equals the total gift amount in the IDs block.

Field Description

Solicitation Method of solicitation for the gift. The default comes from the Gift Defaults window, but it can be changed.Optional.

Duplicate Record - Campaign Solicitation Details Form (AGCCORG)

Count Hits - Solicitation Type Code Validation (ATVSOLC)

Insert Record - Solicitors for Contact

List - Solicitation Type Code Validation (ATVSOLC)

Field Description


Decemb

Benefits block

This block is used to maintain information about benefits or premiums that were provided for the gift selected in the IDs block.

NoteMultiple benefits or premiums can be entered by selecting Next Record. If a gift has more than one benefit or premium, the Multiple radio button in the IDs block is selected automatically.

Organization Solicitation organization credited with the gift. The default comes from the Gift Defaults window, but it can be changed.Optional.

List - Solicitors for Contact

Count Hits - Solicitor Organization List Form (ASCSORG)

ID ID of the solicitor credited with the gift. The default comes from the Gift Defaults window, but it can be changed.Optional.


Count Hits - Solicitors for Organization

Duplicate Record - Solicitation Selections for Organization

Duplicate Item - Solicitation Selections for Campaign

Field Description

Benefit Code Benefit or premium that the donor received for the gift. The default comes from the Gift Defaults window, but it can be changed. Optional.

List - Benefits/Premiums Validation Codes (ATVDCPR)

Description Description of the benefit or premium. Optional.

Field Description



24

Auxiliary Code Auxiliary code associated with the benefit code. The default comes from the Auxiliary Code Validation Form (ATVAUXL). Display only.

This code determines which records are included on the VSE Report (ADPVSER).

Actual Value Face value of the gift. Default is determined as follows:

• If the auxiliary code is associated with a benefit/premium code on ATVAUXL and the benefit/premium code has a cost defined on ATVDCPR, then the default actual value is the cost defined on ATVDCPR.

• If the auxiliary code is associated with a benefit/premium code on ATVAUXL but the benefit/premium code does not have a cost defined on ATVDCPR, then the actual value is left blank.

• If the auxiliary code is not associated with a benefit/premium code on ATVAUXL, then the default actual value is the gift amount entered on AGAGMAS.

The default can be changed.

Auxiliary Value Present value of the gift, if different from the face value. The default is determined as follows:

• If the auxiliary code is associated with a benefit/premium code on ATVAUXL and the benefit/premium code has a value defined on ATVDCPR, then the default auxiliary value is the value defined on ATVDCPR.

• If the auxiliary code is associated with a benefit/premium code on ATVAUXL but the benefit/premium code does not have a value defined on ATVDCPR, then the auxiliary value is left blank.

• If the auxiliary code is not associated with a benefit/premium code on ATVAUXL, then the auxiliary value is left blank.

The default can be changed.

Field Description


Decemb

Changed menu

The *ALUGENTRY Gift and Pledge Payment Entry Menu now includes the Gift Mass Entry Form (AGAGMAS).

Accept/Reject/Not Applicable

Radio group that indicates the status of the benefit or premium:

Accept The donor accepted the benefit. This is the default value if the gift has a benefit code.

Reject The donor did not accept the benefit.

Not Applicable The gift does not have a benefit. This is the default value if the gift does not have a benefit code.

The default can be changed

Deduct for Taxes Check box that determines how the value is derived for tax reporting:

selected Subtract auxiliary value from actual value. This is the default if an auxiliary code is entered, but it can be changed.

cleared Use full actual value.

User User who entered the benefit or premium information for the gift. Display only.

Activity Date Date when the benefit or premium information was last entered. Display only.

Date Date when values were associated with the gift. The default is the current date, but it can be changed. Optional.

Issue Date Date when the benefit or premium was sent to the donor ID. The default is the date when a benefit code is entered, but it can be changed. Optional.

Accept or Reject Date Date when the gift was accepted or rejected. The default is the date when a value is selected in the Accept, Reject, Not Applicable radio group, but it can be changed. Optional.

Comment Free-form comment. Select Edit to view the entire comment. Optional.

Field Description



26

Decemb

2 Enhanced Proposal Processing - Functional

Banner Advancement uses proposals to track the solicitation of funds from individuals, foundations, and businesses. Banner Advancement 8.1 improves the tracking of solicitations by integrating proposal processing and gift processing. The following enhancements provide the ability to track progress toward funding goals and measure the results of solicitation initiatives:

• A proposal can reference specific gifts or pledges that are received as a result of the proposal.

• A prospect can have multiple proposals of the same type.

• The history of proposal changes and project changes can be tracked.

Definitions

Banner Advancement uses the following terms in proposal processing:

Prospect A prospect is anyone who has the potential or willingness to contribute gifts or leadership support to an institution. Within Banner, an assigned prospect is an individual or organization that is identified for personal contact regarding a gift or leadership support at a level greater than annual donations or committees. Assigned prospects are managed through Prospect Management. Additional research, formal proposals, and plans for engagement can be associated with assigned prospects.

Project A project is an institutional initiative that relies on funding or leadership support. Within Banner Advancement, a project can be generic (Scholarship Support), specific (Smith Family Memorial Scholarship), or somewhere between (Endowed Scholarship Support).

Proposal A proposal is a formal presentation to an assigned prospect regarding specific institutional initiatives in which the institution hopes to engage the assigned prospect. Within Banner, a proposal comprises one or more projects, each with a targeted funding amount. A proposal is commonly used for capital campaigns and comprehensive campaigns to ask a prospect to support several initiatives at the same time, rather than asking the prospect to support each initiative separately.


Enhanced Proposal Processing - Functional

28

Tasks

Proposal processing includes the following tasks.

Create a new proposal

Use the following steps to create a new proposal.

1. Access the Proposal Prospect Form (AMAPROP).

2. In the key block, enter the ID of the prospect associated with the proposal.

3. Go to the Proposals window.

4. Enter proposal information in a blank record. The Proposal Code field is required.

NoteSelect Insert Record if you need to create a blank record.

5. (optional) Go to the Proposal Comments window and enter comments.

6. Save.

7. Enter information for each project that is part of the proposal:

7.1. Go to the Projects/Summary window and enter summary information for each project. The Project field is required for each project.

7.2. (optional) Select a project in the Projects/Summary window and go to the Projects/Details window to enter additional details for the selected project.

7.3. Save.

Strategy A strategy is a set of planned moves (actions) established to cultivate an assigned prospect’s gift or leadership support. The actions occur over time with a pre-defined number of wait days between each action. The objective is to progress the prospect to the overall goal established for the prospect, maximizing the prospect’s involvement with the institution.

Banner Advancement 8.1 December 2008Release GuideEnhanced Proposal Processing - Functional

Decemb

Enter project results

Use the following steps to enter information about the pledges or gifts that result from a project.

1. Access the Proposal Prospect Form (AMAPROP).

2. In the key block, enter the ID of the prospect associated with the proposal.

3. Go to the Proposals window.

4. Enter the proposal code.

5. Go to the Projects/Summary window.

6. Select the project for which results are being recorded.

7. Go to the Projects/Results window.

8. Enter information about the gifts or pledges that resulted from the project.

9. Save.

Changed forms

The following form changes support enhanced proposal processing.

Prospect Contacts Form (AMACONT)

The Proposal field has a list of values that shows proposals set up for the prospect. The proposal status code in this list of values was expanded to six characters.

The Proposal Sequence Number field was added to this form to link the contact to a specific proposal record. This sequence number allows a prospect to have multiple proposals with the same proposal code.

Advancement Prospect Information Form (AMAINFO)

The size of the Status fields on the General Information window and on the Project Interest Areas window was increased to six characters.

On the General Information window, the list of values on the Status field is limited to status codes for prospects. Similarly, the list of values on the Status field on the Project and Interest Areas window is limited to status codes for projects. This behavior is based on



30

new check boxes on the Prospect Status Validation Form (ATVPRST) used to assign a status code to prospects, proposals, and/or projects.

Prospect Proposal Form (AMAPROP)

This form is used to manage and track proposals associated with a prospect. A proposal is a formal presentation regarding specific institutional initiatives in which the institution hopes to engage the assigned prospect.

A proposal comprises one or more projects, each with a targeted funding amount. A proposal can have an unlimited number of projects, but only four projects can be active at the same time.

The following changes to AMAPROP enhance the ability to manage and track proposals:

• A new sequence number is used to differentiate proposals that have the same proposal code. Previously, a prospect could have only one proposal for a proposal code. A prospect can now have multiple proposals with the same proposal code.

• A new field tracks the date when a proposal was created. This date can be used to query proposals.

• The size of the proposal and project status codes was increased to six characters throughout the form.

• The proposal status code list of values is limited to status codes for proposals. Similarly, the project status code list of values is limited to status codes for projects. This behavior is the result of new check boxes on the Prospect Status Validation Form (ATVPRST) used to assign a status code to prospects, proposals, and/or projects.

• A new window is available to record the gifts or pledges that are received as a result of a project.

• New windows are available to track proposal changes and project changes.

• A new tabbed interface improves the organization of proposal and project information.

Due to the significant additions and redesign of the form, the entire form is described in the following text.

Key block

This block is used to identify the prospect associated with the proposals.


Decemb

Proposals window

This window is used to create and maintain proposals for a prospect. A prospect can have an unlimited number of proposals. A proposal includes the following information:

• Proposal code

• Status of the proposal

• Total ask amount for the proposal

• Staff assigned to the proposal

• Projects (funding initiatives) and ask amounts associated with the proposal

• Gifts and pledges that result from the proposal

• Comments regarding the proposal

The following fields provide basic information about the proposal.

Field Description

ID Identification number and name given to an advancement individual or advancement organization on the Advancement Identification Form (APAIDEN).

List - Advancement Individual Search Form (AOAIDEN)

Duplicate Record - Advancement Individual Summary Form (APASBIO)

Count Hits - Advancement Organization Search Form (AOACOMP)

Duplicate Item - Advancement Organization Header Form (AOAORGN)

Spouse Identification number and name of the spouse entered on the Advancement Individual Information Form (APACONS).

List - Advancement Individual Summary Form (APASBIO)

Category Primary donor category for the key ID and spouse.

Class Preferred class year for the key ID and spouse entered on the Advancement Individual Information Form (APACONS).



32

Field Description

Proposal Code Code that identifies the proposal. Required.

Note: A prospect can have multiple proposals with the same proposal code.

List - Proposal Codes Validation (ATVPROP)

Sequence Sequence number that uniquely identifies a proposal. This number permits a prospect to have multiple proposals with the same proposal code. This sequence number is assigned automatically when a record is saved. Display only.

Create Date Date when the proposal was created. The default is the current date when a proposal is created, but the date can be changed.

Status Status of the proposal.

List - Prospect/Project Status Code Validation (ATVPRST). The list shows only those status codes that are associated with proposals on ATVPRST.

Active Check box that indicates whether the proposal is active. This setting is based on the Active check box defined for the status code on ATVPRST. Display only.

Status Date Date when the proposal status was entered or last updated. The default is the current date when a proposal is created or updated, but the date can be changed.

Amount Total ask amount for the proposal.

Due Date Date when the prospect manager expects the prospect to act on the proposal.

Note: The staff member assigned to the proposal is identified by either a staff code or an ID. You can enter one or the other, but not both.

Staff Code that identifies the staff member assigned to the proposal.

List - Staff Assigned to Prospect. The list is based on the staff members assigned to the prospect on the Advancement Prospect Information Form (AMAINFO).

Count Hits - User Identification Control Form (GUAIDEN)


Decemb

Projects block

This block is used to enter information about each project that is assigned to the proposal. A project is an institutional initiative that relies on funding or leadership support. A proposal can have an unlimited number of projects, but only four projects can be active at the same time.

Summary tab

This tab is used to enter or update summary information about each project assigned to the proposal.

ID Banner ID that identifies the staff member assigned to the proposal.

List - Staff Assigned to Prospect. The list is based on the staff members assigned to the prospect on the Advancement Prospect Information Form (AMAINFO).

Count Hits - Person Search Form (SOAIDEN)

Duplicate Item - Advancement Individual Search Form (AOAIDEN)

Field Description

Project Project code and description associated with the proposal. A project is an institutional initiative that relies on funding or leadership support.

List - Project/Interest Code Validation (ATVPROJ)

Count Hits - Prospect’s Projects. The list is based on the projects defined for the prospect on the Advancement Prospect Information Form (AMAINFO).

Giving Vehicle Vehicle code associated with the project.

List - Giving Vehicle Code Validation (ATVGIVH)

Field Description



34

Details tab

This tab is used to enter or update details about the project selected on the Summary tab.

Status Status of the project within the proposal. The default is based on the project status defined for the prospect on AMAINFO, but it can be changed. Only four projects can be active for a proposal at the same time. A blank status is assumed to be an active status.

List - Prospect/Project Status Code Validation (ATVPRST). The list shows only those status codes that are associated with projects on ATVPRST.

Target Ask Amount Desired asking amount for the project within the proposal.

Field Description

Project Code Project code and description associated with the proposal. Display only.

Status Code Status of the project within the proposal. Display only.

Status Date Date when the project status was assigned or last updated. The date can be changed.

Target Ask Date Date by which the target ask amount will be solicited.

Target Ask Amount Desired asking amount for the project within the proposal. The default comes from the Summary tab, but it can be changed.

Project Effective From Date

Starting date when the project is effective. The default comes from AMAINFO, but it can be changed.

Project Effective To Date

Ending date when the project is effective. The default comes from AMAINFO, but it can be changed.

Project Text Free-form comments about the project. Maximum number of characters is 2,000.

Field Description


Decemb

Results tab

This tab is used to record specific gifts or pledges that are received as a result of the project selected on the Summary tab.

NoteIf a gift or pledge is adjusted at a later time, information on the Results tab must be manually updated. Results can be changed or removed, if necessary.

Field Description

Project Project code and description associated with the proposal. Display only.

Date Date when the pledge or gift was recorded. Required.

Gift Number Gift number of the gift that was received for the project.

List - All Gift Credit. This list shows all gifts made by the prospect and spouse in the key block.

Pledge Number Pledge number of the pledge that was received for the project. If entered, the pledge number must be valid for the gift number.

List - All Pledges. This list shows all pledges made by the prospect and spouse in the key block.

Campaign Campaign for the associated gift or pledge.

If you selected a gift or pledge number from a list of values, the default is the campaign associated with the selected gift or pledge. If you entered a gift or pledge number manually, you must enter a campaign that is valid for the gift or pledge number.

List - Campaigns. This list shows all campaigns defined on the Campaign Detail Form (AFACAMP).

Count Hits - All Gift Credit. This list shows all gifts made by the prospect and spouse in the key block.

Duplicate Record - All Pledges. This list shows all pledges made by the prospect and spouse in the key block.



36

Proposal Comments block

This block is used to record optional comments for a proposal:

Proposal Change History window

This window displays changes made to all proposals for a prospect. Changed fields are identified by an asterisk (*). Fields show original values, before the changes. All fields are display only.

History records are sorted in the following order:

1. Date when the proposal record was created

2. Date when the proposal record was changed

Designation Designation for the associated gift or pledge.

If you selected a gift or pledge number from a list of values, the default is the designation associated with the selected gift or pledge. If you entered a gift or pledge number manually, you must enter a designation that is valid for the gift or pledge number.

List - Designations. This list shows all designations defined on the Designation Form (ADADESG).

Value Amount of the gift or pledge that was credited to the campaign/designation combination.

If you selected a gift or pledge number from a list of values, the default is the amount of the gift or pledge associated with the campaign/designation combination, but it can be changed.

Comment Free-form comment about the gift or pledge. Maximum number of characters is 2,000.

Total Total amount of the gifts and pledges received as a result of the project within the proposal. This value is automatically updated each time a result record is saved. Display only.

Field Description

Comment Free-form comment about the proposal. Maximum number of characters is 10,000.

Field Description


Decemb

3. Proposal code

4. Proposal sequence number (highest number to lowest number)

The following fields identify the history record.

Status tab

This tab displays original values when the following fields are changed.

User tab


Field Description

Change Date Date when the proposal information was changed.

Proposal Code Code that identifies the proposal.

List - Proposal Codes Validation (ATVPROP) in query mode

Proposal Sequence Sequence number that uniquely identifies the proposal.

Amount Total ask amount for the proposal.

Field Description

Status Status of the proposal. Status codes are defined on the Prospect/Status Validation Form (ATVPRST).

List - Prospect/Project Status Code Validation (ATVPRST) in query mode

Status Date Date when the proposal status was entered or last updated.

Due Date Date when the prospect manager expects the prospect to act on the proposal.

Create Date Date when the proposal was created.



38

Comments tab

This tab displays the original value when the following field is changed.

Project Change History window

This window displays changes made for all projects associated with all proposals for a prospect. Changed fields are identified by an asterisk (*). Fields show original values, before the changes. All fields are display only.

History records are sorted in the following order:

1. Date when the project record was changed

2. Proposal code and proposal sequence number (highest number to lowest number)

3. Project code

The following fields identify the history record.

Field Description

Note: The staff member assigned to the proposal is identified by either a staff code or an ID, not both.

Staff Code that identifies the staff member assigned to the proposal. Staff codes are defined on the User Identification Control Form (GUAIDEN).

ID Banner ID that identifies the staff member assigned to the proposal.

User User ID who changed the proposal information.

Field Description

Comment Free-form comment about the proposal.

Field Description

Change Date Date when the project information was changed.

Proposal Code Code that identifies the proposal.


Decemb

Target Ask Amount tab


Effective Dates and User tab


Proposal Sequence Sequence number that uniquely identifies the proposal.

Project Code Code that identifies the project.

List - Project/Interest Code Validation (ATVPROJ) in query mode

Field Description

Project Code Description

Project description.

Giving Vehicle Vehicle code associated with the project. Vehicle codes are defined on the Giving Vehicle Code Validation Form (ATVGIVH).

List - Giving Vehicle Code Validation (ATVGIVH) in query mode

Target Ask Amount Desired asking amount for the project within the proposal.

Target Ask Date Date by which the target ask amount will be solicited.

Field Description

Status Code Status of the project within the proposal.

List - Proposal Codes Validation (ATVPROP) in query mode

Status Date Date when the project status was assigned or last updated.

Effective From Date Starting date when the project is effective.

Effective To Date Ending date when the project is effective.

User User ID who changed the project information.

Field Description



40

Project Text tab

This tab displays the original value when the following field is changed.

Moves by Prospect Form (AMAPROS)

Mouse-over bubble help was added to the Prospect Status field to display the complete status description if it is longer than the display area.

A sequence number field was added to two windows: Most Recent Contact window and Contacts window. The sequence number links a contact to a specific proposal record. This sequence number allows a prospect to have multiple proposals with the same proposal code.

Contact Mass Entry Form (APACMAS)

APACMAS is used to enter contact details for a group of IDs. For prospect contacts, a proposal code (optional) and a project code are entered on the Prospect Details and Action window. These codes apply to all IDs in the group. If both codes are entered, new logic in the form is used to create prospect contact records. For each ID, the proposal/project combination is compared with existing proposal records for the ID. Based on this comparison, a prospect contact record is created as follows:

• If the ID has a single proposal record with the proposal/project combination, the prospect contact record is created for that proposal record.

• If the ID has multiple proposal records with the proposal/project combination and only one of those records is active, the prospect contact record is created for the active proposal record.

• If the ID has multiple proposal records with the proposal/project combination and more than one of those records is active, the prospect contact record is created for the active proposal record with the highest sequence number.

• If the ID has no proposal records with the proposal/project combination, no prospect contact record is created and a warning message is displayed. All warnings must be corrected before contacts can be created for the group of IDs on APACMAS. A warning is corrected by adding the ID to the Prospect Proposal Form (AMAPROP) or removing the ID from the batch list of IDs on APACMAS.

Field Description

Project Text Free-form comments about the project.


Decemb

Prospect Status Validation Form (ATVPRST)

The size of the Status field was expanded to six characters. The form also has three new check boxes: Prospect, Proposal, and Project. These check boxes indicate which categories are associated with a status code. For example, if the Proposal check box is selected for a status code, then proposals can have that status code.



42

Decemb

3 Enhanced Processing of Third-Party Gifts - Functional

This release enhances the processing of gift details provided by third-party processors, ensuring the safe handling of credit card and ACH transactions from PCI-compliant credit card processing services.

The new External Gift Load Process (AGPEXGF) loads gift details from third-party processors to Banner. An external gift must have the following data:

• Banner ID

• External gift ID

• External record number

• External gift type

• Total gift amount


• Gift amount for each campaign/designation combination

This process accommodates character delimited and fixed length data load files. You must define the format of the data file that AGPEXGF expects to receive. See “Define format of data load file” on page 45 for details.

Setup

The following setups are required before you can use AGPEXGF to load gift details from third-party processors.

Step 1 Define third-party processor

Define the third-party processor on the Data Source Identifier Validation Form (ATVDSRC).


Enhanced Processing of Third-Party Gifts - Functional

44

Fields on ATVDSRC are defined as follows:

Step 2 Define data load file

Define the data load file on the Data File Validation Form (ATVTAPE). The file can be character delimited or fixed length.

The following figure shows a sample definition for a character delimited file:

The following figure shows a sample definition for a fixed length file:

Fields on ATVTAPE are defined as follows:

Code Code that identifies the third-party processor.

Description Name of the third-party processor.

File Code Code that identifies the data load file definition.

Description Description of the data load file.

Process Banner process (AGPEXGF) associated with the file definition.

Delimiter Character delimited file - Character that separates each field in the record (for example, a comma).

Fixed length file - blank.

Marker Marker value that delimits data included in the field. Determines the detail included for each defined field. Used to accommodate files where the selected delimiter value is also used in the data.

Banner Advancement 8.1 December 2008Release GuideEnhanced Processing of Third-Party Gifts - Functional

Decemb

Step 3 Review fields available for data load

Use the Data Field Names Validation Form (ATVTPFD) to review the fields that can be included in the data load.

NoteThe displayed values are delivered by SunGard Higher Education and cannot be changed. Not all values listed are available for AGPEXGF.

Step 4 Map incoming code values to Banner values

Review code values on the data load file. If any of the processor’s code values differ from those in your Banner tables, use the Data Translation Field Value Rules Form (APATRAN) to map incoming values to the Banner values. Incoming values that match existing Banner values do not need to be mapped.

Fields on APATRAN are defined as follows:

Step 5 Review Banner data fields that can be loaded

Use the Data Field Process Rules Form (APATPFD) to review the data fields that are available for AGPEXGF to load into Banner.

Step 6 Define format of data load file

The data load file must contain two types of records for each gift. The format of each record type is defined on the Data Field Position Rules Form (AGATPFD):

Data Source Code that identifies the third-party processor. This code is defined on ATVDSRC.

Field Name Name that identifies the data field in Banner. These names are defined on ATVTPFD.

Incoming Data Value

Value from the third-party processor that needs to be translated to a corresponding Banner value.

Banner Value Banner value that corresponds to the value from the third-party processor.



46

NoteThe gift date (EXT_GIFT_GIFT_DATE) and gift entry date (EXT_GIFT_ENTRY_DATE) are not required. If these dates are not defined, AGPEXGF uses the current system date.

NoteThe cashier (EXT_GIFT_CASHIER) is not required. If this field is not provided, AGPEXGF uses the ID of the person who runs the report.

NoteAny blank lines in the data load file must be removed before running AGPEXGF.

The format definition depends on whether the data load file is character delimited or fixed length, as defined on the Data File Validation Form (ATVTAPE).

Character delimited data load file

A character delimited file uses a special character (for example, a comma) to separate each field in a record. The following illustration shows a sample character delimited data load file. Each gift record must have a header (01) and details (02) as shown here:

The following figure shows a sample definition for Record Number 1 (gift header) for a character delimited data load file:

Record Number Description Required Fields

1 Gift header BAN_IDEXT_GIFT_EXT_GIFT_IDEXT_GIFT_REC_NUMEXT_GIFT_AMT_TOTEXT_GIFT_GIFT_CODE

2 Gift details BAN_IDEXT_GIFT_EXT_GIFT_IDEXT_GIFT_REC_NUMEXT_GIFT_CAMPAIGNEXT_GIFT_DESGEXT_GIFT_DESG_AMT


Decemb

The following figure shows a sample definition for Record Number 2 (gift details) for a character delimited data load file.

The following fields are entered on AGATPFD for a character delimited data load file:

File Code Code that identifies the data load file definition. This code is defined on ATVTAPE.

Record Number Record that is being defined:

1 Gift header

2 Gift details

File Process Banner process (AGPEXGF) associated with the data load file. The process for the file code is defined on ATVTAPE. Display only.



48

Fixed length data load file

A fixed length file uses a predetermined, constant size for each field in a record. The following illustration shows a sample fixed length data load file. Each gift record must have a header (01) and details (02) as shown here:

The following figure shows a sample definition for Record Number 1 (gift header) for a fixed length data load file.

The following figure shows a sample definition for Record Number 2 (gift details) for a fixed length data load file.

File Delimiter Character that separates each field in the record. This character is defined on ATVTAPE. Display only.

Field Name Name that identifies the data field in Banner.

Field Number Position on the file where the field is located.

Occurrence Blank. AGPEXGF does not support repeating data fields.


Decemb

The following fields are entered on AGATPFD for a fixed length data load file:

Tasks

Gift records from third-party processors are loaded into a temporary table, manually reviewed, and then loaded to baseline Banner tables.

File Code Code that identifies the data load file definition. This code is defined on ATVTAPE.

Record Number Record that is being defined:

1 Gift header

2 Gift details

File Process Banner process (AGPEXGF) associated with the data load file. The process for the file code is defined on ATVTAPE. Display only.

File Delimiter Blank for a fixed length data load file.

Field Name Name that identifies the data field in Banner.

Start Starting position of the data field in a file (provided by the third-party processor).

End Ending position of the data field in a file (provided by the third-party processor).

Occurrence Blank. AGPEXGF does not support repeating data fields.



50

Load gift records to temporary table

Use the following steps to load gifts from a third-party processor into a temporary Banner table.

1. Run the External Gift Load Process (AGPEXGF) in report mode. This allows you to test the data load without changing any data in Banner.

2. Review the report and make any changes in the data load file, if necessary.

NoteAny blank lines in the data load file must be removed before running AGPEXGF in update mode.

3. Run AGPEXGF in update mode. This loads the gift data into a temporary table.

Review gift records and load to baseline tables

After gifts are loaded into the temporary table, use the following steps to review the gifts and load them into baseline Banner tables.

1. Access the Review External Gifts Form (AGAWGIF) to display records loaded into the temporary table.

2. Review records on AGAWGIF and make any changes, if necessary.

3. Select the OK to Load check box for each record as you approve it.

4. Select Save.

5. When all records are reviewed and saved, select Create Gift from the Options menu to load the verified records into the Banner baseline tables.

Changed forms

The following form changes support the enhanced processing of gift details provided by third-party processors.

Gift Form (AGAGIFT)

The Gift or Pledge Payment window displays the following new fields.


Decemb

In addition, the Credit Card and Expiration Date fields are no longer required for credit card gifts.

The Additional Gift Information window displays the following new fields.

Review External Gifts Form (AGAWGIF)

AGAWGIF displays the following new fields.

Field Description

Reference Code provided by the third-party processor to uniquely identify the credit card transaction. Can be used by the donor to track a transaction.

Authorization Code provided by the third-party processor to verify that the credit card transaction was authorized. Can be used by the institution, in conjunction with the reference code, to track a transaction.

Field Description

External Gift ID Gift ID supplied by the third-party processor. Display only.

Origin Source of the third-party transaction. Display only.

Field Description

Authorization Code provided by the third-party processor to verify that the credit card transaction was authorized. Can be used by the institution, in conjunction with the reference code, to track a transaction. Display only.

Reference Code provided by the third-party processor to uniquely identify the credit card transaction. Can be used by the donor to track a transaction. Display only.

Origin Source of the third-party transaction. For gifts from third-party processors, this code identifies the third-party processor that sent the gift record. Display only.

External Gift ID Gift ID supplied by the third-party processor. Display only.



52

New process - External Gift Load Process (AGPEXGF)

AGPEXGF is a new process that loads external gift data from a third-party processor into the Banner database.

AGPEXGF is available in report or update mode. When executed in report mode, the process generates a report that can be reviewed before updating the database. Any errors can be corrected or noted for future review.

Parameters

The following table describes the parameters used to run AGPEXGF.

Parameter Name Required? Description Values

File Code Yes Code that defines the data load file.

Data File Validation Form (ATVTAPE)

Data Source Identifier Yes Code that identifies the third-party processor.

Data Source Identifier Validation Form (ATVDSRC)

Data File Name Yes Name of the data load file.

Path of Data File - Part 1 Yes Directory where the data load file is located (up to 30 characters). If the data file path is longer than 30 characters, two additional parameters are available to provide additional data file path details.


Decemb

Path of Data File - Part 2 No Additional details (up to 30 characters) for the directory where the data load file is located. Used with the Path of Data File - Part 1 parameter when the data file path is longer than 30 characters. This entry is concatenated to the end of the details entered in part 1.

Path of Data File - Part 3 No Additional details (up to 30 characters) for the directory where the data file is located. Used with the Path of Data File - Part 1 and Part 2 parameters when the data file path is longer than 60 characters but less than 91 characters. This entry is concatenated to the end of the details entered in part 2.

Report/Update Mode Yes Code that determines whether the database is updated when the process is run.

R Print report; do not update database (default).

U Print report; update database.




54

Output report

The report heading includes the description of the third-party processor and the sort order.

The report body includes two sections for each gift:

• The gift header includes information such as the donor’s Banner ID, Banner gift ID, external gift ID, gift type, giving vehicle, gift date, and total gift amount.

• The detail section includes each campaign/designation combination in the gift and the associated amount.

An error message is displayed below the record where the error occurred. The following conditions result in an error message:

• Missing or invalid information

• Total gift amount does not equal the sum of detail gift amounts

Records with errors are not loaded to Banner. These records must be corrected in the data load file or manually loaded to Banner.

Date Format No Date format that overrides the system-defined date format for this execution of AGPEXGF. Must be a valid Oracle date format. Used solely to evaluate incoming dates and load details to Banner.

Header Record Exists No Code that indicates whether the data load file includes a header record.

Y Header exists (default).

N Header does not exist.

Sort Order No Report sort order. 1 ID (default)

2 Name (last, first, middle)

3 External gift ID



Decem

ber 2008B

anner Advancem

ent 8.155

Release G

uideE

nhanced Processing of Third-P

arty Gifts - Functional

13-O PAGE 1Rele AGPEXGF

Bann

9997

THREE WWW - Web Credit Card ABUS - Area Business Appeal AFS - Annual Fund Solicitors 999743383

Detail Amount Scholarships with a $200.00 lly long Research Center $150.00 estoration Fund $100.00

9997

TWO WWW - Web Credit Card HONR - In Honor of MEMY - Memorial ANON - Anonymous ABUS - Area Business Appeal AFS - Annual Fund Solicitors 999743333 - Geiser, S Craig

Detail Amount estoration Fund $150.00 Scholarships with a $250.00 lly long

CT-2008 SUNGARDHE University ase 8.1 External Gift Load Process Gifts from All, Inc Report Only - Banner ID Order

er ID Name

44444 Geiser, Donald

Banner Gift Number: REPORT External Gift ID: Gift Type: CC - Credit Card Giving Vehicle: Gift Date: 02-OCT-2008 Gift Classes: Total Gift Amount: $450.00 Gift Entry Date: 01-OCT-2008 Authorization Code: ABC123 Reference Number: REF1234567890 Solicitation: Match Form Received: N Solicitor Organization: Cashier: GSMITH Solicitor: Comment: Errors: Solicitor ID does not exist in Banner.

Pledge Number Campaign Designation 0000000 NOR - Norton Building Campaign ATHLS - Athletic really, really, rea 0000000 NOR - Norton Building Campaign BIMED - Biomedical 0000000 NOR - Norton Building Campaign BLCHR - Bleachers R

45555 Geiser, George

Banner Gift Number: REPORT External Gift ID: Gift Type: CC - Credit Card Giving Vehicle: Gift Date: 24-SEP-2008 Gift Classes: Total Gift Amount: $300.00 Gift Entry Date: 36-SEP-2008 Authorization Code: ABC123 Reference Number: REF1234567890 Solicitation: Match Form Received: N Solicitor Organization: Cashier: GSMITH Solicitor: Comment: In Memory of Mary Errors: Invalid Gift Entry Date.

Pledge Number Campaign Designation 0000000 EXCEL - Campaign for Excellence & A BLCHR - Bleachers R Errors: Invalid Campaign and Designation Combination. 0000000 NOR - Norton Building Campaign ATHLS - Athletic really, really, rea Errors: Detail amounts do not equal the Total Gift Amount.

56B

anner Advancement 8.1

Decem

ber 2008R

elease Guide

Enhanced P

rocessing of Third-Party G

ifts - Functional

13-O PAGE 3Rele AGPEXGF

Bann

USER

Para____ _________________________

FileDataDataPathPathPath[R]eDateHeadSortLine

CT-2008 SUNGARDHE University ase 8.1 External Gift Load Process Gifts from All, Inc Report Only - Banner ID Order

er ID Name

* * * REPORT CONTROL INFORMATION * * * parameter Message

:........................ SGEISER

meter Name Value Message_________________________ _____________________________ _______________________________

203421 Code EXT_GIFTS Source Identifier GIFTCO File Name external_gifts.csv of Data File - Part 1 /export/home/sgeiser/ of Data File - Part 2 rel81/xsd/ of Data File - Part 3port/(U)pdate Mode R Format DD-MON-YYYYer Record Exists N Order 1 Count 55

Decemb

Processing tips

The following processing tips apply to AGPEXGF.

File load

You must do the following when you load a file that contains third-party gifts:

• Verify that the input file is in ASCII format.

• Use the File Transfer Process (FTP) to transfer the file in ASCII mode via a Secure File Transfer to a directory that Banner can read from and write to. This directory depends on your operating system. This location is entered as one or more AGPEXGF parameters (depending on the length of the data file path).

• Enter the file name as an AGPEXGF parameter.

Header record

If the file begins with a header record that contains information provided by the third-party processor, set the Header Record Exists parameter to Y. With this setting, AGPEXGF ignores the first record.

Date format

AGPEXGF recognizes all potential Oracle date formats for dates on the data load file. If the Date Format parameter is defined, this format is used for dates. If the parameter is not defined, the format of the current system date is used for dates.

Seed data

The following rows were added to the Data Field Names Validation Form (ATVTPFD) to identify the fields that can be included when gift data is loaded from third-party processors.

Field Name DescriptionValidation Table Column

BAN_ID Banner IDEXT_GIFT_AMT_TOT External Gift AmountEXT_GIFT_CAMPAIGN External Gift CampaignEXT_GIFT_CARD_AUTH_CODE External Gift Credit Card Transaction

Authorization Code



58

EXT_GIFT_CARD_REFR_NUMBER External Gift Credit Card Transaction Reference Number

EXT_GIFT_CASHIER External Gift CashierEXT_GIFT_COMMENT External Gift CommentEXT_GIFT_DESG External Gift DesignationEXT_GIFT_DESG_AMT External Gift Designation AmountEXT_GIFT_ENTRY_DATE External Gift Entry DateEXT_GIFT_EXT_GIFT_ID External Gift IdentifierEXT_GIFT_GCLS_CODE_1 External Gift Class 1 ATVGCLS_CODE

EXT_GIFT_GCLS_CODE_2 External Gift Class 2 ATVGCLS_CODE

EXT_GIFT_GCLS_CODE_3 External Gift Class 3 ATVGCLS_CODE

EXT_GIFT_GIFT_CODE External Gift Type ATVGIFT_CODE

EXT_GIFT_GIFT_DATE External Gift DateEXT_GIFT_GIFT_DESC External Gift DescriptionEXT_GIFT_MATCH_RECEIVED External Gift Match Form ReceivedEXT_GIFT_PGVE_CODE External Gift Giving Vehicle Code ATVPGVE_CODE

EXT_GIFT_PLEDGE_NO External Gift Pledge NumberEXT_GIFT_REC_NUM External Gift Record NumberEXT_GIFT_SOLC_CODE External Gift Solicitation CodeEXT_GIFT_SOL_ID External Gift Solicitor Banner IDEXT_GIFT_SOL_ORG External Gift Solicitor Organization

Field Name DescriptionValidation Table Column


Decemb

4 Miscellaneous Enhancements - Functional

This chapter describes miscellaneous functional enhancements delivered in Banner Advancement 8.1.

Changed form - Review External Gifts Form (AGAWGIF)

AGAWGIF is used to review and accept external gifts. These can be gifts entered via the Web by donors using a new user ID and PIN, or these can be gifts received from a third-party processor. Banner Advancement 8.1 includes the following new features for AGAWGIF:

• A solicitation method, solicitation organization, and solicitor can be assigned to a gift during the review process.

• Additional fields are available to store multiple campaign/designation combinations for a gift. For gifts entered via Banner Advancement Self-Service, only one campaign/designation combination is stored and available for review. If gifts are loaded from other external processes, however, multiple combinations can be stored and reviewed on AGAWGIF and then loaded to baseline Banner tables.

• Gift credit is automatically split on detail records and history records if the donor has a Banner ID and splitting rules indicate that the gift should be split among the ID’s cross references (relationships such as parent or child). Previously, any gift credit had to be split manually if the donor had a Banner ID and splitting rules were defined for the ID.

AGAWGIF has the following new fields.


Miscellaneous Enhancements - Functional

60

Field Description

Solicitation Solicitation type associated with the gift. Optional.


Count Hits - Solicitation Type Code Validation (ATVSOLC)

Duplicate Record - Campaign Solicitation Details Form (AGCCORG)

Organization Solicitation organization associated with the gift. Optional.


Count Hits - Solicitor Organization List Form (ASCSORG)

ID Solicitor ID associated with the gift. Optional.


Banner Advancement 8.1 December 2008Release GuideMiscellaneous Enhancements - Functional

Decemb

5 Gift Mass Entry - Technical

This chapter describes the Banner Advancement 8.1 technical changes that support the gift mass entry enhancement.

New table

The new Gift Auxiliary Hold Table (AGRAUXH) temporarily holds information about auxiliary values and benefit or premium codes associated with gifts entered in a gift mass entry session. When the user exits the gift mass entry session, records are deleted from AGRAUXH and saved on baseline tables.

Changed table

The temporary AGBGHLD table has four new columns:

The value AGAGMAS is stored in AGBGHLD_DATA_ORIGIN each time a gift is entered in a gift mass entry session. When the user exits the gift mass entry session, the data origin and user ID are used to determine which gift records are deleted from AGBGHLD and saved on baseline gift tables.

Changed package

The AGKGIFT package was updated to handle gifts entered on the Gift Mass Entry Form (AGAGMAS). To further enhance gift processing, ACKGIFT was also updated to process the following gift information:

• Solicitation information (solicitation method, solicitation organization, and solicitor)

• Multiple campaign/designation combinations

AGBGHLD_SOLC_CODEAGBGHLD_SOL_ORGAGBGHLD_SOL_PIDMAGBGHLD_DATA_ORIGIN


Gift Mass Entry - Technical

62

New API

The Gift Auxiliary Hold API (ab_gift_auxl_hold) provides the Common Business interface for the Gift Auxiliary Hold Table (AGRAUXH). Each pending gift in a gift mass entry session can have one or more auxiliary values and benefit or premium codes associated with it. When a pending gift is moved to the baseline tables, this auxiliary information is loaded to AGRGAUX.

This API includes the following packages:

Table API Object Name API Entity Name Task Performed

AGRAUXH ab_gift_auxl_hold GIFT_AUXILIARY_HOLD Stores information about the auxiliary values and benefits or premiums associated with gifts.

ab_gift_auxl_hold aokb_gift_auxl_hold0.sqlaokb_gift_auxl_hold1.sql

ab_gift_auxl_hold_rules aokb_gift_auxl_holdr0.sql aokb_gift_auxl_holdr1.sql

ab_gift_auxl_hold_strings aokb_gift_auxl_holds0.sqlaokb_gift_auxl_holds1.sql

Banner Advancement 8.1 December 2008Release GuideGift Mass Entry - Technical

Decemb

6 Enhanced Proposal Processing - Technical

This chapter describes the Banner Advancement 8.1 technical changes that support enhanced proposal processing.

New tables

The following new tables support enhanced proposal processing.

AMBPRPH

The Prospects Proposals History Base Table (AMBPRPH) stores proposal history information. When records in the Prospects Proposals Base Table (AMBPROP) are changed, original data values (before the changes) from AMBPROP are stored in AMBPRPH. Each field in AMBPRPH has a change indicator that contains Y if the value was changed on the current record or N if the field was not changed.

AMRPRPH

The Prospects Proposals Projects History Repeating Table (AMRPRPH) stores project history information. When records in the Prospects Proposals Projects Repeating Table (AMRPROP) are changed, original data values (before the changes) from AMRPROP are stored in AMRPRPH. Each field in AMRPRPH has a change indicator that contains Y if the value was changed on the current record or N if the field was not changed.

AMRPRRS

The Prospects Proposals Projects Results Repeating Table (AMRPRRS) stores information about gifts or pledges that are received as a result of a proposal’s project.

Changed tables

The following table changes support enhanced proposal processing.


Enhanced Proposal Processing - Technical

64

AMBPROP

The table has two new columns:

AMRCONT

A new column (AMRCONT_PROP_SEQ_NO) allows a prospect to have multiple proposals with the same proposal code.

AMRPROP

A new column (AMRPROP_PROP_SEQ_NO) allows a prospect to have multiple proposals with the same proposal code.

ATVPRST

The size of the status code (ATVPRST_CODE) was expanded to six characters. The table also has three new columns used to indicate which categories are associated with a status code:

Changed packages

The following packages were modified to accommodate the new proposal sequence number (AMBPROP_SEQ_NO). This sequence number permits a prospect to have multiple proposals with the same proposal code.

New Column Description

AMBPROP_SEQ_NO Sequence number that allows a prospect to have multiple proposals with the same proposal code.

AMBPROP_CREATE_DATE Date when a proposal was created.

ATVPRST_PROS_IND Indicates whether a status code is associated with prospects.ATVPRST_PROP_IND Indicates whether a status code is associated with proposals.ATVPRST_PROJ_IND Indicates whether a status code is associated with projects.

BWDKPCNTBWDKPPRF

Banner Advancement 8.1 December 2008Release GuideEnhanced Proposal Processing - Technical

Decemb

New APIs

The following new APIs support enhanced proposal processing.

Project History (ab_project_history)

This API stores project history information. When records in the Prospects Proposals Projects Repeating Table (AMRPROP) are changed, original data values (before the changes) are stored in the Prospects Proposals Projects History Repeating Table (AMRPRPH).


Project Results (ab_project_results)

This API creates and maintains information about the gifts or pledges that are received as a result of a proposal’s projects.



AMRPRPH ab_project_history PROJECT_HISTORY Stores history information about changes made to AMRPROP.

ab_project_history aokb_proj_hist0.sqlaokb_proj_hist1.sql

ab_project_history_rules aokb_proj_histr0.sql aokb_proj_histr1.sql

ab_project_history_strings aokb_proj_hists0.sqlaokb_proj_hists1.sql


AMRPRRS ab_project_results PROJECT_RESULTS Creates and maintains information about the gifts or pledges that are received as a result of a proposal’s projects.


Enhanced Proposal Processing - Technical

66

Proposal History (ab_proposal_history)

This API stores proposal history information. When records in the Prospects Proposals Base Table (AMBPROP) are changed, original data values (before the changes) are stored in the Prospects Proposals History Base Table (AMBPRPH).


Changed libraries

The following libraries were updated to support the new proposal sequence number (AMBPROP_SEQ_NO). This sequence number allows a prospect to have multiple proposals with the same proposal code.

ab_project_results aokb_proj_rslt0.sqlaokb_proj_rslt1.sql

ab_project_results_rules aokb_proj_rsltr0.sql aokb_proj_rsltr1.sql

ab_project_results_strings aokb_proj_rslts0.sqlaokb_proj_rslts1.sql


AMBPRPH ab_proposal_history PROPOSAL_HISTORY Stores history information about changes made to AMBPROP.

ab_project_history aokb_prop_hist0.sqlaokb_prop_hist1.sql

ab_project_history_rules aokb_prop_histr0.sql aokb_prop_histr1.sql

ab_project_history_strings aokb_prop_hists0.sqlaokb_prop_hists1.sql

AOQMENU A new global variable (proposal_seq_no) was added.

AOQOLIB The AMBPROP_LOV was updated.

Banner Advancement 8.1 December 2008Release GuideEnhanced Proposal Processing - Technical

Decemb

7 Enhanced Processing of Third-Party Gifts - Technical

This chapter describes the Banner Advancement 8.1 technical changes that support the enhanced processing of third-party gifts.

New tables

The following new tables support enhanced processing of third-party gifts.

AGTGHDE

The External Gift Campaign Designation Detail Temporary Table (AGTGHDE) temporarily stores campaign/designation information that is loaded by the External Gift Load Process (AGPEXGF). Information in this temporary table is reviewed and approved on the Review External Gifts Form (AGAWGIF). Once approved, information is moved from AGTGHDE to baseline Banner tables.

AGTGHLD

The External Gift Detail Temporary Table (AGTGHLD) temporarily stores gift header information that is loaded by the External Gift Load Process (AGPEXGF). Information in this temporary table is reviewed and approved on the Review External Gifts Form (AGAWGIF). Once approved, information is moved from AGTGHLD to baseline Banner tables.

Changed tables

The following table changes support enhanced processing of third-party gifts.

AGBGHLD

The following columns were added to AGBGHLD:


Enhanced Processing of Third-Party Gifts - Technical

68

AGBGIFT

The following columns were added to AGBGIFT:

Changed package

AGKGIFT was updated to process the following third-party gift information:

• External gift ID

• Credit card authorization code

• Credit card reference number

AGBGHLD_DATA_ORIGIN Origin of the third-party data

AGBGHLD_CARD_AUTH_CODE Authorization code received from the third-party processor

AGBGHLD_CARD_REFR_NUMBER Reference number received from the third-party processor

AGBGIFT_DATA_ORIGIN Origin of the third-party data

AGBGIFT_EXT_GIFT_ID Gift ID supplied by the third-party processor

AGBGIFT_CARD_AUTH_CODE Authorization code received from the third-party processor

AGBGIFT_CARD_REFR_NUMBER Reference number received from the third-party processor

Banner Advancement 8.1 December 2008Release GuideEnhanced Processing of Third-Party Gifts - Technical

Decemb

8 Problem Resolutions

This section summarizes the problem resolutions delivered in Banner Advancement 8.1. The detailed description, impact, and resolution information for each problem resolution are delivered in a separate file named advanc80100resolutions.txt.

Summary of problem resolutions

.Object Name Defect # Summary

adpfeed.pc 1-13CGDK ADPFEED did not feed all records to Banner Finance.

adpfeed.pc 1-13CG5D ADPFEED fed records to Banner Finance only if the FOAPAL or account details were present.

adpfeed.pc 1-43PLM1 The GURFEED_TRANS_AMT on the GURFEED header record was incorrectly calculated when debit (negative) transaction amounts were included in the feed. Instead of calculating an absolute total (control total that does not consider + or -), it considered negative figures which caused an incorrect calculation.

adpvser.pc 1-3RQ8BL The report did not round correctly.

adpvser.pc 1-3XURPB Large data fields did not print correctly.

agagsol.fmb CMS-DFCT106023 Rollback returned to the Gift field rather than to the ID field.

agamatg.fmb 1-2WL2QZ The Extended Search feature did not work properly.

agapldg.fmb 1-1Q12GS The Comment field did not wrap.

agapldg.fmb 1-43K49I The default pledge type code did not always default into a new pledge record.

agapldg.fmb 1-PJKM5 Double clicking to return a campaign code did not work properly.


Problem Resolutions

70

agcgift.fmb 1-41PSUS Some amount fields did not include commas.

aoacomp.fmb 1-OPBE0 Performing a query followed by a Rollback resulted in an Oracle error.

aoacomp.fmb 1-PX0U3 The Options menu did not include AOAORGN.

aoacomp.fmb CMS-DFCT85175 The Case Sensitive Query radio button did not always work properly.

aoqrpls.pll 1-3W52QN The name and spouse name fields were too short.

apaacty.fmb LN70-0031-424 On the Years of Participation and Leadership window, double clicking the Years field displayed the calculator.

apacomb.fmb 1-955XU The Extended Search feature did not work properly.

apacomt.fmb CMS-DFCT104167 When you accessed APAIDEN for an ID that had a spouse and then exited to APACOMT, the cursor was in the Subject field rather than in the ID field.

apacomt.fmb CMS-DFCT104808 Subject indexes were not displayed properly.

apacomt.fmb CMS-DFCT85655 Depending on the navigation used, a non-comment supervisor could receive error messages and display confidential comments.

apacomt.fmb CMS-DFCT93301 Selecting text in the Comment field did not work properly.

apacons.fmb 1-3WI19Q A combined mailing name larger than 50 characters caused an error.

apagsum.fmb 1-49V3B Block navigation was not in the correct order.

apaiden.fmb 1-3YZHFH Navigation to the Household Members tab did not always work properly.

apaname.fmb 1-3WI19Q A combined mailing name larger than 50 characters caused an error.

apaxref.fmb 1-9L9V1 The activity date was not changed when the form was updated.

Object Name Defect # Summary

Banner Advancement 8.1 December 2008Release GuideProblem Resolutions

Decemb

apibrws.fmb 1-2KNAJW If the confidential indicator for a spouse was originally set to Y on APAIDEN and then changed to N, the confidential indicator on APIBRWS remained set to Y.

appdcar.pc 1-3QFO4J Installments due in the society year were not always counted.

appdcar.pc 1-3R28UT Totals for complex gifts were not calculated correctly.

appdcar.pc 1-3RFZY2 Default premiums were not created when lifetime gift societies were assigned.

appstdi.pc 1-3JWQT7 When data already existed in APBCONS with zeros, APPSTDI did not update the class and college codes.

axamgrn.fmb CMS-DFCT105937 There were navigation issues, and the activity date had to be manually entered.

Object Name Defect # Summary


Problem Resolutions

72
Banner Advancement 8.1 December 2008Release GuideProblem Resolutions

banner advancement release guide · enter gift details, recognition items, solicitation...

Documents