What's New on Release 24

Welcome to Eagle Release 24 (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.). For full-featured help for a particular new feature or enhancement, click its blue underlined text.

Eagle N Series

POS Enhancements

Inventory Enhancements

Purchasing and Receiving Enhancements

Accounts Receivable Enhancements

Accounts Payable/General Ledger Enhancements

Advanced Receiving Enhancements

Telecommunications/National Account Enhancements

Miscellaneous Enhancements

Security Enhancements

Eagle N Series

• New options and security bits allow you to customize Eagle N Series to meet the needs of your business.

• • Option 1463 "Legacy compatibility - show keyboard shortcuts on menus"

  • Option 1506 "Legacy compatibility - show numbers on tabs"

  • Option 1507 "Enable Compass features in Inventory Maintenance"

  • Option 1508 "Enable Compass features in Customer Maintenance"

  • Option 1509 "Enable Compass features in Vendor Maintenance"

  • Option 1510 "ATMU legacy compatibility - use toolbar with F-keys"

  • Option 1511 "Catalog E4W compatibility - use toolbar with F-keys"

  • Option 1512 "Customer Maintenance E4W compatibility - use toolbar with F-keys"

  • Option 1513 "Eagle Browser E4W compatibility - use toolbar with F-keys"

  • Option 1514 "Inventory Maintenance E4W compatibility - use toolbar with F-keys"

  • Option 1515 "Point-of-Sale E4W compatibility - use toolbar with F-keys"

  • Option 1516 "Purchasing E4W compatibility - use toolbar with F-keys"

  • Option 1517 "Received On Account E4W compatibility - use toolbar with F-keys"

  • Option 1518 "Vendor Maintenance E4W compatibility - use toolbar with F-keys"

  • Security bit 1086 "Ability to access Chat"

  • Security bit 1087 "Ability to maintain queries in the Eagle Analytics Query Selectors"  

  • Security bit 1088 "Ability to edit fields on the Custom Fields tab of Customer Maintenance"

  • Security bit 1089 "Ability to create/edit/delete Eagle User Defined Tabs in Tab Maintenance"

  • Security bit 1090 "Ability to edit fields on the Custom Fields tab of Inventory Maintenance"

  • Security bit 1091 "Ability to edit fields on the Custom Fields tab of Vendor Maintenance"

  • Security bit 1092 "Ability to access Community"

• Eagle N Series compatibility settings. Compatibility settings allow you to customize Eagle N Series to make it more like Eagle for Windows, in order to ease the transition to Eagle N Series. There are various ways you can customize Eagle N Series:

• • Run Eagle for Windows applications instead of Eagle N Series.

  • Enable Compass features in Inventory Maintenance (IMU), Vendor Maintenance (MVR), and Customer Maintenance (MCR).

  • Display keyboard shortcuts on Misc and Go To menus.

  • Display numbers on tabs, as in Eagle for Windows.

  • Display Eagle for Windows toolbars instead of the Eagle N Series ribbon.

• Compass Tabs. The first release of the Compass Tabs feature includes a set of new Compass-based capabilities for Inventory Maintenance (IMU), Vendor Maintenance (MVR), and Customer Maintenance (MCR).  

• Customize Ribbons and Favorites. Eagle N Series allows you to customize ribbons in applications, so that they only contain those actions (Add, Change, Delete, etc.) that you wish to display. The actions that are not displayed are still available via "All Actions" if they are needed. You can also select features of an application as Favorites, displayed in up to three columns, and modify their order. Note that all changes to both Ribbons and Favorites are system-wide (they display at all terminals, and in all stores if multistore).

• New Record feature. Use this feature to create a customized loading screen for adding and changing customer accounts, inventory records, and vendors. The fields you select will display in the New Record screen, in addition to a set of basic  fields that display automatically. The fields you select can include standard Eagle fields as well as Compass fields. The Compass fields can be Epicor-defined or user-defined Compass fields. The New Record feature is currently available in Inventory Maintenance, Customer Maintenance, and Vendor Maintenance.

POS Enhancements

• Important: If you use POS Touch Screen, you must install the latest version of Touch Screen POS after installing Release 24. All POS stations that use Touch Screen must be updated with the latest POS 2.0 Touch Panel Control.    

1. 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.

• New option 1437 “Minimum amount for manually entered credit card liability notification” for credit authorization. This option controls the minimum transaction dollar amount before a dialog displays telling the cashier to obtain an imprint of the credit card. When the amount being authorized is more than this minimum amount and the card number was manually entered without entering a CVV code, this message displays. This option defaults to a value of 9999.99, indicating that you are not using this capability.

