IBM Support

IJ14763: COMMITTING IN GRAPHICAL SCHEDULING THE WORKORDER.CHANGEBY IS THE CREATED BY VALUE IN THE SCHEDULE, NOT THE USER WHO COMMIT

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

  • In Graphical Scheduling (GS) when the Schedule is committed by
    a user other than the one who created the Schedule the
    WORKORDER.CHANGEBY is the Created By value in the Schedule, not
    the user who did the Commit.
    
    Steps to reproduce:
    1. Create a Schedule with at least one work order in it.
    2. Give another user permission to Commit via Manage Commit
    Access.
    3. Log out of Maximo and log in as the user from step 2.
    4. Move the work order and commit the Schedule.
    5. As Changeby is not visible on WOTrack out of the box, run
    this select against the database:
    SELECT wonum, changeby, SCHEDSTART FROM WORKORDER WHERE wonum
    LIKE 'the wonums used' ORDER BY WONUM
    
    RESULT:
    The Scheduled Start/Finish dates are updated on the Work Order
    (as expected/desired).   WORKORDER.CHANGEBY is the value of the
    user in step 1 who created the Schedule, NOT the user who
    committed the Schedule.   The same is true when Commit Selected
    Records is used.
    
    Note: changing the status of a workorder from Scheduler DOES
    set the CHANGEBY correctly.
    
    EXPECTED RESULT:
    That Changeby be set to the user who did the Commit, not the
    one who created the Schedule
    
    VERSION INFORMATION:
    Reproduced in pre-GA 7611 Build 20190312.
    Reported in 7609.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * maximo scheduler users                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In Graphical Scheduling (GS) when the Schedule is committed  *
    * by                                                           *
    * a user other than the one who created the Schedule the       *
    * WORKORDER.CHANGEBY is the Created By value in the Schedule,  *
    * not                                                          *
    * the user who did the Commit.                                 *
    ****************************************************************
    * 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.1.1 of Base
    Services(Scheduler 7673)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ14763

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    767

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-15

  • Closed date

    2019-03-29

  • Last modified date

    2019-03-29

  • 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

  • R767 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":"767","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
29 March 2019