Release Notes: MX: 2017.3: JUL 2017

Released July 17, 2017

Introduction

This document communicates the major new features and changes in the 2017.1 Enterprise Back Office Release.  It also references issues that were addressed during this release.

 

About This Release

The 2017.3 release includes substantive changes to improve the Enterprise Back Office user experience. A few of the release highlights for the Enterprise Back Office Desktop (EBO Desktop) and Enterprise Back Office Mobile (EBO Mobile) are detailed below.

 

Release Highlights

Enterprise Back Office is a cloud-based operating system that provides operational efficiency, cost controls and real-time visibility into restaurant operations that keep the manager in front of customers and focused on their experience, rather than stuck in the back office staring at spreadsheets. Get instant insight into inventory and financials with in-depth, down-to-the item reporting. Gain access to sales data, gross profit, cost of goods sold, loss prevention and exception management with the ability to report down the item level at individual stores. With Enterprise Back Office, food is fresher, waste is reduced, and gross profits are increased.  Highlights include:

 

MxConnect Features

Limit Ability for Users to Skip Scheduled Orders

Background / Business Driver

Within the Ordering module in MxConnect, users are able to skip scheduled orders. Skipping a scheduled order can drive other actions with the vendor and some customers require the ability to limit who can access this feature.

A new security permission has been introduced, which will allow only user groups who are granted this permission to skip a scheduled order. Users without this permission, who do have access to ordering in MxConnect will only be able to create orders, not skip them.

Note: The new security permission is named “Inventory - Ordering - Place - Hide Skip Order” and only affects Scheduled Order functionality in MxConnect. Users with access to Scheduled Orders in MMS will not be limited in this regard.

 

Show “Usage Per Thousand” in MxConnect Ordering

Background / Business Driver

Customers familiar with ordering through MMS who utilize “Usage Per Thousand” projections for certain items require that this calculated value be displayed when placing orders through MxConnect.

MxConnect Ordering has been updated to provide the “Usage Per Thousand” value as an available option through “Manage Columns”, so that users can display this value if it is relevant to them.

Note: “Usage Per Thousand” represents the quantity of inventory needed for an item based on a customizable factor multiplied against every $1,000 of Net Sales, instead of using recipe depletion-based projections.

 

Waste Entry Enhancements for MxConnect

Background / Business Driver

To reduce the potential for user error, the following changes have been introduced to the Waste Entry screen in MxConnect:

• A new configuration to limit the Units of Measure available to use for entering waste.
• Configuration Name: Mobile -> Inventory -> Enabled Unit of Measure types for Waste
• Can be any combination of (Case, Inner, Base, Weight)
• A new configuration to specify the the threshold to prompt users for excessive waste values.
• Configuration Name: Mobile -> Inventory -> Inventory Waste - Amount Warning Threshold
• If the absolute value of the waste entry exceeds this value, then the user is prompted with a warning, but can still proceed with the entry if they so choose.
• A new Security Permission to control who is allowed to modify the Apply Date/Time when entering waste.
• Permission Name: Mobile -> Inventory - Waste - Can Edit Apply Date/Time
• If user’s Security Group has permission turned ON, the user can modify the apply date.
• If user’s Security Group has permission turned OFF, the user cannot modify the apply date.

 

MacromatiX Management System Features

Loyalty Points Adjustment Import

Background / Business Driver

Loyalty Points within the Loyalty module can be added through integrations with the POS or directly within MMS. The ability to increase or decrease a customer’s loyalty point balance through an import file is needed to allow 3rd party applications to provide these adjustments.

A new CSV import has been introduced, which allows points to be added or subtracted from a customer’s account. The import consists of the following fields:

• CustomerID
• PointQty (positive or negative)

Note: This functionality was requested by Busby Brands, but can be used by any customer who utilizes the MacromatiX Customer Loyalty module.

 

Handle Foreign Currencies in Cash Counts

Background / Business Driver

There is a need to be able to capture and report on Foreign Currencies collected at the register to be included in Cashier Reconciliations and subsequent Banking Deposits. When entering cash counts in MacromatiX, users need to be able to review/input the individual currency amounts and have the properly converted values apply to the total cash collected for reconciliation. To satisfy this need, the following changes were made:

