When you approve a timesheet or an employee expense in Project Time and Expense in Microsoft Dynamics GP 10.0, in Microsoft Dynamics GP 9.0, or in Microsoft Business Solutions – Great Plains 8.0, you may receive one of the following error messages or the following unexpected behavior may occur. These problems occur if Automatic Processing is enabled.
Unexpected behavior
Error messages
- You receive the following error message when the pay rate has 4 decimal places. See Resolution 1 or Resolution 2.Processing failed for XYZ-TS-MMDDYY-X : Unit cost for this pay code do not match - unit cost cannot be changed.Note XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
- You receive the following error message when the profit in the rate table has changed since the time that the timesheet was entered. See Resolution 1 or Resolution 2.Total Accrued Revenue does not match sum of lines.
- You receive the following error message when the total cost of the employee expense is rounded to two decimals. See Resolution 1 or Resolution 2.Processing failed for XYZ-EE-MMDDYY-XNote XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
- You receive the following error message when the vendor record does not have a value in the Address ID field in the Primary Address area of the Vendor Maintenance window. See Resolution 1, Resolution 2, or Resolution 3. Processing failed for XYZ-EE-MMDDYY-X: Input variable contains an empty value.Note XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
- You receive the following error message when the currency that is specified in the Billing Currency ID field for the project is not the functional currency. See Resolution 1 or Resolution 2. Processing failed for XYZ-TS-MMDDYY-X : Total Accrued revenue does not match sum of detail lines.Note XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
- You receive the following error message when the status of the budget is set to Completed. See Resolution 1, Resolution 2, or Resolution 4. Processing failed for XYZ-TS-date-1 : Budget status is invalid - budget status needs to be open.Note XYZ is the placeholder for the employee, and date is the placeholder for the date.
- You receive the following error message when the employee expense transaction is for a negative quantity. See Resolution 1 or Resolution 2. Processing failed for XYZ-EE-MMDDYY-X: Input variable contains a negative valueNote XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
- You receive the following error message when the Timesheet transaction is for a negative quantity. See Resolution 1 or Resolution 2. Processing failed for XYZ-EE-MMDDYY-X: Input variable (PATACRV) contains a negative valueNote XYZ is the placeholder for the employee, MMDDYY is the placeholder for the date, and X is the placeholder for the sequence number.
Unexpected behavior
- The employee expense document posts to the Payables Management module even if the Post to Payables Management check box is cleared in the Employee Expense Setup window. See Resolution 1 or Resolution 2.
- Billing notes are not sent to Project Accounting together with the employee expense transaction. See Resolution 1 or Resolution 2.
- The Timesheet Detail Work table (PA10001) contains records that do not have an associated header record in the Timesheet Header Work (PA10000) table. This problem occurs if you received an error message on one, but not all, of the lines of the timesheet when you approved the timesheet. See Resolution 1 or Resolution 2.