From 5c325dbe64f8ba536f96eb1e864b20f53ab1bbd5 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 6 Sep 2021 19:37:56 +0000 Subject: [PATCH] --- docs/8.0/ayanova/docs/ay-report-edit.md | 7 ++-- .../ayanova/docs/ay-start-changes-from-v7.md | 17 ++++++++++ docs/8.0/ayanova/docs/inv-purchase-orders.md | 33 +++++++++++++------ 3 files changed, 42 insertions(+), 15 deletions(-) diff --git a/docs/8.0/ayanova/docs/ay-report-edit.md b/docs/8.0/ayanova/docs/ay-report-edit.md index 90d9194f..d9cca4c5 100644 --- a/docs/8.0/ayanova/docs/ay-report-edit.md +++ b/docs/8.0/ayanova/docs/ay-report-edit.md @@ -62,9 +62,9 @@ Report generation consists of two distinct and separate processes: Processing th * `Scale` scales the report rendering, must be a value between 0.1 and 2, the default is 1 -##### PDF header / footer template notes +#### PDF header / footer template details -The CSS section of the Report template is separate from the header footer templates and not connected at all. Headers and footers require their own complete inline css to be specified as they are part of the PDF generating system, not the Report generating system. +The CSS section of the Report template is completely separate from the CSS Header & Footer templates. CSS Headers and footers require their own complete inline css to be specified as they are part of the PDF generating system, not the Report generating system. Example: Show todays date in the header, and Page x of XX - note also total pages refers to TOTAL pages, NOT pages per object (i.e. if printing from a list of workorders, the total pages will be ALL workorders pages, not pages per workorder. @@ -78,8 +78,6 @@ Footer Page  of      ``` - - ### Report Template The main HTML / Handlebars template. This is where the report is defined and is required to render a report. A template is a mixture of both source HTML and Handlebars templates combined with data to generate the final report HTML. @@ -91,7 +89,6 @@ In order to get up to speed quickly with report design we recommend looking over This section is provided to define the HTML Cascading Style Sheet for the report document. This section is optional. - ### Prepare This section is provided as a way to change the data provided to the report *before* it is rendered. diff --git a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md index 209cc14a..d6f98a4a 100644 --- a/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md +++ b/docs/8.0/ayanova/docs/ay-start-changes-from-v7.md @@ -36,6 +36,23 @@ Migrating from AyaNova 7 will result in a Customer Contact type User being creat As with all User / Contact accounts created in v8 no login is possible by those users until the administrator allows it and assigns a password so there is no security risk of Contact users logging in that previously could not. +### Inventory changes + +The AyaNova 8 inventory system is completely new and works differently than the AyaNova 7 inventory system. + +It is both more flexible as it allows for easily changing values after the fact but more strict in that it has a far more strict control over inventory values than AyaNova 7 allowed. + +V8 inventory 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. + +There is no longer a "Used in service" checkbox in Work orders, they consume inventory immediately upon entry and save. + +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. + +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. + +AyaNova 8 does not permit negative on hand inventory values to exist, every part consumed must have a quantity of on-hand inventory to back it up or it's not allowed to be saved. + + ### Purchase orders / receipts Purchase orders and receipts have been combined in v8 and are no longer separate objects. diff --git a/docs/8.0/ayanova/docs/inv-purchase-orders.md b/docs/8.0/ayanova/docs/inv-purchase-orders.md index 714cb9f8..8dfd4108 100644 --- a/docs/8.0/ayanova/docs/inv-purchase-orders.md +++ b/docs/8.0/ayanova/docs/inv-purchase-orders.md @@ -2,14 +2,27 @@ [Incomplete - under construction] -Notes: -PO Number editing -This feature is provided primarily in cases where imported data has unwanted PO numbers that need to be re-assigned to other numbers. (some v7 users with Microsoft SQL server had numbers jump into high ranges due to a SQL server bug) -Normally you would never change these numbers, just let the system handle it automatically -BizAdmin role can edit the PO number, however it doesn't change the auto po number generator next value, so, 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. -(case 3864) When NEW+ Po Item, when select a Part, the PO Cost and Vendor Number is NOT filled in UNTIL select Save for that PO Item. - WITH NOTE: Vendor Number can ONLY fill in automatically IF selected vendor for the PO is either the part's selected Wholesaler OR Alternative Wholesaler. - On "first" save, Vendor Number overwrites ANYTHING manually entered into the PO Cost field AND that has been manually entered into the Vendor Number field, overwriting with the actual part cost existing, and with the actual vendor number that is existing for the selected part. Once have saved at least once, THEN can edit. +## OVERVIEW + +Purchase order entry screen available when "Use inventory" is selected in Global settings. + +## Inventory in AyaNova + +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. + +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. + +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. + +## 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. + +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. \ No newline at end of file