Infor EAM 11.0 201604 Jira Report€¦ · Installation Instructions for Infor EAM Database...
Transcript of Infor EAM 11.0 201604 Jira Report€¦ · Installation Instructions for Infor EAM Database...
Infor EAM 11.0 201604 Jira Report
Jira Report
Date 11-May-2016
Fix For Version 11.0 Patch
Build 201604
Infor EAM 11.0 201604 Jira Report
Jira Summary
Jira # Title
EAM-15684 Departments - Unable to Edit Department Description
EAM-17857 Lots - Lot Expiration date is missing when Lot is added to PO.
EAM-18102 Monitor Interface - Error field on List View tab is checked but Error field is blank on
Error Correction tab. EAM-18599 Generate WO's - issue when clicking several times on Generate button with
Maintenance Patterns EAM-18603 Requisitions | Parts - when base price retrieved no currency conversion done in specific
situations EAM-18696 Web Services Prompt - MP0220_AddIssueReturnTransaction_002 not showing foreign
language messages EAM-18809 CLONE - InforION: ManufacturerPartyMaster Variation ID Implementation
EAM-19031 Supplier Returns | Parts - Default Value for Reason for Return is wiped out on bringing
back Part EAM-19381 Web Service Prompt - When creating prompt for Work Order Children tab the wrong
web service is used. EAM-19405 Campaigns | Close WOs - When esignatures are turned on and you try to close WOs the
esignature popup never shows up and the user isn't able to close WOs EAM-19590 Base - Dataspy return no records
EAM-19598 CLONE - InforION: Variation ID implementation for CurrencyExchangeRateMaster
EAM-19633 Reports - long term wo list report shows wrong due dates
EAM-19758 Customer Invoice Detail (WZCIND) - rounding problem
EAM-19774 WO Daily Scheduling | Scheduling - cancelling a wo daily schedule will modify the
creation date EAM-19881 Messenger - email notification being sent even if record to trigger the email fails
EAM-20143 User Setup - Add 'Allow Global Dataspy Configuration' to List view, Dataspy and filter
options EAM-20250 Work Orders | Documents - Documents attached to PM/Equipment copied twice to
Work Order. EAM-20308 WO Quick Entry | Add/Edit Activity Comments - Error 'Unable to Retrieve Text'
displayed on saving w/o Activity instead of proper msg. EAM-20671 Requisitions | Parts | Assign Repair Details - using mouse with popup does not save
changes. EAM-20784 Purchasing Contracts | Parts - Error 'An error has occurred while processing your
request. Please contact your system administrator.' when trying to view audit trail on
Net Price field EAM-20897 CLONE - Upload Utility is not supporting TLSv1.2 also for version 11.0
EAM-20916 PM Schedules | Equipment - error 'This record cannot be deleted because it is associated
with another record in the system' when changing due date. EAM-20927 Generate WOs | Preview | Generate - Generate WOs get hung in loop if Perform every
and Perform on both populated on Daily/Weekly record. EAM-20937 Issue/Return Parts - The system does not honor default return bin defined for a part,
when returning parts through pick ticket EAM-20964 Work Orders - Activities are duplicated on MEC WO when WO has a Standard WO
EAM-20981 Installation of patch 201512 (SQL) - error in the log file
EAM-21025 CLONE - Work Orders - error when changing status
EAM-21071 CLONE - CLONE - Release Individual PM WOs - Grid is not displaying records when
the screen is cloned
Infor EAM 11.0 201604 Jira Report
EAM-21075 CLONE - PO Receipts | Active Lines - Cannot receive more items than have been
ordered when trying to receipt a partially Purchase Order EAM-21092 CLONE - Release Individual PM WOs - Error occurs when trying to access the lookup
on the Status field EAM-21114 CLONE - Assets | Meters - The Average Daily Usage as calculated after each meter
reading only shows zero (due to rounding) EAM-21122 CLONE - User groups | Screen Permissions - Security dataspy cannot be selected
EAM-21176 Screens - cannot clone the standard screens
EAM-21200 Databridge - ION - Sync.ItemMaster Manufacturer and Manufacturer Part Code Error:
The combination of Primary Manufacturer and Manufacturer Part Number is not valid.
at /PartStores[0]/MANUFACTURERPARTC EAM-21286 Web Service Prompts - MP2099_AddStoreToStoreReceipt_001 returns error when
creating new receipt EAM-21290 Databridge/ION SyncSupplierInvoice error out for extra line when action code is
Change EAM-21303 Work Orders | Monitored Data Results - Modifying records with aspect prompt fields
does not save changes EAM-21311 Generate WOs - Printing duplicate pm's not showing data
EAM-21313 CLONE - InforION: Variation ID implementation for ConstrainedResource
EAM-21316 CLONE - InforION: Variation ID implementation for CodeDefinition
EAM-21345 Base - WODDRV is inserting date value in wrong format when using french SQL
account EAM-21393 InforBOD: Inconsistent mapping with AssetTrackingData inbound/outbound
EAM-21397 Call Center | Knowledge Base Search - issue with same KBA id in different
organizations EAM-21416 InforION: AssetMeterReading outbound Variation ID Implementation
EAM-21419 InforION: PayableTransaction Variation ID Implementation
EAM-21422 InforION: Invoice Variation ID Implementation
EAM-21431 CLONE - InforION: ReceiveDelivery\Shipment\InventoryAdjustment outbound
Variation ID Implementation EAM-21434 Assets | Meters | View Meter History - Physical Meter of Child Asset not recording the
values properly EAM-21436 CLONE - InforION: EmployeeWorkTime outbound Variation ID Implementation
EAM-21448 CLONE - Customer invoices - not all items passed to interface due to default invoice A
status EAM-21463 InforBOD: ProcessMaintenanceOrder inbound ownid
EAM-21466 InforBOD: MaintenanceOrder inbound with vertical option
EAM-21475 Upload Utility - Missing tabs in UU 11.0 201508 and 201510
EAM-21654 CLONE - Base - Auditing reached max value for Identity column
EAM-21680 CLONE - InforION: ServiceConsumption Variation ID Implementation
EAM-21806 CLONE - InforION: SourceSystemJournalEntry outbound Variation ID implementation
EAM-21828 CLONE - InforION: AssetTrackingData outbound Variation ID implementation
EAM-21858 Materials | Parts - Change part number deletes parts associated records.
EAM-21863 CLONE - Databridge/ION Employee Availability Exception outbound creates two xml's
for one new record for sql server EAM-21877 Work orders | MEC work orders generated without an activity from Duplicate PM
schedule with a route EAM-21913 Requests for Quotations | Selection | Generate POs - Generate PO popup takes report out
of Screen PSRFQT instead of PSRFGP EAM-21923 Purchase orders - issues after canceling PO header and not the lines
EAM-21952 Base | Archive Records - Invoice Custom Field values are deleted but not archived
Infor EAM 11.0 201604 Jira Report
EAM-22014 Assets - security filter checked checkbox becomes unavailable and empty
EAM-22056 WO Quick Entry - Option CLGROUP is not applied for Problem Code LOV.
EAM-22071 Generate WOs - Print Work Orders (WZJOBF) - Duplicate work orders not print
EAM-22084 CLONE - Databrige/ION - Outbound Sync.Shipment not sending the UDF fields.
EAM-22187 Archive - Work Order Activities allowed to be reused on service lines after running the
archive process. EAM-22241 Suppliers | Parts - On List Detail, the List is out of synch with the Detail for the
Preferred checkbox EAM-22357 CLONE - Mobile full VGA: Sync error: "Error in executing query:Operand type clash:
datetime2 is incompatible with int", key - BCCOMOBJWO EAM-22411 Base - Update AppConfig.java for 11.0 201604 patch
EAM-22415 CLONE - Databridge : SyncMaintOrder - with Systems, Positions, Locations getting
error 'OBRTYPE is a required field' EAM-22446 PM Schedules - Meter Due populating incorrectly on minor nested PM when major
nested PM is completed EAM-22459 CLONE - Asset Inventory - Multiple issues
EAM-22463 Customer Invoices - The new generated invoice status should not be "Approved" if an
earlier invoice exists with a status of “Processing Error”(SQL only). EAM-22475 CLONE - Databridge/ION - Inboud ProcessAssetTrackingData BOD fails with error:
java.lang.instantiationException. EAM-22491 CLONE - InforEAMOutboundBODMapping.10.1.4.pdf,
InforEAMInboundBODMapping.10.1.4.pdf sequence number incorrect
Infor EAM 11.0 201604 Jira Report
Installation Instructions for Infor 11.0 201604 Patch In an effort to ensure that your Infor EAM environment continues to operate with maximum efficiency and minimal problems, Infor Global Solutions strongly recommends that you: Note: v11.0 201604 patch is a cumulative patch that includes all fixes provided in the 201512, 201602, and 201604 patches. The patch can only be applied to an Infor EAM environment that is currently at one of the following patch levels: v11.0 201510, v11.0 201512, or v11.0 201602. Back-up your current Infor EAM database before installing this patch. Let only a qualified Infor EAM Integrator/ Administrator install this patch. Apply this patch to a test environment and perform your own user acceptance testing before applying this patch to your production environment. For Infor EAM, on the Administration | Security | Install Parameters form, the Install Parameters: FORMDATE and FORMDATI must have 4-digit year format, i.e. DD-MON-RRRR. " To determine if the Infor EAM v11.0 201510, v11.0 201512, or v11.0 201602 is installed, login to Infor EAM, click on “About” and verify version is equal to one of the three listed versions.
Important Note: If you are using Databridge, please carefully review those JIRAs that come with DATABRIDGE
IMPACT NOTE and evaluate potential patch impact on your interface before installing this patch. Please search JIRA description for ‘DATABRIDGE IMPACT NOTE’ to identify those JIRAs. For instructions regarding how to configure ION server to support the customer survey events functionality, please refer to "ION Configuration Guide for EAM Customer Survey Events.pdf" in the patch install folder. The supporting files are also included in the patch install folder.
Installation Instructions for Infor EAM Database Installations: Installing on an Oracle Database: 1. Log all users out of the application. 2. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 3. Copy and unzip the contents of the DB110201604ORACU.zip file to a local directory that can be called directly from SQL Plus. 4. In SQL Plus, run patchora.sql. This sql script will determine the patch level and apply necessary patch scripts accordingly. Note that the database patch level will need to be at v11.0 201510, v11.0 201512, or v11.0 201602. 5. In SQL PLUS run EAMcomp.sql to validate any invalid objects. 6. Exit SQL Plus. 7. Restart the application server. Installing on an MS SQL Server Database: 1. Log all users out of the application. 2. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 3. Copy and unzip the contents of the DB110201604SQLCU.zip file to a local directory. 4. Edit the patchsql.bat to include 4 necessary database connection parameters (e.g. server, database, username, and password). Note that, it is advisable to use SA user or user with grants similar to SA for the parameter "username". Database patch level will need to be at v11.0 201510, v11.0 201512, or v11.0 201602. 5. Run patchsql.bat by double clicking it or execute it using DOS prompt. 6. Restart the application server.
Infor EAM 11.0 201604 Jira Report
Application Server Installations: Installation steps for Linux Jboss/Weblogic app server environments for Infor EAM: 1. Log all users out of the application. 2. Make sure you are logged in as the same user that installed Infor EAM. 3. Open a shell session and stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. NOTE: A bourne-derivative shell must be used in order to run the patch 4. Ensure that a proper backup of the Infor EAM installation is available, in the event of any problems that arise during the patch process. 5. Copy the patch file EAM110LN201604.sh to a temporary directory like /tmp 6. Navigate to the temporary directory then execute the shell script file like #./EAM110LN201604.sh, type yes, and press enter to unzip. (It will create and unzip files to a EAM110LN201604 folder) 7. Navigate to the EAM110LN201604 directory and set the variable APPSRV_HOME to the location where Infor EAM is installed. 8. Apply the patch by executing this command at the prompt, substituting a value for {logging_level}: ./patch.sh {logging_level} NOTE: The brackets on logging_level denotes that this value is optional The default value for {logging_level} is info. The available logging levels are as follows from least to greatest: error warn info verbose debug 9. Go to the depconfig directory and execute this command at the prompt: ./deploy.sh NOTE: For WebLogic Application Server, all application servers must be running before deploying Infor EAM 10. Once the process is complete, close the command prompt and start the Infor EAM Application daemons. NOTE: For WebLogic Application Server, all application servers must be restarted 11. Infor EAM Application and daemons should now be up. NOTE: During processing, the patch status will be echoed to the console. A patch log will also be created identified by having the current patch execution date and time as part of the filename in the patch directory. One common error is "java.io.IOException: Error in writing existing jar file" which is produced if the Infor EAM daemons were not stopped before patch installation (step 3). To correct, ensure that the Infor EAM daemons are stopped, and repeat the patch installation process. Depending on the specifications of the underlying hardware, the patch process may require up to an hour to perform all necessary updates. Please be patient to allow the patch process to fully complete before halting the patch script or exiting the current shell.
Installation steps for Windows Jboss app server environments for Infor EAM:
1. Log all users out of the application. 2. Make sure you are logged in as the same user that installed Infor EAM. 3. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 4. Ensure that a proper backup of the Infor EAM installation is available, in the event of any problems that arise during the patch process. 5. Copy the patch file EAM110WN201604.exe to a temporary folder like c:\temp 6. Double click on the self-extractor file to execute it
Infor EAM 11.0 201604 Jira Report
7. Press 'Unzip' to create and unzip files to an EAM110WN201604 folder 8. Open a command prompt (cmd.exe) and change the directory to EAM110WN201604 9. Apply the patch by executing ths command at the prompt, substituting values for destination_of_server_root and {logging_level}: patch.bat destination_of_server_root {logging_level} NOTE: The brackets on logging_level denotes that this value is optional destination_of_server_root is the root location of where Infor EAM is installed. (E.g. c:\InforEAM) The default value for {logging_level} is info. The available logging levels are as follows from least to greatest: error warn info verbose debug 10. The patch will automatically redeploy the application components. 11. Once the process is complete, close the command prompt and start the Infor EAM Application services. 12. Infor EAM Application and services should now be up. NOTE: During processing, the patch status will be echoed to the console. A patch log will also be created identified by having the current patch execution date and time as part of the filename in the patch directory. One common error is "java.io.IOException: Error in writing existing jar file" which is produced if the Infor EAM services were not stopped before patch installation (step 3). To correct, ensure that the Infor EAM services are stopped, and repeat the patch installation process. Depending on the specifications of the underlying hardware, the patch process may require up to an hour to perform all necessary updates. Please be patient to allow the patch process to fully complete before halting the patch script or exiting the current shell.
Installation steps for Advanced reporting on Windows server for Infor EAM:
NOTE: In a distributed installation environment, apply this patch first to each content manager, then to each report server, and finally to each web server. 1. Log all users out of the application. 2. Make sure you are logged in as the same user that installed Infor EAM. 3. Stop the Infor EAM Advanced Reporting services. 4. Ensure that a proper backup of the Infor EAM Advanced Reporting installation is available, in the event of any problems that arise during the patch process. 5. Copy the patch file EAM110ADVRPT201604.exe to a temporary folder like c:\temp 6. Double click on the self-extractor file to execute it 7. Press 'Unzip' to create and unzip files to a EAM110ADVRPT201604 folder 8. Open a command prompt (cmd.exe) and change the directory to EAM110ADVRPT201604 9. Set the variable REPSRV_HOME to the location where Infor EAM Advanced Reporting is installed. 10. Apply the patch by executing this command at the prompt substituting a value for {logging_level}: patch.bat {logging_level} NOTE: The brackets on logging_level denotes that this value is optional The default value for {logging_level} is info. The available logging levels are as follows from least to greatest: error warn info verbose debug 11. Go to the depconfig directory and execute this command at the prompt: deploy.bat NOTE: Running deploy.bat will automatically start the Infor EAM Advanced Reporting services 12. Infor EAM Advanced Reporting and services should now be up.
Infor EAM 11.0 201604 Jira Report
Installation steps for Upload Utility on Windows server for Infor EAM:
1. Copy the patch file UUWN110201604.exe to a temporary folder like c:\temp 2. Double click on the self-extractor file to execute it 3. Press 'Unzip' to create and unzip files to a UUWN110201604 folder 4. On the Windows Control Panel, select Add or Remove Programs. 5. Locate Infor EAM Upload Utility and select remove button. Select Yes to remove the application when asked if you want to remove it. 6. Go to the UUWN110201604 folder; execute Setup.exe to install the new Upload Utility.
Fix Content List Patch is contained in compressed file 110201604_patch.zip, which contains the following files: DB Server Files: · DB110201604ORACU.zip · DB110201604SQLCU.zip · EAMcomp.sql App Server Files: · EAM110LN201604.sh · EAM110WN201604.exe · EAM110WNADVRPT201604.exe · UUWIN110201604.exe Readme Files: · readme-110201512_patch.pdf · readme-110201602_patch.pdf · readme-110201604_patch.pdf This product release note is the readme-110201604_patch.pdf.
Infor EAM 11.0 201604 Jira Report
Jira Details for Infor 11.0 Enterprise Asset Management
Infor EAM 11.0 201604 Jira Report
EAM-15684 Departments - Unable to Edit Department Description
Description
Equipment / Setup / Department and then going to department (ex. 553A) and you can't edit the desciption &
save.
When you hit save it does nothing, no error & no save.
If you try to leave the page you receive the following error - Changes have been made to the current page.
Click Yes to continue and save the changes, or click No to continue without saving. Click Cancel to return to
the form without saving
Reproducible in IE & Chrome
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TED-USER1/111111
Took the following steps:
1- Department screen- Selected a department
2- Updated the description and saved
Verified save is successful...issue corrected...closing...
EAM-17857 Lots - Lot Expiration date is missing when Lot is added to PO.
Description
Lot information (expiration date) gets removed when a part is processed in PO receipt
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
Infor EAM 11.0 201604 Jira Report
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. create a Lot with a Expiration Date;
2. create a PO with a part line, approve the PO;
3. Create a PO Receipt against above PO, receive the part with the lot of #1;
4. after approved the PO receipt, go back to check Lot, the expiration date should be retained.
5. Lot Expiration Date and Manufacturer lot retained. (attached screenshot)
EAM-18102 Monitor Interface - Error field on List View tab is checked but Error field is
blank on Error Correction tab.
Description
Monitor Interface: Error field on List view tab is checked but is blank on Error Correction tab.
If Error is checked on List view tab then Error Correction tab should list/display the error.
Steps:
1. Parts: Create PART with Stock data.
2. System Codes: Create record for Entity = DOST, User Status = U1, System Status = U.
3. Status Authorization - Setup record for Status U1 for your User Group for Entity = TRAN.
4. Physical Inventory: Create record with Status U1, Part = PART.
5. Prompt Machine: Create record with Prompt = M231, enter value for all other fields, click Process
Transaction
6. Monitor Interface: Verify
- List View tab: Error field is checked for your record
- Error Correction tab: Error message field is blank.
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 2
Infor EAM 11.0 201604 Jira Report
11.0 SQL Ptch 2
http://usalvleam15.infor.com:7779/web/base/logindisp?tenant=ORA110PATCH02
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Steps:
1. Parts: Create PART with Stock data.
2. System Codes: Create record for Entity = DOST, User Status = U1, System Status = U.
3. Status Authorization - Setup record for Status U1 for your User Group for Entity = TRAN.
4. Physical Inventory: Create record with Status U1, Part = PART.
5. Prompt Machine: Create record with Prompt = M231, enter value for all other fields, click Process
Transaction
6. Monitor Interface: Verify
- List View tab: Error field is Unchecked for your record
- Error Correction tab: Error message field is blank.
Verified Record displayed as expected. Fixed
EAM-18599 Generate WO's - issue when clicking several times on Generate button with
Maintenance Patterns
Description
When we click several times on the generate button on the Preview tab of screen Generate WO's, in case we
use Maintenance Patterns, multiple work orders are being generated. See attached example with screenprints.
Infor EAM 11.0 201604 Jira Report
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TED-USER1/111111
Took the following steps:
1- Standard WO screen- Created Maintenance Pattern STWO called EAM-18599
2- Maintenance Pattern screen- Created Maintenance Pattern called EAM-18599 with "Allow Duplicate Open
WOs" checked and "Pattern Start Date" set to today
3- Sequence tab- Added sequence for previously created STWO with "Perform after" set to 1 month
4- Equipment tab- Added equipment
5- Select equipment record and under "Actions" link choose "Activate MP"
6- Activate MP pop up- Set "Due date" to today select equipment and click submit
7- Generate WOs screen- Set "Generate Through" to 3 months from today, check "Generate WOs for
Duplicate PMs" and uncheck "Release WOs for Fixed/Variable PMs", check "Release Maintenance Patterns"
checkbox and "Maintenance Pattern to "EAM-18599" and click process
8- Preview tab- 3 WOs are shown; Select all and click "Generate" 3 times quickly
9- "3 Records were processed successfully." message is received and "No work orders were
generated/released." message
10- Maintenance Pattern screen- Select MP again
11- Equipment tab- Verified only 1 equipment is shown (not 3)
12- Work Orders- Verified 4 WOs are shown
Issue corrected...closing...
EAM-18603 Requisitions | Parts - when base price retrieved no currency conversion done
in specific situations
Description
Infor EAM 11.0 201604 Jira Report
When one adds a part to a requisition and if there is no supplier, or a supplier but no catalog record set up for
this part, the system will default the base price of the part into the price field. Normally the currency
conversion should happen, but in specific situations it does not happen.
Testing Notes
Verified on environments listed below following steps from Reporters note.
Verified per note on jira and confirmation with Dev: The bug/fix in this scenario is that if we cannot find a
price in the currency of the line, then the price should not default in.
Steps:
DEFCURR = EUR
ORG K000 currency CZK, so part currency is CZK.
Supplier currency EUR.
We have a valid currency rate for CZK (0,0653) (covers the date of the requisition)
The base price in the Parts screen for the part is 3055,83 CZK.
No catalog record for this supplier / part.
Create a requisition (org K000).
Add this part
Verified 2 scenarios:
1. Req header with supplier's currency different from Part Currency. Saving Part
* Msg. is displayed, "Part does not exist in the selected supplier's catalog. Record will be created."
* Price defaults to 0,00.
2. Req header with supplier's currency same as Part Currency. Saving Part
* Msg. not displayed, Part is brought back with Price = 3,055.83 CZK
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
Infor EAM 11.0 201604 Jira Report
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-18696 Web Services Prompt - MP0220_AddIssueReturnTransaction_002 not
showing foreign language messages
Description
The message associated to webservice MP0220_AddIssueReturnTransaction_002 is always in english. Even
when you modify the english message in the database, it does not change. When using a foreign user, it should
show the foreign language message.
SELECT ERT_CODE, ERT_TEXT, ERT_LANG, ERT_TRANSLATE, ERT_UPDATECOUNT,
ERT_SQLIDENTITY
FROM R5ERRTEXTS
WHERE (ERT_CODE = '22518')
Testing Notes
Tested in 11.0 201604 patch
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
1. Set up web service prompt.
2. Set up user with language 'Francais'
3. Log in as this user.
4. Go to screen/tab for the web service prompt.
5. Enter invalid data and save.
6. Verify error message is shown in French.
EAM-18809 CLONE - InforION: ManufacturerPartyMaster Variation ID
Implementation
Infor EAM 11.0 201604 Jira Report
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that Sync inbound BOD with smaller variation id will not overwrite the previous
modifications of the same entity instance with larger variation id, and EAM will always have variation id
included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
Testing Notes
Tested in 11.0 201604 paatch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested ManufacturerPartyMaster inbound, verified BOD with lesser variationID is not processed.
Tested ManufacturerPartyMaster outbound, variationID is present.
EAM-19031 Supplier Returns | Parts - Default Value for Reason for Return is wiped out
on bringing back Part
Description
Supplier Returns | Parts - A default value is setup for 'Reason for Return' field. On invoking the Parts tab, the
default value is displayed fine. but, on bringing back a Part from the LOV, the value is wiped out defeating the
purpose of setting up a default value
Steps:
1. Reason for Return: Create a record.
2. Supplier Returns | Parts: Use Screen Designer to setup a Default value for 'Reason for Return' field
3. Go to Supplier Returns | Parts: Note that default value is displayed fine for 'Reason For Return' field in
Detail section in insert mode
4. Click in LOV for Parts and bring back a Part
5. Verify the value for 'Reason for Return' is wiped out.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Infor EAM 11.0 201604 Jira Report
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TED-USER1/111111
Took the following steps:
1. Reason for Return: Create a record.
2. Supplier Returns | Parts: Use Screen Designer to setup a Default value for 'Reason for Return' field
3. Go to Supplier Returns | Parts: Note that default value is displayed fine for 'Reason For Return' field in
Detail section in insert mode
4. Click in LOV for Parts and bring back a Part
5. Default value for 'Reason For Return' remains
6. Saved record and value remains
Issue corrected...closing...
EAM-19381 Web Service Prompt - When creating prompt for Work Order Children tab
the wrong web service is used.
Description
The prompt is using MP0023_AddWorkOrder_001 when it should use
MP0050_ModifyParentWorkOrder_001
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Create a WSP ADDCWO(desc="19381 CWO") as a tab on screen WSJOBS.
2. On the Web Services tab, enter
Infor EAM 11.0 201604 Jira Report
Screen=WSJOBS
Tab=CWO
Action=Insert
See Web Service is populated with MP0050_ModifyParentWorkOrder_001, save.
3. On the Fields tab, select "Select Multiple Fields" from the Actions menu.
4. Select childworkordernum, dependent, and parentworkordernum on the popup. Submit.
5. Select parentworkordernum from the grid, Parent Screen Key Field=Work Order, Max Length=30, Next
Seq=(the Seq of the 1st field)
6. User Group screen: select your group and go to the Screen Permissions tab.
7. Make tab "19381 CWO" available for screen "Work Orders".
8. Create 2 work order WO1 and WO2.
9. Create another work order W3.
10. For WO3, go to the WSP tab "19381 CWO".
11. Enter WO1, check Dependent, and save.
12. Enter WO1, leave Dependent unchecked, and save.
13. On the Children tab, verify WO1 and WO2 have been added with Dependent checked/unchecked
respectively.
EAM-19405 Campaigns | Close WOs - When esignatures are turned on and you try to
close WOs the esignature popup never shows up and the user isn't able to close WOs
Description
Clone of EAM-13632
Campaigns | Close WOs - When esignatures are turned on and you try to close WOs the esignature popup
never shows up and the user isn't able to close WOs
Testing Notes
Campaign_TC10_S01 passed on Auto 11.0 EE REG01 LN/JB/ORA on USALVAC62 on 4/22/16.
Infor EAM 11.0 201604 Jira Report
EAM-19590 Base - Dataspy return no records
Description
After upgrading to 11, dataspys are not operating properly. The data behind this issue is confusing. once they
upgraded they noticed that copied dataspys returned no values. If a filter was added to the same dayaspy, it
would return values, until the user logged out, then it would return no values again.
Steps to replicate:
• Login as R5
• Go to Work->Work Orders
• Click the right arrow to “Expand Right”
• Select the “All Open Work Orders” dataspy. It will display no records.
• Click on the “Edit” button
• Add security filter “Type” ≠ “Multiple Equipment Child”
• Save
• The dataspy will now display records.
• Log out, then log back in. The dataspy will no longer show any records.
• Perform the same steps again and the behavior repeats.
Generic steps:
Generic problem is if you set DBBUFSIZE < 50 then for each new or existing dataspy the "Number of rows to
retrieve" dropdown on Layout tab remains blank.
Test any grid by creating a new data spy after setting DBBUFSIZE < 50.
Testing Notes
Verified on environments listed below following generic steps from jira description.
Dataspy works fine with DBBUFSIZ < 50.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
Infor EAM 11.0 201604 Jira Report
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-19598 CLONE - InforION: Variation ID implementation for
CurrencyExchangeRateMaster
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that Sync inbound BOD with smaller variation id will not overwrite the previous
modifications of the same entity instance with larger variation id, and EAM will always have variation id
included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
This is to implement InforBOD variation ID standard for CurrencyExchangeRateMaster noun.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested CurrencyExchangeRateMaster inbound, lesser variationID is not processed.
EAM-19633 Reports - long term wo list report shows wrong due dates
Description
When due date is changed in the PM schedule, the due date on the Long term wo list does not follow that
modification.
http://10.21.213.45:7878/web/base/logindisp?tenant=FRGRE-ORA11GR2_EAM11_00041
R5
R5
See attached screenshots.
Infor EAM 11.0 201604 Jira Report
Testing Notes
Tested on the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TED-USER1/111111
Took the following steps:
1- PM Schedules- Created duplcate PM schedule with activity, and equipment and due date of today and
preform every day
2- Generated WO for PM schedule
3- Printed Long Term WO report for today through 10 days from now
4- Verified 10 WOs are printed with correct start dates
5- PM Schedules- Select PM schedule again and modified due date to a month from today on equipment tab
6- Ran report again for todays through 10 days from now
Verified no WOs are shown
Queried R5futureevents and verified dates are updated to reflect new due dates
Verifed that updates to dev mentioned fields also refresh the table for that PM schedule
Issue corrected...closing...
EAM-19758 Customer Invoice Detail (WZCIND) - rounding problem
Description
As well at invoice level as at line level we see that the sum is not correct having a discrepancy of 1 cent on this
report (WZCIND).
This invoice is attached plus a screenshot
Testing Notes
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01 BB-USER1 / 111111
Infor EAM 11.0 201604 Jira Report
1) Created a specific organization.
2) Created an asset 'A1' in the * org, checked Contract Equipment check box.
3) Associated a uom on the Meters tab.
4) Created an absolute reading of 100 for 15-JAN-2015
5) Created an absolute reading of 300 for 10-FEB-2015
6) Created a customer
7) Created a monthly contract starting 01-JAN-2015, until 31-DEC-2016. Next invoice on 01-FEB-2015.
8) Added a contract item, using above asset 'A1'
9) Added a charge definition ( related to above contract item, Usage Charges, Transaction Adjustment, Usage
Based, UOM section- Usage UOM meter 02, Starting Meter Value = null and rate 5.00 )
10) Approved the contract
11) Created an invoice with below
( Oracle )
declare
chk varchar2( 4 );
begin
o7gencustomerinvoices( '', '', '', '' ,'', chk );
end;
commit;
Attached screenshot of Report (WCZIND) and EAM Customer Invoice Screen | Contract Items
EAM-19774 WO Daily Scheduling | Scheduling - cancelling a wo daily schedule will
modify the creation date
Description
cancelling a wo daily schedule will modify the creation date of the scheduled wo (EVT_created).
Infor EAM 11.0 201604 Jira Report
I only tested this in EAM 11 SQL with patch 201510.
But maybe it is seen in Oracle too.
http://10.21.213.16:7878/web/base/logindisp?tenant=FRGRE-SQL2K8R2_EAM11_00013
R5
R5
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Go to work - wo planning - wo daily scheduling
2. Click Create Refresh Schedules
3. Go through all the tabs to finally schedule a wo in the Scheduling tab.
4. Select one of the wos and check evt_created date in database
SELECT [EVT_CODE],[EVT_DESC],[EVT_TYPE],[EVT_RTYPE],[EVT_created],[EVT_STATUS] FROM
[R5EVENTS]
where evt_code like ('YOUR WO')
5. Drag/drop a work order to the below part of the screen (to schedule a wo with a employee)
6. Cancel the session with help of the X button (bottom right of the screen)
7. Verified the evt_target date with script of point 4. has not been changed.
8. Tested with Employees who had start dates in the past and present.
EAM-19881 Messenger - email notification being sent even if record to trigger the email
fails
Description
Customer has a flex on r5events that the WO cannot be closed without a closing comment. They also have an
email trigger on r5events to send an email when a WO is closed.
Infor EAM 11.0 201604 Jira Report
The issue is when a user goes to close the WO without comments the email still sends although the WO really
did not close because the flex stopped it because there were no comments.
Testing Notes
Tested in 11.0 201504 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
1. Create a Post-Update Flex trigger on R5EVENTS:
DECLARE
v_desc VARCHAR2(80);
BEGIN
SELECT EVT_DESC INTO v_desc
FROM R5EVENTS
WHERE ROWID = :ROWID;
IF v_desc='JLG 19881' THEN
raise_application_error(-20003,'JLG testing 19881');
END IF;
END;
2. Create an Email trigger on R5EVENTS for status changed from R to C.
3. Create a wo with description "JLG 19881".
4. Close the wo, get flex error "JLG testing 19881", and wo is not closed.
5. Check Email Viewer, make sure no email generated.
EAM-20143 User Setup - Add 'Allow Global Dataspy Configuration' to List view,
Dataspy and filter options
Description
Infor EAM 11.0 201604 Jira Report
Several customers request this checkbox option is added to the Columns in the Dataspy/Layout, and filter
options so they can filter for and see which users have this option checked.
Testing Notes
Verified fixed on environments listed below.
Steps:
User Setup List View tab: Verified 'Allow Global Dataspy Configuration' is included in Quick Filter and
Dataspy (Filter/Sort/Layout pane) and functions fine using Quick Filter and Dataspy option.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-20250 Work Orders | Documents - Documents attached to PM/Equipment copied
twice to Work Order.
Description
Tested V11.0 patch 201506
Reported by multiple customers both V11.0 and 11.1.
Create or select Asset
Upload PDF document
Select Document and select 'Copy to Work Order' and 'Copy Document'
Create or select PM.
Upload PDF Document
Select Document and select 'Copy to Work Order' and 'Copy Document'
Save.
Infor EAM 11.0 201604 Jira Report
Generate WO from PM.
It has 4 Documents attached to the WO instead of just 2.
The have names with a document number and EVNTwonumber instead of the actual Document name.
Attached a screen shot from a customer that had 4 Documents on the PM and 2 on the System.
It shows 12 documents attached to the WO
If you select the Documents and change it to 'Copy Link' instead of 'Copy Document' it properly copies over
the Documents and displays the correct name.
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
TED-USER1/111111
Took the following steps:
1- Asset screen- Created Asset called EAM-20250
2- Documents tab- Uploaded a document
3- Selected document and checked box to "Copy to Work Order" and clicked "Copy Document" radio button
and saved
4- PM Schedule screen- Created a PM Schedule called EAM-20250 and added activity and equipment
5- Added a new document, following pattern from step # 3
6- Generate WOs- Generated WO for PM schedule
7- Work Orders screen- Selected WO
8- Documents tab- Verified that 2 different documents are shown
Issue corrected...closing...
Infor EAM 11.0 201604 Jira Report
EAM-20308 WO Quick Entry | Add/Edit Activity Comments - Error 'Unable to Retrieve
Text' displayed on saving w/o Activity instead of proper msg.
Description
WO Quick Entry screen - Add/Edit Activity Comments icon does not give proper msg. when icon is clicked.
Pop-up is displayed letting the User enter data and then when clicking Save in the pop-up, error message
'Unable to Retrieve Text' is displayed.
Other icons on this screen give proper msg. indicating required data needs to be entered before po-up can be
displayed.
*Steps:*
1. WO Quick Entry: Bringback a WO w/o an Activity or enter data only for required fields
2. Do not enter data for Activity. Click Save. System generates work order number.
3. Click Add/Edit Activity Comment icon on the WO Quick Entry screen - Activity Activity: Trade: section
4. Verify pop-up is displayed and error is displayed only on clicking Save.
*Browser:* Chrome
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
USR 1 / 123456
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
Testing Notes
Verified on environments listed below following steps from jira description.
Correct message is now displayed: “You must select a record before performing this action.”
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
Infor EAM 11.0 201604 Jira Report
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-20671 Requisitions | Parts | Assign Repair Details - using mouse with popup does
not save changes.
Description
Materials | Requisitions - Parts tab - using mouse with Assign Repair Details does not save changes if multiple
bins exist with a qty and the first one is changed to 0.
Steps to reproduce
1. Go to Materials | Parts.
2. Create Part REP-008, uom is each, tracking method is stocked.
3. Click on the Stores tab.
4. Select a store.
5. Enter a preferred supplier. Enter base, average, std, and last price as 10.00. Save.
6. Click on Stock tab.
7. Enter Store used in step 4. Enter bin, qty on hand as 10 and a lot of *. Save.
8. Click on the Repair Details tab.
9. Click on the Store at the top. At bottom, Change to External Repair Enter a Default Core Bin (REPAIR) and
check auto assign. New bins can be created from Materials | Setup | Stores. Bins tab. 2 repair bins are needed
here. If 2 are not already existing, create REPAIR and REPAIR2)
10. Go to Work | Work Orders.
11. Create a new work order. Does not matter equipment or type as long as its something that a user can create.
12. Add an activity. save.
13. On the Parts tab, issue qty 10 of the part created. Save.
14. Return qty of 5, check core return and bin of REPAIR. Save.
15. Return qty of 5 , check core return and bin of REPAIR2. Save.
Infor EAM 11.0 201604 Jira Report
16. Go to Materials | Requisitions. Create a new req for supplier entered in step 5.
17. Click on Parts tab.
18. Change type to at the bottom to External Repair. Click lookup and add part REP-008. qty 5. Save.
19. Approve req from Record View.
20. Go back to the Parts tab and select the part.
21. Click Options and Assign Repair Details.
22. USE MOUSE click into the first line of 5 and change it to qty 0. CLICK MOUSE into 2nd line qty and
enter 5.
USE MOUSE click Submit.
Click it again and the qtys are back to 5 for first line and 0 for second line even though you just saved it.
If you use tab instead of mouse, it stays saved.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Go to Materials | Parts.
2. Create Part REP-008, uom is each, tracking method is stocked.
3. Click on the Stores tab.
4. Select a store.
5. Enter a preferred supplier. Enter base, average, std, and last price as 10.00. Save.
6. Click on Stock tab.
7. Enter Store used in step 4. Enter bin, qty on hand as 10 and a lot of *. Save.
8. Click on the Repair Details tab.
9. Click on the Store at the top. At bottom, Change to External Repair Enter a Default Core Bin (REPAIR) and
check auto assign. New bins can be created from Materials | Setup | Stores. Bins tab. 2 repair bins are needed
here. If 2 are not already existing, create REPAIR and REPAIR2)
Infor EAM 11.0 201604 Jira Report
10. Go to Work | Work Orders.
11. Create a new work order. Does not matter equipment or type as long as its something that a user can create.
12. Add an activity. save.
13. On the Parts tab, issue qty 10 of the part created. Save.
14. Return qty of 5, check core return and bin of REPAIR. Save.
15. Return qty of 5 , check core return and bin of REPAIR2. Save.
16. Go to Materials | Requisitions. Create a new req for supplier entered in step 5.
17. Click on Parts tab.
18. Change type to at the bottom to External Repair. Click lookup and add part REP-008. qty 5. Save.
19. Approve req from Record View.
20. Go back to the Parts tab and select the part.
21. Click Options and Assign Repair Details.
22. Using mouse, click into the first line of 5 and change it to qty 0. Click mouse into 2nd line qty and enter 5.
Using mouse click Submit.
23. Reopen the Assigne Repair Details window, verify that first line is saved as qty 0, second line is saved as
qty 5.
EAM-20784 Purchasing Contracts | Parts - Error 'An error has occurred while processing
your request. Please contact your system administrator.' when trying to view audit trail on
Net Price field
Description
Purchasing Contracts | Parts - Error 'An error has occurred while processing your request. Please contact your
system administrator.' when trying to view audit trail on Net Price field
Steps to Reproduce:
1. Administration|Security|Audit Setup
2. Table = R5CONPARTS
Infor EAM 11.0 201604 Jira Report
3. Field = CPA_PRICE
4. Check Update, Insert, Delete
5. Go to Purchasing Contracts|Parts
6. Right click on Net Price field and note error message: Error 'An error has occurred while processing your
request. Please contact your system administrator.'
7. This is reproducible in Chrome and IE and in v11.0 and v11.1
Hosted Sumo Log shows the following errors:
2016-01-19 13:46:39,021 ERROR [com.dstm.mp.web.event.administration.AuditListEventHandler] class
com.dstm.mp.web.event.administration.AuditListEventHandler:perform ERROR: java.lang.Exception: class
com.dstm.mp.web.event.administration.AuditListEventHandler:constructAuditInfo ERROR:
java.lang.IllegalStateException: class
com.dstm.mp.web.event.administration.AuditListEventHandler$AuditInfo The columnNames arraylist is
empty
2016-01-19 13:46:39,021 ERROR [com.dstm.mp.web.event.administration.AuditListEventHandler] class
com.dstm.mp.web.event.administration.AuditListEventHandler:constructAuditInfo [tableName:
R5CONTRACTS]
2016-01-19 13:46:39,021 ERROR [com.dstm.mp.web.event.administration.AuditListEventHandler] class
com.dstm.mp.web.event.administration.AuditListEventHandler:constructAuditInfo WARNING more than one
table name exists in R5DEFAULTPAGELAYOUT for this page name: PSCONT_PAR. You must specify a
hidden field called audittablename in the JSP page.
2016-01-19 13:46:39,018 ERROR [com.dstm.mp.web.event.administration.AuditListEventHandler] class
com.dstm.mp.web.event.administration.AuditListEventHandler:perform Audit Params do not exist in Map.
Calling constructAuditInfo...
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Administration|Security|Audit Setup
2. Table = R5CONPARTS
3. Field = CPA_PRICE
Infor EAM 11.0 201604 Jira Report
4. Check Update, Insert, Delete
5. Go to Purchasing Contracts|Parts
6. Created record, right click on Net Price field,
7. Audit Trail box displayed
8, Click Audit Trail box, record displayed as expected.
EAM-20897 CLONE - Upload Utility is not supporting TLSv1.2 also for version 11.0
Description
The UU supports SSLv3 protocol. Since TLSv1.2 is enabled in Apache as a patch to mitigate POODLE
exploitation, UU connection is failing.
There is no configuration related issue.
Testing Notes
Issue is Fixed.
Infor EAM Upload Utility ver 11.0 has been tested for TLSv1.2 support
Also, these Security protocols are enabled now: Tls, Tls11, Tls12, Ssl3
Tested on Custom links below that was setup with Security protocol TLSv1.2. Refer to tPlace#2624 or
http://tplace.infor.com/Issues/EAM/IssueDetail.aspx?id=2624
SQL
URL - https://usalvweam6.infor.com/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TM - Patch 01 11.0 WN/JB/SQL
ORA
URL - https://usalvleam15.infor.com:4443/web/base/logindisp?tenant=Ora110Patch01
TM - Patch 01 11.0 LN/JB/ORA
Test Steps:
Infor EAM 11.0 201604 Jira Report
1. Install Infor EAM Upload Utility ver 11.0 from
http://usgvwdevsql02.infor.com/svn/InforEAM/branches/Patch
11.0.x/patch/released/201512/UUWN110201512_20897.exe
2. Open Infor EAM Upload Utility
3. Invoke Setup and add Web Service Connection
ORACLE:
Web Service URL: https://usalvleam15.infor.com:4443/axis/services/EWSConnector
Tenant: Ora110Patch01
User ID: R5
Password: R5
SQL:
Web Service URL: https://usalvweam6.infor.com/InforEAM/axis/services/EWSConnector
Tenant: Sql110Patch01
User ID: R5
Password: R5
4. Click Test Connection and verified that all connections are successful. This verifies that Upload Utility
supports TLS 1.2
5. Close Setup and in Upload File section
Upload From: <AssetTypeIssue.xls> Modified Data if necessary
Excel Sheet: Asset (Sheet1)
Upload To: Assets
Read First Row as Field Names - Checked
Update Existing Records - Checked
6. Select Auto-Map
7. Select Upload Data
Infor EAM 11.0 201604 Jira Report
8. Verified that Upload was successful
Upload process started.
Row 1 with value ASSET14 was uploaded successfully.
Upload process finished.
9. Click Done and message seen, "1 row was successfully uploaded."
10. Login to EAM, invoke Assets and verified that the Asset Uploaded matches Asset in <AssetTypeIssue.xls>
EAM-20916 PM Schedules | Equipment - error 'This record cannot be deleted because it
is associated with another record in the system' when changing due date.
Description
Steps to reproduce issue:
1. Screen PO schema, Equipment tab select an Object that has an WO (status Awaiting release) associated with
it and a due date.
2. On the tab Tools add a tool.
3. Do a select * from r5tooplan to make sure the tool is associated with the WO in step 1.
4. Now in the tab Equipment try to change the due date of the object used in step 1.
5. System gives error that "This record cannot be deleted because it is associated with another record in the
system.".
==> End user tries to update due date of object but gets a error message that record cannot be deleted.
Testing Notes
Tested in 11.1 201603 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. PM Schedules | Equipment - Select/Create an equipment that has a WO (status Awaiting release) and a due
date.
2. Tools tab - add a Tool.
Infor EAM 11.0 201604 Jira Report
3. Database, query table r5toolplan to verify that tool is associated with the WO in step 1.
4. Equipment tab - change due date of the equipment in step 1.
5. Update is successful.
EAM-20927 Generate WOs | Preview | Generate - Generate WOs get hung in loop if
Perform every and Perform on both populated on Daily/Weekly record.
Description
Duplicate PM. One Equipment record set to Perform Every 2 Weeks and Perform on 2nd Tuesday.
Customer does not know how that could have happened.
Only one record.
Notes from Dev
Package procedure o7wmbwog.x5popdupjobs sits in an endless loop, since they defined ‘Perform On’ data for
a 2 Weeks duplicate.
Also, please enter a Jira, so we can change the procedure to avoid the endless loop.
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
TED-USER1/111111
Took the following steps:
1. Create a duplicate PM for every 2 months, EAM-20927, Perform On 2 Tuesday.
2. Add an equipment for the pm, keep frenquency as every 2 months, set Due Date=today's date.
3. Run this sql statement in the DB to manually change the frequency to every 2 weeks.
ORA:
Infor EAM 11.0 201604 Jira Report
alter table r5ppmobjects disable all triggers;
update r5ppmobjects set ppo_perioduom='W' where ppo_ppm='EAM-20927';
commit;
alter table r5ppmobjects enable all triggers;
SQL:
alter table r5ppmobjects disable trigger all
update r5ppmobjects set ppo_perioduom='W' where ppo_ppm='EAM-20927'
go
alter table r5ppmobjects enable trigger all
4. Generate WOs screen: Gen thru=today+2month, PM=EAM-20927, check the option to gen. wo for
duplicate PMs, no other option checked.
5. Click Process
Verified system no longer hangs and correct WOs are shown to be generated
Issue corrected...closing....
EAM-20937 Issue/Return Parts - The system does not honor default return bin defined
for a part, when returning parts through pick ticket
Description
Parts | Setup a store with different default bin / return bin (store). DOC-CUR-10001 and DOC-CUR-10002
Define bin, lot and quantity on hand (stock).
Create work order: 262857
Create Pick ticket #10003 with both parts --> Approve.
Issue / return parts:
- Create issue first. Retrieve the parts using the "Pick Ticket" option in the "Actions" button. --> Submit
- Create return. Retrieve the parts using the "Pick Ticket" option in the "Actions" button.
Infor EAM 11.0 201604 Jira Report
All the parts of the pick ticket are retrieved at once, and the system does not honor the default return bin, * is
defaulted instead of -.
See attachment.
Test system:
http://10.21.206.150:7878/web/base/logindisp?tenant=FRGRE-SQL2K12_EAM11_00025
Testing Notes
Verified on environments listed below
Steps:
1. Stores: Create STORE1.
• Bins tab: Create BIN1 and BIN2
2. Parts: Create PART1
• Stores tab: Add STORE1, Default Bin = BIN1, Default Return Bin = BIN2
• Stock tab: Add STORE1, BIN = BIN1, LOT = *, Qty. on Hand = 1000
3. Work Orders: Create WO1 with Activity
4. Pick Ticket: Create PICKTKT1.
• Parts tab: Add PART1
• Record View: Approve.
5. Issue/Return Parts:
• Issue: select WO1, Actions Menu - select Pick Ticket (PART1 is added to grid), Submit Transaction
• Return: select WO1, Actions Menu - select Pick Ticket.
• Verify Bin = BIN2 and not BIN1 in Grid and Detail section
*** Additional Testing ***
1. Submit Transaction is successful
2. If Default Return Bin not set, and Default Bin exists, Bin defaults to BIN1
3. If Default Return Bin and Default Bin not set, Bin defaults to BIN1 (issued to BIN)
Infor EAM 11.0 201604 Jira Report
4. If Default Return Bin set and Default Bin not set, Bin defaults to BIN2
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-20964 Work Orders - Activities are duplicated on MEC WO when WO has a
Standard WO
Description
When adding a route to a WO with a Standard WO the activities are duplicated on the MEC WO.
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Steps:
1. Organization Option ROUTEEOB = Y
2. Standard WO - Create a standard wo with 1 activity
3. Routes - Create route with at least 1 equipment
4. Work Orders - Create a new WO using the standard WO from step 2.
5. Save.
6. Add the route from step 3 and save
7. Filter for the MEC WO.
8. Filtering on MEC WO indicated only 1 activity listed.
Infor EAM 11.0 201604 Jira Report
EAM-20981 Installation of patch 201512 (SQL) - error in the log file
Description
When installing the patch 11.0 201512 (SQL) the log file shows the following error:
BEGIN EAM110PATCH201512SQL16744.sql
Msg 248, Level 16, State 1, Server FRGRE-SQL2K8R2\INS2008R2, Line 2
The conversion of the nvarchar value '4625335567' overflowed an int
column.
The statement has been terminated.
(1 row affected)
(0 rows affected)
(1 row affected)
END EAM110PATCH201512SQL16744.sql
The problem seems to come from this statement:
UPDATE r5boilertexts SET bot_text = N'Equipement d''en-tête OT' WHERE bot_pool = 32631 AND bot_lang
= 'FR'
Testing Notes
11.0 201512 patch scripts were updated and tested. Issue has been resolved.
EAM-21025 CLONE - Work Orders - error when changing status
Description
An error is encountered when changing the status of a work order.
For example work orders : 69643 and 729922.
The error with status change is due to standard EAM (NullPointerException) in WorkOrderManagerBean
closingCodesChanged method. In the screen we did not change action/problem/failure code but only the status.
Infor EAM 11.0 201604 Jira Report
I think due to screen configuration some fields did not get any value (null) and get NullPointerException .
SOLUTION (maybe...?!) :
In stead of isStringEqual java string method, we should use the MP5 method (GenericUtility.isStringEqual)
which takes into account null objects.
private boolean closingCodesChanged(WorkOrderDef pOldWorkOrderDef, WorkOrderDef
pNewWorkOrderDef) {
String vOldProblemCode = pOldWorkOrderDef.getProblemCode();
String vOldActionCode = pOldWorkOrderDef.getActionCode();
String vOldFailureCode = pOldWorkOrderDef.getFailureCode();
String vOldCauseCode = pOldWorkOrderDef.getCauseCode();
DSTMDate vOldReported =
DSTMDate.toDSTMDate(pOldWorkOrderDef.getWorkOrder().getWorkOrderCore().getREPORTED());
String vNewProblemCode = pNewWorkOrderDef.getProblemCode();
String vNewActionCode = pNewWorkOrderDef.getActionCode();
String vNewFailureCode = pNewWorkOrderDef.getFailureCode();
String vNewCauseCode = pNewWorkOrderDef.getCauseCode();
DSTMDate vNewReported =
DSTMDate.toDSTMDate(pNewWorkOrderDef.getWorkOrder().getWorkOrderCore().getREPORTED());
if(!isStringEqual(vOldProblemCode, vNewProblemCode) || !isStringEqual(vOldActionCode,
vNewActionCode)
||!isStringEqual(vOldFailureCode, vNewFailureCode) || !isStringEqual(vOldCauseCode, vNewCauseCode))
{
return true;
}
if ((vNewReported == null && vOldReported != null) ||
(vNewReported != null && vOldReported == null) ||
Infor EAM 11.0 201604 Jira Report
(vNewReported.compareTo(vOldReported) != 0))
{
return true;
}
return false;
}
Testing Notes
Verified on the following environments with the steps below…
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 2
11.0 SQL Ptch 2
Created a wo where the Date Reported field was not populated.
Added an activity.
Add two equipment records on the Equipment tab.
Changed the status of the work order to completed with no errors.
EAM-21071 CLONE - CLONE - Release Individual PM WOs - Grid is not displaying
records when the screen is cloned
Description
Records are displayed in the grid when the screen is cloned and the original screen exists in the menu.But the
records are not displayed when the original screen is removed from the menu.
Steps to reproduce:
--
1. Set install parameter PPMSTAT = 'A'
Infor EAM 11.0 201604 Jira Report
2. Navigate to PM Schedules screen, Create a record say PM1
3. Select Activities tab and enter a record and save
4. select Equipment tab and enter a record and save
5. Navigate to Release Individual PM WO's screen and hit run dataspy and you should see PM record PM1
created in step 2.
Now clone the screen WSRELJ (Relase Indivudal PM WO's)
1. Create your own user group/user.
2. Clone WSRELJ screen.
3. Add it your user group menu.
4. Remove the original screen off your user group menu.
5. Navigate to Release Individual PM WO's screen and run dataspy.
ISSUE: There are no records displayed in the grid.
Tested on the following builds:
--
http://usgvlshotgunora.infor.com:7779/web/base/logindisp?tenant=DS_MP_1
http://usgvlqvm05.infor.com:7777/web/base/logindisp?tenant=DS_MP_1
User/Pass : R5/R5
Browser: Chrome 43.0
Testing Notes
Verified on environments listed below.
Steps:
1. Install Parameters: PPMSTAT = A
2. PM Schedules: Created PM1 and PM2, Type = Fixed and Variable, with Activity and EQ with Due Date =
<today>
Infor EAM 11.0 201604 Jira Report
3. Release Individual PM WOs: Ran dataspy, verified PM1 and PM2 is displayed in grid
4. Screens: Created a copy of WSRELJ (Release Individual PM WO's)
5. User Groups | Menus tab: Added Copy of WSRELJ screen to User Group
6. User Groups | Menus tab: Actions menu - use 'Delete Menu Item' option to remove Original WSRELJ
screen for User Group
7. Logout and log back in, invoked Copy of WSRELJ screen
8. Ran dataspy - Verified PM1 and PM2 record is displayed fine.
9. Verified PM can be released successfully.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-21075 CLONE - PO Receipts | Active Lines - Cannot receive more items than have
been ordered when trying to receipt a partially Purchase Order
Description
Steps to reproduce:
1- Go to Purchasing - Purchase order - Create a new PO
2- Go to Parts Tab and add a new line with the following information
Qty= 300
Price= $100
3- Approved the PO created.
4- Go to Materials - Transactions - PO receipts and create a new PO Recepit for this PO.
5- Go to Packing Slip Tab and clic on "Retrieve Lines" option.
Infor EAM 11.0 201604 Jira Report
6- Receive only 295 qty instead of 300 qty. Save the record.
7- Select the record and Clic on "Record Packing Slip" option process
8- Go to Active Lines Tab, select the line and clic on "Approved Part" option menu
Here the message "Cannot receive more items than have been ordered" appears and this is a new PO with a
new PO Receipt.
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Testing steps.
1- Go to Purchasing - Purchase order - Create a new PO
2- Go to Parts Tab and add a new line with the following information
Qty= 300
Price= $100
3- Approved the PO created.
4- Go to Materials - Transactions - PO receipts and create a new PO Recepit for this PO.
5- Go to Packing Slip Tab and clic on "Retrieve Lines" option.
6- Receive only 295 qty instead of 300 qty. Save the record.
7- Select the record and Clic on "Record Packing Slip" option process
8- Go to Active Lines Tab, select the line and clic on "Approved Part" option menu
9. No message displayed.
10. Continued to Processed Lines tab and record for 295 qty displayed as expected.
Infor EAM 11.0 201604 Jira Report
EAM-21092 CLONE - Release Individual PM WOs - Error occurs when trying to access
the lookup on the Status field
Description
If an advanced security filter is defined on the 'Release Individual PM WOs' screen the lookup of the Status
field (accesible via key F9) returns the error "Lookup failed due to an internal system error".The same logic
applied to the "standard" Filter section of the security dataspy does not cause this error.
Testing Notes
Tested on the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
R5/R5
Followed steps in attached document
Verified clicking F9 in WO Status field after adding criteria in ‘Advanced’ section - LOV opens fine, error is
not displayed.
Value can be brought back successfully
EAM-21114 CLONE - Assets | Meters - The Average Daily Usage as calculated after each
meter reading only shows zero (due to rounding)
Description
After entry of each meter reading the Average Daily Usage is calculated. But this value is rounded so will
yield 0 (zero) in all cases. The logical meter is used to record "Builds". A significant fraction of all preventive
maintenance ("Cycle Checks") is determined by the number of builds. A requirement is to calculate the best
estimate for the "Meter Due Date", i.e. the date on which the next maintenance order is expected. To this
purpose the number of builds remaining must be multiplied with the Average Daily Usage. But the misplaced
rounding prevents the proper use of this field.Note: with an Average Daily Usage of 10 the accuracy of the
extrapolated "Meter Due Date" will be 10%. The smaller the value of the Average Daily Usage the larger the
inaccuracy. When the Average Daily Usage is less than 0.5 the rounding will cause it to become 0 and the
"Meter Due Date" can no longer be calculated.
Testing Notes
Verified on environments listed below.
Infor EAM 11.0 201604 Jira Report
Verified on Meters tab of Assets and Assets Healthcare screen with User Locale = Europe
Verified creating record where Avg. Daily Usage value is > 1 and < 1. Correct Value was displayed.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-21122 CLONE - User groups | Screen Permissions - Security dataspy cannot be
selected
Description
On the Work Orders tab of the PM Schedules screen you can define a security dataspy. But in the Screen
Permissions tab of the User Groups screen no security dataspy can be selected.
Two screenshots have been attached.
Suspected cause: gridname WSPPME
Testing Notes
Verified on environments listed below
Steps:
1. PM Schedules | Work Orders tab: Create a dataspy, Security filter = checked
2. User Groups | Screen Permissions tab: select Work Orders tab of PM Schedules screen - Click in 'Security
Filter' LOV
3. Verified LOV contains dataspy created in step 1 and can be brought back and submitted successfully
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Infor EAM 11.0 201604 Jira Report
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-21176 Screens - cannot clone the standard screens
Description
Customer is not able to clone standard screens anymore. Eg. WSJOBS or OSOBJA. System throws error :
The system failed to carry out this function because of the environment or configuration problems.
Steps to reproduce:
# Go to Administration - Setup - Screens
# Look for WSJOBS
# Copy screen and try to save to WSKAAS (whatever)
Error pops up.
Testing Notes
Verified on customer schema environment below following steps from jira description.
1. Restored the db and reproduced the error
2. Had the db patch to 201604
3. Followed steps
4. Verified error is not displayed on saving/copying existing screen - WSJOBS
*** Additional Verification ***
1. Verified copied screen can be added to User Group
2. Verified Can invoke the copied screen and submit WO record successfully.
http://usgvlautsrv01.infor.com:7777/web/base/logindisp?tenant=ORA110ISSUE2620
R5/R5
Infor EAM 11.0 201604 Jira Report
EAM-21200 Databridge - ION - Sync.ItemMaster Manufacturer and Manufacturer Part
Code Error: The combination of Primary Manufacturer and Manufacturer Part Number is
not valid. at /PartStores[0]/MANUFACTURERPARTC
Description
When the Sync.ItemMaster BOD is sent to EAM with a new Manufacturer and Manufacturer Part Code,
Databridge is throwing the error:
The combination of Primary Manufacturer and Manufacturer Part Number is not valid. at
/PartStores[0]/MANUFACTURERPARTCODE[0].
This error is only with Databridge / ION transactions. The same Manufacturer and Manufacturer Part can be
entered for the part directly in EAM without any errors.
A copy of the BOD used to test has been attached.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested ItemMaster inbound with ManufacturerCode, ManufacturerPartCode, no problems. Also tested with
invalid manufacturer (gives error), and tested where only manufacturer/manufacturer part is presented (is
successful if already in the EAM stock record.)
EAM-21286 Web Service Prompts - MP2099_AddStoreToStoreReceipt_001 returns error
when creating new receipt
Description
When using prompt screen created from MP2099_AddStoreToStoreReceipt_001 to create a new receipt EAM
will return the message:
The system failed to carry out this function because of the system or configuration problems
Testing Notes
Tested Envronments:
Infor EAM 11.0 201604 Jira Report
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Web Service Prompt - Create a WSP using the MP2099 web service
Screen - SSSTSR.
2. Add the new prompt (Screen) to Menu structure for User group.
3. Navigate to the prompt and enter the required data and save.
4. Verified new Receipt in Store to Store Reciept screen.
NOTE: Do not use attachment to import prompt for testing the fix.
EAM-21290 Databridge/ION SyncSupplierInvoice error out for extra line when action
code is Change
Description
When eam.Databridge is set to true SyncSupplierInvoice error our for extra line when action code is Change.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested SupplierInvoice inbound with eam.Databridge flag set to true. Tested for new and existing invoice
lines.
EAM-21303 Work Orders | Monitored Data Results - Modifying records with aspect
prompt fields does not save changes
Description
1. Work || TPM Metric Reports - (Clone of WSJOBS)
2. Dataspy - AM Line Period Report Testing - select any WO
3. Use additional tabs dropdown arrow - Report Data (Monitored Data)
4. Select Metric Category T005 AM Line Measurements - Employees
Infor EAM 11.0 201604 Jira Report
5. Enter numeric value into the #Drumbeats EMP.AM Step 1
6. Save the report - entered value will disappear
7. Select T004. Select Down Day Score.
Enter value and submit. Value is erased.
WO 6876536
Testing Notes
Tested on Environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Steps:
1. Assets: Create BB-ASSET01
2. Custom Fields: CHAR1, CHAR2, NUM1, DATE1
3. Associated all Custom Fields to EVNT entity
4. Aspects: Created ASP1 and ASP2
5. Prompts tab: for ASP1: Added Custom Fields, Display = Checked for all.
CHAR1, Upload Column = EPO_VARCHAR1
NUM1, Upload Column = EPO_VARNUM1
DATE, Upload Column = EPO_VARDATE1
6. Prompts tab: for ASP2: Added Custom Fields, Display = Checked for all.
CHAR1, Upload Column = EPO_VARCHAR1
NUM1, Upload Column = EPO_VARNUM1
DATE, Upload Column = EPO_VARDATE1
CHAR2, Upload Column = EPO_COMMENT
Infor EAM 11.0 201604 Jira Report
7. Monitored Data: selected Assets 'BBASSET-01'.
Point Tab: Add record
Aspects tab: Added ASP1 and ASP2.
Aspect Popints tab: Add record for ASP1 and ASP2
8. Work Orders: Created WO1 with BB-ASSET01. Add Activity
9. Monitored Data Results tab:
- brought back AST1, ASP1,
- Verified associated Custom Fields are auto populated correctly
- Entered data for all Custom Fields and required fields, Saved
- Verified record is saved with value for all Custom Fields correctly
- Verified can update Custom fields value successfully
10. Monitored Data Results tab: Repeat step 9 with ASP2
*** Additional Testing ***
1. Verified on Work Orders Healthcare and Work Orders Hospitality screen.
EAM-21311 Generate WOs - Printing duplicate pm's not showing data
Description
Generating and printing duplicate pm's using WZWOSH report only shows the header and footer, no data.
Testing Notes
Tested hot fix in 11.0 201510 patch
http://usalvleam19.infor.com:2443/web/base/logindisp?tenant=ORA110ISSUE2573
Tested in 11.0 201604 patch
Infor EAM 11.0 201604 Jira Report
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
1. For screen WSBWOG, set the background for the screen as WZWOSH.
2. Go to Work | Process | Generate WOs
3. Select date to generated through and select check box for 'Generate WOs for Duplicate PMs.
4. Click Preview tab. Select Duplicate PM and check Print Work Orders check box. Click Generate.
5. Report now contains WO data, as it should.
EAM-21313 CLONE - InforION: Variation ID implementation for ConstrainedResource
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that Sync inbound BOD with smaller variation id will not overwrite the previous
modifications of the same entity instance with larger variation id, and EAM will always have variation id
included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
This is to implement InforBOD variation ID standard for ConstrainedResource noun.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested ConstrainedResource inbound, lesser variationID not processed.
EAM-21316 CLONE - InforION: Variation ID implementation for CodeDefinition
Description
DATABRIDGE IMPACT NOTE:
Infor EAM 11.0 201604 Jira Report
Enhancement is made so that Sync inbound BOD with smaller variation id will not overwrite the previous
modifications of the same entity instance with larger variation id, and EAM will always have variation id
included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
This is to implement InforBOD variation ID standard for CodeDefinition noun.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested CodeDefinition outbound, variationID included in BOD.
As per note in EAM-19280, there is no effect on CodeDefinition inbound.
EAM-21345 Base - WODDRV is inserting date value in wrong format when using french
SQL account
Description
When using MS SQL EAM account (SQL Server) in French, dates are inserted wrongly in database by the
WODDRV driver (administration - data collection - jobs). This produces wrong Graph results in start center.
The driver WODDRV runs every night and triggers O7POPULATECHARTDATA_WORKORDERCOST.
This triggers converts a date field from r5events table (and other fields) and inserts that newly formatted date
into R5SCWORKORDERCOST. The trigger takes into account the SQL server user language apparently and
depending on that language the date format is YYYY-MM-DD or DD-MM-YYYY (which is wrong). In
french it will take that last format it appears.
Be aware that if you run that trigger 7POPULATECHARTDATA_WORKORDERCOST manually on a
"french" database, it will produce the right date format.
Can be reproduced on any 11.0 SQL database.
Testing Notes
Tested in 11.0 201604 patch
http://usgvweamfrench.infor.com:7777/web/base/logindisp?tenant=SQL110ISSUE2626
1. Setup SQL server database in French.
2. Setup work orders for years 2015 and 2016.
Infor EAM 11.0 201604 Jira Report
3. Start Center - setup Chart Controls
a. Chart Type = WO Costs by WO Type
b. Chart Period = Months.
c. Show Year/Year = checked
4. Job Setup - make sure WODDRV driver is running.
5. After run notice that graph displays properly in Start Center.
6. Verify cws_date in table r5scworkordercost has correct format.
EAM-21393 InforBOD: Inconsistent mapping with AssetTrackingData inbound/outbound
Description
DATABRIDGE IMPACT NOTE:
Inbound actually maps tkd_sourcesystem and tkd_sourcecode from
AssetTrackingData\UserArea\Property\NameValue[@name='eam.SourceSystem'] and
AssetTrackingData\UserArea\Property\NameValue[@name='eam.SourceCode'].
Inbound mapping PDF points AssetTrackingData\Property\NameValue[@name='SourceSystem'] and
AssetTrackingData\Property\NameValue[@name='SourceCode'] which are consistent with outbound and
outbound mapping.
We will modify our inbound implementation to be consistent with outbound and inbound mapping while we
still ensure backward compatibility.
END OF DATABRIDGE IMPACT NOTE
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested AssetTrackingData inbound. Verified new mapping for Source System and Source Code.
Infor EAM 11.0 201604 Jira Report
EAM-21397 Call Center | Knowledge Base Search - issue with same KBA id in different
organizations
Description
An issue has been identified with Knowledge base searches in the call center screen. Descriptions from KBA’s
in 1 organization are being seen in another organization where they have the same KBA id.
See attached document
Testing Notes
Verified on environments listed below per confirmation with Dev.
Steps:
1. Created 3 KBA records - at * Org, Common Org and Specific Org with same value for "Title' field but
different value for Department, Provider, Service Category and Service Problem Code
2. Call Center - Searched for KBA - Verified all 3 KBAs are displayed fine
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 2
EAM-21416 InforION: AssetMeterReading outbound Variation ID Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle variation id for outbound only without saving cross-reference table.
Testing Notes
Infor EAM 11.0 201604 Jira Report
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested Sync AssetMeterReading outbound. Verified variationID attribute is present.
EAM-21419 InforION: PayableTransaction Variation ID Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that Sync inbound BOD with smaller variation id will not overwrite the previous
modifications of the same entity instance with larger variation id.
END OF DATABRIDGE IMPACT NOTE
This is to implement infor messaging standard requirement.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested PayableTransaction inbound, BOD with lesser variationID is not processed.
EAM-21422 InforION: Invoice Variation ID Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
This is to implement infor messaging standard requirement.
Testing Notes
Tested in 11.0 201604 patch
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Infor EAM 11.0 201604 Jira Report
Verified Invoice outbound (for contract invoice) had variationID present.
EAM-21431 CLONE - InforION: ReceiveDelivery\Shipment\InventoryAdjustment
outbound Variation ID Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle outbound only. ReceiveDelivery/Shipment involves PO Receipt/SupplierReturn, and Parts
Issue/Return(non-PO related Invy Transactions).
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested PO receipt and supplier return. Outbound BODs contain variationID.
EAM-21434 Assets | Meters | View Meter History - Physical Meter of Child Asset not
recording the values properly
Description
After assigning a new physical meter child meter readings recorded incorrectly.
Testing Notes
Verified on environments listed below following steps from Reporter's note.
Steps:
1. Create Asset RODOLFO-PARENT and Asset RODOLFO-CHILD. Create the structure between them and
associate a logical meter KMT to both. Parent with the Type of meter: Parent and Child wild type of Meter:
Parent & Child.
2. Insert 2 different readings in RODOLFO-PARENT. the Meter rolldown to the child which is correct.
Infor EAM 11.0 201604 Jira Report
3. Go to Equipment - Setup - Meters and create 2 different Physical Meters PARENTMETER and
CHILDMETER.
4. Go to RODOLFO-CHILD asset, meters tab and click in KMT. Assign the new physical, CHILDMETER
meter to this asset.
5. Go to RODOLFO-PARENT asset, meters tab and click in KMT. Assign the new physical,
PARENTMETER meter to this asset.
6. Insert 1 meter in RODOLFO-PARENT.
7. Verified Reading and Difference as same value
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-21436 CLONE - InforION: EmployeeWorkTime outbound Variation ID
Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle outbound only without the need to saving cross-reference table.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested EmployeeWorkTime outbound, variationID attribute is present.
Infor EAM 11.0 201604 Jira Report
EAM-21448 CLONE - Customer invoices - not all items passed to interface due to default
invoice A status
Description
When customer invoices are created with a default status A, one encounters a problem when incomplete
invoice is sent to the interface (Databridge/ION).
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1) Create a specific Org.
2) Associate the Org to your User,
3) Create an Asset and mark it as 'Contract'.
4) Create a Customer.
5) Create a Contract, using above data. Start Date 01/01 End Date 12/31. Next Invoice Date 02/10.
6) Associate the Asset on the Items tab.
7) Add a Charge Def, using above Item.
8) Approve the contract.
9) To be able to see the changes, setup audit on table r5customerinvoices, column civ_rstatus ( insert +
update).
10) Run the procedure in PL/SQL Developer:
declare
chk varchar2( 4 );
begin
o7gencustomerinvoices( null, null, null, null, null, chk );
end;
Infor EAM 11.0 201604 Jira Report
11) Check whether there are records in r5audvalues for the table of step 9). There should be records with value
P ( that is the new status introduced ). Also check that the status of the created Invoice is U.
12) On the Contract screen, create a new revision, set the Default Invoice Status to Approved and finally
approve the contract again.
13) Regenerate the invoice, using the correct values for invoice and org:
declare
chk varchar2( 4 );
begin
o7gencustomerinvoices( 'your invoice', 'your org', 0, null, null, chk );
end;
14) Check whether there are records in r5audvalues for the table of step 9). There should be more records with
value P ( that is the new status introduced ). Also check that the status of the created Invoice is A.
For SQL Server use:
declare @chk nvarchar( 4 )
execute o7gencustomerinvoices null, null, null, null, null, @chk.
EAM-21463 InforBOD: ProcessMaintenanceOrder inbound ownid
Description
DATABRIDGE IMPACT NOTE:
For ProcessMaintenanceOrder inbound processing, the following changes are made: if lid of incoming
Document ID is EAM's own id, the document id of the wo is assumed to be created in EAM. If incoming wo is
not found in EAM, a wo using incoming wo id will be created and no auto wo number will be used. Incoming
wo id needs to following EAM wo ID restrictions.
END OF DATABRIDGE IMPACT NOTE
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Infor EAM 11.0 201604 Jira Report
Tested Process MaintenanceOrder with lid attribute matching Partner ID in Databridge Partners screen.
1. If it matches, and this is a new work order, system takes the work order ID from the BOD
(MaintenanceOrderHeader\DocumentID).
2. If it does not match, system uses auto generated sequence number in EAM.
EAM-21466 InforBOD: MaintenanceOrder inbound with vertical option
Description
DATABRIDGE IMPACT NOTE:
We will add an optional element "eam.Vertical" under header UserArea and the valid values are
"Base","Hospitality". This element will decide how EAM handles incoming wo add/update/change request. If
the value is "Base", Databridge will call EAM base wo related web services only. If the value is "Hospitality",
Databridge will call EAM Hospitality wo related web services only. Otherwise(other values or this element is
absent from incoming xml),the current behavior remains and Databridge calls all wo related web services.
END OF DATABRIDGE IMPACT NOTE
This will resolve the following issue and some other vertical-related issues.
Steps:
# Work Order with status “FMAR - Pending FM Approval” is sent to ION using SYNCMAINTORDER
outbound BOD
# Workflow picks up and provides Approve / Reject buttons
# After the workflow has ended, and Acknowledgement BOD is sent to EAM, it includes the new Status.
Databridge fails to process the acknowledgement, citing a problem with the service code
# When repeating the process without service code, the updates works like a charm.
Notes (BBeemsterboer):
# I use the SYNCMAINTORDER bod to create a workflow in ION/Mingle
# The workflow changes the status to “Budget Approved” or “Budget Rejected”.
# After the workflow has ended, the new status is sent back to EAM viaa de Confirmation BOD
If the work order contains a value in the Service Code field, the error appears.
If the work order does not have a value in that field, the workflow executes perfectly.
Infor EAM 11.0 201604 Jira Report
Some screenshots of ION included
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested MaintenanceOrder inbound both with and without eam.Vertical tag, no problems.
EAM-21475 Upload Utility - Missing tabs in UU 11.0 201508 and 201510
Description
Since UU 11.0 201508 and 201510 some tabs are missing. In other terms, customers cannot upload data to
some tables due to missing options. See comparaison in attached screenshot. Eg. The parts associated tab is
present in the base 11.0 UU and 11.1 UU versions, but not in UU 11.0 201508.
Maybe it has something to do with the modification of UU for EAM-16752.
Also is attached the .exe UU for 11.0 201510
Testing Notes
Issue is Fixed.
Tested Connection to
Patch 01 11.0 WN/JB/SQL
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Web Service URL: http://usalvweam6.infor.com:7777/InforEAM/axis/services/EWSConnector
Tenant: Sql110Patch01
Patch 01 11.0 LN/JB/ORA
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
Web Service URL: http://usalvleam15.infor.com:7778/axis/services/EWSConnector
Tenant: Ora110Patch01
Infor EAM 11.0 201604 Jira Report
Test Steps:
1. Installed UU 11.0 201512 from
http://usgvwdevsql02.infor.com/svn/InforEAM/branches/Patch
11.0.x/patch/released/201512/UUWN110201512_21475.exe
2. Ran Upload Utility v11.0
3. Verified that 'Upload To' fields matches Attachment UU 201503, therefore FIXED !!!!
EAM-21654 CLONE - Base - Auditing reached max value for Identity column
Description
Customer reporting errors in front end with Auditing on for R5EVENTS.
R5AUDVALUES table has reached the max value for INT data type on AVA_SQLIDENTITY column.
Testing Notes
Verified on the following environment with the steps below…
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
1. Setup Auditing on R5EVENTS, evt_desc
2. Created a Work Order with a description.
3. Confirmed that an audit record was inserted into the r5audvalues table.
4. Ran the following SQL command on the database dbcc checkident(r5audvalues, reseed, 2147483646)
5. Updated the work order description to create another audit record.
6. The second audit record was created with the AVA_SQLIDENTITY = 2147483647 (maximum value for an
integer field.)
9. Updated the Work Order description to create another audit record.
10. Confirmed that no error was shown.
Infor EAM 11.0 201604 Jira Report
11. Confirmed that the audit record was created with the AVA_SQLIDENTITY = 2147483648
12. Ran several other audit record entries and no errors were shown.
EAM-21680 CLONE - InforION: ServiceConsumption Variation ID Implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle outbound only without the need to saving cross-reference table.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested ServiceConsumption outbound, verified variationID is present.
EAM-21806 CLONE - InforION: SourceSystemJournalEntry outbound Variation ID
implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle outbound only without the need to saving cross-reference table.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested SourceSystemJournalEntry outbound, verified variationID is present.
Infor EAM 11.0 201604 Jira Report
EAM-21828 CLONE - InforION: AssetTrackingData outbound Variation ID
implementation
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made so that EAM will always have variation id included in Sync outbound BOD.
END OF DATABRIDGE IMPACT NOTE
We will handle outbound only without the need to saving cross-reference table.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested AssetTrackingData outbound (for customer survey and event log), variationID is present.
EAM-21858 Materials | Parts - Change part number deletes parts associated records.
Description
Steps to reproduce:
1. Materials | Requisitions - Create a new requisition.
2. On parts tab - Choose Create New Part from the Action menu.
3. Materials | Parts - Open the new part record.
4. Click on Parts Associated tab and add one or more parts.
5. Click on the Record View and right mouse click to Change Part Number.
6. Enter a new part record that does not currently exist.
7. Click on Parts Associated. Note all the associated parts are gone
Testing Notes
Verified on the following environments with the steps below…
Infor EAM 11.0 201604 Jira Report
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
1. Materials | Requisitions - Create a new requisition.
2. On parts tab - Choose Create New Part from the Action menu.
3. Materials | Parts - Open the new part record.
4. Click on Parts Associated tab and add one or more parts.
5. Click on the Record View and right mouse click to Change Part Number.
6. Enter a new part record that does not currently exist.
7. Click on Parts Associated. All the associated parts are still correctly shown.
EAM-21863 CLONE - Databridge/ION Employee Availability Exception outbound
creates two xml's for one new record for sql server
Description
Trigger XMLOUT_POSINS_EXC (in file XMLOUT_POSINS_EXC.trg) should not be there.
Testing Notes
Tested in 11.0 201604 patch
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=SQL110PATCH02
Tested EmployeeWorkSchedule (for exception) outbound. Verified only one outbound BOD generated per
record. Verified XMLOUT_POSINS_EXC trigger is removed.
EAM-21877 Work orders | MEC work orders generated without an activity from
Duplicate PM schedule with a route
Description
When generating a Duplicate PM schedule with an activity and with a route, we get the main work order with
the activity, but the MEC work orders do not have the activity.
If the PM type is for example Variable, the MEC WO's do have an activity added.
Infor EAM 11.0 201604 Jira Report
Testing Notes
Verified on environments listed below.
Create a route, with Asset2 and Asset3.
Create a PM schedule with main equipment Asset1. The PM type is Duplicate.
Add an activity. Under equipment tab, add the Route.
Generate this PM,
Verified all 3 WOs have Activity associated to it.
*** Additional Testing ***
Verified generating WO for Fixed and Variable PMs with Activity. Works fine
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-21913 Requests for Quotations | Selection | Generate POs - Generate PO popup
takes report out of Screen PSRFQT instead of PSRFGP
Description
Generate PO popup takes report out of Screen PSRFQT instead of PSRFGP.
The request for quotation report is printed, r5pzprfq.xml, in stead of the PO report.
https://eam11.inforcloudsuite.com/EAM11/web/base/logindisp?tenant=INFORSUPEE_AX2
R5
111111
Testing Notes
Tested in 11.0 201504 patch
Infor EAM 11.0 201604 Jira Report
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
# Create a part, supplier, and store.
# Create an RFQ and add a supplier line and part line.
# Progress the RFQ to the "Sent to Supplier" status.
# Navigate to Quotations and find the quotation generated from your RFQ.
# Navigate to the Parts tab and update the part line to fill in a price.
# Set status of Quotation to "Received"
# Navigate back to RFQs, select your record, and navigate to the Selection tab.
# Check the part record and choose "Generate POs" from the Actions menu.
# Fill in required information and check the "Print PO" checkbox.
# Click the Generate button.
PO Report has been printed successfully.
EAM-21923 Purchase orders - issues after canceling PO header and not the lines
Description
When the PO header is set to Cancel status, system will give the possibilities to cancel the associated
requisition/lines and po lines.
Two questions are shows.
If you answer : NO and NO,
- the wo and activity fields are emptied
- requisitions fields are emptied
PO Line status is set to Unfinished. The issue is that it cannot be set to Cancelled. It will come up with
message : You must enter a work order and activity or a piece of equipment when purchasing a direct part.
If you answer : YES and NO,
Infor EAM 11.0 201604 Jira Report
- requisition will be cancelled
PO Line status is set to Unfinished. The issue is that it cannot be set to Cancelled. It comes up with message :
Requisition/line is invalid.
Could this be handled differently ? The messages are not very user friendly and seems even to be a bug.
https://eam11.inforcloudsuite.com/EAM11/web/base/logindisp?tenant=INFORSUPEE_AX2
R5
111111
Testing Notes
Verified on environments listed below followings steps from Dev's note.
Steps:
1. Create a WO/ACT.
2. Create a Requisition for WO/ACT with a Supplier.
3. Add a part line for the Req.
4. Approve Req, select Create PO.
5. Approve the PO, then cancel.
6. Select NO to prompt for canceling Req lines.
7. Select NO to prompt for canceling PO lines.
8. PO Lines tab: Make sure Req/Line and WO/ACT are not cleared from the PO line.
9. Repeat steps 2-8 except selecting YES/YES in step 6.
10. Repeat steps 2-8 except selecting YES/NO in step 6
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
Infor EAM 11.0 201604 Jira Report
EAM-21952 Base | Archive Records - Invoice Custom Field values are deleted but not
archived
Description
Create Custom Field and associate to INV (Invoices)
Create PO and Recieve. Create Invoice
Add value to the custom field on the Invoice.
Query R5PROPERTYVALUES where prv_rentity='INV' to verify record.
Archive Purchasing so it includes the above PO/Invoice.
No records in R5PROPERTYVALUES_ARCHIVE but the records are deleted from
R5PROPERTYVALUES.
Testing Notes
Tested against the following environments:
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
TED-USER1/111111
Took the following steps:
PREREQUISITE: Set install parameter ARCHTIME = null, so that the archival process starts faster
1- Custom Fields- Created custom field called CHAR01
2- Associate Custom Fields- Associated custom field to INV entity
3- Purchase Orders- Created PO with part line and approved the PO
4- PO Receipt- Received the PO and approved the part lines
5- Invoice Vouchers- Added PO to the invoice and approved the invoice; add value to custom field
6- Queried r5propertyvalues to verify custom field record is there
Infor EAM 11.0 201604 Jira Report
7- Archive Records- Created archive record for todays date and with only Purchase Orders checked
8- Clicked Start
9- Once process runs, checked r5propertyvalues again
Verified that record is removed from r5propertyvalues and added to r5propertyvalues_archive
Issue corrected...closing...
EAM-22014 Assets - security filter checked checkbox becomes unavailable and empty
Description
After having created a security filter on the asset screen, the security filter checkbox becomes unavailable and
empty after having saved the grid of the screen
https://eam11.inforcloudsuite.com/EAM11/web/base/logindisp?tenant=INFORSUPEE_AX2
R5
111111
Steps to reproduce:
1. Connect to EAM and open Equipment - Assets
2. Edit dataspy and create a security filter by checking security filter checkbox
3. Save the dataspy and leave the dataspy screen
4. In the listview the dataspy that is shown, is the new security filter dataspy
5. Save the GRID of the screen (with save icon on rightbottom of the screen)
6. Disconnect and reconnect
7. Open the asset screen and select the dataspy that is ticked as the security filter
8. Edit dataspy : no checkbox and unavailable
Testing Notes
Verified on the following environments with the steps below…
Infor EAM 11.0 201604 Jira Report
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
1. Connect to EAM and open Equipment - Assets
2. Edit dataspy and create a security filter by checking security filter checkbox
3. Save the dataspy and leave the dataspy screen
4. Log out and log in.
5. On the Asset Listview, select the security databaspy, resize the description field and click save at the right
bottom of the screen.
6. Log out and log back in.
7. Open the asset screen and select the dataspy that is ticked as the security filter
8. Edit dataspy : security filter checkbox is still correctly checked and enabled.
EAM-22056 WO Quick Entry - Option CLGROUP is not applied for Problem Code LOV.
Description
# Closing Codes: Create Closing Codes with a Group.
# Install Parameters: Set CLGROUP to GROUP or FULL.
# WO Quick Entry: The Problem Code LOV just shows an normal LOV listing the codes. The CLGROUP
setting is NOT applied.
Same problem exists on Work Requests Problem Code LOV
Note : On Work Orders, the Problem Code LOV shows the codes using the Groups created earlier. The
CLGROUP setting is applied correctly.
This also is not working on the Create Work Order screen, Problem Code field.
Tested in both 11.0 and 11.1
Open existing WO, Click Problem Code LOV. Codes are grouped per CLGROUP
Infor EAM 11.0 201604 Jira Report
Click + to create new WO. Click Problem Code LOV. Full list of Codes, not grouped.
NOTE FROM DEV: The scenario about insert mode in Work Orders is by design, pick an equiment first, since
the LOVs are equipment org controlled.
Testing Notes
Verified on environments listed below following steps from jira description.
Verified with CLGROUP = FULL and GROUP.
Verified all 4 LOVs (where applicable) displays fine on Work Orders, WO Quick Entry and Work Request
screen.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-22071 Generate WOs - Print Work Orders (WZJOBF) - Duplicate work orders not
Description
Work\Process\Generate WOs
Put a check in Generate WOs for Duplicate PMs and Print Work Orders.
Click the Preview Tab.
Put a check in a Duplicate WO(PM Type D). Click Generate.
Report(WZJOBF) shows No Records Returned. Same if I change that screen to use WZWOSH.
X out of the report viewer window, scroll down and select a F(Fixed) or V(Variable) type and click Generate.
The WO shows and prints no problem.
Infor EAM 11.0 201604 Jira Report
Testing Notes
Tested against the following environments:
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Took the following steps:
Create a PM schedule of type Duplicate. 1 weekly.
Add an activity.
Add a piece of equipment, with today's due date.
Go Generate WO's screen.
Check the generate Duplicates checkbox.
Go to preview tab.
Select our duplicate WO which has a temporary code starting with WOG.
Check the checkbox Print Work Order and select Generate.
The report opens with the duplicate PM WO displayed...issue corrected...closing...
EAM-22084 CLONE - Databrige/ION - Outbound Sync.Shipment not sending the UDF
fields.
Description
According to the InforEAMOutboundBODMapping.11.1.1.pdf, it is possible to send User Defined Fields
when Issuing/Returning items. However, these fields are not transmitted when sending Sync.Shipment.
Process.Shipment does contain the UDF fields. .
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Infor EAM 11.0 201604 Jira Report
1. Databridge Partners | Subscription - set up special handling for UPDINV | ExportInventoryTransactions to
be 'InforSoaDocumentExporter/R01/R01/OnRamp/BD'
2. Issue/Return parts - issue part, set up values for user defined fields.
3. DatabridgeMessageStatus - verify outbound BOD SyncShipment contains the user defined fields.
EAM-22187 Archive - Work Order Activities allowed to be reused on service lines after
running the archive process.
Description
Steps to reproduce:
1. Purchase order for vendor labor is approved and received to a work order.
2. Leave work order open and run archive process to include date that would archive the purchase order.
3. Purchase order is archived but the work order is still open and does not get archived.
Since the work order no longer has a corresponding relationship to a record in r5orderlines, the system allows
another purchase order to be created for this same wo/act.
Testing Notes
Verified on environments listed below following steps from jira description.
Verified WOs with System Status R and C and <User Created Status R> and <User Created Status C>
Verified:
1. POs are not archived when associated to WOs at R or <user created R status>. Correct Error message is
displayed on Archive Records | Purchasing tab - "The PO is related to a Work Order with a system status of R"
2. Updated the same WOs status to C and <user created C status>, PO records are archived fine.
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
Infor EAM 11.0 201604 Jira Report
EAM-22241 Suppliers | Parts - On List Detail, the List is out of synch with the Detail for
the Preferred checkbox
Description
If you add an alternate supplier on the suppliers tab, this will show the added supplier as a preferred supplier
on the suppliers screen when it should not be marked as preferred.
Testing Notes
Verified on environments listed below following Reporter's 'Steps to Reproduce' note.
1. Select a part on Parts screen, on the record view verify a preferred supplier is selected.
2.Now go to the suppliers tab and add a new supplier there, but do not check the preferred checkbox on the
new supplier.
3.Suppliers | Parts tab: Verify Preferred checkbox on top and bottom of screen
For SUP 1 = Checked
For SUP 2 = Unchecked
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
EAM-22357 CLONE - Mobile full VGA: Sync error: "Error in executing query:Operand
type clash: datetime2 is incompatible with int", key - BCCOMOBJWO
Description
EAM 11.1 Build 201511 and EAM Mobile Full VGA 11.1
Infor EAM 11.0 201604 Jira Report
After Sync Date you have error: "class com.dstm.mp.mpentitycollection.base.xmlquery.XMLQueryException:
Error in processing entity XMLQuery Error in processing entity XMLQuery Error in executing query:Operand
type clash: datetime2 is incompatible with int", key - BCCOMOBJWO
It is a failure on downloading equipment comment, other functions should work.
Testing Notes
Issue is Fixed.
Tested on Full VGA and HandHeld device
Patch 01 11.1 WN/JB/SQL
http://usgvwqaserv04.infor.com:7777/BASEURI/web/base/logindisp?tenant=Sql111Patch01
Patch 01 11.1 LN/JB/ORA
http://usalvleam10.infor.com:7779/BASEURI/web/base/logindisp?tenant=Ora111Patch01
Schema: d111patch01
Infor Ming.le Enterprise 11.1.2.439
Chrome: 49.0.2623.87
Login as GD-MOBUSER1 / 111111
Test Steps:
1. In EAM, invoke Assets screen and create 5 Assets (ASSET1 thru ASSET5) with Comments
2. Next, invoke Work Order screen and create (WO1) with ASSET1, Assigned To <GD-MOBEMP1>
3. Create another Work Order (MEC WO2) with ASSET1, Assigned To <GD-MOBEMP1>. Equipment tab,
add ASSET2, ASSET3, ASSET4
4. Invoke Standard WO screen and create a Standard WO (STWO1). On Comments tab, add a comment.
5. Invoke Work Order screen and create (WO3 with Standard WO) with ASSET5, add Standard WO
(STWO1), Assigned To <GD-MOBEMP1>
6. Login to Infor EAM Mobile and click on Sync Configure
For = <GD-MOBGRP1> and make sure that 'Download Equipment Comments' and 'For downloaded WO
only' are Checked.
Infor EAM 11.0 201604 Jira Report
7. Save
8. Next, invoke Sync Data and do a Full Sync. Sync is successful.
9. Logout/Login and invoke Work Order
10. Select <WO1> and click on Equipment Comments. Verified that Comments are seen.
(satisfies BCCOMOBJWO --Grid for Equipment comment for downloaded WO)
11. Next, go back to List View and select <MEC WO2> and click on Equipment Comments. Verified that
Comments are seen
12. Next, click on Equipment tab and select each Equipment in grid, ASSET2, ASSET3, ASSET4, and click
on Equipment Comments. Verified that Comments are seen for each equipment
(satisfies BCCOMOBJWO_MEC --Grid for Equipment comment for downloaded MEC WO)
13. Next, Close out form and Invoke Equip | Equipment Details | and select ASSET1 thru ASSET5 and click
on Equipment Comments.
14. Verified that Comments are seen for ASSET1 thru ASSET5
15. Invoke Work Order screen and select <WO3 with Standard WO> and click on Equipment Comments.
Verified that Comments are seen.
(satisfies BCCOMST – Grid for Standard WO comment)
----------------------------------------------------------------------------------------
Issue is Fixed.
Tested on Full VGA and HandHeld device for SQL and ORACLE
Patch 01 11.0 WN/JB/SQL
http://usalvweam6.infor.com:7777/InforEAM/web/base/logindisp?tenant=Sql110Patch01
Patch 01 11.0 LN/JB/ORA
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=Ora110Patch01
Schema: d110patch01
Infor Ming.le Enterprise 11.1.2.439
Chrome: 49.0.2623.87
Infor EAM 11.0 201604 Jira Report
Login as GD-MOBUSER1 / 111111
Test Steps:
1. In EAM, invoke Assets screen and create 5 Assets (ASSET1 thru ASSET5) with Comments
2. Next, invoke Work Order screen and create (WO1) with ASSET1, Assigned To <GD-MOBEMP1>
3. Create another Work Order (MEC WO2) with ASSET1, Assigned To <GD-MOBEMP1>. Equipment tab,
add ASSET2, ASSET3, ASSET4
4. Invoke Standard WO screen and create a Standard WO (STWO1). On Comments tab, add a comment.
5. Invoke Work Order screen and create (WO3 with Standard WO) with ASSET5, add Standard WO
(STWO1), Assigned To <GD-MOBEMP1>
6. Login to Infor EAM Mobile and click on Sync Configure
For = <GD-MOBGRP1> and make sure that 'Download Equipment Comments' and 'For downloaded WO
only' are Checked.
7. Save
8. Next, invoke Sync Data and do a Full Sync. Sync is successful.
9. Logout/Login and invoke Work Order
10. Select <WO1> and click on Record View | Equipment Comments. Verified that Comments are seen.
(satisfies BCCOMOBJWO --Grid for Equipment comment for downloaded WO)
11. Next, go back to List View and select <MEC WO2> and click on Equipment Comments. Verified that
Comments are seen
12. Next, click on Equipment tab and select each Equipment in grid, ASSET2, ASSET3, ASSET4, and click
on Equipment Comments. Verified that Comments are seen for each equipment
(satisfies BCCOMOBJWO_MEC --Grid for Equipment comment for downloaded MEC WO)
13. Next, Close out form and Invoke Equip | Equipment Details | and select ASSET1 thru ASSET5 and click
on Equipment Comments.
14. Verified that Comments are seen for ASSET1 thru ASSET5
15. Invoke Work Order screen and select <WO3 with Standard WO> and click on Record View | Equipment
Comments. Verified that Comments are seen. (satisfies BCCOMST – Grid for Standard WO comment)
Infor EAM 11.0 201604 Jira Report
EAM-22411 Base - Update AppConfig.java for 11.0 201604 patch
Description
Change BUILD_VERSION to 11.0 201604
Testing Notes
Verified on the following environments that the build number was updated to 201604…
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 2
11.0 SQL Ptch 2
EAM-22415 CLONE - Databridge : SyncMaintOrder - with Systems, Positions, Locations
getting error 'OBRTYPE is a required field'
Description
After upgrading to 11.2 errors in outbound SyncMaintorders when EVT_OBJECT is position, location or
system.
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested Sync Maintenance Order outbound with equipment types asset, position, system, and location. No
errors found.
EAM-22446 PM Schedules - Meter Due populating incorrectly on minor nested PM when
major nested PM is completed
Description
Infor EAM 11.0 201604 Jira Report
When completing a major nested PM work order that has both an Hours and Miles meter - the minor nested
PM's "Meter Due" field is updated with the Miles meter instead of the hours meter even though the Meter
Interval is set to Hours on both PM's.
Attached document lists additional details and steps to reproduce.
Testing Notes
Verified on the following environments with the steps below…
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
1. Create asset A1 with two meters with UOMs U1 and U2, put U1 on the record view (primary meter).
2. Create meter-based PM1, PM2 for A1:
3) Both are of Variable type.
4) They are nested with a Nesting Reference code NR1.
5) Intervals are 150 U2 for PM1(minor) and 900 U2 for PM2(major). (Note PMs' meter uom=U2 while asset's
primary meter uom=U1.)
6) Both Meter Due at 1000 U2.
7) On the Asset entered in a reading of 1001 for the U2 Meter.
8) Release Individual PMs: Release both PMs, minor one is by-passed.
9) Go to the major WO to enter meter readings: 20,000 U1 and 3,000 U2.
10) Close WO.
11) The meter due field on PM1 for U2 is correctly set to 3,150. For PM2 U2 is correctly set to 3,900.
EAM-22459 CLONE - Asset Inventory - Multiple issues
Description
Infor EAM 11.0 201604 Jira Report
Please see attached document. Customer discovered several issues on the Asset Inventory screen. For some a
work around exists but we would still need your feedback, For two issues on Inventory Verification Date no
work around exists (bugs) :
# For all these assets the Inventory Verification Date is already populated – before anything is verified at all.
This is incorrect: it is very unlikely that the Verification Date will be equal to the date the session has been
created.
# When no Observed Location is entered the resolution is set to ‘Asset Not Found’ when the session is
approved. This is correct but still the Inventory Verification Date on the Asset screen is updated! Erasing the
Inventory Verification Date on the Results tab prior to approval has no effect as the Verification Date is
repopulated immediately. This is a serious issue! Especially when assets are not found this should be
highlighted instead of hidden by overwriting the date last (truly) verified.
Testing Notes
Verified on the following environments with the steps below…
http://usalvweammingle/sitepages/inforsuite.aspx
11.0 ORA Ptch 1
11.0 SQL Ptch 1
1. Create two locations, LOC1/ORG1 and LOC2/ORG1.
2. Create asset A1 with Assigned To=E1 and Location=LOC1.
3. Create asset A2 with Assigned To=E1 and Location=LOC1.
4. Asset Inventory Parameters: Assigned to=E1 and Parent Location=LOC1, create the session.
5. Asset Inventory Results: change dataspy to All Records - A1 and A2 show up - Verification Date should be
blank for both.
6. Select A1, enter observed location LOC2/ORG1, and click the link to update location - Verification Date is
set to today's date.
7. Approve the session: Verification Date remained unchanged for A1(today's date) and A2(blank).
8. Verified values for Inventory Verification Date on the Assets screen: A1(today's date) and A2(blank).
EAM-22463 Customer Invoices - The new generated invoice status should not be
"Approved" if an earlier invoice exists with a status of “Processing Error”(SQL only).
Infor EAM 11.0 201604 Jira Report
Description
Customer Invoices - The new generated invoice status should not be "Approved" if an earlier invoice exists
with a status of “Processing Error”(SQL only).
According to use case EAM.WORK.SCOPE.GenerateCustomerInvoices.docx 8.3, the status of the new
generated invoice should not be "Approved" if an earlier invoice exists with a system status of “Unfinished” or
“Processing Error”.
8.3 Previous Invoice Not Approved
If an invoice is generated for a Customer Contract or Customer Rental and an earlier invoice exists with a
system status of “Unfinished” or “Processing Error” the new invoice generated or regenerated by this process
cannot get system status “Approved”. Rather than “Approved” assign the System Default for system status
“Unfinished” or, in case of errors, system status “Processing Error”.
http://usalvweam2.infor.com:7777/web/base/logindisp?tenant=SQL111REG02
Browser: IE11
Steps to reproduce:
1. Log in as 5DADC22Z02N9GU1P08C2V676K2/111111
2. Go to Customer Invoices, click Expand Right, set filter field to Contract, filter value to 5213SNQ7, click
Run
3. Noticed that status of invoice 10010 is "Processing Error", the next invoice (10014) status is "Approved".
Note: Failed script: CustomerContracts_TC04_S02 and CustomerContracts_TC06_S01
Testing Notes
Verified on the following:
http://usalvweam2.infor.com:7777/web/base/logindisp?tenant=SQL111REG02
Browser: IE11
Steps to verified:
Run Customer Contracts RTP(Including CustomerContracts_TC04_S02, CustomerContracts_TC06_S01), it
passed without issue.
Attached the log.
Infor EAM 11.0 201604 Jira Report
EAM-22475 CLONE - Databridge/ION - Inboud ProcessAssetTrackingData BOD fails
with error: java.lang.instantiationException.
Description
DATABRIDGE IMPACT NOTE:
Enhancement is made for EAM to support ProcessAssetTrackingData inbound in addition to
SyncAssetTrackingData inbound.
END OF DATABRIDGE IMPACT NOTE
ProcessAssetTrackingData BOD fails with error: java.lang.instantiationException.
Looks like the system does not support verb Process for AssetTrackingData
as changing the verb to Sync did work. Can this be added?
Testing Notes
Tested in 11.0 201604 patch
http://usalvleam15.infor.com:7778/web/base/logindisp?tenant=ORA110PATCH02
Tested Process AssetTrackingData inbound. BOD is processed successfully. Acknowledge AssetTrackingData
outbound BOD is sent in return.
EAM-22491 CLONE - InforEAMOutboundBODMapping.10.1.4.pdf,
InforEAMInboundBODMapping.10.1.4.pdf sequence number incorrect
Description
The ION AssetMaster BOD mapping (both inbound and outbound) describe the tag for the variable fields as
containing the variable sequence number between brackets:
eam.Variable(i): obj_variable(i) where (i) =1,...,6,
while in reality no brackets should be used:
<Property>
<NameValue name="eam.Variable6" type="StringType">01A001</NameValue>
</Property>
The documentation should be updated.
Infor EAM 11.0 201604 Jira Report
Testing Notes
Mapping documents for AssetMaster are updated.