Passa al contenuto
Menu
È necessario essere registrati per interagire con la community.
La domanda è stata contrassegnata
1 Rispondi
6499 Visualizzazioni

While importing BoM records in chunks of 1,000, everything was going along swimmingly, until about record 10,000.  At that point, I received this error:

new row for relation "mrp_bom" violates check constraint "mrp_bom_bom_qty_zero" DETAIL: Failing row contains (18480, 1, 2014-07-18 17:53:15.396004, 2014-07-18 17:53:15.396004, 1, null, null, 1, null, null, 0.000, null, 1, t, 0, HDL081, null, 1, null, 29253, 2928, null, normal). at row 33

Looking at my import file, I can't find any difference between the offending record and any others.  There is a non-zero value (0.0004) in the column for quantity required, so I'm thinking that maybe the error is in something that OpenERP is filling in automagically?  Or perhaps there is some sort of rounding applied by OpenERP, and since the value is so small, it considers it zero?

Avatar
Abbandona

Please word your question with more detail - forcing readers to open your question to learn if they can help reduces the chances it will be answered.

What happens when you try to enter this same data via the UI ?

Autore Risposta migliore

It does appear that the value of 0.0004 was rounded to 0.000.  See the 5th value before the part name "HDL081" in the error.  After some googling, I have seen multiple posts that say to to go "Settings-->Technical-->Database-->Decimal Accuracy", but that option wasn't present when I looked.  Turns out that you have to go into the User permissions settings and enable the "Technical Features" option first, then you will be able to set decimal precision. 

Hope this helps someone else with the same problem!

Avatar
Abbandona

There is also a decimal precision on the unit of measure. Not sure if this would have a similar effect on imports.

Post correlati Risposte Visualizzazioni Attività
1
gen 22
3650
1
ott 23
4495
1
gen 20
2962
1
lug 16
3126
0
mar 15
8029