The Asset Import Reports for equipment, locations, systems, and repairable spares include Transaction Date and Transaction Reason columns, which work together with the Status field to define the asset’s most recent operational state. These fields determine how the system records the latest status change and ensure that Asset History remains accurate and chronological.

 

How Status, Transaction Date, and Transaction Reason Work Together
When importing asset records, the system evaluates the Status value to determine which additional fields are required and how the update will be applied.
•     Status = Down — A Transaction Reason and a Transaction Date are required.
This indicates the asset has gone out of service, and the system needs both the date of the event and the reason for the downtime to create a valid history entry.
•     Status = Up — A Transaction Date may be entered but is optional.
This reflects that the asset is operational. If a date is provided, it becomes the timestamp for the asset returning to service; if not, the system uses the import timestamp.

 

Rules for Updating Asset Status Through Imports
Asset Imports can only update the most current status of an asset. The system does not allow historical entries—defined as any transaction with a date earlier than the most recent entry already recorded in the Asset History.
This ensures:
•     Asset History remains chronological.
•     Imports do not overwrite or insert events out of order.
•     Only the latest operational state of the asset is updated through the import process.

 

Practical Implications for Data Management
•     Imports are best used for bulk updates to current asset conditions, not for backfilling past events.
•     If historical corrections are needed, they must be entered directly through the Asset record rather than through an import.
•     Ensuring accurate Transaction Dates during imports prevents conflicts with existing history and avoids rejected rows.