IJ35980: PRCOST CALCULATES VALUES DIFFERENTLY DEPENDING ON THE ORDER VALUES ARE FILLED IN ON SCREEN

APAR status

• Closed as program error.

Error description

• The PRCOST table has different values than the PRLINE table when
  the order that the fields are entered is from bottom to top.
  Create a PR with two service lines, both lines will have a
  quantity of 100, Unit Cost of $10 each, for a total line cost of
  $1000.
  After saving, query the PRLINE and PRCOST table to see different
  values.
  
  Go to Purchase Requisitions and insert new record
  Go to PR Lines tab and click New Row,
  (perform the folowing in this specific order)
  Change Line Type to Service, Item Description=test
  Click in field Quantity and delete value
  Click in field Order Unit and type EACH
  Click in Line COst fields and type in 1000.00
  Click in Unit Cost Field and type in 10 and tab out
  Click New Row again
  (perform the folowing in this specific order)
  Change Line Type to Service, Item Description=test
  Click in field Quantity and type 100
  Click in field Order Unit and type EACH
  Click in Unit Cost fields and type in 10.00
  Tab out and the Line Cost field updates automatically to 1000.00
  Save record
  
  Log in to a query tool and execute the following statements:
  
  Select orgid,siteid,prnum,prlineid,quantity,linecost,loadedcost
  from prcost where prnum='prnum_above':
  
  Select orgid,siteid,prnum,prlineid,orderqty,linecost,loadedcost
  from prline where prnum='prnum_above':
  
  RESULTS
  
  PRCOST (QUANTITY) and PRLINE (ORDERQTY) have different values
  due to
  the order the fields were filled out
  
  Return to the pr in question in the UI and look at the prlines,
  the values showing on screen are different than the values in
  the database
  
  EXPECTED RESUTLS:
  The values should be consistent regardless of the order in which
  the fields were entered
  Request:
  To correct this problem, the auto-calculated quantity value
  needs to be passed to the PR Cost table.
  
  
  Reported Version:
  
  Tivoli's process automation engine 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PRLINE.ORDERQTY and POCOST.QUANTITY differ when LINECOST     *
  * entered first.                                               *
  ****************************************************************
  PRCOST.QUANTITY differs from PRLINE.ORDERQTY when
  the order that the fields are entered is from bottom to top. 1.
  Go to Purchase Requisitions and insert new record.
  2. Go to PR Lines tab and click New Row,
  (perform the folowing in this specific order)
  3. Change Line Type to Service, Item Description=test
  4. Click in field Quantity and delete value
  5. Click in field Order Unit and type EACH
  6. Click in Line COst fields and type in 1000.00
  7. Click in Unit Cost Field and type in 10 and tab out.
  8. Click New Row again
  (perform the folowing in this specific order)
  9. Change Line Type to Service, Item Description=test
  10. Click in field Quantity and type 100
  11. Click in field Order Unit and type EACH
  12. Click in Unit Cost fields and type in 10.00
  13. Tab out and the Line Cost field updates automatically to
  1000.00
  14. Save record
  15. Log in to a query tool and execute the following
  statements:
  Select orgid,siteid,prnum,prlineid,quantity,linecost,loadedcost
  from prcost where prnum='prnum_above':
  Select orgid,siteid,prnum,prlineid,orderqty,linecost,loadedcost
  from prline where prnum='prnum_above':
  RESULTS:
  PRCOST.QUANTITY and PRLINE.ORDERQTY have different values due to
  the order the fields were filled out.
  EXPECTED RESULTS:
  The values should be consistent regardless of the order in which
  the fields were entered. To correct this problem, the
  auto-calculated quantity value needs to be passed to the PR Cost
  table.
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: Release 7.6.1.3 of Base Services
  

Temporary fix

Comments

APAR Information

• 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