Adjust Cost batch run problem: blocked item error

Roelof

Hi,

On of our customers is trying to run 'Adjust Cost Iem Entries', but is getting an error regarding a blocked Item. Is there a way to fix that or to overcome that problem?

Roelof.

themave

unblock the item, run the report and then block again, no easy way, since it needs to make an entry for that item

Savatage

We have created a Discontinued (Blocked) Date field on the item table & Card.

OnModify of the Blocked field, when it's updated the work date is entered into this field (Discontinued date) or blocked (whatever you need to call it).

We have many items that come in then out & get discontinued every month.

Getting back to your question, by having this date I can filter on just the items that have been blocked since the last time we ran Adjust Cost....

Run the Report & then re-block the items again.

I created an "Item Maintanence" form where this can be done. Where Items with the date field <>'' and blocked = ''. Unless someone has an easier way - I'm all ears too!

jreynolds

This has been done in a recent release (it's in 4.00, not sure if it appears earlier). Codeunit 22 has been modified to not test the Blocked field of the item if called from 'Adjust Cost Item Entries'. It souldn't be too hard to bring these changes back to an earlier release.

ara3n

this is a quick fix I had to do for a client in cu 22

IF ItemJnlLine."Source Code" <> 'INVTADJMT' THEN
Item.TESTFIELD(Blocked,FALSE);

It's called in two places. Put the if statement above it, and you are done.




this is how it's fixed int 4.0

IF NOT CalledFromAdjustment THEN
Item.TESTFIELD(Blocked,FALSE);

The CalledFromAdjustment boolean is set through a new function
SetCalledFromAdjustment(NewCalledFromAdjustment : Boolean) which is called from adjustment routine.

Savatage

So is it the basic opinion that this was done just to give us more work to do?

I never changed it in case it was there for some "important" reason. But apparently not.

themave

that would be my guess, Many Navision routines where clearly written by a programmer who never ever worked at a business where Navision would actualy be used.

ara3n

That's why in another post, I had suggested that Navision themselves should get a new client for every new version of Navision, that uses every single functionality in navision and they should be on navision for 6 months to see the pain we solution centers go through.

Roelof

Thanks guys, for all your reply.