Replacing Assets

You need to be familiar with the general rules on building CSV files for Bulk Data. See Setting up a CSV File|topic=Setting up a CSV File; document=Documents\Conquest III User Guide.docx.

The rules for replacing Assets are described in the documentation of the Replace Asset Function.

The Replace Asset function supports both the replacement of an Asset with another Asset or with itself, but both types of process cannot be in the same import file as the columns required are different.

Replace Assets on existing Assets

The import file to be loaded for this function must contain these columns, in this order:

•      AssetID
The Asset ID of the Asset to be replaced

•      ReplacedDate
The date of the replacement

•      Residual
Any proceeds from disposal. Also see note below.

•      AcquisitionCost
The cost of the new Asset

Replace Assets with New Assets

Replacing an existing Asset with a new Asset, works in much the same as importing an asset.  The process and file format is described in the section on Importing Assets, with the following additional fields:

•      Status
Must be Proposed to replace existing Assets

•      ReplacedAsset
The AssetID of the existing Asset, which the new Asset will replace

•      ReplacedDate
The date of replacement

•      Residual
Sale price of the old Asset

•      AcquisitionCost
Purchase/construction cost of the new Asset

Things to be aware of:

You are now able to set an amount to carry forward from the current asset value as part of the new asset value.  The value defaults to the residual value but the user can set this in the Proceeds / Residual Value field in the Replace Asset dialog.  This function only applies to the Replace function where the current Asset is maintained.

After the Replace Asset function is completed, the Asset maintains the amount carried forward in the Value column.  The Disposal transaction is modified to match this.

The column name that supports this in the csv file has changed from 'Proceeds' to 'Residual'.