Forum Discussion

TTO's avatar
TTO
Experienced Cover User
4 years ago
Solved

Negative stock values - RECURRING fault with MYOB

a)  there doesnt appear to be an inventory related topic to choose from here?   b).  I have an inventory issue.   c)  this is a RECURRING and never resolved problem with Accountright.  I move a l...
  • Steven_M's avatar
    Steven_M
    4 years ago

    Hi TTO 

     

    Thank you for confirming that information

     

    I've sent you a direct email with all the details in regards to getting that file sent in for an investigation and possible repair. All the information required is included in the email but do let us know if you have any questions about the process.

Steven_M's avatar
Steven_M
Former Staff

Hi TTO 

 

I've arranged for those scripts to be run again over that company file ID 17 as requested. Do ensure that you close down and reopen the company file for those changes to be fully applied.

TTO's avatar
TTO
Experienced Cover User
4 years ago

Hi again Steven_M 

 

Still not fixing some of the stock.   

 

If, when I 'open' the stock item to look at its details, the stock with the corrupted o/hand number, displays "0" as the stock on hand in the detail area.  Can't a "mask" be put over the display in the Items List Inventoried page that says if it's < zero, display zero?  It shows up as zero in print reports and in the item detail.

 

TTO

  • Steven_M's avatar
    Steven_M
    Former Staff
    4 years ago

    Hi TTO 

     

    So we can investigate in more detail would you mind providing additional information into what you can see. For example a screenshot of the Item list and one of the Item's Profile tab.

    • TTO's avatar
      TTO
      Experienced Cover User
      4 years ago

      Hi Steven_M 

       

      2 screenshots attached.    Every day during harvest and distillation, we produce tea tree oil.  It will always have a little water left in it.  We let the oil cool in a big tank and remove the water.  This changes the quantity of oil we record as actually yielded from any given paddock - information we need to know.   So I reduce the oil quantity by 0.5litres (say) on any given day but  I typically accumulate all the water over the season and then put it back to zero.  Usually the water quantity doesn't give me any problem but after the last harvest it just wouldn't go back to zero, showing me the corrupted number instead.  I have 3 other stock items remaining in a similar state.  All show zero when I open the stock item or print a report.  Sigh.

       

      TTO

      • The_Doc's avatar
        The_Doc
        Ultimate Partner
        4 years ago

        Hi TTO 

         

        As mentioned in a prior post I believe this problem is not easy to fix and that running a script over the inventory to zero items that are not EXACTLY ( double precision) zero - to zero.

         

        Here is the problem that appears to be the root of it - and from your perspective - hard to fix.

         

        And this problem reared its ugly head to confound me with the API - where I was comparing website quantities (for an e-commerce live site) with the backend definitive quantity (a live MYOB perpetual inventory file).

         

        To ensure quantities on the website matched actual available I always checked every 30mins during the day (as there was a built in rounding for cutting) that any order ALWAYS rounded to the next 0.25 length - therefore ensuring there was always a bit over for loss during cutting.

         

        i.e. the web showed 2.5 lengths - and MYOB showed 2.5 lengths - and order came through for 0.4 lengths - the web now shows 2.1 lengths left - the order is rounded to 0.5 - POSTED to MYOB - MYOB now shows 2.0 lenfths in stock - web is updated to available 2.0. (not 2.1)

         

        All well and good EXCEPT - MYOB quantity (in the backend is stored as double precision) however it is displayed as (single precision) - to explain 2.00 shows in the inventory window Quantity on Hand but in reality in the backend 2.00 (single precision) becomes 2.00xxxxxxxxxxxxxxxxxxx rounded in double precision - i.e it is never EXACTLY zero.

         

        The problem with mixing and matching in science and maths with double and single precision - except in the computer - single precision is cheaper to store than double precision - and if you don't need double don't use it.

         

        However, MYOB needs it in allowing up to 6 decimal places in prices - so it comes around and bites them in the rear end.

         

        And by the way - that doesn't work in the API POST of an invoice - there is a bug - and you can only get 1 to 2.

         

        Anyway - that is the explanation - simply - but until I corrected in my code for this - my system constantly thought every web item 1500 was different from MYOB - my API would get the qunatity on hand from MYOB before the comparision (but it was in double precision) - and it just never was right.

         

        Here is the other twist (depending on the CPU and mathematics component) the double precision value can vary.

        i.e. quantity of item (NOW) in double precision is slightly different to (NOW) + time a bit!!!!!

         

        So it is almost impossible to get to ZERO.

         

        My cure - very simple - always download Quantity on Hand as Single precision - problem was cured instantly and never went wrong again.

         

        For you - the problem is you cannot do what I have done - the problem is hard wired.

        The script just cleans up these errors - today - but they recur.

         

        Sorry for the long winded explanation.

         

        The Doc