• A new security permission called “Entity Manager - Foreign Currency - Can Access” was added, which allows users to add foreign currencies to a store.
• A new section to Category Administration was added for “Currency Payment Type” that allows individual payment types to be mapped to the appropriate currencies.
• LiveLink POS Interface updated to translate Foreign Currency tenders into Control Info and Transaction Payment records.
• Cashier Reconciliation updated to display and allow entry/modification of the Foreign Currency amounts collected during the cashier’s shift and have these values properly impact the over/short using Financial Groups.
• Banking Reconciliation updated to display Foreign Currency amounts collected across all cashier reconciliations for the day using Financial Groups, impacting the store’s daily total over/short.

 

Foreign Currency Assignments to Stores

 

Foreign Currency Payment Type Mappings

 

Foreign Currencies in Register Reconciliation

 

Foreign Currencies in Register Verification (Variance)

 

Foreign Currencies in Deposit Entry

 

Authorize Petty Cash for Banking

Background / Business Driver

MacromatiX has functionality allowing Petty Cash transactions to be included in the store’s Banking Deposits. Some customers have a requirement where these transactions should only be included when these transactions are authorized for addition to or deduction from the deposit. This allows petty cash fund balances depleted from Paid Outs to be “topped up” using funds from the available deposit or excessive receipts of Paid Ins to be deposited to the bank.

To satisfy this requirement:

• The existing configuration to include Petty Cash in Banking was extended to allow the options:
• No (Default)
• By Transaction Date
• By Authorization Date
• A new permission was introduced to grant users the ability to Authorize Petty Cash Transactions.
• The Petty Cash Screen was enhanced to introduce an “Authorization” tab.
• Within this tab, authorized users can select any Petty Cash transactions that have not already been authorized (for current or previous business days) and authorize them as a batch under the selected business day. These authorized batches are applied to the available funds for deposit under banking for the selected day.
• Users are also able to delete the batches, or “unauthorize”, as long as the batch has not already been included in a deposit.

 

Import to Update Local Vendor Item Price

Background / Business Driver

The existing MacromatiX imports for Vendor Items (Catalog) and Vendor Item Pricing only update the Vendor Item Prices. These do not get applied to the Inventory Item Costs until orders are received under the new pricing. Some customers require that the Vendor Item Price and the associated Inventory Item Costs get updated at the same time, without requiring the receipt of an order.

A new import has been created called “Vendor Item Price Extended Import”. This can be provided in CSV or XML formats and identical to the existing “Vendor Item Price” import in structure and validation requirements. The difference applies in how the Price change is handled.

• Vendor Item Price Import - Updates the Vendor Item Price for the specified Vendor Item(s) at the specified Store(s) only. Inventory Unit Cost is NOT updated via import.
• Vendor Item Price Extended Import - Updates BOTH the Vendor Item Price and the Inventory Unit Cost for associated Inventory Items for the specified Vendor Item(s) at the specified Store(s).

 

Update Logging Frameworks for Consistency

Background / Business Driver

The various components of MacromatiX use a variety of logging mechanisms. To improve consistency, maintenance and support processes, a centralized logging framework is needed.

MMS, MxConnect, ServerManager and LiveLink have been updated to use the nLogger framework. As part of this:

• 3 Types of Logs are available: Error, Warning, Information
• All logs are created in the “Logs” folder as configured in the application’s configuration file.
• Log files are automatically archived based on size defined in the configuration file.
• The maximum number of archived log files can be configured in the configuration file.

 

Scheduled vs. Non-Scheduled Orders in PO Export

Background / Business Driver

Some vendors need to identify if a Purchase Order transmitted through MacromatiX is for a Scheduled Order or a Non-Scheduled order, as different processes or fees may apply.

The standard Purchase Order Export data set has been updated to include:

• A True/False indicator named IsScheduled.
• True = Scheduled
• False = Unscheduled
• The Cut-Off Date (applicable to Scheduled Orders Only)

These additional fields are available to any vendor’s Purchase Order export, but will not be included unless specifically translated through the export’s XSLT under Purchase Order setup.

Note: Applies whether order is created in MMS or MxConnect.

 

Employee Data Integrated Between MX and HS

Background / Business Driver

