IBM Support

IJ51020: PM WORK ORDERS GENERATED FROM NESTED JOB PLANS IN JOB PLAN SEQUENCE POPULATE WITH INCORRECT DESCRIPTIONS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • ABSTRACT:
    PM Work Orders Generated From Nested Job Plans In Job Plan
    Sequence Populate With Incorrect Descriptions
    
    DESCRIPTION:
    When a Nested Job Plan is used to generate a Work Order in a Job
    Plan Sequence scheme, the Work Order Description populates with
    the first Task Description of the Nested Job Plan instead of the
    Description from the Nested Job Plan.
    
    Support Engineer reproduced this on lab environment and with
    customer on customer environment
    Lab environment: http://mx2-docker.fyre.ibm.com:9090/maximo/web
    client/login/login.jsp
    7.6.1.3-IFIX20240227-1651
    
    Support Engineer collected log from customer environment during
    web meeting when issue was reproduced;
    dec0609maxap04_MAXUI1_sql.log
    Peer-reviewed by Maximo Applications support team
    
    STEPS TO REPRODUCE:
    1. Log in to maxdemo instance
    2. Go To Planning | Job Plans
    3. Common Actions | New Job Plan
    4. Enter values:
    	Job Plan: MO-001
    	Description: "Monthly Job Plan"
    	Template Type: Maintenance
    	Duration: 8.00
    	Include Tasks in Schedule: checked
    	Tasks: (no Sequence values)
    		1 Monthly Task 1
    		2 Monthly Task 2
    	Labor tab:
    		Craft: ELECT "Electrician - 1st Class"
    		Quantity: 1
    		Hours: 2.00
    5. Save the record
    6. Common Actions | Change Status
    7. In the New Status field, select Active, then click OK
    8. Repeat the steps to create two more Job Plans:
    	Job Plan: QTY-003
    	Description: Quarterly Job Plan"
    	Template Type: Maintenance
    	Duration: 8.00
    	Include Tasks in Schedule checked
    	Tasks: (no Sequence values)
    		1 "Quarterly Task 1"
    		2 "Quarterly Task 2"
    		3 "Quarterly Task 3 w Nested Job Plan MO-001"
    			Nested Job Plan: MO-001
    	Labor tab:
    		Craft: ELECT "Electrician - 1st Class"
    		Quantity: 1
    		Hours: 4.00
    
    	Job Plan: SA-006
    	Description: "Semi Annual Job Plan"
    	Template Type: Maintenance
    	Duration: 8.00
    	Include Tasks in Schedule checked
    	Tasks: (no Sequence values)
    		1 "Semi Annual Task 1"
    		2 "Semi Annual Task 2"
    		3 "Semi Annual Task 3 w Nested Job Plan QTY-003"
    			Nested Job Plan: QTY-003
    	Labor tab:
    		Craft: ELECT "Electrician - 1st Class"
    		Quantity: 1
    		Hours: 0.00
    9. Go To Preventive Maintenance | Preventive Maintenance
    10. Common Actions | New PM
    11. Enter values:
    	PM: P-001
    	Description: "Nested Job Plan Description Test"
    	Asset: 13144 *change the Asset Status to Operating if necessary
    
    	Work Type: PM
    	Work Order Status: APPR
    	Frequency tab:
    		Use Last Work Order's Start Date to Calculate Next Due Date?:
    checked
    		Frequency: 1
    		Frequency Units: MONTHS
    		Estimated Next Due Date: 2 days ago
    	Job Plan Sequence tab:
    		MO-001 Sequence: 1
    		QTY-003 Sequence: 3
    		SA-006 Sequence: 6
    12. Save the record
    13. Common Actions | Change Status
    14. In the New Status field, select Active, then click OK
    15. More Actions | Generate Work Orders
    16. Click OK at the System Message similar to, "BMXAA3208I - PM
    P-001 created work order B1458."
    17. Repeat the Generate Work Orders action 5 more times (uncheck
    the "Use Frequency Criteria?" option each time) so that the PM
    Counter updates to 6
    18. Note the Work Order number that gets generated on the 6th
    iteration (the Semi Annual sequence)
    19. Go To Work Orders | Work Order Tracking
    20. Open the Work Order that was generated on the 6th iteration
    21. On the Plans tab | Children of Work Order section | view the
    Summary field value for the row (Record Class = WORKORDER)
    
    RESULT:
    The Work Order Description is "Semi Annual Task 1"; this is the
    Description from the Job Plan's first task.
    
    EXPECTED RESULT:
    The Work Order Description should be "Semi Annual Task 3 w
    Nested Job Plan QTY-003" The expected result is that the child
    Work Order that gets generated from the PM will take its
    Description from the Job Plan Task that contains the Nested Job
    Plan.
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.3-IFIX20240227-1651
    Build 20220823-0909
    
    LOCAL WORKAROUND:
    none
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * PM WORK ORDERS GENERATED FROM NESTED JOB PLANS IN JOB PLAN   *
    * SEQUENCE POPULATE WITH INCORRECT DESCRIPTIONS                *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR will be contained in future release
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ51020

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-29

  • Closed date

    2024-06-12

  • Last modified date

    2024-06-12

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
12 June 2024