SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsSupport Services ModuleSPAPERS (#89039)When an SSN/SIN/TFN is saved that already exists in the database, the pop-upwindow with a warning message will now be displayed consistently. The message inthe window reads: “*WARNING* SSN/SIN/TFN/ already assigned to another record.”Resolved in Release 6.2.TableSPBPERS (#71953)Problem resolution #45031 completed in Release 5.2 corrected the situation whereSPAPERS was updating the SPBPERS_CONFID_IND field to Y or Null, instead of Y orN. The code fix set the value of the SPBPERS_CONFID_IND field to N when theConfidential (Indicator) field was unchecked on SPAPERS. This correction workedwith future records but not past records. Past records now have three values for theSPBPERS_CONFID_IND field: Y, N, or Null.A new non-display field has been added to the SPBPERS block for theSPBPERS_CONFID_IND field, that sets the initial field value to N instead of Null.The following objects affected by this scenario have also been corrected in Release6.1 or in a previous release.• sfarqst.fmb - Corrected in Release 5.4.• sprpdir.pc - Corrected in Release 5.4.0.1.• slarmap.fmb - Corrected in Release 5.4.0.1.• shacrse.fmb - Corrected in Release 5.4.0.1.• sortape.pc - This object was made obsolete with Release 6.0.• saaquik.fmb - Corrected in Release 6.1.• sraquik.fmb - Corrected in Release 6.1.• srkpre1.sql - Corrected in Release 6.1.• supdper1.sql - Corrected in Release 6.1.Support Services ModuleFormsSEADETL (#93197)Previously, place holders for the *CONFIDENTIAL* and *DECEASED* messagesappeared as white blotches above the ID field in the Key Block. These blotches havebeen removed as part of the new user interface technical methodology beingapplied to all forms where the messages appear. Resolved in Release 7.0.January 2005 Student Release 7.0Confidential Release Guide 325