Release Notes: Adaco 4_6_64

The information in this document and any document referenced herein is provided for informational purposes only, is provided AS IS AND WITH ALL FAULTS and cannot be understood as substituting for customized service and information that might be developed by Fourth USA Incorporated for a particular user based upon that user’s particular environment. RELIANCE UPON THIS DOCUMENT AND ANY DOCUMENT REFERENCED HEREIN IS AT THE USER’S OWN RISK.
© 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 Type

This document provides high-level release notes for the bug fixes and new developments which will be available from 29th November 2016. This document contains a description of changes since version 4.6.63

Summary of new features

• Support for Forecast and Planning budgets
• ​Inclusion of Purchase Requisition values in Project Report
• Enhancements to POS sales processing
• Populating Outlet Revenues based on POS sales
• Amendments to Event Plan Scale & Print of recipes
• Transmission of vendor’s unit of measure in EDI orders

System Requirements

The requirements for running the Adaco 4.6.64 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
F2216 (US22096 / US22095 / US22536 / US23514)	Accounting & Reporting	Support for Forecast and Planning Budgets It is now possible to manage three types of budgets in Adaco: Budgets – What is hoped to be achieved Forecast – What is expected to be achieved Plan – What could be achieved Separate values can be maintained for each of the above three budget types.  Values can be entered and updated manually in Accounting > Budgets > Checkbook Maintenance.  Values can also be imported using Accounting > Budgets Import Budgets.  The same (existing) csv template should be used when importing any type of budget. The Checkbook Accounting report will now show committed spend against all three budget types as well as variance against each budget type. When submitting a Purchase Requisition the value of the PR will be checked against both the Budget and Forecast values and where either value is exceeded the user will receive a warning stating that the PR will exceed the budget for the period.  The user can select to view the Budget Review Report which will show the committed spend against the Budget and Forecast.  Plan budgets are not shown in the Budget Review Report.
US16965	Projects, Reporting	Inclusion of Purchase Requisition Values in Project Report   The value of pending Purchase Requisitions not yet converted to Purchase Orders which are assigned to a project will now be included in the spend value for that project.   Note: Where a project is allocated to a specific outlet then only spend assigned to that outlet and the project will be counted against the project budget.
US21748	POS Sales Processing, Reports	Inclusion of PLU Description in POS Error Report When processing POS Sales there is an option to run the POS Error Report which will show any items not processed.  Where an item is not processed due to the PLU not being mapped the report will now show both the PLU and the PLU description to assist a user identifying the correct item in Adaco to map the PLU against.
US22083 / US22084	POS Sales Processing	Automatic Updating of Mapped Revenue Centres and PLUs When assigning a revenue centre to an Outlet or assigning a PLU to either a retail product or a recipe it is no longer necessary to re-load the sales transactions in order to update any previously unmapped sales records.  When a revenue centre or PLU is mapped all effected sales records will be automatically updated.
US22943	POS Sales Processing	Process all Mapped Sales Transactions When Processing POS Sales When the POS Sales Processing job runs it will now process all sales records which do not have errors i.e. all sales records where both the Revenue Centre and PLU are mapped. Note: when mapping a PLU or Revenue Centre you should be aware that any historical sales records effected by the mapping will be processed the next time the POS processing job runs. Note: Historical sales transactions dated earlier than the current inventory period will only be processed if the option “Allow Modification in Closed Period” is selected.
US23508	POS Sales Processing, Reporting	Manually Processed Sales Recorded in Log Report The Adaco Log Report now includes a new option to show POS Sales which have been manually imported and processed When this option is selected the Adaco Log Report will show details of any POS Sales files which have been imported and / or processed.  This selection will also show any sales submitted via the POS API which have been processed within the selected date range. Note: To see the processing on API sales the report option “Api sales” should also be selected
US23512	POS Sales Processing	Amendments to POS Processing Report Log When processing POS Sales the Report Log tab has been amended in the following ways: It is now possible to select a date range and search for all sales files / transactions within that period All sales files / transactions are included in the Report Log even if they have been fully processed (previously only files or transactions with un-processed sales were shown).  For each sales file / transaction the number and value of sales processed is shown as well as the number of sales records un-processed
US22941	POS Sales Processing	Sales Effective Date Shown When Selecting Sales Files / Transactions When selecting POS sales files or transactions to process the effective sales date is now displayed (previously only the Loaded On date was displayed).  It is only possible to select sales transactions for processing in batches which have the same Effective Date. When sales transactions are selected the Effective Date will be used to populate the Posting Date dropdown which will subsequently be used as the transaction date when processing the sales.
US21747	POS Sales Processing, Reporting	Option to Populate Outlet Sales with POS Sales Values In Property > Administration > Property Preferences > Customization > General there is a new option called “Update Outlet Sales from POS Data”.  When this option is selected the values in Outlet Sales are updated with the total value of sales imported and processed from the POS system.  Sales values will be shown in one of two ways: Where the POS Sales have been successfully processed the value of sales will be written as a record with the comment “Processed POS Sales” and the name of the POS type from which the sales were processed. Where the POS Sales have been mapped to an outlet but were not processed due to un-mapped PLUs or insufficient stock the value of the sales will be written as a record with the comment “Un-Processed POS Sales” and the name of the POS type from which the sales were processed. If Un-Processed sales are subsequently processed the values for both Un-Processed and Processed sales will be updated accordingly. It is still possible to manually add Outlet Sales values to reflect sales made which were not processed through the POS system. Where the sales items are not mapped to an Outlet their value will not be added to the Outlet Sales values. The total value of Outlet Sales will be shown in the Summary Usage Analysis report and used to calculate the Cost of Sales for an outlet.
US22945	Events	Amendments to Scale and Print Option in Event Plan Within an Event Plan there is an option to Scale and Print the Event to see the total recipe requirements for the Event based on the content of the Event and the forecasted number of covers. When selecting this option there is an option to also scale the sub-recipes.  Where this option is selected the sub-recipes required to produce the recipes within the Event are also scaled.  The scaled requirements for each sub-recipes are consolidated across all recipes which include the sub-recipe so that only one scaled recipe card is produced for each sub-recipe showing the total requirements for each sub-recipe. When printed, each main recipe is printed followed by any sub-recipes required to complete the main recipe.  Where a sub-recipe is included in more than one main recipe it will be printed after the last main recipe which includes the sub-recipe.
US9145	Vendor Interfaces	Include Vendor Unit in EDI Order Transmission It is now possible to map a vendor’s units of measure against the units of measure set up in Adaco.  These units can then be included in orders sent to a vendor via EDI so that the vendor will receive their orders with their own units of measure included.

 

Bug Fixes and Optimisations

 

 

ID	Area Affected	Description
D12520	AP Interface	Incorrect Appearance of Multiple Outlet Invoices in AP Export Screen   Previously some invoices which were posted against multiple receivings for an order which included multiple outlets was incorrectly displayed in the AP export screen.  This has now been resolved and such invoices will be displayed correctly.
D12874	AP interface	Error When Exporting Invoices on Last Day of Period   When using the M3 AP interface there was an error when attempting to export invoices with the last day of the current period selected as the posting date.  This has now been resolved and invoices can be exported with any selected posting date.
D13109	AP Interface	Exclusion of Zero Values Records in M3 Interface   Previously invoices which had a zero value were exported when using the M3 AP interface which caused errors in the M3 system.  The behaviour of this interface has been modified so that no records will be created in an export file for invoices which have a zero value.  Where an invoice with zero value is selected for export it will be marked as exported and removed from the AP export screen however no record for the invoice will be written.