Error Resolution
Fixing and understanding system error messages.
Unable to view receipt in back office or PortalAn approver cannot view the receipt attached to an expense in Portal or back office.
Error: Number of fields on file do not match number of Required ColumnsError when a back office user tries to upload a P11D file.
Error: Tax year on the system needs to be updatedWhen a user tries to update availability dates in the Car Administration Centre, the following error appears: Tax year on the system needs to be updated
Exclude expense group from ERRExclude an expense group from the ERR parameter screen.
Error: Invalid claimant, possibly not set up correctly, contact your administratorError when accessing a claimant's record in back office.
Error: Error Transferring Log File... User-Defined ExceptionWhen generating the General Ledger file, the following error appears: Error Transferring Log File... User-Defined Exception
Error: You are not Authorised to ApproveA back office user is unable to bulk approve claims in the approval processing screen. The following error appears: You are not Authorised to Approve
Error: Invalid BIC codeWhen viewing the claimant details, the following error appears: Invalid BIC code.
Error: My Approvals 404: Not FoundA manager goes to their My Approvals section to approve an expense trip and error message "404: Not Found" displays.
Error: Unable to modify this claim as the information has been prepared for the paypath fileBack office user is getting an error message when trying to action a claim via the Approval Processing screen.
Error: FRM-41214 Unable to run reportError when trying to run validation on expenses.
Number of claims that can be included on an expense trip reportRestrict the number of claims that can be included in an expense report.
Error : You have selected a mileage expense code but have not selected a carWhen entering a mileage claim in portal, the following error appears:
You have selected a mileage expense code but have not selected a car
Error: User does not have access to claimant no ###A back office user is unable to view claimant details on the expense enquiry screen. The following error appears: User does not have access to claimant no ###
Error: Sort Code not specified for ClaimantError when attempting to run the create paypath data in the expense run:
Sort Code not specified for Claimant
Error: FRM-40212 - Invalid value for field APPROVER_NOAn employee is unable to approve expenses in back office due to the following error message:
'FRM-40212 Invalid value for field APPROVER_NO'.
Error: POST TEXT ITEM trigger raised unhandled exception ORA-01422When a back office user attempts to enter a location from the dropdown menu, the screen hangs, and the following error appears:
POST TEXT ITEM trigger raised unhandled exception ORA-01422
Error: ERROR - Invalid expense group codeWhen a back office user attempts to access the Expense System Users screen, the following error appears:
ERROR - Invalid expense group code...
Error: FRM-40831 Truncation occurred: value too long for field FROM_LOCATION/TO_LOCATIONWhen viewing a trip in Expense Trip Enquiry screen , the following error appears: FRM-40831 Truncation occurred: value too long for field FROM_LOCATION/TO_LOCATION
Error: Error in Submit batch ORA-00001: unique constraint (OPS$COREHR.EX_TASKS_TO_RUN) violatedError message appearing when running the Complete Cheque Update in PeopleXD Expense.
Error: No scale class found for scale code XXWhen setting up a claimant, the following error appears:
No Scale Class set up against Scale Code XXX
Error: Your dates seems to be spanning expense yearWhen creating an expense report in portal with dates for the next expense year and trying to save the report, the following error appears:
Your dates seem to be spanning…
Error: Unable to read P11D load flat file, failed at location ##...ORA-06502: PL/SQL: numeric or value errorWe have attempted to load our P11d csv file into both UAT and LIVE but our file is not being accepted.
Error: Claimant does not exist - cannot set up on expensesWhen accessing a claimant's record in back office, the following error is encountered: Claimant does not exist - cannot set up on expenses.
Error: INVALID EMPLOYEE - PLEASE CHECK THAT THIS IS A VALID COREPAY EMPLOYEEWhen attempting to load a P11D file, a report is produced with the following error: INVALID EMPLOYEE - PLEASE CHECK THAT THIS IS A VALID COREPAY EMPLOYEE
Error: Please review the form for errorsWhen an employee attempts to submit an expense item in Core Portal, the following error appears: Please review the form for errors.
Error: Error calling py_err.payroll_submission Employee ALL at location L error ORA-01403: no data foundWhen generating the ERR for an expense run, the following error appears:
Error calling py_err.payroll_submission Employee ALL at location L error ORA-01403: no data found
Error: Unable to notify claimant; no email address existshen trying to save an expense or proxy claim, the following error appears: Unable to notify claimant; no email address exists
Error: Complete update cannot be run as the Paypath data has not been createdWhen running the complete cheque update in PeopleXD Expense, the following error appears: Complete update cannot be run as the Paypath data has not been created.
Upload P11D CSV detailsRequirement for uploading data in PeopleXD Expense for P11D and P11D(b).
Unable to view all reference menu options in Core ExpenseSteps to add the reference menu options in Core Expense.