2,010
There is a KB article addressing it but it asks you to delete UPR tables which sounds dangerous to me. What's the best approach? http://support.microsoft.com/kb/865813
*This post is locked for comments
Delete statements delete data in tables. Drop table statement delete the tables. You would run these statements against the company with which you are having this issue. In the other statements that begin with Dynamics, that is the full table name so it will run against those tables in the DYNAMICS database.
To confirm, do those delete statements clear data or do they delete the table? And they would be run against the live dba, except for the first two that have 'dynamics' in the statement?
These are just the payroll work tables. No harm in clearing. It could be that the employee you are trying to delete is part of an existing batch. You could try removing the build and then find the employee in the batch and delete it.
Here is a list of the actual tables involved.
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
Plus these if you use direct deposit
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)
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
