MYOBCommunity
Partner Zone
|
|
Partner Zone

Inventory value less than zero - that old chestnut!!

1 REPLY
Experienced Partner John_Dinning
26 Posts
Experienced Partner
Australia
John_Dinning
Experienced Partner

26Posts

0Kudos

3Solutions

Re: Inventory value less than zero - that old chestnut!!

With the help of MYOB API support, I have some answers to my questions so thought I would post them here:

 

The 9603 and 4059 errors are caused by the item being 'out of balance'. See this link for more information:

http://help.myob.com/wiki/display/ar/Error%3A+Non-zero+value

If the solution given there does not fix it, it may require the MYOB support team to correct the data.

 

Currently, if a batch of Inventory Adjustments fails there is no way of knowing which item in the batch caused the exception. I have asked that they consider changing this in future. A workaround it just to process them one item at a time.

Experienced Partner John_Dinning
26 Posts
Experienced Partner
Australia
John_Dinning
Experienced Partner

26Posts

0Kudos

3Solutions

Inventory value less than zero - that old chestnut!!

Using AccountRight 2018.2 and the latest version of the SDK.

I am getting exceptions when posting a batch of Inventory Adjustments. (InventoryAdjustmentService.Insert)

 

ErrorCode: 9603   Message: CurrentValue of Item must be reduced to zero when QuantityOnHand of Item is reduced to zero   Name CurrentValueOfItemNotZero

and 

ErrorCode:4059   Message: Inventory_ValueMustNotLessThanZero   Name ValidationError

 

These are caused by what I believe to be a bug in AccountRight but more on that later.

 

My problem is that I cannot tell which item(s) within the batch are causing the problem, and the whole batch is failing.

Is there a way of finding out from the exception, or by any other method,  which item is causing the problem? 

 

 

The underlying problem is caused when trying to reduce the stock on hand quantity to zero.

My theory is that AR tries to adjust the value of the stock using the average cost which it calculates based on previous purchase prices.

Somehow this may be different from what it calculates is the total value of the adjustment so the resulting total value is not zero.

 

I can reproduce this problem in AR itself. I have an item which has be bought and sold several times at different prIces and I cannot adjust the quantity to zero.

This may be just a rounding issue as in my example in Inventory Adjustment, AR displays the 'Unit Cost' as $208.579999 and the 'Amount' as -$208.58.

Adding those two values would not give zero, unless the underlying values were rounded to the same number of decimal places.

 

Any thoughts or suggestions welcome.

 

Didn't find your answer here?
Try using advanced search to find a post more easily Advanced Search
or
Get the conversation started and make a new post Start a Post