13.07.2015 Views

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 23 Problem ResolutionsBenefits and Deductions AdministrationPPIADDR (#92317)Previously HR security was not invoked on the Address List Inquiry Form(PPIADDR) allowing all users to see potentially confidential employee addressinformation. Now, the security routines have been modified to enforce the HRsecurity rules as established by the user/administrator on the Organization SecurityForm (PSAORGN), the Employee Class Security Form (PSAECLS) and/or the UserCode Rules Form (PTRUSER). The information is now secure based on the site'ssecurity policies and security set ups. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> <strong>7.0</strong>.Benefits and Deductions AdministrationPDABCOV (#89765)Some changes to end dates on Beneficiary Coverage Form (PDABCOV) were notbeing recorded in the history table PDRBCHS, and as a result, the Audit Trail Report(PORAUDT) would not show an accurate audit trail. This problem has beencorrected, and now the changes are recorded in the audit trail. Resolved in <strong>Human</strong><strong>Resources</strong> <strong>Release</strong> 6.0.2.1.PDABENEThe following defects have been resolved:• (#84057)Previously, the Beneficiary Form (PDABENE) allowed you to check or uncheckthe College Indicator check box on the "S"elf relationship record. Thisfunctionality was inadvertently removed. This problem has been corrected.Now, you can now use the College Indicator check box on the "S"elf record.Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.• (#88077)When adding a new beneficiary record on the Beneficiary Form (PDABENE)by selecting an existing ID from the LOV (flashlight) button, you would get anerror indicating that the SSN could not be changed. This was an incorrecterror as the user was not trying to change the SSN, they were only adding thePPAIDEN record as a dependent record on PDABENE where the SSN is not arequired field. This problem has been corrected and now you can utilize theLOV to select the proper record to add to the Beneficiary Form (PDABENE).Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.• (#93656)Previously, when updating information on the Beneficiary Form (PDABENE),the Activity Date and Time were not correctly being updated. This has beencorrected. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.0.1.January 2005 <strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 295

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!