RM40401 Sequence number getting overwritten

(0) Share

Report

Posted on by DominicBeland

330

HI,

One of our client is having an issue where the RM sequence number gets overwritten with a new number. This happenend 3 times since the beginning of 2018. We suspect there is a a sequence of events that causes the sequence number to be overwritten.

There is a third party that generates it's own sequence number and when it goes into the RM, it usually just does as if a user typed a totally new number in the Document Number field.

Usually this doesn't affect the RM40401 numbering sequence. But it looks like there is something that forces the new numbering. Has anyone encountered such a problem in GP ?

*This post is locked for comments

All responses (2)

Answers (0)

DominicBeland 330 on at

Like (0)

Report

RE: RM40401 Sequence number getting overwritten

My problem is that I'm unable to recreate the issue.

My client is generating thousands of invoices per month with the third party. why is there 1 invoice out of them that forces the new numbering?

Looking at the SQL logs from a trial software that the client won't buy we saw that the Sequence number in the RM40401 went from 14012 to 14013 back to 14012, then to 14013 back to 14012 and then BOOM 2106509 (new numbering)

It looks to me a sequence of manual events.

I tried to put a Trigger on the RM40401 but this causes GP RM transaction window to cause an error as soon as it looks for the next number.

Is there a way to create a trigger without causing the error in the GP window?
Frank_Heslin 895 on at

Like (0)

Report

RE: RM40401 Sequence number getting overwritten

In a test environment I would try disabling the 3rd party product & see if that resolves the issue. If it does resolve it, then I would contact the 3rd party vendor to get them involved.

If that doesn't resolve the issue, then I would run a trace while processing a transaction to get a log file to review.