QAD Enterprise Asset Management 12.7

Field Name	Setting
Host Name	DNS name or IP address of the EAM DB server
Login ID	Login ID used to log into the EAM DB server (for example mfg)
Host OS	UNIX or Windows NOTE: Reserved for future use, select UNIX (Windows is not supported)
Password	Password used to log into the DB server. NOTE: The password is encrypted before it is stored in the database.
Port No	DB Server's SSH port (usually 22)
Domain	Reserved for future use
Script Timeout	Reserved for future use; leave this at 240
Idle Timeout	Reserved for future use; leave this at 240
Script 1 Pattern	This is the pattern EAM is looking for before it runs Script 1 Value. Usually this the OS’s command line prompt. Example: $
Script 1 Value	The command line value to enter once EAM sees the DB server write Script 1 Pattern. This should be used to run mpro and pass it the .pf file used by the EAM appserver. Note: Place a period followed by a space (. ) at the beginning of this line so that the Progress Editor window will close after the Progress session ends. Without this, users will be left at the server’s command prompt… Example: . mpro -pf /qadapps/eam/pf/eamtest.pf
Script 2 Pattern	(Optional) This is the next pattern EAM is looking for. It will run Script Value 2 when it sees it. This can be used to skip through Progress messages related to codepage, if they occur. Example: Press space bar to continue.
Script 2 Value	The keyboard strokes / text that EAM will automatically write to the telnet session when Script 2 Pattern is detected. An example would be a space (" " without the double quotes).
Script 3 Pattern	(Optional) If more keyboard automation is required, EAM will look for this pattern.
Script 3 Value	(Optional) If more keyboard automation is required, EAM will automatically enter these keystrokes when Script 3 Pattern is detected.
Script 4 Pattern	(Optional) If more keyboard automation is required, EAM will look for this pattern.
Script 4 Value	(Optional) If more keyboard automation is required, EAM will automatically enter these keystrokes when Script 4 Pattern is detected.
Min Connections	Reserved for future use
Max Connections	Reserved for future use

Fixes and Enhancements for EAM 12.7
Component	QAD Issue	Description
Analysis	EAMNET-25 96	Consignment Inventory: Transformation of the Consignment Transactions by Vendor Report.
	EAMNET-3356	Added report System Administration/Role Users to print the role and the users attached to the Role.
	EAMNET-5643	Consignment Transaction by Vendor now only displays consignment inventory parts.
	EAMNET-7065	When a new Quote is added for a part the PO Text on that part prints on the Quote Document.
	EAMNET-7257	Introduced Downtime Summary report. Filtering is available based on Equipment data.
	EAMNET-8673	Purchase Order Print: when selected from the PO browse, the Document Print action, prints the PO with all labels translated to the Vendor's language. Note the main menu's Analysis\|Purchasing\|Purchase Order Print only prints in the user's default language.
	EAMNET-9582	The dollar total on the Consignment Transactions by Vendor report is now correct.
Browse	EAMNET-2815	In the Requisition browse, if the user right-clicks on the column header and chooses Sort Columns, and clicks OK, the Requisition browse does not blank out. Previously, that same scenario caused the browse to display a big red X.
	EAMNET-7889	If a new browse is created and a sort is applied to one of the columns, then on saving the browse no columns are deleted. Previously some of the columns were deleted.
	EAMNET-9311 EAMNETS-627	Export to CSV in option ALL PO LINES works correctly when Windows language is set as Polish (non US language).
