This commit is contained in:
@@ -124,7 +124,7 @@ The service bank feature has not been ported to AyaNova 8 as it does not appear
|
||||
|
||||
### Inventory
|
||||
|
||||
To ensure the inventory balances match, all parts are initially migrated to v8 with a billion in stock quantity. Then all inventory related objects are migrated such as Purchase Orders, Inventory adjustments and Service Work orders. Finally at the end of migration adjustements are made to the v8 inventory levels to bring the quantity on hand into balance with the v7 quantity on hand for each part.
|
||||
To ensure the inventory balances match, all parts are initially migrated to v8 with one billion in stock quantity. Then all inventory related objects are migrated such as Purchase Orders, Inventory adjustments and Service Work orders. Finally at the end of migration inventory transactions are made to the v8 inventory levels to bring the quantities on hand into balance with the v7 quantity on hand for each part. In AyaNova 8 inventory is consumed the moment a Part is saved on a work order which differs from v7 where inventory is consumed when a Part is set to Used in service on a work order. For this reason inventory totals will be lower in v8 than in v7 due to any work orders migrated that have not had their parts set to Used in service in v7.
|
||||
|
||||
#### Inventory adjustments
|
||||
Inventory and Serial numbers work differently in v8; Inventory adjustments can not be migrated with their original entry dates as the new v8 inventory "blockchain" system does not allow entries out of order so they are migrated as Inventory Transactions in v8 and the description of the transaction is named in this pattern: `v7Adjustment {v7 inventory adjustment ID number} {v7 adjustment "reason" field} {v7 adjustment "Date Adjusted"}` For example "v7Adjustment 45 Store stock opening inventory adjustment on 2005-11-27 10:50:53 AM".
|
||||
|
||||
Reference in New Issue
Block a user