Customers who utilize both MacromatiX and HotSchedules Labor require the ability to have MacromatiX be the point of entry for the following data and transmit it to HotSchedules:

• Employee Details
• Employee Job Assignments

To facilitate this request, the following enhancements were applied to MacromatiX:

• A new Web-Service Export has been provided, which will transmit Employee Details from MacromatiX to HotSchedules through the HotSchedules setEmps method in the EmpService API.
• Can be scheduled or event-driven.
• A new Web-Service Export has been provided, which will transmit Employee Job Assignments from MacromatiX to HotSchedules through the HotSchedules setEmpJobs method in the EmpService API.
• Can be scheduled or event-driven
• The Employee Management UI has been updated to allow certain fields to be required for entry/update.

Fields that can be configured as required or not through the configuration setting “Workforce -> Employee Management -> Custom Required Fields for Employee Management” are:

• Employee Number
• Phone
• Mobile PHone
• Fax
• Birthdate
• Hire Date
• E-Mail Address
• Address 1
• Address 2
• City
• State
• Zip Code
• Country
• POS ID

 

Required Field Validation

 

New Labor KPIs to Display on Scheduler

Background / Business Driver

Some customers require the ability to view Scheduled and Actual Transactions Per Labor Hour that exclude Management and “Shift Runner” hours. Although requested by KFC Thailand, these new KPIs can be turned on for other customers.

• Transactions Per Scheduled Team Member Labour Hour
• Calculated as: (Total Transaction Count from Forecasted Sales) / (Scheduled Team Member Hours)
• Transactions Per Team Member Labour Hour
• Calculated as: (Total Transaction Count from Forecasted Sales) / (Authorized Team Member Hours)

Note: Existing KPIs for Scheduled and Actual Labor Hours against forecasted sales remain available and include ALL hours (Team Members, Shift Runners, and Management).

 

Update Xceed FTP Library

Background / Business Driver

MacromatiX utilizes a 3rd party library called “Xceed” for handling file transmission over FTP/SFTP. The outdated version in place was causing issues, including crashes for some client FTP integrations.

During the 2017.2 development cycle, usage of the Xceed library was investigated to identify the scope of work needed to upgrade to a new version.

During the 2017.3 development cycle, replacement with the new version was started, but is still incomplete. Until all components are updated to use the new version and fully validated, a configuration setting is available in the Mx.Config file for MMS, MxConnect, and Server Manager to use the “Legacy” version.

No customer environments should be transitioned to the new version until authorized to do so by Product Management & SaaS Ops.

 

Reporting Data Store Features

Add Inventory Travel Path Data to RDS

Background / Business Driver

Custom inventory reports built from RedShift data need to be arranged by each store’s Inventory Travel path. To support this, the Travel Path data needs to exist in RDS.

Two new data tables were added to RDS to support inventory reporting:

• StoreInventoryLocation - The storage locations defined at each store.
• StoreLocationItem - The items assigned to each storage location at each store, including the sort order of the items within the location.

 

Add Inventory Count Group Data to RDS

Background / Business Driver

Custom inventory reports built from RedShift data need to provide grouping by Inventory Count Group (Stocktake Group), as this is how managers are used to reporting against their items.

One new data table was added to RDS to support inventory reporting:

• InventoryCountGroup - The Inventory Count Groups defined by the customer, including desired sort order.

The existing data table, InventoryItem, in RDS has been updated:

• Added column InventoryCountGroupID to identify the Inventory Count Group associated with each Inventory Item.

 

Add Pay Allocation & Shift Data to RDS

Background / Business Driver

Custom Labor and Weekly Summary reports built in RDS require the calculated pay for employees by store, shift, job, and pay category for calculating labor cost. Some reporting also requires a breakdown by store shifts (AM/PM).

Four new data tables were added to RDS to support Labor reporting:

• BusinessDayShift - Day Shifts (AM/PM) created by the POS, used to summarize data by shift.
• RegisterShift - The shift marker timestamp records created by the POS to identify the Start and End Shift times.
• PayCategory - The customer-defined Pay Categories used to identify the type of pay applicable to a shift or a portion of a shift (Regular, Overtime, Penalty, etc.)
• PayAllocation - The calculated pay for each employee’s authorized shift; by store, date, Pay Category, and Job.

 

