Sage 100

MAS90 4.5.1 duplicate posting in DTR from Sales order invoices. Sage has discovered a bug in the update process that results in duplicate postings in the DTR. The DTR is in balance so it can go unnoticed. Also, it is random so hard to spot. Workaround is to preview the Sales journal, say NO to update and then print the Sales Journal. They are working on a hot fix. My customer found it when the AR TB did not match the GL AR balance. Sage says a couple of other customers have reported it.

SCHEIST!

So what's the better release for new customers, 4.40.07 or 4.5.1 ??

Alan - was there supposed to be an attachment? If so can you PDF? When I opened it was blank. Is there a KB PER on this? Thanks!!!

I don't know of a KB, yet. I reattached the email that Shelly from Sage support sent to me as a .pdf.

Thanks - nice catch. This is scary combined with the other issue of receipt of goods where on backorder items were being removed.

Which is why we don't rush upgrades. I'd rather YOU guys find all the 'scary' issues... ;)

Alan, the PDF attachment didn't upload. Can you edit your post and try again? This issue was posted on The Community a couple days back.......... I hope this is a HOT fix!!!!!!!!!!!!!!!!!!!!!!!!!!! Therese, C'mon in. The water is GREAT!

Preview the Daily Sales Journal. Answer No to print the other reports (Gross Profit, Sales Recap, etc) Print the Daily Sales Journal as normal as well as all other subsequent reports Answer Yes to update Print the Daily Transaction Register it should reflect the correct detail and total information. Engineering is working on determining the cause of the duplication so they can fix the issue.

Anyone know how prevelant this is? I' have an upgrade scheduled for this weekend on a LARGE client. They need to upgrade to install and use the latest version of Sage CRM - I'm now haveing second thoughts

At this point, we have issues pending with PO's (backorders), SO's (slow SO printing), Invoicing (Duplicate DTR), issues with duplicate printers, I have basicly told my clients that they are on hold for upgrades until I see some resolutions to these problems.

4.40.08 scheduled for 12/20 (Next Tuesday). Stay tuned...

Hopefully, v4.5.2 will be release simultaneously.

Amazing! After reading the PDF, it brought back the memory of a similar issue encountered while beta testing v4.4. In PR, if you printed the payroll transaction register, it would NOT update to the general ledger and all the entries were LOST! Now if you PRINT, the entries will double.

Are we sure that this issue is fixed in PU2 for 4.50? I don't see it in the Release Notes and I cannot find anything about this in the KB.

I don't think this one is fixed yet - it's the PO one that is fixed. (Definitely - I tested.)

I had someone on my email list send me this update from Sage regarding the SO issue: I apologize for the delay. I was out last week on vacation. As I mentioned in my voice mail this morning, update 2 was already in final testing for release when this new issue was reported to Engineering. It is currently scheduled for update 3. We are hoping to provide the client with a separate fix prior to the update 3 release. If/When that occurs, we will request a pre-release agreement to be signed by the client. I will continue to keep you updated on the status of this case. If you have any questions, feel free to email or call me directly.

I have a customer experiencing this now. I suppose we don't know when PU3 is coming out?

Spent much of my Sunday finding and correcting this for my one and only 4.50 client. How relaxing.

So is this happening for all v4.5 installs or just the lucky few. Does anyone know what the trigger is for the client to be on the wrong side of the update?

Just to give you an idea - client has 2 divisions who both post invoices daily in at least 2 batches entered by 2 different people. Since Nov 18, one division had 11 batches with errors, the other had 12. Some batches had only 1 invoice wrong, but some batches had more than 1 invoice that double posted. It's a bitch to find them, since they also may have similar parts on the same invoice with the same qty and price and cost, so you can't assume that if you see the same posting twice, it's an error.

And the invoice posts correctly to the AR History?

Yes - I see no issues anywhere else. AR History is how I had to manually figure some of them out - as to whether they were an issue or just multiple same price/qty/cost items.

When you refer to batches, is the batch feature active?

Yes

I wonder if this is a factor. In all of my v4.5 installs, the SO batch entry is off and none have reported this issue. Alan, what about your client?

Just verify that your clients are matching their AR to their GL - if they're lazy, they're not going to notice the error until the auditors give them funny looks.

According to Sage they are still trying to determine the cause. Also, it is sporadic so if you try to test it with a couple of invoices they may post fine. Previewing first and then running it again seems to correct it so it is a decent work around.

thanks. Can you verify whether your client is utilizing the batch feature? Are you updating from the preview or just previewing it first THEN printing (to generate the PDF) then updating?

