SCT Banner Human Resources / Release Guide / 7.0

More documents

Recommendations

Info

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 inHuman Resources Release 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 HumanResources Release 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 Human Resources Release 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 Human Resources Release6.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 Human Resources Release 6.1.Human Resources/Position Control Release 7.0 January 2005320 Release Guide Confidential
Section 23 Problem ResolutionsReports and ProcessesPHPCALCThe following defects have been resolved in the Payroll Calculation Process(PHPCALC):• (#87730)The Payroll Calculation Process (PHPCALC) was not compiling correctly onsome platforms. A technical change was made to compile correctly. Resolvedin Human Resources Release 6.0.0.1.• (#94599)The FLSA "daily" overtime hours was not being calculated with time entrybreakdown methods other than daily. This resulted in too many overtimehours being generated for each work period. This has been resolved. The dailyovertime hours are now calculated correctly for FLSA, weekly, and pay periodtime entry breakdowns. Resolved in Human Resources Release 6.1.0.1.• (#87044)The Payroll Calculation Process (PHPCALC) was not calculating the dailyFLSA overtime correctly for employees with multiple jobs. This problemoccurred when the total hours worked on a given day exceeded the maximumdaily hours allowed as defined on the Work Period Rules Form (PTRWKPR),and the employee had hours entered for two or more days in the pay period.This problem has been fixed and overtime is now calculated correctly. Resolvedin Human Resources Release 6.1.• (#3188)Rounding problems occurred when creating Time Distribution records forFLSA generated earnings.For example: An employee had a default labor distribution split 50/50 betweentwo FOAPALS. In the current pay event, .75 hours of FLSA OT was generated.The hours calculated for each FOAPAL was .38 hours, for a total of .76 hours.When the user queried this pay event, he/she was trapped in the form sincethe earn hours did not equal the earnings labor distribution hours. Thisproblem has been corrected and the hours will now be rounded so that theyequal. Resolved in Human Resources Release 6.1.• (#89437)The Payroll Calculation Process (PHPCALC) was not compiling on anon-MicroFocus compiler. This problem has been corrected. Resolved inHuman Resources Release 6.0.0.2.• (#92181)The Payroll Calculation Process (PHPCALC) has been modified to look to theState code rather than the Tax code to determine if the tax amount for thespecific state should be rounded or not. The rounding process only applies tocertain states, namely, ME, MN, MO, OK, SC, VA, CO, ID, NC, ND, and MT atthis point. Resolved in Human Resources Release 6.1.PHPCHKL (#90199)The Long Check/Direct Deposit Notice (PHPCHKL) was not printing the bankaccount information for the direct deposit. This printing problem also causedproblems for other information on the form. The process has been corrected andnow prints properly. Resolved in Human Resources Release 6.0.4.1.January 2005 Human Resources/Position Control Release 7.0Confidential Release Guide 321
Page 1 and 2:
SCT BannerHuman Resources/Position
Page 3 and 4:
Release GuideHuman Resources/Positi
Page 5 and 6:
Table of ContentsChanged Forms . .
Page 7 and 8:
Table of ContentsSection 12 CA-MIS
Page 9 and 10:
Table of ContentsSection 21 Miscell
Page 11 and 12:
Table of ContentsSection 24 Problem
Page 13 and 14:
IntroductionIntroductionThis Releas
Page 15 and 16:
IntroductionOSHA Reporting Enhancem
Page 17 and 18:
Section 1 New Banner Online HelpInt
Page 19 and 20:
Section 1 New Banner Online HelpFea
Page 21 and 22:
Section 1 New Banner Online HelpFea
Page 23 and 24:
Section 2 New User Interface-Functi
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Section 3 Employee API - Functional
Page 45 and 46:
Section 3 Employee API - Functional
Page 47 and 48:
Section 4 Employee API - TechnicalO
Page 49 and 50:
Section 4 Employee API - TechnicalN
Page 51 and 52:
Section 5 Banner Support for Salary
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Section 6 Banner Support for the Sa
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Section 7 Support for 1099-R Change
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Section 8 Support for 1042-S Change
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Section 9 Support for US W-2 and MM
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Section 10 Support for Puerto Rico
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Section 11 Support for 1099-R Chang
Page 171 and 172:
Section 12 CA-MIS Reporting Enhance
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Section 14 OSHA Reports for 2003 -
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Section 16 IPEDS Reports for 2003 -
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Section 18 VETS-100 Reporting for 2
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Section 20 Canadian Regulatory Enha
Page 255 and 256:
Section 21 Miscellaneous Enhancemen
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270: Section 21 Miscellaneous Enhancemen
Page 291 and 292: Section 23 Problem ResolutionsImple
Page 293 and 294: Section 23 Problem ResolutionsRule
Page 295 and 296: Section 23 Problem ResolutionsBenef
Page 297 and 298: Section 23 Problem ResolutionsBenef
Page 299 and 300: Section 23 Problem ResolutionsEmplo
Page 305 and 306: Section 23 Problem ResolutionsHealt
Page 307 and 308: Section 23 Problem ResolutionsTime
Page 313 and 314: Section 23 Problem ResolutionsTax A
Page 315 and 316: Section 23 Problem ResolutionsRepor
Page 319: Section 23 Problem ResolutionsRepor
Page 331 and 332: Section 24 Problem Resolutions- Tec
Page 337 and 338: Appendix A Example of Annual Salary
Page 339 and 340: Appendix A Example of Annual Salary
Page 341 and 342: Appendix B Example - Setting Up VBS
Page 361 and 362: Appendix C Using the Common Person
show all

SCT Banner Human Resources / Release Guide / 7.0

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

Delete template?

Save as template?