Skip to main content
Solved

Error in register purchase order arrival

  • August 18, 2025
  • 7 replies
  • 112 views

Forum|alt.badge.img+7

Not allowing to GRN (Purchase Order Arrival) an Inventory part due to the error 

“The value of the inventory transaction may not be 0 for part”

But there is a value in the purchase order line. 

I tried changing Misc part info to “Zero Cost Allowed” then the ARRIVAL got created with 0 value in the inventory transaction history. 

Best answer by Kavindu911

The issue is sorted now. 
 

We have been able to get the issue rectified. 

 

Found that the issue was due to a failed background job "Copy Costs To Cost Set One" which occurred due to the insufficient table space in the Database.

 

After increasing the tablespace, we were able to run the background job.

7 replies

Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 16 replies
  • August 18, 2025

 


Forum|alt.badge.img+11

Hi ​@Kavindu911, please check whether the Cost Element is missing for the Cost Bucket 110 in Cost Bucket screen. Thanks.


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 16 replies
  • August 18, 2025

Hi Ravinatha,

 

Its available.
 

 


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 16 replies
  • August 18, 2025

Also identified that, there is no Accounting available when we do the GRN by changing the inventory part to Zero cost allowed. 

 

 


Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 48 replies
  • August 18, 2025

What value do you have in this screen below? It sounds like the part in question is setup under standard costing and there is no value below. A cost roll-up may need to be performed as well.

 

 

 


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 16 replies
  • August 19, 2025

Hi 
 

 


Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • 16 replies
  • Answer
  • August 19, 2025

The issue is sorted now. 
 

We have been able to get the issue rectified. 

 

Found that the issue was due to a failed background job "Copy Costs To Cost Set One" which occurred due to the insufficient table space in the Database.

 

After increasing the tablespace, we were able to run the background job.