First off, I do not have the routed systems packages. I do limited work with components that are "per lenght" as opposed to "per each".
For this reason I have developed a custom BOM Table that uses PARAMETERS and RELATAIONS to populate a custom BOM_QTY.
IF EXISTS ("ASM_MBR_BOM_QTY")
For each component that I wish to quantify by lentgth, the BOM_QTY parameter is set by a relation in the model (i.e. BOM_QTY=d0).
I use the FLEXIBILITY (varied items) for such components so that the component legth can be dictated for each assembly.
The BOM_QTY value shown for such components in the BOM TABLE (Repeat Region) will reflect this "flexibility".
This part is working well.
The dilema is that we work in both Metric (mm) and English (in). Our latest designs are Metric.
Existing model of wire, that was modeled in Eglish (in): WIRE_PART_ENGLISH
New Metric Assembly: METRIC_WIRE_ASSY
WIRE_PART_ENGLISH is placed into METRIC_WIRE_ASSY and made to be flexible. The legth of the tube d0 is made flexible. The value entered is 10 for 10 inches. It appears that the flexibitly window uses the units of the component, in this case inches.
The BOM table in the METRIC_ASSY drawing shows 22 (in) instead of 558.8 (mm). On another note, if the WIRE_PART_ENGLISH dimension d0 (or any other dimention of this component) is shown on METRIC_WIRE_ASSY drawing it will display as 22 (in), not 558.8 (mm). The wire that was modeled in metric displays correctly both BOM information and dimensions.
Option 1. Find a way to have the BOM_QTY value of the components in the BOM display in the units of the ASSY, despite the units of the components
Option 2. Find a way to have a USER DEFINED or SYSTEM paramter for the UOM displayed in the BOM TABLE that mathes the units of the BOM_QTY. If the compnent is a "per each" item, then have EA displed as the UOM.
In eiter case I had to set up the model and the repeat region:
First, for the "per length" component, the BOM_QTY parameter was set up with units (Insert Unit). The Unit Sensitive was turned on in the Relation Utilities and a relation was set up to equate BOM_QTY to the length (BOM_QTY=d0).
For the repeat region, the RELEATIONS and PARAMETERS were set up as follows:
Then I tried to implent Option 2.....
Additional PARAMETERS and RELATIONS were set up to look at the UNITS of the BOM_QTY.
I would think the way to pull the UNIT information from the BOM_QTY parameter would be to use &ASM.MBR.PTC_UNIT.BOM_QTY
Note: The syntax in the relation is to replace the "." with "_"
The issue is that I cannot get the relations to work. I get a hidden error. That is when I Execute\Verify the relations the system says Relations have been successfully verified.
However, when the UPDATE TABLES is run, the system says that "There are errors regenerating repeat region relations".
And for the "per length" items, not only do I get a "blank" value in the UOM column, but the QTY column also now shows a "blank".
Could it have something to do with replacement of the "." with a "_" when you use a PARAMETER in a REPEAT REGION RELATION?
When using &ASM.MBR.PTC_UNIT.BOM_QTY in a relation, it is written &ASM_MBR_PTC_UNIT_BOM_QTY.
I wonder if upon regeneration or update the ASM_MBR_PTC_UNIT_BOM_QTY is interpreted as ASM.MBR.PTC.UNIT.BOM.QTY? The "." between PTC and UNIT would not make sense.
This is driving me nuts!!!!!
UPDATE: 3:11pm 10SEP2012...
I tried to remove the "_" in my BOM_QY and BOM_UOM parameters, and change them to BOMQTY and BOMUOM respectively.
This time it resulted in an error when Execute\Veriry was run. So, it points more to the "_" in the PTC_UNITS being an issue???
Still driving me nuts!!!!!
Message was edited by: Michael Gwin
Solved! Go to Solution.
I know how you feel, this has been driving me crazy. You would think after 20+ years that Pro/E (Creo) would have a simple way of generating a BOM that you can easily configure (per component) to drive the qty as you wish, either by EA, LENGTH, AREA, etc. and it would also be able to automatically list the units.
Thanks for your efforts. I did try the ASM_MBR_PARAM_UNIT also and it did seem to work. However, the only hole is that if you have units defined in more than one PARAMETER, in the model then you get multiple listings in the REPEAT REGION.
I added two phony PARAMETERS in the METRIC PART and gave them random UNITS. As you can see the METRIC PART has multiple listings now. NO DUP/LEVEL is applied as an attribute of the REGION.
This alone sent my whole perception of reality back. I had no idea that REPEAT REGIONS are driven by PARAMETERS and not the COMPONENTS.
In other words, I thought the REPEAT REGION simply had one row per COMPONENT (assuming no duplicates or no dup/level) and would then fill in the other cells in the table based on their value for that COMPONENT.
So, I am down to the following two choices.
I did open a PTC case and referred them to this discussion on PTC Planet. I will wait to see if they have any other revelations and let you know.
Welcome to the wonderful world of repeat region relations.
First thing I'd try would be to stop using BOM_QTY as your special quantity parameter. For exactly the reasons you're describing, I limit myself to one word with no underscores. I'd go with bomqty instead of bom_qty.
Second... there is a chance that the underscore in ptc_units is an issue- but there's nothing you can really do about it. I'm very impressed you got as far as you did. Most people get stuck and call for help somewhere in the first few steps. You've made it very far into the problem. You've turned on units sensitivity and you know about the ptc_units tag. You can count the number of people who know this exists on two hands. So congratulations for getting as far as you have!
I really need to go back and carefully digest the material you've posted so far. At first glance, you're on the right track. But there are some nuances with the ptc_units mechanism you need to watch out for. First, I believe you have to have units sensitive turned on and then generate a new relation before the ptc_units tag will work. Simply turning units sensitive on and then trying to query it is not enough. You have to create a relation after that switch it set before ptc_units will work.
Let me take a closer look at your problem and I'll write back with better advice or a solution.
Many thanks for the compliments, this means a lot coming from someone with your expertise.
I specifically sent you a link to this post after reading one of your replies to another community member regarding 1/2 pieces in a BOM. In that post you mentioned that "_" in user defined parameters cause issues.
I have updated my post as well as removed the "_" from my UDPs. They are now BOMQTY and BOMUOM.
I have a bad feeling the system parameter PTC_UNIT is causing the relations to fail (now upon Execute\Verify) because of the "_".
As you said, please take your time to digest.
Look forward to collaboration on this.
Interesting post. Looks like you have done some research on the matter before posting.
Since I don't have any experience with ptc_unit report in particular I can only mention couple of basic steps related to repeat regions in general and those are:
1) To make sure that your repeat region contains all the parameters used in cells of repeat region table and also including parameters used in relations. From my experience user defined parameters don't get defined automatically after the relation is verified. So if you have a &ASM.MBR.PTC_UNIT.BOMQTY in one of cells of your repeat region table then make sure you have ASM_MBR_PTC_UNIT_BOMQTY parameter defined in relations of your repeat region.
2) Sometimes when you choose to just simply type in the repeat region cell for example the &ASM.MBR.PTC_UNIT.BOMQTY then it won't report the parameter after the table is updated. So instead of using RMB and going for properties the sure way is to choose "Report Parameter" instead and go for selection of asm... --> mbr... --> ptc_unit... --> User Defined in an opened tab and then type in the parameter name upper case.
Thanks for the kind words... I'm happy to help. I've built a little model mimicking your scenario. I have a few more bits to add. Once I have modeled the problem, I'm sure we can find a way through it. There were so many moving parts- the flexibility thing, the units differences, the repeat region relations, etc. I just felt I needed a model that duplicated the problem before I could really dig into it.
I'll take a deeper look this evening. Thanks for your patience!
Attached are files that I just created from scratch.
Currently, the relations in the repeat region set BOMUOM=”LENGTH”.
If this is changed to BOMUOM=ASM_MBR_PTC_UNIT_BOMQTY, then the repeat region does not fill in correctly.
The “per length” parts data for BOMQTY and BOMUOM both go blank.
The Execute\Verify does not give error. However, when you update tables you get an error message at the bottom of the dialogue window.
It is really looking like the "_" in PTC_UNIT is causing issues.
By the way. We are working in Wildfire 3.0 currently and hope to move to Creo in the coming months.
I'm the person with the half part.
Are the cables part of a family table? If they are, is the parameter values of the generic defined (i.e. the BOMQTY and the BOMUOM) - could be something a simple as a dash.
I found that values would not propogate properly from family tables if the value of the generic/parent had not been given a value.
You have quite a quirky problem there! I think you're right, the underscore in "ptc_unit" is preventing the relation from working. I've suspected some problems with this before. There are only a few options that have an underscore in them. This is fine except they seem to violate the "replace the dot with an underscore" rule once you get to table relations.
This problem definitely gave me a workout. Doing battle with table relations is always a bit like stepping into the Twilight Zone. That's usually fun for me but this problem just ticked me off. So... I blew off the homework and quiz due tomorrow for my programming class and, hopefully, solved the problem.
Check out the screen shot below (click to enlarge). The BOM is live and using your relations (with one small change):
So what's the change that made it work? Well, the Pro/REPORT parameters you use to populate a table are a true disaster. Just a few revisions ago, you could find a comprehensive list of all the available permutations of these parameters. Today, the help files for report parameters have magically disappeared. This is an epidemic by the way... the help files just keep getting slowly worse... and worse. Somehow there's always less information, no pictures, etc. It's almost like someone want you to take a class to learn how to operate the software.... except that no one offers a class on how to do this stuff!
Anyway, it's late and I'm rambling... sorry!
The point is... there are so many possible permutations of report parameters, you can often find several strings of parameters that give the exact same value! After I couldn't get the ptc_unit tag to work, I tried some of the other variations and found one that seems to work. Instead of asm_mbr_ptc_unit_bomqty try asm_mbr_param_unit. See the screenshot below for the modified relations:
How in the world does that work? We didn't even have to provide the name of the parameter to interrogate. I mean... how does it know which parameter we're trying to get the units from? hrug: I dunno! Maybe it uses the last parameter defineed using the units_sensitive option. I'd be lying if I said I understood the logic behind it. I just know from experience that sometimes you can play with similar sounding parameter strings and you'll hit paydirt. Notice there's no extra underscore anywhere in asm_mbr_param_unit to cause problems!
One thing to note here, you must add the parameter to the local parameters at the bottom of the relations window before attempting to use it in the actual relations. This happens frequently. If you try to use asm_mbr_param_unit outright, you'll get a failure. Whenever this happens, you have to either go to the local parameters section of the relations window and add it by hand or else add the parameter to the table itself and regenerate. This second option just does the same thing as adding the parameter to the local parameters manually.
To add the parameter manually, just click the green "+" sign at the bottom of the relations window. Type asm_mbr_param_unit as the parameter name then click OK (or hit enter). For a moment you'll see the parameter set to "Real Number" and a default value of 1.000 but these will disappear once you select OK (or press enter). After this is done, you can freely use asm_mbr_param_unit in your relations and no failures will appear.
Hopefully this helps! I shouldn't write these posts late at night. This message is a monster! I could've just said "Use asm_mbr_param_unit" and you'd have figured it out.
Let me know how it works... or if there are any holes in this solution I haven't found yet.