IBM Support

IJ31160: WORK ORDER ORIGINAL DATE AND EXTENDED DATE ARE OVERWRITTEN WHEN WO DEFERRAL IS SET TO ACTIVE

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

  • DESCRIPTION:
    Original date in the Work Order Deferral gets
    overwritten with the Initial Target Start date when a deferral
    is set to active.
    
    
    STEPS TO REPRODUCE:
    1) Create a new WO in
    the WOTRACK(CM) Application; Create New Workorder: 1342;
    (i)
    Set Target Start Date in the past: 01/01/21 09:00; Save
    
    2)
    From More Actions -> Select Deferrals;
    (i) Enter a new
    Deferral by clicking in the new Row; Observe the Original Date
    is set as current date (here - 15/01/21 09:17);
    (ii) Enter
    Type: FLB; Reason: MAINT; Source: MCC; Duration: 10; Extended
    Date is increased to Original date + Duration which is as
    expected (here- 25/01/21 09:17);
    (iii) At this point, Original
    Date is current date; Extended date is 'Original date +
    Duration' and Deferral status is PENDING.
    (iv) Change the
    Deferral Status to ACTIVE; Click Ok
    
    3) Go to Deferrals again;
    
    (i) Note that the original date now displays the Initial
    Target start date.
    (ii) and the Target Start Date (in the Main
    Work Order Tab) is updated with the Extended Date
    
    
    RESULT:
    Original date in the Deferrals is replaced/overwritten with the
    Initial Target Start date. (here- 01/01/21 09:00)
    
    
    EXPECTED
    RESULT: Original date should be the same as it appeared while
    the Deferral status was PENDING. (here- 15/01/21
    09:17)
    
    
    REPORTED IN VERSION:
    IBM Maximo Asset Configuration
    Manager 7.6.7.2
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Maximo Asset Configuration Manager users.            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ORIGINAL DATE AND EXTENDED DATE ARE OVERWRITTEN WHEN WO      *
    * DEFERRAL IS SET TO ACTIVE                                    *
    ****************************************************************
    

Problem conclusion

  • A change in the code was made to fix the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ31160

  • Reported component name

    MX ASSET CONFIG

  • Reported component ID

    5724R4500

  • Reported release

    767

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-04

  • Closed date

    2021-09-24

  • Last modified date

    2021-09-24

  • 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

    MX ASSET CONFIG

  • Fixed component ID

    5724R4500

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKSJ","label":"Maximo Asset Configuration Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"767"}]

Document Information

Modified date:
25 September 2021