What's New on Release 24.1 Eagle for the Aftermarket

Welcome to Eagle for the Aftermarket Release 24.1 (server Level 36). This document summarizes the new features and enhancements. Use the red links below to take you to a particular section of this document (POS enhancements, Inventory enhancements, etc.).

Eagle N Series

POS Enhancements

LaserCat 3 Enhancements

Inventory Enhancements

Purchasing and Receiving Enhancements

Accounts Receivable Enhancements

Accounts Payable/General Ledger Enhancements

Advanced Receiving Enhancements

Telecommunications/National Account Enhancements

Pricing Enhancements

Miscellaneous Enhancements

Security Enhancements

Eagle N Series

POS Enhancements

  1. The latest POS 2.0 Touch Panel Control is located on the Eagle client CD. The file is named touchpanel.msi and is located at the root level. Note: POS Touch stations typically do not have CD drives, so you must either place the touch panel control file on a network shared folder/CD drive, or copy it over to the POS Touch station. Save the POS 2.0 Touch Panel Control file in the C:\3apps\temp folder on the POS Touch station.   
  2. Double-click the touchpanel.msi icon to begin the installation. When the Epicor Eagle POS Touch Interface Control window displays, click the box to accept the terms in the License Agreement, and then click Install.
  3. From the window displaying the status of the Eagle POS Touch Interface installation, click Finish when the installation completes.

Before you set option 1468 to Yes, you must first configure the option equivalents of the preferences you have defined at your POS stations. At a POS station where you create special orders, create a print screen of the Tools/Options Deposit & Special Order tabs. Now go into Options Configuration, and using the settings from these tabs, configure the equivalent options listed below:

For Orders (these also apply to Service Orders):

For Special Orders:

For both Orders and Special Orders:

Note the following:

This option applies to the signature capture pad’s display (both 3 and 5 line displays) and the consumer digital display monitor.

Note: Multiple deposits on an order can’t be aged as separate deposits because the data doesn’t track them separately. Aging is per the first deposit taken on the order, and the amount remaining is after all deposit activity for that order has been applied.

Point-of-Sale events that can be identified for collecting consumer information include the following.

§  Starting a special order

§  Starting a layaway

§  Starting an estimate

§  Starting an order

§  Totaling a transaction with Consumer Info Code 1 thru 9

§  Totaling a transaction with a return

§  Totaling a tax-exempt transaction

§  Totaling a transaction with a special tally item

§  Totaling a transaction for a customer who requires additional information

§  POS Order Viewer. This viewer has a new column for email addresses.  This column is populated with the email address collected by the new Flexible Consumer Information collection feature.

§  Quick Recall Viewer enhancements. 

§  A new column has been added for email addresses.  This column is populated with the email address collected by the new Flexible Consumer Information collection feature.

§  A new button, Credit Card Lookup, appears in the “Reprint, View, Fax, or Email this invoice” dialog when the new option 1496 “Include Credit Card Lookup in POS’s Reprint, View, Fax, or Email” is set to Yes. This option is only available when option 9537 “Returns Validation with Receipt” is set to B (Both receipt and credit card) or C (Credit Card).  When the button is selected, a customer’s credit card, debit card, or gift card can be swiped or manually entered and a list of the transactions paid by the card will be displayed.

§  Return Validation Viewer. A “Code” column has been added to the viewer. This field contains the vendor buyout code when a part is sold as a vendor buyout.

§  New option 1524 “Require Password to Invoice Order or Credit Memo” When set to Yes, the clerk will be required to enter a password prior to pressing the final total key for an order.

§  New option 9263 “Require entry of driver’s license for checks this amount and over”  If a transaction equals or exceeds the amount specified in this option and the transaction is paid by check, the clerk will be required to enter a value in the Driver’s Lic # field of the Check Guarantee dialog. This option applies to POS stations doing Check Guarantee which have option 1090 (Default Check Guarantee) set to either A (Bank account number) or D (Driver’s license number).

§  New option 314 “QuickRecall number of years to keep Special SKUs transactions.” This option allows QuickRecall transactions that contain special SKUs to be store for up to 99 years.  Before the option was added, these transactions could only be stored for up to 96 months (8 years). If special SKU transactions do not need to be kept for more than 8 years then leave the option blank and the system will use the value in Legacy function Modify QuickRecall Constants (MQK).  If special SKU transactions need to be kept for more than 8 years then enter the number of years (1 to 99) in option 314.  The value entered in this option will supersede the “Default Criteria for Purging Special SKUs” in MQK.  Note:  Special SKUs are items whose Tally flag is set to any of A, P, R, S, T, or X.

