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

Multi Level BOM

  • Filter
  • Time
  • Show
Clear All
new posts

  • Multi Level BOM

    I have designed a Preventative Maintenance Application, but one of the remaining limitations is that it has only a single level BOM.

    I know that I need to change it to a Multi Level BOM to be truly useful, but have not been able to build this in Alpha 5 yet.

    Has anyone information on the technique, or a sample application, on how to structure and build a multi level BOM (Bill of Materials) in Alpha Five?

    Andy Sigrist

  • #2
    Re: Multi Level BOM

    Just trying to help!

    This may get better coverage if you post your thread in the proper place. I/we don't know what version of alpha or if it is web based or desktop?
    Dave Mason
    Skype is dave.mason46


    • #3
      Re: Multi Level BOM


      thanks for the suggestion. I will post it in another forum.



      • #4
        Multi Level BOM (Bills of Materials)

        I created a Preventative Maintenance Application, but one of the remaining limitations is that it has only a single level BOM.

        I know that I need to change it to a Multi Level BOM to be truly useful, but have not been able to build this in Alpha 5 yet.

        The application is written in A5 V10 for the desktop and Web application. It is mostly used as a desktop application by customers.

        Has anyone information on the technique, or a sample application, on how to structure and build a multi level BOM (Bill of Materials) in Alpha Five?

        Andy Sigrist


        • #5
          Re: Multi Level BOM (Bills of Materials)

          Hi Andy
          Since a BOM itself is the lowest level schedule resulting from a materials management system - if one looks at it from the POV of the factory/equipment/machinery/finished goods etc being the top.
          If the multi-levels you refer to is subdivisions of some kind, that indicates a component of the data at whichever level.
          If they are sub-assemblies then it involves different technology, perhaps reticulation.
          Give some detail of what you mean by "multi level" and where the current system is failing.


          • #6
            Re: Multi Level BOM

            Originally posted by DaveM View Post
            This may get better coverage if you post your thread in the proper place. I/we don't know what version of alpha or if it is web based or desktop?
            This is the proper place. But you're right, we do need to know if it is desktop or web.
            AlphaBase Solutions, LLC



            • #7
              Re: Multi Level BOM

              Here are some ideas ---

              Three tables gets you a basic BOM:

              WorkOrder ---< WorkOrder Items ----< WorkOrder SubItems

              More complex you add a traveler table - this table would detail the movement of each part through the shop:

              traveler_status_table (this would be fired by a stored procedure or xbasic in A5)

              You could also create a table full of standard build / repair items:

              WorkOrder SubItems --- < subItems_has_Process >---- WorkOrder_Process

              Michael Carroll


              • #8
                Re: Multi Level BOM

                My application is mostly used as a Desktop application, currently in A5 V 10.5. I do have a web interface as well that some customers use. Screenshots of the application can be found at

                The Multi Level BOM I am looking for is similar to what SAP or other ERP systems would used. It is a hirarchical tree of a finished good items consisiting of individual parts and subassemblies. Parts are assembled into subassemblies. Finished food is built from a combination of parts and subassemblies.

                An analagy could be a food recipe system. A completed food item product requires a BOM. It includes individual ingredients, but also pre-prepared items (sub-assemblies) for sauces etc. Sugar may be used in a sub-assembly, but also as a direct ingredient in the final product.

                The way I approached it so far is to:
                - created a table called ITEMS. Any part, subassembly or finished good - in short anything - is an item.
                - created a set called BOM consisiting of a BOM header and one-to-many linked BOM Item
                - each BOM by itself is single level, but BOM items can include items such as sub-assemblies that are have in turn their own BOM. This is the multi-level part.

                This approach works for me so far and is based on a an ERP system (Made-to-Manage) that I am also familar with. My largest problem at this point is the ability to display on the screen or print the multi level BOM.

                I may be on the right track and just need some help on how to display and print the hirarchical tree, or there may be a better approach to this.

                If anyone has done a similar application or insights, I appreciate all help with this.



                • #9
                  Re: Multi Level BOM

                  This takes me back...
                  No doubt there are many ways to tackle this but let me offer the following as a solution that I have used.
                  In my case everything was made from bought items. I start by assigning a "level" to every part as follows:
                  Let's assume you have a table that all parts are recorded in and call that table Items. In here parts are flagged as bought Y/N.
                  Parts that are Bought=Y are automatically level 1 and all other parts are initially set to level = 0.
                  Now cycle thru the BOM's line items of Parts where level = 0. When you find a BOM where all components are level = 1, then the level of that parent part is 2, which is then set accordingly in Items. After passing through all parts, if there are any parts still with level = 0, then cycle thru again and when you find a part made from items with level > 0 then that part is level 3. You just keep going until there are no parts in Items table with level = 0. In my case we had went to level = 7.

                  Now that every part has a level, when you want to print a BOM you can use the level of the top level part and cycle thru the BOM of each assembly/subassembly until you get down to only bought items (level 1). You write a record for each part into a temp table with a calculated "list order" field that you eventually use to sort the parts for printing or displaying on screen as a heirarchical tree. Calculating the "list order" requires some clear thinking but hopefully I have provided enough info to point you in the right direction.
                  Last edited by Garry Flanigan; 09-20-2011, 02:42 AM.


                  • #10
                    Re: Multi Level BOM


                    thank you for the detailed explanation, I will try it over the next few days alongside another attempt that I am working on. I will post feedback here as soon as I have more questions or can share my solution with you and everyone else that may be insterested in this.

                    Andy Sigrist