Skip to main content
C
CN_14970431-Visitor
1-Visitor
October 13, 2024
Question

How can I make an index with duplicate find no in my smart BOM

  • October 13, 2024
  • 1 reply
  • 948 views

I am using Smart BOM, my company requires that if there is an ALTERNATE (or SUBSTUTUTE) part, the new "ALTN" part need to have the same FIND NO with the main part . 

 

For example: Main part is "ABCD" and FIND is currently 6, above FN6 is FN7 with part # "AFGK"

I need to add new part "xyzk" as ALTN to FN6, it will have the same FN 6 as the main part and sit in between FN6 and FN7. 

In the next message, I will tell about how I make it but it still NOT working as we want. JUst tell the community what I already tried to make it.

 

We are using Creo 7

But if newer Creo can make it, we can change to new version. 

 

Thank You

1 reply

C
CN_14970431-VisitorAuthor
1-Visitor
October 13, 2024

And here is steps that I already done

1- in the relation of the BOM, I create a new parameter and assign its value to the rpt.index

MyIndex = rpt.index

2- Replace rpt.index (cell on top of the FIND NO) to &rpt.rel.Myindex . Update table, Now the BOM  show the same since the value of "Myindex" is the same as rpt.index

3- In the assembly, Include xyzk.prt . Now the BOM show xyzk as a new part witrh QTY  1 

4- Get into the relation and add these line:

If asm_Partnumber == "xyzk"

   num = "ALTN"    (to display the QTY as ALTN)

  MyIndex = 6      (To display the FN as 6, same as the FN of main item)

endif

5- Update the table, yes, the new xyzk item now has FN6 as I want, but it still stay at its location (on top of the BOM) instead going down on top off the main FN6

6- I use "sort" table and add the key as FIND No and forwarding, then yes, I got the xyzk now go to above main item FN6 as I wish, but the real FN7 above FN6 (AFGK) becomes FN8 instead of FN7, all the FN above it is also added 1, as if the new ALTN FN6 is FN7 but show as 6, this new ALTN occupied the slot 7 and pump 7 and all items above to one number.

7- I use fix index to fix the FN8 (was correctly FN7) back to FN7,yes, it is back to FN7 and sit on top of the main FN6 and pump the ALTN 6 above it, the sequence now is FN6 then FN7 then FN6 ALTN.

 

My question is how can I make the display of the BOM as FN6 -> FN6 ALTN -? FN7 and so on.

 

Thank you very much

 

V
vnamboodheriCommunity Manager
Community Moderator
October 17, 2024

Hi @CN_1497043,

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

 

Regards,

Vivek N

Community Moderation Team.

C
CN_14970431-VisitorAuthor
1-Visitor
October 17, 2024

Thank you VNamboodheri.

I think my issue is unresolvable since I worked with Creo for almost 30 years (Since ProE 16 on Unix) and have this problem with SMART BOM since!

WE have one solution, It works, bt for me, It can't be acceptable since it's too complicated, time consuming, not worth it. Let me list steps here and if you want more details or example, I can provide

 

1- Create a repeat region with a col called FInd NO calling rtp.index and other cols

2- Flat index and accept duplicate, every item now is display with QTY 1

3- In the table relation, create a variable called MyIndex and assign its value to be rpt.index  (MyIndex = rpt_index) now you have MyIndex with the same value to rpt.index

4- From the BOM replace the code on Find No Col from rpt.index to new &mbr.asm.rel.MyIndex[0.0] the BOM now display the same with prt.index since they are the same values

5- Now click on each FIND value and assign the  Find No as you want from 1.0 to x.xx. WIth the format of x.xx as

    X.0  is the main index and x.10, x.11 x.12 ... are the ALTN parts for example: If you want to display 4 screws AAAAA.prt as FN6, and Screw BBBB , CCCC as ALTN then

   at line of 1st  AAAAA, click and assign 6.0 the second line of AAAAA is also 6.0 and 3rd as 6.0 4th is also 6.0, we will have duplicated [arts AAAAA all with 6.0 later 4x of this 6.0 will be display on the BOM as QTY 4 for these 4 items when you change the BOM back to no duplicate (later).  Then at BBBB, assign the FN to 6.1  CCCC to 6.2  now we will have BBBB as 1st ALTN, bare same FN6 as AAAAA on top of FN6 and CCCC is second ALTN on top of BBBB

6- Go into the relation and add these line:

If mbr_asm_partnumber == "BBBB"  (the syntax to call asm part number may be slightly different since I did not open Creo to check the correct wording)

 num = "ALTN"

endif

Then the QTY of this part  will show ALTN

7- Go to the table = property and change the to balloon tab and change the select (currently) rpt.index to &mbr.asm.rel.MyIndex[0.0]

    THis will make the smart balloons to call out with the number assigned manually to the FInd No as above

8- Go to the repeat region and change to "No Duplicate" now the table will show AAAAA at FN6 with QTY 4 and BBBB, CCCC on top of FN6, also have same value FN6 with QTY sown as ALTN ... then FN7 ...

 

Now you can run Table Create Balloon and it will work Smart same as with rpt.index

 

AS I said, this method WORKS but not reasonable since:

1- If you add one more part that is already in the BOM, let say if you add one AAAAA to the assembly, the BOM will not assign this new part to FN 6 even we already HAD AAAAA, we have to assign the new AAAAA as 6.0 to add it to the existing BOM

2- If the assembly is a large assy, with many hardware, let say we can have 100x screws AAAAA and 100 washer DDDDD, we have to assign 100x 6.0 to AAAAA and 100x N.0 to DDDDD and so on.

3- SInce all index in this method are manually assigned, then during review, some reviewers want to change the FN sequence on the BOM, with the rpt.index call out, we only need to go to the repeat region and "FIX index", here, we3 have to open the BOM to duplicate and reassign the whole table with the new indexes!  It will be a nightmare!

 

Best regards to all

 

 

Terms & ConditionsAccessibility statement