• Special Orders have been made easier to create and maintain, improving usability in the retail environment. If you don’t use special orders today, and would like to, click the hyperlink to learn how to easy it is to set up and use special orders. If you are already creating special orders today, the following new features are available:
• • The Cash Customer Information dialog now allows you to scan the back of the customer’s driver’s license to automatically fill in the fields with the pieces of information available from the license’s 2D barcode. Most but not all states use the 2D barcode. Look for a band of black and white squares in a random pattern. Currently, the following scanners support scanning this 2D barcode: Motorola DS6708-DL, Motorola DS9208-DL, and Motorola DS6878-DL (cordless Bluetooth). The information stored in the barcode varies by state, but typically contains the licensee's Name, Driver’s License Number, and License Issuer fields, and for some states also includes the Address.
  • When you are creating a special order, the Cash Customer Information dialog now has "tool tips" that display to explain the following fields so that the clerk knows what to enter in them: Short ID, Source Vendor, and Stocked Type.
  • Easier posting of special records. When posting a Special Record (freight, labor, or misc) item to a special order transaction, the system no longer defaults to the posting area’s P.O. number; therefore, the clerk no longer has to clear it out to keep that fee from being added to the special order PO.
  • New option 1464 “Display item's cost as asterisks (*) in POS posting area?” This option allows the clerk to enter an item's cost without the chance of a customer seeing it, such as when creating a special order for a customer. If this option is set to Yes, the posting area's Cost field always displays the item’s cost as asterisks (*) on entry and display. This option also applies to the Cost field on the Add SKU dialog used when adding a non-stock item to inventory by posting a template SKU. To view the item’s actual cost, the clerk can click <Menu> and select 3 “Show item costs” to see the unmasked cost. Note: This option applies to all transaction types, not just special orders.
  • New option 9042 “Prompt the clerk for a purchase order number when using RSRV?” This option controls if the ‘Reserve a Purchase Order number’ dialog displays when the item being special ordered is posted with the PO number set to RSRV. If this option is set to No, the system automatically generates a PO number and eliminates this pop-up for special order transactions, special order items added to an order, and special order items on a sale. Note: When set to No, the clerk can't change the PO’s Due Date (which is calculated using the Lead Time in Vendor Maintenance).
  • New option 1468 “Use Options instead of POS\Tools\Options Deposit & Special Order tabs?” This POS option in Options Configuration indicates if you are using the old-style Tools/Options tabs for Deposit and Special Order preference settings, or if you are using Options Configuration to maintain these settings. Best business practice is to set this option to Yes to use Options Configuration. Using Options Configuration is easier to maintain and gives greater flexibility in that you:
  • • Can define these options from one terminal for all terminals, instead of having to set the preferences at each terminal.
    • Have the ability to use any domain (such as Store or System), instead of only "by terminal"
    • Have the added flexibility of different deposit settings for Orders and Special Orders

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):

1. 1. • 1470 - Order Deposit Calculation - 1st range's order total cutoff
      • 1471 - Order Deposit Calculation - 1st range's deposit percentage
      • 1472 - Order Deposit Calculation - 2nd range's order total Cutoff
      • 1473 - Order Deposit Calculation - 2nd range's deposit percentage
      • 1474 - Order Deposit Calculation - highest range's deposit percentage
      • 1475 - Order Deposit Calculation - Minimum Deposit Amount
      • 9364 - Calculate Deposits on Orders for which type of customers?
      • 1476 - Allow Order Deposit to be paid by Bankcard?
      • 1477 - Allow Order Deposit to be paid by Charge?

For Special Orders:

1. 1. • 1480 - S/O Deposit Calculation - 1st range's order total cutoff
      • 1481 - S/O Deposit Calculation - 1st range's deposit percentage
      • 1482 - S/O Deposit Calculation - 2nd range's order total Cutoff
      • 1483 - S/O Deposit Calculation - 2nd range's deposit percentage
      • 1484 - S/O Deposit Calculation - highest range's deposit percentage
      • 1485 - S/O Deposit Calculation - Minimum Deposit Amount
      • 1469 - Calculate Deposits on Special Orders for which type of customers?
      • 1486 - Allow Special Order Deposit to be paid by Bankcard?
      • 1487 - Allow Special Order Deposit to be paid by Charge?

For both Orders and Special Orders:

1. • • 1490 - Create Purchase Orders in POS for Special Orders
     • 1491 - Default sku for posting not in file special order items in POS
     • 1492 - Default Vendor for posting special order items in POS
     • 9390 - Prompt clerk if Reserved PO should be used for other Special Orders
   • Suppress the deposit prompt when deposit calculation is 100%. When creating a special order or an order (or Service order), and that transaction type is set to calculate a 100% deposit, with the proper security the clerk can now bypass the deposit prompt. If the clerk has security bit 539 “Prompt for deposit on orders/special orders/service orders” set to Y and security bit 610 “Allow override of suggested deposit amount” set to N, pressing total enters a 100% deposit and takes the clerk to the tender screen, bypassing the deposit prompt.
   • New option 1467 “Transaction types with 100% deposit that allow edits which change total.” This option allows you to determine if Special Orders or Orders or Service/Repair Orders with a 100% deposit are allowed to be recalled and saved with changes that have changed the total (either up or down), causing the deposit to no longer match the transaction’s total.   
   • New option 1460 “Update special order item cost when cost is changed in MPO.” This option applies when changing the cost of a special order item in Purchasing & Receiving (MPO). This option determines if that change in cost is also made to that item on the customer's special order/order.
   • New option 1465 “Automatically complete invoicing order when total due is .00.” This option controls whether the clerk sees Total Due .00 when a special order, order (or service order), or layaway is being invoiced and the amount due is .00, which is typically due to a 100% deposit.    
   • POS Order Viewer has the new selection criteria field “Special Order P.O.” This allows you to find the customer order(s) linked to the specified purchase order generated from a customer special order (or special order item on an Order).  

