This commit is contained in:
2022-01-31 18:36:24 +00:00
parent 7dc310605f
commit 6832ad7a3d
2 changed files with 96 additions and 18 deletions

View File

@@ -40,11 +40,11 @@ When a Customer is no longer required it should be set to inactive by un-checkin
## Customer data table
The Customers [data table](ay-start-form-data-tables.md) lists all the customers available and access to data table [common menu options](ay-start-form-data-tables.md#common-menu-options).
The Customers [data table](ay-start-form-data-tables.md) lists all the customers available, provides the '+' link to create a new customer and provides access to common [data table menu options](ay-start-form-data-tables.md#common-menu-options).
## Customer edit form
The Customer edit form contains all the [standard edit form](ay-start-edit-forms.md) functionality and contains the following fields:
The Customer edit form provides all the [standard edit form](ay-start-edit-forms.md) functionality and the following fields:
### Customer tab

View File

@@ -1,28 +1,106 @@
# INV-POS Placeholder
# Purchase orders
[UNDER CONSTRUCTION]
#b4beta not completed yet
The Purchase orders [form](ay-start-form-overview.md) is part of the [AyaNova inventory system](inv-part-inventory-transactions.md#how-inventory-works) and is availabled when [inventory is enabled](adm-global-settings.md#use-inventory) in AyaNova.
## OVERVIEW
Purchase Orders are used to:
Purchase order entry screen available when "Use inventory" is selected in Global settings.
- identify the quantity of [parts](inv-parts.md) and the the price for those parts that you want ordered for inventory
- restock the [required minimum quantity level](inv-part-stock-levels.md) for parts that have gone below their minimum required inventory levels
- fulfill [part requests](inv-part-requests.md) for workorders and track the connection between the work order and the purchase order
- automatically [notify](home-notify-subscriptions.md) users that the parts they have requested to complete a work order are received
## Inventory in AyaNova
## Authorization Roles required
The AyaNova inventory system is "live" and affected instantly when a PO or Work Order are saved with any *changes* of the Received or consumed quantity (respectively) for a part. This means that when you receive 10 parts on a PO they will be available for use immediately on work orders etc. If the PO is then edited to change the 10 to a 5, the inventory is immediately updated to remove the 5 that are now not received.
This form is available to User's with the following [roles](ay-biz-admin-roles.md):
If a work order consumes a quantity of 5 for a part and is saved that amount is *immediately* removed from inventory. If the work order is subsequently edited to change the 5 to a 3 then a quantity of 2 is immediately returned to inventory upon saving the changed work order.
Full access
All inventory changes are tracked in a blockchain inside your AyaNova database and this block chain can be viewed in the Inventory transactions data table. Inventory transactions are required for any change of inventory and the inventory transaction blockchain is the only repository for inventory quantities in AyaNova.
- Accounting
- Business administration
- Inventory
Read only access
- Business administration - restricted
- Inventory - restricted
- Service manager
- Service manager - restricted
## How to access purchase orders
Purchase orders are accessed in the following ways:
- From the `Inventory` navigation pane `Purchase orders` item to open the Purchase orders [data table](ay-start-form-data-tables.md)
- From any [data table](ay-start-form-data-tables.md) column showing purchase orders such as the [inventory transactions](inv-part-inventory-transactions.md) or [Work order item part request](svc-workorders.md) data tables
## How purchase orders work
## Purchase order data table
The Purchase orders [data table](ay-start-form-data-tables.md) lists all the purchase orders previously entered, where you create a new purchase order and provides access to common [data table menu options](ay-start-form-data-tables.md#common-menu-options).
## Purchase order edit form
The Purchase order edit form provides all the [standard edit form](ay-start-edit-forms.md) functionality and the following fields:
#### PO number
This is the number of the purchase order as it's displayed in forms and reports. This is also the primary identifier when searching for a purchase order to select in [autocomplete](ay-start-form-autocomplete.md) lists.
Purchase order numbers are assigned by the AyaNova server and are a serial number that increases by one automatically.
This PO Number automatically generated by AyaNova does not need to be unique and it can be changed to another number manually by a user with the Business Admin Role. Generally you would never need to change a PO number however this feature is provided primarily for those that are importing data from a previous version of AyaNova.
Editing an existing PO number manually has no effect on the next PO Number automatically generated in sequence, however you _can_ change the next automatic PO number that will be issued in the global settings form [set next seed number](adm-global-settings.md#set-next-seed-number) area.
#### Vendor
Select the [Vendor](vendors.md) the purchase order is intended for. This is the only **required** field on the Purchase order form. All other fields are optional.
[Vendor alert notes](vendors.md#alert-notes) will display at the top of the purchase order if this particular Vendor has an internal staff alert about them. Vendor alert notes would be for internal messages about using this vendor such as "Check pricing carefully with this vendor" etc. Vendor alert notes do not display on the stock purchase order report intended for the vendor.
#### Purchase order status
This optional field provides an overall status of the progress of the Purchase order for reference purposes only. It does not affect any part of the Purchase order or PO process. You can filter or sort on this field in the Purchase orders data table to enforce process control and identify outstanding items.
#### Ordered date
Set this date when the PO is ordered from the supplier to keep track of the age of the order placed. This field defaults to the current date and time when a new PO is first opened for editing however you can clear this optional field if the order is not yet ready to place with the supplier.
#### Expected date
Set this optionaly field to the date you expect delivery of the order. This is helpful for tracking overdue orders.
#### Reference number
This optional field is provided for any purpose that makes sense in your business. It may be an order reference number provided by a vendor or related to some other internal business process.
#### Project
Optionally connect this order with a [Project](svc-projects.md) for tracking and reference purposes.
#### Vendor memo
This optional field is provided for special instructions to be sent to the [Vendor](vendors.md) and displays on the stock purchase order [report](adm-report-templates.md).
#### Text 1 / Text 2
These legacy optional text fields are provided for reference and tracking purposes. They can be [customized or removed](ay-customize.md) if not used.
#### Drop ship to customer
This optional field is provided for scenarios where the order should be delivered directly to a Customer site. When selected the the stock purchase order [report](adm-report-templates.md) will automatically include the customers shipping address in the purchase order report that is intended for to the Vendor.
#### Notes
Optional notes area for any purpose that makes sense to your business. Often this field is used for keeping notes around anything unusual about the order or the order process for reference later.
This field does not display on the stock vendor purchase order report.
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
## New PO Item first save
PO item fields are filled in upon first **save** of the PO Item. When first saved the Vendor Number and Cost fields will be updated (overwriting anything entered manaully in them before save) automatically. After that point it's safe to edit the vendor number of cost manually as it will not be overwritten in subsequent saves.
PO item fields are filled in upon first **save** of the PO Item. When first saved the Vendor Number and Cost fields will be updated (overwriting anything entered manaully in them before save) automatically. After that point it's safe to edit the vendor number of cost manually as it will not be overwritten in subsequent saves.
Note that the "Vendor Number" will only be filled in automatically if the selected vendor for the PO is either the Part's matching Wholesaler or Alternative Wholesaler
## PO Number editing
The PO Number automatically generated by AyaNova can be changed to another number manually by a user with the Business Admin Role. Generally you would never need to change a PO number however this feature is provided primarily for those that are importing data from a previous version of AyaNova. Changing a PO number manually has no effect on the next PO Number automatically generated in sequence, however you *can* change that particular next sequence number in the form accessed from: Administration -> Global Settings -> Set next seed number.
For example if the last generated number was 10 and an existing po is edited to change the number from 7 to 11; when the next new PO is made, it will be automatically assigned number 11 and there will then be two number 11's. To avoid this use this feature of editing PO numbers in conjunction with the reset serial number feature under global settings to ensure no duplicates. i.e. lets say you have the last po number auto generated is 10, you could reset the auto generated number to 20 to free up a block of 10 numbers to use on existing po's.