Docstoc

MCARRI NC TT

Document Sample
MCARRI NC TT Powered By Docstoc
					Issue Description Documentation                                                                         Page 1 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




1164684000 AA 8 SP1: Courses graded incomplete and marked, as repeats are still satisfying advisement
requirements
Student has courses that are graded with an incomplete grade (an in-progress grade in the grading basis table). The
course has been manually updated with a repeat code that turns the earned credit flag off. The courses are still
satisfying advisement requirements that have a wildcard course list. Per documentation, a course list to intersect
only courses that have earned credit was attached and no change occurred. It appears the advisement logic is not
evaluating the course beyond the in-progress grade assigned.

Resolution: Modified SRPCACOL to correctly set the earned credit flag based on the values off STDNT_ENRL if the
REPEAT_CODE has a value.


1231588000 AA 8 SP1: Authorize Student Exceptions To tab does not display requirement group descr. Navigation:
Manage Student Records, Define Academic Requirements, Use, Authorize Student Exceptions
Prior to SA Bundle #7, the requirement group title displayed when creating an authorized student exception on the
TO tab. After SA Bundle #7, the title or descr no longer displays.

Resolution: Made major changes in the component STDNT_RQ_DRCT_DET and associated pages, views, and
record peoplecode to correctly fix the problem.


1246653000 AA 8 SP1: Requirement prompt in authorize student exception referencing incorrect row following SA
Bundle #7.
 After applying SA bundle #7, customer is finding that users cannot enter any more authorize student exceptions of
the Requirement Change type. The prompt for requirements does not seem to reference the requirement term or
requirement group selected; it either returns the requirements on the earliest effective dated requirement group row,
or the most current effective dated row requirement group requirements.

Resolution: Changed the properties on the Advisement Override Scroll on the page AA_OVRD_COLLISION to not
do any automatic SQL processing.


1256034000 AA 8 SP1: After SA Bundle #7, requirement descr (related display) on requirement group does not
display.
When adding a requirement line type to either an Enrollment Requirement Group (on Requisite Detail page) or to an
advisement Requirement Group (Detail page), the requirement descr does not display until the page is saved. Prior to
SA Bundle 7, the requirement descr displayed as soon as the user tabbed off the field.

Resolution: Made major changes in the component STDNT_RQ_DRCT_DET and associated pages, views, and
record peoplecode to correctly fix the problem.


1261916000 AA 8 SP1: Update ID 607718 People Code error when creating student exception when TO group
value is blank.
When creating a student exception requirement group override following the application of critical fix in Update ID
607718, if the user clicks OK button without entering a TO value for the requirement group, a peoplecode error is
returned.

Resolution: Made major changes in the component STDNT_RQ_DRCT_DET and associated pages, views, and
record peoplecode to correctly fix the problem.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 2 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




1132518000 AD 8 SP1: A data conflict error occurs when the same plan is added to more than 1 program at the first
time save (adding subsequently the same plan after the first, works okay) on application entry after SA bundle #2 A
data conflict error occurs when the same plan is added to more than 1 program at the first time save (adding
subsequently the same plan after the first, works okay) using the following link: Home > Develop Enrollment >
Process Applications > Use > Application Entry
E.g.,
Prog 0: BUS with DBBA plan
Prog 1: BUS with DBBA plan

Resolution: Modified Peoplecode to add plan and subplan information to the prospect record only if it does not
currently exist, regardless of the program number from the application.


1163570000 AD 8 SP1: Changes to EOS Record Layout
ACT has changed the EOS layout for 2004 - 2005. Changes include the removal of the Grade Classification and
Batch Processing Number as well the codes used for Gender.

Resolution: Modified ADEOSLOD.SQR, ADEOSPST.SQR to account for changes to the layout.


1171715000 AD 8 SP1: LSDAS loading problem.
After loading the LSDAS data (adlstlod.sqr), some suspense records cannot be accessed through the Law Suspense
page. All these records have multiple test scores. The screenshots of this error are attached. Started to get the
Numeric value out of range error when trying to pull up record 76 (as the test number for that record added up to
100). That test number in ADLSTLOD.SQR was populated from #seq_no, which doesn't get reset any where in the
program.

Resolution: Modified ADLSTLOD.SQR and the LSDAS suspense pages.


1216335000 AD 8 SP1: Grades posting in ADTRNPST is not consistent with manual entry.
In SA Bundle 1 the External Course page in the Education Component was revised so that when a user enters a
grade in the Grade In field, the Official Grade field populates automatically (Incident 518966000). In EDI processing,
this does not occur - the Official Grade field is blank. This creates inconsistencies in the data depending on how it
was entered.

Resolution: Modified adtrnacd.sqc to mimic the behavior of the education component.


657215000 CC 8 SP1: DDA: Invalid Date (2,112) at SA_Bio_Demo_Data3: Activate PCPC:3839 Statement 48 An
invalid date has been encountered in the Peoplecode Program
Get the following error when moving from any page in a Biographical Data component back to the Bio/Demo Data
page. Invalid Date (2,112) at SA_Bio_Demo_Data3: Activate PCPC:3839 Statement 48 An invalid date has been
encountered in the Peoplecode Program. The users who get the error have a primary permission list for display only
of Bio/Demo Data and partial masking of Birthdate.

Resolution: Added a component boolean check to only format the date/nid once, as they will not be editable for DDA
masking to be applied. This becomes the wrapper around the Masking code in
SA_BIO_DEMO_DATA3.PageActivate.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                           Page 3 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




661606000 CC 8 SP1: Cursor returns to top of page after returning from Sub Pages
After entering information in subpages (i.e. see Birth Information, Citizenship, Ethnicity Detail, etc on BIO/DEMO
pages) the cursor returns to the top of the initial page. This is having drastic effect on "heads down" data entry -
causing the data entry people to have to hit tab 20 - 30 times after each bit of data is entered.

Resolution: Created 6 new fields and added into DERIVED_CC1 record such that each field represents independent
hyperlinks in SA_BIO_DEMO_DATA3 page. Added new field change people code to transfer the navigation using
DoModal function. Created 3 new Message Catalog Entries to display the heading in the secondary pages.


724385000 CC 8 SP1: Problems when trying to add a new External Organization in CFR
When we click on "Ajouter" (Add), the External Org Id has the default value of "Nouveau" (New). But PeopleSoft
looks for "NEW" in order to look for the Next Available Id. "Nouveau" doesn't trigger the "get Next available Org Id" so
it will create the External Organization with the Id of "Nouveau".

Resolution: Changed the Peoplecode to look for the message catalog entry that designates a "NEW" organization,
instead of a hard coded value.


727747000 CC 8 SP1: Future inactive rows are populated into Personal Data and Pers_Data_effdt
PS_PERSONAL_DATA and PS_PERS_DATA_EFFDT update address fields with inactive future addresses. This is
a departure from how 7.6 worked and how we expect 8 to work. The code should be checking EFF_STATUS on
PS_ADDRESSES.

Resolution: Modified Record People Code ADDRESSES.EFF_STATUS.SavePostChange.


728662000 CC 8 SP1: FUNCLIB_HR.NID_SPECIAL_CHAR.FieldFormula problem after applying Update id
125279
After applying HR 8 SP1 Bundle #4 (Update ID 125279) record FUNCLIB_HR.NID_SPECIAL_CHAR.FieldFormula
has a National Id (SSN) display format problem in SA_BIO_DEMO_DATA3. We have attached our code listing of
Record FUNCLIB_HR.NID_SPECIAL_CHAR.FieldFormula that is causing a National Id (SSN) display format
problem in SA_BIO_DEMO_DATA3 Page.

Resolution: Modified Record People Code FUNCLIB_HR.NID_SPECIAL_CHAR FieldFormula.


740971000 CC 8 SP1: Process > Checklist > Item Update - Automated: Get SQL error in ccucitms.sqc
When attempting to update checklists (Home>Build Community>Checklists>Process>Item Updated-Automated), the
user receives an error. The process runs ccitmupd.sqr, which includes ccucitms.sqc. When the sql query that
updates PS_PERSON_CHK_ITEM runs, it errors out because the "WHERE" condition it builds does not escape the
strings around the $NAME variable. An error will be produced whenever the Name has a single quote somewhere
within the string--a not uncommon condition. (In our case, "ST MICHAEL'S CATHOLIC ACADEMY" triggered the
error.)

Resolution: The procedure Update-Checklist-Item-Status in ccucitms.sqc has been modified such that if any quotes
present in the External Organization Name then an extra quote is appended to the existing name.


1159602000 CC 8 SP1: 3C Engine - Performance Issue.
Customer is experiencing a 3 to 4 minutes delay to save an application instance when the 3C engine is triggered.
The biggest bottleneck appears to be a delete statement against PS_ENG_CHKD_TMP2.



                                      Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 4 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




Resolution: This resolution is specific to the 3CENGINE app engine process. It targets the Manage Duplicate
Assignment feature of the 3CEngine Run Control. The main goal was to reduce the number of database hits against
the Communication table and/or the temp table loads from the Communication table. The following modifications
were made to 3CENGINE_LIB:

Duplicate Communication Check