Browse, Maintenance	EAMNET-9035	We have limited the Downtime Hours Down field display to 2 decimals in the Downtime Browse and the All Downtime Browse.
Client UI	EAMNET-9824 EAMNETS-692	Update NumericBox.cs and NumericLookup.cs so that on entry (whether tab or click) the entire text value is highlighted.
Data Entry	EAMNET-9172	On Store requisition line, there is an option available to select/enter the location from where inventory can be issued.
Finance	EAMNET-10007	Project could not be deleted if the field "Estimation to complete" was entered on the project. The value was just displayed on the UI but not saved. The solution is based on the fact that the value of this field is also stored in database.
	EAMNET-6937	Incorrect rounding error GL transaction was created when Costing methods set to FIFO and Non Stock Item received. Now rounding error entry is created correctly in the above scenario.
	EAMNET-7648	During status change, the validation was changed to ignore WOs of the same state; that is, the to and from state.
	EAMNET-7910 EAMNETS-529	Requisition menu now takes less time to save the newly added requisition line to existing requisition when requisition has more than 700 jobs attached to it.
	EAMNET-7912 EAMNETS-524	In Project Jobs, we now only allow the creation of a Fixed Asset to be sent to the ERP if the Job is a Capital type Job. Creating Assets from the Project itself already behaved this way.
	EAMNET-8078 EAMNETS-558	The following changes have been made: • When deleting jobs that have not had any transactions against them, return the following message to the user: "Are you sure you want to delete Job "x". • If transactions have occurred against the job, do not allow the delete and provide the following message: "Cost has been posted against Job X, delete not allowed”.
	EAMNET-8080 EAMNETS-553	You can now correctly enter a date in the Find field
	EAMNET-8165	Modify Job Capital Asset returns “Error: fab_det does not exist” when the fixed asset being modified as depreciation posted (fa_mstr.fa_post = “yes”).
	EAMNET-8325	In the Project menu, the Refresh action now correctly calculates AP Variance and APInvoice amounts or multi-line PO having multiple Projects. Previously in the above scenario, AP Variance and AP Invoice amounts were incorrectly calculated for Projects.
	EAMNET-8339	Corrected an issue that was causing the Tax Accrual GL Transactions to be created with a blank reference number, or a reference that just had the letters "MI" instead of the correct reference number, which is "MI" plus the Date Stamp.
	EAMNET-8518 EAMNETS-592	Inventory Adjust and Relocate now creates Inventory Transactions with correct comment. Previously in the above scenario, comment field in Inventory Transactions was null.
	EAMNET-8534	Added a field Amt to Receive on the Material and Contract detail tabs for Project/Job Cost Analysis to show the remaining amount to receive. The Amt to Receive is calculated as: (PO quantity ordered - quantity Received - quantity Canceled) * PO Order Cost
	EAMNET-8864 EAMNETS-529	Requisition menu now takes less time to save the newly added requisition line to existing requisition when requisition has more than 700 jobs attached to it.
	EAMNET-8912	In the Project menu, the Refresh action now correctly calculates AP Variance and APInvoice amounts or multi-line PO having multiple Projects. Previously in the above scenario, AP Variance and AP Invoice amounts were incorrectly calculated for Projects.
	EAMNET-9048 EAMNETS-394	Corrected errors in the Return to Vendor functionality, when a return was performed for a part that had an Order UOM that was different from the Issue (or Inventory) UOM. The errors corrected were: • Rounding transactions were incorrectly created, with amounts that were too high. • Location quantity on hand was updated incorrectly. • LIFO/FIFO quantities were incorrectly assigned at times. • LIFO/FIFO cost was also sometimes incorrectly assigned. • The Planned and Ordered quantities for the part were being incorrectly assigned. • The returned and open quantities on the Purchase Order Lines were being incorrectly assigned.
	EAMNET-9053 EAMNETS- 581	Issue inventory across sites now post GL transactions to both sites and ERP. Previously, GL transactions were not posted in ERP and sites.
	EAMNET-9065	When a project is referenced by any other business entity, then project cannot be deleted. Error message preventing deletion is displayed.
	EAMNET-9285	Receive error message and project cannot be deleted if it contains a Spending Limit.
	EAMNET-9491	The system displays the Project warning limit when posting labor. If the project notify field is not blank, the user sees the project warning limit message and an e-mail message is sent to the Project notify person. Previously, when the PO was ordered, the Project warning limit message was given. The system was not designed to give the message when adding the requisition line.
	EAMNET-9510	Nexteer JD: EAM Req Routing by COA Combination
	EAMNET-9530 EAMNETS-655	Deleting a project now deletes the expense accounts associated with it. Previously, the expense accounts were not deleted.
	EAMNET-9535 EAMNETS-654	Requisition Line displays a warning message to the user when the Total Spent of the Project/Job will exceed the Warning Limit. Also, an e-mail is sent to the person defined in Notify under Project. Previously, no message was displayed.
	EAMNET-9560 EAMNETS-673	When the authorized amount is changed on either the project or the job, the same calculation logic is used for both. We should only add the difference of the new amount to the total calculation for the validation, not the entire amount of the old and new amount combined. Now, when the Purchase order\|Order Added or Modified Lines action is clicked, the correct message is displayed in terms of project/job validation.