Windows LaserCat 3 Enhancements

Windows Inventory Enhancements

Note: If desired, the system can prompt you to delete the batches that were printed or loaded to the Label Manager grid. New option 5824 “Label Manager - Prompt user to delete label batches after <Import>.” Set this option to Y to be prompted to delete the label batches with the answer defaulted to Yes, or set it to X to be prompted to delete the label batches with the answer defaulted to No. You can also set this option to N to not be prompted to delete the label batches.

Windows Purchasing & Receiving Enhancements

Notes for classic MPO users: 1) If the cost is changed before posting the item in classic MPO, all three costs match, and are the vendor’s cost.  2)  If the cost is changed after posting in classic MPO, the unit costs match and the original cost is the vendor cost on file.  3)  If the PO is created on a classic store configuration, the unit costs are for the vendor being used and match the PO, but the original cost is the replacement cost.

Note: If you use option S, you must also use Update Prices option P “Update Retails in PO Based on Landed Cost” or Q “Update Retails in PO Based on Landed Cost (Preserve Highest Retail),” and you cannot use option F. Additionally, option 105 in Options Configuration must be set to X or Y, but you do not have to enter Freight and/or Other Charges to recalculate a new retail, since it will be calculated from the projected new average cost and desired gross profit. Multi-store users with option 118 "Keep Prices the Same in All Stores?" set to Yes can only create price changes for new retails from Store 1 purchase orders.

How to Use:  

§  “From Address” has been changed to “From Email.”

§  “To Address” has been changed to “To Emails.”

§  If RPO is being run for one PO or vendor, all email addresses entered in Vendor Maintenance that are set up to receive emailed POs will display in the “To Emails” field. Email addresses can be removed or added as needed.

§  If RPO is being run for more than one PO or vendor, the system assumes multiple vendors, so no email addresses are displayed. When the field is empty, a note at the bottom of the screen indicates that each PO will be emailed to the addresses entered in Vendor Maintenance for that PO’s vendor. If email addresses are entered in To Emails, all POs will be emailed to those recipients regardless of the PO’s vendor.

§  The More Emails field is used to enter additional recipients of the purchase order. These are in addition to the recipients entered in Vendor Maintenance.

Note: If an RPO is added to an EOD queue, the To Emails address field should be left blank. When the queue runs, the system will use the recipient emails which exist in Vendor Maintenance at the time the queue runs. If the field is not empty in the queued RPO, the system uses those entries.

Windows Accounts Receivable Enhancements

Installing Release 24.1 copies all of the email addresses in Note types 10 and 11 into Contacts. Notice that Note Type 10 and 11 still exist, and that the system automatically adds them, changes them, and deletes them as you make changes to a Contact. However, Note Type 10 and 11 are now display-only. When statements or invoices are emailed, the system still uses the emails in Note Type 10 and 11, but you now only enter them in Contacts, and the system takes care of keeping them in sync.

The Statements field on the Contact’s Add and Change dialogs replaces the step of manually adding the contact’s email address to that account/job’s Note Type 10. If the account’s Misc menu “E-mail Statement” field is X or Y, and you want the contact to be emailed A/R statements, enter their email address and set the Statements flag to Y.  

The Invoices field on the Contact’s Add and Change dialogs replaces the step of manually adding the contact’s email address to that account/job’s Note Type 11.  Use these guidelines for setting this field:

There are two new fields in Contacts: “Primary Contact” with choices of Y and N. The contact you mark as Primary (Y) will be the first to display in the user-interface where the system shows the customer’s contacts. The second field is “Opt Out” with choices of Y and N, which is used in filtering contacts when creating an email or call list.   

Customer QuickAdd had some related changes:

The Customer Contacts Viewer has two new lookups: 1) Customer From/Thru, which you can use to create a calling, mailing, or emailing list – you can filter for Y in Opt Out to exclude customers who do not want to be contacted, and 2) Email, so that if you want to find the accounts with a particular email address, you can enter just the first part of an email address, and the system finds the relevant accounts.

§  Customer Maintenance (MCR) enhancements. 

