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

Announcement

Collapse

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

Stock Level Control

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Stock Level Control

    I used AlphaSports as my test bed.

    Here is a little tip to make sure that the Quantity on an Invoice cannot be greater than the amount held in Stock and the level will never be a minus value.

    First add a new field to the Invoice_Items table. Say we call it "Qty_in_stock". This will of cause be Numeric.

    In field rules make "QUANT_IN_STOCK" calculated, the expression is the LookupN function.

    LOOKUPN("F",PRODUCT_ID,"Qty_in_sto","product","Product_Id")

    It important to note the Index of "Product_Id" on the field PRODUCT_ID, this syntax was a little confusing for me at first, but as this Index is already build into AlphaSports, it helped.

    This is to get the stock level value with that PRODUCT_ID into the Invoice Item line.

    Also in the same table, make the field rule for Quantity, with a Validation of, QUANTITY

    The other rule is Posting, this is to subtract the value of Quantity from Qty_in_sto

    Any questions please email me.

    Regards

    Keith Hubert

    Guild Member
    London.



    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    #2
    RE: Stock Level Control

    Quote: ""Here is a little tip to make sure that the Quantity on an Invoice cannot be greater than the amount held in Stock and the level will never be a minus value.""

    Keith....

    In the real world of retail sales I've found it necessary to allow quantities to dip into the negative range simply because "crap happens".

    Example:

    #1 - The person doing the receiving hasn't yet inputed the invoice and the product mysteriously gets put out on the shelf. Try explaining to the customer standing in front of you... that you can't sell it yet, because it hasn't be received! (By the way, after receiving the quantities will be corrected)

    #2 - A customer special order arrives, and the customer comes in before it can be received.

    #3 - Some retailers want to be able to enter a negative quantity to allow returns or exchanges for another product.

    --Bob

    Comment


      #3
      RE: Stock Level Control

      Hmm.
      Maybe as a certified CPA I can add some light to this.
      I can understand that Keith was happy to share his findings with the community, after all that is what this forums are for.

      BUT.
      The fact whether this has any practical value depends on the used stock appreciation and management system.
      We can speak of a "Technical" and "Economical" Stock.
      Where the technical stock would be what is actually there, the economical stock would be what is there, plus what has already been ordered from the supplier and is yet to receive, minus what has been already sold to customers but has yet to be handed out.

      It is obvious, that in the last case the stock could be negative at any given moment.

      Then, understanding this principle, whe also have lots of stock in-out systems. There is LIFO (last in first out) or FIFO (first in first out), IRON STOCK (which relates to a number of articles always to must be in stock) and several other systems that influence how issues of goods are influencing stock.

      There are dozens of complete books written about this subject if one should care for more info.

      Greetings,

      Marcel

      Comment


        #4
        RE: Stock Level Control

        Thanks Guys for your constructive additions to my Tip.

        As you know, with Alpha Databases there are many applications where a developer is asked to produce an app which prevents a user entering a data because of a condition.

        Low level Stock could mean anything to anybody, e.g. the number of rooms in an Hotel. Or the number of spaces in a parking lot. At any given moment there will always be a finite number of stock available. How this informaion is used is for the end user to decide.

        I just hope this little tip has helped at least one Alpha user.

        Regards

        Keith Hubert

        Guild Member
        London.
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment

        Working...
        X