Section Step Action Comment:
CONDEXST STEP01 SQL Update InsertSelect statement to include COMMON_ID. Bind in Process Instance
CONDEXST STEP02 SQL Delete - no longer needed
NOCOND STEP01 SQL Update InsertSelect statement to include COMMON_ID. Bind in Process Instance
NOCOND STEP02 SQL Delete - no longer needed
ONLINE STEP01 SQL Update InsertSelect statement to include COMMON_ID. Bind in Process Instance
ONLINE STEP02 SQL Delete - no longer needed
ONLINE STEP03 SQL Delete - no longer needed
COMMVARD STEP02 Peoplecode Update InsertSelect statement to include COMMON_ID.


Duplicate Checklist Check

Section Step Action Comment:
CHKDUPU2 STEP01 SQL Update InsertSelect statement to include COMMON_ID. Bind in Process Instance
CHKDUPU2 STEP04 SQL Delete - no longer needed
CHKDUPU STEP02 SQL Update InsertSelect statement to include COMMON_ID. Bind in Process Instance
CHKDUPU STEP 04 SQL Delete - no longer needed
CHKVARD STEP04 Peoplecode Update InsertSelect statement to include COMMON_ID.


1213161000 CC 8 SP1: Update id 597769 fixes the security issue but causes the following error on
USER_SELF_SERVI_SA.
PeopelSoft is missing the field "OPRDEFNDESC" on new delivered page USER_SELF_SERVI_SA in this recent fix.
Please see attachment for error -this occurs when a user does not have an ID associated to their User Profile. Field
does not exist - CC_OPRDEFN_SRCH.OPRDEFNDESC at SS_CC_MYPROFILE.GBL.

Resolution: OPRDEFNDESC was added as a hidden field to page USER_SELF_SERVI_SA.


1219728000 CC 8 SP1: Two issues: U151733B.SQR in update # 151733 inserts non-current rows; Script
upd151733_9.dms errors out for some clients.
Issue #1: In update # 151733 (SA 8 SP1 Bundle #7) (issue 737685000) there is an SQR U151733B.SQR, which we
are instructed to run to correct discrepancies between name fields in NAMES, PERSONAL_DATA, and
PERS_DATA_EFFDT. When discrepancies are found between NAMES and PERSONAL_DATA, the names fields in
PERSONAL_DATA are updated. There is logic to decide whether a new row should be inserted in
PERS_DATA_EFFDT when the PERSONAL_DATA update occurs. However, the logic here is incomplete. It will only
end up inserting a non-current (older) row into PERS_DATA_EFFDT. What needs to happen is that if
PERSONAL_DATA is updated, the current row in PERS_DATA_EFFDT needs to be updated so that the names
fields match. With the logic as written, in some cases you end up with NAMES and PERSONAL_DATA in synch,
after updates to PERSONAL_DATA, but a mismatch of the name fields in the current row in PERS_DATA_EFFDT.
Issue #2: A few customers have reported getting an error running script upd151733_9.dms because of mismatched
Transfer Credit Detail and External Course records. A modified version of the script is required to avoid this problem.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 5 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



Resolution: Issue #1: Updated sqr script, U151733b.sqr originally distributed with SA SP1 Bundle #7 that addressed
incident 737685000. The sqr now identifies inconsistent names information across three records, NAMES,
PERS_DATA_EFFDT and PERSONAL_DATA including the fields LAST_NAME_SRCH, FIRST_NAME_SRCH,
SECOND_LAST_SRCH and PREF_FIRST_NAME previously missed in the original sqr.
Using the NAMES record as the master for names information the following scenarios are employed.
1. If the current effective date for the NAMES record is greater then the current effective date for record
PERS_DATA_EFFDT for an ID a new row will be entered for PERS_DATA_EFFDT with the information contained in
the NAMES record.
2. If the current effective date for the NAMES record is equal to the current effective date for record
PERS_DATA_EFFDT for an ID and there is inconsistent data, the row contained in PERS_DATA_EFFDT will up
updated with the information contained in the NAMES record for that row.
3. If the current effective date for the NAMES record is less than the current effective date for record
PERS_DATA_EFFDT for an ID, a message line is printed stating the inconsistent data and need for manual
intervention.
4. If the information contained in PERSONAL_DATA does not match that contained in the current effective dated row
in NAMES, the PERSONAL_DATA record will be updated with the information contained in the NAMES record.
5. If max effective dated rows are future dated and contain inconsistencies in their data, a statement containing the
mis-matches will be printed at the end of the report.

Issue #2: Modified script upd151733_9.dms to update only the Transfer Course Detail rows with matching External
Course records in the Education component. This modified script can also be found in Customer Connection as
Solution ID = 200966169 (SR 8SP1: UPD151733_9.dms from SA 8SP1 Bundle #7 fails). Clients who downloaded
the script from Customer Connection do not need to run it again.


1224867000 CC 8 SP1: Password and Personalization page does not enforce proper validation when doing a
password change
The SA 8SP1 Personal Portfolio Password and Personalization page is not enforcing proper current password
validations when a user is changing a password.

Resolution: Peoplecode was added to component SS_CC_MYPROFILE so that the edits in component
USERMAINT_SELF are also enforced in the Student Administration's password change page.


658290000 CR 8 SP1: Lifetime Giving Clubs member summary and details not working
When creating a giving club and NOT selecting the "Reset Membership at Fiscal Year" checkbox (lifetime clubs),
then manually entering members through Use - Giving Club Membership, the giving club summary and detail are not
updated with members. It continues to show zero members. However, if you go to the member's giving club
progress page, the club displays there.

Resolution: Modified peoplecode AV_GCLUB_LVL.GCLUB_LVL.ROWINIT.


665972000 CR 8 SP1: Mass Actions does not populate Prospect Managers
When using Mass Actions (as opposed to creating an individual action), the Prospect Manager does not appear on
the Action.

Resolution: We modified the Mass Action Peoplecode to carry the identified Prospect Manager for each constituent
forward to the newly created action.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 6 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




735968000 CR 8 SP1: Outreach View Person/Org components do not have a link to Resource Assignments
Outreach officers need to view Resource Assignments along with other summary/inquiry screens from Outreach.
Navigation: Outreach > Outreach Officer > View Prsn
Most of the inquiry screens that are listed in CR > Manage Prospects > Inquire, are also on the Outreach menu for
Outreach Officer > View Prsn and the Outreach menu for View Org as well. One of the exceptions is Resource
Assignments. You cannot access a person or org resource assignment summary from the Outreach menus.

Resolution: We added the View Prospect Assignments components on to the Outreach Menu for both Persons and
Organizations.


741280000 CR 8 SP1: Acknowledgement Process cannot use Service Indicators for Orgs to identify which
Acknowledgement letter the org should receive.
 Acknowledgement Process cannot use Service Indicators to identify which Acknowledgement Letter an Organization
should receive.

Resolution:
1.) Added Service Indicator Acknowledgements for ORG's
2.) Created new working storage S-SVCIND3.
3.) Created new stored statement S_SVCIND3 in AVPACKNL.DMS
4.) Created new paragraphs ME200-SELECT-SRVC-IND-ORG and ME250-FETCH-SRVC-IND-ORG


1127539000 CR 8 SP1: Outreach Incident: prompt for ask only if ask.
Outreach should only prompt the user for ask amounts (AV_OUTR_ACTN_ASK) if on the previous page they
selected the Action Type of "Ask" (AV_OUTR_ACTN_DTL).

