SCT Banner Human Resources / Release Guide / 7.0

Section 23 Problem ResolutionsReports and Processestable and sees that it has already processed the earns from the PHATIMEprocess and consequently does not process them again. This leaves you withzero hours on the On-Line Time Entry Form (PHAHOUR) for the regularearnings which it must delete so that you're not left with earnings that havezero hours. The PHPMTIM process doesn't seem to work this way when theTime Entry Type on the Employee Jobs Form (NBAJOBS) is set to exceptiontime only. To resolve this problem, touch each earning on the Mass Time EntryProcess (PHPMTIM) for the employee for whom you enter additionalearnings. Secondly, if earnings became zero by delete operation in PHAMTIM,the zero earnings would not get removed. These problems have beencorrected.Now, once the earnings get initialized and loaded for the pay period time entryemployees, these earnings will not be re-initialized even if the Mass Time EntryProcess (PHPMTIM) is run multiple times. Also, zero earnings are removed fornon-payroll time entry employees regardless of the existence of PHRMTIMrecords. Resolved in Human Resources Release 7.0.• (#87164)Previously, when FOAPAL information was not entered in the PHRMTIM tableand the PTRPCLD or NBRJLBD tables contained an Index, the process would notcorrectly retrieve the account index. This problem has been fixed and thelabor distribution is now retrieved correctly. Resolved in Human ResourcesRelease 6.1.• (#87051)The Mass Time Entry Process (PHPMTIM) had not been inserting the hoursproperly if an employee had FLSA as the Time Breakdown Method. Theprocess has been updated and hours are now inserted correctly. Resolved inHuman Resources Release 6.1.• (#90196)The Mass Time Entry Process (PHPMTIM) would not report Oracle errors thatoccurred when loading information from the Web Time Entry tables into themass Time Entry Table, PHRMTIM, but erroneously updated the status of thetime transaction on the Web as Completed. Consequently no information wasbeing loaded into PHRMTIM or pay history. This problem has been corrected.An errors is now reported without changing the status. Resolved in HumanResources Release 6.0.4.1.• (#96939)This defect was created due to performance issues with the Mass Time EntryProcess (PHPMTIM). The change was to wrap a TO_CHAR function around alloccurrences of USERENV('SESSIONID') preventing a full table scan on thePOTPARM table. Resolved in Human Resources Release 6.1.0.1.January 2005 Human Resources/Position Control Release 7.0Confidential Release Guide 325