§  Six new security bits have been added that control access to the associated tabs.  These will be set to Yes if bit 131 “Access Customer Maintenance (MCR)” is set to Yes.

§  1099 – View MCR Credit tab

§  1100 – View MCR Department tab

§  1101 – View MCR Sales tab

§  1102 – View MCR Payment tab

§  1103 – View MCR Misc tab

§  1104 – View MCR Contacts tab

§  On the Contacts tab, the Name field can now be changed in the Change function.  Previously, the contact had to be deleted and re-added in order to change the name.

§  New option 1600 “Show statements for other stores in Statement Archive Viewer (SAV)”  When set to No, only statements of customers whose “Store Account Opened” option matches the current locked-in store will display in the viewer.  When answered Yes, all customer statements will display.

§  New option 3581 “Allow tender type selection for back office ROA payments”.  When set to Yes, back office ROA will include a “Tender Type” drop-down.  Select the tender type which applies to the payment being added or changed.  General Ledger will then be updated accordingly. The default tender type is cash/check (blank or C) but this may be changed to any of these other choices: American Express (A), Discover (I), Master Card (M), Diners Carte (N), Private Label (P), or Visa (V).it is important to note that the system does NOT do bankcard validation, credit card processing, check guarantee, or check endorsing logic in back office ROA.

Also added for this feature is the related new option 3589 “ROA copy tender type to transaction code position.”  When a payment is added in back office ROA, the Tender Type selected will be represented as a one character value in the code position specified by this option in the A/R transaction. This code is visible in the Payments and Credits tab of ROA, in the A/R Transaction viewer, on the RDJ report, and is available in Compass.  This allows additional analytics to be performed on payments based on the specified Tender Type.

Accounts Payable/General Ledger Enhancements

Setup:  A new set of “Prepaid Inventory” types is available in GLSET. There is a store-level Prepaid Inventory type as well as Inventory Department Prepaid Inventory types.  At minimum, the “Store – Prepaid Inventory should have a GL account assigned before setting option 9939 to E or N. The GL account number for Prepaid Inventory should be the same GL account number used when manually entering a voucher for prepaid inventory. Once GLSET has been setup, option 9939 can be set to E or N.

How to use: Create a PO in MPO to account for the inventory being purchased where the vendor is requiring payment.  Manually enter the voucher in ATMU for the PO Vendor as either a Regular or Prepaid voucher. The PO number of the open purchase order in MPO should be entered in the PO number field of the voucher.  “PREPAID” should also be entered in the Voucher Reference field.  When the voucher is posted via RATJ, RATJ will update the PO to prevent the PO from generating a voucher when the PO is received.  When the PO is received, APP should not generate a temporary voucher. The line items received should update ITR with the quantity and purchase cost.  Since they were received in a “prepaid” purchase order the Sub-source should indicate “Prepaid” then the GL Passoff indicator should match to what option 9939 is set to.. For a Normal PO, if the Prepaid ITR records have the GL Passoff flag set to E, when GLP for ITR runs, it will credit the new Prepaid Inventory GL account and debit the Purchases/Inventory GL account form ACON. For a Credit/Defective PO, it will debit the new Prepaid Inventory GL account and credit the Purchases/Inventory GL account from ACON.

Advanced Receiving Enhancements

Method 1 - If you want to ensure that the RV Document does not finalize unless AP Invoice information is entered, set option 8412 to Yes. Any changes to the RV document will not update Inventory Maintenance nor AP and GL unless the AP Invoice information is received and entered in the MRV AP Invoice window. RRV with option F can be run to finalize the RV Document individually or across all RV Documents that have AP Invoice information entered.

Method 2 - If you want to be able to selectively finalize RV documents regardless of whether AP Invoice Information is entered, set new option 8412 to No. You can finalize an RV Document without AP Invoice information individually or by selective batch. This allows any changes to cost and quantity to update Inventory Maintenance as well as update AP and GL without requiring AP Invoice information. As you are working through your receipts, if you don’t want to finalize the RV Document, simply keep the receipt’s Batch field set to No until it is ready to be finalized.  

You can also use a combination of Method 1 and Method 2 - If option 8412 is set to Yes, once the AP Invoice information is entered in the RV Document, you can decide whether to finalize by Batch. RRV with option F can be queued to finalize only RV Documents that are ‘Ready to process by batch.’ Only RV Documents with AP Invoice information entered and have the Batch field set to Yes will be finalized. Requiring both adds additional complexity to the AP process, but also allows for additional checks and balances to ensure accuracy before the RV Document is finalized.

