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 ResolutionsReports and ProcessesPERLEAV (#87876)Some of the Grand Total fields for displaying the leave hours on the Leave LiabilityReport (PERLEAV) were not large enough. The Available Balance, YTD Accrued,and Begin Balance fields were increased by 2 characters to match the YTD Takenfield size. When the field value exceeded the field size, the original issue caused #signs to be printed in these fields. This problem has been corrected. Resolved in<strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.PERUTAN (#14168)The Percentage of Weighted Factor parameter in the Utilization Analysis Report(PERUTAN), which defaulted to 100%, was missing from job submission. Thissituation caused erroneous results in the Summary Report. This problem has beencorrected and the parameter is available from job submission. Resolved in <strong>Human</strong><strong>Resources</strong> <strong>Release</strong> 6.1.PERV100The following defects have been resolved in the Veterans Employment Report(PERV100):• (#90681)The New Hires Within Period section of the VETS-100 report process, was notincluding employees that were terminated within the Start and End dates ofthe reporting period. The report was correctly counting employees in theNumber of Employees section of the report, in that, employees that wereterminated before the end date of the report were not included in the counts.With this update, the New Hires Within Period section of the report countsterminated employees as long as the termination (of the Employee record)falls within the reporting dates. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.0.4.1.• (#89562)In counting veterans to be reported, the process reported the same employeemultiple times if the employee had multiple primary jobs that fell within thereporting period. An example might be that an employee had multiple adjunctcontracts, that were designated as primary assignments within the reportingyear. This problem has been corrected. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong>6.0.1.1.• (#96702)The total number of employees reported in the 'Maximum' amount may beincorrect when running the report for the year (as opposed to running it for amonth time frame). This can happen when differing pay ID's pay period startand end dates overlap each other, such as two biweekly payrolls with differentCheck Issue Dates and only one Check Issue Date falls within the reportingperiod.The employee selection was modified so that the maximum count will includeemployees whose Pay Period Begin Date or Pay Period End Date fall within thereport selection period. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.<strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong> January 2005320 <strong>Release</strong> <strong>Guide</strong> Confidential

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

Saved successfully!

Ooh no, something went wrong!