Lori Maloof just emailed me that they still have no resolution but they have escalated it. I would have hoped they would have escalated it before now, but anyway, that's the latest today. (IT's a freaking accounting package making fictitious (sp?) postings to GL! How much worse can you get?)

I'll ask again, does anyone have this causing issues at a client that is NOT using SO batches?

@BethBowers @alanniergarth Is there a KB# on this so we can find a report in the KB?

Jeff - my client is also using batches. FYI

Well, if everyone that is having problems is processing with SO batches, this might be something to try to rule out...........

Anyone have a PER on this or is the issue in stealth mode at Sage?

Here is Sage's KB Entry: http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=540417

Jon Reiter over at DSD is looking at this -- if you have been impacted and want to talk to him to explain the steps to reproduce give him a call -- 619-683-9900

I love the ""Allow the incorrect posting to the General Ledger and enter a Manual Journal Entry"" in the KB....

If Sage wrote KB entries for WebMD: Subject: Getting Shot Results in Dying PROGRAM ISSUE ** THIS INFORMATION HAS NOT BEEN VERIFIED ** Steps to Duplicate: 1. Have someone shoot you with a gun. 2. Die. Possible Workarounds: 1. Dodge bullet. 2. Get hit by the bullet, but have a doctor remove bullet before you die.

Wonder how many people they'd wound attempting to duplicate the issue?

How many people do they wound now by releasing software with bugs in it like G/L entries that double?

Sage has the gun. They have the victim. They just cannot duplicate the person dying.

If any of them had an accounting background they would understand that this is huge but since there is a workaround they probably don't see it as that critical. Problem is that since the dtr is in balance the customers don't even know there is a problem, let alone to use the workaround. I spoke to a customer yesterday who just saw the problem and has been running for over 2 months. He said he had already sent financial statements to his bank - he was ready for a breakdown.

Umm, don't they ever balance the AR TB to the GL?????

I thought the same thing but you've been doing this long enough to know that a lot of people don't except quarterly or yearly if at all.

I once had a client who did reconcile the A/R to the G/L ... and if it was off, he made an adjustment to a balance sheet account (not the A/R account). If A/P was off -- yep, the adjustment went into the same balance sheet account. When inventory was off, same balance sheet account. When we finally got to them, we questioned what this account was for. The bookkeeper said that this was an ""adjustments"" account. It just went up down every month ... year after year. The company's accountant never caught or questioned it.

Per Elliott of Sage: "" We have now been able to duplicate the issue which brings us closer to a resolution. It appears to be caused when there is a wash of GL Accounts such as the Inventory Account and Cost of Goods Sold Account. We will keep you posted!

Doh!

Progress! I am sure they have their TOP Dogs on the hunt!

Dogs? You mean as in plural?

Sage have this explanation posted in the 4.5 PU area -- though it says the actual software fix is coming soon -- http://reviews.cnet.com/smartphones/motorola-electrify-u-s/4505-6452_7-35016711.html

Or go to http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isResolutionConceptID=540417 if you don't want to read about a phone. ;)

oops - tx

Here is the latest update from Sage: ""We have traced the issue down to file pointers, which is beyond what we had communicated earlier. Our initial changes have produced favorable results. We are closely reviewing the code to see if any other scenarios could be affected and should be able to provide you with a target correction timeline next week.

Per Elliott of Sage: "" We have now been able to identify the enemy and it is us which brings us closer to a resolution

According to Diane Coffman (Sage) on LinkedIn about 1/2 hr ago: ""We hope to have a fix available for the DTR double posting from Sales Order later today."" http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=88373187&gid=1644357&commentID=65790038&trk=view_disc&ut=1lLgn_1RX7Bl41

http://support.sagesoftwareonline.com/mas/query/index.cfm?action=tipdetail&tip_id=1926 from https://90minds-com.socialcast.com/messages/8777020-sage-mas-90-and-mas-200-support

Isn't there still a bug in PO that is causing major issues still? Or is this the ""all clear"" for those brave v4.5 upgrader souls?

Let the upgrades commence.

way to stay on top of this everyone! the group comes through again!

This is happening to one of my clients- just randomly on typically one invoice a day. Has anyone heard of a resolution yet?

What version? I believe this has been resolved in one of the updates.

It was addressed in product update 3: In Sales Order Journal Update, the Daily Transaction Register no longer double posts invoices when the journal has been printed and updated in the first pass. 7 DE 98228 PER 112734 Resolution ID 540417

Opps. I unhid all the comments and have found the happy hot fix. Yay 90 minds!