web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Dynamics GP Support and Services Blog / New troubleshooting documen...

New troubleshooting document available for Project billing

Views (23567)
Pam Peterson Profile Picture Pam Peterson Microsoft Employee

Hello everyone,

I wanted to make sure you were aware of a new, comprehensive troubleshooting guide we have available for Project Accounting billing issues.  This document covers the following topics:

1. Data entry problems with billing invoices for Time and Material projects
2. Data entry problems with billing invoices for Cost Plus or Fixed Price projects
3. Data entry problems with billing invoices for projects that bill fees
4. Posting problems with billing invoices for Time and Material projects
5. Posting problems with billing invoices for Cost Plus or Fixed Price projects
6. Posting problems with billing invoices for projects that bill fees
7. The error message - You cannot enter a Batch ID that has unposted receivables transactions
8. The drill back from the inquiry window is incorrect 

Also included in the Appendix is a SQL script that you can use to see all of the tables a specific billing document exists in.  Simply enter your document # and run it against your company database.  If you are not able to correct your issue, open a support case and send the file results to Support and we can take a look at it for you!

Find this guide and script using these links -

Customers - Click HERE  
Partners - Click HERE

Enjoy!

Pam Peterson

Comments

*This post is locked for comments

  • Pam Peterson Profile Picture Pam Peterson Microsoft Employee
    Posted at

    Hey Kristie,

    You certainly could update the ORTRXSRC field but I can't really think of any ill affects from it being RMSLS. I would be more concerned about the TRXSORCE field being wrong since that can cause drillbacks to not bring you to the expected place.

  • Kristie McNulty Profile Picture Kristie McNulty 1,008
    Posted at

    Hi Pam, I have a question about the GL queries provided in the "All Billing Doc" SQL script.  First, I had to remove the part of the script limiting the returned rows for SERIES = 7 because my latest interrupted batch of PA invoices has been posted from the Sales module and the SERIES value returned in the GL is 3 which also results in the ORTRXSRC value in the GL20000 table starting RMSLS instead of PABL.  So my question is, does the ORTRXSRC value need to be updated to the PABL value it would have been had the transaction posted from Project Accounting originally?

  • Pam Peterson Profile Picture Pam Peterson Microsoft Employee
    Posted at

    Hi Rahim,

    I'm glad you like the document.

    Unfortunately there are no known steps that cause the type of interruption that you are describing and until we have steps that will re-create the issue at will, there is very little we can do to code around it.

    In the meantime, I would encourage the users to print Edit Lists before posting and check for any errors there that could prevent the problem.

    Good luck!

  • Rahim J Profile Picture Rahim J
    Posted at

    Pam - this is a very helpful document.  We have a client that is experiencing a number of issues when posting Billing Entries in PA - primarily, the entries post fine in PA but not in RM (they end up in Batch Recovery).  It's usually a simple fix of just recovering them and manually posting in RM, as you mentioned in your document.

    Is this issue being addressed by Microsoft?  Is there a concrete way to reproduce this error?  I have been unable to reproduce it myself, but have received numerous complains from clients as it continues to occur to them.

  • Pam Peterson Profile Picture Pam Peterson Microsoft Employee
    Posted at

    Thanks for your comment, Kristi.  We tried to just return the most important data in the script results rather than whole tables since there can tend to be a lot of information there to sort through.

    So if you want to see more of what was in the GL, then I would recommend using the JRNENTRY value that was returned in the billing script and using it in your Where clause in a full select statement. The value in the Status field will let you know which GL table to do the select from.

    1 - GL10001

    2 - GL20000

    3 - GL30000

    So if you see the following results in your billing script:

    ORDOCNUM JRNENTRY Status

    BILL0000000000005     3470 2

    Your statement would be:

    SELECT * FROM GL20000 WHERE JRNENTRY = 3470

    Good luck!

  • Kristie McNulty Profile Picture Kristie McNulty 1,008
    Posted at

    I'm using your document to troubleshoot a billing batch interruption issue and the SQL script embedded is not complete for the "GL" section.  Do you happen to have the rest of the script for the GL section you can share please?

  • Pam Peterson Profile Picture Pam Peterson Microsoft Employee
    Posted at

    That is great to hear that it was helpful to you!

    KB 874076 provides steps on how to reverse a billing invoice so I would start there. If you need further help, please post your question on the Forums which is an area better suited for troubleshooting.  Thanks!

  • Benyamin Profile Picture Benyamin 250
    Posted at

    Very nice document, really helpful...

    btw, I have 1 issue where a bill was posted to a customer for a material purchased via a PO... turns out the PO used an incorrect cost category, now I need to cancel/reverse out the bill. Is that possible, can you help to provide a step by step guide (i'm quite new to this PA module)

    Thanks.