SCT Banner Human Resources / Release Guide / 7.0

Section 23 Problem ResolutionsTime Entry and Payroll ProcessingTime Entry and Payroll ProcessingPHAADJTThe following defects have been resolved:• (#86028)The Adjustment Processing Form (PHAADJT) was setting the ReconciliationIndicator field and Reconciliation Date of an original event to null if an Eraseadjustment was performed on an adjustment to that event. This problem hasbeen corrected. Resolved in Human Resources Release 6.0.0.1.• (#86371)Deduction records were not being extracted correctly when a deduction isterminated on the last day of pay period and the previous status was eitherExempt or Waived. This has been corrected so that the extract logic matchesthe Time Processing Report (PHPTIME) and the Waived and Exempt recordsare now processed correctly when the deduction is terminated on the last dayof the pay period. Resolved in Human Resources Release 6.1.0.2.• (#87921)The Adjustment Processing form (PHAADJT) was allowing you to void aredistribution event. This was creating an out-of-balance condition since aredistribution transaction had already generated a reversal of money. The formhas been changed to preclude you from creating a void from the reversalsequence of the redistribution transaction. Resolved in Human ResourcesRelease 6.1.• (#89059)When a site established the Leave Processing Method as Leave By Job, an errorwas encountered when using the Adjustment Processing Form (PHAADJT).On entering the pay adjustment information in the called On-Line Time EntryForm (PHAHOUR), an error was created when an Earn code that was tied toa Leave code was used. This situation has been corrected so that any eligibleEarn code may be used on the adjustment transaction. Resolved in HumanResources Release 6.0.0.2.• (#91635)When processing a manual transaction and the print indicator was manual, theAdjustment Processing Form (PHAADJT) was giving an incorrect message andwas not allowing you to exit the form or complete the document historyinformation. After entering document information and attempting to save, thecursor would go to the Bank Routing Number field. Once this error wasencountered, all manual print transactions thereafter produced the samemessage forcing you to exit Banner and then go back in to continue withoutgetting this message. This problem has been fixed. Now you will be able toenter the check data correctly. Resolved in Human Resources Release 6.1.0.1.Human Resources/Position Control Release 7.0 January 2005306 Release Guide Confidential