This commit is contained in:
2022-02-08 01:33:39 +00:00
parent f9049cb32b
commit ddf6b64dc7
5 changed files with 52 additions and 0 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.8 KiB

View File

@@ -715,6 +715,24 @@ Enter the quantity used here. When the work order is saved the quantity will imm
If this item is later deleted and the work order saved the inventory is immediately adjusted and the quantity entered here is put back into inventory.
##### Insufficient Quantity validation error
If you save this work order item part record and the AyaNova server sees there isn't enough inventory available it will return a validation error with a button to request more parts be ordered:
![Work order item parts insufficient quantity](img/svc-wo-parts-insufficient-quantity.png)
Here you can see that the user entered 500 as the Quantity however there were only 85 in stock at the moment the work order was saved. The green link prompts you to create a [Work order item part request](#part-requests) for 415 more of this part.
You have two choices here:
- Request the part by clicking on the "Request 415 more" green link and save the work order to trigger a request for 415 more which will flow through to the inventory system where it appears when the purchase orders [Part requests](inv-purchase-orders.md#part-requests) feature will populate it on to a purchase order. Additionally the request may trigger a notification to any subscribers to the Object created -> work order item part request event if they have [subscribed](home-notify-subscriptions.md) to that event.
- Change the Quantity to 85 or less and re-save the work order.
If you request the part, a work order item [part request](#part-requests) record will be created in the local work order and displayed in the work order item Part Requests section below the work order item Parts section:
![Work order item part requests](img/svc-wo-part-requests.png)
#### Suggested quantity (legacy)
This field will only display when a work order has been migrated from version 7 of AyaNova and contains parts not yet consumed in inventory.
@@ -835,6 +853,36 @@ You can also refresh the page to abandon this and any other changes made locally
Until the work order is saved the items are not actually deleted.
### Part requests
![Work order item part requests](img/svc-wo-part-requests.png)
The work order item Part Requests section is where any previously [request parts](#insufficient-quantity-validation-error) are displayed.
This section is created automatically and is not editable by the User directly.
The user can delete rows in this section provided the part has not yet been ordered on a [Purchase order](inv-purchase-orders.md).
There is no edit form for Part Requests, all their information displays in the Part requests table.
#### On order
Once a Part request has been added to a Purchase order it will display additional information in the table:
![Work order item part requests on order](img/svc-wo-part-requests-on-order.png)
Here we can see there is a link to the [Purchase order](inv-purchase-orders.md), the date it was ordered and the expected date it will be received based on fields entered in the Purchase order.
#### Received
When the part is received on the purchase order, it will display as received in the Part request table:
![Work order item part requests received](img/svc-wo-part-requests-received.png)
If the service tech had subscribed to the _Requested part received_ [notification](home-notify-subscriptions.md) they would also receive a notification the moment it was received.
Now the user can update the part record from 85 to 500 (or add a new line for the 415 additional) and complete the service.
### Labors
![Work order item labors](img/svc-wo-labors.png)
@@ -1287,10 +1335,14 @@ This field is a [date time field](ay-start-common-controls.md#date-and-time) con
This field is is used to enter the point in time when the Unit is expected to be returned from the repair service.
If a user has subscribed to the _Outside service overdue_ [notification](home-notify-subscriptions.md) they will receive a notification if this date passes without a return date being entered so they can follow up.
#### Date returned
The point in time when the Unit was received back in your shop from the repair service.
If a user had subscribed to the _Outside service unit received back_ [notification](home-notify-subscriptions.md) they would also receive a notification the moment it was received.
#### Tax code
[Tax](acc-tax-codes.md) to be charged for this Outside service.