SCT Banner Advancement / Release Guide / 7.1

SCT Banner 

Advancement 

Release Guide 

May 2005 

Release 7.1

Confidential Business Information 

This documentation is proprietary information of SunGard SCT and is not to be copied, reproduced, lent or disposed of, nor used for any 

purpose other than that for which it is specifically provided without the written permission of SunGard SCT. 

Prepared By: 

SunGard SCT 

4 Country View Road 

Malvern, Pennsylvania 19355 

United States of America 

© SunGard 2005. All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or 

the information contained herein is prohibited. 

In preparing and providing this publication, SunGard SCT is not rendering legal, accounting, or other similar professional services. SunGard 

SCT 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. 

SunGard, the SunGard logo, SCT, the SCT logo, and Banner, Campus Pipeline, Luminis, PowerCAMPUS, SCT Matrix, SCT Plus, SCT OnSite 

and SCT PocketRecruiter are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other 

countries. All other trade names are trademarks or registered trademarks of their respective holders.

Release Guide 

Advancement System 

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 

Section 1 Householding Enhancement - Functional. . . . . . . . . . . . 7 

Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 

Setting Up Householding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 

Maintaining Household Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 

Making Household Addresses Inactive . . . . . . . . . . . . . . . . . . . . . . . . . . 9 

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 

Advancement Individual Information Form (APACONS) . . . . . . . . . . . . . . . . . 9 

Advancement Control Form (AGACTRL) . . . . . . . . . . . . . . . . . . . . . . . . . 10 

Advancement Identification Form (APAIDEN) . . . . . . . . . . . . . . . . . . . . . . 11 

