11. Assets
Menu mapping: Products/ Assets / Assets
Assets are a sub type of stockable product. However the need was expressed to be able to track asset type products on an individual basis, and therefore there is a specific data sheet, an Asset Form, which can be created for each asset type product managed in the system. Currently there are no specific features for assets developed by Finance (to track depreciation of assets etc). Please refer to Finance documentation.
Asset forms represent master data records. A Unique reference “Asset code” is automatically created for each new Asset form, but reference can be modified before saving. Asset form must be linked to a product which is an Asset.
Several warehousing transactions in Unifield require an asset code to be entered in order to process the lines/transaction. However, where this reference is mandatory, it is mandatory for the line, which may contain product quantity of more than one. It is not mandatory for the line to be split into number of lines of quantity. There is no consistency check on previous use of Asset reference. Asset forms can be synchronised if contained within transport documents (SHIP & OUT).
It is mandatory to have an Asset Form reference for Asset type products in the following transactions (when products are entering or leaving the instance): Incoming Shipment, Pick/Pack/Shipment transactions, Delivery Order and Consumption report.
Asset events
Menu mapping: Products/ Assets / Assets events & follow up
Status or move changes of the asset can be registered as asset events. Any Asset event must be related to an asset form. There are no automated events, as these must be created manually. Asset events are linked to the asset form.
For Event type these options can be selected:
Reception, Start Use, Repairing, End Use, Obsolete, Loaning, Transfer (internal), Donation (external), Other
Current status of the asset can be:
In Use, Stock, Repair
Direct Reports / Exports
Asset form
12. Scheduler Range days for Purchase documents
Menu mapping: Administration / Companies
The planning horizon for which procurement documents will be generated is set as 80 days by default, and this setting is defined at the point of configuration for each instance. This means that if the requested delivery date (RDD) on IR or FO is more than 80 days in the future, the relevant document (i.e. PO or Tender) will not be created until the RDD falls within the planning horizon. It is possible to change the scheduler range days to a different value.
