IBM Support

IJ49119: EPTRANS.DEPAMT WRONGLY CALCULATED WHEN ASSET DEPSCHED.STARTDATE IS NOT THE END OF THE PERIOD

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

  • Problem:
    We found out that the Depreciation Amount (DEPTRANS.DEPAMT) is
    wrongly calculated when the asset start date
    (DEPSCHED.STARTDATE) is not the First or Last day of the month.
    
    Steps to Reproduce:
    
    1. Go to asset
    2. Select any asset
    3. In more actions select Manage Depreciation Schedules
    4. Fill the following data:
    - Starting cost: 1,000,000
    - Salvage amount: 0
    5. In the definition add a new row and fill the following data
    - Method: SL (lineal)
    - Period Type: DATE
    - Periods: 8 (in order for the cron task to complete the full
    depreciation schedule up today)
    - Ratio: 100
    - Check both, Financiala and Create GL Transactions
    6. On the Date Period section fill the following:
    - Units: MONTHS
    - Calculation day: LAST
    - Start Date: Jan 30th 2023 (note that is one day before LAST
    day of the month)
    7. click OK.
    
    Results:
    Wrong value being displayed in depreciation amount as it is
    greater then the start cost of the asset. Depreciation amount is
    showing the total depreciation (the accumulated depreciation)
    instead of the actual amount
    
    Expected Results:
    The actual depreciation amount should be displayed correctly.
    
    
    Reported In Version:
    Tivoli's process automation engine 7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DEPTRANS.DEPAMT WRONGLY CALCULATED WHEN ASSET                *
    * DEPSCHED.STARTDATE IS NOT THE END OF THE PERIOD              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ49119

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-11-07

  • Closed date

    2023-12-29

  • Last modified date

    2023-12-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 ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

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

Document Information

Modified date:
29 December 2023