Add Account Sales Mappings to RDS

Background / Business Driver

Custom Sales Exports often need to map sales amounts to specific GL Accounts either by Sales Category or by individual sales items. To facilitate exports of this nature through RDS, these Account Mappings need to be added to the RedShift database.

Four new data tables were added to RDS to support reporting or exporting Sales by Account Mapping:

• AccountingClass - Stores the Account Class definitions that encapsulate the Mapping Template.
• AccountingSystemStoreMapping - Stores the individual Stores that are assigned to the Mapping Template.
• AccountSaleItemMapping - Stores the definitions for Sales Item Classifications used for mapping (Sales Item, Department, Group, etc.)
• AccountingSystemSalesItemMapping - Stores the individual mappings from the Item,Group, Department, etc. to the desired Account Name and Number.

 

Add Pay Allocation & Shift Data to RDS

Background / Business Driver

Custom Sales Exports often need to map transaction payment amounts to specific GL Accounts based on their payment (tender) type. To facilitate exports of this nature through RDS, these Account Mappings need to be added to the RedShift database.

A new data tables was added to RDS to support reporting or exporting Transaction Payments by Account Mapping:

• AccountingSystemTenderTypeMapping

This table can be joined with the following tables to obtain the correct mappings by Accounting System and Store:

• AccountingSystem
• Store
• AccountingSystemStoreMapping
• TenderType

 

Add “Other” Account Mappings to RDS

Background / Business Driver

Some customers utilize “Other” Accounts for data exports that are not directly tied to standard MacromatiX data elements. To support custom reports/exports through RDS that leverage these “Other” Accounts, two tables were added to the RedShift database.

• CustomAcccount - The definitions of the Custom Accounts added by/for the customer.
• AccountingSystemCustomAccountMapping - Maps the Custom Accounts to the desired GL Account Name/Number by Accounting System and/or Store.

 

Update VendorStoreInventoryItem Table in RDS

Background / Business Driver

There are three pieces of information related to Vendor Items at individual stores that are required for some custom reports and exports that were not originally included in the table definition in RDS. These have now been added:

• StockTakeUnitInnerID - The Unit Of Measure ID used for counting the “Inner Pack” of the Vendor Item at the store.
• PerformStockCount - True/False indicator of whether the vendor item is counted during inventory counts.
• RestrictedOrder - True/False indicator of whether the vendor item is restricted from being ordered through MacromatiX by the store.

 

Update StoreVendor Table in RDS

Background / Business Driver

The StoreVendor table in RDS contains all of the Vendors assigned to individual stores. The original definition of this table in RDS excluded several fields that were determined not applicable to reporting. There are, however, several fields that are required for custom exports or reports by various customers.

The following fields were added to the RDS table “StoreVendor”:

• DaysRequiredIn - The default # of days after placing an order that it is expected to be received.
• LeadTimeDays - The # of days lead time required to fulfill orders for a vendor at each store.
• AutoClearBackOrder - Specifies whether backorder quantities are automatically cleared when partial quantities are received.
• OrderFrequency - Specifies how frequently orders are expected to be submitted to the vendor.
• OrderItemCode - Indicates whether to use the Inventory Item Code or the Vendor’s Item Code.
• ScheduledOrderExtraDays - # of days added to an order’s “Cover Until” for Scheduled Orders.
• GenerateCreditNote - Determines whether Credit Notes are automatically generated for returns.
• EmailOrder - Specifies if an e-mail is automatically generated when orders are submitted
• AutoReceive - Specifies if orders for the vendor are always automatically received.

 

Update StoreInventoryItem Table in RDS

Background / Business Driver

The count types (frequencies) assigned to inventory items can be overridden by store. These overrides were not originally populated in the RedShift database. To facilitate certain custom reports/exports dependent on the count types, this data needed to be added to the table StoreInventoryItem:

• CountTypeDefault - A bitmapped value indicating what the default count types are for each item.
• CountTypeSpecific - A bitmapped value indicating what the overridden count types are for each item at each store.
• Available Types/Frequencies are mapped as (from right-to-left):
• Spotcheck (Bit 0)
• Daily (Bit 1)
• Weekly (Bit 2)
• Monthly (Bit 3)
• Periodic (Bit 4)
• Example:
• Stored Value = 12
• Binary Value = 01100
• Enabled Types = Weekly & Monthly

 

