SCT Banner Advancement / Release Guide / 7.1

More documents

Recommendations

Info

Section 3 Problem Resolutions External Data Load 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. Advancement Release 7.1 May 2005 24 Release Guide Confidential
Section 3 Problem Resolutions External Data Load (#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. Resolved in Release 7.1. (#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. Resolved in Release 7.1. (#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. Resolved in Release 7.1. (#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 May 2005 Advancement Release 7.1 Confidential Release Guide 25
Page 1 and 2: SCT Banner Advancement Release Guid
Page 3 and 4: Release Guide Advancement System Ov
Page 5 and 6: Overview Overview This guide descri
Page 7 and 8: Section 1 Householding Enhancement
Page 19 and 20: Section 2 Household Enhancement - T
Page 21 and 22: Section 2 Household Enhancement - T
Page 23: Section 3 Problem Resolutions Exter

SCT Banner Advancement / Release Guide / 7.1

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

Delete template?

Save as template?