Skip to main content
Question

Serial number change results in accounting not balanced (again)


KennethP
Do Gooder (Customer)
Forum|alt.badge.img+4

Long story short, we are running 23R2 upgraded from version 8, with Weighted Average. Revaluation events cause SERREN+/SERREN+ to be not balanced. What seems to happen is at the first revaluation event that the system creates new M191 postings instead of all the old M3s. The result is that the accounting does not balance. M1 and M191 balances though. Removing the old M3s seems a bit unorthodox since they also have voucher numbers. Question:

  • Is it safe to remove faulty postings (thereby removing some of the sequence numbers for a transaction)?
  • Is this a known problem already? We have looked at corrected bugs in the upgrade script. However the upgrade script changes the posting control basic data from M3 to M191, but does not update old transactions.

4 replies

HONSLOCKLEAR
Do Gooder (Customer)
Forum|alt.badge.img
  • Do Gooder (Customer)
  • 4 replies
  • February 26, 2025

We just had the same problem. I noticed that your comment “again” makes me think this happened to you at least one other time. Did you figure out how to fix it?

 


HONSLOCKLEAR
Do Gooder (Customer)
Forum|alt.badge.img
  • Do Gooder (Customer)
  • 4 replies
  • February 27, 2025

We contacted an IFS senior analyst and the only thing we could do was write an sql script to delete the transactions in error from mpccom_accounting_tab


KennethP
Do Gooder (Customer)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Customer)
  • 10 replies
  • February 28, 2025

Yes, we had to do that too. It’s been a while, so when I look at the data repair we did I almost don’t understand it anymore. But basically it looks like our strategy was to:

  • Adjust the (new) M191 postings with the values from the M3s, both on debit and credit side, so everything is in balance
  • After that, update the M3 postings to the use M191 as transaction code. This is to prevent the whole thing to happen again.

I guess you can do things different ways, but as I remember it you don’t want any M3s left in there, since that will trigger new errors.


HONSLOCKLEAR
Do Gooder (Customer)
Forum|alt.badge.img
  • Do Gooder (Customer)
  • 4 replies
  • February 28, 2025

For us, we didn’t want the M191 postings. But we had to find all of the unbalanced transactions and delete them. The only reason we could do this was because the value of the transactions was less than $1USD. If it had been for a lot more money, we probably couldn’t have gotten away with this.

 

This script helped us find the unbalanced transactions. 

SELECT *
FROM mpccom_accounting_tab a
WHERE status_code = '99' AND trans_reval_event_id = '85450';


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings