APAR status
Closed as program error.
Error description
Maximo Scheduler Run Optimization against Scenario: Runoptimization with "run at this time" option, COMMITINPRG flag stays to 1, not set back to null or 0, preventing publish to work. Step-by step to reproduce Maximo Scheduler Run Optimization against Scenario: Runoptimization with "run at this time" option, COMMITINPRG flag stays to 1, not set back to null or 0, preventing publish to work. Step-by step to reproduce 1- Preventive Maintenance -> Select PMs with a craft on the job plan 2- Select Action -> Generate Workorders (Uncheck the User Frequency criteria checkbox) Ensure when the workorders are created that they have the following required fields using the sql below: (Job Plan labor hours would be ideal so that information gets automatically populated on the workorders but not required as the other fields can be manually populated afterwards) -- Scheduler Required Populated Fields select a.wonum as "Work Order", wo.estdur as "Work Order Duration", a.laborhrs as "Assignment Hours", wp.laborhrs as "Work Order Plan Labor Hours", jl.laborhrs as "Job Plan Lab Hours", jl.craft as "Craft", jp.jpduration as "Job Plan Duration", jp.jpnum as "Job Plan"--, wp.in as "WO Interruptable?" from assignment a, wplabor wp, jobplan jp, workorder wo, joblabor jl where a.wonum = wp.wonum and a.wonum = wo.wonum and wo.jpnum = jp.jpnum and jp.jpnum = jl.jpnum and jp.status = 'ACTIVE' and a.wonum in ( select wonum from workorder where (woclass = 'WORKORDER' or woclass = 'ACTIVITY') and historyflag = 0 and istask = 0 and siteid = 'UK' and targstartdate >= '2017-04-08 00:00:00.000' and vendor = 'MESD' ) order by wo.estdur, a.wonum; 3- Go To -> Planning and Scheduling -> Scheduler 4- Create a new Schedule, using Person Calendar and Shift Top Level Work Records Only - Checked Refresh when opening Gantt view - Checked Scenario Allowed - Checked Work Query - (woclass = 'WORKORDER' or woclass = 'ACTIVITY') and historyflag = 0 and istask = 0 and siteid = 'UK' and targstartdate >= '2017-03-01 00:00:00.000' and vendor = 'MESD' Resource Availability - exists (select 1 from dbo.personcal where ((shiftnum = 'SCHED_85' and calnum = 'SCHED_P')) and (personid=labor.personid and orgid=labor.orgid) and endlocation is not null) 5- Select Action -> Create Scenario / Create Resource Leveling Scenario 6- Click Toggle Scenario 7- Run Optimization against Scenario - At this time today's date + 1 minute - Refresh Project Data - Checked - Constraints tab no box ticked (selected) 8- Select Action -> View Optimization Processes To check what status the scenario is at. The refresh button can be used until the status shows "Processed" 9- Go To Scheduler Gantt view tab - In this example you will see 2 Engineers for the EDU-Mobile AC Engineer craft - You'll see all jobs have been scheduled for 8:00AM. They should have been scheduled across the day and on future days until all the work has been scheduled 10- Go To -> Graphical Assignment application 11- Select Action menu -> Create Work List from Schedule 12- Select your Scenario 13- Select Action menu -> Create Spatial Scheduling Scenario 14- In window Create Spatial Scheduling Scenario - Enter a Scenario Name and Description - Click OK 15- Make sure the scenario has been toggled to and click on Run Optimization button 16- On Spatial Scheduling Optimization window - Select Run at this time: Today's date and time = 1 minute - Objectives tab Select Maximize the Number of Assignment Work Orders, Minimize Travel - On Constraints tabs: Include Travel Time in Total Time (Checked) - On Variables tab: keep as it is. - Click on Submit button View Schedule Optimization 17- Go To -> Gantt View - Workorder on wrong date as expected as the original schedule was incorrect - All workorder again assigned on the same initial date - WO are not assigned to any of the engineers 18 Click on the Globe Publish Scenario - Assignment Status should change to Assigned but it doesn't as the COMMITINPRG field on the SKDPROJECT table had not been set back to NULL after the optimization finished. The DB2 sql script to check if the COMMITINPRG field has been set back to NULL when the optimization finishes select * from skdproject where name like '%APR17%' and COMMITINPRG = 1 Expected Result The COMMITINPRG field on the SKDPROJECT table should be set back to NULL or 0 after the optimization finished. Environment: App Server: IBM WebSphere Application Server 7.0.0.41 Software Product & Version: IBM Maximo Asset Management 7.5.0.10 Build 201604172215 DB Build V75010-00 Tivoli's process automation engine 7.5.0.10 Build 20160417-2030DB Build V75010-28 IBM Maximo for Service Providers 7.5.3.0-20151014-1011 Build 20151014-1011 DB Build V7530-19 HFDB Build HF7530-07 IBM Maximo Asset Management Scheduler 7.5.2.0 Build 20160417-2030 DB Build V7520-189 IBM TPAE Integration Framework 7.5.1.5 Build 20160408-1816 DB Build V7515-02 IBM Maximo Mobile 7.5.1.0-20140716-1426 Build 20130603-1027 DB Build V7510-05 HFDB Build HF7510-03 Server OS: Windows Server 2012 6.2 build 9200 Server DB: DB2/NT64 10.5 (SQL10057)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: * * maximo scheduler users * **************************************************************** * PROBLEM DESCRIPTION: * * RUN OPTIMIZATION WITH "RUN AT THIS TIME" OPTION, COMMITINPRG * * is not set back to 0 * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fix has been made to fix....The fix for this APAR is contained in the following maintenance package: | release\fix pack\interim fix for Release 7.6.0.8 of Base Services
Temporary fix
Comments
APAR Information
APAR number
IV95422
Reported component name
MAXIMO SCHEDULE
Reported component ID
5724R46SE
Reported release
752
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-25
Closed date
2017-05-03
Last modified date
2017-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MAXIMO SCHEDULE
Fixed component ID
5724R46SE
Applicable component levels
R752 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"752","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
03 May 2017