New Feature Summary
This section describes the new features that are available in EAM 2015.
Shared AppShell with QAD Enterprise Edition
EAM 2015 is now available to run in the same instance of the AppShell and in the same workspaces as EE. It is visible in the EE menu when properly licensed.
• Login and Password Changes. EAM 2015’s login process has been altered to comply with Enterprise Edition 2015 rules. When running in the same AppShell with Enterprise Edition 2015, EAM uses the EE password policies. Additionally, if LDAP integration is enabled in EE, EAM relies on EE to validate login ID and password. EAM retains the rest of its security mechanisms, including EAM Role and User/Role functionality.
ERP login ID and password maintenance have been moved from the system registry to a new action on the System Control browse. Users with permission to access this action can enter the ID that EAM uses to access EE’s APIs. The password for this ID also can be entered and changed. It is protected from view so that it remains secure and, when changed, must be entered twice to ensure that the user entered the value accurately.
When a password is changed in a merged 2015 AppShell, EAM does not check to see if the new password matches the old or previous passwords. When a password is reset in EE by an administrator and the next login forces a password change, EAM does not check to see if the new password matches the old or previous passwords.
EAM’s Change Password User browse action is disabled in a merged 2105 environment.
• Prior Version E-mail Hyperlinks Inactive. As a result of EAM’s move into the core AppShell, some of EAM’s menu IDs changed. This change caused the hyperlinks in EAM e-mails to break. When upgrading to EAM 2015, the links in all e-mails prior to the upgrade no longer work.
• User Maintenance. When EAM is integrated with EE in an environment that has 2015 EE or higher, the addition or deletion of system users within EAM is no longer allowed. These actions must be completed in EE and downloaded into EAM.
Work Order Document and Printing Enhancements
Work Order Print now prints safety instructions before any other instructions lists. Previously, the instructions lists were printed in ascending order of the instruction list number.
When selecting Global Print Document for work orders, you can now print the documents or links attached to all selected work orders.
An alternate work order document format is available to print and manually mark up as you address the tasks for the work order. The document displays a selection of available codes that can be manually selected: Class, Repair, As Left, and As Found. Shift and Failure Code can be entered on the printout. You also can indicate yes or no for Leave WO Open and Waiting on Parts. For instruction lists printed with the WO, you can specify with yes or no whether each step has been completed.
Buyer Commodity Purchasing
Use the Buyer Commodity Purchasing option to require a buyer to be assigned to a commodity code. The buyer is assigned to the inventory part based on the commodity code entered. The buyer then defaults onto requisition lines based on the stock part entered.
Route Stores Requisition Lists for Approval
Stores Requisition Approval Groups have been added, allowing stores requisition lists to be routed for approval to a group rather than a single user. The first approver in the group who selects Approve authorizes the stores requisition list.
Over Budget Requisition Routing Authorization
The Use Over Budget option allows you to control requisition approvals by lowering spend authorization when the budget has been reached for either the month or year. A requisition budget can be entered manually when integrated with QAD Enterprise Edition. Standard Edition users can automatically download the budget and refresh the budget as needed. You can view the budget analysis for requisitions to assess expense vs. budget for either the month or the year.
Additionally, reporting is provided for Budget Amounts and Budget Activity by Account or Cost Center.
Purchase Order Printing Enhancements
When selecting Print Document or Global Print Document for purchase orders, you now can print the documents and links attached to the purchase orders.
Email PO to Supplier
You can now e-mail purchase orders to the supplier from the Purchase Order browse.
The error handling of the Email PO Action in the Purchase Order browse is improved. Now instead of a generic message, you see a detailed message that points out the problem EAM had sending out the e-mail, if there are any issues.
The Email PO functionality required a change to EAM e-mail. EAM now sends e-mails from the EAM client (Email PO) as well as from the EAM server (all other e-mails). When EAM sent e-mails only from the server, you could specify “localhost” as the SMTP Server value in the System Control|Maintenance screen. However, the client does not recognize “localhost,” which means you now must specify the actual DNS Name or the IP Address of the SMTP server in order for e-mail to work on the client side. This is needed only if you use the Email PO functionality, and the change does not affect other types of e-mails.
New Financial API
QXtend is no longer used to post transactions between EAM and EE. EAM now uses the Journal Entry API (JE API) to:
• Post an inventory adjustment transaction in EE.
• Relocate and receive from relocate transactions in EE.
• Change a physical inventory status to closed.
• Modify cost transactions in EE.
• Post stores requisitions.
• Post purchase order receipt and purchase order return transactions.
• Post inventory issue and return to inventory transactions.
• Post work order receipt and work order return transactions.
• Transfer ownership transactions.
• Post labor transactions.
• Post labor GL transactions in EE.
• Post manual GL transactions in EE.
• Stop any transactions previously listed when an error is returned from EE.
Budget Analysis Reports
Four new reports are available for budget analysis:
• Budget Activity by Cost Center
• Budget Activity by Account
• Budget by Cost Center
• Budget Amounts by Account
E-mail Address Required for All Users
A unique e-mail address is now required for each user.