IBM Support

IJ04115: CLEARANCES, TEMP LIFTS: TEMP LIFT DOES NOT MOVE TO COMP STATUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Temp Lifts: Temp Lift does not move to COMP status
    
    Description:
    Temp Lift should move automatically from REAPPLY to COMP when
    all tag actions are completed
    
    Maxvars:
    Automatically share tags during Shift Supervisor approval
    Use CL Groups = Yes
    Tag Seq Num Unique = No
    Allow IV changed on DRAFT status = Yes
    Set to Automatically transfer tags prior to operations approval
    APPR to READY manually when all tagging actions are complete
    Multiple CL for a WO = Yes
    Test Tags: Prevent Multiple Tags = T
    Caution Tags: compatible with Danger, Test, Grounding, and No
    tags.
    
    Steps to Reproduce:
    1. Create Clearance 2001A, CL Group A, with tags on TEST_E1 and
    TEST_E2, and related WO 2201.  Promote to ACTIVE, status.
    2. Revise CL 2001A, add a tag on TEST_E3, and promote Rev 1
    READY status.  Issue Revised Clearance.  Promote CL 2001A Rev 1
    to ACTIVE status.
    3. Create Clearance 2002, CL Group A, with a tag on TEST_E2,
    and related WO 2202.  Promote the clearance to APPR status, and
    SHARE the tag on TEST_E2.  Promote CL 2002 to ACTIVE status.
    4. Create CL 2003, CL Group B, with a tag on TEST_E2, and
    related WO 2203.  Promote CL 1003 to ACTIVE status.  Tag on
    TEST_E2 does not share since it is in a different CL Group. 5.1
    (CL 2001A Rev 1 in ACTIVE, CL 2002 in ACTIVE, CL 2003 in
    ACTIVE); CL 2001A Rev 1 TL 10 in DRAFT above, Location TEST_E2
    below. 5.1
    5.1 On CL 2001A Rev 1, create TL 10.  Select the Shared tag
    1036 on TEST_E2 for LIFT.  Add a TEST tag 1039 on TEST_E2.
    Click the Link Affected Clearances button, and the SHARED tag
    1036 on CL 2002 is selected, as well as the independent tag
    1038 on CL 2001 is selected.  Click OK.
    5.2 Promote TL 10 to WAPPR status.  Do not interrupt work.
    Navigate to WOs 2201, 2202, and 2203, Sign Off Labor on all the
    WOs.  Perform Accept Boundary Revision on all WOs.
    5.3 Bypass the problem by Releasing the WOs from the CLs and TL
    10 by signing Work Complete on WOs 2201, 2202, and 2203.
    5.4 Promote TL 10 to APPR.
    5.5 Promote tags 1036 and 1038 to TEMPLIFT status, then promote
    tag 1039 to TEMPADD status.
    5.6 Promote TL 10 to READY.
    5.7 Promote TL 10 to REAPPLY status.  No tagging activities
    performed yet.
    5.8  On CL 2001A Rev 1 TL 10 in REAPPLY above, open the Temp
    Lift Tagging Activities dialog.  Take shared tag 1036 from
    TEMPLIFT to APPLIED and Test tag 1039 from TEMPADD to RESTORED.
     Click OK and close the Tagging Activities dialog.
    5.9  On TL 10 in REAPPLY status, reopen the Tagging Activities
    dialog and take tag 1038 from TEMPLIFT to RESTORED.  TL 10
    should move automatically from REAPPLY to COMP when the tag
    action is completed, however stays in REAPPLY.
    
    
    Expected Result:
    TL 10 should move automatically from REAPPLY to COMP when the
    tag action is completed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All user from Maximo for Nuclear Power                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * TEMP LIFT DOES NOT MOVE TO COMP STATUS                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • a fix was provided.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ04115

  • Reported component name

    MAXIMO FOR NUCL

  • Reported component ID

    5724R5300

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-14

  • Closed date

    2018-03-07

  • Last modified date

    2024-10-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 FOR NUCL

  • Fixed component ID

    5724R5300

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLL8M","label":"Maximo for Nuclear Power"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 October 2024