SCT Banner Human Resources / Release Guide / 7.0

Section 23 Problem ResolutionsEmployment Administration• (#93718)The Employee Jobs Form (NBAJOBS) now allows job changes to invalidsupervisor information after the effective date of the supervisor termination.Resolved in Human Resources Release 7.0.• (#96282)The Employee Jobs Form (NBAJOBS) was allowing terminated records thatwere prior to the last paid date to be removed. This would happen if thetermination date were some other date other than the last day of the payperiod. This deletion should not happen because there are payroll records thatexist. Now, the termination record cannot be removed once pay history existsfor the pay period in which the termination date falls. Resolved in PositionControl Release 6.1.0.3.• (#96501)Previously, when a time sheet organization code was invalid, the Employee JobsForm (NBAJOBS) did not allow future changes to be made via the Job Detailwindow. This has been corrected to allow the future change to be saved andviewed on NBAJOBS. Resolved in Human Resources Release 7.0.NBIJLST (#88821)The sort order on the Employee Job Inquiry Form (NBIJLST) has been changed tosort by effective date rather than the original sort based on the employer code. Now,the earliest records are displayed at the top of the list with the most recent record atthe bottom of the list. Resolved in Human Resources Release 6.1.PEAEMPL (#89863)When processing Leave by Employee, the Employee Form (PEAEMPL) was notinserting new leave codes when an employee was changing from one Leave Categorythat did not grant specific leave, to a new one that included a new leave code. Thisproblem has been corrected so that when you change an Employee Class or LeaveCategory, the appropriate leave records will be inserted into the employee's leavebalances. Resolved in Human Resources Release 6.0.2.1.PEAESCH (#98142)The Employee Status Change Form (PEAESCH) was not populating the DeductionEnd Date field with the correct value when a Terminate action was chosen, the AllRecords check box was checked, and the Personnel Change Date was less than theLast Paid Date.When the Personnel Date value is less than the Last Paid Date, the form shouldterminate jobs and deductions as of the date in the Last Paid Date field. This was nothappening for deductions. The form seemed to be using the pay period end datefrom the pay event (PTRCALN) in which the personnel date fell. This caused theerror message: * ERROR* Deduction End Date cannot be prior to the Last Paid Date todisplay and you could not advance beyond the Key block.Human Resources/Position Control Release 7.0 January 2005300 Release Guide Confidential