IBM Support

IJ47730: UNIT COST VALUE DOESN'T GET CHANGED, WHEN QUANTITY IS REVISED IN INVOICE APPLICATION.

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

  • Description:
    Revising the Quantity value to the original value (as on PO) in
    the Invoice application does not change the Unit Cost value.
    
    STEPS TO REPRODUCE:
    ==================
    1)Login to Maximo Application.
    2)Go to Purchasing >Purchase Order Application.
    3)Create the NEW PO(1213). In Vendor Section specify the company
    
    name and save it.
    4)Go to PO Lines Tab, Click on NEW ROW and select the ITEM
    Value.
    5)In Quantity and Costs section add storeroom value.
    6)Then mentioned the value for quantity, Order UNIT, UNIT COST
    after that Save it then Approve the PO.
    7)Go to Purchasing Application> Invoices and create the New
    Invoices i.e 1081
    8)In Invoice Section, Filter the PO number i.e 1213 which
    created earlier
    9)Click on Invoice Lines Tab, click on Copy PO Lines (It will
    show the same PO number)
    10)Select the PO Number and expand it.
    11)Check all values in the Quantity and Costs section are
    correct i.e previous one which was created for PO.
    12)Now change the value for Unit Cost field. Line Cost, Tax, and
    
    Loaded Cost fields are updated automatically.
    13)After that, Change the value for Quantity and save it.
    14)Then please revert the changes for Quantity to original value
    
    as on the PO.
    15)It appears Unit cost value is showing the new one, it doesn't
    
    revert to previous Unit Cost Value which was created for PO.
    
    RESULT:
    Unit Cost value doesn't change or revert to previous one in
    Purchase Order Application
    
    
    EXPECTED RESULT:
    Unit Cost value should be reverted to previous one which was
    created for the Purchase Order.
    
    
    REPORTED IN VERSION:
    Tivoli's Process Automation Engine 7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UNIT COST VALUE DOESN'T GET CHANGED, WHEN QUANTITY IS        *
    * REVISED IN INVOICE APPLICATION.                              *
    ****************************************************************
    When the InvoiceLine quantity is revised and the invoiceLine
    quantity is the same as the POLine quantity then we set the Line
    cost value (also loaded cost and tax) as per POLine values but
    the unit cost is not updated.
    

Problem conclusion

  • This will be fixed in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ47730

  • 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-07-28

  • Closed date

    2024-04-11

  • Last modified date

    2024-05-13

  • 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":"BU048","label":"IBM Software"},"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:
13 May 2024