IBM Support

IV96965: WOT - CONSTRAINT - ALLOWS CIRCULAR VALUE TO BE ENTERED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Steps to reproduce:
    
    1.go to Work Order Tracking application and create a Work Orders
     parent/child relationship. (For all work orders following
    fields need to be populated under Work Order tab > Scheduling
    Information:
    Scheduled Start, Scheduled Finish, Duration. The Parent Duration
    should be consistent with Children.
    PH02 parent of PH02-A5015
    PH03 parent of PH03-A5001
    PH05 parent of PH05-A5018
    
    2.create constraints for following work orders:
    PH02-A5015 is predecessor of PH03-A5001 is predecessor of
    PH05-A5018 is
     predecessor of PH03-A5001
    -select PH03-A5001 and on the Work Order tab go to Scheduling
    Information section > Predecessors field
    -click on 'Select More Work Records' and select PH02-A5015 as a
    predecessor
    -select PH05-A5018 and follow steps above to set a PH03-A5001 as
    a predecessor
    -select PH03-A5001 and follow steps above to set PH05-A5018 as a
    predecessor
     The last step should not be allowed as it is circular.
     PH05-A5018 should not be allowed as a predecessor of PH03-A5001
    because PH03-A5001 is already a predecessor of PH05-A5018.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users on 765                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Fix has been made against the algorithm and the process to   *
    * validate circular dependencies.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the fix pack release 7608 iFix                         *
    ****************************************************************
    

Problem conclusion

  • Fix has been made against the algorithm and the process to
    validate circular dependencies. Check and return your feed back.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV96965

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    765

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-07

  • Closed date

    2017-06-21

  • Last modified date

    2017-06-21

  • 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

  • R765 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"765","Edition":""}]

Document Information

Modified date:
21 June 2017