What's New on Release 19.1?What's New on Release 19.1?
If you haven't installed a previous version of Release 19, then be sure to also review What's New on Release 19.
Windows Inventory Enhancements
Windows Purchasing and Receiving Enhancements
Windows Accounts Receivable Enhancements
Service and Repair. This new feature is a purchase option that allows you to enter and process service orders, and includes the following features:
Enter and process Service Orders
Enter repair items and their corresponding serial numbers, parts, and labor including the ability to select pre-defined service packages
Track Service Orders by technician
Enter free-form comments, printing or non-printing (internal)
Print Service Orders using a new form (Enhanced Forms only)
Design a standardized service label that can be printed with service information and attached to items for repair (requires Eagle for Windows POS Flex-Labels--option 82 is set to Y).
Take advantage of a controlled Service Order flow through statuses of Quote, Checked-in, Work-in-Process, Waiting on Parts (if applicable), and Complete.
Track Service Order history by customer, SKU, and serial number/VIN number/tag number to easily determine what work has been done on what equipment
Use the Service Order Viewer to give quick information on all open Service Orders, with the ability to quickly assign technicians to check-in orders, make status updates, add a comment, and delete Service Orders. You also have the ability to access the Service Order History viewer for invoiced service orders.
(Customer Order Management [COM] users) Take advantage of the COM features of special order, buyer’s list, transfer, and backorder which function seamlessly within Service and Repair.
Use the Service Order header area to enter up to three user-defined codes, which allow you to record information such as the level of technician expertise required for a service order.
Note that the Service and Repair feature does not support the following: service contract management and billing, preventative maintenance, technician time management and analysis, or warranty tracking and claims to manufacturer.
Inventory Balancing. This feature is a purchase option for multi-store users that allows you to easily move overstock from one store to another. While creating a purchase order in the Purchasing and Receiving window, you can view overstock quantities available in other stores, enter the amount of overstock you want transferred, and with one button tell the system to automatically generate the transfer(s) required to move that stock to the requesting store(s). Additionally, the new Inventory Balancing Report (RIB) can be run by store to identify items that are understocked in that store, and then look at other stores (specific store, ALL stores, or Store Group) on the system to determine if there is any overstock. Then based upon a set of rules, it moves that overstock by automatically generating transfer(s).
Electronic Check Conversion (ECC). ECC allows ProtoBase users to process checks in a much more efficient manner, resulting in lower processing costs, faster processing, reduced paperwork, and quicker access to funds—all guaranteed. ECC simplifies cash management and allows you to consolidate bank accounts, since you are no longer required to physically deposit checks at a bank.
When a consumer pays with a check at POS, the cashier scans the check through a Magnetic Ink Character Recognition (MICR) scanner device, which captures checking account information. If you have a MICR supported printer, upon completing of the ECC payment the printer prints Void/Void/Void across the face of the check. If you use a stand-alone MICR device, the cashier must stamp "VOID" on the check using a hand-stamp. The cashier then returns the check to the consumer, who signs a receipt that authorizes electronic payment and serves as a record of the purchase. ECC then uses the information to automatically initiate a debit from the consumer's bank account. The funds are typically moved within 48 hours of the purchase. Actual funds transfer timing is based on the terms of your ECC agreement with your vendor.
iNet 2.0. Epicor's suite of electronic commerce products collectively known as iNet have been completely redesigned so that they now include countless tools for customizing your e-commerce. iNet allows you to create an online store front, communicate with suppliers and customers online, as well as automate the maintenance of information such as item and catalog detail as well as price changes. While Eagle is a fully networked application, it also fully leverages the internet to let you increase revenue as well as customer satisfaction. Working in concert with Document Management, the Eagle electronic commerce applications enable you to leverage your system investment and put your business in a position to thrive in today's robust online marketplace.
Enhanced Lead Times. This new feature enables the system to keep a history of the actual lead time for every receipt of an item. This information allows the Order Point Report (ROP) to calculate more accurate order points. It also allows the system to assign more accurate Due Dates on purchase orders.
Sending the PO to the Vendor (by Transmitting, Emailing, Faxing, or Printing) sets the "Date Sent to Vendor" which starts the "clock" for lead times of that PO. Then either manually marking the PO as "On Dock" or beginning the receiving process sets the "Date Receiving Started" which stops the "clock" for the lead times that will be recorded for that PO. Some of the key features of Enhanced Lead Times include:
More accurate due dates on purchase orders so that you have a better idea about when a particular item will be received/available on a given PO. When you create or maintain a PO in Purchasing and Receiving or the Suggested Order Report (RSO), the Due Dates on the PO will be based upon historical lead times.
Tracking Average Lead Time. In Inventory Maintenance on the Stocking tab, the “Additional Ordering Info” hyperlink displays the new Average Lead Time field, which indicates the average of the recorded lead times for that item across all vendors.
Lead Time History which you can use as a decision point in choosing whether or not to do business with a vendor.
More accurate order points due to the use of the item-level averaged historical lead time. Use the new option L "Use Enhanced Lead Times" when running the Order Point Report (ROP). Option L uses the average store/item lead time in the calculation of a new order point and maximum stock level for an item.
Ability to exclude by Vendor, or even a specific PO, having the actual lead times used in the calculation of Order Points or PO Due Dates. The lead time history gets recorded but gets flagged as Use = No.
Gift Card Giveaway. If you use Gift Cards or In-Store Gift Cards, use the Gift Card Giveaway feature if you want to issue a free gift card to customers who reach a designated purchase threshold. For example, you could set up a giveaway for customers who spend over $100 so that they receive a $10 gift card. This feature also supports a percent instead of a specific amount. For example, you could offer 20% of purchase back in a gift card (maximum of $200). With either method, the free gift card is automatically added to the transaction and a trade discount for that same amount is applied to the transaction, so that the subtotal remains the same. Note: if you choose to use the Gift Card Giveaway feature, you should also use the Returns Validation feature so that if a customer returns an item(s) that helped them earn a free gift card, the system will automatically reduce the amount of the return by the amount of the free gift card the customer received.
Note the following limitations of this feature:
The giveaway begins as soon as you complete the setup, and ends if/when you clear the setup function. In other words, currently there is no Begin and End Dates in the setup function.
On saved transactions (Order, Special Order, Service Order, or Estimate), currently the gift card reward is applied when the transaction is invoiced (rather than when the transaction was created) and is based upon the giveaway rules in place at that time.
Option 8942 “Returns Validation - use net return price?” should be set to Yes. This ensures that when an item is returned, the system will prorate the trade discount to the item the customer is returning.
New option 8942 “Returns Validation - use net return price?” This option only applies when Option 8305 "Merchandise Returns Validation on System" is set to Yes. Set option 8942 to Yes if you want discounts given from the Totals screen on the original sale (trade discount and/or immediate terms discount) to reduce the price of returns. Otherwise set this option to No to post returns with the price from the original sale. When determining the price of a return using a prior sale, if this option is set to Yes and the original transaction had a totals trade discount or immediate terms discount and the item being returned was trade-discountable, the system will prorate the trade discount to the price of that return.
New column in the Daily Journal Viewer. A new column for "Store Account Opened" has been added to this viewer.
New option 9385 "Append Special Order Items to specific Purchase Order(s) Now? Prompt." This option controls the prompt that displays when totaling an Order or Service Order (COM users) or on a Special Order (Advanced Special Order users) that has special order items linked to a purchase order. Answering Yes to the prompt causes the items to immediately append to the linked purchase order. Set this option to Yes if you want the answer to default to Yes. Set to No if you want it to default to No, e.g. if clerks typically need to make modifications (such as a cost change) to special order items on an Order, Special order or Service Order transaction before appending to the linked purchase order.
RDI new option C “Create Defective POs.” Use the new option C on the Daily Inventory Update Report (RDI) to create defective purchase orders during the day instead of waiting for the RDI option F that runs in your end-of-day queue. When you use option C, the system creates defective POs for defective returns/exchanges done since the last time RDI option F or C was run.
New option 3123 “Value to use when WinMCR "Adding Name Allowed" flag is blank.” This option determines the value for the Adding Name Allowed field in Customer Maintenance when it is blank (you access this field by clicking the POS hyperlink on the Main tab). Set this option to Yes if you want to allow clerks to add contacts in POS for the majority of your customers. Then, for any exceptions, change the Adding Name Allowed field in Customer Maintenance to No. Set this option to No if you don't allow clerks to add contacts in POS for the majority of your customers. Then, for any exceptions, change the Adding Name Allowed field in Customer Maintenance to Yes.
New option 5166 “Default for the Print field in the Total's <Save As> dialog?” This option is for Customer Order Management (COM) users. Set this option to Yes if you want the Print question in the <Save As> dialog to default to Yes. Otherwise, set this option to No so the Print question defaults to No. Set to X to force No as the default with no ability for the clerk to select Yes. Choosing X means the clerk can't print saved orders, quotes, or suspended transactions. This option is only relevant when option 8203 "go to tenders screen when totaling an order" is set to Yes.
Cash Drawer Balancing enhancements.
Existing security bit 718 “Show expected cash amount when balancing cash drawer” now not only applies to cash drawer balancing in POS (using No Sale menu option K), but it now also controls viewing the expected amounts in the back office Cash Drawer Balancing Viewer (CDB).
New security bit 912 “Allow user to view/change other users in Cash Drawer Balancing Viewer.” Set this bit to Yes if you want the user to be able to view and change entries for other stores/terminals/clerks using the Cash Drawer Balancing Viewer. Otherwise, set this bit to No.
These two security bits (718 and 912) were created to support the following workflow: When finished for the day, cashiers take their drawer to the back office where they physically count it. They then update their counted cash quantities using the Cash Drawer Balancing (CDB) Viewer. Their security is set to prevent them from seeing the expected cash amounts (security bit 718 is set to No) and from seeing the cash drawers for other clerks (security bit 912 is set to No). Once cashiers have updated their "actual amounts," marking them <All Done>, managers can review them, make any necessary revisions, and mark them as <All Done> a second time which updates the Approving User column to that manager’s login.
If you set these security bits to No and option 5419 "Accumulate and Print Cash Drawer Totals By Clerk, Terminal, or Store" is set to Clerk, then only the current signed-on user's cash drawer displays in the CDB Viewer. To allow a clerk to count only their drawer in the back office using the CDB Viewer, set security bits 708 "Access cash drawer balancing viewer" and 709 "Change allowed in cash drawer balancing viewer" to Yes, and set bit 912 to No.
If a manager with security bit 912 set to Yes clicks the <All Done> button in the CDB Viewer, the new column “Approving User” is populated with the Approving manager's login code. If multiple managers approve a count, the last approving manager’s login code stays in the column. If a cashier (without the above security bits) goes back into a count to make further changes, the Approving User column is blanked out once they click <All Done,> to reflect that the change hasn't been approved by a manager.
New option 9281 “Require zip code (or other information) for cash customers.” Place a check mark next to each field in this option that you want to be required whenever the cash customer information window displays in POS. For example, if you want to request the customer’s zip code in POS, scroll down in the list and click the check box next to Z for Zip Code. Only the selected field(s) display in the cash customer window. If you don't select any fields in this option, then the cash customer window is governed by option 9280 "Required fields in POS Cash Customer Information window."
This option applies when the transaction's customer has the "Prompt for Cash Customer Information" field on the Misc tab of Customer Maintenance set to Yes, and there are no exceptions in the transaction that require more information about the customer. If there are exceptions, the Cash Customer Information window is governed by option 9280 "Required fields in POS Cash Customer Information window," not by this option.
Possible exceptions where option 9280 applies instead of this option:
Option 5494 "Require cash customer information on a return" is set to Yes and the transaction has a return
Special order transaction
Layaway transaction
Tax exempt transaction (when option 5472 "Tax Exemption - Applies to which customers?" is not set to N)
Transaction contains a special item type. So, if the Tally flag is set to A, P, R, S, T or X and option "Default Criteria for Purging Special Sku's" is not blank.
New option 9379 “Prompt for price override reason?” Set this option to Yes if you want to require the clerk to enter the reason they have overridden the price (regardless of whether a manager override is required to change the price). You pre-define the override reasons in option 9380 “Add/change user-defined price override reason codes.” The code for the override reason displays in the Item User Codes column of the QuickRecall Viewer with Details checked, and in the User Codes column of the QuickRecall Document Viewer. Note: this option does not apply when posting an item that has the Keep Prices field in Inventory Maintenance set to N, nor does it apply to changing the price on a Bill of Materials (BOM).
Tax exemption enhancement. With option 8225 "Tax Exemption-Applies when?," you can now set the tax exemption statement and signature requirement for a non-taxable customer. This option only applies if option 5472 "Tax Exemption-Applies to which customers?" is NOT set to N. You must also set up option 8227 "Tax Exemption - Applies to what items?" From the following list, select the choices that apply to your business needs:
Select N to require the tax exemption when the <No Tax> key is used to post a normally taxable item as non-taxable.
Select S to require the tax exemption if the transaction's tax code is the one specified in option 8226 "Tax Exemption-Specific Tax code."
Select T to require the tax exemption if the customer's Taxable field in Customer Maintenance is set to No. Note one exception: if the customer's Taxable field is set to N and an expired resale code causes the transaction to be changed to Taxable (when option 9285 "Expired Resale Code Action" is set to T); in this case, the tax exemption will not be required.
Select O to require the tax exemption if the item posted is on the customer's Tax Override Plan AND the tax code on that plan has a 0% tax rate AND option 3573 "Post item(s) as non-taxable when item level tax code's rate is 0%?" is set to Yes.
Note: If you select S, then any time a transaction's tax code matches option 8226, the tax exemption statement and signature are required, regardless of what items are sold or their taxability.
New columns in QuickRecall.
Trx Sales Rep – (relevant only if option 9299 “Show Sales Rep field in POS” is set to Yes) The Sales Rep for the transaction if one was entered.
Item Sales Rep – (relevant only if option 9299 “Show Sales Rep field in POS” is set to Yes) The Sales Rep entered at the line-item level. If one was not entered for the item, then this column will contain the transaction-level sales rep if one was entered.
UPC – The UPC that was scanned to post the item, or the UPC manually typed into POS posting and matched by smart lookup.
Server Date – (for users with option 9264 “Multiple time zones on system” set to Yes) The date and time of the transaction in "server" time.
Server Time – (for users with Option 9264 “Multiple time zones on system” set to Yes) The date and time of the transaction in "server" time.
Scanned Image? – (for Document Scanning users) This column populates only if the new option 8614 “Check for Scanned Images in QuickRecall” is set to Yes. If so, then as the QuickRecall grid loads, if a transaction has scanned images associated with it, this column displays a "Yes" hyperlink, which when clicked displays that invoice's scanned image(s).
Image? – (for Document Management users) If a transaction has an invoice or receipt in the Document Archive, this column displays a "Yes" hyperlink, which when clicked displays the image of the receipt and/or invoice. The hyperlink is the same as the Image hyperlink seen on the displayed transaction, except in this case you don't have to display the transaction first.
Zip Code
New option 9347 “List Price Cost Formula can be entered in Cost field.” This option allows a clerk to enter a list price and formula to calculate the cost of an item in POS. The clerk inputs the list price from a manufacture's catalog and uses the discount percentage the manufacture allows for purchasing so that the system calculates the cost of the item being posted. The formula is "L nnn.nn - nn.nn%". The L tells the system this entry is a list price formula. The nnn.nn represents the List price and the nn.nn% represents the discount percentage. For example, if the clerk enters L 100.00 -40.00% in the cost field, when the item is posted the system will calculate and post the cost of 60.00. Security bit 543 "(MO) Ability to change the cost of an item" is respected when using the formula in a cost field. Additionally, with option 8451 "Pricing codes can be entered in Price field" set to Y, the clerk can have the system calculate a price using a gross profit percent and the new cost. For example: Enter G26% in the price field and L100.00-40.00% in the cost field. Once you press enter to post the line item, the system first calculates the cost which would be 60.00 and then the price of 81.08 (60.00/.74). Also see new option 9348 "Display tool tip for List Price Cost Formula" to determine if the tool tip displays when in the cost field.
Serial Number Tracking Enhancement. To support the now longer serial number (up to 30 characters), POS now supports scanning the barcode representation of a serial number that is longer than 14 characters in the posting area’s SKU field. Scanning the serial number will look up the item to which the serial number is linked, post that SKU for a quantity of 1, and post the serial number descriptor.
Ability to access the Document Archive Viewer in POS. Document Management users (option 3350 "Eagle For Windows Document Imaging on system" is set to Yes) can now see all types of archived documents for a customer from POS. In the posting area, press <Menu> and use the new choice V “View Archived Documents.” The system displays the Document Archive Viewer, carrying in the current transaction’s customer/job (if not equal to the value in option 330 "Default Customer Number") and displays the list of archived documents for that customer/job. This includes documents from all origins – scanned (if you have Document Scanning) and printed/emailed/faxed from POS. If the current customer is the Default Customer, the viewer displays with blank customer/job, and you must enter your selection criteria and press <Refresh>.
For access to Posting Menu choice V, the following must be true. Otherwise, this choice displays but is greyed out.
The Eagle server must be running Eagle OS
Option 8112 “Document Archive Viewer Type” must be set to 2
Security bit 679 must be set to Yes
Ability to see scanned documents attached to a SKU from POS. This feature requires Document Scanning (option 49” Eagle for Windows document scanning feature on system” is set to Yes). In the posting area with a value entered in the SKU field, press the <Menu> button and use the new choice W “View Scanned Documents for SKU” to see any scanned documents attached to that SKU.
For access to Posting Menu (SKU Entered) choice W, the following must be true. Otherwise, this choice displays but is greyed out:
Server must be running Eagle OS
Option 8112 “Document Archive Viewer Type” must be set to 2.
Security bit 753 must be set to Yes.
Note: Because you now have direct access to the Document Archive Viewer from within POS, new security bits 921 “Document scanning feature - Access confidential customer information” and 922 “Document scanning feature - Access Vendor/PO scanned documents” allow you to limit the type of documents a POS clerk can see using this viewer (from any access point, not just when launched from POS). See the Windows Security Enhancements section of this document for more information about these new bits.
Customer Price List enhancement. The customer price list that was added on Release 19 now has an additional column "Customer Price Src (POS)+." If option 900 “POS Display Price Code” is set to Yes then this new column displays the source of each price when it is not simply the item’s retail price. For example, it may show Category Plan, Open Quote, Matrix, List, Cost, Promotion, etc.
Increased security to avoid errors in Customer QuickAdd. For customers using Customer QuickAdd in POS (option 5432 is set to Y), new security bit 923 “Add customer in Customer QuickAdd with cust# other than default template” was designed to protect against the clerk inadvertently adding an account or adding the wrong information to an existing account. Epicor strongly recommends that this bit be set to No (use the template customer only) for the following reasons:
If the clerk selects Menu option 8 to make a change to an existing account, for example to update the phone number or enter an email address, he or she could accidentally press <Add> instead of <Change> which would add a second account for that customer, instead of changing the existing account. Setting this bit to No will protect against this mistake.
If the clerk is using the customer drop-down to locate an account in POS and doesn’t find the account, he or she could accidentally select the wrong one from the drop-down. They then could press Menu 8 to add the new customer, unknowingly carrying in the existing customer's information. Then they enter the new customer's information and press <Add>. For the fields not included in the Add dialog, the system uses the previously-displayed customer’s information instead of using the information from the template customer.
New option 5157 “Prompt clerk to reprice status R transfers when recalled.” For multistore users. If this option is set to Yes, when a clerk recalls a status R (Request) transfer while locked into the "From Store" and the clerk proceeds to the posting screen, the system prompts the clerk with the message "Do you want to reprice this transfer? Yes/No" which defaults to Yes. If the clerk selects Yes, the system automatically reprices the transfer using Reprice Method Y, Price Indicator E, and Recost Method A (average cost). If the clerk selects No, then what happens next depends on new security bit 941 “(MO) Allow change of Reprice Transfer prompt to N.” If the clerk has this bit, they can continue without a manager's override. If the clerk does not have this bit, they must obtain a manager's override to proceed without repricing the transfer.
New option 9441 “Include Customer Name In Title Bar.” Set this option to Y if you are using multiple POS sessions and you would like the customer name added to the title bar of the POS sessions to aid in distinguishing between sessions in the Windows Taskbar. Set this option to N if you would like the title bar of the POS session to not contain the customer name.
New options to enforce minimum age requirement for a purchase. Options 9412-9414 and 9416-9418 are two new sets of options that help enforce the minimum age required to purchase certain items. The two sets of options allow you to set up two different item types, known as type 1 and type 2. For example, type 1 might be items that require a minimum age of 18 (e.g., cigarettes), and type 2 might be items that require a minimum age of 21 (e.g., alcohol).
You will use option 9419 "Post minimum age birth date as comment" to tell the system if the customer's birth date should be posted to the transaction as an internal (non-printing) comment or a external (printing) comment. You'll use option 9420 "Post underage comment when minimum age requirement is not met" to tell the system if a comment recording the fact the customer was not old enough to buy an age restricted item should post to the transaction.
Options 9412-14 are for type 1 items and are described below. Note that the same descriptions apply to options 9416-18, which are for type 2.
Option 9412 "Minimum Age to purchase type 1 items." Enter the minimum age required to buy items identified as "minimum age type 1" items. When an item identified as this type of item is sold at Point-of-Sale, the clerk will be prompted for the customer's birth date. The system uses the birth date and this option to determine if they are old enough. If they are not old enough, minimum age type 1 items cannot be posted. Use options 9413 and 9414 to tell the system what items are subject to this minimum age requirement. Use options 9419 and 9420 to tell the system if the customer's birth date should be posted to the transaction and if so, whether to post it as an internal (non-printing) comment or a external (printing) comment. Note: Set this option (9412) to 0 if you are not using this feature.
Option 9413 "Use Code position to identify Minimum Age type 1 items." Use this option in conjunction with the value specified in option 9414 "Code value that identifies Minimum Age type 1 items" to identify items subject to this minimum age requirement. You can select any Use Code position:
User Codes position 1, 2, 3, or 4
Expanded A User Codes position 1, 2, 3 or 4
Expanded B User Codes position 1, 2, 3 or 4
Expanded C User Codes position 1, 2, 3 or 4
Expanded D User Codes position 1, 2, 3 or 4
Selling Minimum Age items in POS. The first time a minimum age type 1 or 2 item is sold, the clerk is prompted to enter the customer’s birth date (they are only prompted for the birth date once per transaction). If the customer is clearly old enough to make the purchase, then the clerk still has to enter a birth date and should use something easy like 7/7/77. The birth date entered posts to the transaction as an internal or external comment depending upon the setting in option 9419.
If the customer isn’t old enough to purchase a type 1 and/or a type 2 item, each time one is attempted to be posted the clerk will be given this response: "Age restricted item. Item cannot be sold to this customer." A comment indicating the customer wasn’t old enough to purchase optionally posts to the transaction depending upon the setting in option 9420. When a minimum age item can’t be sold, the only information that posts (optionally based on the setting of option 9420) is the comment "Minimum age not met – not sold." Note that there is no indication of the item that they attempted to buy.
Note: SKUS that have a user code to indicate they are a Minimum Age item are considered "special SKUs," thus the amount of time a transaction with a minimum age SKU is kept in QuickRecall is determined by the MQK setting “Default Criteria for Purging Special SKUs” (option 3 in Options Configuration).
Longer Serial Numbers. The maximum length of a serial number has been changed from 14 to 30 characters. Note the following:
If you have a ReQuest (RQ) procedure or ODBC query for serial numbers, you will need to recreate them. For RQ, your existing routine selects UPC Numbers where UPC Source matches A (available serial #’s) or X (sold serial #’s). There is now a separate set of fields for Serial Numbers in INVENTORY->VARIOUS INVENTORY INFORMATION and the old method using UPC Number no longer works. The new fields are: SERIAL-NUMBER, SER-SKU, SER-REFERENCE, SER-SOLD-FLAG, AND SER-STORE. No selection is required since this list contains only actual serial numbers.
If you have been entering serial numbers longer than 14 characters with the leading “+” and remainder in the serial # Reference field, you no longer need to do this. When you install Release 19.1, the system automatically concatenates the two parts of the serial number together into the new expanded serial number field, and clears out the Reference field.
QuickRecall has the new Misc Menu option S “Search for Serial Number” for looking up a sold item by its serial number that is up to 30 characters long. You can scan the serial number if it is available – .ie. if the item is being returned and they want to look up the original invoice on which it was sold. Note that you can still enter the serial number into the SKU lookup field in the QuickRecall Viewer, but that method is limited to serial numbers that are not longer than 14 characters.
New column in Quantity Break and Price Matrix Maintenance. Quantity Break Maintenance (MQB) and Price Matrix Maintenance (MPM) now have a new column called "Note" where you can enter the type of item(s) or the type of customer(s), respectively, to which the code applies. You can enter up to 42 characters for each description.
New column in Modify Item Promotion. The Modify Item Promotion (MIP) window has a new column for Future Order Quantity (FOQ).
Copy supporting files from one store to another. You can now use COPYRECS to copy supporting files such as departments, classes, etc. to your other stores. This feature is particularly useful when creating Kits or BOMs (Bills of Material)that you want to exist in all stores. Simply enter ALL in the "To Store" field when running COPYRECS. Note that selecting ALL does not apply when copying inventory records from one specific store to another specific store, but only when copying supporting files.
Print pending locations from the Physical Inventory count file. The Physical Inventory Report (RPI) has been enhanced so that even if you do not use location codes (option 6 "Always use LOCATION code" is set to N), you can still enter a Location in the From/To fields on the RPI when reconciling or finalizing counts. The report will include any counts where the from/to Location matches at least one of the three locations in the count record.
Inventory Labels enhancement. You can now include Old Retail as a field on an Inventory label.
Multiple Order Points (Stock Transfer Balancing users only). The system now supports up to five Order Points (and Maximum Stock Levels) for an item. Requires option 1057 “Multiple Order Points on System” be set to Yes. For example, you may want to set a static order point that corresponds to shelf/rack space for an item, plus you may want to maintain a true order point based on sales for that same item (perhaps generated from running ROP).
On the stocking tab of Inventory Maintenance you can click the Order Point field label which is now a hyperlink to see and change these additional Order Points. You can update the additional Order Points manually in this dialog or by running the Order Point Report (ROP).
There is a new field in ROP called “Calculate Order Point” on the Options Page which allows you to select which Order Point is updated by that run. As with today’s ROP, the corresponding Maximum Stock Level for the selected Order Point will be adjusted (or not) based on how you set the Max Stock Level field in ROP.
There is a new ROP Method 4 that allows you to "Copy Order Point from Current Order Point." For example, if you run ROP with Calculate Order Point set to "Order Point/Max Stock Level" and Copy Order Point from Current Order Point set to "Additional Order Point A," the values of Order Point A and Max Stock Level A are copied to the primary Order Point and Max Stock Level.
There is a new field in the Suggested Order Report (RSO) called “Use Order Point” that determines which order point/max stock level to use for the order calculation.
New columns in the PO Viewer. For Enhanced Lead Times users, these new columns include: On Dock (this column contains "On Dock" if the PO has been marked as On Dock using Misc Menu option O), Date Receiving Started (the date the PO is marked as On Dock, when you begin receiving the PO in Eagle Mobile Receiving, or when you press Receive (F2) on the PO in the Purchasing and Receiving window.
Larger part number column on laser RRP. For Long SKU users, a new format is available for printing laser receivers in the Receiving Report (RRP). In this new format, the SKU column now prints up to 30 characters, and it also has a Location column. The "Mfg #/Special" field now prints as a detail line if an item has something in this field on the PO. In addition, you can now double-space a laser receiver.
Pending Transfers Viewer enhancements. (Stock Transfer Balancing users only)
The term "Session ID" has been changed to "Batch ID."
New toolbar button <Change / Shift F5> that allows you to change the quantity you want to transfer for the highlighted line. This requires security bit 920 “Allow Change of Transfer Quantity in Pending Transfers Viewer.” When you press <Change>, a dialog box displays the SKU being transferred, the store to which it is being transferred, the overstock quantity in the "from store," and a field that allows for you to enter a new transfer quantity. Pressing OK/Enter posts the new quantity on the pending transfer. A quantity of 0 can be used to cancel a transfer.
New toolbar button <Assign/F8> (same as option A in the Misc Menu) allows you to assign a new Batch ID number to the checked rows in the grid. For example, you can finalize a subset of the pending transfers that an RIB created by first assigning the checked items a new Batch ID using the <Assign> button, and then using the <Finalize> button to finalize just the items with that new Batch ID. Or, use the <Assign/F8> button to group several sessions created by Stock Transfer Balancing in Purchasing together and finalize at the same time. This combines items that had the same "from" and "to" store into one transfer.
Note: If you launch the Pending Transfers Viewer by entering VIEWPT in the Eagle Browser's Launch bar (or selecting Pending Transfers Viewer from the menu), the From Store, To Store, and Source default to ALL. If you launch the viewer by entering VIEWRIB in the Launch bar (or selecting Inventory Balancing Transfers Viewer from the menu), the Source field defaults to RIB and only shows batches created from the RIB report, and the From Store and To Store default to the Lockin store. Thus, VIEWPT and VIEWRIB display the exact same viewer but with different selection criteria defaults.
Note: When the selection criteria’s From Store and To Store are the same, the viewer shows all pending transfers coming to this store, and all pending transfers going out of this store.
Note: When you press<Finalize>, all items whose Batch ID matches the Batch ID of the current row which has focus are finalized, whether they are checked or not, or even if they are not showing in the grid (i.e., they are filtered out).
Two new columns in the Customer Viewer. Resale Code and Resale Expiration Date are now included in the Customer Viewer. These columns are useful for creating a list of customers whose resale codes are about to expire so you can inform the customers of this fact.
Customer Code Update (RCCU) enhancements. You can now update the following newer fields.
“Printing Plan” which is located on the Misc page of RCCU, but is only visible if option 7732 ” Printing Plans on system” is set to Yes.
"Adding Names Allowed," "Job’s POS Adders," "Post POS Adders," and "Subtotals on Invoices" which are all located on the new Misc 2 page of RCCU.
Customer Maintenance enhancement. You can now control the ability to make changes for each tab in Customer Maintenance. See the new security bits 891 through 896.
Eagle Mobile Enhancements.
For Central Distribution Receiving users only (option 9081 “Centralized Distribution on System” is set to Yes), Receive by PO now checks for central distribution purchase orders, and allows you to distribute the received quantity across all stores on the purchase order.
If you search for and select a purchase order that has lines for multiple locations, and the PO is currently not a central distribution PO but Centralized Distribution is on the system (option 9081 is set to Y), Eagle Mobile asks if you want to change the purchase order to central distribution. Note: You cannot change the Central Distribution field back to N from the Eagle Mobile application.
When receiving a central distribution PO, after scanning an item, the system distributes the quantity received across all locations on the purchase order. If you re-scan the same item, the total received displays at the bottom of the screen. If you click Receive again, it adds to the total quantity received and redistributes the new amount across all locations. As with non-central distribution purchase orders, you have the option of replacing the total received instead of adding to it. Simply go into the Details menu and select “Replace Qty Received.”
To view all stores on the purchase order for a given item, scan the item and then click the “Multi” hyperlink. This displays all stores/lines for that item as well as the quantity ordered and the quantity being received for each location. Note that you can't modify the received quantity at a per-store level from Eagle Mobile; you must use an Eagle terminal.
Security for changing a PO into a central distribution PO is based on the store in the header of the purchase order. You are not required to have security for all stores on the purchase order.
Note the following:
You are not allowed to add items to a central distribution purchase order. All other functionality, such as capturing UPC’s and printing labels, work as it did for non-central distribution purchase orders.
You are not allowed to next/previous through a central distribution PO, as it groups lines by item number.
Transfers are not created until you run the Receiving Report (RRP) from an Eagle terminal.
You are not allowed to receive a central distribution purchase order in the Receive by Item function.
Receive by PO performance improvements. In previous Eagle Mobile versions, the average time to post a receipt and re-display an item was around 4 seconds. This now takes only 2 seconds.
Physical Inventory now respects security bit 887 "Change/Delete physical inventory counts for other users." If a user does not have security bit 887 and scans an item that has been counted by another user, they will receive an error.
PCI security changes and incorporation of PCI patches. In addition to the security changes and patch incorporation, you will receive a checklist for you to review to ensure that you are PCI compliant.
Document Scanning improvement for invoices from Offline POS. If you use barcode recognition software, the system now embeds within the barcode a code for Document Scanning that indicates that the invoice is coming from offline POS. Then, when you scan the signed invoice into Document Scanning, the system recognizes that it's from Offline POS and matches it to the permanent document number so that the signed invoice can now appear on the customer’s A/R statement.
Change to existing option 8125 “Use High-Capacity grid in viewers?" This option has a new setting H "Default to High-Capacity but allow the user to select Standard." This setting allows you to default viewers to High-capacity, but set other viewers where you do quick grid data entry to Standard in order to prevent the unexpected results you can see when using high-capacity viewers. The viewers to set to Standard if you do quick grid data entry are: Item Price Change (IPC), Physical Inventory Posting (PIP), and Modify Item Promotions (MIP) windows. In these viewers you can save the default grid to use the standard mode rather than the High-Capacity mode.
New Price Checker options for Loyalty pricing. If you use a loyalty program (True Value, Ace, Do it Best, or on-system Loyalty), you can set option 9437 "Show Loyalty Promotion Price on Price Checker" to Y to allow the Price Checker device to show the Loyalty Price. If desired, you can change option 9438 "Show Loyalty Promotion Price Label on Price Checker" so that it displays the label you want rather than the default label of "Loyalty Price." For example, you could enter the label “Rewards Price” in option 9438.
New COR option to reduce refresh time. Use new option 9345 “Offline Database Refresh Exclusions” to reduce the amount of time it takes to refresh the offline database by choosing to exclude certain types of data from the database. Select L to exclude loyalty customers whose Standard Selling Price is Retail, select A to exclude information for lookups by alternate part number in Offline POS, select M to exclude information for lookups by manufacturer part number in Offline POS, or select U to exclude information for lookups by UPC in Offline POS.
Various utilities are now available from the Eagle Browser. You can now access the following legacy utilities from the Eagle Browser: Editor, Backup File Maintenance (MBC), Shutdown, and QuickRecall Transaction Count (QRTRXCNT). Editor, Shutdown, and QRTRXCNT all require security bit 91 for access. MBC requires bit 388.
Windows version of RUNQ is now available. Simply type RUNQ in the Launch bar of the Eagle Browser. Use RUNQ to run a report queue now, or at the end of the day. Requires security bit 79.
Display backup media rotation. Simply type DBR (Display Backup Rotation) in the Launch bar of the Eagle Browser to display a window telling you the next backup set to use, as well as backup history. Requires security bit 91.
The following are the new security bits for Release 19.1.
Bit 887: " Change/Delete physical inventory counts for other users." This new bit controls the ability for a user to change or delete a count entered by a different user. Set this bit to No to disallow changing or deleting a count done by someone other than the user who entered the count. This security bit is checked in Windows Physical Inventory Posting (PIP) and Eagle Mobile Physical Inventory. Note: Legacy/Network Access PIP and QPIP do not check for this bit when changing a count; therefore you should set security bit 890 "Access legacy physical inventory functions PIP/QPIP" to No.
Bit 809 "Ability to change cost in WinMRV." When this bit is set to No, the cost field displays in the grid, but the user will not be able to change it. When this bit is set to Yes, you must also set security bit 319 "Add/Change previously received purchase orders" to Yes.
Bit 891 "Ability to make changes on the Main tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Main tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bit 135 "Change customers" to Yes.
Bit 892 "Ability to make changes on the Credit tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Credit tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bit 135 "Change customers" to Yes.
Bit 893 "Ability to make changes on the Dept tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Dept tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bit 135 "Change customers" to Yes.
Bit 894 "Ability to make changes on the Payment tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Payment tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bit 135 "Change customers" to Yes.
Bit 895 "Ability to make changes on the Misc tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Misc tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bit 135 "Change customers" to Yes.
Bit 896 "Ability to make changes on the Notes tab of Customer Maintenance." Setting this bit to Yes allows the user to change the fields on the Notes tab of Customer Maintenance. Note: When setting this bit to Yes, you must also set security bits 135 "Change customers" and 309 "Add/Change/Delete on Notes tab of Inventory, Customer, and Vendor Maint" to Yes.
Bit 906 "Allow Order Verification Exceptions Report." Ability to access the Order Verification Exceptions Report (ROV).
Bit 907 "Allow Inventory Balancing Report (RIB)." Ability to access the "Inventory Balancing Report (RIB).
Bit 908 "Access/Update Order Verification." Ability to access and update Order Verification on the Eagle Mobile device.
Bit 911 "Allow Service Orders in POS." Applies when option 1093 "Service and Repair on System" is set to Yes. Controls the ability to create or recall a Service Order. When set to No, the selection for "Service Order" on the Start Transaction/F2 menu will be grayed out. In addition, if option 102 "Return to Header Screen After Each POS Transaction" is set to S, the user is told this is not allowed.
Bit 912 "Allow user to view/change other users in Cash Drawer Balancing Viewer." Set this bit to Yes if you want the user to be able to view and change entries for other stores/terminals/clerks using the Cash Drawer Balancing Viewer. When this bit is set to No and option 5419 "Accumulate and Print Cash Drawer Totals By Clerk, Terminal, or Store" is set to Clerk, then the only cash drawer that displays in the Cash Drawer Balancing Viewer is the drawer for the current signed-on user. To allow a clerk to count only their drawer in the back office using the Cash Drawer Balancing Viewer, set security bits 708 "Access cash drawer balancing viewer" and 709 "Change allowed in cash drawer balancing viewer" to Yes, and set this bit (912) to No.
Bit 919 "Disallow reversal of Transfer transaction." Set this bit to Yes if you want to prevent a user from reversing a transfer transaction. Set to No to allow a user to reverse a transfer transaction.
Bit 920 "Allow Change of Transfer Quantity in Pending Transfer Viewer." Set this bit to Yes to allow the user to change the transfer quantity when viewing pending transfers.
Bit 921 "Document scanning feature - Access confidential customer information." This bit is only valid if Document Scanning has been purchased (option 49 is set to Yes) and the Document Archive Viewer Type (option 8112) is set to 2-Integrated. If this bit is set to No, the user cannot see documents linked to a customer that has a type of Mixed or Other. If set to Yes, the user can see all documents linked to a customer in the Document Archive Viewer (note: the user must also have bit 753 or 679).
Bit 922 "Document scanning feature - Access Vendor/PO scanned documents Security Bit: Yes/No This bit is only valid if document scanning has been purchased (Option 49) and option 8112 (Document Archive Viewer Type) = 2 (Integrated). If this bit is set to No, the user cannot view scanned documents linked to vendors or purchase orders. If set to Yes, the user can see all documents linked to a Vendor or Purchase order (note: the user must also have bit 753 or 679).
Bit 923 "Add customer in Customer QuickAdd with cust# other than default template." This bit applies when Option 5432 "Allow quick add of customers/jobs in POS" is set to Yes. When this option (923) is set to Yes, adding a customer in Customer QuickAdd in POS can be done with either the template customer or any existing customer. When set to No, adding a customer in Customer QuickAdd in POS requires the add to be done using the template customer. Keep in mind that whatever customer is displayed at the time you press <Add> determines how the fields not contained in this dialog will be set.
Bit 941 "(MO)Allow change of Reprice Transfer prompt to N." This bit applies when option 5157 "Prompt clerk to reprice status R transfers when recalled" is set to Yes. Set this bit to Y to allow the clerk to change the Reprice Transfer prompt to No without a manager override. Set to No to require a manager override if changing this Reprice Transfer prompt from the default of Yes to No.