Finance, Integration	EAMNET-7518	The Invoice Amount on the Projects\|Invoices sub-menu now displays the correct invoice amount when discount is entered on the sales order trailer. Previously, it displayed sales order line amount without including the discount.
Finance, Inventory	EAMNET-7094	Stocked Item quantity adjusted to 1 at the rate $10 and received quantity 1 at price $10.01 then issued both the quantity 1 by one and make on hand quantity to zero. In this scenario there should not be balance for inventory account in Posted GL transaction considering costing method is Weighted Average on Domain.
General	EAMNET-5898	Because there was no dependent code, removed the following fields from Domain: Require CC, Require Acct, and Require Sub-Acct.
	EAMNET-9049 EAMNETS-629	In the Physical Inventory menu, if a user presses the tab key on the last editable field, the cursor moves to the first editable field in the next line if that line is not closed and can be edited.
	EAMNET-9320 EAMNETS-624	When integrated with QAD EE, EAM now includes validations that consider the GL Account Analysis tab settings. These validations are used with existing COA Mask GL validations for accounts, sub-accounts, cost centers, and projects used in EAM. See the QAD EE Financials User Guide for details on GL Account Analysis setup.
	EAMNET-9511	Added the BEField and Field Name to Revisions table.
	EAMNET-9742	The following fields from Site menu are absolute: • Inventory Tab. Sales Order Cost Center/Account/Sub • More Inventory Tab. Variance/Std cost Dept/Account/Sub/cost center • Maintenance Tab. Calc % Budget Unauth/Auth/committed Disabled all the fields from the Operations frame on the MFG Options tab. Also removed the dependent functional code.
General, Inventory	EAMNET-9107 EAMNETS-284	In Domain, on the Inventory tab, the Inv Cost method field now has three values (FIFO, LIFO, and Weighted Avg). Previously, there was one more value available (Standard).
Integration, Maintenance	EAMNET-7201	Once changes have been made to the work orders in MS Project, such as resources (assigned) and due dates, you can Import the WO back into EAM reflecting the changes made in MS Project, by selecting the Import Action from the WO Browse in EAM. The import file can have the same name as the exported file or can be renamed when created. When importing: • You are able to enter a Notify user/group for the WO. The Notify user/group receives an e-mail when no changes are applied in EAM because the work order is Closed, Canceled, or restricted by the Owner field or if the data being imported is invalid compared to current EAM defined values. • The history for the work order changes and the revision history are updated if revision control is turned on. • Open Service Requests are updated if Assigned and Start Date changed for the WO referenced on the SR. • Similarly, open Stores Requisitions Lists that reference a WO No. where the Start Date changed, copies the new Start Date to the Required Date.
	EAMNET-7223	EAM provides the ability to schedule work orders using MS Project 2007. When selecting the Export Action from the WO Browse, you can specify a filtered set of work orders. Then the system creates a file for specific WO fields and their values from the set of Work Orders specified. These are used for scheduling in MS Project. • You are able to name and save the export file created for EAM Work Orders into MS Project. • You can create and save multiple files for different groups of WO, by sites for example, as needed. • When you open MS Project you can select the file created and it will be loaded ready to schedule. You will then be able to make changes to specific data for the EAM work order, such as Resources (assigned) and Due Dates. • You can Import the WO back into EAM reflecting the changes made in MS Project.