Resolution: We changed the stepping process in the Outreach Add/Update An Action component to bypass the
ASK page (page #2) when the action type is not ASK. Step #2 will still be available for returning to or directly
accessing after initially passing it. We changed initialization Peoplecode to Grey or UnGrey the ASK fields,
depending on the type of the action.


1128276000 CR 8 SP1: Outreach: email an action that doesn't have an associated contact report
Create the ability to email an action that doesn't have an associated contact report. AV_OUTR_CNCT_SEND could
be an option added to the end of the "Add/Update an Action" function, the "Complete an Action" function as well as
the "Complete a Contact Report" function.

Resolution: We added the Send Contact button and page to the Outreach Add/Update An Action component and
the Complete An Action component. We added Peoplecode to format the Send Contact email from the new locations
as well.


1128287000 CR 8 SP1: Outreach: Action Details on Email
Outreach: Include Action details on the email as well as the Contact Report contents. (dates, contact types, involved,
results, etc) The current contact report email doesn't even positively identify the prospect (emplid) The full action
details should be included on the email.

Resolution: We changed the Send Report Page and it associated Peoplecode to provide more information. The
contact email now consists of a Constituent section, an Action Section, and a Contact Report Section. The
Constituent section details ID, Name, Constituent Type, City and State, Prospect Manager, and Gender. The Action




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 7 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



Section details Number, Brief Description, Description, Planned Date, Complete Date, Action Type, Contact Type,
Status, and Result. The Contact Report section details Author, Report Date, and the Contact Report itself.


1128501000 CR 8 SP1: Outreach: can set an action to Complete without entering a result code.

In CR, when you enter an action that is complete or you modify an action to status = complete, you are required to
enter an Action Result code. However, on Outreach you can enter an action, mark it complete on the first pass, and
you are not required to enter the Result code and you are not prompted for the result code. On the last "page" of the
action entry you get a summary which displays the action result as blank and it allows you to edit the result from
there, but it should be part of the data entry "flow" and should be required if the action is set to complete.

Resolution: The Outreach Add/Update an Action behavior was changed to bring it more inline with the Prospect
Manager Action component. The Add/Update an Action page was changed to include a secondary page for entering
Action completion information. It was also noticed that unlike the Prospect Manager Actions component, the
Complete An Action component was allowing the edit of the Actual Commitments Amount field. This field was
changed to a display only field and calculated based on the Pledge and Gift(s) attached to the Action. The Total
Commitments field on the Add/Update and Action summary page was also modified to perform and display the same
calculated amount.
   We modified shared Prospect Manager and specific Outreach Peoplecode to perform Action Results calculations,
Status Code change formatting, and Completion Status editing similar to the Prospect Manager Actions component.


1157158000 CR 8 SP1: Changes to ACAD_ORG table wipes out Internal Legacy Degree.
Whenever changes are made to the ACAD_ORG table, it has the possibility of wiping out our Legacy Degree
information. For example when the nursing program was ended at Cornell, the value was inactivated in the
ACAD_Org table. At that point for anyone that had received a degree in that program - where the degree information
was entered on the Internal Legacy Degree page - the Acad Org now shows an (invalid value) instead of Nursing.
We can't have our information wiped out every time a change is made.

Resolution: Created a derived record DERIVED_AV_EFDT with one field EFFDT as key. Added that field to pages
AV_LEGACY_DEG and AV_LEGACY_DEG_INQ. Wrote Peoplecode in AV_LEGACY_DEG.AV_CLASS_YR.RowInit
and FieldChange to populate DERIVED_AV_EFDT.EFFDT with a date that corresponds to the class year.
Created view AV_ACD_ORG_VW and used AV_ACD_ORG_VW.DESCR to display the description in page
AV_LEGACY_DEG and AV_LEGACY_DEG_INQ. Created view AV_CMPS_TBL_VW and
AV_CMPS_TBL_VW.DESCR to display the description in page AV_LEGACY_DEG and AV_LEGACY_DEG_INQ.



1209250000 CR 8 SP1: Role missing from Mass Action and Mass Action Workset.

Customer would like to be able to specify roles for 'others assigned' to a mass action. This is captured on the Action
page, but both Mass Action and Mass Action workset (AV_MASS_ACTN) are missing this field for data entry.

Resolution: We changed the Mass Action Component to allow the entry of a Role for each Others Assigned
Resource. We added and modified existing Peoplecode to initialize the prompt for the Role based on the Assignment
Type and the Installation Assignment Role Option.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                          Page 8 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




1219510000 CR 8 SP1: Membership Adjustment Screen repeating start date warning message too many times
Membership Adjustments for RENEWED memberships where users enter a new end date (to cancel a membership)
result in a warning message being shown for multiple emplids in session, not just emplid being adjusted.

Resolution: Modified record Peoplecode AV_MBR_DTL.MBR_PMT_NO.SaveEdit. Added a check at the top of the
loop to only check the adjusted dates if the rowset had been changed.


41512000 FA 8 SP1: Budget Formula - Processing Order field needs an edit to prevent duplicates.
Panel: BUDGET_FORMULA
The Processing Order field on the BUDGET_FORMULA panel needs an edit to prevent a duplicate value. If a
duplicate value is entered for some Budget Item Code the Budget process will fail with the following error: SQLRT:
DA000-FETCH 00936 ORA-00936: missing expression. A trace of the Cobol will show a SELECT FROM
PS_STDNT_BDGT_ASGN with a blank WHERE clause.

Resolution: Added Peoplecode to BDGT_FORMLA_TBL.PROCESSING_NBR.FieldEdit to prevent duplicated being
entered.


595189000 FA 8 SP1: FA Term: problem with calculating cumulative statistics
Cumulative statistics are not correct when student does not apply for Financial Aid every year. Scenario: Student is
enrolled in 3 or more consecutive aid years. Student is aid year active in year 1, NOT ACTIVE in Aid Year year 2*,
then aid year active again in year 3. The cumulative units -- total passed and total taken -- for year 3 will calculate
incorrectly. The program starts with the cum units from the last active term (year 1), and adds on the units from year
3, completely ignoring the units from year 2.

Resolution: Modify FAPTRMU1.CBL when verifying prior FA Term row, also check for prior STDNT_CAR_TERM
row. Use stats from the greater of those two prior term data rows.


604417000 FA 8 SP1: Changing the Processing order of budget formulas does not re-order the formulas
The formulas on page BUDGET_FORMULA do not re-order consecutively when the Processing Order is changed or
a new row inserted. The page, when refreshed, should display the formulas in their correct processing order.

Resolution: Added Peoplecode to BDGT_FORMLA_TYP.EFFDT.RowInit to re-order the formulas correctly.


605045000 FA 8 SP1: FA/SR 8SP1: Academic Plans must sort by Plan Sequence number
The Academic Plan sort on the Student Program/Plan pages/tables should be based upon the associated Plan
Sequence number. Currently, the Academic Plan sorts alphabetically. This would allow the Academic Plan
sequenced first to carry to the Financial Aid Term pages/tables. This alphabetic sort is negatively impacting Financial
Aid's day-to-day processing because many of our monetary awards/scholarships are based upon a student's primary
major.

Resolution: FAPTRMU1.DMS modified to order by PLAN_SEQUENCE on S_AP_ACD.


616159000 FA 8 SP1: Inefficient code in FAPTRMU1.DMS makes FAPTRMU1.CBL run long
Customer noticed that after applying Fin. Aids Reg 3 release, the PS-delivered program, FAPTRMU1, began taking
much longer to run. Instead of 2-3 hours, it began taking over 6 hours to run. It appears that a SQL statement in
FAPTRUM1.DMS is one of the causes.




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 9 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



Resolution: Corrected SQL S-DATES in FAPTRMU1.DMS by adding appropriate table aliases.


617703000 FA 8 SP1: Perkins Loan MPN.
Dept of Ed has now published specs for Perkins MPN: http://ifap.ed.gov/dpcletters/CB0311.html
Perkins prom note Master Promissory Note is required by ED in November '04. How is PeopleSoft going to
incorporate the option to print either single or multi-year prom notes? Please keep in mind that users need to assign
checklists for prom notes. The current procedure utilizes an admin function of LOAN with variable data specific to an
aid year. There are problems with this. First, admin function of LOAN dictates that Users send separate missing
information letters, which is poor student service. All missing information related to financial aid should be able to
print on 1 missing information letter. Second, if schools wish to implement a multi-year prom note, students only need
to sign it once. The entire Perkins promissory note printing process needs to be re-examined and redesigned to
incorporate the regulatory changes, and computer based training will also need to be updated. Please design
something that will enable users to assign a checklist that can print on the same letter as other FINA admin function
checklists, and only be assigned for students who have not previously completed a checklist before for a previous
year Perkins Loan. Please see Dear Colleague letter CB-03-14.

Resolution: Created a new process to generate Perkins Master Promissory Notes based on the institution defined
settings on the new Perkins MPN setup page. Also added a new component to track Perkins MPNs. Updated
Authorization to look for a signed Perkins MPN before authorizing funds (for Perkins Item Types that have the new
MPN Required checkbox set).


628005000 FA 8 SP1: FA Term builds an old (prior Aid Year) term from which student withdrew in the current Aid
Year
FA Term Build is building an additional term for the current aid year. This occurs when the students has a prior old
(prior Aid Year) term from which they withdrew. In some cases this wrong term will have an Aid Year value of (Invalid
Value). In other cases, the term will have an Aid Year value of the current Aid Year. In this second case, packaging
will error with "Term Mismatch" errors.

Resolution: FAPTRMU1.DMS modified in S_SC_WDRL to find only those terms withdrawals that have terms set up
in valid terms for career.


630160000 FA 8 SP1: FA: Just in time funding Disbursement Request Offset changed to 7 days for 2003-2004
Page: PELL_PMT_OPTION; Record: PELL_PMT_OPTION; Field: PELL_DISB_OFFSET
According to the COD full participant Implementation Guide
(http://www.ifap.ed.gov/cod/attachments/0304CODVol2Sec1FPIGvApr03.pdf), the number of days a Just in Time
(JIT) institution can submit a disbursement 7 days prior to the actual disbursement date. This is an increase from 5
days in prior aid years. The FieldChange Peoplecode on the PELL_DISB_OFFSET field only allows for -5 days.

Resolution: The Peoplecode has been modified to satisfy the following conditions:
For the Aid Year < 2004, the Disbursement Request Offset should not be less than -5 when Pell JIT Institution check
box is checked.
For the Aid Year >= 2004, the Disbursement Request Offset should not be less than -7 when Pell JIT Institution
check box is checked.


639501000 FA 8 SP1: Problems with DL Disbursements for one-term loans
Users are unable to properly split disbursements for one-term loans. Neither of the Even Split Options allows the
user to split the money between a first and sixth disbursement (in a 10 disbursement setup). 'Even Among First Disb
for Term' puts all of the money in the first disbursement. 'Even across disbs by term' splits the money across all
disbursements. Federal regulation requires a single term loan be split into at least two disbursements.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 10 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



Resolution: Added new functionality and logic to be able to automatically split a single, one term award into 2 or
more equal scheduled disbursement for both DL and other item types. In addition, this feature is accompanied by a
new Disbursement Protection enhancement that was implemented to protect single term scheduled award amounts
in the event that funds have been disbursed to the student and the student is being repackaged. For setup
instructions, more detail explanation, and examples as to how this new feature works please review the
documentation that is supplied with this release.


656250000 FA 8 SP1: Batch Authorization & Disbursement run long because of FAPDISBS_S_DISB and
FAPAUTHS_S_DISB
FAPAUTHS_S_DISB runs long. See the attached batch statistics. Based on the Execution Plan results (also
attached), it looks like the SQL could benefit from some tuning as there are 3 full table scans (the one on
STDNT_AWARDS looks inefficient) and some hash joins. The second statement is FAPDISBS_S_DISB.

Resolution: Added “AND A. SETID =D.SETID” to the FAPDISBS.DMS for both S_DISB and S_DISBITM


661188000 FA 8 SP1: Problem using Marital Status in Budget Formulas
When using Marital Status in a budget formula, no one is selected because the prompt values on the formula do not
match the values on PS_STDNT_BDGT_ASGN. On the Budget formula the valid values are 1-5 but the value
inserted into PS_STDNT_BDGT_ASGN is a character. The MAR_STATUS that is written to
PS_STDNT_BDGT_ASGN is selected from PERSONAL_DATA.

Resolution: Added Peoplecode to BDGT_FORMLA_DFN.FIELD_VALUE.FieldChange,
BDGT_FORMLA_DFN.FIELD_VALUE.RowInit, BDGT_FORMLA_DFN.FIELD_VALUE.SaveEdit to set the correct
marital status values.


673821000 FA 8 SP1: Scroll bar in page PELL_00_OUTBOUND not suppose to be there
Customer found a page (page name pell_00_outbound) in version 8 that in the definition of the page it has a scroll in
it. This causes the page to never come up and then it times out. If they delete the scroll bar the page works fine.

Resolution: Removed Scroll bar from page PELL_00_OUTBOUND.


694253000 FA 8 SP1: Unable to Assign Errors to lowercase User ID on Disbursement Calendar
User receives an error when trying to assign a lowercase User ID to "Asgn Err's To:" on Disbursement Calendar. It
appears the DISB_CAL_TBL.ASSN_OPRID is defined as upper case only.

Resolution: Modified the ASSN_OPRID property to mixed case.


732805000 FA 8 SP1: FAPAUTHP - INSERT COUNTER BLOWN - BUMP IT UP
Two programs one for authorization and one for disbursement have the problem with unique date time stamps for the
following 3 tables. The tables are PS_STDNT_AWRD_ACTV, PS_STDNT_ACTV_COA and
PS_STDNT_ACTV_TERM. The reason for the problem is the date time stamp is a key and only goes to the second
not to sub second values. The COBOL delivered programs that have this problem are FAPAUTHP.CBL and
FAPDISBP.CBL. The programs currently obtain the date and time up to 500 times to see if get a date-time stamp
that is unique for record trying to insert or fail. Both programs could be changed to change the compare value from
500 (in three places in each program) to some larger value and to change the field definition for WK-INSERT-CTR
from PIC 9(3) to PIC 9(4) (in each program) to allow for values up to 9999 rather than 999 being the maximum.

Resolution: Updated the WK-INSERT-CTR to PIC 9(4) and increased the counter check to 9999.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 11 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




738910000 FA 8 SP1: Unable to add new zip code region to Budget Tree
User is attempting add a new zip code region by either (1) using the Budget Tree delivered tree and modifying it or
(2) deleting/renaming the delivered tree, and then create a new tree using the old tree name. Neither is working
however. When trying to add a new region to a new tree the following error is displayed: "Menu not found". There's
currently no Component housing data entry page BDGT_REGION_TABLE (which updates table
BDGT_REGION_TBL). To workaround this, user has to SQL INSERT a row into table BDGT_REGION_TBL.
However, additional problems occur when trying to add nodes to the new region.

Resolution: Created new component BDGT_REGION_TABLE and added it to menu MANAGE_NEED_ANALYSIS.
Created script upd151734_7.dms to populate setup fields for FA_ZIPCODE_REGIONS tree.


740922000 FA 8 SP1: FA: Problem with School ID Reporting Prompt on Print Pell Grant ESOA page (FA870)
Navigation: Administer Financial Aid>Process Pell Payment>Reports>Print Pell Grant ESOA
On the page RUN_CNTL_PG_RPT, the field name TIV_SCHOOL_CODE uses the prompt table
TIV_SCHL_CD2000. TIV_SCHL_CD2000 is a view that contains the following SQL:
SELECT CPS_SCHOOL_CODE,
           DESCR,
           DESCRSHORT
FROM PS_TIV_SCHOOL_TBL
WHERE AID_YEAR='2000'
If new school codes have been added since 2000, those school codes will not be available.

Resolution: In the page Print Pell Grant ESOA (Home > Administer Financial Aid > Process Pell Payment > Reports
> Print Pell Grant ESOA ), the lookup table for the field Pell ID Reporting was changed to display the correct list of
values according to the Aid Year selected.


745290000 FA 8 SP1: FA: Direct Loan Out abends if running multiple Aid Years on the same run control
Process: FAPLDOA5/FAPLDOA4
If a user is attempting to run Direct Loan Out for more than on aid year, one row for 2004 and one row for 2005. The
process abends with the following error:

FAPLDOA4 : End program execution at 08. 29. 01. 340000 on 2004-07-22
COMMIT LEVEL = 00500
S-XFER Select EDI information from PS_LN_XFER_ID_TBL
AID-YEAR: 2004
LOAN-PROGRAM: D
I-ECTRANSID: DEPF05IN

FAPLDOA5 - SQL ERROR IN SECTION: S-XFER (FETCH)
FAPLDOA5 - TERMINATING PROGRAM EXECUTION

Application Program Failed
In Pgm Section : S-XFER (FETCH)
With Return Code: 00001
Error Message : End of fetch

PTPSQLRT - Error Encountered
No longer have connection to DB due to an error from previous
action: SQL FETCH . Bypassing current action: ROLLBACK.
Terminating Program.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 12 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




The process seems to be attempting to find the DEPF05IN EC Transaction ID on the PS_LN_XFER_ID_TBL table
but for the Aid Year 2004. This will never return a row because DEPF05IN is a 2005 EC Transaction ID. If only one
aid is run at a time, the process completes without error.

Resolution: Fixed the code that populates the DLOUT-TABLE which is passed to each outbound program. The
program was not re-initializing the table properly and as a result run controls records for 2004 were being processed
by 2005 programs.


747762000 FA 8 SP1: FA: Invalid Verification status being sent by Pell Out
Process: FAPPOOR0 Pell Out is incorrectly sending the VERIF-STATUS-CODE of B on outbound files. This is an
invalid value and will be rejected by the Pell Processor.

Resolution: Modified FAPPOR0.cbl to send out spaces when VERIF-STATUS-CODE = "B".


1134835000 FA 8 SP1: Incorrect loan error message descr being displayed for Direct Loans.
Page: LN_DL_ORIG_SEC
Record: LN_ORIGMSG_VW and LN_DISBMSG_VW
On the Loan Action Detail Message, the description that is displayed for Direct Loans is incorrect. The view
(LN_ORIGMSG_VW and LN_DISBMSG_VW) does not consider Loan Program and the descriptions for FFELP loans
are returned

Resolution: Updated the views LN_ORIGMSG_VW, LN_DISB_MSG_VW, and LN_PNOTEMSG_VW to include
LOAN_PROGRAM so the correct Loan Action Message will be retrieved.


1140655000 FA 8 SP1: COD rejects records (Pell and DL) if sent with different names.
According to COD, once COD accepts a record with a certain transaction number, then any future records coming in
with that same transaction number, are then matched up against the student's name in COD that was built with that
Transaction. In Pell Processing the name is selected from the ISIR Data, for Direct Loans the name comes from
Campus Community Bio/Demo Data. If schools do not update Bio/Demo data based on the ISIR, these can be
different. Although the EDE Technical Reference says only the first two letters are matched (edit 012) this doesn't
seem to be the case. Pell and DL Information needs to come from the same source.

Resolution: Modified App Engine People code for FA_COD_OUT. For DL awards select names from ISIR tables
instead of LOAN tables.


1140703000 FA 8 SP1: faldpnt2.sqr doesn't join on career between communication and loan_orignatn tbls. Process:
FALDPNT2
Users are unable to print appropriate loan request amount on Inst. prom notes when multiple careers have rows for
same loan type cd in loan origination. The program doesn't join career value from communication var data to career
in loan orig tables.
Example: Student had loan as UGRD career, was originated, prom note printed and then the loan was canceled. The
student then switches to the UENG career and the same item type is awarded and originated. The Communication
var data reflects career change, but note extracts with the "wrong" career row in loan orig tables. Adding a check of
the ACAD_CAREER to the Get-Loan-Detail section of faldpnt2 allows the process to retrieve the correct amount.

Resolution: Added career to joint between communication and loan_orignatn tbls in faldpnt2.sqr .




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 13 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




1143396000 FA 8 SP1: fapldpn2.dms doesn't correctly join career, results in multiple comm assign.
Process: FAPLDPN2.dms does not join PS_LOAN_ORIGNATN and PS_LOAN_ORIG_DTL based on career. This
results in multiple comm keys being assigned.

Resolution: Modified FAPLDPN2.dms to join PS_LOAN_ORIGNATN and PS_LOAN_ORIG_DTL based on career.


1143619000 FA 8 SP1: The Pell Reconciliation Component only displays the first record in the batch.
Page: PELL_RECON_00
The PELL_RECON_00 page contains no scroll area so users can only see the first row of data in the batch.

Resolution: A scroll area has been inserted into the Pell Reconciliation page (Home > Administer Financial Aid >
Process Pell Payment > Inquire > Pell Reconciliation) to see all the rows of data in a batch


1145055000 FA 8 SP1: Problem with FAPBUDGD_S_ISIRCTL.
There is a problem with FAPBUDGD_S_ISIRCTL. If a student has multiple institutions on PS_ISIR_CONTROL, the
select can fail to find a row. When this occurs the budget formula process might select the wrong budget item.
FAPBUDGD.cbl checks for ISIR data with FAPBUDGD_S_ISIRCTL. If it can't find a row on PS_ISIR_CONTROL,
the program skips checking PS_ISIR_STUDENT for more info and puts a blank value for Housing Type when it
creates a PS_STDNT_BDGT_ASGN row for the budget item. This can cause the wrong budget item to be assigned.

Resolution: Added Institution to the sub select of FAPBUDGD_S_ISIRCTL on FAPBUDGD.DMS.


1174220000 FA 8 SP1: COD .xml file with reject status loading false messages.
Loaded an origination acknowledgement file that has no information in it other than a reject code
(<DocumentStatusCode>R</DocumentStatusCode>). When the COD programs ran it tried to figure out what the Orig
Status was. Since no response information was in the rejected file, the function that calculates the Orig Status had
nothing to go on and returned nothing, which tools translated to a zero. That zero then got loaded into the system and
now the Direct Loan Orig Action page shows a status of 'Processed, pending P Note'. Because of this false status,
client is unable to disburse funds to the student.

Resolution: Modified App Engine People Code FA_COD_IN. When loading a Document with Reject status, set
COD_PS_PROC_STAT = "I" (Processed) so subsequent processes will not pick it up and load false messages.


1178464000 FA 8 SP1: COD receipt files overwrites response files.
COMRECOP files contain lots of types of files. We have an issue with a combination of two types. RC files are
receipt files and RS files are the full response file to the initial data we sent. In some cases, we get RC files from COD
after RS files. The problem comes when the RC file comes in after an RS file. The problem with the loading of receipt
files is that the records received in the full response file aren't loading in Direct Loan In or Pell In when the Document
Type is RC - and the document type isn't updating to RS when the full response file and the receipt are loaded in the
same file. Client automated the send, receive, and load process to run during our nightly batch jobs. Since they don't
have the file list option with COD Inbound, they're concatenating the COD files pulled in during the night into one file.
These load ok unless they get the receipt file and the response on the same night.

Resolution: Modified App Engine People Code FA_COD_IN.Step10. When Inbound Receipt file, do not change
Processing status. Update Receipt Date only.




                                      Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 14 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




1180274000 FA 8 SP1: FA Term page header extended when a service indicator appears on page.
The 3Cs buttons are pushed way over to the right whenever a service indicator appears for a student on the FA Term
page.

Resolution: Corrected page STDNT_FA_TERM by moving the PERS_SRCH_CS_SBP over to the left one pixel
and up one pixel.


1190073000 FA 8 SP1: Date-times used for award activity transactions are not standardized.
The date and time stamps used when writing award activity transactions are not consistent across programs. The
packaging engine uses database time, and the authorization/disbursement programs use system time where the
program is running (app server or process scheduler time). This has causes some transactions to be out of
sequence due to clock differences. The solution would be to modify the authorization and disbursement programs to
get the date/time from the database, as done in the packaging program.

Resolution: Date and Time will be retrieved from the database.


1200942000 FA 8 SP1: NSLDS File layout changes for the December 2004.
The NSLDS load process needs to support the changes made to the NSLDS file layout that was issued in December
2004.

Resolution: Modified files FAPTALRT.CBL and FAPTALRT.DMS, along with File Layout TRALRTOP03, to reflect
the new NSLDS record layout.


1214656000 FA 8 SP1: Awarding page shows incorrect warning message when adjusting fully disbursed loan.
On the Award Entry page, when manually adjusting a fully-disbursed loan, after the Offered amount is changed a
warning message is displayed alerting the user that the Accepted amount is below the Disbursed amount and that
Professional Judgment was used to allow this.

Resolution: This is actually working as designed. The intent was that if user was manually reducing an award below
the disbursed amount, that is intentional on the part of the user and we should allow it. The warning message alerts
the user of the consequences and advises the user of downstream processing necessary to complete the reduction.
Message Set 14420, Nbr=78 has been modified as follows: "Warning -- This award has been reduced below the
Disbursed amount. Authorization and Disbursement processes should be invoked to make sure correct amounts are
posted to the student's account."


1215712000 FA 8 SP1: INAS 2005-2006 Federal Methodology - Final Release.
INAS 2005-2006 Federal Methodology - Final Release.

Resolution: INAS 2005-2006 Federal Methodology - Final Release was received from College Board on 1/28/2005.


1221627000 FA 8 SP1: Pell budget amounts doubling for 1 term.
If term budgets are not all built or re-built at the same time, the Pell COA becomes over stated. For example, a
student had both fall and spring budgets built. The Academic Year Pell COAs are equally divided between the two
terms. Ok, fine. Then the Fall budget is rebuilt independently to, say, reflect census date enrollment. Each fall budget
item is assigned the AY Pell COA amount, which is added to the COA amounts previously assigned to the spring
budget items. So, now the Pell COA = Pell COA for the AY + Pell COA for one term. Using the Pell Adjustment button
on the Pell Adjustment Page would "fix" the Pell COAs for all existing term budgets in the year.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 15 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




Resolution: Removed logic from FACPELLP.cbl which derived weeks of instruction from base weeks and enrolled
term count if the weeks of instruction were equal to zero. Added logic to zero out Pell Item Amount and Less than
half time Pell Amounts if FA Load does not exist.


1234261000 FA 8 SP1: FAOSAPLD.sqr inserting 'Null" value into PS_STDNT_AWD_PER.
When running FAOSAPLD.sqr, the process abends with the following (SQR 5528) ORACLE ORA-01400: cannot
insert NULL into ("SYADM"."PS_STDNT_AWD_PER"."SFA_PELLYR_COA_LHT") There are two inserts into
PSSTDNT_AWD_PER. The second insert does not account for the SFA_PELLYR_COA_LHT field.

Resolution: Added field SFA_PELLYR_COA_LHT to insert statement of PS_STDNT_AWD_PER.


1234699000 FA 8 SP1: Direct Loan COD Annual Updates. Annual updates for Direct Loan COD processing.

Resolution: Added new objects/programs and updated existing code to enable 2005-06 Direct Loans processing.


1236702000 FA 8 SP1: FA: ISIR Load is hard coding COUNTRY_CODE on PERSONAL_PHONE as USA Process:
FAP00SLD
Record: PS_PERSONAL_PHONE
Field: COUNTRY_CODE
ISIR Load (FAP00SLD) is hard coding the COUNTRY_CODE as 'USA' when inserting into
PS_PERSONAL_PHONE....
       MOVE 'USA'
        TO COUNTRY-CODE OF I-PHONE
The Country Code for a phone number should be numeric.
When VENDOR_SYNC is run it causes the message to crash because the COUNTRY_CODE for a phone number
should be numeric.

Resolution: Modified program FAP00SLD.CBL to use the value '001' instead of 'USA'. The script
upd151734_6.dms is provided to clean up the existing data.


1241265000 FA 8 SP1: Or’ logical operand used in Student Group returns incorrect budget items.
If user creates the following budget formula:
ACAD_CAREER = 'UGRD' AND STDNT_GROUP = RESL OR STDNT_GROUP = RESS
the FAPBUDPF.CBL program generates the following SQL:
SELECT A.EMPLID FROM PS_STDNT_BDGT_ASGN A, PS_STDNT_GRPS B WHERE (((A.ACAD_CAREER =
'UGRD' AND (B.STDNT_GROUP = 'RESL' ) OR (B.STDNT_GROUP = 'RESS' ))))
This SQL will pick up all students with STDNT_GROUP 'RESL' or 'RESS' regardless of Career. Customer instead
wants only UGRD Career AND students in 'RESL' OR 'RESS'

Resolution: Modified dynamic sql section (I1800-PROCESS-STUDENT-WHERE                 SECTION) of FAPBUDPF.cbl to
correct the problem.


1242519000 FA 8 SP1: FA: Unable to load ISIRs after using ISIR/NSLDS Delete.
Page: ISIR_DELETE
Record: DERIVED_ISIRDEL
Field: ISIR_DEL_PB
If all ISIRs are selected on the ISIR/NSLDS Delete page, when the 'Delete Selected ISIR(s)' is clicked, a row is



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 16 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



inserted into PS_ISIR_CONTROL with an EFFDT of today and an ISIR_TXN_NBR=0. When a user than tries to go
and load an ISIR, the ISIR is suspended with the reason '7 - ISIR Tran Num Out of Seq'

Resolution: Modified the RowInit Peoplecode for ISIR_CONTROL.CORR_EMAIL_ADDR and
ISIR_CONTROL.CORR_PHONE so that it does not execute for the ISIR Delete Component.


1244162000 FA 8 SP1: Packaging process is retaining previously disbursed awards.
As of Bundle #7, the packaging process is retaining previously disbursed awards even though the award is unlocked
and not protected by disbursement protection. For example:
1. Create a packaging plan, which awards two items. First is Fall Only item. Second is Spring Only.
2. Retrieve the plan and authorize and disburse the Fall Only item (this item is not locked nor disbursement
protected).
3. Run the same plan again against the student.

Resolution: Changed FAPPKCTL.cbl, removing all references to WS-HAVE-DISB-LOCK and AT005-CHK-FOR-
DISB-LOCK


1256082000 FA 8 SP1: INAS 2005-2006 Technical Upgrade #3 - Posting #2
INAS 2005-2006 Technical Upgrade #3 - Posting #2.

Resolution: INAS 2005-2006 Technical Upgrade #3 - Posting #2 was received from College Board on 3/28/2005.


1266622000 FA 8 SP1: Problem with student's Worksheet B field in INAS Simulation
In INAS Simulation 05/06 (Home > Administer Financial Aid > Manage Need Analysis > Use2 > INAS Simulation
05/06) if the value for student's Worksheet B is changed in INAS Simulation, and then the EFC is recalculated using
INAS, the Worksheet B value is blanked out. It remains stored in the table and is used in the INAS Calc, but the value
is invisible on the page.

It does insert the updated amount (that was blanked out) into ISIR Correction if the user clicks 'Use Simulated Data'.

Resolution: Originally made aware of issue via the PS Financial Aid listserv in early March 2005. Modified the
RowInit PeopleCode for INAS_SIM_STU.TOTAL_FROM_WS3, adding a reference to 05/06 Simulation Component
INAS_SIMULATION_06.


711171000 SF 8 SP1: SF8: Receipt Posts To Student With Wrong Amount When Credit Card Tx Corrected
Navigation: Home, Manage Student Financials, Run Cashiering, Use, Student Payments
When entering a cashiering receipt, and the credit card declines you are asked to re-create a receipt. When the
amounts of the transaction are adjusted to accommodate the limit on the credit card and the receipt is re-created the
original amount is posted to the student not the changed amount. Changed amount posts on the credit card.

Resolution: Changed Peoplecode in Cashiering to defer the saving of quick post rows up to the point where the
payment is authorized.


721459000 SF 8 SP1: Posting an Out of Balance Transaction on Student Payment Page
Navigation: Home, Manage Student Financials, Run Cashiering; Use, Student Payments
When posting on the Student Payment page we have discovered that it is possible to post transactions that are out of
balance. This causes the closing amount to be incorrect when the drawer is being closed for the day, as the
orignl_item_amt field will be 0.00.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 17 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




Resolution: Made a change to CSH_OFF_RCPT_T.ORIGNL_ITEM_AMT FieldChange to perform default the
AMOUNT_SF when the Original item amount is zero. In addition, changed the message number for
CSH_OFF_RCPT_L.AMOUNT_SF SaveEdit from 14810,118 Positive Amount is expected for this Tender to
14810,13089 Positive Amount is expected for this Target.


746808000 SF 8 SP1: SF8: Duplicate Merchant ReferenceNumbers/PendingPost Occur When Posting Pgm Fails
Navigation: Home, SA Self Service, Learner Services; Finances, Make A Payment
If the SFPQCCWB (posting program) Cobol process aborts while processing a self-service payment, the user
remains on the submit page and can resubmit the payment. When this happens they can end up with multiple
authorizations and/or settlements When the user gets an error message after hitting the submit button, they will
remain on the submit page and can hit the submit button again. If they hit the submit button again they will get the
multiple authorizations on the same Merchant Reference Number.

Resolution: On fieldedit of sf_payment_wrk.sf_submit_pb, added a call to function PayStatusEdit, which will cause
an error message saying that the payment has already been processed.


1231473000 SF 8 SP1: Refund Reversal By Date Times Out With Large Volume Of Refunds.
Navigation: Home, Manage Student Financials, Refund Customers; Use, Refund Reversal By Date

Resolution: An incorrect related display was corrected on the Refund Reversal By Date and Corp Refund Reversal
By Date pages.


1243649000 SR 8 SP1: Can no longer transfer courses into multiple careers after Bundle #7.
Client recently implemented bundle 7. The problem did not exist previously. System does not allow enrollment to be
processed as internal transfer credit into more than one career.

Resolution: The SQL in SRPCCART.dms that picks up the input was corrected to include classes that have been
used in other models.


508159000 SR 8 SP1: SR8. 0: Increase Maximum field length for Transcript Component Data
Transcript - Degree Plan/Honors Description
TRSCRN_DESCR is a 100-character field. Degree Honors DESCR is a 30-character field while Degree Honors
DESCRFORMAL is a 50-character field. At the Plan level, there is a Degree Prefix, the Plan Transcript description
and a Plan Suffix. The transcript COBOL uses the formal description; therefore the maximum field length for
Transcript Component Data should be 50 + 100 + 50 (Degree Honors Prefix formal description + Transcript
Description + Degree Honors Suffix formal description) or 200 characters.

Resolution: Added logic to SRPCTEXT.CBL to combine and word wrap the degree and degree honors descriptions.


699190000 SR 8 SP1: Under certain circumstances, cannot produce Enroll Ver Report
Receive an error: Cannot produce an enrollment verification request because To Term is less than From Term. This
has been observed to occur under certain circumstances when a student requests enrollment verification by using the
self-service page. from ps_ENRL_VER_REQST. Once this happens in Self Service it is easy to go and redo and is
fine. But Admin can not get a new enrollment verification report without receiving error: "To Term must be greater
than or equal to From Term - even when terms are the same.".
If a student requests enrollment verification in the following sequence: Enter Term; Enter Address (without choosing
"send to my address"); Enter different Term; Submit



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 18 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



It has been shown that ENRL_VER_REQST.FROM_TERM is becomes greater than
ENRL_VER_REQST.TO_TERM.

Resolution: Changed Peoplecode to set TO_TERM to FROM_TERM when using the self-service component. This
way there is always a value.


709672000 SR 8 SP1: SR 8SP1: Unit incongruity prevents students from rolling off waitlist- SRPCWAIT
When using unit override OR unit conversion, a student waitlisted is prevented from rolling off the waitlist through
SRPCWAIT with message: Invalid Input Value for Units Taken
Customer is seeing an error message (set 14640, Message 103). Students on the waitlist with this error do not roll
when waitlist runs. Customer is able to enroll these students via the enrollment engine so there are no other conflicts.
In all cases these are cross career enrollments (for example: grad student taking undergrad course) and the error
only occurs when the student is trying to move from the waitlist to enrolled. No error when the student is initially
enrolled but put on the waitlist.

Resolution: Modified srpcwlpr.dms so that the override for class unit is always selected when generating w/l
transaction off student enroll table.


721944000 SR 8 SP1: SR 8 SP1: Minimum unit limit not enforced in enrollment request and self service enrollment
Navigation: Manage Student Records, Manage Academic Records, Use, Enrollment Request
Different results are received when dropping classes individually or when multiple drops are included in the same
enrollment request in situations where the drops would put the student below the minimum units limit for the term
defined on the academic program table. There is also an inconsistency on the minimum unit enforcement depending
on whether or not the W grade is set up to be excluded or included in progress units.

Resolution: Modified SRCCEPRD.cbl, SRCCETRM.cbl, SRPCETRM.cbl, and SRPCEPRD.cbl to exclude dropped
classes even if the grade is present and the units_attempted flag is selected when calculating minimum enrollment
units.


735223000 SR 8 SP1: SR 8SP1: On swap transaction, entering change to value first grays grading basis field for
OPT grading basis
If a student creates a swap transaction and enters the class number for the "change to" field FIRST, before entering
the class number that is the "from" class, the grading basis populates and is grayed out. When the grading basis is
OPT, this means the transaction posts with OPT as the grading basis, which is not a valid grading basis. When
grade rosters are created, the student can't be graded.

Resolution: Added a hidden field in page ENRL_REQUEST for the Swap To Class' Course Grade Scheme, and
added logic in FUNCLIB_CS.ENRL_REQ_ACTION.FieldFormula to use this grade scheme in Swap transactions.


736326000 SR 8 SP1: SR 8 SP1: Enrollment engine allows drops of classes with coreqs during drop with penalty
period
Navigation: Manage Student Records, Manage Academic Records, Use, Enrollment Request
Enrollment engine allows a drop of a class that is a co requisite of another class during the drop with penalty period
with no error or warning. During the drop retain period, an error is received that the class cannot be dropped
because it is a co requisite class. Both time periods should prevent the drop.

Resolution: Modified SRPCEPRD.cbl to pass original settings of units_attempted, earn_credit, include_in_gpa
(before the drop grade is applied) when checking for requisites. This will allow checking the requisites properly even
if a grade penalty is being applied. Modified SRPCETRM.cbl to save the original settings of these 3 fields.



                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                          Page 19 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




738282000 SR 8 SP1: SR 8 SP1: Reserve capacities not enforced when reserve caps are lowered
Navigation: Manage Student Records, Establish Courses, Use, Schedule of Classes
When a class has multiple reserve capacities set up and one or more of the reserve caps are lowered after initial
enrollment into the class, the remaining reserve capacity limit is not being enforced.

Resolution: Modified SRPCEPRD.cbl & srpceprd.dms so that it will waitlist student even if class is open but
someone already is waitlisted provided that the auto enrl from waitlist is set to N. New message (14640, 214) to
inform of error if waitlist ok is not selected. Corrected logic in counting the needed reserve seat. Added logic to set
waitlist daemon when the reserve cap is changed and it will create open gen pop seat and someone is in waitlist.


1112428000 SR 8 SP1: SR 8SP1: Graduates only NSLC report incorrectly includes students with degrees from prior
terms
The NSLC extract run control has a report type of graduates only. When using this report type, students are included
who are active in the term that corresponds to the academic stats period term but who have a COMP row for a prior
term. It appears the logic to select on the effdt of the COMP row looks for any date prior to the as-of date of the stats
period definition, rather than any date within the term begin and end dates.

Resolution: Modified the Consolidated Statistics COBOL programs, copybooks, and stored statements to correctly
NOT pull in an academic program that was completed in a prior term.


1112636000 SR 8 SP1: SR 8SP1: Program status (PROG_STATUS) reverts to previous row value on ACAD_PROG
record.
When inserting multiple EFFSEQ rows with the same EFFDT, the PROG_STATUS field reverts to the prior row
value. Student was discontinued, and then reinstated. When inserting the third sequence row on the same effective
date and saving, the status on that row and the previous row is updated to discontinued. It should remain Active in
Program.

Resolution: Added code in ACAD_PROG.EFFDT.FieldChange so that when the EFFDT value is changed, the next
EFFSEQ for the row based on the EFFDT is defaulted by the system. Page STDNT_PROG was also modified to
turn off 'Deferred Processing' for field EFFDT to activate the defaulting code for field EFFSEQ.


1117644000 SR 8 SP1: SR8SP1: Last Date for Wait List not behaving correctly in Self-Service
The date value in this field works as described in the administrative transaction, Enrollment Request and Quick
Enroll. However, in Self Service, students are not able to add waitlist on the date entered in this field - the Wait List
Okay check box does not appear if student is trying to waitlist on the LAST Date to waitlist. The SS workaround was
to enter the "day after" the final date, instead of the final date. Then, on the actual day after the final date, we will
have to set the field value back to the actual final date in order to keep administrative users from adding waitlist
requests. PeopleBooks describes this date as follows: Last Date for Wait List - Enter the final date on which a
student can be placed on a wait list for this session. The enrollment engine assigns a student to the wait list for a
class if the class is full and the user selects the Wait List Okay check box for the enrollment request.

Resolution: Modified FUNCTLIB_SR.ENRL_REQ_ACTION.FieldFormulat to check date using >= instead of only >.


1127093000 SR 8 SP1: Course Catalog Detail link can display incorrect courses.
SA Self Service, Learner Services, Catalog, View Class Schedule
The View Class Schedule results page has a link to see Course Catalog Detail. This leads to a page course search
result page, which usually displays correct information. However, the search is based on subject and catalog number



                                      Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                        Page 20 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



rather than course ID. So if two course IDs share the same subject and catalog number, an extra (wrong) course
description displays.

Resolution: Modified Peoplecode to search for course catalog based on course ID.


1140247000 SR 8 SP1: Consolidated stats picking up program completed in prior terms.
When a student has multiple programs, srpcconp will pick up a program that was completed prior to the reporting
term and use it for PS_STDNT_CONS_STAT.ACAD_PROG_MAIN. The current, active program is not used. This
occurs when the academic statistics type is set to include completed programs. It should only include programs
completed in the reporting term, however.

Resolution: Modified the Consolidated Statistics COBOL programs, copybooks, and stored statements to correctly
NOT pull in an academic program that was completed in a prior term.


1143051000 SR 8 SP1: Grade lapse process uses wrong date on transcript.
The date that prints on student's transcript is the lapse process date and not the lapse days value that PeopleBook
says. The PeopleBook entry indicates that the process date is NOT used; however, that is the date that is used. The
process may be run long after the date the grade actually lapsed, so the transcript is inaccurate.

Resolution: Modified SRPCEPST.cbl and srpcepst.dms so that the program uses the lapse_deadline date from
PS_STDNT_INCOMPLTE when generating transcript lapse notes.


1144164000 SR 8 SP1: When student Views My Assignments, dropped classes are displayed.
Navigation: SA Self Service, Learner Services, Academics, View My Assignments or, SA Self Service, Gradebook,
Assignment, View My Assignments
When a student has a dropped class it still shows up in Learner Services under the 'View Class Assignments'.
Problem for dropped retained classes or dropped with penalty grade.

Resolution: Added checking enrollment status to views that determine which classes are available for student
viewing. (A.STDNT_ENRL_STATUS = 'E' AND A.ENRL_STATUS_REASON IN ('ENRL','EWAT')


1149180000 SR 8 SP1: Problems with Active Student list in Gradebook - erratic results.
The STDNT_GRADE_HDR gradebook record is populated by Peoplecode. Depending on the
STDNT_ENRL_STATUS and ENRL_STATUS_REASON on the STDNT_ENRL records, the student will or will not
display on the Gradebook page. As delivered, only E-ENRL and E-WDRW students are displayed when the 'Show
Active Students Only' checkbox is checked. However, customer found that when they unchecked the box, the E-
DROP and D-DROP students would not all display. For example, if they had three dropped students in the class,
usually only one of them would display. Upon rechecking the box and uncheck it again a different dropped student
would display. They could not get all three to display at the same time. Gradebook (STDNT_GRADE_HDR) contains
student emplids that have since been drop/purged from student records. Therefore STDNT_GRADE_HDR contains
more empldis than GRADE_ROSTER because the enrollments are gone for those purged students. When the
instructor pushes the UPDATE button (via self service) for the class, only partial grades are updated. There is a
while loop in Peoplecode and once a mismatch is found, the program breaks. The remaining students (alphabetical
list) will not get their grades updated and therefore not posted. A sample message reads The Grade Roster has 32
students, and 28 have been updated. (14600,654).

Resolution: Simplified the Peoplecode that hides/unhides student rows, now using the function ShowAllRows().




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                         Page 21 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



1169887000 SR 8 SP1: Student Incorrectly Waitlisted if Reserve Cap Present.
Customer is seeing students who do not meet the criteria of a reserve cap being placed on the waitlist even though
there is space in the section for non-capped students. They have course with a lecture /discussion combination. The
discussion is the enrollment section, has 20 seats and has a reserve cap of 5 for majors. If the "OK to Waitlist" flag is
checked upon submitting the enrollment request, a non-major student will be placed on the waitlist even though there
are 15 seats (20 - 5 reserved) available. If the request is submitted without the "OK to Waitlist" flag on the student is
enrolled into the empty seat. The students do not seem to roll off the waitlist.

Resolution: Add logic to properly determine if class is closed when transaction is about to post on classes with
reserve cap.



1170315000 SR 8 SP1: Remote call error in enrollment request when waitlisted and enrolling into combined section.
Navigation: Manage Student Records, Manage Academic Records, Use, Enrollment Request
When a student tries to add a different section of the same class for which he or she is already wait listed and the
class is in a combination with another class, a remote call error is returned.

Resolution: Missing Cobol statements when executing SRPCEPST_S_COMBS. Corrected logic in SRPCEPST.cbl
program.


1173856000 SR 8 SP1: Academic Standing sets values for no_gpa units even when Exclude no GPA Attempted
units checkbox is on.
Customer has set up an academic standing rule to evaluate students based on cumulative and current term GPA.
The Exclude No GPA Attempted Units checkbox is on for every sequence row in the rule. However, students who
have only credit/no credit grades (earned credit but not included in the GPA) and a blank GPA are being evaluated
against the rule as having a ZERO grade point average. The Exclude checkbox should exclude those courses from
consideration.

Resolution: Modified program SRPCEASC.cbl to properly handle cumulative and current term GPA rules when the
Exclude No GPA checkbox is turned on.


1181750000 SR 8 SP1: Override Projected level flag causes Peoplecode error on the Enrollment page.
When the Override Projected Level checkbox is checked in Term Activation, it prevents users from being able to add
a class, add a grade or change a grade on the Enrollment page due to a Peoplecode error. Invalid decimal value -
FUNCLIB_CS.TOT_CUMULATIVE Field Formula update totals.

Resolution: The code in FUNCLIB_CS.TOT_CUMULATIVE.FieldFormula that assigns the value of Projected
Academic Level to Projected Level Total was causing this error, because the source field is defined as a character
field and the target is a numeric field. The code was corrected to assign the correct values to both Projected
Academic Level and Projected Level Total.


1196035000 SR 8 SP1: Peoplecode error on student incomplete when course is outside student's career.
Navigation: Manage Student Records, Manage Academic Records, Use, Student Incomplete
The problem will occur if a student receives an incomplete grade in a course taken outside the student's career. If the
student's career uses a different term unit type than the course's career, a Peoplecode error is received when trying
to access the Student Incomplete page. Error is: "ScrollFlush: Record UNT_CONVR_TBL not found in scroll level 0
at FUNCLIB_CS.UNT_MULTIPLIER Field Formula GetUnitMultiplier"




                                     Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                          Page 22 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



Resolution: An invisible scroll area that contains UNIT_CONVR_TBL was added to page STDNT_INCOMPLETE to
prevent the error.


1200614000 SR 8 SP1: Waitlisted classes display in self-service View My Grades.
In the SA Self Service View My Grades page, the classes that students are still wait listed in appear in the list.
Problem does not occur in the Manage Academic Records > Inquire page.

Resolution: Altered view STDNT_GRAD_SSVW SQL to include "AND A.STDNT_ENRL_STATUS <> 'W' "




1205668000 SR 8 SP1: Attendance Roster Generator batch process options not working correctly.
The Attendance Roster Generator (batch process) doesn't pick up newly enrolled students when using the
Attendance/Active Only option. The result is that newly enrolled students don't appear on the Class Attendance
rosters. The problem seems to be linked to the Attendance Roster Generator not working properly. When using the
Generate button in the Class Attendance page, and selecting the Attendance/Active Only option, the newly enrolled
students ARE picked up. Enroll a student in a class and generate a Class Roster using the Attendance Roster
Generator (process) with the Create Attendance option selected in the Roster option. You then enroll another
student, and re-generate the Class Attendance using the Attendance Roster Generator (process) with the
Attendance/Active Only option selected to avoid losing previous data entered in the Class Attendance page. As per
PS documentation, you'd expect the new student to be picked up. It isn't. It seems that the Attendance Roster
Generator processes SRATTENJ, SRATTEND and/or SRATTENP aren't working properly.

Resolution: Added debugging statements to SRATTEND.SQR, streamlined the PS Job for the Roster Generator,
fixed some Peoplecode and field default properties for the 'synch with class meeting' checkbox.


1207723000 SR 8 SP1: Peoplecode error when hitting the Cancel Class push button.
Error received is: Fetch Value: Row 0 not found in scroll level 3 error after hitting the Cancel Class push button
Problem occurs because the field CLASS_MTG_NBR is being updated differently in PS_CAMPUS_MTG than it is in
the other tables. In PS_CAMPUS_MTG, the second section of the class is inserted as CLASS_MTG_NBR 0, but it is
being inserted as CLASS_MTG_NBR 2 in the other tables.

Resolution: Class meeting pattern flags were set to YES even if all requirements fpr a campus meeting row were
not met. Modified Peoplecode so the campus meeting flag is only set when a campus meeting row exists for it.


1208278000 SR 8 SP1: Transfer Credit unit conversion when Rule term type is different than model career type.
Additional testing after Bundle 7 has found that Transfer Credit unit conversion when Rule term type is different than
model career type does not work.

Resolution: SRCCARTP.cbl was modified to handle unit conversion correctly, and to award the correct equivalent
units for 'Specify Max' rules when there is more than one input.


1219019000 SR 8 SP1: Fetch button on transfer credit model does not fetch courses where official grade field is
blank.
Clicking the Fetch button on Course Credits model page does not to fetch courses that do not have an entry in the
Official Grade field on External Courses. In the past, it did. This is a problem because the PeopleSoft EDI process
does not populate the CRSE_GRADE_OFF field.



                                      Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                           Page 23 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:




Resolution: Modified adtrnacd.sqc to mimic the behavior of the education component.


1219026000 SR 8 SP1: Transfer Priority logic no longer working correctly after SA Bundle #7.
The transfer priority logic seems to have been reversed. Client created a transfer credit rule for a 2:1 equivalency as
transfer priority 1, and each of the same external courses articulating to a single internal course as transfer priority 2.
Before SA Bundle 7, a student with both courses got the 2:1 equivalency because it was transfer priority 1. Now they
get two 1:1 equivalencies (transfer priority 2).

Resolution: The articulation program logic was modified to apply transfer credit rules in ascending order.




1223212000 SR 8 SP1: Academic Levels not greying out appropriately on term activation after SA Bundle #7.
Incident 700211000 fix in SA Bundle #7 now allows the user to access the Override checkboxes on Term Activation
when the Level rule determination is set to Default, but now the user no longer needs to check the checkboxes. All
the level fields display on the page (they should be hidden until the checkbox is checked) and are editable.

Resolution: All 3 level fields should be hidden unless one of the override checkboxes is selected for the following
Level Determination values: Default, Unit, and Term. For Manual, the fields should always be editable regardless of
the checkbox value. Modified Peoplecode to resolve these issues.


1225509000 SR 8 SP1: Repeat checking failing with severe error when term not specified.
Navigation: Manage Academic Records, Process, Repeat Checking
After applying SA Bundle #7, repeat checking now requires a term to be specified on the run control. Without a term
a severe error is encountered in the process. Users need to be able to process repeat checking on students' entire
records and not just for one term.

Resolution: Corrected SRPCERTD.cbl program to handle blank term.


1226545000 SR 8 SP1: Problems with WaitList and Drop if Enrolled.
Students with Drop If Enroll classes listed are having their classes dropped EVEN IF they are not actually enrolled in
the class as a result of the WaitList Processor (meaning they are still on the WaitList but not still enrolled in original
class).

Resolution: Modified SRPCEPRD.cbl program to handle backing out of transaction when an error is detected on
waitlist transaction with drop if enroll option.


1228243000 SR 8 SP1: Remote call error returned on Fetch when save excess units checkbox is on.
Following SA Bundle #7, when the transfer subject area - subject area elements page setup for a particular course
has the Save Excess Units to a Course checkbox turned ON, a remote call error is returned when the user executes
a fetch against that articulation rule.

Resolution: The articulation program logic was fixed so it does not fail with this setup.


1230194000 SR 8 SP1: Wildcard character configuration on subject area elements changed in SA Bundle #7.
Navigation: Manage Student Records, Process Transfer Credit, Setup, Transfer Subject Area



                                      Peoplesoft, Inc. Proprietary and Confidential
Issue Description Documentation                                                                          Page 24 of 24



Resolution ID: 151734
SA 8 SP1 Bundle #8
The following Report IDs have been bundled together in the fix located in the Resolution Section of this incident.
Listed below are the issue descriptions that appeared in the original incidents:



The issue reported in incident 710372000 has not been resolved, Additionally, SA Bundle #7 delivered a change to
the wildcard functionality on external courses. The articulation rule is defaulting in the maximum unit value when the
Specify Maximum Units value is set and a wildcarded external course exists on the rule. When a specific course
number exists on the rule, the unit value for the external course is defaulted in the fetch. An articulation equivalency is
defined in Process Transfer Credit, Setup, Subject Area Elements with a wildcard checkbox indicator turned on.
Previously, when a course was represented as a numeric and a # (i.e., 3#), the articulation would apply to courses
with any length of course number beginning with the numerid (i.e., 320, 35, 3). Following SA Bundle #7, the same
value now only articulates for two-digit course numbers. The wildcard of 3# will articulate only for courses numbered
30 through 39. For courses with three digits, customers would need to correct the existing entry to 30# and create
nine additional rows of articulation equivalency to have the equivalency apply to courses numbered 300-399.

Resolution: SRCCARTP.cbl was corrected so that wildcard rules are implemented the same way course-specific
rules are: when it is Specify Max Units, the equivalent course gets units from the incoming units up to the maximum
value specified in the rule.


1237634000 SR 8 SP1: Enrollment Engine not respecting Reserve Cap if Okay to Waitlist is Yes.
When a large volume of refunds has been processed for a particular business date, the request times out after
entering the business unit and refund date on the search dialog box.

Resolution: Modified SRPCEPRD.cbl to properly check if student is going to be waitlisted when the class is set with
reserve cap & combined section.


1255762000 SR 8 SP1: Enrollment Component: Row Separators Lost in View All Mode.
When view all rows on the Enrollment component, the row separator lines occur in the wrong place, such that the
Class Nbr for row 2 appears to be part of Row 1. The problem is manifested on the Enrollment 2, 3 and 4 pages.

Resolution: Pages STDNT_ENRL1, STDNT_ENRL2, STDNT_ENRL3, STDNT_ENRL4, STDNT_ENRL_LAST and
CAN_RPT_STDNT_CRSE were modified to add space between the scroll area controls and the data fields on Level
1.




                                      Peoplesoft, Inc. Proprietary and Confidential

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:10
posted:4/24/2012
language:English
pages:24