Project Accounting Misc Log entry-detail line to default to expanded mode. The user has to deliberately click on the 'show more details' icon so that they can key in a unit cost. The default capture mode should be expanded so that the cost field is easily visible.
I've discovered that there is a problem with the inventory quantities being allocated in the inventory tables if a project inventory transfer is saved into a batch and the Inventory Reconcile task is run. I therefore think that it would be excellent if the option of marking the PA Inv Trf to post through to the GL actually did that - it must post right through. I could then enable transactional posting for that PA transaction type.
I know that standard functionality won't post right through to the GL if the entry is not saved in a batch in the sub-module, but it would be great if an exception could be made for this PA transaction type bearing in mind the issue around the stock quantities saved in a batch.
This is my suggestion to ensure that the stock quantities are not corrupted and that the finance user does not have to manually post the batches.
When billing fees, it is often necessary to include a quantity without associating the fees with a cost transaction. Suggestion: add the option to bill (and budget) a quantity x rate for Fee Billings so the users don't have to waste lines in the Fee notes to add that information.
A Project Accounting PO created off a Requisition must be allowed to be cancelled. Currently there is no way of cancelling a PO line or voiding or deleting a PO if a requisition that has project accounting on it was transferred into a PO. This is a bug which should be fixed as soon as possible.
Allow employees to view their historical project accounting timesheets and expense reports via web client. As it is now, once a user's timesheet is submitted/processed/posted he/she cannot look at it again. If she wants to see how many hours she worked on a given week, she has to ask accounting to run a report.
The tools to change Customer, Vendor, Item and Payroll related ID's are phenomenal! We need the same tool for Project Accounting! It would nice to see an option for Project Number and Contract Number since they're the key fields, but if we need to prioritize or choose one, the Project Number would be the choice due to the fact that it's the key field for all data entry.
On the Project Closing window, there is no way to determine if a timesheet that has charged to a project is still in workflow. The project closing checklist is checked which tells me that the project is ready to be closed. There should be a warning that there are some pending timesheets waiting to be approved if you try to close a project.
You're able to make cost categories inactive - it would be great to have the same option for fees (Project Accounting > Cards > Fees), in order to maintain historical details but keep users from using fees that no longer apply.
Not all GP Project Accounting users know the amount/fee that will be billed at the time the project/budget is created, and some companies do not care to budget that. For those companies, having to add the fee to the project before being able to bill that fee is just a wasted step, which in turn is wasted time. I would like to see 2 related options added to the billing setup options:
1. Add fees on the fly (i.e.: when billing, select a fee and be able to choose to add it on the fly, just like you can for cost categories)
2. Allow the fee billing amount to exceed the budgeted fee amount
Both of these options exist for T&M cost category billing and it would be nice to see the consistency flow through all T&M project billing methods.
We have employees that utilize timesheet templates. The employee may only utilize just a few of the lines on the template on a given week. What I am finding in tracing the SQL and Dex code is that GP is processing each day for each line regardless if any time has been entered thus causing the submission process to be slower than it needs to be.
Two stored procedures could be modified to only process the lines where time has actually been entered on.
The first stored procedure is zDP_PTE10001L_1 by adding an additional AND clause "and pte_quantity<>0 " which will remove the lines that do not have time on them from being considered.
The second stored procedure is a temporary stored procedure that gets generated in the dex code. In this particular instance, the stored procedure is ##zDP_2113547F_1.
When executing that stored procedure , you get results which includes all the lines regardless if any time has been entered for them…
If you modify the stored procedure to include a where clause
to exclude results from the pte_qty_week_x columns that equal 0
you receive significantly less results.
By making the changes, GP will only process the projects that have time applied to them.
You can further optimize the process by only processing the actual day if pte_qty_week_1 through 7 is greater than zero. In a sample dex trace, GP calls a lot of stored procedures for each day that scan a lot of PA tables even if no time has been entered for it. For example,it will will loop through each call 7 times for the one line that the employee has a pay code on even though he did not even use it.