IBM Support

IV91694: ASSET COSTS ROLLUP ARE NOT CALCULATED CORRECTLY - MATERIAL COSTSDOUBLED IN REPORT OUTPUT - 7604

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Asset costs are not calculated correct in Asset application.
    Total Cost
    in Asset is not similar to sum of total cost of all connected
    workorder
    with that Asset. The filed Total cost in Asset application is
    updated
    by report.
    
    
    
    Replication Steps :
    
    The following steps are basic test plan steps to run the asset
    cost rollup report:
    ===
       Create 2 new work order records
    1. Create 2 new Work Orders for an Asset (which does not have a
    parent.  In this example, I'll call this Asset A123)
    2. Report actual Labor, Material, Tool and Service costs to
    these 2 Work Orders.
    3. Approve the labor transaction costs.
    4. Complete and close the work orders.
    
    Note the labor, material, tool and service costs for A123 for
    each work order, along with the total of all costs.   Call the
    total Value, A123 Total.
    
    Assign A123 to a parent Asset
    4. In Assets > Assets, filter for asset A123
    5. Go to the 'Select Action' menu and select 'Move/Modify
    Assets'.
    6.  Select another asset to be the parent of A123.   In this
    example, I'll use A123P as the parent of A123
      *Pick an asset that does not have any other children for this
    exercise only.
    7. Click on 'OK' button.  The 'Move/Modify Assets' window
    closes.
               Asset A123P  appears in the 'Parent' field in the
    Details section for Asset A123.
    
    Run Maintenance Cost Rollup report
    8.  In Assets > Assets, filter to find all records.
    9.  Go to the 'Select Action' menu and select 'Run Reports'.
    10.  Select the Maintenance (Asset) Cost Rollup report
    11. Click on the 'Submit' button.  Report is generated and
    displayed.   Print the report.
    
    Validate results for Asset123
    12.  Locate Asset A123 within the report.  Validate that the
    field 'New YTD Costs' is the same as A123 Total from Step 4
    above.
    
    13.   Look at the New Labor, New Material, New Services and New
    Tool Costs in the report..  Validate that those fields are the
    totals for A123 (of the 2 work orders)  from Step 4 above.
    
    14.  Look at the New Total Cost field in the report.  Validate
    that it is equal to the New YTD cost + Previous YTD Cost (the
    previous YTD cost is an existing value from the database
    ASSET.YTDCOST)
    
    
    Validate results for Asset123P
    
    15.  Locate Asset A123P within the report.  Validate that the
    field 'New YTD Costs' is the same as Asset A123 as it inherits
    the costs from its child asset.
    
    Repeat steps 13 and 14 above.
    
    Run Maintenance Cost Rollup Update report
    16.  In Assets > Assets, filter to find all records.
    17.  Go to the 'Select Action' menu and select 'Run Reports'.
    18.  Select the Maintenance (Asset) Cost Rollup Update report.
    19. Click on the 'Submit' button.  When the report is generated
    - click the update button on the bottom.
    
    This will take the total costs of the assets (that were
    validated in steps 12-15 above) and change their database values
    of ASSET.YTDCOST and ASSET.TOTALCOST
    
    It will also set the individual actual transaction records from
    rolledup = 0 to rolledup = 1
    LABTRANS.ROLLUP: Set to 1
    MATUSETRANS.ROLLUP: Set to 1
    TOOLTRANS.ROLLUP: Set to 1
    SERVRECTRANS.ROLLUP: Set to 1
    
    
    Run Maintenance Cost Rollup report - New YTD Cost and New Total
    Costs at 0
    20.  In Assets > Assets, filter to find all records.
    21.  Go to the 'Select Action' menu and select 'Run Reports'.
    22.  Select the Maintenance (Asset) Cost Rollup report.
    23. Click on the 'Submit' button.  Print the report
    
    Validate that the New YTD Cost, New Total Cost, New Labor, New
    Material, New Services and New Tool Costs for Assets A123 and
    A123P are 0.
    
    They are set to 0 because the costs have been previously rolled
    up and accounted for in step 19.
    ===
    
    In the client's case the material costs are getting doubled.
    IBM Support has reviewed and determined that there is an issue
    from the SQl query of the report. It is not joining the work
    order on site-id.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maintenance Cost Rollup Reports                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * invalid join from transaction tables to work order table     *
    * caused invalid cost aggregate.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Import that latest report designs for Maintenance Cost       *
    * Rollup and Maintenance Cost Rollup Update reports.           *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IV91694

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    760

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-23

  • Closed date

    2017-01-04

  • Last modified date

    2017-01-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSCHPL3","label":"Assets"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":""}]

Document Information

Modified date:
04 January 2017