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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Inventory Assembly Posting

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Inventory Assembly Posting

    I am working on an invoicing and inventory application, and I am hoping someone can help me with the best way to handle decreasing the on hand amount for assembly items when the master item is sold. For exmple: I have an Inventory database with Part_no 101 Hygiene Kit which is made up of assembly items with Part_no 1011 Soap, 1012 Toothpaste, 1013 Toothbrush. When I sell a Part_no 101 I want to decrease the inventory of all the items that make up Part_no 101 (1011,1012,1013). I currently have an inventory table (Part_no, On_hand fields), an Invoice_header, an Invoice_items tables, and an Assembly items table (used to link the assembly items to the inventory table Part_no, Assempart, Qty). I'm sure there is a good way to handle this using xbasic or am on the wrong track. Thanks.
    Tags: None
    #2
    RE: Inventory Assembly Posting

    Hello Gary,

    It's good to see you on the board. You are the 'old' Gary Smith of A4 fame, right??

    >>I am hoping someone can help me with the best way to handle decreasing the on hand amount for assembly items when the master item is sold.

    Comment

      #3
      RE: Inventory Assembly Posting

      Gary,

      I think an important thing to consider is "when" you do this. If you are doing it on line , as Jim suggests, deleting lines becomes a factor. Additionally changing quantity sold on the kit item gets more complex ( you need to know the qty sold on the prior save as well as the qty sold on the current save and only adjust the difference ). It's not that it's not doable, but it can get a little messy. I might consider a batch process for this to be done after a series of invoices has been entered, printed and verified. You could have an "inv_update" status field on the invoice header record. You could perform a batch script with a variation of Jim's xbasic logic on invoices with a status of "inv_update" = "N". After the script adjusts inventory for all the component items as well as any items that are directly sold but are not kits, you could change the status on the "inv_update" status on the invoice to "C" for complete. Another thing you might consider is making an inventory transaction file ( in's and outs) and addding to it when the update is done. One of these component deletions becomes an "issue" transaction as opposed to a "sale" transaction for items that are directly sold and not part of a kit. This helps if you need to know how many widgets were sold directly as opposed to how many were issued as part of a kit sale.

      Good Luck
      John

      Comment

        #4
        RE: Inventory Assembly Posting

        Hey Jim,
        I appreciate your advice on my inventory assembly problem. I have been out of internet reach for several weeks now and have been wanting to get back to you with appreciation and further advice. I think I follow your logic iterating through the child records, but my on_hand field is in the main inventory table not the assembly table. The tables are setup as follows with the inventory table linked to the assembly table one to many (Part_No to Part_No).
        (ie Part_No 9972 would be made up of 2 Assempart 520 and 1 Assempart 552) Assempart(s) 520 and 552 are also sold individually and included in the INVTRY table as Part_No(s)520 and 552.

        INVTRY
        Part_No
        On_Hand

        INVOICE_ITEMS
        Part_No
        Qty_Sold

        ASSEMBLY
        Part_No
        Assempart
        Assemqty

        Part_no 9972 would include 2 Part_no(s) 520 and 1 Part_no 552 when I sell a 9972 I need to decrease my On_hand in the INVTRY table for items 520 and 552 by 2 and 1 respectively, and Like you say, reverse the operation for a deletion. Any advice you can give me would be appreciated including restructuring my tables if necessary. Thanks.

        Comment

          #5
          RE: Inventory Assembly Posting

          Gary,
          I think it would be much easyer to do if you had a fourth table linked to the assembly table with primary key on assembly number. This would be a one to many link. For single Items the assembly number would be the same as the part number.
          For kits the the assembly number would be the linking field to the fourth table.
          Are maybe you could just add a field called assembly to the invtry table and link it to assembly on that field.
          Then when the assembly number is used fetch thought the child table based on the assembly number and update your inventory.


          I hope this is clear than mud.

          Nick

          Comment

          Previous template Next
          Working...
          X