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 ResolutionsEmployment AdministrationIf an employee had a series of job effective dated records and you terminatedthe record prior to the last effective dated record, the End Date was set to bethe Effective Date of the terminated record. The future change record was notconsidered when populating the End Date.Both the problems have been corrected to reflect the correct End Date whenthe greatest effective dated record has a status of terminated, or a null EndDate when the greatest effective dated record has a status other thanTerminated. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.• (#85322)When entering a new effective dated record to terminate an employee with aterminated supervisor, the form looked at the employee termination date todetermine if the invalid supervisor message should be displayed. The errorshould display only if the employee termination date is after (greater than) thesupervisor termination date. This allows an employee and supervisor to beterminated on the same day without incorrect error messages. Resolved in<strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> <strong>7.0</strong>.• (#88112)The NBAJOBS End Date was not being populated when creating a neweffective-dated change as a termination. This problem has been corrected andyou cannot exit the form when a termination exists without populating the EndDate or changing the Job Detail status. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong>6.1.• (#90898)When future changes were added in the Detail window of the Employee JobsForm (NBAJOBS), where the effective date was in a fiscal year that was notchecked as Active on NBAFISC, the PERJHIS record was not written out. Thisproblem has been corrected. Now, a PERJHIS record is always written when anew job detail record is changed or inserted. Resolved in <strong>Human</strong> <strong>Resources</strong><strong>Release</strong> 6.0.0.2.• (#92337)This defect only affects those clients who allow for the insertion/deletion ofNBAJOBS records between effective dates. This is accomplished by setting theInsert Job Detail Data Between Existing Records indicator on the PositionControl Installation Rules Form (NTRINST) to Allowed.Two scenarios using NBAJOBS have been disabled so as to remove thepossibility of corrupted data records being saved to the database. One of thescenarios allowed you to delete the first effective dated record when futuredated records exist. You are given the proper warning messages, but deletingthe first effective dated record caused an orphaned record in the database.This has been corrected so that the first effective dated record cannot beremoved. An error message has been added to this effect.The second scenario included trying to insert a record with an effective dateprior to the job begin date. This is no longer allowed. An error message ispresented when you tried to insert this new record. Resolved in <strong>Human</strong><strong>Resources</strong> <strong>Release</strong> <strong>7.0</strong>.January 2005 <strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 299

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

Saved successfully!

Ooh no, something went wrong!