Mark accounts as employee accounts in Customer Maintenance. You do this on the Misc tab’s Additional Flags dialog in Customer Maintenance by setting the Customer Type field to E “Employee.” If you use Signature Capture, set new option 4911 “Note/Text to use for Signature Capture for employee purchases” to require employee signatures on all POS transactions.
Customer Code Update (RCCU) enhancement. You can now change the Customer Type and E-Mail Invoice/Credit flags via RCCU.
Customer Maintenance enhancements.
The Department tab’s grid now allows column filtering, and you can save a view of the grid that has a sort or filter.
An account can be set up as write-protected in Customer Maintenance. To do so, set up options 9055 "MCR Account code position to write-protect a customer record" and 9056 "MCR Account code value to write-protect a customer record," and then enter the code value in the code position for any customer record in Customer Maintenance. Any change/delete in Customer Maintenance and in QuickAdd in POS for customer records set up as write-protected will require the user to have security bit 993 "Ability to change protected customer record."
If the new option 9783 "Ask cash/loyalty customers if they want receipts emailed?" is set to Yes, then the blank choice in the Misc tab’s "E-Mail Invoice/Credit" is worded as “Ask if they want emailed receipts (cash/loyalty customers)” and the N choice is worded as “Do not e-mail, do not ask”. If option 9783 is set to No, both N and blank are worded as “Do not e-mail.”
A/R Statements (RSM) enhancements.
There is a new choice D “Summarize payments as detail items” in existing option 3578 “Print payment summary on A/R Statements - Open Item?” If you set this option to D, each payment appears on the statement as one detail line showing the check number of the payment in the Description column and the original document number of the payment in the Reference column. This is so that even if the payment was applied to multiple invoices, a payment detail line prints on the statement only once.
New print option W “Include YTD purchase summary from customer department history.” If the “Keep Dept History” field on the Credit tab is set to Yes for a customer, then the last page of the statement will show “*** YTD Purchase Summary ***” and a line for each department from which they have purchased during the year, with the department’s description in the Description column and the net purchases for that department in the Credit column.
New A/R aging by store. You can now run an A/R Aging Report (RAG) by store to see the A/R aging for just one specific store. Set option 9377 "Allow Aging (RAG) by store?" to Yes so that the Store selection field appears on the RAG’s From/To page. If this option is set to N, the RAG includes A/R transactions for all stores; in other words, the aging will be system-wide (all stores). If this option is set to Y and you select a specific store, then only transactions that were created in that store will be included in the RAG aging totals. For open item customers, if a payment, credit, or adjustment is created in one store, and applied to another store, it is included in the A/R totals for the store to which it is applied. In the G/L, however, if a payment is taken in store 1, it offsets the A/R in store 1, regardless of where it is applied. This means that for open item customers, the G/L by store may not match the RAG by store. For balance forward customers, all A/R transactions are reflected in the store in which they were created. Note: Finance Charge documents and balance forward documents are created based on the "Store Account Opened" in Customer Maintenance. Thus, they will be reflected in A/R based on this store.
Enhancement to the G/L Control Number Viewer which is accessed by pressing T-Acct (F11) from the General Ledger Detail Viewer (GINQ). The G/L Control Number viewer now show all entries made on the same date using the same control number. Prior to this change,the viewer would show all entries made with the same control number, where some entries that were assigned the same control number from a different date would display. Now, when inquiring as to all entries associated with a specific entry in GINQ, only those entries that were assigned the specific control number on the specific date display in the Control Number Viewer.
View Posted A/P Transactions (AVIQ) enhancements.
Check Date is a new column that displays the date selected when processing a Prepaid check through ATMU, or Manual check through RAMP, or Automatic check through APCM, or voiding checks through RPCM. The Check Date column only has a date on transactions whose Transaction Type is Automatic, Manual, or Void. The Check Date also continues to appear in the Invoice Date column.
When using the Lookup by Remit-To Vendor in AVIQ, transaction-type rows such as Automatic, Void, Manual, Credit, and Debit Trx Type now display right below the voucher they reference, so you can easily tell which transactions go with which vouchers.
General Journal Transaction (GGMU) enhancement. You can now save a view with a calculated column in GGMU.
New AP Transactions (ATMU) enhancements.
A new column has been added in the New AP Transaction Viewer for User ID. The User ID column indicates the user who adds a new voucher or changes an existing unposted voucher. For those that use APP (Purchasing to AP Passoff) to create temporary vouchers, "RRP"will be the User ID for these vouchers.
The Remit-To vendor address now appears in the header of ATMU. If there is no address in the Remit To Address fields under the Accounts Payable Tab in Vendor Maintenance, the address from the Main Tab in Vendor Maintenance is used. The address fields are view only, and cannot be modified.
Existing option 425 “Accounts Payable transaction full clear in ATMU” has been enhanced with a new value A to “Clear all fields including the Voucher Date". If you set this option to A, pressing Clear (F12) from the Main tab in ATMU clears all fields and will reset the voucher date and invoice date to show today’s date. This allows you to easily add multiple vouchers which all have the same voucher date. This will help ensure that vouchers are always entered for the current period. Setting this option to No causes the Clear key to clear all fields except for the vendor field, the remit-to vendor field, and the voucher date. Setting this option to Y clears all fields except for the voucher date.
New option 9011 “Execute separate check runs for bank codes assigned to vendors in MVR?” There is a new field “Bank Code” in Vendor Maintenance (MVR) on the Accounts Payable tab. You can now define a specific bank code for a vendor if the bank code will be different than the default bank code in the A/P Control File (ACON). This new field is used in conjunction with option 9011. With option 9011 set to Yes, you can do multiple check runs using the APCM function for all invoices selected in APMU using the new bank code field in Vendor Maintenance. If the bank code entered in APCM is the default bank code in ACON, the system will print checks for all vendor invoices selected where the vendor has either a blank bank code or a bank code that matches the ACON default bank code in MVR. If the bank code entered in APCM does not match the default bank code in ACON, the system will only print checks for the vendor invoices where the bank code in MVR matches the bank code entered in APCM. After running APCM, any invoice that did not meet the bank code criteria is still marked as ‘SELECTED’ in APMU for the user to run APCM for another bank code.
General Ledger Recurring Entries (GSJU) enhancements. You now have more flexibility when recurring entries are posted because you can now determine which entries to post at any given time during the accounting period. This enhancement includes protection against recurring entries being posted more than once within an accounting period.
Two new columns in GSJU – ‘Trx Date’ and ‘OK to Post.’ The Trx Date column will begin populating with the first ‘Post Recurring G/L Transactions (RGJG) that runs after the upgrade to release 21. This date will be the last GL date to which the recurring entry was posted to the GL (the last day of the Current Period in which the RGJG ran). The ‘OK to Post?’ column defaults to Y(Yes), but you can change it to N to control which entries post the next time RGJG runs.
The ability to add transactions using the T-Accounts viewer is now available in GSJU. The T-Acct button (F-11) has been added to the GSJU toolbar.
Post Recurring G/L Transactions Report (RGJG) enhancements. A new "From/To" page in this report gives you more control over which recurring entries will post.
New selection field ‘Transaction Type’ has the choices Permanent, Variable or All transactions. For example, if a user wants to post only Permanent transactions, selecting P for Permanent would only post those transactions whose Transaction Type in GSJU is Permanent.
New selection field ‘Source’ allows you to enter a source that would match a source in GSJU if you only want to post transactions that matched that specific Source. Leaving this blank will look for all transactions regardless of what the Source is.
New selection field ‘All entries to post?’ allows you to choose which transactions to post based on the ‘OK to Post?’ flag in GSJU or all transactions regardless of the ‘OK to Post?’ flag in GSJU.
RGJG will not post a transaction that has already posted in the current period. If the ‘Trx Date’ in GSJU is blank or has a date from a prior period, the transaction will post. If the ‘Trx Date’ has the current period date, it is assumed that the transaction has already been posted and will not post again.
RGJG will not post transactions that are out of balance. The transactions that meet the selection criteria must be in balance in order to post.
You can now pass off the tax amount on transfers to the General Ledger. The transfer customer must have both the Charge Allowed field and the Taxable flag set to Yes in Customer Maintenance. Create a tax code Maintain Tax Codes (MTX) specifically for transfer tax as a way to separate tax liabilities for reporting purposes. This tax code should be assigned to the transfer customers that allow tax on transfers. The transfer will also consider the tax code that is tied to a specific item and will calculate the tax amount based on that tax code rather than the tax code assigned in Customer Maintenance. The tax amount is recorded in the transfer’s "From" store. Transfer customers that have the Charge Allowed set to "T-Transfers" will continue to not allow tax on transfers.
Modify Receiving Documents (MRV) enhancements.
Vendor name and address for the Remit-To Vendor now appears in the AP Voucher window in MRV. If there is no address in the Remit To Address fields under the Accounts Payable Tab in Vendor Maintenance, the system uses the address from the Main Tab in Vendor Maintenance. If there is an address in the Remit To Address on the Accounts Payable Tab in Vendor Maintenance, the system uses this address regardless of whether there is an address on the Main Tab in Vendor Maintenance or not.
The new toolbar button <Inv. Mnt./F11> has been added to Advanced Receiving (MRV). While a SKU is highlighted in the MRV posting grid, you can press the <Inv. Mnt./F11> button. This will take you into Inventory Maintenance with that sku/receiving store.
The MRV grid has these new columns:
Style – The style code used to define the style attribute of an item. This only applies to Softgoods users (option 1052 is set to Yes).
The number of sessions in MRV/RRV has been increased from 9 to 999.
A new toolbar button, Invc Tot (F11) has been added to the Advanced Receiving Document Header Window to calculate the Invoice Total automatically. To display this window, click either the Freight, Other, or Invc Total hyperlinks on the main MRV screen. When you do so, the system adds the amounts currently showing in the ‘Received $’, ‘Freight’, and Other Total fields and updates the Invoice Total field with this amount. This eliminates any potential variance. Once the Invoice Total has been calculated, you still need to press Change (F5) before closing this window to write that new Invoice Total back to the receiving document.
New option 1159 “Mobile Physical Inventory Count List viewing sequence.” Requires that option 9585 "Inventory Item Lists Enabled" was set to Yes, and option 1155 "Mobile Use Physical Inventory with Count List" set to Yes. This option controls the order in which items display when viewing the Item List in Mobile Physical Inventory. Set to L to see the items in order of Location/Sequence Number, set to N to see the items in order of Location/SKU, or set to S to see the items in order of SKU.
Eagle Mobile Inventory, Location Maintenance, and Physical Inventory now have up to six locations for an item. How many locations appear in these applications is controlled by existing option 1136 “Number of Locations Per Item.”
Existing option 62 “Allow setting up Store Groups” is automatically set to Yes on multi-store systems when you install release 21.
Spooler Maintenance (MSP) now has Start and Ending dates for selection criteria to improve usability when there are multiple occurrences of one type of report in the spooler.
New option 9572 “Latest Nightly Maintenance Start Time.” You must consult with an Epicor LPS, Support Specialist, or Product Development before changing this option. Specify a time between 3:30 and 6:30 AM that specifies the latest time that nightly maintenance may start. Enter a time as h:mm (e.g. 3:45, 4:30, 6:00). Notes: 1) See also Osprey function MMO which determines when nightly maintenance begins. Ensure that you have an adequate amount of time between the MMO start time and this option to perform the required maintenance. 2) Also refer to options 9570 and 9571 to assist in the configuration of nightly maintenance performance and scheduling.
Existing option 3509 “Allow access to customer contact fields in Customer Maintenance” is automatically set to Yes when you install release 21 if option 1605 “Windows AR” is set to Yes AND option 1021 “A/R on System” is set to 2.
Security bits 931 and 932 are automatically set to Yes when you install release 21 because they were added to control functionality that existed on prior levels. In addition, bit 985 is automatically set to Yes if existing bit 629 is Yes, bit 987 is automatically set to Yes if bit 212 is Yes, bit 988 is automatically set to Yes if bit 213 is Yes, and 989 is automatically set to Yes if bit 509 is Yes.
New security bits 931 “(MO) Ability to sell Minimum Age (or selling restricted) type 1 items” and 932 "(MO)Ability to sell Minimum Age (or selling restricted) type 2 items.” These bits control the ability to sell items identified as "minimum age type 1 (or 2)’' items. Use options 9413 and 9414 (and 9417 and 9418) to tell the system what items are subject to this minimum age requirement. You can also use one or both of these bits and their corresponding options to restrict selling any type of item – not just minimum age required items. When an item identified as this type of item is posted in Point-of-Sale, if the clerk doesn't have this security bit (i.e., isn't old enough in the case of a minimum age item, or isn’t knowledgeable enough in the case of a "selling restricted" item), then a manager override is required to sell it. This means a manager old enough (or knowledgeable enough) to sell that item is required to signon. Once an override by a manager with this bit has occurred in the transaction, then selling additional type 1 items in that transaction does not require an override. The idea is that a clerk will have this bit set to No until he or she is old enough to sell minimum age type 1 (or type 2 in the case of bit 932) items, or is knowledgeable enough if using these bits and their options for generally restricted items.
The indicator as to what the minimum age type 1 options/bit are being used for (age restricted or selling restricted) is whether or not an age is entered in option 9412. If option 9412 has a value > 0, then the items identified by the user code defined in Options 9413 and 9414 are items which require a minimum age to purchase. Bit 931 is used to restrict clerks not old enough from selling this type of item. If option 9412 is 0, then the items identified by the user code defined in options 9413 and 9414 are items which are selling restricted items, and bit 931 is used to restrict clerks not knowledgeable enough from selling this type of item. These two sets of options/bits are:
931 (security bit) “(MO)Ability to sell Minimum Age (or selling restricted) type 1 items”
9412 (option) “Minimum Age to purchase type 1 items”
9413 (option) “Use Code to identify Minimum Age (or selling restricted) type 1 items”
9414 (option) “Code value to identify Minimum Age (or selling restricted) type 1 items”
and
932 (security bit) “(MO)Ability to sell Minimum Age (or selling restricted) type 2 items”
9416 (option) “Minimum Age to purchase type 2 items”
9417 (option) “Use Code to identify Minimum Age (or selling restricted) type 2 items”
9418 (option) “Code value to identify Minimum Age (or selling restricted) type 2 items”
New security 985 "Ability to access File menu's Load View" is required to use Load View from the File menu. The ability to use Load View used to be tied to option 629 which now solely controls the ability to access the Tools menu (installing release 21 sets the new bit 985 to Yes if bit 629 is set to Yes)
New security bit 987 “Change an item on a purchase order”
New security bit 988 “Add an item to a purchase order”
New security bit 989 “Delete an item from a purchase order”
New security bit 990 “Allow Warehouse Pull Ticket report” (a feature of Buyer’s Purchasing which will be released on L21.1)
New security bit 991 “Access to Prescription Record Management Viewer (RXV)”
New security bit 992 “Allow access to management level data in Compass Business Advisor”
New security bit 993 “Ability to change protected customer record”
New security bit 994 “Ability to delete in e-Invoice Viewer”
Existing security bit 212 used to control both changing a PO’s header information AND changing an item on the PO. Now it only applies to making changes on the PO header, and new bit 987 controls the ability to change an item on a PO. Installing release 21 sets new bit 987 to Yes if bit 212 is Yes.
Existing security bit 213 used to control both adding a PO AND adding an item to a PO. Now it only applies to adding a new PO, and new bit 988 controls the ability to add items to a PO. Installing release 21 sets new bit 988 to Yes if bit 213 is Yes.
Existing security bit 509 used to control both deleting a PO AND deleting an item from a PO. Now it only applies to deleting a PO, and new bit 989 controls the ability to delete an item from a PO. Installing release 21 sets new bit 989 to Yes if bit 509 is Yes.
New security 985 "Ability to access File menu's Load View" is required to use Load View from the File menu. The ability to use Load View used to be tied to option 629 “Ability to access Tools menu “ which now solely controls the ability to access the Tools menu. (Installing release 21 sets the new bit 985 to Yes if bit 629 is Yes.)