What's New on Release 20.1What's New on Release 20.1Inventory Planner is a new inventory application that allows you to improve the accuracy of your forecasting, build broad strategies for inventory levels, and easily manage exceptions, resulting in improved Order Points in your Eagle system. Key Features of Inventory Planner include:
Best Fit Forecasting allows each item to automatically utilize the most accurate forecasting strategy from pre-defined Forecasting Models based on industry standard methodologies, removing all the guess-work from defining inventory strategies
Multiple Order Points allow updating and use of four additional order points per item
Forecasting by Weeks, Calendar Months, Fiscal Months, and Retail Months
New Item Proxies allow for improved forecasting of new items by using an existing item’s usage as a proxy for a new item
Manage exceptions to global strategies using highly flexible Inventory Rules and Filters
Effective Dates allow for strategies to be in effect only during specified time periods
Service Level Calculations automatically calculate safety stock based on lead times and desired in-stock position
Starting Points management screen provides single-click access to manage plans and view performance metrics
Built-in Wizards make setup and implementation easy
Full integration with Eagle and Compass Analytics allows for easy setup, implementation, and reporting
FarmPlan enhancement. Protobase is no longer required for the FarmPlan application. It can also be used in conjunction with another Private Label program.
Pick, Pack, Ship (PPS) enhancements. These enhancements only apply if option 74 "Use Pick/Pack/Ship flow in Order Entry" is set to Yes.
D - Fill backorders by SKU/Delivery Date allocating additional QOH. The system allocates any available QOH of an item to orders where there is a backorder quantity for it. It allocates in delivery date order – oldest to newest. If you use Backorder option F (see below), then the system only allocates available QOH to that item’s backorder quantity if it can be fully filled.
F - Full shipment of item required. If this option is not selected, partial shipment is allowed (this option is only relevant when option D is also selected).
If a line item with a Picked status is partially picked, the deferred pick quantity is placed on a second line item with an On Order status instead of a Picked status, thus allowing for the release at a later date (Example: Line item released for a qty of 1000 bricks, but only 800 fit on the delivery truck. You can change the picked status line to 800 and deferring the quantity of 200 to be released and shipped at a later time).
Enhancements to "Quick Add of Non-Stock Items." The following enhancements are available to multistore users with Advanced Special Order (option 1028 "Special Orders Allowed in RPOS" is set to Yes)
If you use template SKUs to create and add non-stock items to inventory, you can now use an unlimited number of templates (used to be limited to 2500). These template SKUs can be general or specific; that is, they may be set up to represent adding items within a department, a class, a fineline, or a vendor.
You can now add non-stock items to not only the lockin store, but also a list of additional stores. To do this, use the “Add to Additional Stores” field in the “Add SKU” dialog.
You can use new option 8457 “Default store group for Quick Add of Non-Stock items in POS” if you want to enter a default list of additional stores to which the non-stock SKU can be added. This new option applies both when using template SKUs in POS posting and when adding non-stock items (using <Sell> button) from a Catalog, including user-defined catalogs (the latter requires that option 8717 "Add mode used when using <Sell> from Catalog" be set to A or S). This option determines the default stores in the "Add to Additional Stores" field in the "Add SKU" dialog. Enter the Store Group for the list of stores that you would like to have as the default. Note: The Add SKU function always adds the item to the current POS Header store in addition to the stores indicated in the "Add to Additional Stores" field. If you want the "Add to Additional Stores" field to default to all stores on the system, set this option to the store group code that contains every store on the system. If you want "Add to Additional Stores” to default to a specific subset of stores for each store, change the "Kept By" method of this option to Store, and for each store set this option to the store group code that represents the list of stores to which to add the special order item. Enter the store group with a leading G (between G1 and G999). If you leave this option blank, the "Add to Additional Stores” field defaults to the current POS Header store. You can override this default by exception in the Add SKU dialog in POS to choose a specific store, All stores, or a store group.
New option 5470 “Layaway sales - monthly sales units to update.” Select C-Created Date, or I-Invoiced Date to determine which period's sales units to update with layaway sales data. If you want to update sales history based upon the date the layaway is invoiced, set this option to "I" to update the current period sales history. If you want to update sales history based upon the date the layaway was created, set this option to "C." This option affects regular sales units, promotional sales units, and markdown sales units. Note: When set to C, if the layaway is being invoiced (final payment) more than 13 months after the date it was created, sales history for the current period is updated.
New setting for existing option 8633 “Display Customer Credit Card List only on Protobase enabled terminals.” New setting “O-only on demand” which means a customer’s stored credit cards or gift cards do not automatically display when totaling a POS transaction (on Protobase terminals). Instead, if the customer wants to use a stored payment card, the clerk can use Totals Menu option 8 “Select credit card” to view and select the stored credit card (or gift card) as the method of payment.
New option 9074 “Check the balance of stored In-Store Gift Card.” This option automatically checks the balance for a stored In-Store Gift Card on the customer account. If the balance is greater than zero, POS prompts the cashier to apply the gift card's available balance to the sale.
New option 9390 "Prompt clerk if Reserved PO should be used for other Special Orders." This new option is for Advanced Special Order users only (option 1028 "Special Orders Allowed in RPOS" must be set to A). This option determines whether the PO created for a special order item should be used for all special orders from that Vendor. For example, if PO 1001 is created using RSRV while posting a special order coming from vendor ABC, you want special orders from vendor ABC that are for other customer's to be appended to PO 1001. Y = ask and default to Yes. A clerk using RSRV to create a special order PO is asked "Use Reserved PO for other special orders?" with the answer defaulted to Yes. X = Ask and defaults to No. A clerk using RSRV to create a special order PO is asked "Use Reserved PO for other special orders?" with the answer defaulted to No. N = Do not ask. A clerk using RSRV to create a special order PO is never asked if that PO should be used for other special orders. T = Use preference on POS/Tools/Options/Special Order tab. This is the legacy behavior that has always been available, where the system uses the setting in POS/Tools/Options on each POS station. Epicor recommends you change this option to either Y, N, or X in lieu of using this legacy method of setting an option. Note: If the clerk is asked to "Use Reserved PO for other special orders" and answers Yes, the PO is created with its Order Type set to S. The S option allows clerks to add other items to this purchase order (whether from the same special order, or another special order). The PO# in the special order posting area defaults to this PO number when other items are ordered from this vendor.
New option 8708 “CPP 'Down from retail' applies to promotion price.” Setting this option to Yes means the Category Pricing Plan (CPP) Method "Down from Retail" applies the discount to the Promotion price if the item is on an active promotion, otherwise it applies the discount to the Retail price. If you set this option to Yes, CPP plans using "Down from Retail" need to have the CPP field “Inc CPP < Non-Disc/Promo Prc” set to Y or P. Setting this option to No means you don't want "Down from retail" to apply to promotion prices, but only to the Retail price.
New option 9527 "Returns Validation - Use original sale's tax code on return." On a validated return, if the tax code on the original sale (either header tax code, or line item tax code) is different from the header tax code on the return transaction, then the original tax code appears at the end of the "Original" descriptor. For example, “Orig: F44642/1 01/01/11 TX:A11” tells the clerk that the return of this item has been taxed using tax code A11.
New option 8952 “Alternate term to use for Bag/Bucket Sale.“ This option allows you to define your own term for this type of sale. If you enter a value in this option (max. of 17 characters), it is used in POS instead of “Bag” or “Bucket.” Leave this option blank to have the system use existing option 8640 to determine what term is used - “Bag” if option 8640 is set to 1, or “Bucket” if option 8952 is set to 2. Refer to option 8640 "Term to use for Bag/Bucket Sale" for more details.
New "Lowest Sell Price" field in Inventory Maintenance. This new field is on the Codes tab of Inventory Maintenance under the Additional Codes Flags hyperlink. This field can be set to a pricing indicator that represents the lowest price this SKU can be sold for in POS in any situation. L = list price, R = retail price, A = average cost, C = replacement cost, 1 = matrix level 1, 2 = matrix level 2, 3 = matrix level 3, 4 = matrix level 4, and 5 = matrix level 5. Security bit 976 “(MO) Allow selling items below Lowest Sell Price” controls if the clerk can sell an item below the lowest sell price, or if a manager override is required. The system checks for lowest sell price when adding an item, changing an item, repricing a transaction after changing the customer number associated with the transaction, or when using Copy/Reprice (F3) on the POS Big Header screen. Note: Lowest Sell Price does not apply to Transfers.
New "Max Units per Transaction" field in Inventory Maintenance. This new field is on the Codes tab of Inventory Maintenance under the Additional Codes Flags hyperlink. If desired, enter a value of 1 to 99999 to indicate the maximum quantity of this item that may be sold on a POS transaction. The new security bit 975 “(MO) Allow selling items beyond Max Units per Transaction” controls if the clerk can sell more than the specified maximum quantity, or if a manager override is required. When an item with a Max Units per Transaction is sold in POS, the system checks for all instances of that item on the transaction. If the total quantity of that item on that transaction exceeds the Max Units per Transaction, and new security bit 975 is set to No, a manager override is required. If no manager override is obtained, the item clears from the posting area. You cannot enter a fractional quantity in the Max Units per Transaction, but the clerk may post items with fractional quantities and the total will be correctly compared to the max units allowed. The system checks for the maximum units when adding or changing an item. Note that Max Units per Transaction does not apply to transactions whose source is iNet, nor does it apply to Transfers.
New option 9653 “Suppress watermark on reprinted invoices.” This option only applies to Enhanced Forms. If this option is set to yes, the watermark "REPRINT" never prints on a reprinted invoice. This option applies to all ways of reprinting an invoice, as well as faxing from QuickRecall, faxing or emailing from the Document Archive, and when printing collated invoices on statements.
Defective Item receipt enhancement. If you have option 9499 “Print defective return receipt for item returned/exchanged as defective” set to Yes, the “Defective” receipt that prints for each item returned as defective or exchanged prints the comment lines that immediately follow the defective item on the transaction. That way, the clerk can post comment lines to describe what is defective about the item, and these comments then print on the receipt being attached to the defective item.
New option 4901 “Minimum Amount to prompt for Signature on credit card approvals.” WARNING: Do not use this option unless you first verify this minimum amount with your credit card processor and ensure it is supported by your Merchant agreement. This option controls the ability to bypass the signature capture process on approvals equal to or less than this specified amount. The merchant copy of the receipt prints "** NSR based on purchase amount" in lieu of the customer's signature. Set this option to zero if you want a signature to be required for all credit card approvals regardless of amount. Note: This option does not apply to credit memos or negative sales. Also refer to Option 4900 "Signature Capture - Require signature on a bankcard return."
Daily Inventory Update Report (RDI) Option F can now print PO number for defective purchase orders. To do this, option 2810 “RDI create defective purchase orders” must be set to A or B. Previously, the RDI report only printed the first defective PO number that was created. It now prints all defective POs that are created that day for the defective returns.
Prompt for a customer signature on invoices for returned items. For customers which only have an Invoice Printer configured (no receipt printer), the system can be configured to prompt for a customer signature for returned items. The signature prints on the customer’s invoice and is of course also in the archive. To have the system prompt for the customer’s signature when at least one item has been returned and the printer is only configured for an invoice printer ,set both Options 5481 “Print a store copy receipt for returns” and 290 “Print Charge Customer on Receipt Printer?” to Yes.
Show Dynamic Promotions Pricing. Once a transaction has been totaled, you can now use Misc Menu “Show Dynamic Promotions Pricing” to see what Dynamic Promotion pricing has been applied to the transaction. Previously, this recap was only available on the Posting Menu and you had to look at it before pressing Totals. Now it is available in both – posting as well as totals.
Update kits during receiving. The Receiving Report (RRP) now has the ability to receive a kit and update the quantity on hand and average cost of the kit’s components. The new option 2831 “Receiving report (RRP) receives kit components” controls this enhancement. If you have vendors from which you order a single SKU/item that represents an assortment (a "display") of different SKUs, then you can set this up as a kit with each item in the display as a component of the kit with a kit quantity of 1. Enter only the kit header SKU on the PO. When you receive the kit header SKU with RRP, the quantity on hand of each component in the kit will be updated as will the average cost of each kit component.
New promotion codes in Modify Promotion Date report (RPD). When selecting “Add items to promotion file” to add items to the promotion file, the Options page has the new field “Promotion Codes” (4 individual codes) allowing the user to add codes to the promotions they are adding.
New option 8948 “Flag new UPC as the only Primary UPC?” This option automates the maintenance of the Primary UPC flag. When this option is set to Yes, the system marks the last added UPC as the Primary UPC. This applies to all ways of adding UPC's. All other UPCs for that item will have their Primary UPC flag set to No. When this option is set to No, the system does not automatically set the Primary UPC flag. Instead, you manually maintain the Primary UPC flag in Inventory Maintenance. Note that if option 3240 "Do Telecomm applications update the Primary UPC flag?" is set to Yes, this option (8948) does not apply because the Primary UPC flag is set based on the supplier's recommendation per the UPC data they supply.
"FOB Point” enhancements in Purchasing and Receiving.
All Purchasing & Receiving applications now use the field name/report name of “Freight Policy” rather than “FOB Point.”
New option 9613 “Add/change user-defined Freight Policy Codes” allows your to set up your own freight policy codes and definitions. Once you have set up the codes in option 9613, change option 9612 “Using user-defined Freight Policy Codes?” to have the system use them in the Freight Policy drop-down in Vendor Maintenance and Purchasing & Receiving. Option 9613 defaults to a pre-defined set of freight codes which you can modify if desired. The default list of freight policy codes include:
Code |
Description |
blank |
NFA - No Freight Allowed (buyer pays) |
P |
PPD – Prepaid freight (vendor pays) |
F |
FFA - Full Freight Allowed (buyer reimbursed) |
D |
DES - [Old] Destination |
O |
ORG - [Old] Origin |
Set this option to No if you want the system to continue to use the old codes of: Blank = No FOB, O = FOB Origin, and D = FOB Destination. Set this option to Yes if you want to define your own Freight Policy Codes. You define your own codes and descriptions by clicking the Current Value field and then clicking Edit This Table. This opens the Freight Policy Codes table. Note that when adding a new freight policy, make the first three characters of the description a recognizable abbreviation. Additionally, when adding the first entry in this table, which is used for "no freight allowed," leave the Code field blank, entering only the description "NFA - No Freight Allowed."
Enter minimums for free freight. Enter minimums (dollars and weight) required for getting free freight when purchasing from a vendor. Do this in Vendor Maintenance on the Order Info tab by clicking the new Freight Policy hyperlink. The Suggested Order Report (RSO) indicates the free freight minimums and indicates if the PO has not yet met those minimums. The PO Header’s Minimums hyperlink (same as Misc Menu option 6 “Vendor Detail Information”) now includes the Freight Minimums, and the existing minimums have been renamed “Ordering Minimums.” On the Header screen of Purchasing and Receiving, "Not Met" displays below the Minimums hyperlink if the PO doesn’t meet either the vendor’s Ordering Minimums or Freight Minimums. The minimums which haven’t been met yet display in red in the Vendor Detail Information dialog. If option 9477 “Store specific fields to copy to synchronize with other stores (MVR)” is set to “I” (Minimums), then these two additional minimums are copied just as the existing minimums are. If option 9477 is blank and you have Store set to All, when you press <Change> these two new minimums are copied to all stores.
Vendor Maintenance new field “Purchasing Stores.” This new field is for Customer Order Management (COM) users only. Set option 432 “Using the Purchasing Stores field in Vendor Maintenance?” to Yes if you want to use this field; it doesn’t appear in Vendor Maintenance until this option is set to Yes. The primary use of this new field is to show POS clerks creating Orders which stores are allowed to order an item when there is insufficient quantity on hand of the item. This field appears in the “Stores” panel of the Source Menu. An asterisk displays next to each store that is allowed to order from that item’s primary vendor. This information also appears in the HTML viewer that displays from Inventory Maintenance and the Purchasing and Receiving window when you click the SKU hyperlink, or click the Item (SKU) hyperlink in the POS posting area, or click the Quantities hyperlink in Inventory Maintenance. This new field is located on the Order Info tab’s Purchasing Options dialog. Use the drop-down list in this field to specify which stores or store groups are allowed to purchase from a vendor. If all stores are allowed to purchase from the vendor, leave this field blank. Note: Changing this field in Vendor Maintenance changes it in all stores for that vendor. Also note that if the item’s primary vendor is set up in Vendor Maintenance with Purchasing Stores blank, then in the “Stores” panel, an asterisk displays next to each store that sku exists in – indicating that ALL stores are allowed to purchase from that vendor. If the item’s primary vendor field is blank, the “Stores” panel still shows all stores that SKUs exists in, but does not display an asterisk next to any of them since there is no primary vendor it can use to determine this.
New columns in the Vendor Viewer. Both the "by Vendor Name" and "by Vendor Code" viewers have the following new columns: Freight Minimum Dollars, Freight Minimum Weight, and Purchasing Stores.
New column in the Purchase Order Viewer. The new Last Receipt Date column is only relevant on Status P (partially received POs) and shows the last date the PO had receipts finalized by the Receiving Report (RRP) option F.
Purchasing Information Report (RPP) enhancement. On the Options page of RPP, there are now two new options that allow you to purge older POs, "Purge Status F or T POs Created More than__Days ago," and "Purge Status P POs with Last Received Date More than___Days Ago". For both fields, the number of days ago must be a minimum of 60 days. This means you cannot purge F status PO’s until they are at least 60 days old.
Item Price Changes (IPC) and Modify Item Promotions (MIP) show the Primary UPC. Both IPC and MIP now have a “UPC” column which displays the Primary UPC for the item. If the item doesn’t have a Primary UPC, then the UPC last used displays.
Print/Fax Purchase Orders (RPO) new “Group By” field. This enhancement is for iNet Email Purchase Orders users only. Use this new field if emailing multiple POs from the Email Setup page of RPO. Set to “P-create one PDF for each PO” if you want each PO to be received as its own separate email, each with a PDF of that PO. Set to “V-Group PDFs by Vendor” if you want each vendor represented by the from/to range to receive one single email, with a PDF containing all POs for that vendor.
Enhancements to Inventory Import Tool.
You can now update the following fields using Inventory Import: Hazardous Code, Web? Flag, Keep Prices, and the new fields Lowest Sell Price and Max Units Per Transaction.
The “Add SKU number prefix” value can now be up to 10 characters instead of only 3 characters.
When adding SKUs, you can now use both “Add SKU number prefix” and Auto-assigning SKUs.
You can now include up to five alternate vendors in one import file in order to add or change up to five alternate vendors for an item.
Hazardous Code field enhancement. The Hazardous Code field in Inventory Maintenance on the Code tab’s Additional Codes Flags dialog now has a corresponding Hazardous Codes Maintenance function accessed from Misc Menu option Z. A set of default Hazardous Codes is included on the system, but you can modify these default codes, add your own, or delete an existing hazardous code.
Physical Inventory Report (RPI) printing enhancement. RPI has the new Print Sequence 7 “Location/Seq #” which can be used to load and print count sheets, and can also be used to print the reconciliation. Using count sheets in Location/Shelf Seq # order is much more useful than ones printed in “Location/SKU” order.
New option 434 “Use the A/P terms from the Pay-to vendor instead of the PO vendor.” When this option is set to Yes, then when a purchase order is added in Purchasing, the system loads the Pay-To Vendor's terms code in the PO header. When the PO is then received with RRP option F, the terms code from the PO is passed to APP and is used to create the A/P voucher. If this option is set to No, the system uses the PO vendor's terms. Note the following: 1) If this option is set to Yes and the PO vendor has no Pay-to Vendor, the system uses the PO vendor's terms. 2) Regardless of how this option is set, if the Terms Code is blank, then the system uses Terms Code 1. Also note that you can select a different terms code in Purchasing, in which case RRP passes the selected terms code to APP, and this terms code is used to create the A/P voucher.
Purchasing and Receiving enhancement for Multi-Store users. New option 9618 “WinMPO - Apply cost change to all instances of the item?” can be set to Yes so that when changing cost on a multi-store PO, you only need to change the cost once. The system then makes that cost change on all instances of that item on the PO. Note the following: 1) This option only applies to POs which are status F. 2) The system only changes the cost on other instances of that item on that same PO. It does NOT find that item on other POs and change their cost as well. 3) Special Order items are excluded from this logic. This means the system does not update the cost on other instances of the item if any of the following fields are set in Inventory Maintenance: The Special Order SKU field (accessed from the Additional Codes hyperlink) is Yes, Order Indicator field is S, Keep Prices field is No, or Special Record field is F, L, or M (not blank). 4) If Buyer's Purchasing (Option 1051) is set to Yes, the system finds and changes the cost of that item on other POs whose Alt PO# matches the Alt PO# of the PO being changed. This option applies regardless of how option 118 "Keep Prices the Same in All Stores" is set.
RICU (Item Code Update) enhancement. The fields Lowest Sell Price and Max Units Per Transaction are now available in RICU.
Flexible Inventory Loading (FIL) and Flex Inventory Loading Report (RFL) enhancement. The fields Lowest Sell Price and Max Units Per Transaction are now available in FIL and RFL.
Windows Purchasing & Receiving now shows Defective Policy column. This applies to both the posting and receiving grids (this column was hidden on prior releases). This field is populated with the defective policy code from the Electronic Catalog for Ace, True Value, or Do It Best Corp. when the PO being created or received is for one of those vendors.
A/R Aging Report (RAG) new update option Y “Age Unapplied Credits for Open Item Accounts on Due Date.” This new update option on the RAG requires that you have existing option 3556 “Calculate due dates on unapplied credits same as invoices” set to Yes in Options Configuration so that unapplied credits have a due date based on terms. Use RAG Option Y to have unapplied credits for Open Item Accounts age based upon their Due Date. If you do not use option Y, they age based on Due Date, but then if a credit balance exists, the system applies the credit to the next most current aging bucket.
New security bit 136 “Change Charge Allowed on Main and Credit tabs.” See the Security section below for details.
Option 9009 "Reduce exclusive use of AP & GL transaction files" now controls General Journal Transactions (GGMU) as well as ATMU. On Release 20, this option was created so that "exclusive use" of New A/P Transactions (ATMU) was no longer required when running RATJ. Now, when this option is set to Yes, in addition to ATMU, "exclusive use" is no longer required for the GL Transactions file (GGMU) when running RGGG . This means that GL clerks can continue working in GGMU while RGGG is running, as long as the RGGG is run using a from/to for a specific user.
New security bit 929 “Ability to change Voucher Date in ATMU.” See the Security section below for details.
New Pay-to vendor lookup in View Posted A/P Transactions (AVIQ). For example, if the purchasing vendor is "Ready Flame" but you get a call from the Pay-to vendor which is "Jensen." You can now look up the vendor in AVIQ by either the Purchasing vendor (Ready Flame in this example), or you can look up the Pay-to vendor (Jensen in this example). To look up by Pay-to vendor, click the Lookup button on the tool bar and then click Pay-to Vendor.
New Voucher Date column in the Show Distributions window of AVIQ. Voucher Date (date posted to the G/L) is now a column in the Show Distributions window of View Posted A/P Transactions (AVIQ). In AVIQ, click a transaction in the grid, then click MISC and select "Show Distributions." The "Voucher Date" is now a column in this table. This allows you to see when the expenses for a given A/P voucher were posted to the G/L.
New Voucher Reference column in General Journal Transactions (GGMU) and General Ledger Detail (GINQ).
There has been a number of usability enhancements made in Modify Receiving Documents (MRV), as described below.
The Sequence Number field now defaults to 1 instead of blank. This makes it easier to recall a PO by typing in the PO number and pressing Enter to recall the first sequence of a purchase order. You used to have to type in the PO number, press Enter, and then press Next to recall the first sequence of a PO.
MRV now includes AP terms and Freight Policy. The header area of MRV now includes the purchase order's AP terms description and its Freight Policy.
The "PO #" field label is now a hyperlink. When clicked, this new hyperlink displays the PO’s special instructions for viewing and/or editing (equivalent to using Misc Menu option 4 “Add/Change Special Instruction Note”).
The "Vendor" field label is now a hyperlink. When clicked, this new hyperlink displays the vendor’s Note Type 5 from Vendor Maintenance (equivalent to using Misc Menu option 5 “View Vendor Notes”).
New “Edit Mode” field. This field allows you to toggle between two ways to do grid data entry on the details of the receiving document:
Edit Mode – the default mode that has always existed where you can enter the quantities received in the New Rcvd Qty column, and if necessary, change any costs in the New Cost column.
Click Mode – this mode is typically used for session invoices, so that clicking on the row’s checkbox automatically populates the New Rcvd Qty and New Cost columns. For session 0 (non-session invoices), clicking the checkbox moves Last Rcvd Qty to New Rcvd Qty and Last Cost to New Cost. For session 1 or higher, clicking the checkbox moves the Qty Not Invcd to New Rcvd Qty and Last Cost to New Cost. Note: To clear the values in the New Rcvd Qty and New Cost columns, simply click the row’s checkbox.
MRV has new grid columns. These new columns are listed below. In MRV, they are initially hidden; use Select Columns to View to select any of the columns that you want to see. Note: the fields marked with an asterisk in the list below will not have values for receipts that existed prior to upgrading to release 20.1. Only new receipts created after the upgrade will have data in these four columns.
UPC
Alt Part Number – Contains the part number for the PO’s vendor, which is either the SKU or the alternate vendor’s part number (if the PO is for the item’s alternate vendor)
New Extd Rcvd Cost – The New Extended Received Cost that is only populated if there has been a new received quantity or new received cost posted in MRV.
Qty Orig Ordered (Stk) – The original order quantity on the PO in stocking units.
* Qty To Be Rcvd (Stk) - What the Receiving Report (RRP) had left to receive at the time it ran (same as the Qty T-Rec on the RRP)
* Qty on Backorder (Stk) - The quantity left to receive if the PO’s Backorder field was set to Y; if the Backorder field was N, then this column will display 0.
* Total Qty Rcvd On This PO (Stk) - The total quantity received by RRP for this PO.
* Qty T-Rec minus Qty B-Rec (Stk) - This is a calculated column, indicating the variance in what the RRP had left to receive against what it actually received. Therefore, on combined lines, it would always be the sum of the RRP Qty T-Rec minus the sum of the RRP Qty B-Rec.
New “Append to RV” field on the Accounts Payable tab of Vendor Maintenance (MVR). If this field is set to Yes, then finalizing a subsequent receipt of a PO (with RRP option F) appends the newly received lines to the already-existing receiving document for that PO. If the new receipt is on a line#/SKU that already exists in MRV for that PO, and if that existing line has the same cost and has not previously had changes entered for quantity or cost, then the newly received quantity is added to the Last Rcvd Qty already on that line item. If the cost does not match or if the existing line has had modifications, the system looks through the items received for that PO for another match for that sku and cost which has not been modified in MRV. If not found, a new line is added to the receiving document. Note: When “Append to RV’ is set to Yes, if the already-existing receiving document has sessions or an invoice number, it cannot be appended to – instead, the system creates a new receiving document.
New Net Invoice information. The MRV screen has a new section (right-hand side of the header area) that shows the Net Invoice amounts for each additional vendor for which "Other Charges" were added to this receipt. You no longer have to click on the Other hyperlink to see this information (only viewable on screens with resolution greater than 1024 x 768). Clicking the Net Invoice hyperlink displays the dialog to update freight and other charges (same dialog that clicking Other displays).
The AP Voucher dialog has the new fields Total and Net. These fields are locate below the Voucher Reference field, and indicate the net payable for the PO’s Vendor.
You can now find a receiving document when all that is known is the SKU or UPC of an item on that receipt. Use the toolbar’s <Lookup> button and select “SKU/UPC” to use this new capability.
You can select multiple receiving documents to which a freight bill’s total cost should be prorated. Use Misc Menu A “Prorate freight to checkboxed rows,” checkmark the POs the freight bill applies to, then select Misc Menu A, and enter the total freight and press Enter. The system then prorates the freight to each PO based upon a ratio of each PO’s Cost to the summed total cost of all checkboxed POs.
New Advanced Receiving report RVC “Combine Receiving Documents.” RVC allows you to combine multiple receipts of the same purchase order into one receiving document. Enter the PO # and Seq # to which you want the other receipts to be appended. Then either enter a list of up to 20 sequences to be appended, or set the Combine All field to Yes to append all existing sequences to the "append-to" receiving document. Note that the PO's "vendor" and "created-in-store" must both match the append-to document, the PO must have no sessions, it cannot have freight for another vendor on it, and it cannot have an assigned invoice number.
Receipts of the same item for a store are combined if they have the same cost and have not previously had changes entered for quantity or cost; otherwise they are appended to the receiving document as a new line.
Issue with Datalogic Falcon device is resolved. There was an issue in previous versions when downloading new versions of Eagle Mobile to a Datalogic Falcon device using the configuration application. This issue has been resolved, but you must cradle the device one last time to install this version. After that, your configuration application will be able to download new versions.
New option 1182 "Show List Price on Mobile Price Check Screen." This option determines if the list price is viewable on the price check screen.
New security bit 930 "Eagle Mobile: Access Inventory Price Check screen." This new bit allows a user to see the price check screen, but not access all inventory tabs. This security bit only applies if bit 868 "Eagle Mobile: Access Eagle Mobile Inventory" is set to No. If bit 868 is set to yes, the user already has access to all Inventory functions including price check, so bit 930 is not checked. If bit 868 and 930 are both set to No, then for that user, the inventory function will not appear on the main menu. If bit 868 is set to no and 930 is set to yes, the inventory function appears on the main menu, but when selected, the only screen the user can see is the price check screen, even if the default screen (option 1127 "Mobile inventory default screen") is set to something else. The lower right hand menu will also be disabled so the user cannot access the stocking screen.
Additional defaults for the count field in Physical Inventory. Option 1143 "Mobile Physical Inventory Count First Scan as 1?" now has an additional value of QOH (Quantity on Hand). If option 1143 is set to QOH, when you count an item in the physical inventory or physical from a List functions, it populates the count field with the quantity on hand from Inventory Maintenance.
New option for count warning. New option 1157 "Mobile Physical Inventory Maximum count without warning" allows you to enter a value between 1 and 99999 to receive a warning if a user tries to count a value greater than that amount in any single posting (you will not receive the message if you already counted 15 and you try to count 7 more). Set the value to zero or blank if you do not want to receive this warning message. If the user answers yes to the warning, the count will be posted. If they answer no, they will be returned to the counting screen to correct the count.
New option 1181 "Mobile Receiving Allow scan of PO number." If this option is set to Yes, the cursor in Eagle Mobile Receiving continues to default to the PO # field, which is now scannable, noted by the pink background in the PO# field (note that the barcode comes from the vendor; Eagle Purchasing and Receiving cannot print barcodes). If you want to scan an item number, you must tab to the item field to enable item scanning, noted by the pink background in the Item field. If you tab to the vendor field, the scanner is disabled.
Improved Add Item Screen. This screen that allows you to add items to a purchase order has been modified to make it more user-friendly. There is a now a cancel button that allows you to easily exit if you do not want to add the item to the purchase order. The buttons have also been relocated to make them more standard with the rest of the receiving function.
New Batch Receiving functionality. Batch receiving is much like the receive by item feature, but restricts the POs that are returned in the search results to just those POs that are associated to the batch selected. This is particularly useful if you are receiving a shipment from a vendor that includes multiple POs. You can create a batch of up to 18 POs on that truck to help the receiving clerk select the correct PO against which to receive. To use this feature, you must set option 1180 "Mobile Batch Receiving enabled" to Yes so that any user that has access to the Purchasing and Receiving menu will now see the new menu entry “Create/Maintain Receiving Batches (MRB).”
New option 1183 "Mobile Receiving: Always show distributions on central distribution POs." On the previous version of Eagle Mobile, when receiving a central distribution PO, the “Mult” link was always available so you could see the stores to which the product was set to be distributed. This was true even if there was only one store for that item. In this new version, there is a new option that controls when the “mult” link is visible: either on all items, or only those that are truly on multiple lines. If 0ption 1183 "Mobile Receiving: Always show distributions on central distribution POs" is set to Yes, then the Mult link is always visible. If it is set to no, it is only visible on items that are on more than one PO line.
Transfer Receiving now available in Eagle Mobile. To receive transfers in Eagle Mobile, option 1175 "Use Transfer Receiving" must be set to Yes, and security bit 866 "Access/Update Mobile Receiving" is required. To begin receiving, you can look up a transfer by the transfer number, purchase order number, or item number. The application searches all transfers where the to-store on the transfer equals the lock-in store on Eagle Mobile. Once a transfer has been selected, transfer receiving is very similar to receive by PO, except that cost and retail can not be updated, and the from-store is indicated. The Details menu has an additional option where you can view variances for all items that are not fully received. These variances can also be viewed in the Transfer Receiving Variance Viewer (VIEWTV).
The inventory at the from-store and to-store are updated for the full shipped amount, and then you perform a transfer adjustment for any variances. You do this in the Transfer Variance Viewer. Once an adjustment has been created for a transfer, it is removed from the Viewer. Thus, if a transfer has multiple variances, they should all be corrected at the same time.
Creating Ordering Lists and Labels Lists. Set option 9585 "Inventory Item Lists Enabled" to Yes so that when you create an Item List, you can now select the type of list you want to create: either a Labels list which can be used for printing labels, or an Order list which is used with the Suggested Order Report (RSO) to generate orders. If you create an ordering list that does not include quantities and you use it in RSO, the RSO reviews each item and use its calculations to determine order quantities needed. If you create an ordering list with quantities and use it in RSO, RSO generates orders with the quantities from your list.
You can now delete Item Lists from the Eagle Mobile application. To do this, select the item list from the select list page, then from the Details menu, select “Delete List.”
You can now verify Transfers with Shipment Verify. If you are multistore and have option 1169 “Eagle Mobile Shipment Verification on System” set to Yes, you can verify transfers in any status (Requested, Shipped, Complete). In Shipment Verify, transfers work exactly the same as orders or invoices with the exception that the “Finalize + Invoice” option will not be available on transfers in the details menu. If option 1027 "Transfer Access Allowed" is set to Y, the Shipment Verification Exceptions Report (ROV) shows transfers as well as orders.
See the iNet online help on the Eagle website.
Alert User Profile setup fix. (iNet Connect users only) Alerts which support “Me” (Only show the alert if it is for me) in the “Receive Alert” column are now properly only emailed to that specific user if the alert’s “Receive Email” is set to Yes. Previously, the alert was emailed to all users set up to receive that type of alert.
Keep keystroke logs longer. New option 9611 “Number of Months to Keep Keystroke Logs” can be set to 2 to keep 60 days of keystroke logs on each PC instead of just 30 days.
Business Advisor enhancement for Daily Notes. You can now view or print the daily notes for a range of dates. You use the Daily Notes feature, which is accessed on the Management Summary screen by clicking the Date hyperlink, to enter notes about that day that may explain some unusual results. There is now a <Print> button in this dialog, which displays a dialog where you can enter a date range to view and print a range of notes. After entering the date range and clicking OK, the notes for that range of days display in Windows Notepad, where you can view them, print them, or export them to Excel. The first column is the date of the note, the second column is the store for the note, and the third column is the note itself.
New option 9346 “Activity limit for customer to be included in Offline Database Refresh.” If you have a very large customer file, you can use this option to reduce the amount of time the Offline Database Refresh takes. In this option, enter the number of days in which a customer has to have been active for it to be included in the refresh. For example, setting this option to 90 will include only those customers which have a date of last sale within the last 90 days. Also select new choice I “Inactive Customers” in existing option 9345 “Offline Database Refresh Exclusions” so that inactive customers are excluded from the refresh.
New option 9587 ”Backup Wait Time.” This option allows you to specify the number of minutes to wait for reports to complete before starting Backup. The process checks every minute, up to the number of minutes specified, to see if the report(s) has completed. If the report(s) does complete, then Backup is started. If after the specified number of minutes the report(s) is still running, Backup does not run.
If this option set to 0, then 1) SHUTDOWN checks for reports running, 2) If any report is currently running, Shutdown quits and there’s no backup, and 3) If no reports are running, Shutdown continues with next steps (backup, etc.). If this option is set to any non-zero value (for example set to 15 minutes), then: 1) SHUTDOWN checks for reports running, 2) If any report is currently running, Shutdown will wait a minute and check again and do so for up to 15 minutes, 3) If no reports are running (initially or after a subsequent check after each minutes), Shutdown continues with next steps (backup, etc.), and 4) If 15 minutes has elapsed and reports are still running, Shutdown quits and there’s no backup.
Do It Best (DIB) enhancement for Date Effective of transmitted price changes. New option 3246 “DIB price changes - use the 'Date Effective' from each record received?” Setting this option to Yes means that the Date Effective (in Item Price Changes [IPC]) for each item in the batch will be the Date Effective found in each individual incoming price change record. This means that you could have different dates as the Date Effective for different items in the price change transmission. Setting this option to No means that the Date Effective for the entire batch of price changes will be the Date Effective found in the first incoming price change record. This means that every item in this price change transmission will have the same Date Effective and will be activated at the same time by RPC option F.
New report SPLP “Spooler Archive Purge.” This report can be launched from Eagle Browser if you have security bit 256 “Change/Delete spooled reports.” SPLP is a purge function that completely removes reports from the Spooler Archive. These deleted reports are NOT staged for storage in an off-server archive. To use this purge, specify the name of the reports you want to purge in the Reports field, separated by commas. Then enter a number of 60 or greater in the "number of days old" field.
Alerts enhancement. For users that have security bit 6 “View data in all stores” set to Yes, Alerts that are specific to a store(s) can now be received only when the alert is about an event/activity for your store. In Alert User Profile, set the Column “Signon Store Only?” to Yes to receive only those alerts that are for your store. In Alert User Profile, those alerts which are store-specific display either a Yes or No in the Signon Store Only? column. A blank in this column means that alert is not store-specific and therefore that cell is not editable. Once you install Level 20.1, you can go into your Alert User Profile and set the “Signon Store Only?” column to Yes for this alert. With this flag set to Yes, when they are in store 1 they will only see alerts relevant to store 1. Note: If the manager from store 1 has to cover for a sick manager at store 2, the terminal they work on at store 2 is locked into store 2; therefore, they will see the store-specific alerts for Store 2. If they want to see the alerts for store 1, they must change their lockin store to 1. Note that since there is no lockin store on reports, the source store for alerts is always set to 1; therefore, if your business limits managers to only data for their store (security bit 6 is set to N), the only managers which can see alerts written by reports are the managers in store 1. Example: RPC is finalizing price changes for store 2 and an item is getting a new retail less than cost. Since that alert’s source is 1 (because it is a report), the manager in store 2 who has bit 6 set to no does not receive this alert. If they have bit 6 set to Yes, and have this alert in their profile set to Y, they will see that alert.
New security bit 973 “Ability to access Display Backup Rotation (DBR and TAPE).” See the Security Enhancements section below for more information.
Ace ERP report enhancements. Orders on the Ace ERP report now print in SKU order to make finding a particular item on the report easier. Additionally, any purchase order that was updated by ERP is now printed on the report. Previously, only purchase orders that were added by ERP processing were printed. Since both are now printed, it is now easier to find any order in Purchasing and Receiving (MPO). Reconciling your report against the Ace statement is now easier as well.
Policy claim enhancement in Ace Catalog. The policy A field for Ace items now shows “Y” or “A” for Ace policy A items, and now shows “B” or “C” for non-policy A items. This enables you to more easily file the right type of defective claim to Ace.
RA99 “Print 1099 Forms” available from Eagle Browser. Type RA99 in the Launch bar and press Enter to access this report. If the forms are being printed to a laser printer, then Device Configuration for the print server to which the printer is pointing must have the entry “Laser Form 1099 Printer” configured with the laser printer to which the 1099’s should print. Otherwise, if this entry in Device Configuration says “Not Configured,” the RA99 output will be formatted for printing to a dot-matrix, pre-printed form. To run RA99, you must have security bit 469 “Allow A/P federal 1099 report.”
Network Access utility “Verify and Clean the Long Sku/LinePart Reference File” has been added to Eagle Browser’s Point-of-Sale Reports menu. It can be launched with CLEANANX. This utility is for Mode 2 (Long SKU) and Mode 3 (Line/Part--automotive) users only, and requires security bit 91 for access.
Network Access utility “Protobase Settlement” has been added to Eagle Browser’s Point-of-Sale Reports menu. It can be launched with PBSTL, and requires security bit 573 “Allow ICSETUP or PBADMIN” for access.
True Value Catalog has two new fields, Visibility and UOM Item. These field are received with EFM and added to the electronic Catalog. Note that these new catalog fields will not be fully enacted until September 2011. Until then, the new fields and columns will be visible but not populated. Visibility and UOM Item have been added to the Catalog’s Item Detail screen, to the Catalog Item List grid as columns available to view, and to the Analyzer Tool filter on the Catalog Item List screen as additional filters. The “Visibility” flag shows if an item is a highly visible item (H), a visible item (V), or a blind item (B) which helps you determine the price sensitivity of the item. The “UOM Item” flag indicates if an item is purchased in one unit of measure but True Value suggests that it be sold at retail in a smaller unit of measure (i.e., spools of rope or chain, etc.). This flag identifies those items for which True Value provides two suggested retails: one for the purchase unit and one for the selling unit.
Two new columns in the Purchasing and Receiving posting grid. The new True Value Visibility and True Value UOM Item fields are available in the Purchasing posting grid. They are populated when the PO is for True Value and option 8285 “Display the PO create/maintain posting grid in expanded format?” is set to Yes.
Bulk Mail Discounts using Intelligent-Mail® Barcode. The United States Postal Service (USPS) has mandated that in order to receive bulk mail discount rates, you must be using the new Intelligent Mail bar code (IMB) by May 2011. USPS has also announced that as of May 2011, PostNet barcode bulk rate mailers will no longer be eligible for mail automation discounts. Eagle for Windows now supports the ability to print USPS Intelligent Mail Barcodes for Accounts Receivable Laser Statements. To receive Intelligent Mail Barcode automation discounts, you must qualify for bulk mailing rates and you must register and certify your statement forms with the US Postal Service. Contact your local USPS office for registration and certification details. Once you have registered, the US Postal Service will issue you a service ID (e.g. first class, periodicals, etc.) and a mailer ID. Once you have obtained these IDs, set option 8109 “Print Postnet / Intelligent Mail Barcode on A/R Statements?” to either I-Print Intelligent Mail barcode or J-Print Intelligent Mail barcode with delivery point. Then enter the Service ID in option 8107 “Intelligent Mail Barcode Service Type ID” and the mailer ID in option 8108 “Intelligent Mail Barcode Mailer ID.” Now you must perform a local certification step prior to using the Intelligent Mail Barcode, which entails printing a sample of 20 or so statements, placing them into separate statement envelopes, and providing them to your local USPS certification specialists. Once you are certified, you can begin printing accounts receivable statements with the Intelligent Mail Barcodes and receive your automation discount. The statement using the intelligent mail barcode is designed to be tri-folded and placed into a #10 window envelope. The existing envelope (designed for use for a bi-fold statement) will not allow for certification with the Intelligent Mail Barcode program. If you wish to continue bi-folding your statements, you must order statement envelopes with a modified (larger) window to allow for USPS Intelligent Mail Barcode certification.
New security bit 136 “Change Charge Allowed on Main and Credit tabs.” This bit is only relevant for users who have Customer Maintenance security bit 135 “Change customers “ set to Yes, and if either or both of 891 “Ability to make changes on the Main tab of Customer Maintenance” and 892 “Ability to make changes on the Credit tab of Customer Maintenance” are set to Yes. If you want the user to be able to make changes to all fields on the Main tab of Customer Maintenance, then set bits 135, 136, and 891 to Yes. If you want the user to be able to make changes to all fields on the Main tab of Customer Maintenance except for Charge Allowed, then set bits 135 and 891 to Yes, but set bit 136 to No. If you want the user to be able to make changes to all fields on the Credit tab of Customer Maintenance, then set bits 135, 136, and 892 to Yes. If you want the user to be able to make changes to all fields on the Credit tab of Customer Maintenance except for Charge Allowed, then set bits 135 and 892 to Yes, but set bit 136 to No.
New security bit 969 ”Delete category pricing plans.” This bit controls the ability to use the Delete key to delete an entire pricing plan in Category Pricing Plans (CPP). See also related bit 209 which controls the ability to delete a category from a CPP plan. (Note: Release 20.1 automatically sets new bit 969 to the value of existing bit 209.)
New security bit 928 “(MO) Allow taking a deposit greater than the balance due.” This bit controls the ability for the clerk to enter a deposit amount that is greater than the transaction's total/balance due. If a clerk does not have this bit, a manager's override is required before the clerk can proceed in taking a deposit greater than the balance due. Note: This security bit does not apply to the situation where the existing deposit on a transaction is greater than the balance due.
New security bit 929 "A/P Ability to change Voucher Date in ATMU." When this bit is set to Yes, the user is allowed to change Voucher Date in function ATMU. When set to No, the user is not allowed to change this date on an existing voucher (including temporary vouchers), and when adding a new voucher they are not allowed to set this date to anything other than today's date.
New security bit 930 "Eagle Mobile: Access Inventory Price Check screen." This bit is only used if security bit 868 "Eagle Mobile: Access Eagle Mobile Inventory" is set to No. If bit 868 is set to Yes, the user already has access to all Inventory functions including price check, so bit 930 is not relevant. If bit 930 is set to yes, the inventory function appears on the main menu, but when selected, the only screen a user can see is the price check screen, even if the default screen (option 1127 "Mobile inventory default screen") is set to something else. The lower right hand menu is also disabled so the user can not access the stocking screen.
New security bit 973 “Ability to access Display Backup Rotation (DBR and TAPE).” This bit controls the ability to access function DBR "Display Backup Rotation" from Eagle Browser (also applies to the alternative method of typing TAPE in the Launch Bar). DBR tells you the next backup set to use, as well as backup history. DBR (And TAPE) used to be tied to bit 91. Note: Release 20.1 sets this new bit to Yes if bit 91 is set to Yes.