处理物料接收和发票中的数据精度

snow.lovers

Go to Db config,将下述字段长度和精度分别设为13和5
do a search for attribute UNITCOST with type DECIMAL
set the fields below to 13 with scale 5
POLINE.RECEIVEDUNITCOST
POLINE.UNITCOST
MATRECTRANS.CURRENCYORDERUNITCOST
MATRECTRANS.INVOICEMATUNITCOST
MATRECTRANS.POUNITCOST
MATRECTRANS.CURRENCYUNITCOST
INVOICELINE.UNITCOST
INVOICECOST.UNITCOST
Leave other costs fields in poline, matrectrans, matusetrans, invoiceline, invoicecost of DECIMAL type to a scale of 2 (out of the box maxdemo has the DECIMAL defaulted to 10,2)
stop app server. Run DBConfig
Create PO 1070, vendor is ATI
Make sure PAYONRECEIPT flag is false
with a line item 560-00 of qty 1, unitcost .25567
tab out of the unitcost field, linecost is rounded to .26
conversion faction is 1, storeroom CENTRAL, no tax
save and Approve PO
go to receiving app
click select ordered item button
select the poline, save. receipt status is now COMPLETE.
25. query the database as below:

SELECT UNITCOST FROM MATRECTRANS WHERE PONUM=\'1070\';

output is .00128

SELECT RECEIVEDUNITCOST FROM POLINE WHERE PONUM = \'1070\';

output:
RECEIVEDUNITCOST
----------------
.26

Create Invoice 1053 for PO 1070, copy poline to it. invoice unitcost is 0.26000

NOTE: Maximo should not be rounding the unit cost in step 25 and 26


There is a Hotfix available for this Issue which requires changing the matrectrans.unitcost to 13,5 via the back end. Please contact Maximo Support to get more information.

snow.lovers

偶试了一下上面的方法，觉得说的好像不是很正确，但是告诉大家可以采用这种方法来处理实施中遇见的数据精度问题

jeffreyqi

学习中。。。。。。。
还限制回复的字数的啊。猛

gjd1981

这样危险性比较高,觉得还是让发票保留两位比较好

gjd1981

楼主能否解释一下