OneWorld Time Entry Errors, WBT & Support
Who: All IT Help Desk Technicians
Why: To provide a list of known errors, causes and resolutions for OneWorld Portal Time Entry.
What:
What GPSS Denver supports:
Once you have logged into the Time Entry application, support is provided by GPSS Denver. For all other issues follow normal support procedures/documentation.
Time Entry WBT:
If you have not completed the training please access the following location to launch the WBT for the Time Entry system:
\\corwrls1\world\Public\WBT\TimeEntry\MainMenu.htm
Troubleshooting invalid Time codes:
If a you cannot use a particular code or combination of codes, use the visual assist (torch icon shown to the right of the field) to display the list of valid codes for your BU in this field. It is possible the code you are trying to use is not valid/available for your BU. In this case refer to your manager, a coworker, or to Mylissa Moore for assistance in determining the correct code/s. The TSO cannot assist in determining the correct code(s).
Time Entry Lockout:
When Time Entry is closed you cannot access the grid to add time. You can, however, view previously entered time.
Reporting Issue:
Any time a new OneWorld package is deployed (once a month), it erases all user-created Time Entry reports. If this is the case you will need to recreate the report that you desire. If a new package was not deployed since you last ran the report(s), send a NorthStar ticket to GPSS Denver to investigate.
Troubleshooting Tips:
Time Entry is accessed through the OW Portal. Once in the OneWorld portal, select the Employee Workspace. The time entry component appears in the workspace for employees only.
Information Technology Users should NOT use the Quick Entry fields in Time Entry. Always use Detail Entry.
Work order entries require a ‘W’ be entered in the subledger field. This is new with OneWorld.
Some Business Unit/Pay Type combinations require a Cost Code be placed in the cost code field.
Save your time entry often (hit the save button).
It is a legal requirement that you enter your own time.
Account Validation in Time Entry allows only specific pay types to be used with certain business units. You should retry the combination of pay type to business unit before entering a call.
Known Errors:
These are the known errors in the OneWorld Time Entry application, along with the associated descriptions, causes, and resolutions.
If you are unable to resolve the error using the information provided, create a call in NorthStar
to be assigned to GPSS Denver.
| Error Message | Description | Cause |
|
| 5585 | Blank Charge To Business
Unit Invalid |
Business Unit/Project field is not populated. |
|
| 5586 | Pay Type cannot be used with the BU | BU type and Pay Type are not compatible per the BU Type to Pay Type Cross Reference Table (P5505001) |
|
| 5506 | Work Order/Subledger is Required | Pay Type requires that the Work Order/Subledger be populated per the BU Type to Pay Type Cross Reference Table. |
|
| 045J | Subledger Type Entry Invalid | If the subledger field is blank, the Subledger Type field must also be blank. If the Subledger field is not blank, the Subledger Type field cannot be blank.
|
|
| 044D | Subledger &1 &2 Invalid | The subledger entered must exist as a record in the proper file indicated by the the A = Address Book (Customer, Employee, Owner Numbers) - F0101
C = Business Unit Numbers - F0006 E = Equipment Numbers - F1201 J = Change Request Numbers - F5301B I = Item Number - F4101 L = Lease Numbers - F1501 O = Order Numbers - F4201 W = Work Order Numbers - F4801. |
|
| 0004 | Date Invalid or Missing |
The date field is invalid for one of the following conditions: Month not valid (must be between 1 and 12), Day not valid (must be between 1 and 31, and valid for month), Year not valid (must be between 00 and 99), Date has not been entered. Date must also be entered using either 6 digits or 8 digits. A leading zero must be used for months such as January (01 not 1).
|
|
| 1486 | Date Must Be Specified | No date was specified in either the date worked field of the subfile or in the header. |
|
| 1573 | Hours Must Be Greater than Zero | Hours field cannot be blank. |
|
| 0052 | Business Unit Invalid | The Business Unit entered does not have a Business Unit Master Set Up. |
|
| 4382 | Non-posting Business Unit | The Business Unit has been set to non-posting. You can not post transactions to this business unit. |
|
| 059S | Invalid Pay Type | The Pay Type that was entered is either non-numeric, less than 1, or greater than 999. |
|
| 3176 | Invalid Pay Type for Payroll System | The Pay Type being used is not set up for your Job Type. |
|
| 091C | Account Number is Invalid | This account does not exist in the Account Master file (F0901). |
|
| 0938 | Non-Posting Account or Business Unit | One piece, or the entire accounting structure being created (BU.object.subsidiary) is a non-posting account. |
|
| 056I | Subledger and Subledger Type Required | The posting edit code of this account indicates that a subledger and subledger type are required. |
|
| 070G | Subledger or Subledger Type Invalid | Subledger or Subledger Type is Invalid or Inactive |
|
| 0376 | Tax Area Invalid | The tax area does not exist in the Tax Area Master file (F069016) |
|
| 018A | &2 not found in User Defined Code &3 &4 | &1 &2 was not found in User Defined Code for system &3 , type &4 |
|
| 0626 | Asset Number Invalid - Input | This asset number does not exist in the Item Master file (F1201) or it is invalid. |
|
| 058P | Pay Type Not Setup | The pay type specified for the Regular or Vacation or Sick or Holiday hours has not been set up in the P051125 processing option. |
|
| 3176 | Invalid Pay Type for Payroll System | The Pay Type being used is not set up for your Job Type. |
|
| 008V | Model Account Number
Invalid |
You are attempting to make an entry to an account number designated as a model. Model account numbers do not post, therefore entries may not be made to them. |
|
Created by the PeopleSoft Knowledge Management Team.
Copyright © 2003
All rights reserved.
Created: amq 10/15/2003
Revised: amq 12/17/2003