Integration, Purchasing	EAMNET-8680	This job program uses the SCP/bid XML file to update RF quote and RF quote line records in EAM. In EAM application side, make sure you have the following registry setup: • SCP/bid file directory, • SCP/bid file naming (rfq_bidding), and • SCP/bid file archive. On the EAM server side, the SCP/bid file directory and archive directory should have full access permission for importing to EAM application.
Integration, Purchasing	EAMNET-9101 EAMNETS- 632	While creating requisitions, the Receiver Matching in EE now saves successfully even if spaces are entered after the Vendor number. Previously, the following error was given: "Value is too long".
Inventory	EAMNET-4870	A Consignment flag has been added to Inventory transaction history.
	EAMNET-5679	The stock replenishment site field is no longer editable. Previously, the user was able to change the site. If the user entered an invalid site and saved the record, the stock replenishment record was created in the database.
	EAMNET-5764	When the Relocate Action is selected for a Consignment part, a new dialog screen appears when parts are relocated between different sites. In addition to the Site relocation data required, you can select from Company Owned parts or Vendor Owned parts as available from the Consignment stack for the Qty to Relocate.
	EAMNET-5765	Relocating consignment parts updates the consignment stack for qty of the relocated parts.
	EAMNET-5768	Inventory and GL transactions created for consigned parts relocation now reflect the associated consignment vendor and consignment accounting.
	EAMNET-5971	When consigned parts are used in Stores Requisition Lists, the Issue action now provides the ability to select vendor owned, vendor and display OH balances for company or vendor as information from the part's consignment stack.
	EAMNET-5972	Inventory issue transactions for vendor owned consigned parts in Stores Requisition Lists now record Vendor Owned, Vendor No, and Vendor Name.
	EAMNET-5973	When a consigned part is Issued and the OH qty for the Part is less than the Planned Qty, you can select to proceed with the Issue and expect to see the OH qty for the Vendor/company updated for the Stores Requisition list line.
	EAMNET-6013	When a consigned part is Vendor Owned, the Issue, Return to Inventory, and Transfer of Ownership actions create an Issue transaction that is sent up to ERP.
	EAMNET-8214	Consignment Transaction History Report reports transactions when filtering by vendor.
	EAMNET-8372 EAMNETS-521	From 12.5.2.2 through 12.6.0 there was an issue in the EAM Net client that could cause long running server processes to stop unexpectedly. These processes include (but aren't limited to) any activity that attempts to operate against data in a site that has more than a few thousand records. For example, Stock Replenishment Global Add in a site that has 10K records could fail at random and would, on occasion, work properly. NOTE: This issue was actually addressed by EAMNET-8628.
	EAMNET-8401 EAMNETS-567	The program has been fixed that populates the required date on Stores Requisition Lines whenever they are created.
	EAMNET-8402 EAMNETS-533	For Stores Requisition lines, the label "Item No" was changed to "Line No" to better represent the meaning of this column.
	EAMNET-8862 EAMNETS-600	In Physical Inventory, the Global Add action now filters by date and fetches correct data. Previously, filter by date did not fetch any data.
	EAMNET-8876	Fixed the problem where LIFO/FIFO costing was causing the Simulate Update Report to not balance with Stock Update.
	EAMNET-8879 EAMNETS- 615	After relocation of the stock from one location to another location with FIFO: • Relocation Inside One Site. As this is not treated from functional perspective as new issue/receipt, system should take correct stack layers and move them to the new location. Receipt date of the goods is not changed. • Relocation Between Two Sites. This is treated from functional perspective as new issue/receipt. System should create a new layers in the FIFO stack with the new receipt date. The receipt date will be today if not In transit functionality is activated, otherwise the real date of receipt in destination site/stock.
	EAMNET-8882 EAMNETS-621	When closing the physical inventory, the following error message is received: GL already in ERP. In certain circumstances this error message could prevent GLs from moving into EE.
	EAMNET-9322 EAMNETS-609	Inventory Issue can now be done by a Requestor defined for a site different than the working site. Previously, the Requestor was limited to the working site only and the following error was given: "Requestor is not a valid employee for site XXXXX".
	EAMNET-9357	Inventory Codes tab does not contain 'Warrantied?' flag. Previously the flag was available.
	EAMNET-9778	For Inventory Adjustment transactions for Consigned Parts that are Vendor Owned, the setting of the Vendor's Send Cons ERP? option determines the GL transaction type. • When Vendor Send Cons ERP? setting is selected, the GL transaction type = MI and the GL can be sent to ERP • When Vendor Send Cons ERP? setting is not selected, the GL transaction type = MR and the GL is cannot be sent to ERP
Inventory, Purchasing	EAMNET-5969	When a requisition is created through stock replenishment, and the Consignment? setting is selected on the new requisition, the Taxable? setting, by default, is not selected and the Tax Code defaults to blank.
	EAMNET-5974	For requisitions created from Stores Requisition Lists for consigned parts for both header and line: • Consignment? setting is selected, • Taxable? setting is not selected, and • the Tax details are not defaulted. Previously, the Consignment? setting was not selected and the Taxable? setting was selected.
	EAMNET-6012	GL Transactions created for Consignment Receipts, Relocations and Modify Consignment Cost transactions have a transaction type of "MR" in EAM and are only created in EAM and not sent to ERP.
Maintenance	EAMNET-5710 EAMNETS-238	The format of the Time column in the Labor History browse changed from -HH:MM to -MM. This was required because a labor history reversal will be recorded as negative and most spreadsheet applications cannot handle a -HH:MM format.
	EAMNET-7352 EAMNETS-492	This ticket relates to sorting of time fields (start time and received) in the Work Order Browse. These fields store the time in the 12 hour clock which includes the text 'am' or 'pm'. Because of this, it is not possible to correctly sort these columns. These fields have been converted to display in the 24 hour clock instead of the 12 hour clock. This allows for correct sorting and be more consistent with other QAD products. In addition, the ability to enter equipment downtime in the 12 hour clock has been removed from the registry and the related fields. Start time and End time are now displayed and entered using the 24 hour clock. The AM/PM Clock entry has been removed from the registry as it is no longer supported. In order to update the client's database, a conversion program is included which converts the data’s four fields to the 24 hour clock. These fields are: • work_order.received_time • work_order.start_time • equip_down.endtime • equip_down.stime. In addition, the conversion program removes the registry entry for the AM/PM Clock option.
	EAMNET-7903 EAMNETS-534	Fixed the problem, when after creating a PO from a requisition with 0 cost, the following error was given: "PO has not yet been authorized.".
	EAMNET-8079 EAMNETS-557	The Projects Refresh action now correctly calculates Planned Internal cost when a Requisition is created with Contractor flag selected. Previously, in the above scenario, Planned Internal cost was calculated incorrectly.
	EAMNET-8081 EAMNETS-552	When users enter instruction lists on work orders manually, the project's Planned Labor cost updates correctly.
	EAMNET-8083 EAMNETS-549	Site code in Copy Project should not be case sensitive.
	EAMNET-8084 EAMNETS-544	When copying project and jobs from one site to another site, newly copied job’s Expense Site has incorrect site code. It still shows the source site.
	EAMNET-8167 EAMNETS-65	In the manual GL /Unposted GL screen, if a user adds GL lines to the GL header and the GL line has an associated Project no or Job no and if the GL line amount is over the Project or Job spending limit, the user will get an error message when "Post" action is clicked. The error message will stop "Post" GL action.
	EAMNET-8211	Tolerance screen should not close until a correct user ID is entered in the notify field when okay is pressed. Previously in this scenario, the screen closed with the "Invalid Notify". message and all the other field data was lost.
	EAMNET-8221 EAMNETS-568	Account and Sub-Account lookups on Equipment screen now showing all the accounts and related sub-accounts properly. Previously, it was showing only account/Sub-accounts for Project entered on Equipment.
	EAMNET-9500 EAMNETS-672	Fixed a problem to make sure that the labor time was properly formatted before allowing it to be saved.
	EAMNET-9502 EAMNETS-663	When labor is posted for a project and the rate is defined for a particular Employee, the labor post history shows the correct Reg Rate. Previously in the above scenario, it was showing zero.
	EAMNET-9504 EAMNETS-657	Added a getNextWorkingDate method to calculate the next working date for both the start and target date on a WO, that is created from a PM Template, if the 'Shift Work Day?' setting is selected.
	EAMNET-9825 EAMNETS-693	Updated the client (.NET, AcitonHandler.cs) code to make sure the intracompany logic is: • Not case sensitive when comparing source and expense sites, • If intracompany validation fails, the error message is displayed to the user, and • If intracompany validation passes, the receiving logic actually fires. Reviewed the Stores Requisition logic that automatically creates fabricated work orders to ensure it reliably (100% of the time) populates expense site.
Other	EAMNET-8104 EAMNETS-27	Two level and three level Browses now correctly display results for values entered in the find field. Previously, lower level browse results were incorrectly displayed.
	EAMNET-8591 EAMNETS-602	If fixed asset detail is pre-populated, the capitalize asset returns an error.
	EAMNET-8595 EAMNETS-605	When editing an asset that has already been posted in the ERP, the system will not submit the changes to EE (FA API is EE only). Instead, it will only apply the changes to EAM’s internal records of the asset, in the Fixed Asset subdetail of the Job or Project, and it will give the user the following courtesy message: "Depreciation has already been posted in MFGPRO for this asset. These changes were recorded in EAM but not submitted to the ERP." All asset modifications need to be done directly in EE if the asset is posted already, and the user then will record these changes in EAM to update the Project or Job's Uncapitalized Amount.
Purchasing	EAMNET-2718	New Registry setting, VerifyCurrencyExchExists, determines if multicurrency transactions are allowed if a current exchange rate does not exist.
	EAMNET-5701	In the All browse, when a user presses the Enter on last editable field, the system saves the record and the cursor remains on the same line. If a user presses the Tab key on the last editable field, the system saves the record and the cursor moves to the next line.
	EAMNET-5892	When you do not select the Consignment? setting on a PO or Requisition, the appropriate Tax defaults based on Ship To, Vendor, etc should be updated. When you select the Consignment? setting, the existing values for tax settings are disabled and the Tax setting is not selected.
	EAMNET-5893	For a consigned PO the Actual Freight will always be zero and disabled.
	EAMNET-5894	If consignment flag is selected on header level, the user is not allowed to update the fields related to taxes and all the fields related to taxes are blanked out on the requisition line.
	EAMNET-5967	When EAM is integrated with QAD Purchasing, Consignment Receipts are not uploaded to QAD Purchasing. Only an EAM Receipt No is assigned for Consigned PO Receipts regardless of the EAM Domain setting for Receiver? = MFGPRO. This is an exception only for consigned part receipts.
	EAMNET-7516	A PO cannot be received using the Receive action, if it already exists in PO Pay Schedule. Similarly, if a PO is received using the Receive action then it cannot be added in PO Pay Schedule.
	EAMNET-7908 EAMNETS-536	A PO cannot be placed on order when the equipment on the line is locked. Previous to this fix, EAM allowed this action.
	EAMNET-7926	We have corrected a couple of issues that were happening when doing receipts in a different UOM from the part: • The PO Line or the PO Header were not being closed when receipts were done in full. • If a PO Line was not auto-issue, but was in a different UOM, an extra/unnecessary rounding transaction was being created, as if it would apply to an auto-issue. We are now assigning the PO Number to the Rounding Error transaction's corresponding field. Previously, it was only being mentioned in the PO Description, but that would make it hard to reconcile all GL Transactions that were created for a PO.
	EAMNET-8064	Now on Return to vendor screen, if the user enters a return code, which is not available in database, the system displays the error message, "Invalid Return" on the UI screen.
	EAMNET-8068	EAM Purchase Orders Return to Vendor (Action) on Blanket Release is changing PO line status to P instead of O. This issue has been resolved by assigning the ‘Date Ordered’ as Today on the PO line when the status of the requisition header is ‘O’ (Ordered).
	EAMNET-8087 EAMNETS-540	When Requisition Currency is changed due to Vendor change, the requisition menu now correctly calculates and sends Order Cost, Total Cost and Total Cost to ERP in Vendor Currency. Previously in the above scenario, Order Cost, Total Cost and Total Cost in Vendor Currency were calculated incorrectly.
	EAMNET-8170 EAMNETS-195	Return to Vendor functionality was corrected, so that it does not reset an existing canceled quantity when returning a requisition line that has been closed.
	EAMNET-8207	Removed "Euro" and "Use Euro" from Currency menu. Also removed dependent codes to those fields.
	EAMNET-8222 EAMNETS-566	In the Blanket Orders menu, for non-stock parts that overlap the effective date and expiration date of another blanket order with non-stock parts, the Copy Blanket Orders action no longer displays the error "Line X Part X is in the same period as blanket order X line X". Previously, in the above scenario, the error was displayed.
	EAMNET-8224 EAMNETS-570	Vendor Return document now correctly prints records for stack of inventory returned. Previously Vendor Return document was incorrectly printed.
	EAMNET-8405 EAMNETS-583	When a requisition has a line item which is canceled, attaching an existing PO to this requisition. From this Purchasing Order line items browse, the user can see a PO Line No 0. Now this issue has been corrected. Even with a line canceled, the PO line items browse displays PO Line No with the correct PO line no.
	EAMNET-8516 EAMNETS-595	In the BO layout, fixed an issue with list price.
	EAMNET-8590	When entering a Requisition Line for non-stock parts it is mandatory to enter a part number. To enforce this, the Requisition Line entry screen has been updated, so that the user first has to enter the Part No before updating all the other fields. Once the Part Number has been entered, the other fields in the screen will be enabled for data entry.
	EAMNET-8625 EAMNETS-606	User was not able to change the description on the Requisition line when attached Project is locked. Now, after this fix user is able to change the Requisition Line description and able to send it to ERP when PO is Ordered.
	EAMNET-8878	At Purchasing/Requisitions, when attempting to Edit a Requisition Line with Auth Status of Authorized, EAM should allow the user to edit: • If "Any Buyer" at General\|Business Units\|Domain is enabled and the user is flagged as a Buyer at General\|Employees for the Site where you are attempting to Edit the Requisition Line. • If "Any Buyer" is not enabled but the current user is the buyer designated in the Requisition Header. • If the current user is designated as the Auth By in the Requisition Header EAM prevents anyone from modifying a Requisition Line if it is closed or cancelled. In other words, existing pi_status = "C" and pi_status = "X" checks remain in place.
	EAMNET-8900 EAMNETS-622	This issue was fixed on EAMNET-8878.
	EAMNET-8902 EAMNETS-606	Modified the “just where” clause to avoid a whole-index error. No functional impact.
	EAMNET-9051 EAMNETS-561	If there is a special character line or more than 76 characters in PO Clause, the system no longer goes into an infinite loop during Po Order. Previously, this caused the system to go in an infinite loop.
	EAMNET-9078	EAM 12.5 & 12.6: 12.5 & 12.6 release of EAM utilized a registry value being set to determine whether to allow requisition authorizations over the project spending limit. This enhancement was added to ensure the functionality in previous releases where schema changes are not possible. With future releases a schema change would be an improved solution. If an upgrade was taking place, a conversion script would be required, to get the value from the registry to the Site maintenance. EAM 12.7: As this is the current release, 12.7 release of EAM introduced a schema change which added a new field to the Sites maintenance screen. The new field replaces the need to use registry entries as was the case with previous versions. The new field can be found on the Sites maintenance screen under the “Authorization Options” tab. A conversion script has been created, which will take the value of the setting from the registry, and assign the value to the Site definition. This conversion routine has to be applied when the EAM system is updated from version 12.5 or 12.6 to the more recent one.
	EAMNET-9102	After receiving all the ordered quantity for a Consignment part, the status of the PO, Requisition, and Requisition Line remains O for Ordered. The Receipts sub detail confirms what we see in the PO and Requisition browse. The expected result is the status should be C and behave the same as any standard part receipt when all open quantity is fully received.
	EAMNET-9110 EAMNETS-354	You should be able to save a requisition line for an unauthorized project. • Requisition can be created and saved when Project Auth is selected and the Project is not authorized. • Requisition cannot be Routed for Authorization when Req Auth and Project Auth are selected and the Project is not authorized. Once the Project is Authorized the Req can be routed for authorization. • Requisition cannot be put On Order when Req Auth is not selected and Project Auth is selected and the Project is not authorized.
	EAMNET-9112 EAMNETS-613	Now, on Requisition Header, the system updates the date due when a user changes the date due on PO header and selects yes on " change due date on PO line(s)?" prompt.
	EAMNET-9267	As a buyer, when releasing a blanket order, I want to be able to enter new accounting information.
	EAMNET-9268	As a Buyer, I need to include Standard Clauses on the Blanket Order print.
	EAMNET-9269	JD fixed an issue regarding EAM Return To Vendor (RTV) for Nexteer JD v12.5.1.3.
	EAMNET-9270	Buyer Limit Logic should be added to Blanket Orders.
	EAMNET-9271	JD fixed an issue regarding: Nexteer - GSM-2135 "All PO Revisions" Browse.
	EAMNET-9272	Need 3 Blanket Header fields.
	EAMNET-9321 EAMNETS-619	If the same Supplier code is used in multiple domains and if one of the domain supplier codes is inactive and a user enters an inactive supplier code in BO (in domain where supplier code is inactive), the system gives the error "inactive supplier code".
	EAMNET-9497 EAMNETS-660	When Return To Vendor action is performed on Purchase Orders, the error message “GL already in ERP” was received. In certain circumstances this error message could prevent GLs from moving into EE.
	EAMNET-9503 EAMNETS-661	If another user has deleted a Req line and if you try and save that Req line, the following error message is given: "Requisition line X has been deleted by another user. Please discard your changes." Previously, a non-explanatory error message was displayed.
	EAMNET-9505 EAMNETS-647	When a requisition line is copied, the PO text is also copied to the new requisition line.
	EAMNET-9509	As a Buyer, I want to be notified if a line item changes on an authorized BO.
	EAMNET-9525 EAMNETS-638	Blanket Orders should not allow any user/buyer to change the status when it is in routing. Previously, the system allowed you to change the status.
	EAMNET-9740	PO Text has been added to the Quote Lines. The PO Text can default from the part record or Requisition line if the Quote line is created from a Requisition. You can also update it directly in the Quote line. The PO Text will also be visible for the Quote line in SCP if have the integration implemented All of the Vendor Part numbers recorded in EAM inventory will be sent to SCP for the vendor to review and change when they update bid.
	EAMNET-9814	When changing information that has nothing to do with consignments, fixed the problem so that you do not get a consignment error.
Reporting / Filtering	EAMNET-5970	Consignment Transactions by Vendor report should be filtered to only vendor owned transactions.
System Administration	EAMNET-2897	Now, the User Defined Mail menu does not allow you to edit the Mail Be field name in the lower browse and the Business Entity Name. Now, Project does not contain obsolete fields. Previously, you could edit the Mail Be field name and project had obsolete fields.
	EAMNET-3192	In Inventory, if the Job No is made mandatory and the project no is not entered, Issue, Work Orders, Post Labor, and saving PM Templates executes without any error. Previously, it displayed an error "Job No is a required field".
	EAMNET-5633	The options in Roles are now displayed only once. Previously, some of the options in Roles were displayed multiple times.
	EAMNET-5958	Now, the Registry setting does not have: “Custom/UnauthPOUponAnyChange” flag as it is replaced by selective Req Reroute/Notify Fields and PO Reroute/Notify Fields. Previously “Custom/UnauthPOUponAnyChange” setting was available in Registry.
	EAMNET-7259 EAMNETS-481	Once the Project in EAM is closed, the completion date should not be changed. When downloading projects from ERP, the project completion date in EAM cannot be overwritten.
	EAMNET-8216	The CIM Load Job Program #23 can now be copied and used to upload Driving Unit of Measure (DUOM) Monitor readings from a text file. The format of the text file is: Equip No DUOM Reading Date Time User ID. Time must appear as a numeric as the number of seconds since midnight. The location of the text file is added to the Run Parameters of the Job Program. An error log with any invalid data noted in the text file is also found at this location. Once the job runs, the Monitor readings can be viewed in the Equipment Readings submenu. These readings can produce an Out Of Tolerance (OOT) condition. If an OOT condition results, a CM work order and an e‑mail can be generated automatically. The e-mail is sent to the Notify person or group noted in the Update Tolerances screen or on the Equipment Readings screen. A CM work order is added if the option is selected in the Update Tolerances screen.
	EAMNET-8660 EAMNETS- 597	The Role permissions have been changed so that the user now will have access to a combined number of programs, based on his/her access being granted in all sites, instead of only the site that he/she is logged in to. However, the drop down Site field at the top of the screen, will only show the sites that the user has access to.
	EAMNET-9512 EAMNETS-676	Corrected job program autostck.p to process multiple sites.
	EAMNET-9552	The Progress Editor can now be used inside of the EAM .NET UI. This is very similar to the "mgeditor.p" program in QAD SE and EE, with some distinct differences: • Telnet is not supported. Only SSH/SSH2 is supported. • Windows-based servers are not supported, only Unix/Linux. In other words, if your AppServers and DBs are on a Windows server, you will not be able to use this feature. • Key mapping, font settings and colors cannot be modified by users or system admins.
	EAMNET-9865 EAMNETS-694	Work Order Document reinstated as substitutable.
	EAMNET-9868 EAMNETS-656	Refactored Vendor Refresh code to help eliminate possible locking issues.
	EAMNET-9888	A new Action called "Telnet Options" was added to the System Control browse. This action is used to maintain the system information needed to support the Progress Editor added in EAMNET-9552 'Enable Progress Editor in the EAM Plugin'. These options control everything from which server is accessed to what ID and password are used to log in and even what keyboard strokes are automated so that the EAM can automatically open the CHUI Progress Editor from the server's command line. See Enable Progress Editor in the EAM Plugin.