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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Dynamics GP 2013 Payroll Batch Posting Interrupted

(0) ShareShare
ReportReport
Posted on by

We have a client who's Dynamics GP 2013 payroll processing was interrupted during the final posting and can't release the batch or gain access to it - also didn't complete the payroll posting routines. Ran Select SQL statement against the company database around the following tables and they all have information. Does anybody know if running this clears the one hung payroll batch processing to finish it or does it clear the tables and they have to rerun payroll. This came from this KB. support.microsoft.com/.../851664

Delete DYNAMICS..UPR10300
Delete DYNAMICS..UPR10304
Delete UPR10200
Delete UPR10201
Delete UPR10202
Delete UPR10203
Delete UPR10204
Delete UPR10205
Delete UPR10206
Delete UPR10207
Delete UPR10208
Delete UPR10209
Delete UPR10213
Delete UPR10301
Delete UPR19900
Delete UPR19901

*This post is locked for comments

I have the same question (0)
  • Mick Egan Profile Picture
    3,561 on at

    The UPR10301 is the Batch Header Table.  Check the field UPRBCHMK in SQL, you might be able to reset to "0", and access the Batch.  Not sure if the Marked By user field comes into play, but might clear that column as well.

    Mick

  • Suggested answer
    sandipdjadhav Profile Picture
    18,306 on at

    Henry,

    Have you deleted these tables too? It's mentioned on same kb.

    Delete DD10100 --(Direct Deposit Employee Deposit Work) 
    Delete DD10200 --(Direct Deposit ACH Copy) 
    Delete DD10300 --(Direct Deposit ACH Cross Reference) 
    Delete DD10400 --(Direct Deposit ACH Header) - If this file is renamed or deleted, you will lose any builds in the generate ACH file window (Transactions | Payroll | Generate ACH file.) 
    Delete DD10500 --(Direct Deposit ACH Items) - If this file is renamed or deleted, you will lose any builds in the generate ACH file window (Transactions | Payroll | Generate ACH file.) 
    Delete DD10600 --(Direct Deposit Prenotes Completed) 
    Delete DD10700 --(Direct Deposit Exceptions)



    Thanks much
    Sandip
  • Suggested answer
    Sherlene Sorenson Profile Picture
    967 on at

    Henry,

    This script will clear out the payroll work tables that were populated during the Build and Calculate process. Generally it is helpful if there is a batch stuck or anything weird during the print checks process.  After this script is run and the CheckLinks process has been done (also should be in that KB you mentioned) the transaction batches used for the payroll would all be available to begin the process over. If checks really had printed and you don't want to void them or reprint, be extremely cautious that when you do the Build/Calculate and Print Checks again that you have exactly the same totals and check numbers as was used on the first time through, and print the checks to plain paper.

    It sounds like your client was already past the Print Checks stage and into the Posting process when the interruption occurred.  In a perfect world, when the posting process completes, the tables listed above in that KB would be empty. So in any case, that script is safe to run. (Be sure you have a backup before doing anything...)

    Since the interruption happened DURING the posting process, you really need to look in the tables that are affected by payroll posting, to see if they have been partially updated. If they have been partially updated, the decision needs to be whether to do "SQL Surgery" to fix up those tables, or remove that check run entirely and re-process it. This is a job for a very experienced GP Payroll/SQL skilled consultant, or Microsoft support.

  • Suggested answer
    Sherlene Sorenson Profile Picture
    967 on at

    Please be very cautious about deleting the DD tables. If an ACH file hasn't been created yet for a check run that was processed, the information to do that will be wiped out of these tables. I usually do not clear the DD tables unless there is a specific reason to do it.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans