Table of Contents
Legal Notes: 1
Introduction. 2
Document Type.. 2
Summary of new features. 2
System Requirements. 2
New Functionality. 3
Bug Fixes & Optimisations. 5
Legal Notes: 1
Introduction. 2
Document Type.. 2
Summary of new features. 2
System Requirements. 2
New Functionality. 3
Bug Fixes & Optimisations. 5
Legal Notes
© 2015 Fourth USA Incorporated. All rights reserved.
FOURTH USA INCORPORATED PROVIDES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION CONTAINED IN THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN. Fourth USA Incorporated provides no warranty and makes no representation that the information provided in this document or any document referenced herein is suitable or appropriate for any situation, and Fourth USA Incorporated cannot be held liable for any claim or damage of any kind that users of this document or any document referenced herein may suffer. Your retention of and/or use of this document and/or any document referenced herein constitutes your acceptance of these terms and conditions. If you do not accept these terms and conditions, Fourth USA Incorporated does not provide you with any right to use any part of this document or any document referenced herein.
Complying with the applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without the express written permission of Fourth USA Incorporated.
Fourth may have patents, patent applications, trademarks, copyrights or other intellectual property rights covering subject matter within this document. Except as provided in any separate written license agreement from Fourth, the furnishing of this document does not give you, the user, any license to these patents, trademarks, copyrights or other intellectual property.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred.
Adaco is the registered trademark of Fourth USA Incorporated in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Introduction
Document TypeThis document provides high-level release notes for the bug fixes and new developments which will be available from 24th January 2017. This document contains a description of changes since version 4.6.64
Summary of new features
- Support for using vendor’s units of measure when processing EDI documents
- Enhancements to non-PO invoice entry
- Invoice Log report implemented at CP
- Inclusion of Manually entered POS Sales in Outlet Sales values
- VAT Excluded from Project Report
- Support for searching by product brand
System Requirements
The requirements for running the Adaco 4.6.65 Client Application are:Operating System | Microsoft Windows 7, Windows 7 SP1, Windows 8, or Windows 8.1, Windows 10 |
.NET Requirements | Microsoft .NET Framework 4.5.2 (for client application) Microsoft .NET Framework 4.5.2 (for server side application) |
Internet Browser | Internet Explorer 7 or above, Windows Edge |
System Requirements | Minimum 1GB memory |
New Functionality
ID | Area Affected | Description |
---|---|---|
F2614 | Vendor Interfaces |
Support for Vendor Units in EDI and Punchout Transactions It is possible that a vendor will use different identifiers for units of measure than those used by yourself within Adaco. For example in Adaco you may have a unit of measure to represent a bottle which would have the unit code of “BO” whereas your vendor may use a unit called “bouteille” which might have a unit code of BT. Equally your vendor may use a unit “PC” to represent single unit of a product (piece) which in Adaco could include products with the unit Each, Bag or Basket. So that the units of measure used by your vendors can be interpreted into Adaco units of measure (and vice versa) it is now possible to create a mapping between the units of measure used by your vendor and the units of measure used with your Adaco instance. These “Vendor Unit Mappings” can be set up in a new tab called “Units” which is located on the main Vendor detail screen. For full details of how this functionality operates please consult with a Fourth Interface Specialist. ![]() ![]() |
US14214 | Invoices |
Ability to delete an invoice line when entering a non-PO invoice In Accounting > Invoices > Invoice Entry it is possible to enter the details of an invoice which is not being posted against a received PO (for example for invoices for services where there is no PO sent to the vendor). When entering the invoice details it is possible to enter one or more distribution lines to allocate the invoice to the correct general ledger accounts and cost centres. When entering the distribution lines it is now possible to delete a line by right clicking on the line and selecting “Delete” from the context menu. |
US16652 | Invoices / Projects |
Ability to assign a non PO Invoice to a Project In Accounting > Invoices > Invoice Entry it is now possible to assign a non PO Invoice to an existing project so that the cost of the invoice can be associated with the project. Important note: The calculations which will apply the cost from a non PO Invoice to a project in the Project Report will not be implemented until Adaco version 4.6.66. In version 4.6.65 the ability to select a project when entering a non PO invoice is a visual change only and will currently have no impact on the reported project spend. |
US23908 | Projects |
Exclusion of VAT from Project Report In Report Centre > Project Report the value of orders and invoices reported against a project will no longer include any value associated with a Rate which is marked as being VAT. The value reported with be the value net of VAT. |
US23134 | Reports |
Only Show Overspend Against Budgets in Red In Report Centre > Checkbook Accounting all variances against Budget, Forecast or Plan were previously shown in Red. This has now been changed so that only overspend variances are shown in red. Where the variance represents an underspend, the variance will be shown in the normal black font. |
US23552 | Reports |
Invoice Log Report at CP The existing report called “Invoice Log” is now also available from within the CP property. When run in CP there is an additional filter with which a user can select one or more properties and the report will return a separate report page for each selected property. |
US24084 | POS Sales / Reports |
Manually Posted POS Sales Included in Outlet Sales Values When the option Property > Administration > Property Preferences > Customization > Update Outlet Sales from POS Data is enabled the value of any sales which are entered in Recipe > Recipe Sales > Enter / Maintain Sales History will be reflected in the Outlet Sales values (which are in turn reflected in the Usage Analysis reports) |
US25250 | Products |
Ability to Search on Product Brand In the Product Search form it is now possible to search for a product based on its Brand. The product brand for each item returned in the search will be shown in the last column on the search form. The Product Search form is initiated from a number of placed within the application including Requisition entry, Purchase Order entry, Maintain Guides and Recipes. |
Bug Fixes & Optimisations
ID | Area Affected | Description |
---|---|---|
D12960 |
Vendor Interface |
Incorrect Message when Auto Create and Transmit Orders Fail Previously when an order was transmitted using the Auto Create and Transmit functionality and the order transmission failed the message suggested that the order had been transmitted correctly. This has now been changed so the user is informed if the transmission of an Auto Create & Transmit order fails. ![]() |
D13112 | GL Interface |
Rounding Errors in GL Export due to Decimal Precision Due to the way that large amounts of data are consolidated into a single value it is sometimes possible that the debit and credit in an Inventory Variance journal may be out of balance by a very small amount. This has now been amended so that any rounding difference is added to the entry with the highest value (up to an pre-determined threshold). |
D9341 | Recipes |
Ingredient Replacement Blocked/Slow When Recipe Recost Job Runs Previously when an ingredient replacement was processed the recipe recost job would run and re-cost all recipes within a site which could cause performance issues and delays before the next ingredient replacement could be processed. This has been changed so that only recipes effected by the ingredient replacement are recosted. |
D9398 | Recipes |
Allergen Update - Top Level Property Recipes Are NOT Updated Previously when you amended the allergens assigned to an ingredient and selected the option “Update all recipes containing this product” only the recipes in the properties below the CP were updated. This has been amended so that all recipes either in the property making the change or the CP or Enterprise module above the property will be updated to reflect the changed allergens. |
Comments
0 comments
Please sign in to leave a comment.