Missing / NOT Returned or NEW the Asset is UNAVIALABLE

The system was coded to be very lenient towards Sites who did not initially embrace the full integration of the application’s modules. I.e. Asset Management while linked did not require use of the Shipping Module.

Well this can lead to challenges when the sites use their own “preferred” pieces of the code and expect the application to adapt to their practices. To meet our community’s rather expansive business practice (challenges) we have added another coding twist.

The code change is as follows.

If an Asset is placed on the Pick List for show “A” and that Asset does not return from the show, provided you are receiving Assets back and the Asset in question is not “checked” back at the time the Final Receiving Flag for the Project is selected and the Receive Items button clicked the Asset will automatically be made Unavailable in the db. This reduces your Unit Count by one on the V/E/S screen and avoids a customer from selecting that instance of the Asset until you change the Asset back to Available.

Keeping with our flexibility policy, you do not have to use the Shipping Module for this to work and in fact if you are happy with the way things are now and are not using the Receiving Module, continue as you are and the system will return the Asset to the V/E/S screen for selection based on the pre-set days after close of show that you have established for the Asset Type. However if you want to “interrupt” this automated function, preventing customers from ordering Assets that did not return, simply check the final Flag and receive the Project’s Assets back without checking the missing Asset as received and the system will do the rest.

BUT WAIT THERE IS MORE!

Allowing that you are using the Receiving Module here is what will begin to happen by the end of next week for Project’s “B”, “C”, where and Asset has been Included, when that Asset is flagged by the system through this new automated process or by a manual decision to flag the Asset Missing / NOT Received from Project “A”.

The system will look up any future Projects where the specific instance of the Asset is Included and send an alert Task to the internal PO of that Project. Additionally we now look across the system and make the Asset “Unavailable” on all screens in future Projects.

Of special note here is that on the Manage Load screen we insert the Unavailable icon but keep the Asset active so you can Remove it or change the instance pro-actively anticipating that the Asset may not be located in time for use on the Project. On a shipment’s Packing List screen we gray the Asset selection box out entirely. So you can work on the Asset but you can’t put it on a shipment when it has gone missing.

There is an accompanying change in icons with the above code.


The Blue Ball once indicating “NEW” has been replaced.

The circle/slash icon which has been in the system to indicate when an Asset is Unavailable will now appear in place of the ball. The change occurs on the Mange Load screens and has also been returned to the Receiving screen.

In addition it will appear for the first time on the V/E/S screen.

A New Asset was always an Asset that was Unavailable. Now that the system automatically moves a Missing / Not Returned Asset to the condition of Unavailable this new icon will indicate that an Asset is unavailable. It may have not yet been produced or maybe it is lost but in either case the Asset is UNAVIALABLE.