IC Setup Options > Costing > Cost Items During set to Posting?

Thank you for the response. I am not familiar with this option but will check it out tomorrow Australia time. Could this also be the reason why posting an order seems to take a long time, i.e because it is doing additional background processing? And what are the alternatives to Cost Items During - Posting? Thanks again for your time.

Found the answer to my question - Cost Item During Posting or End of Day. I will do some testing tomorrow. Thanks

Day end Processing
Posting = data corruptions in OE and PO. There are bugs in this process, seen this at many clients, bad option to use.

Ditto. Don't use it if you have more than 1 user in the system.

OK, thanks. So if Cost Items During set to 'Posting' might be causing these errors and the alternative 'Day End Processing' can cause corruption, is there anything else that I might be able to try to reduce these errors?

You misunderstand. "Costing during posting" is the only problem. Costing during Dayend is always fine.

OK, great. I understand now. Would you also recommend setting create G/L transactions and audit information to Day End Processing. That is also currently set to Posting

That's not quite the same thing. Create GL transactions is either day-end or on request, and it should be day-end, and "creating and posting a new batch".

Apologies Jay, I think I got the terminology wrong. I meant to say 'create subledger transactions and audit information during' This option is on the same tab IC Setup Options > Costing. It currently set to Posting but the alternative is Day End Processing

OK, got it. I will discuss with the customer and give these changes a try. Many thanks Jay and 49153. You have been a great help.

We also recently ran into problems with a customer who strongly prefers Costing During Posting, which results in fewer residual costs for them. When Day End failed shortly after upgrading to version 2017, I was looking for something to back up my recommendation to switch to Costing During Day End -- but I was surprised to find Stephen Smith advising otherwise! smist08.wordpress.com/.../. It's an old post, but still informative, as the program hasn't changed much.

In my client's case, Day End would occasionally fail in Version 2017. We could replicate the conditions that caused it to fail, and found that it was only a problem with Costing During Posting. We traced it to a specific .dll from an interim (hot fix) Product Update before the official 2017 PU1 came out. Once we replaced the problem .dll with the original, we were able to go back to Costing During Posting. When the official PU1 was released, we installed that, and still fine. They have 25-35 users in OE/IC/PO every day.

So -- if your client still pushes for costing during posting, get back to me and I'll give you more details of what we found.

Hi Wendy - I'd love to hear what you found.

Our experience with IC costing on posting has been negative: OE and PO transactions are being lost when multiple users post transactions at the same time. This error was replicated and recreated on demand, i.e. we proved it without any doubt. The problem persists in newer versions and has not been resolved.

49153 - can you tell us how to replicate the problem with lost transactions? I'd like to do some further testing for this client.

Have 2 or more people post a PO receipt at the same time - that will crash at least 1 of them. Same with OE shipments and invoices. PO purchase orders and OE sales orders do not have any effect since they do not generate accounting entries.