Cross Reference Form (APAXREF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 

Cross Reference Code Validation Form (ATVXREF) . . . . . . . . . . . . . . . . . . . . 16 

Children Information Form (APACHLD) . . . . . . . . . . . . . . . . . . . . . . . . . 17 

System Identification Form (GUASYST). . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Section 2 Household Enhancement - Technical. . . . . . . . . . . . . . . 19 

New Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

aofhhld1.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

household_child.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

household_general.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

household_spouse.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Changed Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

aludbpr.sql . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

3

Table of Contents 

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Cross-Reference Repeating View Table (APRXREF) . . . . . . . . . . . . . . . . . . . . 20 

Cross-Reference Validation Table (ATVXREF). . . . . . . . . . . . . . . . . . . . . . . 20 

Advancement Installation Control Table (AUBINST) . . . . . . . . . . . . . . . . . . . 20 

New Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

f_session_id_active_ind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

Section 3 Problem Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

External Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

Advancement Release 7.1 May 2005 

4 Release Guide Confidential

Overview 

Overview 

This guide describes Release 7.1 of the SCT Banner Advancement System. It 

describes a new enhancement, Householding, and problem resolutions. 

Prerequisites 

Before you install this release, you must have already installed the following: 

• General Release 7.0 

• Advancement Release 7.0 

May 2005 Advancement Release 7.1 

Confidential Release Guide 5

Overview 

This page intentionally left blank 



Section 1 Householding Enhancement - Functional 

Tasks 

Section 1 

Householding Enhancement - Functional 

This enhancement allows you to organize people into households so you can 

maintain address and telephone information about them more easily. 

For example, if a student lives with his parents and the family moves, your users 

would: 

1. Change the student’s address and telephone information as usual. 

2. Access the new Household Members tab on the Advancement Identification 

Form (APAIDEN). 

3. Review the information displayed there about all the members of the 

household. 

4. Update the rest of the family members to have the same address and telephone 

information as the student with one mouse click (if you set Update as the default 

in your rules). 

Note: You can also make an address type inactive for all members of the 

household using this new tab. 

In addition, you can now access the System Identification Form (GUASYST) from 

APAIDEN so you can see which Banner modules are associated with the person or 

household members. 

Tasks 

Setting Up Householding 

1. Access the Cross Reference Code Validation Form (ATVXREF). 

2. Look at each of the codes defined on the form, and determine if the 

relationship they define should be considered part of the same household. 

Select the Household check box for each one that is. 

Note: To make sure your forms and processes behave consistently, Banner will 

select the Household check box for the reverse value, too. For example, 

if you select Household for Husband, the form will automatically select it 

for Wife. 

3. Save your changes. 




Tasks 

If you want the Update check box on the Advancement Identification Form 

(APAIDEN) to be selected by default, perform the next steps as well. 

4. Go to the Advancement Control Form (AGACTRL), and navigate to the 

Institution window. 

5. Select the Yes radio button for Household Member Address Automatically- 

Flag-for-Update. 


Maintaining Household Information 

When an address or telephone number has changed for one member of a 

household and you want to make the corresponding changes to the other members’ 

records: 

1. Access the Advancement Identification Form (APAIDEN). 

2. Enter the ID of the person whose information has changed. 

3. Perform a Next Block to access the Current Identification tab. 

4. Select the Address tab and scroll through the records to find the address and 

phone number you want. 

This will make the Household Members tab active, and the number of 

additional members (besides the current person) will appear in parenthesis on 

the tab. 

5. Select the Household Members tab. The information about the current person 

and each household member will be displayed. The household members are 

populated from the Cross Reference Form (APAXREF). If there are any 

discrepancies between the current person’s address and phone records and the 

highlighted household member’s information, a pound sign (#) will appear 

before the appropriate rows. 

Note: If the Yes radio button was selected for Household Member Address 

Automatically-Flag-for-Update Default on the Institution Window of the 

Advancement Control Form (AGACTRL), the Update check box will 

automatically be selected for records with discrepancies. 

6. Review the records for the household members. If you want to change the 

household member’s information to match the current person’s, make sure 

the Update check box is selected. 

7. Select Save. Banner will change all the records where the Update check box 

was selected to have the same address and telephone information as the 

current person, and it will save them. 




Changed Forms 

Making Household Addresses Inactive 

If an address type becomes inactive for a person, you can easily make it inactive for 

all the other members of the household. 

1. Access the Advancement Identification Form (APAIDEN). 

2. Enter the ID of the person whose information has changed. 

3. Perform a Next Block to access the Current Identification tab. 

4. Select the Address tab and scroll through the records to find the address and 

phone number you want to make inactive. 

The Household Members tab will now be active, and the number of additional 

members (besides the current person) will appear in parenthesis on the tab. 

5. Select the Household Members tab. 

The information about the current person and each household member will 

be displayed. 

6. Select the Update check box for each person. 

7. Select the Inactivate Selected Household Addresses button. 


You cannot go back and perform household maintenance for an address type after 

the address of that type has been made inactive. 

Changed Forms 

Advancement Individual Information Form (APACONS) 

A new check box has been added to the Spouse Information window to indicate if 

the person is a member of a household. You can select or clear it to change the 

household status for anyone set up with a cross reference code on the Cross 

Reference Form (APAXREF), where the Spouse indicator is selected on the Cross 

Reference Code Validation Form (ATVXREF). 

When users create new spouse records, the household indicator (if selected) will 

cause the appropriate fields on APACONS to be automatically populated with the 

default values specified on ATVXREF. 




Changed Forms 

Fields 

. . . . . . . . . . . . . . 

Household 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Indicates if the person is a member of the household. Valid values 

are: 

selected - the person is a member of the household 

cleared - the person is not a member of the household 

This check box will be selected by default if the Household check 

box on the Cross Reference Code Validation Form (ATVXREF) 

is selected for the code. 

Advancement Control Form (AGACTRL) 

Two new items have been added on the Institution window in the Miscellaneous 

Defaults block. 




Changed Forms 

Fields 

. . . . . . . . . . . . . . 

Address Source 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Specifies the default address source to be used when 

automatically updating address details for the household 

members. Leave the field blank to use the address source details 

from the source address record. 

(lookup) List Address Source Code 

Validation (STVASRC) 

Household 

Member 

Address 

Automatically- 

Flag-for-Update 

Default 

Indicates if addresses in a household that are different should be 

flagged automatically on the Household Members tab of the 

Advancement Identification Form (APAIDEN). This will be the 

system-wide default. Valid values are: 

Yes - the Update check box will be selected automatically when 

there are discrepancies between the address or telephone 

number of the current person and one or more members of the 

household 

No - the Update check box will be cleared by default. When users 

want to update the address or telephone information of a 

household member to match that of the current person, they will 

have to select the Update check box manually for each one 

Advancement Identification Form (APAIDEN) 

A new tab, Household Members, has been added to this form. You can only access 

it from the Address tab and when there are additional members in the household. 




Changed Forms 

The tab displays in parenthesis how many members exist (as defined on APAXREF), 

not including the current person. 

The type of address and phone information displayed depends on which address 

and telephone type you selected on the Address tab. 

Programming logic checks to see if the addresses and telephone numbers match the 

one for the current person. If they don’t, a pound sign (#) appears before the 

appropriate fields. 

You can update the addresses and telephone numbers to match the current person’s 

by selecting the Update check box and saving. 

Note: The Update check box is selected automatically if you set the Household 

Member Address Automatically-Flag-for-Update Default indicator to Yes 

on AGACTRL. 

The tab is locked for that address type for all members of the household while it is 

open so one user cannot overwrite another user’s changes. If someone tries to access 

it, they will receive an error message that identifies the member of the household 

and the Oracle username of the person who is updating the record. 

Current Person Block 

All the information here is populated from other parts of APAIDEN, and are displayonly. 

Fields 

. . . . . . . . . . . . . . 

Name 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

The current person’s name. 

ID 

The current person’s Banner ID. 

Address Type 

The type of the address that is displayed. If this is not the address 

type you want to update for household members, go to the 

Address tab to find the correct one. 

Sequence 

The sequence number of the address for that type. 

Address 

The street address of the current person. 

City (untitled) 

The city of the current person. 




Changed Forms 

Fields 

. . . . . . . . . . . . . . 

State or 

Province 

(untitled) 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

The state or province for the current person. 

ZIP or Postal 

Code (untitled) 

The ZIP or Postal code for the current person. 

From 

The date when this address became active. 

Telephone Type 

The telephone type for the current person. 

Telephone 

Number 

The telephone number associated with this address. 

To 

The date the address will become inactive. 

The GUASYST button takes you to the GUASYST form, where you can see the 

modules in Banner in which the current person is set up. You can easily see which 

modules are allowed to update address and telephone information for the current 

person. 

To display the modules for which a household member is set up from APAIDEN, 

select the Update check box for that member, and perform a Count Query Hits. 

Household Members Window 

This window displays the information about the other members of the current 

person’s household, based on address type. 

If the address or telephone information for that member differs from the 

information for the current person, a pound sign (#) appears before the 

appropriate row. 

Note: Although they are not displayed, street line 2, street line 3, county and 

nation are used by the programming logic to see if the household 

member’s address information matches the current person’s. 

All these fields, except for the Update check box, are display only. 




Changed Forms 

Fields 

. . . . . . . . . . . . . . 

Update 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

If selected, the address and telephone information for this 

household member will be changed to match the current 

person’s information when you save the record. 

You will also select this if you want to make the displayed address 

for this household member inactive. After you select it, click on 

the Inactivate Selected Household Addresses button. 

Name 

The household member’s name. 

ID 

The household member’s Banner ID. 

Cross Reference 

The cross reference code from ATVXREF that defines this 

household member’s relationship with the current person. 

Age 

The household member’s age. 

Address 

The street address for the household member. 

City (untitled) 

The city of the household member. 

State or 

Province 

(untitled) 

The state or province for the household member. 

ZIP or Postal 

(untitled) 

The ZIP or Postal code for the household member. 

Telephone 

Number 

The telephone number of the household member. 

From Date 

The date on which the address became active. 

To Date 

The date on which the address will become inactive. 

The Inactivate Selected Household Addresses button allows you to make addresses 

for the household members inactive. Select the Update check box for the 

appropriate household members, then click on this button. The addresses for those 

members become inactive. 




Changed Forms 

Note: You should only do this if there are other good addresses that are known 

for the household. Be careful not to inactivate the last known active 

address, unless you’re sure you want to do that. 

Cross Reference Form (APAXREF) 

A new check box has been added to this form: 

Fields 

. . . . . . . . . . . . . . 

Household 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

This check box indicates if the person is a member of the same 

household as the person in the key block. Valid values are: 

selected - the people are in the same household 

cleared - although they may be related, the people are not in the 

same household 

This check box will be selected by default if the Type code has 

been defined on ATVXREF as being part of the same household. 

You can update this check box as necessary. 




Changed Forms 

Cross Reference Code Validation Form (ATVXREF) 

A new check box, Household, was added to this form: 

Fields 

. . . . . . . . . . . . . . 

Household 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Indicates if the relationship defined by the code should be 

considered to be part of the same household. For example, you 

would probably consider spouses to be in the same household, 

but not a person and corporate headquarters. Valid values are: 

selected - people with this relationship should be considered to be 

in the same household 

cleared - this code does not define a relationship where members 

are part of the same household 

Note: To make sure your forms and processes behave consistently, Banner will 

select the Household check box for the reverse value, too. For example, 

if you select Household for Husband, the form will automatically select it 

for Wife. 




Changed Forms 

Children Information Form (APACHLD) 

The Household indicator has been added to this form in two places: 

Children Information Window 

Fields 

. . . . . . . . . . . . . . 

Household 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Indicates if the child is a member of the same household as the 

person in the key block. It is selected by default if the Household 

indicator on ATVXREF has been selected for the Current Cross 

Reference code. Valid values are: 

selected - this child is a member of the same household as the 

person in the key block 

cleared - this child is not a member of the household 

You can override the default value. 

Create Child Relationship for Additional ID 

If you are adding a relationship for the child with another person, and you know 

that the new person is part of the same household as the child, select the Household 

indicator. 




Changed Forms 

Fields 

. . . . . . . . . . . . . . 

Household 

Descriptions 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Indicates if the child is a member of the same household as the 

person being added. It is selected by default if the Household 

indicator on ATVXREF has been selected for the Additional ID 

Cross Reference code. Valid values are: 

selected - this child is a member of the same household as the 

person in the key block 

cleared - this child is not a member of the household 

You can override the default value. 

System Identification Form (GUASYST) 

Changes were made behind-the-scenes for GUASYST so that when you selected the 

GUASYST button on the APAIDEN form, GUASYST would appear. It will display the 

modules for which the current person is set up. 

To display the modules for which a household member is set up from APAIDEN, 

navigate to the record for that member, and perform a Count Query Hits function. 

For more information, please refer to the SCT Banner General 7.1 Release Guide. 



Section 2 Household Enhancement - Technical 

New Script 

Section 2 

Household Enhancement - Technical 

New Script 

aofhhld1.sql 

This script defines a new function, f_session_id_active_ind, that makes sure 

multiple users cannot update addresses for the same household at the same time. 

household_child.sql 

This script creates the household link between parents and children in the 

APRXREF table. 

household_general.sql 

This script creates the household link between general cross-references in the 


household_spouse.sql 

This script creates the household link between spouses for existing records in the 


Changed Script 

aludbpr.sql 

This script was changed to include the new aohhld.sql script. 




Changed Tables 

Changed Tables 

Cross-Reference Repeating View Table (APRXREF) 

A new column was added to this table to hold the household indicator. 

Column Name Null Data Type Description 

APRXREF_HOUSEHOLD_IND Not null VARCHAR2(1) This indicator identifies whether or not the 

person with this XREF lives at the same address as 

the one identified by reverse. It should always be 

the same for both the XREF and the reverse. It 

defaults to value on ATVXREF, but may be 

overridden by the user. 

Cross-Reference Validation Table (ATVXREF) 

A new column was added to this table to hold the new household indicator. If this is 

Y, the Household indicator will be selected by default for that relationship on 

APAXREF, APAIDEN, APACHLD, and APACONS. 


ATVXREF_HOUSEHOLD_IND Not null VARCHAR2(1) Specifies if the relationship represented by the 

code can be part of a household. The valid values 

are: 

Y - the relationship can be part of a household 

N - the relationship is not part of a household 

(default) 

Advancement Installation Control Table (AUBINST) 

Two new columns have been added to this table to store: 

1. The value for the new Household Member Address Automatically-Flag-for- 

Update Default field on AGACTRL. It specifies if the Update check box should 

be selected by default on the Household Members tab on APAIDEN for records 




New Function 

where the address or telephone information does not match that of the current 

person. 

2. The value for the Address Source field on AGACTRL. It specifies the default 

address source to be used when automatically updating address details for 

members of a household. 


AUBINST_DEF_HOUSEHOLD_ 

IND 

Not null VARCHAR2(1) Specifies if the Update check box should be 

selected by default: 

Y - the check box should be selected by default. 

N - the check box should not be selected. Users 

will have to select the Update check box for each 

record they wish to update. 

AUBINST_DEF_ASRC_CODE VARCHAR2(4) Specifies the default address type to use for the 

household members. The values must already 

exist on the STVASRC table. 

New Function 

f_session_id_active_ind 

This function makes sure multiple users cannot update addresses for the same 

household at the same time. It is defined by aofhhld1.sql. 




New Function 

This page intentionally left blank 



Section 3 Problem Resolutions 

External Data Load 

Section 3 

Problem Resolutions 

This section lists the problem resolutions included in Release 7.1. 


APASRVW.FMB (#100982) 

Previously, when you created or linked constituent spouse relations records on the 

Spouse Review Form (APASRVW), APPCUPD.PC would only create the Constituent 

Spouse Table (APRCSPS) record for the ID in the key block. It would not create the 

corresponding APRCSPS record for the other ID. 

In addition, when APRXREF records were loaded via APASRVW, the 

APRXREF_CM_PRI_IND column was set to null, rather than being populated with P 

(primary spouse) for the ID in the key block and S (secondary) for the other 

APRXREF spouse record being created. 

Now, when you create records via APASRVW form, APPCUPD.PC correctly creates 

both spouse records when the incoming spouse record has an ID. It also updates 

APRXREV_CM_PRI_IND on the APRXREF table correctly when the spouse record is 

loaded. Resolved in Release 7.1. 

APILRVW.FMB (#102406) 

Users could receive an ambiguous error message when they attempted to 

acknowledge a load of processed employment records. The message, *ERROR* Load 

Activity Failed, appeared whenever required information was missing from employer 

detail records. 

To resolve this problem, the error message has been changed to make it clearer. It 

lists the ID for which data is missing, and specifies what the missing data is. Resolved 

in Release 7.1. 

APPCUPD.PC (#103191) 

When you executed APPCUPD.PC to load a delimited data file, the process had not 

been clearing out all the temporary details held for review from the previous record 

if the subsequent records were shorter. This resulted in the trailing characters being 

appended to the end of the new record details, creating the potential for bad data 

to be added to the Banner tables. This has been corrected. 

Note: Use the associated .lis files created by the Update runs of APPCUPD.PC, if 

they are still available, as a starting point to see if any of your data has 

been affected. Visually review the reports to help identify any bad data. 





If the data loaded by APPCUPD is data that goes into one of the review 

tables (APRCRVW - Child Review, APRDRVW - Degree Review, 

APRERVW - Employer Review, or APRSRVW - Spouse Review) you can see 

the bad data on their review forms (APACRVW, APADRVW, APAERVW, 

and APASRVW, respectively). Do not push records that contain bad data 

to the database; correct the records manually or delete them. 

For data that could have been directly loaded to the base tables, review 

the tables (listed below) for records with changes since you ran the data 

load in update mode using the date for selection. 

The base tables potentially affected include SPRIDEN, SPBPERS, 

SPRTELE, GOREMAL, APBCONS, APRCATG, APRACTY, AMREXRT, 

APREXCL, AMRPUSR, AMRPRSC, and AMRPSRC. 

Resolved in Release 7.1. 

(#97481) 

Previously, this process was reading delimited input files without regard to the file 

definition details, so the process would not recognize that anything needed to be 

updated for the ID in question. 

Now it reads the data file definition for character delimited files correctly, and it 

allows users to skip files within the data file that will not be loaded. The logic that 

parses delimited files will correctly extract the values from each input line. Resolved 

in Release 7.1. 

(#97630) 

The tables AGRTPDF and APRTPFG where changed to no longer store an activity 

date with an incoming address in a previous release. Because this process still 

expected to find them (as AGRTPFD_ADDR_ACTIVITY_DATE and 

APRTPFD_ADDR_ACTIVITY_DATE, respectively) users would receive the error 

message ORA-01843: not a valid month. 

The code to handle AGRTPFD_ADDR_ACTIVITY_DATE and 

APRTPFD_ADDR_ACTIVITY_DATE has been commented out two scripts have been 

delivered to remove data from the tables; agrtpfd2.sql to remove the activity date 

information from the AGRTPFD table, and aprtpfd2.sql to remove it from 

APRTPFD. 

Note: These scripts are described in the SCT Banner Advancement Upgrade Guide. 

Now the load process identifies the activity date as the date of execution, and does 

not require any additional information for the activity date. Resolved in Release 7.1. 

(#95705) 

Previously, this process would generate the following error messages whenever an 

International zip code was part of an address: ORA-01858: a non-numeric character was 

found where a numeric was expected. Now the process loads International ZIP codes 

(which contain non-numeric characters) with no errors. Resolved in Release 7.1. 





(#95625) 

PREF_MAIL was listed on the Data Field Names Validation Form (ATVTPFD) as a 

delivered, supported field, but this process was referencing PREF_EMAIL_CODE 

instead. 

The description for PREF_ADDRESS_CODE has been changed on ATVTPFD to more 

accurately describe the purpose of the field. All references to PREF_MAIL have been 

removed - they were duplicates of PREF_ADDRESS_CODE. A script, aprtpfd.sql, has 

been provided to change all the records in the AGRTPFD table that had referenced 

PREF_MAIL to reference PREF_ADDRESS_CODE. 

Note: This script is described in the SCT Banner Advancement Upgrade Guide. 


(#90562) 

This process was changed to stop inserting a trailing slash (/) for the file location, 

which caused errors on the VMS platform. Now users must identify the full file 

location details, including any trailing / requirements. Resolved in Release 7.1. 

(#94216, related to #89658) 

Previously, APPCUPD.PC would allow you to load more than one preferred e-mail 

address. If a new preferred address was included in the data load, and one already 

existed on the database, the process would load the new one in addition to the old 

one. 

Also, it would allow you to load a new primary telephone number when one already 

existed on the database for that address type and sequence. Now the process checks 

the telephone information against the database and, if there is a new primary 

telephone record, it makes the old one inactive. 

Note: You can now define a stand-alone telephone number to be inserted into 

the database without a corresponding address record by mapping the 

details of the new record to the fields PHONE, PHONE_ALL, PHONE_AREA, 

and PHONE_EXT. 


(#94677) 

Previously, APPCUPD.PC only looked at the names that matched the specified type 

instead of checking all existing SPRIDEN name records when it was executed in 

update mode. Now the process will insert a new SPRIDEN record when the 

incoming details do not exactly match the existing first, middle and last name 

details, and there are no previous name records that match the details exactly. 


(#98930) 

APPCUPD.PC had been loading source values with whatever values that were 

provided, even though a source value means nothing without a score, value, or level 





- it is invalid data. Now the process will not insert a record unless the score, value, or 

level is provided in addition to the source value. Resolved in Release 7.1. 

(#98951) 

APPCUPD.PC has been changed to review existing e-mail records to see if there are 

duplicates, and it will no longer insert a duplicate record. It also checks to see if the 

preferred indicator is selected for the e-mail type and will update the preferred 

indicator for the existing e-mail address if the indicator has not already been 

selected. Previously, the process was inserting duplicate records with multiple 

records designated as the preferred e-mail address. Resolved in Release 7.1. 

(#101561) 

The version of APPCUPD.PC delivered with problem resolution #94677 had compile 

issues. They have been corrected. Resolved in Release 7.1.

SCT Banner Advancement / Release Guide / 7.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?