APAR status
Closed as program error.
Error description
PROBLEM: TPAE7604 - Workorder Scheduled Finish Date is not updated upon decrease of planned labor hours. ENVIRONMENT: App Server IBM WebSphere Application Server 8.5.5.3 Tivoli's process automation engine 7.6.0.4 Build 20160316-1020 DB Build V7604-37 IBM Maximo Mobile 7.5.1 .0-20150911-1512 Build 20130603-1027 DB Build V7510-05 HFDB Build HF7S10-03 IBM TPAE Integration Framework 7.6.0.4 Build 20160313-2330 DB Build V7604-22 IBM Maximo Asset Management 7.6.0.4 Build 20160310-1641 DB Build V7604-01 Server OS Windows 6.3 Server DB Oracle 11 .2 (Oracle Database 11 9 Release 11 .2.0.4.0 - 64bit STEPS TO REPRODUCE: 1. Go to Work Order Tracking application 2. Create a new Workorder 3. Set Scheduled Start- and Finish date to 'Right Now'. 4. Switch to Plans tab 5. Plan Labor Hours by clicking New Row button 6. Enter 8 Regular Hours for Labor STANLEY 7. Go back to Main tab and confirm that Scheduled Finish Date has been updated 8 hours ahead 8. Switch to Plans tab again 9. Change STANLEYS Regular Hours to 4 10. Go back to Main tab and note that Scheduled Finish Date still shows 8 hours ahead as in step 7. - This is wrong, it should be updated to only 4 hours ahead. This is causing incorrect finish date on customers work plans. When a labor is deleted or reassigned to a task, the scheduled start/finish dates should be re-evaluated.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * Maximo users who use the Work Order Tracking application. * **************************************************************** * PROBLEM DESCRIPTION: * * The Work Order Scheduled Finish Date is not updated/reduced * * when when user reduced the hours of a planned labor record. * * This is when the value of the system property * * mxe.skd.syncwodates is 0. * **************************************************************** * RECOMMENDATION: * * Please use the System Properties app to change the value of * * the system property mxe.skd.syncwodates to 1. * ****************************************************************
Problem conclusion
This is fixed in code. Additionally, user needs to change the value of system property mxe.skd.syncwodate to 1. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Interim Fix for Release 7.6.0.8 Product
Temporary fix
Comments
APAR Information
APAR number
IV85830
Reported component name
WORK ORDERS
Reported component ID
5724R46WO
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-17
Closed date
2016-12-13
Last modified date
2016-12-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
WORK ORDERS
Fixed component ID
5724R46WO
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPPU","label":"Work Order Tracking"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
13 December 2016