In Inventory Module, we would be very happy if we were able to edit the grid columns in the Costing Tab. We would like to add the column "Location" to this tab, and are not able to. Reasons we wish to do this are quick to explain if someone is right in front of you, but would make a long explanation on paper, so I won't go in to the why of this request.

But is it possible to do? Also on the costing tab, we are shown the Receipt number of the goods coming in, which is wonderful. The problem is that when an adjustment is done to that "lot", the receipt number disappears. Any way to change this so that adjustments can be done to a "lot", but the receipt number stays?

Thanks very much, as always, you guys are wonderful!

The problem with this is Adagio only keeps one common cost for all locations rather than separate costs by location. I know that cost by location is on the wish list but I'm not expecting it anytime soon.

Not sure why the receipt number in not retained when an adjustment is posted.

Doug is correct. Cost is not stored by Location in the data, so even if you could edit this grid, Location would not be available for inclusion. We cannot change this and still remain compatible with Accpac Plus IC.

If items are simply shipped from a FIFO/LIFO costed item, the Receipt information on the costing lot is maintained.

If other transactions (adjustments, stock transfers, merging costing lots after posting receipt #6, etc) that affect costing are performed, the Receipt number and date disappear because this was the behaviour in Accpac Plus IC, and the initial design of Adagio was to replicate the behavior. One could argue that the average cost on the costing lot is not the same as the receipt.

Would it be useful to not ever lose the receipt information on the lot (with the exception of when costing lots are merged)? Or perhaps are there scenarios where having the Receipt info should be removed?

Andrew,

Could you give a short description of what OEF files do? We have a workstation that fails to find existing data with the F6 search function and I am searching for a reason as to why.

David

I assume you meant to post this note on a different thread...

OEF### files are the saved SmartFinder results files. When a user performs a SmartFinder search, the information is remembered until the application is closed. It is these files where the search results are saved. There are control files OEFCTL'I and OEFCTL'R that keep track of all the results files.

Failing to find records within a Smartfinder search is different than receiving an error message. It may be that the defined search is not properly defined and thus won't find what you think it should. Especially if you are using AND and OR and not getting the syntax correct.

Sorry....You are correct...wrong thread.

David