Update InventoryCreditMemo Table in RDS

Background / Business Driver

The Credit Memos associated with purchase order returns are extended to RDS in the table named “InventoryCreditMemo”. When this table was initially added, some fields required by custom exports/reports were not included and needed to be added:

• ClaimType - The type of claim applied (Credit, Debit, etc.)
• VendorClaimAmount - The value of the claim, confirmed by the vendor.
• VendorClaimTaxAmount - The amount of tax applicable to claim, confirmed by the vendor.
• ProcessedBy - The User ID associated with the user who processed the Credit Memo.
• ProcessedComments - The comments (if any) entered by the user upon processing the Credit Memo.

 

Update SalesItem Table in RDS

Background / Business Driver

The SalesItem table in RDS did not include “Brand” or “Universal Product Code” in the definition when it was originally added. These fields are required for some custom reports or exports and have been added.

 

Browser, Device and Cube Version Prerequisites

In order to deliver a best in-class software solution to our customer base, Enterprise Back Office relies on the latest updates and advances available from Web Browsers to ensure improved security, a richer feature set and heightened performance.

2017.3 Supported Browsers and Devices

The following browsers and devices are officially supported by Enterprise Back Office in the 2017.1 release:

• Enterprise Back Office Desktop Solution Supported Browsers are: Microsoft Edge, IE 9+, Chrome 34+, FireFox 28+, and Safari 7+
• Enterprise Back Office Mobile Solution Supported Browsers are: IE 9+, Chrome 34+, FireFox 28+, Safari 7+, iOS 7.04+, iOS 8, iOS 9, iOS10
• Mobile Device recommendations: iPad and IPad Mini
• Minimum recommended device display resolution of 1024px x 768px
• POS: MICROS 3700, NCR Aloha, NCR Compris, Panasonic PANo7700, Panasonic PARJournal, POSIXML, Radiant, SIGNATURE Signature, and XPIENT POLLO

Cube Version

Several areas of EBO Desktop have dependencies upon facts, measures, and other components in the cube. (Version dependency between EBO (Desktop & Mobile) and the OLAP cube.) This version compatibility is the minimum cube version that is compatible with an EBO Desktop version.

Note: The Cube is backwards compatible. Always upgrade to the latest version of the cube.

 

EBO Desktop & Mobile Version	Minimum Cube Version
2017.3	2016.1.38
2017.2	2016.1.38
2017.1	2016.1.38
2016.6	2016.1.37
2016.5	2016.1.35
2016.4	2016.1.34

 

Release Notes - EBO Desktop

Core:

The Enterprise Back Office Desktop Solution can help reduce costs through efficient supply chain management improving accuracy and efficiency through automation and electronic communications. Changes include:

 

• Resolves issue of Feature Unavailable displayed when Store calendar and Business Calend have differing calendars loaded.
• Improved efficiency of SQL query syntax.
• A fix has been applied wherein failing to provide a specific file mask type for an imported file will no longer prevent the generation of an attachment of failed records in a configured autonotification; attached records will have a neutral file format.
• A fix has been applied to the MMS_Admin_Entity.aspx page wherein already in-use values for Hotschedules Concept ID were not being persisted to the database when entered for subsequent entities.
• The Logging framework for MMS and MxConnect have been updated to use the unified nLogger functionality.

 

 

Financial:

The Enterprise Back Office Desktop Financial Solution provides revenue management of monetary transactions, settlements, and deposits. The functionality to account for and track the movement of cash and other trading types in a store. Financial changes include:

