this batch is being posted

[waely]

hi,
my PC crached during creating a payroll batch file. the status of that batch was Marked instead of being available. I set the marked status in SY00500 table to 0 and delete the related record from SY00800. now I have the batch status set to printing and I can't inactivate employees and do some other functions because the system is still thinking that the batch is being posted.

any suggestions. I'm running win98 and great plains 5.

thanks

 

[klewis10367]

Update SY00500 set BCHSTTUS=0 where BACHNUMB='Input Batch here'

 

[waely]

already did and still showing status as printing.

 

[barbola]

Can you open any of the transactions in the batch? If so, create a new batch and save the transactions to the new batch and then delete the one that is marked as printing.



Thanks!
Barb E.

 

[waely]

I'm trying to delete that batch but I can't find it. not sure what table has that batch in sql....

thanks

 

[waely]

FYI. Neither SY00800 nor SY00500 has that batch.

 

[waely]

does anyone know where my batch status is still says Printing? there is no record for this batch in SY00500 or SY00800?

thanks

 

[waely]

I'm sorry. I meant to say why my batch status not where.

 

[klewis10367]

Check the UPR10301 table. Make sure the value in the UPRBCHMK field is 0, for yor batch.

 

[waely]

my batch wasn't in that table. however I made sure all UPRBCHMK values are 0. not sure where else to look....

thanks

 

[klewis10367]

I do not know if this will help but it might get your batch back so you can delete it( This is a Great Plains tk.:

I am on eEnterprise for SQL Server and have a batch that is marked for posting in Payroll which states checks are currently being printed. How do I unmark the batch?

The following error messages may also occur to indicate the Payroll batch is stuck:
Error - "Open operation on UPR_Temp_Post2 has incorrect record length"
Error - "Remove Range Operation on Table ddDeposits has caused known error 2"
Error - "Batches with zero transactions cannot be marked"
Error - "Another user is performing a check run"
Error - "UPR_Work_Post failed accessing SQL data"
Error - "The employee record cannot be inactivated or deleted Pay run is in progress for this employee"

Also, an Open Operation, Get/Change, or Save Operation error may occur on one of the following files to indicate the Payroll batch is stuck:
UPR_WORK_MSTR
UPR_WORK_MSTR_Detail
UPR_WORK_HDR
UPR_WORK_Pay_Type
UPR_WORK_Deduction
UPR_WORK_Benefit
UPR_WORK_State_Tax
UPR_WORK_Local Tax
UPR_WORK_Check
UPR_WORK_Post
UPR_Flat_Tax_Records
UPR_Account_Cache

Resolution

Perform the following steps to eliminate any of the errors mentioned above:

1. Run the following script in Query Analyzer or the Support Administrator Console on MSDE against the COMPANY database. Note - The first two lines in the script will delete the contents of the activity files in the Dynamics database and the rest of the files will delete the contents of the work and activity files in the Company database.

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

2. Open Windows Explorer and select the Temporary directory (C:\Windows\Temporary). Delete the files in the directory that begin with "TNT" and delete the files that have a "tmp" extension.

3. If you have Direct Deposit, run the following scripts:

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)

4. In Dynamics, go to File | Maintenance | Check Links. Choose Payroll for the Series and insert the Payroll Transactions. Process this. You will get errors on the error log which you can ignore as the Check Links process is re-attaching the Batch ID to the existing transactions.

5. Build the check file again; all batches will still be there.

Note:
If you have recurring batches and you delete the UPR10301 above, when you run check links the frequency will default back to single use. Before posting the batch, you will need to go to Transactions | Payroll | Batches pull up the recurring batch and change the frequency to something other than Single.

This article was TechKnowledge Document ID: 21840

 

[barbola]

Are there any locked sessions in the TempDB? you can delete DEX_SESSION and DEX_LOCK if there are. But careful not to delete any active sessions.

Checklinks on your sales table may also recover your batch so you can delete it.


Thanks!
Barb E.

 

[waely]

thanks for the info. I deleted all records from the above tables but I still see my batch "UPRVC00000296" in my list of batches marked as Printing. I did check links and got no errors. I logged off and logged back in and it's still there.
if I double click on the batch I get this message: " the batch is being posted" and if I try to inactivate an employee from a different PC I get: "there are unposted transactions for this employee. the employee record cannot be deleted or inactivated".

so the problem is still there.
any other ideas?


thanks much.

 

[waely]

barbola, where is the TempDB and what table should I look for?

thanks

 

[klewis10367]

Are you seeing this batch in the Financials or Payroll. With that batch name it looks like it has posted in Payroll and is stuck in the Financials.

 

[waely]

the batch is in the financial not in the payroll. I asked my accountant and he said it's in the general ledger.

thanks

 

[barbola]

First, in the Dynamics database, each active user in the Activity table has a session ID. If there is a session in the DEX_SESSION table in the database called TempDB (in SQL) you can delete that session if it is not in Activity.

There is more information on Customer source about this.



Thanks!
Barb E.