This document applies only to the following language version(s):
The new Install/Remove asset logic in Maximo Asset Configuration Manager 126.96.36.199 fixes a problem where transactions entered out of chronological sequence caused the transaction history to be corrupted.
Users of Maximo Asset Configuration Manager can install or remove asset transactions out of chronological sequence. Maximo Asset Configuration Manager 188.8.131.52 introduces a new logic to ensure that the transaction history always reflects the correct sequence of events whenever new transactions are specified.
Each asset transaction performed by the Install/Remove action or the history modification process now includes a Type value associated with it. The Type value is derived based on the type of transaction and related transactions. Transaction records are compared with associated transactions (against the same asset and related assets or positions) and the Type value of the transactions that are affected is updated.
The Parent History, Child History, and Position History subtabs in the View tab of the Assets (CM) application display the type of transaction in the On/Off type column.
The types of transactions are:
- N (valid On): The installation (On) date of the transaction is a confirmed date, which means that a positive transaction happened that did not require the subject asset to be moved from an existing parent asset (known as the "donor") to a new parent asset (known as the "receiver"). When a type value of "N" is displayed with both an On and Off date time, the Off date time is an assumed transaction.
- F (valid Off): The removal (Off) date of the transaction is a confirmed date. When a type value of "F" is displayed with both an On and Off date time, the On date time is an assumed transaction.
- B (both On and Off are valid): The On and Off transaction dates are both confirmed.
When a new transaction is specified, the history records are changed to reflect the new situation.