Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Lifo Fifo or Average value

  • Filter
  • Time
  • Show
Clear All
new posts

  • Lifo Fifo or Average value

    I have my inventory system set up using average cost as the basis for costing. I am now looking at ways to approach costing as either LIFO (last in first out) or FIFO (First in first out). The only way I can think of doing this is to create an inventory table that has a child table linked by product code to the parent inventory table. The records of this child would essentially hold the purchase price of the stock, the quantity of the purchase, the current quantity of the stock and a calculated field that yields the difference of the previous two. It would also contain a purchase date. What I envision is that whenever a customer makes an order the program will find the last batch purchased ( that is if we choose the LIFO method of inventory valuation) and subtract the quantity from it the costing will be at the actual cost at the time of purchase. the only other way I can think of is to actually generate an actual stream of records for each inventory item purchased so that whenever a sale occurs the inventory will be reduced by that amount. Any more ideas?

  • #2
    RE: Lifo Fifo or Average value

    The best way to accurately keep track of that information is to set-up a database that tracks inventory levels to keep accurate pricing. Relieving and receiving into levels as appropriate.

    For example:

    A record for each receipt at that specific price is created as inventory is received. Then as invty is relieved, qty is pulled from the most recent level until either that level until that level is used up. When a new receipt is recorded, if it is the same price, it can be received into the current level, however if the price is diff, a new level is created.


    10/10/2000 + 20,000 12.50/ea L_1
    10/12/2000 + 5,000 13.25/ea L_2
    10/14/2000 + 7,500 11.80/ea L_3
    10/15/2000 + 2,000 11.80/ea L_3
    10/20/2000 + 15,000 10.25/ea L_4


    10/13/2000 - 13,000 LVL_2 -5,000 (l_2 depleted)
    LVL_1 -8,000 (l_1 reduced)

    10/17/2000 - 12,000 LVL_3 -9,500 (l_3 depleted)
    LVL_1 -2,500 (l_1 reduced)

    10/21/2000 - 9,500 LVL_4 -9,500 (l_4 reduced)

    EOM Levels

    Level_1 9,500 @ 12.50/ea = $118,750.00
    Level_4 5,500 @ 10.25/ea = 56,375.00

    I probably went into way more detail and info than you need. But just wanted you to be aware of what is involved. Also, their are tax implications switching to LIFO or FIFO, which I'm sure you are probably aware of.


    • #3
      RE: Lifo Fifo or Average value

      Mark I am haing trouble understanding you levels system. Can you enlighten me on how you tables are structured?


      • #4
        RE: Lifo Fifo or Average value

        Greg - You may want to take the time to go to the "Business Owners Toolkit" - topic, "Identification of Inventory Items". This is a very complete analysis of the FIFO and LIFO systems, how to evaluate your inventory, how to arrive at cost of goods sold, etc.




        • #5
          RE: Lifo Fifo or Average value


          You probably should have a separate price table and quantity table for inventory in order to do this data chore. Your inventory objects would be uniquely linked to the child historical price associated with each order quantity. Also review the LIFO and FIFO references previously mentioned.

          For FIFO cost you would total the value from the start of the quantity and prices list for the number of items currently sold. For a LIFO cost you total the value from the end of the quantity and prices list and work toward the start until you've costed the number of items sold.

          I like to add a start date and end date to my child price history records. If there is a question about which price was in effect, you can compare this with the date of the order to check for entry errors and other linking problems.