admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-07-31 00:06:12 +00:00
parent 1b65059336
commit 7d8421c4af
1 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/8.0/ayanova/docs/svc-pms.md
View File

@@ -7,7 +7,7 @@ Notes for docs:
### Automatic date calculations
(Note: The very first time a Work order is generated from a newly saved PM it will take the exact values as entered by the user on the PM for all dates and transfer those to the first generated work order. Only after the first work order has been generated will the PM dates be re-calculated and updated for the **next** time it generates a work order in the process outlined below.)
(Note: The very first time a Work order is generated from a newly saved PM it will take the exact values as entered by the user on the PM for all dates and transfer those to the first generated Work order. Only after the first Work order has been generated will the PM dates be re-calculated and updated for the **next** time it generates a Work order in the process outlined below.)
All selectable dates on the PM are advanced relatively based on the next service date calculation:
@@ -21,4 +21,16 @@ If an date is left empty it will not be affected by this process so for example
### Service Date and Excluded days
When a PM is first created it will use the exact service date chosen the **first** time it generates the first workorder regardless of which day it falls on as it's assumed the user specifically wants that particular day for the first work order generated from that PM. Subsequent generate events will take into account the chosen excluded days.
When a PM is first created it will use the exact service date chosen the **first** time it generates the first workorder regardless of which day it falls on as it's assumed the user specifically wants that particular day for the first Work order generated from that PM. Subsequent generate events will take into account the chosen excluded days.
### Inventory handling
AyaNova removes inventory from stock immediately upon a Work order item Part record being saved and the same is true if the Work order is generated by a PM at the server automatically.
During the Work order generation from a PM, inventory levels are checked and if they are found to be insufficient the amount that *is* in stock is set on the Work order item Part record created (or zero if none are in stock) and a Work order item Part Request is automatically added to the Work order that is being generated with a quantity equal to the needed balance.
For this reason, it's helpful to set the "Generate before" setting on the PM far enough in advance to handle ordering in parts if necessary.
To avoid this situation entirely, AyaNova provides an Insufficient inventory warning notification which can be subscribed to and will alert the notification subscriber that at that moment in time there is insufficient inventory to fulfill an upcoming PM.