IBM Support

IV87827: INVOICE AUC DISCREPANCY BASED ON WHETHER BUINESS RULE DOES OR DOES NOT CONSIDER STAGEDBAL A PART OF CURBAL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM
    .
    Problem title
    Invoice AUC Issues
    .
    Problem description and business impact
    
    INVOICEMATCH records are not being created correctly in the
    MATRECTRANS table.  When a variance is identified the
    corresponding INVOICEMATCH and MATRECTRANS records were not
    taking into
    account the combination of INVBAL.CURBAL + INVBAL.STAGEDCURBAL
    
    Description:  Invoice AUC PMR testing to identify issues with
    missing INVOICEMATCH/MATRECTRANS records and incorrect
    INVOICETRANS
    records.
    
    Scenario 1 - Price Variance - INVOICEMATCH and MATRECTRANS
    records not being created as not taking into account
    STAGEDCURBAL
    
    1.  Create and approve a PO containing 1 PO line against an ITEM
    in a valid storeroom.  For the test PO's create 1 POLINE
    specifying an ORDERQTY of 10 with a UNITCOST of $10.00.
    
     2. Update the INVCOST and INVBALANCES to amounts of 0
    For that ITEMNUM/STOREROOM combination this can be done via the
    front end using the Select Action  -> Inventory Adjustments  ->
    Average Cost action, set the Average Cost to a value of 0 and
    press the
    OK button.
    
    Maximo Screenshot of Average Cost Adjustment dialog:
    https://ecurep.mainz.de.ibm.com/rest/download/23958%2C442%2C000/
    mail20160527-162755-Winn_Donna_C/PPM_31656_-_Invoice_AUC_testing
    .docx
    
    3.  Perform and complete receiving all amounts for the POLINE
    created in step 1.  This should update the INVBALANCES.CURBAL to
    the
    POLINE.ORDERQTY specified in step 1.  This should also update
    the INVCOST.AVGCOST to match the POLINE.UNITCOST specified in
    step
    1.
    
    4.  Reset the current inventory balance to be less than the
    amount that will be invoiced.
    This is done by using the Inventory application for the
    ITEMNUM/STOREROOM combination to set the INVBALANCES.CURBAL to a
    value of 5 by using the Select Action  ->  Inventory Adjustment
    ->
    Current Balance action and setting the New Balance to a value of
    5, the
    Adjustment Reason to QUANTITY, a valid Shrinkage Account, an
    appropriate Remark, and press the OK button.
    Now using the Inventory Usage application press the New
    Inventory Usage button, specify a value of 11900 for the From
    Storeroom, press
    the New Button in the Usage Lines section, enter an Item value
    of
    116975, enter a Transaction Type value of Issue, enter a From
    Bin value of
    NONE, enter a Bin value of NONE, enter a valid GL Debit Account,
    enter
    a Quantity value of 5, press the Save button, press the Change
    Status button, enter a value of STAGED, select the  "Use current
    bin"
    radio button, and press the OK button.
    
    Maximo Inventory and Inventory Usage Screenshots:
    https://ecurep.mainz.de.ibm.com/rest/download/23958%2C442%2C000/
    mail20160527-162755-Winn_Donna_C/PPM_31656_-_Invoice_AUC_testing
    .docx
    
    5.  Create and approve an invoice containing 1 Invoice line
    against the PO created above with the INVOICEQTY of 10 specified
    and the
    UNITCOST of $20.00.  This is not creating a corresponding
    INVOICEMATCH or
    MATRECTRANS records for the variance.
    
    RESULTS:
    Run
    
    select invoicenum, invoicelinenum, ponum, polinenum, transdate,
    quantity, linecost, transtype from invoicematch where
    invoicenum='1068'
    
    See client result here:
    https://ecurep.mainz.de.ibm.com/rest/download/23958%2C442%2C000/
    mail20160527-162755-Winn_Donna_C/PPM_31656_-_Invoice_AUC_testing
    .docx
    
    Run
    
    select matrectransid, ponum, issuetype, polinenum, transdate,
    quantity,unitcost, linecost, loadedcost, proratecost,
    totalcurbal,
    qtyoverreceived, costinfo from matrectrans where ponum='1099'
    
    EXPECTED RESULT:
    
    We should be seeing an INVOICEMATCH record created with a
    QUANTITY of 0 and a LINECOST of 100.
    We should be seeing a MATRECTRANS records created with a
    QUANTITY of 0, UNITCOST of 0, and LINECOST of 100.
    
    Scenario 2  - Price Variance  - INVOICETRANS records not
    being created correctly as not taking into account STAGEDCURBAL
    
    1.  Create and approve a PO containing 1 PO line against an ITEM
    in a valid storeroom.  For the test PO, create 1 POLINE
    specifying
    an ORDERQTY of 10 with a UNITCOST of $10.00.
    
    2.  Go to Invenotry and for that ITEMNUM/STOREROOM combination
    go to the Select Action  ->  Inventory Adjustments  -> Average
    Cost
    action, set the Average Cost to a value of 0 and press the OK
    button.
    
    Maximo Screenshot of Average Cost Adjustment dialog:
    https://ecurep.mainz.de.ibm.com/rest/download/23958%2C442%2C000/
    mail20160527-162755-Winn_Donna_C/PPM_31656_-_Invoice_AUC_testing
    .docx
    
    3.  Perform and complete receiving all amounts for the POLINE
    created in step 1.  This should update the INVBALANCES.CURBAL to
    the
    POLINE.ORDERQTY specified in step 1.  This should also update
    the INVCOST.AVGCOST to match the POLINE.UNITCOST specified in
    step
    1.
    
    Run
    select itemnum, location, avgcost, lastcost from invcost where
    itemnum= '52-130' and location='CENTRAL' and siteid='BEDFORD'
    
    select itemnum, location, binnum, curbal, stagedcurbal, orgid
    from invbalances where itemnum in '52-130' and
    location='CENTRAL' and
    siteid='BEDFORD'
    
    
    4.  Reset the current inventory balance to be less than the
    amount that will be invoiced.  This can be done by using the
    Inventory Usage
    application press the New Inventory Usage button, specify a
    value of 11900 for the From Storeroom, press the New Button in
    the Usage
    Lines section, enter an Item value of 116975, enter a
    Transaction Type
    value of Issue, enter a From Bin value of, enter a valid GL
    Debit
    Account, enter a Quantity value of 5, press the Save button,
    press the
    Change Status button, enter a value of STAGED, select the  àÂ
    Use
    current bin àÊ  radio button, and press the OK button.
    
    Maximo Inventory Usage Screenshot:
    https://ecurep.mainz.de.ibm.com/rest/download/23958%2C442%2C000/
    mail20160527-162755-Winn_Donna_C/PPM_31656_-_Invoice_AUC_testing
    .docx
    
    5.  Create and approve an invoice containing 1 Invoice line
    against the PO created above with the INVOICEQTY of 10 specified
    and the
    UNITCOST of $20.00.  This is not creating the corresponding
    INVOICETRANS
    record correctly.
    
    RESULTS:
    Run
    
    select invoicenum, linecost, transtype from invoicetrans where
    invoicenum='1069'
    
    EXPECTED RESULTS:
    We should be seeing an INVOICETRANS record created with a
    LINECOST of 100.
    
    The question is: "Why does Inventory Usage
    allow the Unit Cost to change at the time the Usage Document is
    changed
    from Staged to Complete or Cancelled if the Staged Current
    Balance
    isn't being considered as "Stocked Quantity"?"
     We can't update AUC by a portion of our inventory balances and
    then  create transactions as if the Staged Balance was included
    in
    the  calculation.
    
    There is an accounting issue not being considered arising from
    when we
    1) Stage Quantity at an AUC
    2) Stocked AUC changes (per IBM this is only CURBAL not
    STAGEDCURBAL)
    3) However, when the Usage Document is changed to COMPLETE from
    STAGED
    it takes the current AUC of the storeroom
     a) Note: The current AUC change in the storeroom didn't take
    into  account the Staged Quantity.
    4) Technically, Maximo is including the Staged Balance as part
    of the Stocked Quantity because we issue Staged Quantity out at
    Current
    AUC.
    5) Therefore, if our AUC is overstated/understated because we do
    not factor the Staged Current Balance as "Stocked Quantity" Per
    IBM,
    it doesn't make sense to complete or cancel a usage document and
    have the Unit Cost updated to the current AUC.  We
     are creating dollars via the linecosts.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users using Invoice application                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * INVOICE AUC DISCREPANCY BASED ON WHETHER BUINESS RULE  DOES  *
    * OR DOES NOT CONSIDER STAGEDBAL A PART OF CURBAL              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply Release 7.5.0.11 of Base Services or request an        *
    * Interim Fix                                                  *
    ****************************************************************
    

Problem conclusion

  • The staged balance was not being used in the calculation of the
    inventory current balance.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV87827

  • Reported component name

    PURCHASING

  • Reported component ID

    5724R46PU

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-11

  • Closed date

    2016-08-24

  • Last modified date

    2016-08-24

  • 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

    PURCHASING

  • Fixed component ID

    5724R46PU

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPN3","label":"Purchase Requisitions"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 August 2016