• A fix has been applied where, under certain circumstances, the Offline Cash application was causing Beginning Cash values for Register Floats closed while offline to display as 0.
• A fix has been applied within the Offline Cash Manager application to correct the finished finished transaction values such that taxes are properly included when Closing a cashier via the Offline Cash Manager.
• A fix has been applied to the MMS_Stores_Cashup6.aspx page such that new store locations without configured floats can now add a new float via the Add New Store Float button without experiencing a Feature Unavailable notice.
• Able to successfully change Value for the Cash Count for Cash Count in Night Shift.
• A fix has been applied wherein the Adjust Change Receive functionality within the MMS_HO_DataAssurance.aspx page was failing to do so when the Save button was clicked.
• A fix has been applied wherein the Currency dropdown on the MMS_admin_Entity.aspx page was defaulting to the first configured Currency on the system when one was not designated for the Entity being examined.  The dropdown will now display Not Set when the Currency value for an examined entity has not been.

 

Inventory:

The Enterprise Back Office Desktop Inventory Solution can help reduce inventory holding costs through efficient supply chain management. It can improve purchasing accuracy and efficiency through automation and electronic communications. Inventory Ordering changes include:

• Issue resolved to prevent multiple cancellation for an order being sent which results in the inventory on hand being erroneously adjusted.
• A fix has been applied wherein exports triggered by the PurchaseOrderExportTriggered event were also firing off at the Receiving of an Open purchase order.
• A fix has been applied wherein some items on a given store/Vendor's Standard Order were not being copied when the Copy function of the MMS_HO_StandardORder.aspx page was utilized to copy that Standard Order to another store that was otherwise ready to receive it, i.e. Vendor and VendorEntityItems assigned to new store.
• Resolves issue where incorrect Apply Date was being set on Amended Credit Memo Claims.
• Resolve issue where cancelling Order where shipping confirmation received with only some inventory items resulting in incorrect on order quantities.
• Resolve issue where incorrect dates for scheduled orders import through UI and server manager caused overflow exception. Add logging to indicate where error occurs.
• A fix has been applied wherein users of the Container receiving functionality were unable to view the list of Container configured items when pressing the Containers button on the Receive tab of the MMS_Stores_OnlineOrderClassic.aspx page.
• SP qryMMSTransactionControlInfo_GetForDeletionsAndReductions query syntax optimised for best performance.
• Content of the Credit Note export file now matches the UI of Credit Notes page when tbVendorEntityItem has more than one records for same VendorID and EntityID.
• The Purchase Order Export has been updated to allow inclusion of the type of order (Scheduled vs. Unscheduled) and the Cut-off Date for Scheduled Orders. These additional elements must be added to each vendor's through the custom transform that generates the export in the vendor's desired format. 
• Incorrect itemcode was returned in the Receipt Export

 

Workforce:

The workforce module allows users to setup labour laws and working restrictions, create schedules, manage Time and Attendance, employee availability & time off and more.

• Fix was implemented to stop Time and Attendance overlapping shifts from being recorded  where existing clocked out shift starts in the middle of new shift.

 

Loyalty:

The Loyalty Campaign module allows users to create and run ongoing campaigns through which their customers can earn and redeem benefits according to specific criteria. Loyalty changes include:

• The Entity ID we call when MX calls FD for value reset has been reverted to Entity ID 258
• A new import named "Loyalty Points Import" has been provided that allows Loyalty Customer account balances to be increased or decreased by specified quantities, based on the customer's Loyalty Card ID.

 

Reporting:

• Issue resolved where telerik grid failed to load on the account Mappings Sales Modifier mappings tab.
• Report G.I.T now shows details of Orders when configured on the Vendor page.

 

Release Notes - EBO Mobile

Enterprise Back Office Mobile is designed for use on a mobile device so that you have constant access to your data in real time for Forecasting: Inventory Counts, Ordering, Transfers, and Waste; as well as Labor. The mobile inventory count enables users to perform an inventory count on a mobile-enabled device (for example, iPad), as well as manage the item’s travel path. Mobile ordering enables store managers to place inventory orders with their suppliers. Both EDI and email order creation are supported. Stores can create orders using the scheduled orders option or by creating an unscheduled new order. Users can also search the order history.

 

Core:

• Two new exports and web-service export destinations have been added to provide the ability to send Employee Details and Employee Job Assignments from MacromatiX to HotSchedules.
• Any orphaned data in table ReportMeasure was not ignored

 

Financial:

• N/A

 

Inventory:

