You receive an error when you try to enter a negative quantity or do a return for a project in Microsoft Dynamics GP

Symptom
You experience one of the following errors when you enter a negative quantity on a cost transaction or enter a return in an attempt to reduce the cost on your project. 


You are not allowed to have negative Actual Quantity.

You are not allowed to have negative Actual Costs.

You are not allowed to have negative Actual Accrued Revenues.

You are not allowed to have negative Total Revenue for the Cost Category within the Budget.

You are not allowed return accrued revenues greater than the actual posted amount.

You are not allowed to return a quantity greater than the actual posted quantity.

You are not allowed to return costs greater than the actual posted amount.



These errors may be seen in the following cost transaction entry windows:

Timesheet Entry

Employee Expense Entry

Equipment Log Entry

Inventory Transfer Entry

Returns from Project Entry

Returns Transaction Entry


Cause
When you enter a negative cost transaction or a return transaction in Project Accounting the system will look back to what has previously been posted against that project and cost category to determine if the transaction you are entering now will bring the posted amount below zero. It does this in 3 areas: Quantity, Cost, and Revenues and will only let you complete entry of the transaction if all 3 values will result in 0 or more on the project.

It is the PA01301 (Project Budget Master) table that is examined to make this determination. These are the fields that are reviewed for each of the areas.

Quantity -- PAPostedQty and PAUnpostedQty

Cost -- PAPostedTotalCostN and PAUnpostedTotalCostN

Revenues -- PAPosted_Accr_RevN and PAUnpostAccrRevN

The system will add up the values in both fields and then compare that to what you are currently entering. For example, you posted a timesheet with a quantity of 8 hours (PAPostedQty = 8). You then entered a new timesheet for -2 hours to reverse part of the original and saved it in a batch (PAUnpostedQty = -2). You would be able to enter another transaction for -6 (8 + -2 + -6 = 0) but not for -7 since then with the 3 transactions you would have a -1 quantity on the project.

The same calculation applies to the Cost and Revenue fields.

Note Miscellaneous Log cost category types are the only ones that are allowed to go negative for actual posted Quantity, Cost, and Revenues.

Resolution
To review the values considered, access the project and cost category in the Budget Detail Entry window. To access the Budget Detail Entry window on the Cards menu, point to Project, and then click Project. Enter your Project Number and click Budget. Highlight the cost category and click the expansion arrow on Cost Category ID field. Review what is displayed for Qty and Total Cost in the Actual row. To review the detail behind those summary values, click Actual to drill back to the associated cost transaction inquiry window.

You can also review the values in the table by running the following script.

SELECT PAUnpostedQty, PAPostedQty, PAUnpostedTotalCostN, PAPostedTotalCostN, PAUnpostAccrRevN, PAPosted_Accr_RevN, * FROM PA01301 WHERE PAPROJNUMBER = 'XXX' and PACOSTCATID = 'YYY' 

Note XXX would be replaced by the Project Number.

Note YYY would be replaced by the Cost Category ID.

If your detail transactions do not support your summary values, run PA Reconcile on Cost Transactions for the customer on this project. To run PA Reconcile on the Microsoft Dynamics GP menu, point to Tools, point to Utilities, point to Project, and then click PA Reconcile.

If PA Reconcile does not correct the error, then verify there are no orphan, unposted transactions in the corresponding Work transaction table.

Timesheets: PA10001

Employee Expenses: PA10501

Equipment Logs: PA10101

Purchase Materials: PA10901 and PA10702

Inventory: PA10901

If stranded records are found, remove them, and then run PA Reconcile again.

More Information
If the PA01301 is not reflecting the actual posted quantity, cost or revenue when you compare to the detail and PA Reconcile is not correcting it, then there is likely something incorrect or damaged with the posted cost transaction(s). Review the cost transaction for abnormalities and consider removing history and reentering the transaction.

Posted cost transactions are stored in the following tables:
Timesheets: PA30101

Employee Expenses: PA30501

Equipment Logs: PA30201

Purchase Materials: PA30901 and PA31102

Inventory: PA30901

Note If you are working with a purchase materials transaction, verify in the PA31102 that the ORD field is set correctly. If the receipt was from a purchase order (PApurordnum field is populated), then the ORD field should be populated with something other than 0. If no PO was involved, then the ORD field should be 0. If it is incorrect, update it, and then re-run PA Reconcile on Cost Transactions.  

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Propiedades

Id. de artículo: 2549380 - Última revisión: 03/17/2016 23:34:00 - Revisión: 7.0

Microsoft Dynamics GP 2015, Microsoft Dynamics GP 2013, Microsoft Dynamics GP 2010, Microsoft Dynamics GP 10.0, Project Accounting

  • kbmbsmigrate KB2549380
Comentarios