I remember doing this once long long ago, no clue where the code is, can't even 
remember
who it was for.

But in that case we KNEW the maximum number of levels out it could go.  If 
there isn't a
limit to the levels then my approach wouldn't work.

But basically I would step thru the main level one-by-one in a cursor, load 
that top level part
into my temp table.  Then cursor each of its sub-parts and load those into the 
temp table, but
actually in different columns so the "indent" is built in.  So my program would 
have 3 nested
cursors.  The report simply shows each column from the table.

One table that holds the parts & descripts, another 2-column table that has the 
parent/child
relationships of all parts.  The lowest level would have no child

I'll bet this won't come thru formatted so I apologize, but the basics for a 
3-level design would
be this table that has 3 columns in it, with the program loading the data into 
the appropriate
level's column.   The report would just have located spots for the 3 columns.

Column name:
Level1        Level2        Level3
----------------------------------------
Part01        <null>        <null>
<null>        SubPart01     <null>
<null>        <null>        SubSubPart01
<null>        <null>        <null>  (blank row between Level1 parts


Karen


 

 

 

-----Original Message-----
From: Albert <[email protected]>
To: karentellef <[email protected]>
Sent: Wed, Nov 25, 2015 10:14 am
Subject: [RBASE-L] - Re: BOM

I would use a temporary reporting table for this. The columns to report 
would be as follows or both Assy/Sub part numbers and descriptions. I 
find that system easier than using report variables.
     Assembly
     Assembly description
     Sub Level 1
     Description Level 1
     Sub Level 2
     Description Level 2
     Sub Level 3
     Description Level 3

Load the table with a stored procedure, repeating the values in each 
column and adding the subs as needed.

Each column would be reported with repeated values hidden. That should 
give you what you need.

Albert

On 2015-11-25 8:57 AM, Jim Belisle wrote:
> For years we have costed our products with a simple report just throwing 
> together all parts making up a product not worrying about using an indented 
> BOM.
> We would like to go to an indented BOM.
> Right now it is just
> Model# then all parts making up the model.
>
> We want something like this:
> Level 1: Model#
>            Level 2: Assemblies and parts we ship
>                     Level 3: Sub assemblies (or parts if no subs) making up 
> the assemblies.
>                               Level 4: Parts making up the sub assemblies.
>
> I can get it so all assemblies are together and then all subs together by 
> assigning a BOMtype to them.
> So it will be:
> Assy
> Assy
> Assy
>            Sub assy
>                     parts
>            Sub assy
>                     parts
>            Sub assy
>                  Parts
>
> That is not however what we want. I just can't seem to figure the proper way 
> to handle this.
> Any blues clues would be appreciated.
>
> James Belisle
>
> Making Information Systems People Friendly Since 1990
> [cid:[email protected]]
>
>



Reply via email to