SCT Banner Human Resources / Release Guide / 7.0

More documents

Recommendations

Info

Section 23 Problem ResolutionsTime Entry and Payroll Processing• (#94818)The Labor Redistribution Form (PHAREDS) did not split the labordistribution when a payroll crossed fiscal years. The entire transaction wasposted based on the Posting Date entered in the form, which was a requiredfield. This has been corrected to allow for a Null override of the Posting Datewhen the pay event is split across fiscal years. New edits have been added to theform as follows:(a)(b)When a Posting Date is entered, an edit will validate that the BannerFinance accounting period is open (or in accrual). If not, an errormessage will be displayed, *ERROR* Accounting period closed. Re-enter a newPosting Date.When a Posting Date is not entered:Validate that the pay event spans two fiscal years. If it doesn't span twofiscal years, an error message will display, *ERROR* Posting Date is requiredif pay period does NOT cross fiscal years.Validate that the prior fiscal year accounting period is not closed. If theprior fiscal year accounting period is closed, an error message will display,*ERROR* Old fiscal year period for split pay event is closed. Posting Date isrequired.A posting date is calculated based on the fiscal year (prior or new) inwhich the split part of the pay event falls. If the split is effective during theprior fiscal year, the calculated posting date is typically in the prior fiscalyear. If the split is effective during the new fiscal year, the calculatedposting date is typically in the new fiscal year.When editing labor distributions, the scope of the changes is limited tothe pay event being edited and will not affect any other pay events thatmay have been queried. This specifically applies when the Change All boxis checked.(c)If the Posting Date is changed the form will re-edit the labor distributionsusing the new Posting Date. This will happen during the OK Changes orsave/commit.(d) Changes to the labor distribution edits:When a Posting Date is entered, during data entry the FOAPAL is editedagainst Banner Finance using the entered posting date. A re-edit is alsoperformed during the save.When a Posting Date is not entered, during data entry the FOAPAL isedited against Banner Finance using the calculated posting date. A re-editis also performed during the save.Human Resources/Position Control Release 7.0 January 2005310 Release Guide Confidential
Section 23 Problem ResolutionsTime Entry and Payroll ProcessingIf the 'Change All' box was checked, the FOAPAL is edited against BannerFinance using the calculated posting date for each earnings labordistribution in the pay event. If a FOAPAL component is invalid, an errormessage is displayed similar to, *ERROR* Fund 1000 is terminated. See JobA10001-00, Effective Date 10-AUG-2004, Earn Code REG, Shift 1 of this payevent.(e)New edits on the Search and Replace Posting Date.The Search Posting Date remains a required field. An edit now validatesthat the Banner Finance accounting period is open (or in accrual). If not,an error message will be displayed: *ERROR* Accounting period closed. Reentera new Posting Date. Resolved in Human Resources Release 7.0.PHATIMEThe following defects have been corrected in the Electronic Approvals of TimeEntry Form (PHATIME):• (#88918)When deleting a time transaction that was classified as a Leave Report, thefollowing message was being displayed in error: *ERROR* Leave Code is notdefined on PTVLCAT. The system displayed an additional message: Removing thisrecord will delete the employee's time transaction. Do you want to delete this transaction?On responding Yes, the form then displayed: Delete Process is Complete. Followingthese messages, another error popup window was being displayed: *ERROR*Leave Code is not defined on PTVLCAT. This message had to be acknowledgedtwice, and then the form would close, even though additional employeesexisted in the Leave Report list. This problem has been corrected. TheElectronic Approvals of Time Entry Form (PHATIME) no longer displays theerror message regarding the Leave Category Validation Form (PTVLCAT) andyou can now remove a Leave Report without the form terminating its process.Resolved in Human Resources Release 6.0.1.1.• (#93396)Superusers can now submit any leave report or time sheet in a "in progress"status when the time/leave entry period is open. Previously, superusers couldonly submit when the time/leave entry period was closed.A superuser can also extract any leave report/time sheet when the leave/timeentry period is open or closed. If the entry period has not opened, then no onecan extract a leave report/time sheet. Previously, superusers could only extractwhen the time/leave entry period was closed.These extended capabilities were added so superusers have more flexibility inhandling time sheets when an employee is unable to extract or submit theirtime sheet on time. If the superuser knows that the employee won't be able toextract or submit their time sheet before the entry period closes, he/she won'thave to wait for the entry period to close to process a time sheet for theemployee.This change was delivered with the 6.0 release of Banner Human Resourcesand Employee Self-Service, but was not documented in the Release Guides.Documentation defect resolved in Human Resources Release 6.1.January 2005 Human Resources/Position Control Release 7.0Confidential Release Guide 311
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:
Section 21 Miscellaneous Enhancemen
Page 259 and 260: 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 309: Section 23 Problem ResolutionsTime
Page 313 and 314: Section 23 Problem ResolutionsTax A
Page 315 and 316: 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?