Automatic Costing Posting Off

shepherd

I have a client who operates a large database (alot of data and 100+ users) and performs many large transfers during the day (200-300 lines). They also have numerous branches where a high number of sales orders (2-20 lines) are processed. Automatic Costing posting is on currently and we are in the process of upgrading to version 4.

I have tuned the SQL server for transfer and sales order posting but I'm not getting the performance I need on transfers still, i.e. 100+ line transfer still take 90 secs plus and this causes sales orders to back up behind it. I'm looking for any advantage in improving this throughput. Part of the problem is the cost posting to the g/l that happens in a transfer. I have a number of process improvment ideas but what I'd like to place on the table again is turning off the Automatic Cost Posting flag and thereby a large part of the conflict between the large transfers and the counter operation can be removed.

If you have clients who have this off could you advise any negative impact on the business apart from the obvious one where the costs are not up to date until the post to g/l is run.

Thanks.

David_Singleton

Firstly talk with Finance. Its prtty rare that the accounting department will need to know Inventory valuation and atrue p/l at lunch time on Wednesday the 12th. They most likely want it monthly, or mayb weekly.

Cost posting can alsobe done by Inventory/business group, which make life much easier,but does not give the ability to then use navigate on Itemledger entries to the GL level. So checkif thatisneeded.

In terms of running cost posting batch, thisisgenerally a much better wayof doing things, since you can do cost adjustment first, and have more acurate numbers. One modI often make, is to date the GL posting the same as the Vlaue entry, so that Navigate works.

Personally I always advise clients to use batch posting, but nearly al clients want it live, with out realy having a good solid business reason for doing so.

ssingla

Also look in the analysis view. If there are too many analysis view and they are on update on posting the performance tends to be slow. This is more in case of 4.0 where we have analysis view for inventory sale /purchase. If Some analysis view can be tuned to be periodical update it might do the trick.