How to Use: After setting option 8412 to Yes, you can make changes to an RV document to add freight or other charges or to change quantity and/or cost, but the RRV-F will not update Inventory nor create the voucher in AP until the Vendor Ref Number, Invoice Date, and Terms Code are populated in the MRV AP Invoice window.

You can leave some RV documents ‘In Progress’ without the AP invoice information entered. An RRV-F in an end-of-day queue with the 'Allow Multiple PO/Date Range Update’ field set to Y and no from/to ranges, will only finalize those receipts which have the AP invoice information entered (Vendor Ref Number, Invoice Date, and Terms Code filled in).  

Any RV document that does not have the required AP information populated will not be finalized and will be recorded in the Misc Log in SHOWLOG.

N – Do not process by batch

Y – Ready to process by batch

Once the clerk is done updating a receiving document in MRV and feels the document is ready to be finalized, they will set the Batch flag to Y ‘Ready to process by batch.’

When RRV-F is run with the new choice B “Only allow update of POs marked ‘Ready to process by batch,’ RRV-F will finalize only the receiving documents with their Batch field set to Y (ready to process).  

Additional notes about using RRV-F with B “Only allow update of POs marked ‘Ready to process by batch’”:  

 How to Use:

  1. Open MRV and display a receipt.
  2. Make any necessary modifications to Invoice Total, Received Amount, Freight, and/or AP Invoice information.
  3. Click the Batch hyperlink located in header area of the receiving document, and select Y ‘Ready to process by batch.’
  4. Repeat steps 1 thru 3 for each receiving document.
  5. When ready, open RRV.
  6. In Update Options, select F – Finalize PO Receipts.
  7. On the From/To page, in the Allow Multiple PO/Date Range Update field, select B ‘Only allow update of POs marked Ready to process by batch.’
  8. Make sure that the PO Number, PO No-Seq, PO Rcpt Date, and Vendor From and To fields are blank.
  9. If multi-store, make sure that the Rcpt’s for Store and Items For Store fields are blank to include all stores.
  10. Press Run. Only the receiving documents that have the new Batch field set to Y will finalize. Any ‘In Progress’ RV documents with the Batch field set to No remain ‘In Progress’.

RRV with the new ‘Allow Multiple PO/Date Range Update’ set to B can be run without selecting option F. It will only report on RV Documents with the new Batch flag set to Yes, but will not finalize them.

Limitations:  New RV sessions will still need to be finalized individually to close the session in order to create a new session. The last session that will mark the sessions as ‘Complete’ can have the Batch flag set to Y.

Telecommunications/National Account Enhancements

Pricing Enhancements

Miscellaneous Enhancements

The following is the "before" behavior where the following bits controlled two different abilities:

The following is the "after" behavior of these existing bits, and their descriptions have been updated to reflect that they now only control the one ability:  

The following is the "after" behavior with the addition of these new bits to control the Accounts Payable abilities previously controlled by bits 414, and 420-423:

Note: Prior to the upgrade to Release 24.1, if a user or role has the existing security bits set to Yes, the user or role will have the existing and new security bits set to Yes after upgrading to Release 24.1.

§  Network Access/Secure Access enhancement. The Eagle Browser now displays either Network Access of Secure Access depending on the setting of option 1098 “Secure Access Enabled.” If the option is Yes then Secure Access displays, otherwise Network Access displays. In addition, Network Access and Secure Access can be launched from the Browser Launch Bar by entering either NA or SA. The correct program will be launched based on the setting of option 1098.

Note:  PCs running Windows 7 or 8 will have a new desktop shortcut for Secure Access automatically created when release 24.1 is installed, regardless of how option 1098 is set.  If the Eagle station already has a shortcut for Network Access or Secure Access, the installation of Release 24.1 does not automatically remove these older shortcuts.  They will need to be removed manually.

§  For Multi-Store users, new option 558 “Default Store to All Stores when changing password in Ebrowser Signon” is available.  When set to Yes, the Change Password in Store field of the Ebrowser Signon screen will default to All stores when using the Change Password feature.  When the option is set to No, the Change Password in Store field will default to the lockin store.

New/Changed Security Bits