• "A new security permission has been implemented so that a user is no longer able to 'skip' a scheduled order on the scheduled order page in the mobile solution.  If the permission is not enabled, the user will have the option to create or skip placing the order. if the permission is enabled, the user will only have the option to create the scheduled order."
• Waste Entry in MxConnect has been enhanced to:
• Prompt users if their waste entry's value exceeds the configured threshold.
• Restrict Waste entry to specific Unit of measure fields (Unit, Weight, Inner, Outer) based on configuration.
• Allow users (by security permission) to modify the Apply Date/Time of the waste entry.

 

Forecasting:

N/A

 

Workforce:

N/A

 

Reporting:

N/A

 

Release Notes - Reporting Data Store (RDS)

The Enterprise Back Office solution is a prolific collector of operational data. The Reporting Data Store (RDS) has been conceived in order to give users ownership and access to their own data. Users will have the ability to design and build their own reports and interrogate the database at will. Progress, for the feature, continues.  The following fields have been added to the Reporting Data Store:

• RDS has been enhanced with 4 reference tables to be used for financial account mapping against Sales activity:
• AccountingClass
• AccountingSystemStoreMapping
• AccountSalesItemMapping
• AccountingSystemSalesItemMapping
• Fix: performance degradation addressed for SQL Server (EBO) part of sync process for RDS table safemovement.
• Following the change no values of 'IV' or 'EX' in accountingclasscode should exist in inventoryitem
• Pipe character will be replaced with Space for Purchace Orders - RDS Table InventoryPurchaseOrder - for the following columns:
• shippingaddressattention
• shippingaddressstore
• shippingaddress1
• shippingaddress2
• shippingaddress3
• Invoicenumber
• The RDS Table, StoreVendor, has been updated to include the following fields:
• StoreAccountCode (Store Identifier referenced by the Vendor)
• DaysRequiredIn (The Default number of days orders created for the vendor are set for Expected Delivery)
• LeadTimeDays (Any additional number of days needed for Lead Time to submit orders to the vendor)
• AutoClearBackOrder (True/False - determines whether back order quantities are automatically cleared if partial quantities are received)
• OrderFrequency (The frequency at which orders are typically submitted for this vendor)
• OrderItemCode (Determines whether "VendorCode" or "ItemCode" are used in Purchase Orders)
• ScheduledOrderExtraDays (The number of additional days applied for calculating coverage for scheduled orders)
• GenerateCreditNote (True/False - determines whether Credit Notes are automatically created when purchase returns occur)
• EmailOrder (True/False - determines if a copy of the order is sent via e-mail upon submission)
• AutoReceve (True/False - Indicates if orders for this vendor should be auto-received upon processing of Auto-Receive Orders task)
• RDS has been updated to include "Brand" and "UniversalProductCode" in the SaleItem table to be used for reporting purposes.
• The RDS Table, InventoryCreditMemo, has been updated to include the following fields:
• ClaimType (Credit, Debit, etc.)
• VendorClaimAmount (the value of the claim)
• VendorClaimTaxAmount (the amount of tax included in the claim)
• ProcessedBy (the person who processed/approved the claim)
• ProcessedComments (the comments entered when the claim was processed)
• The RDS table StoreInventoryItem has been updated to include fields for "CountTypeDefault_Raw" and "CountTypeSpecific_Raw" so that the count types assigned to the item can be used in reporting. _Note: These are bitmap values that will require calculation to determine which count types are enabled/disabled._
• The RDS table, VendorStoreInventoryItem, has been updated to include the following fields:
• StocktakeUnitInnerID (Unit of measure ID used for counting the "Inner Pack" of the vendor item)
• PerformStockCount (true/false - indicates if Vendor Item is active for counting)
• RestrictedOrder (true/false - indicates if Vendor Item is restricted from being ordered)
• RDS has been updated to include the "PayAllocation" table, which will allow for reporting against calculated pay for authorized shifts based on the configured labor rules for determining regular pay, overtime, and other pay categories. This will allow reporting on employee pay or labor cost by store, day, shift, and employee.
• Two new tables were added to the RDS database to allow reporting against the Inventory Count Travel Path for inventory items at a store.
• StoreInventoryLocation
• StoreLocationItem
• The Common Items Yield report uses SalesItemID's in the tbItem.OtherID column.  The Common Items Yield report uses the transaction count as the sold quantity in the calculations.

 

******************