What is the best explanation of how OVERDIST (over distribution) tiers that are created using FIFO?

SUGGESTED

I understand how negative OVERDIST tiers occur, but a bit fuzzy on how positive OVERDIST tiers occur.  Is there a good write up that someone has done that explains this process for both myself and my clients?

Parents Reply Children
  • 0 in reply to KrystalB

    Just put 29852 in the search box. Came right up for me.

    Thanks Shelly.  Have wondered about that myself but never got ambitious enough to hunt down the info.

  • 0 in reply to TomTarget

    Hmm. Okay I feel foolish.  It's not coming up for me.  Is there a way to attach a screenshot?  Perhaps I'm doing something wrong.  

  • 0 in reply to KrystalB
    What are positive OVERDIST tiers on the Inventory Valuation Report?



    Products


    Sage 100




    Description


    What are positive OVERDIST tiers on the Inventory Valuation Report?




    Resolution


    The positive OVERDIST tiers are created for FIFO and LIFO items. The tiers are created when either of the following events occur:
    1.When updating a Sales Order credit memo in Sales Order Invoice Data Entry
    2.When updating a Credit Memo generated from Return Merchandise Authorization

    Prior to Business Framework, it would be added to an existing tier. In Business Framework, the system will add to/create an OVERDIST tier. This is done so the return won't add to a receipt tier that had a different receipt date or different cost.




    Category


    Batches, entries, posting




    Entitlement


    Sage 100
  • 0 in reply to KrystalB
    Did you log in before searching? It gives the impression that you don't need to do so, but I don't think the search will find anything if you aren't logged in.
  • 0 in reply to KBatch
    Thanks Tom. :)

    KBatch, I was logged in, but because we use Sage 50 for our sister company and my email address is linked to that, it would not "find" the article for Sage 100. I just got off the phone with tech support and that issue is now solved. I was able to locate KB 29852 right about the time I got the email telling me about these replies.