IBM Support

IV30407: AS LEFT STATUS NOT CALCULATING CORRECTLY ON A DATASHEET.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • As Left Status Not Calculating Correctly on a datasheet.
    
    Maximo is not calculating the correct  As Left Status  on a
    datasheet.
    If you look at this example(see attachment), it FAILED on line
    30 but
    the overall status is marked as PASS. This is incorrect. The  As
    Left
    Status  should be FAIL.
    
    
    The value to be displayed on the "As Left Status" depends on how
    the
    data was entered and how the tolerances are defined .  If the
    user have
    created a Tolerance that is +/-1 EU and when they enter the As
    Found/As
    Left data it falls outside this range - so it is out of
    tolerance then
    we automatically calculate that as a fail.
    
    
    But client replied this:
    If any asset function has an as found or as left status of FAIL
    the
    overall Data Sheet status should be FAIL.  Any data sheet that
    has
    multiple asset functions must correctly determine the overall
    data sheet
    status taking into account the status of each asset function.
    The
    individual Calibration Point data does not matter in the case,
    it is
    simply the fact that it was outside of the limits for a test
    point.
    
    As per client, when the "as found" is set to PASS does not
    happen.., and
    the "as left status" seems to be updated correctly...
    when the "as found" is set to BROKEN, then the problem happens,
    and the
    "as left status" is not updated correctly  ...
    
    Lisa Stuckless confirmed this is a product defect.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo Users on Calibration                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The As-Left status is not being set correctly when there is  *
    * a broken As-Found status.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fix available in fixpack 7504                                *
    ****************************************************************
    <span>As Left Status Not Calculating Correctly on a
    datasheet.<br/>Maximo is not calculating the correct  As Left
    Status  on a<br/>datasheet.  If you look at this example(see
    attachment), it FAILED on line 30 but the overall status is
    marked as PASS. This is incorrect. The  As Left Status  should
    be FAIL.<br/>The value to be displayed on the &quot;As Left
    Status&quot; depends on how<br/>the data was entered and how the
    tolerances are defined .  If the<br/>user have created a
    Tolerance that is +/-1 EU and when they enter the As Found/As
    Left data it falls outside this range - so it is out
    of<br/>tolerance then we automatically calculate that as a
    fail.<br/>But client replied this: If any asset function has an
    as found or as left status of FAIL the overall Data Sheet status
    should be FAIL.  Any data sheet that has multiple asset
    functions must correctly determine the overall data sheet status
    taking into account the status of each asset function.  <br/>The
    individual Calibration Point data does not matter in the
    case,<br/>it is simply the fact that it was outside of the
    limits for a test point.<br/>As per client, when the &quot;as
    found&quot; is set to PASS does not happen.., and the &quot;as
    left status&quot; seems to be updated correctly... when the
    &quot;as found&quot; is set to BROKEN, then the problem
    happens,<br/>and the &quot;as left status&quot; is not updated
    correctly  ...<br/></span>
    

Problem conclusion

  • <p style="margin: 0in 0in 0pt 0.5in; mso-layout-grid-align:
    none"><span><span>As Left status is not being set
    correctly.<br/><br/>The fix for this APAR is contained in the
    following maintenance package:<br/></span></span></p><p
    style="margin: 0in 0in 0pt 0.5in; mso-layout-grid-align:
    none"><span><span><span>            </span><span> </span>|
    release\fix pack | Interim Fix for Release <span>7.5.0.4 of Base
    Services</span></span><br/></span></p>
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV30407

  • Reported component name

    MAXIMO LIFE SCI

  • Reported component ID

    5724R5200

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-17

  • Closed date

    2012-11-05

  • Last modified date

    2012-11-05

  • 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 LIFE SCI

  • Fixed component ID

    5724R5200

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKZS","label":"Maximo Calibration"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
15 November 2022