SCT Banner Human Resources / Release Guide / 7.0

Section 23 Problem ResolutionsBenefits and Deductions AdministrationPDADEDNPTRBDCAPTRBDMCPDAFLEXPDABDSUPDCCOCE(#94904)These forms displayed amounts incorrectly by truncating starting with the zero onthe right side of the decimal. This did not cause incorrect data in the underlyingtables, but it did affect the display.For example, amounts of 5.23, 5.00, 5.10, & 5.03 were displayed as follows:"5.23" was being displayed as "5.23" correctly."5.00" was being displayed as "5" - truncating the value at the zero."5.10" was being displayed as "5.1" - truncating the value at the zero."5.03" was being displayed as "5.03" correctly.This has been corrected so that the forms in question now display the four decimalplaces if they have a plan associated with their calc rule; two decimal places if flatamount or percentage.As a note, the LOV display will continue to truncate the trailing zero(s) on the rightside of the decimal. Resolved in Human Resources Release 6.1.0.2.PDADEDNThe following defects have been resolved in the Employee Benefit or DeductionForm (PDADEDN):• (#89197)Under certain conditions, the Employee Benefit or Deduction Form(PDADEDN) would allow an employee to have two precluded deductionsactive on the same day. This problem has been corrected. Now, two precludeddeductions cannot be setup on the same day. Resolved in Human ResourcesRelease 6.0.1.1.• (#89668)The Employee Benefit or Deduction Form (PDADEDN) would erroneouslydelete the Self Beneficiary Coverage record (PDRBCOV) and the ExcludedPay ID record (PDRXPID - if one existed) when a deduction record wasdeleted, but the deduction still existed on a past Effective Date. This problemhas been corrected. If there are more than one PDRDEDN effective-datedrecords existing, then beneficiary records will not be deleted. Resolved inHuman Resources Release 6.0.1.1.• (#92278)When a deduction code is being created for the first time and a plan or amountwas required, using certain navigation options, it was possible to create recordswhere the first deduction detail record effective date did not match the basededuction begin date. This caused processing problems. The form navigationhas been corrected to now present an error message that the base record mustbe saved first before creating a future-dated deduction record. Resolved inHuman Resources Release 6.1.0.1.Human Resources/Position Control Release 7.0 January 2005296 Release Guide Confidential