• Penny Elimination for Canadian customers (option 9954 set to C) automates accounting for pennies when a POS Received on Account (ROA) is paid by Cash. This feature applies to Canadian stores that have the following options set: Option 200 "Store's Country Code" is  Canada, option 9954 "Penny Elimination in POS enabled" is set to Canadian Rules, and new option 9960 "Penny Elimination Paid Out/In for pennies on an ROA" is not blank. In option 9960, enter the Paid Out/In number that the system should use for a POS ROA for penny elimination. For example, When an ROA is taken in POS and the tender type is Cash, the Change Due amount is rounded to the nearest $0.05 (whether it's up or down) and the rounded pennies are accounted for by automatically posting these pennies as a Paid Out/In to the Paid out type entered in option 9960. For example, if the customer tenders $172.00 in cash for an ROA whose totals is $170.84 for a difference of $1.16, the clerk is prompted to give Change Due of $1.15, and the system automatically creates a Paid In for -.01 to balance the drawer. The receipt/invoice prints the Change that was actually given to the customer ($1.15 in this example), and it prints the Paid-In or Paid-Out amount below the payment section.

Note the following:

• • For invoices, this feature is only supported on enhanced invoice forms.
  • A separate Paid-In/Paid-Out receipt does not print.
  • The Paid-In/Paid-Out uses a journal number (separate from the journal number used on the ROA) and appears in the Daily Journal Viewer (VIEWDJ), and is included on the Daily Sales Report (RDS) for that paid out/in.
• For Multi-Store users, existing option 5157 “Prompt clerk to reprice status R transfers when recalled” has a new choice A “Always reprice without asking.”  When set to A (always), when you recall a status R (Request) transfer, and your terminal is locked into the “From Store,” the system automatically reprices it. The purpose of repricing a transfer when recalled is to ensure the current price is set before shipping the merchandise.
• Existing option 9558 “Dynamic Promotions - does qualifier keep discounted price?” has the new choice A--Retail Price. This option determines if an item(s) that qualifies another item or group of items for dynamic promotion pricing, but which itself does not receive dynamic promotion pricing, should receive a discounted price. This option already had the choice of R--Retail Price unless on promo, in which case the qualifier’s price is reset to the Retail price from Inventory Maintenance, unless it is on a regular promotion in which case it retains that promotion price. New choice A--Retail Price always sells the qualifier(s) at the Inventory Maintenance Retail Price.
• Deposit Activity Viewer (DEP) enhancements.
• • The amount columns now show the amount as negative (and in red font) for Applied and Refunded activities so that a quick sort and subtotal can be done.
  • The new Amount column has been added (initially hidden). This is the total amount of each deposit action. For example, if a deposit action has amounts in more than one tender, the total of those tenders displays. A quick sort and subtotal on this column indicates the remaining deposit of an order.
  • These new columns apply when using the new ‘by Deposit Remaining’ lookup, and are initially hidden:

  • • POS Order’s Deposit Remaining – from the Order’s header, this is the remaining deposit on that order. Note: If the lookup is by Deposit Remaining, and Show Details is "No, show summary only," and if the amount in this column doesn’t match the amount in the Amount column, then both cells display in red to alert you that there is a discrepancy.  

    • Deposit Age – when there is an outstanding deposit on an order, this column shows the aging of the order’s deposit based on today’s date and the Activity Date of the first "deposit taken" record for that Store/Order. These columns indicate 1-30, 31-60, 61-90, and over 90.

    • Days Outstanding - the number of days old the deposit is. For the given Store/Order, it is the number of days since the first deposit was taken, to the date it was fully applied, or if there is still a remaining deposit, it is the number of days since the first deposit was taken, to today’s date.

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.

• 1. • New lookup called Deposit Remaining which has the following selection criteria: All, 31 days and older, 61 days and older, and 91 days and older. It defaults to All. Use Orders Created After to limit the amount of deposit activity records the system searches through when looking for orders with a remaining deposit older than X days. For example, if you select ‘31 days and older,’ the deposit activity for orders with a remaining deposit amount, and the first deposit taken is 31 days old or older, displays. Orders display oldest to newest, the first one in the grid being the oldest order created on or after the date entered in Orders Created After whose first deposit taken was taken at least 31 days ago (and that order still has a deposit remaining). This lookup also has a selection field Show Details with choices of ‘Yes, show the deposit activity’ (default) and "o, show summary only."When No is selected, one row is shown for each order where the Amount column is the summation of all deposit activity for that order and therefore is the amount remaining of the deposit.  The same applies for each of the tender types. The columns such as Activity Date, Activity, and Activity Store show this information for the last deposit action taken on that order.

• Special Order Simplification is a new configuration wizard for customers implementing Special Orders for the first time. "Special Order Setup" is accessed from the Ribbon’s File menu of Eagle N Series POS or the Tools menu if using the toolbar in POS. This feature is already set up to use options related to special order creation and workflow according to Epicor’s best business practice, and walks you through configuring a set of 13 to18 options to meet your specific needs. If Calculate Deposits is set to “% of total,” you are instructed to click the <% of Total> button. Use the Summary View to see a recap of how all 13-18 options are currently set. The Current Value column shows the setting selected in the wizard.  Some settings in the wizard update more than one option. Sliding the horizontal scroll bar to the right shows the present settings for the actual options in Options Configuration.

• New option 5098 "Restrict modifying or invoicing an order selected for Batch Invoicing." Set this option in Options Configuration to Yes if you want the system to restrict recalling an order or special order in POS and modifying it, when that transaction has already been added to an invoicing batch. Setting this option to Yes causes the system to automatically place an identification code of B in the second header code position when an order or special order is added to an invoicing batch (added either manual or by a report process such as ROO). Subsequently, in POS if a user recalls a transaction that has been coded with the B, indicating the order resides in a batch, a warning displays to indicate that changes are not allowed. If the user has security bit 1098 "(MO) Allow recall and edit of order/so selected for Batch Invoicing" set to Yes, they have the choice to continue. If the user has this bit set to No, then a manager override is required for the user to continue with any changes in the header area or to proceed to posting.

• Cash Drawer Balancing Viewer (CDB) has two new columns. The new column “Dynamic Coupons #” displays the number of coupons used to activate Dynamic Promotion discounts given. The new column “Dynamic Coupon” displays the dollar value of the discounts given.

• New option 1503 “Print Dynamic Promotion Coupon Redemptions on the RDS Report?” When this option is set to Yes, the number of coupons used by consumers to redeem a Dynamic Promotion discount prints on the Daily Sales (RDS) report's Cash Balancing Worksheet. The amount of discount which was given as a result of using the coupons also prints. This can be used for security purposes; the amount of coupons in the cash drawer should match the amount of coupons printed on the report. If there are more coupons on the report than in the cash drawer, then the cashier might be giving the promotional discount to consumers that do not have the coupon. The same information is also displayed in the Cash Drawer Balancing (CDB) viewer, under the columns "# Dynamic Promo Coupons' and 'Dynamic Promo Coupons." When this option is set to No, the Dynamic Coupon line does not print on the RDS report.

Windows Inventory Enhancements

• New option 1434 “Update Kit Header's Mfg Cost with Total Retail Value of components.” Set this option to No if you don't want the system to update the kit header SKU's Manufacturer (Mfg) Cost with the total of the component SKUs' retails. Modify Kits (MKR) will still show this total in the Total Retail Value field, but will not place that value in the kit header's Mfg Cost. When set to Yes, the system updates the Mfg Cost field of the kit header SKU in Inventory Maintenance with the total of the component SKUs' retails. This option applies to adding or changing a kit in MKR where the Total Retail Value field shows the total of the component's retails. This option also applies when running the Kit Report (RKR) with Update Option U "Update Cost and Retail."

• Physical Inventory Posting (PIP) – Use the new toolbar button <Inv Maint/F7> to launch Inventory Maintenance and display that item in the count file. In PIP, click the grid row of the item you want to display in Inventory Maintenance, and press F7.   
• New fields in Inventory Import Tool. You can now import the following fields: Order Point A, Order Point B, Order Point C, Order Point D, Max Stock Level A, Max Stock Level B, Max Stock Level C, and Max Stock Level D.

• New option 1504 “IMU - Give "unsaved changes" warning upon exit or changing tabs?” This option applies when you have made changes in Inventory Maintenance (IMU) that have not been saved by pressing <Change>, and you attempt to change tabs or exit Inventory Maintenance. This option controls whether you receive a warning that there are unsaved changes, and have the ability to answer Yes to save those changes, or to answer No to not save those changes. Set to B (Both) to be warned there are "unsaved changes" when you attempt to change tabs or exit Inventory Maintenance. In both cases, you are asked if you want to save those unsaved changes, and the answer defaults to Yes. Set to E (Exit Only) to be warned there are "unsaved changes" only when you attempt to exit Inventory Maintenance. If the system detects there are unsaved changes when changing to another tab, no warning is given, and the system automatically saves those changes. Set to T (Tabs Only) to be warned there are "unsaved changes" only when you attempt to change to another tab. If the system detects there are unsaved changes when you exit IMU, no warning is given and the system automatically saves those changes. Set to N (Neither) to receive no warning when changing tabs or exiting IMU. If the system detects there are unsaved changes, no warning is given, and the system automatically saves those changes.
• Streamlined Label Printing
• • Both Modify Item Promotions (MIP) and Item Price Changes (IPC) have the new toolbar button <Labels>. This button facilitates printing labels directly from these grid-based applications. You can print labels immediately, save records from grid -based applications to Label Manager, launch the label manager and select the records  for which you want to print labels, or save records from grid-based applications to “batch” files for later processing.
  • Activate a promotion from Modify Item Promotions (MIP). Use the new <Activate> toolbar button to launch Update Promotion Price Report (RUP) to activate a promotion.  
  • Finalize price changes from Item Price Changes (IPC). Use the new toolbar button <Finalize> to launch the Price Change Report (RPC) to finalize price changes.  
  • Label Manager has vastly improved usability for the <Import> function, now called "Batch Management." When you press <Import>, you can pinpoint the batch(s) you want to print by entering the batch’s Store, Source, Created By User, Terminal Created at, and From and Thru Created date range. The batch(es) that match your selection criteria display, and you can either Print Now, Add to Label Manager, or Delete.

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.

• • New option 5825 “Create label batches by store from RBL or using <Labels> in MIP and IPC.” This new option allows multistore users to create a separate batch file for each store so that you can more easily print your own labels to your store’s printer. This option applies when:
  • • Using the Item Bin Labels Report (RBL) from the Price Change File or Promotion File with the Store field set to ALL and using Label to Use "Generate File for Label Manager" to generate a file for the range of items by store that you want to import into the Label Manager. A batch is created for each store the selected items represent.  
    • Using the <Labels> button in Item Price Changes (IPC) or Modify Item Promotions (MIP) and selecting "Save to new batch" to place the selected price changes or promotion records into a file for import into the Label Manager and the selected items are for more than one store.  A batch will be created for each store the selected items represent.

• Bin Label Report (RBL) enhancements:

• 1. • RBL can now be added to an End-of-Day queue. This change allows you to use the new ‘Days before Effective’ (Price Changes) and new ‘Days before Start’ (Promotions) to add RBL to a daily queue to print labels for price changes whose effective date is X days away or promotions whose start date is X days away. For example, a daily RBL using the Price Change file, with ‘Days before Effective’ set to 1, prints labels for price changes whose effective date is tomorrow.  

     • RBL from Price Change file enhancement. There is a new field on the RBL Options page called “Days before Effective” that allows you to create label batches the designated number of days before the effective date that you enter. This field defaults to blank, and is only valid when using Label to Use "generate file for label manager." in RBL. Note: If RBL is run with Store=All and option 5825=Yes, it generates a batch file for each store.
     • RBL from Promotions File enhancement. There is a new field on the RBL Options page called “Days before Start” that allows you to create label batches the designated number of days before the start date that you enter. This field defaults to blank, and is only valid when using Label to Use "generate file for label manager." Note: If RBL is run with Store=All and option 5825 is set to Yes, it generates a batch file for each store/each promotion type. If you have a single-store or multistore system, but option 5825 is set to No, RBL generates a batch file for each promotion type. Note: this enhancement doesn’t apply to Progressive Promotions where it is the Update Promotion Price Report (RUP) that generates a label file for Label Manager.

• New option 7320 “Days to Keep Label Manager batch files.” This option lets you control how long label batches, which were not manually deleted after use, stay on the system. A label batch will be deleted if its Date Created is older than the number of days specified in this option. This purge is run during the monthly archive purge.  
• Catalog enhancement. The Add Item dialog contains two additional fields: # Bin Labels and Order Indicator.   
•  Update Promotion Price Report (RUP) new report option G “Finalize (activate only) a single promotion. Option G activates a single promotion with a start date of today or earlier (not tomorrow as option F does), and it neither deactivates nor deletes items on a promotion set to end today. The purpose of this new option is to activate a one-day promotion, or to add items to an already active promotion. You can use option G with Y “Update IMU with the lowest promo price” so that RUP checks if any of the items being activated are on another active, overlapping promotion, and if so, the lowest promotion price between the two is recorded as the item’s promotion price in Inventory Maintenance. Note: Option G cannot be used with option F and must be run for only one promo type.
• Exclude Item Lists from being finalized in the Physical Inventory Report (RPI). For Directed Counts users (options 1100 “Eagle Mobile on System”, 9585 “Inventory item Lists Enabled”, and 1155 “Mobile Use Physical Inventory with Count List” are all set to Yes), the Physical Inventory Report (RPI) has a new “Exclude (Y/N)” field in the From/To section of the report. If you select an Item List and set the “Exclude (Y/N)” field to Y, the system ignores all items on the specified Item List, and only finalizes items within the specified From/To range, including Sequence/SKU, Department, Class, Fineline, Prime Vendor, Manufacturer, Location, Mfg Part #, Last PI Date and Shrinkage Type. If you leave the “Exclude (Y/N)” set to N, the system only finalizes items that are on the specified Item List and ignores all other items in the count file. Before this change, RPI could only either finalize items on a specific Item List, or all items in the count file, including any Item Lists..

Windows Purchasing & Receiving Enhancements

• New Receipt Posting (RRP) Update Prices option S “Create Price Changes in IPC (use with options P or Q).” This new option allows you to create price change records with the new retail price calculated from what will be the new average cost once the PO is finalized, and the item’s Desired Gross Profit Percent. This means you can now manage price changes in one place--Item Price changes (IPC)--and you can do so as soon as the Freight and Other Charges have been entered (if any) and the item receipt quantities and costs have been entered. This saves a step in that you no longer have to print bin labels (RBL) from the PO for the retail changes before you finalize the PO.

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:  

1. 1. In Purchasing and Receiving, receive a PO by Receive All or Receive Only method, adjusting any receipt quantity and cost on any or all of the line items.
   2. Go back to the PO Header and enter any Freight or Other Charges (optional).
   3. Run RRP for the PO with only option P or Q, as well as option S.
   4. If any landed cost changes resulted in a retail increase or decrease when recalculated against the current desired gross profit percent, a price change record for the item is created in IPC. RRP also reports any retail price changes.
   5. Run RRP again with option F to finalize the PO and to update Inventory Maintenance. This only updates quantities and cost.
   6. Any price changes are updated in Inventory Maintenance only when you run the Price Change Report (RPC) with option F.

Windows Accounts Receivable Enhancements

• Integration with Blue Tarp Financial. As a purchase option, you can now integrate your Accounts Receivables with Blue Tarp Financial. For more information about purchasing this feature, call your Customer Account Manager at 800-538-8597.
• The term "Loyalty Gift Card" has been changed to "Loyalty Dollars." This change is due to legal and financial implications, since loyalty rewards are not a liability, and gift cards are. This term has been changed in the following applications and options:
• • POS Customer QuickAdd – the "Loyalty Gift Card Number" field now reads "Loyalty Dollars ID”
  • POS Customer Detail dialog – the “Loyalty Gift Card $” now reads “Loyalty Dollars”
  • Gift Card Viewer Misc Menu – the report "Set Loyalty Gift Card to Zero (GCS)" is now called "Set Loyalty Dollars to Zero (report GCS)"
  •  For options 3534, 9067, 9068, 9129, 9894, and security bit 900, their descriptions contain the new terminology

• Eagle Loyalty now has 10 tiers available for entering the amount of points required to earn a coupon reward. Options 9877 and 9878, which were used to set up a single tier of points and the corresponding reward, are now tier 1, and an additional nine tiers can be set up in options 1442 through 1459. You can use any number of tiers,they don't have to be in ascending order, and you can have gaps between tiers. A tier is only valid if you have entered both the points and coupon for that tier. The system skips any invalid tiers (one that doesn’t have both a points level and coupon), and it looks for the highest tier for which the customer is qualified and uses the coupon that is assigned to that tier.  
• New security bit 1069 “Allow changing Charge Allowed in Windows ROA.” This bit controls the ability to use ROA’s Misc Menu 2 “Change Charge Allowed” to change the customer’s Charge Allowed field in Customer Maintenance (MCR). Note: Today if you have access to ROA (bit 306 is Yes), you can use this capability. Installing release 24 automatically sets new bit 1069 to Yes if bit 306 is Yes.   

• Change Customer Number (CCN) & Change Customer To Job (CCJ) now include Dynamic Promotion PUNCH records (Dynamic Promotion Types 11 & 12). This is useful if you use Punch Card Promotions, and you have a customer who accidentally signed up as a loyalty member more than once, and has purchased items that qualify for the PUNCH promotion under the different accounts. You can run CCN / CCJ to combine the accounts, which merges their PUNCH records.
• Customer Contacts Management streamlining. If you email customers their POS transactions and/or you A/R statements, Release 24 consolidates all emails for customers into the Contacts tab of Customer Maintenance. The fundamental change is that the email address(s) in Note Type 10 (statement emails) and Note Type 11 (invoice emails) have been consolidated to Contacts, so you no longer have to add the contact and then add the email address to Note Type 10 and/or 11. If you have been using Compass, RQ, or ODBC to get emails from Contacts and Note Types 10 & 11, this will still work, or you could change it to get customer email addresses from only the Contacts tab. You no longer use the Notes tab to add an email address for POS invoices or A/R statements--instead, you add the contact on the Contacts tab, with the email address, and set the new Statement and/or Invoice field appropriately.

Installing Release 24 copies all of the email addresses in Note types 10 and 11 into Contacts. Notice that Note Type 10 and 11still 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:

1. • If the account (job) is not set up on the Misc tab to receive emailed documents, or it is but you don’t want this contact to receive emailed POS documents, set Invoices to N.
   • If the account (job) is set up on the Misc tab to receive emailed documents and you want the contact to receive emailed POS documents, set Invoices to Y, or one of these other choices:  
   • • If the account is set up on the Misc tab to receive invoices/credits and order/special orders/estimates, but you want this particular contact to ONLY receive emailed invoices/credits, then set Invoices to I.
     • If the account is set up on the Misc tab receive invoices/credits and order/special orders/estimates but you want this particular contact to ONLY receive emailed orders/so/estimates, then set Invoices to O
     • You can further refine a contact to only be a Cc on all document types (set to C), Cc on only invoices/credits (set to J), or Cc on only orders/so/estimates (set to P).
     • You can further refine a contact to only be a Bcc on all document types (set to B), Bcc on only invoices/credits (set to K), or Bcc on only order/so/estimates (set to Q).

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::

1. • Existing option 9140 “Where to place e-mail address from POS Customer QuickAdd” no longer applies.
   • Customer QuickAdd’s Maintain Customer Contacts, displayed by clicking on the E-Mail hyperlink, no longer has the <Statement Email Address> and <Invoice Email Address> buttons.
   • The <Add> and <Change> dialogs that come up from the Maintain Customer Contacts include these four additional fields: Primary Contact, Opt Out, Statements, and Invoices.

The Customer Contacts Viewer as 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.

Accounts Payable/General Ledger Enhancements

• Import Eagle journal entries into QuickBooks.™ As a purchase option, you can now import financial data into QuickBooks General Ledger or import payroll data from Quickbooks Payroll into Eagle General Ledger. For more information about purchasing this feature, call your Customer Account Manager at 800-538-8597.
• New option 426 “ATMU - Return cursor to Vendor instead of Trx Type.” For streamlined data entry, set this option to Yes so that pressing <Clear> between transactions in New A/P Transactions (ATMU) automatically sets the transaction type to R-Regular Voucher, and places the cursor in the Vendor field. The same occurs after using <Check> to print the AP check. If this option is set to No, the cursor returns to the Trx Type field on the main screen of ATMU.

• New option 9896 “Always prompt for A/P dated billing when adding a new voucher?” If you use “Accounts Payable Dated Billing” (option 9895=Y), this option controls if the prompt to set up installments displays each time a regular voucher is added in New A/P Transactions (ATMU). Enter Y to continue to receive the "Installments" prompt each time you add a new A/P voucher in ATMU with the default answer set to Yes, enter X to prompt and default to No, or enter N to not prompt to set up installments for each new voucher added. Use Go To menu option B “Dated Billing Maintenance” to enter installment information for a voucher at any time. Alternatively, if option 9896 is set to Y or X, you can also use <Change> on the un-posted voucher to enter the installment information.  

• You can now run the Post New A/P Transactions Report (RATJ) right from ATMU’s <Post> menu using choice 3 “Post Signed On User Transactions to A/P Files.” If you have option 9009 “Reduce exclusive use of AP & GL transaction files” set to Yes, then using Post option 3 queues the RATJ to post the transactions that the current signed-on user added in ATMU. To begin using ATMU’s <Post> choice 3, enter the channel you want the RATJ to use in option 435 “Spooler channel to use when posting A/P transactions by user?” How to use: After posting AP vouchers in ATMU, press Post (Shift F2). Select the new choice 3. This new Post Menu option automatically queues RATJ to the channel entered in option 435 and with the with the current signed-on user entered in the report’s From/To User so that only transactions for that user will be posted.  

• After selecting invoices to pay in APMU, use the new <Print Chk/KPad+> toolbar button to open Print Checks (APCM). This allows you to print the checks for those payments without having to close out of or minimize APMU. Simply press the + on the keypad or click the <Print Chk> button. This opens APCM beginning with the printer selection to Print Checks.

• Check Reconciliation (ACKR) now supports using the High Capacity grid.   

• You can now set up AP Control File Maintenance (ACON) in Eagle. Prior to this change, new A/P users had to set up ACON in Network Access. How to use this new feature: After entering all of the information needed in ACON, click Change. If Accrue Temp A/P Trx’s? is set to Yes, you must specify an Accrued A/P and Accrued Purchases GL Account. Access to ACON requires security bit 338 “Change A/P constants” (same bit as in Network Access).

• You can now run ABMU directly from Eagle Browser to maintain your bank codes. Access requires security 411” Add/Change/Delete/Report A/P bank codes”. Note: ABMU is still also available from ATMU’s Go To menu.

• Accounts Payable/Notes enhancement. The A/P Remittance Note entered/maintained in either Purchasing (MPO) (Misc Menu N) and/or Modify Receiving Documents (MRV) (Misc Menu N) now carries over to the A/P Voucher, and can be viewed/maintained in both A/P Invoice Maintenance and Payment (APMU) and Posted A/P Transactions (AVIQ).  

• New option 1520 “In ATMU ignore distribution tab when vendor is set up with auto-distribution.” Setting this option to Yes streamlines adding a voucher for a vendor configured to automatically distribute to G/L accounts set up for that vendor. Adding a voucher in New A/P Transactions (ATMU) will no longer take the clerk to the distribution tab to confirm the distributions. The message “Record Added – Transaction Auto-Distributed” displays at the bottom of ATMU, indicating that the voucher has been added and is fully distributed. Note: To set up an account for auto-distribution, set the Auto Distribute flag on the Accounts Payable tab of Vendor Maintenance to Yes.

Advanced Receiving Enhancements

• Enhancement for multistore users in Modify Receiving Documents (MRV). When using <Add/F4> to add an item to a receiving document, the Store in the "Add SKU to Receiving Document" now defaults to the store the P.O. was created in, instead of the lockin store as it did before this change.
• The next two enhancements (Method 1 and Method 2 below) facilitate the ability to run the Receiving Documents Report (RRV) with option F in an end-of-day queue for all receipts, and it will only update those receipts which are ready to be finalized. You have two methods to select from to indicate receipts ready to be finalized. These guidelines will help you to select which method best meets your needs:  

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.

1. • Method 1:  Receiving Documents (RRV) – New option 8412 “Require MRV's AP Voucher entry before processing Adv. Receiving document” which when set to Yes causes the RRV-F to process an Advanced Receiving document, will now requires that these 3 fields have been entered on the receiving document before the RRV-F will finalize the receiving document to update both Inventory Maintenance and create the AP Voucher: Vendor Ref Number, Invoice Date, and Terms Code.  If an RV document does not have all three fields populated in the MRV AP Invoice Window at the time the RRV-F runs, the RV document will remain ‘In Progress’ and no updates will occur to inventory or AP.  

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’s, 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.

1. • Method 2: Modify Receiving Documents (MRV) & Receiving Documents (RRV) – A new field called “Batch” has been added to the header area of MRV as well as to the Document Header dialog, displayed by clicking any of these hyperlinks: Batch, Freight, Other,or Invc Total. The choices for this new field are:

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’”:  

1. 1. • If Option 8412 is set to Yes, a receiving document with Batch set to Yes which does not have the AP Invoice information entered (Vendor Ref Number, Invoice Date and Terms Code are not all filled in) will do no updating to inventory or AP.
      • If Option 8412 is set to No, a receiving document with Batch set to Yes which does not have all of the AP Invoice information entered will finalize, updating the inventory information and creating a T-type AP Voucher.   

 How to Use:

1. 1. 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

• Send Inventory and Pricing to Do it Best. The Eagle system can collect and send your store’s inventory and pricing information to Do it Best. Your Eagle sends only six-digit numeric SKUs with Prime Vendor set to Do it Best. This process is known as Inventory Data Feed and replaces the obsolete IMCS data feed. This data feed checks to see if any of the following fields were changed since the last time data was sent. If so, it sends the new data:

Discontinued flag

Store Closeout flag

Location

Retail

QOH

QOO

Keep Prices flag

Keep Stock flag

Date of Last Sale

UPC code

Item added to system

Item deleted from system

• New option 3242 “Write price change records for both Repl and IV cost changes?.” This option determines if the price change record for a new cost is created with not only a new replacement cost (or manufacturer cost) but also a new alternate vendor cost if the item’s alternate vendor matches its primary vendor. You must use EFM Update Option C “Update Repl Cost Only” to take advantage of this option. Use of option 3242 allows users who receive price changes electronically and that use PO Worksheet (Buyer’s Purchasing) to synchronize the replacement cost (or manufacturer cost) to the corresponding alternate vendor cost. For systems set up to use Buyer’s Purchasing, inventory is set up so that the Primary and/or Mfg Vendor also has a corresponding alternate vendor record. For example, item 12345 is set up with the primary vendor as ABC and an alternate vendor as ABC. When receiving price changes electronically via EFM from vendor ABC, the system can download the cost update to replacement cost and alternate vendor cost.

Miscellaneous Enhancements

• Purges for Dynamic Promotions (option 9849) and Item Lists which are used for Dynamic Promotions (option 9850).  
• • New option 9849 “Days to Keep Dynamic Promotions” has been added so you can control when inactive promotions are deleted by the monthly archive purge. An inactive promotion is deleted once its End Date is older than the number of days entered in this option.
  • New option 9850 “Days to Keep Dynamic Promotion Item Lists” has been added so you can control when Item Lists used by Dynamic Promotions are deleted by the monthly archive purge. The item list is deleted once its Date Last Updated is older than the number of days entered in this option AND the Dynamic Promotion(s) which use it are no longer in Maintain Dynamic Promotions (MDP).   
• New security bit 1063 "Delete end-of-day queues or a report within a queue.” Set to Yes to allow a user to delete queues or reports within a queue in End-of-Day Queue Maintenance (MEQ). Otherwise, set to No. Previously, existing bit 80 “Change report queues” controlled both the <Change> and <Delete> commands in MEQ. Bit 80 now only controls the use of <Change>, which is used to add/change comments to end-of-day queues and change the order of reports. Note: The upgrade to Release 24 sets new bit 1063 to Yes for those users/roles which have existing bit 80 set to Yes.
• New security bit 1064 “Delete scheduled report queues.”  Set to Yes to allow a user to delete scheduled queues in Schedule an End-of-Day Queue (SEQ). Otherwise, set to No. Previouslyb existing bit 22 “Add and Change scheduled report queues” controlled <Add>, <Change> and <Delete> commands in MEQ. Bit 22 now only controls the use of <Add> and <Change> for respectively adding and changing scheduled report queues. Note: The upgrade to Release 24 sets the new bit 1064 to Yes for those users/roles which have existing bit 22 set to Yes.  

•  You can now have the Element Settlement (EESTL) loaded into an End-of-Day (EOD) queue and it will settle that day’s transactions. When adding EESTL to an EOD queue, leave the from/to for Query Date blank, and enter a Y in the drop-down to have it run each day using the run date for the selection of the data.
• "Change Store" in Options Configuration's Misc Menu’s choice 3 "Add/Change/Delete Store" has two new fields which can be entered for a store. They are information only, and are Date Store Opened and Date Store Closed.
• Security bits that once controlled functions to both Physical Inventory and Accounts Payable have now been separated into their own individual security bits. Note: The upgrade to Release 24 will set the new bits to Yes if the existing bits are set to Yes.

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

1. • 414 – “RF – Allow RF Shelf Manager UPC Operations.” This bit allows access to UPC Maintenance in the RF Menu. This bit also controls the Post A/P Adjustment Report (RAAJ) in both Network Access and Windows.
   • 420 – “Add physical inventory counts using quick mode (QPIP); also APPM.” This bit controls the ability to access QPIP in Legacy and the QPIP button in Windows PIP. This bit also controls access to the APPM menu – “Void Posted Checks” in Network Access and Windows.
   • 421 – “Change physical inventory constants and shrinkage types; also APPV” This bit controls the ability to access MPI in Network Access as well as MPI options in Windows. This bit also controls access to the APPV menu in Network Access as well as running RPCM in Windows.
   • 422 – “View physical inventory history; also APRI." This bit controls access to view physical inventory history in both Network Access and Windows. This bit also control access to APRI “Reset A/P Invoice File” only available in Network Access.
   • 423 – “Add/Change/Delete physical inventory counts; also APRM.” This bit controls access to Physical Inventory Posting (PIP) in both Network Access and Windows. This bit also controls access to APRM (AP Recurring Vouchers) in both Network Access and Windows.

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:  

1. • 414 – “RF – Allow RF Shelf Manager UPC Operations.” This bit allows access to UPC Maintenance in the RF Menu.
   • 420 – “Add physical inventory counts using quick mode (QPIP).” This bit controls the ability to access QPIP in Legacy and the QPIP button in Windows PIP.
   • 421 – “Change physical inventory constants and shrinkage types.” This bit controls the ability to access MPI in Network Access as well as MPI options in Windows.
   • 422 – “View physical inventory history.” This bit controls access to view physical inventory history in both Network Access and Windows.
   • 423 – “Add/Change/Delete physical inventory counts.” This bit controls access to Physical Inventory Posting (PIP) in both Network Access and Windows.

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:

1. • 1081 – “Allow A/P invoice adjustments report (RAAJ).” This bit controls the Post A/P Adjustment Report (RAAJ) in both Network Access and Windows.
   • 1082 – “Access to A/P Void Checks (APPM).” This bit controls access to Voiding Checks function APPM. It also controls use of Network Access APPM 5 "Post Void Check Transactions to A/P files."
   • 1083 – “Post A/P Void Checks.” This bit controls access to Network Access APPM A/P Void Check and Eagle Browser RPCM.
   • 1084 – “Access Reset A/P Invoice File (APRI).” This bit control access to APRI “Reset A/P Invoice File."
   • 1085 – “Access to A/P Recurring Vouchers (APRM).” This bit controls access to APRM (AP Recurring Vouchers).

Note: Prior to the upgrade to Release 24, 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.

• Options Configuration now has a new, simpler, more powerful lookup screen.  
• • Search – The system will search the Option’s description and extended description for the value you enter in this field, and display those options which contain that value. Note: Entering multiple words (partial or entire word) in the Search field does an "and" search. For example, entering SPEC ORDER will find options that have a word that begins with spec (ie special or specify) AND also has a word that begins with order. In this example, the search would return option 432, since it contains order and specify. Entering SPECIAL ORDER will not include option 432.
  • Options Group – Use this to display All options (default), All options plus security bits, or a logical grouping of options.
  •  "All Options+Security" Select this Options Group to search for security bits. You can identify security bits in the Options grid because the "Type" column says "MSE," and the Message column contains the string “<-- Security NNNN,” where NNNN is the security bit. Note that this is a lookup-only feature; if you want to change a user's security, you must use Security Maintenance to do so.
  • <ID> button on the toolbar – You can use the <ID> button to display a specific option if you know its ID number.

• POS security enhancement. This enhancement is available to those not using as well as those using High-Security Passwords. A user is prompted with the message “Password Change Required” when the following conditions are met:

• • If option 556 "Allow <Change Password> function in POS Signon" is set to Yes

  • If the user entered the correct password or the User Record (MUR) is set up as "Check Password At P.O.S." = No

  • If the user has security to sign on to this terminal/store

  • If the clerk is not the same clerk from the last POS Signon on this terminal for this POS session

  • If clerk has “Require Password Change” set to Yes in the User Record (MUR)

New/Changed Security Bits

• 1062 “Ability to generate 'restricted use' UPCs in Maintain UPC Codes”
• 1063 "Delete end-of-day queues or a report within a queue”.  (L36 SE/TE advance will set to Yes if existing bit 80 is Yes.)
• 1064 “Delete scheduled report queues” (L36 SE/TE advance will set to Yes if existing bit 22 is Yes.)
• 1065 “Ability to access the Vendor Report Card tabs of MVR”
• 1066 “Ability to change fields on the Vendor Report Card tabs of MVR”
• 1069 “Allow changing Charge Allowed in Windows ROA” (L36 SE/TE advance will set to Yes if existing bit 306 is Yes.)
• 1081 – “Allow A/P invoice adjustments report” This bit controls the Post A/P Adjustment Report (RAAJ) in both Network Access and Windows.
• 1082 – “Access to A/P Void Checks (APPM)”This bit controls access to the APPM menu – “Void Posted Checks” in Network Access and Windows.
• 1083 – “Post A/P Void Checks” This bit controls access to the APPV menu in Network Access as well as running RPCM in Windows.
• 1084 – “Access Reset A/P Invoice File” This bit control access to APRI “Reset A/P Invoice File” only available in Network Access.
• 1085 – “Access to A/P Recurring Vouchers” This bit controls access to APRM (AP Recurring Vouchers) in both Network Access and Windows

• 1086 – “Ability to access Chat”
• 1087 – “Ability to maintain queries in the Eagle Analytics Query Selectors”
• 1088 – “Ability to edit fields on the Custom Fields tab of Customer Maintenance”
• 1089 – “Ability to create/edit/delete Eagle User Defined Tabs in Tab Maintenance”
• 1090 – “Ability to edit fields on the Custom Fields tab of Inventory Maintenance”
• 1091 – “Ability to edit fields on the Custom Fields tab of Vendor Maintenance”
• 1092 – “Ability to access Community”
• 1093 – “Ability to use Edit capability in New Record function”

• 1094 – “Allow access to Purchase Order Worksheet (POW)”

• 1095 – “Ability to access and change the vendor's ACH information”