Friday, May 27, 2011

No good deed goes unpunished.

Not to whine….but. My little fingers are bloody stubs, trying to catch up on all the great updates from Cliff & Naveen’s kitchen.

So I send out a wonderful “Good News” blog about automated Missing Not/Returned Assets and I am immediately swamped with intelligent follow on questions.

One of our dear readers writes concerning this topic:

"The one area that wasn’t covered was the eventual receiving of asset gone missing (and now unavailable). It was my understanding that once the asset was received, the system will automatically move it back to available. Can you please confirm this?"

Yes dear reader the system will in fact go back through all future Projects and update the Asset’s uses that are still in place.

This does call attention to one other fact.

The Asset should be Received on the Project where it was reported Missing Not / Returned. As our db keeps a History of Damage codes should you leave the missing Asset on a future Project ( remember you can’t get it on a Shipment) but for some strange reason Receive it back on that Project it will update all future Projects but leave the Asset Missing NOT / Returned on any prior Project.

You’ll of course see this when you run the now famous ALL Assets NOT Returned report and can correct it. But try to avoid the needless confusion.