Finance | Project Operations, Human Resources, ...

Transaction Level Posting Interruption

(0) Share

Report

Posted on by P Aitken

We had a posting interruption on a PM Transaction level posting and when we go into PM Transaction Entry we get the following error:

pastedimage1671169776754v1.png_2D00_640x480.png

I freed up the stranded trx in the sy00500

Ran Checklinks on the PM Series

I no longer get that message but now get the following message when I go into Transactions->Purchasing-> Batches then

Unhandled script exception:
Index 0 of array 'VerifyBatchTotals' is out of range in script 'Batch_Lookup_Scrolling_Window SCROLL_FILL'. Script terminated.

I recreated the SY01500 by following Option 1 of Original KB number: 2316165

https://learn.microsoft.com/en-us/troubleshoot/dynamics/gp/errors-when-looking-up-a-purchasing-batch

I went in and we no longer get the error message but I'm worried we may run into problems as a result of this error. Is there anything else we should do? Or, should we restore to a backup and follow a different path?

Categories:

Microsoft Dynamics GP

All responses (2)

Answers (0)

Suggested answer

JanelleM on at

Like (0)

Report

RE: Transaction Level Posting Interruption

Hi,

If you are still getting a duplicate error after a posting interruption, it is possible the transaction record is in both the WORK and HIST tables. Transaction records can only be in one of these tables. If you do find the transaction in both tables, then you will want to remove the duplicate record. Normally, the duplicate record is the WORK table, but you will want to look at the data for this transaction to see what is listed. Also, make sure that the status in the PM00400 table does match the status of the transaction.

I hope this information helped.

Thank you,

Janelle

Microsoft GP Support
Richard Wheeler 75,730 on at

Like (0)

Report

RE: Transaction Level Posting Interruption

I would perform a backup, then using SSMS run DELETE [dbo].[PM00400] on your company database and then run check links again. You will get a lengthy report as it will rebuild for payables key master table(PM00400).

Here is an old note I wrote about this.

community.dynamics.com/.../pm-key-master-table-pm00400-rebuild-in-gp-2013-r2-still-an-option