bom_format: documentation and examples?

[painaz]

wildfire users (creo do not know)

for those who do not have a pdm from the info menu, distinct base it is possible to see the distinct base.

the distinct base is displayed in the integrated browser, but can be redirected to a text file.

the option is:

info_output_format that can be set text or html

there is also another option:

bom_format nameformed.fmt

to what seems to be possible to export in text file a distinct real, which also contains the parameters defined by the user.
the problem is that on the help is not indicated the syntax that should have this file

could be very useful to those who do not have a pdm.

Does anyone know how a nameformed file should be written?fmt? ? ?

 

[tartufon80]

Hello painaz!

the problem is "ancient"!

Try to take a look here..

 

[painaz]

Hello painaz!

the problem is "ancient"!

Try to take a look here..

Oooppppss!! ! !

I had done a search on the network in international forums finding little or nothing; for this I said, "Let's try to ask", without too many illusions and without doing a preventive research on the cad3d forum.

Mea culpa!

I found more information here than on international forums.

now I open notespad and write 100 times: "I will always use the search function before asking a question"

 

[tartufon80]

Oooppppss!! ! !

I had done a search on the network in international forums finding little or nothing; for this I said, "Let's try to ask", without too many illusions and without doing a preventive research on the cad3d forum.

Mea culpa!

I found more information here than on international forums.

now I open notespad and write 100 times: "I will always use the search function before asking a question"

:hahahah:

I wasn't arguing!

breaks the boxes in fact that there is no dedicated section on the guide!
but go on anyway!! :finger:

 

[DANI-3D]

... I found more information here than on international forums. . .

We're always the best. If you need more clarification, hit a hit.

 

[painaz]

bingo!!!!

dopo aver torturato google, ho trovato questo documento:


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
the source of the bill of materials (bom) output format can be configured by the configuration file option bom_format. for more information, see configuration file options in pro/help.

****************************************************************
(qui si riferisce alle opzioni da settare di cui ho parlato all'inizio della discussione)
****************************************************************

the default output format for the bom (see the following figure) is divided into two sections:

breakdown--lists the name, type, and number of instances of each member and sub-member.

summary--lists the total quantity of each part included in the assembly. it amounts to a ``shopping list' of all the parts needed to build the assembly from the part level.

default bom format file

a user-defined bom output format specifies the format of the breakdown section and the summary section separately. you can include one or both sections, but you must specify the column titles, row content, and display format for each included section.

the user-defined format file contains a combination of text and formatting commands. the overall layout of the bom is specified with the following section commands, which appear at the beginning of a line:

.breakdown--this command appears at the beginning of the breakdown section of the bom. lines of text following the .breakdown command appear as a heading for each assembly breakdown.

.summary--this command appears at the beginning of the summary section of the bom. lines of text following the .summary command appear as a heading for the summary section.

.titles, .row--these commands may be used within each section of the bom to specify the column titles and the information to be included on the repeating rows of the bom.

at any point in the format file, you can specify a system-supplied or a user-defined attribute:

%$--a percent sign followed by a dollar sign indicates that the next word is one of the three system-supplied attributes: name, type, or quantity. for example, %$type.

%--any word preceded by a percent sign only is a user-defined parameter.

text that is not a part of a parameter name is printed as it appears. for example, to print a dollar sign before the user-defined attribute price, type $%price.

system-supplied and user-defined parameters may be followed by a
c language-style format specifier, enclosed in square brackets ([ ]), that indicates the data type and printout width of the attribute's value. these format specifiers are optional, but may be needed for correct column alignment.

examples of format specifiers are as follows:
[4s]--the preceding parameter is a string variable (text), and the field width is 4.
[3d]--the preceding parameter is an integer, and the field width is 3.
[6.2f]--the preceding parameter is a floating point variable (real number). the total field width is 6 (including a decimal point), and 2 digits follow the decimal point. example: 400.25.
[8.8s]--the preceding parameter is a string variable. the field width is 8, and longer strings are truncated to 8 characters.

note:

field widths may be overridden by strings that are longer than the specified field. use this format to ensure that the field width remains the proper size.
[-4s]--the text in this field is left-justified. (the minus sign indicates left-justification).

in each of the preceding format specifiers, the letter is optional; pro/engineer determines the type of the user-defined parameter (string, integer, or floating point) if you omit it.

note:

you cannot use the bom function on the info menu to print parameters defined as ``note' type parameters.

entering the field [%[$total(item)]] in the format file (where item may be a user-defined parameter name) calculates the total for item. when entered within a .row command, the total is for that row only. anywhere else, the $total() command must also be preceded by the .row command and the total is for all item within the sub-assembly or assembly. you can also use [%[$total($quantity)]], where quantity is a system-supplied attribute.

note:

in $total(item), do not put a percent sign (%) before item or $quantity.

the system checks the format file for errors. if an error is found, the bom format file appears in an information window with the error highlighted.


***********************************************************************

tempo permettendo, se riesco a tirarci fuori qualcosa di utile farò una mini guida tipo quella fatta per modelcheck
da mettere a disposizione del forum

il link dove ho trovato le informazioni è:
http://www.eng-tips.com/viewthread.cfm?qid=212113

 

[tartufon80]

compliments for tenacia painaz! :finger:

Now we explain why certain hieroglyphics! :biggrin:

Good to make! ! !

 

[Ghery]

if my *.fmt is so composed :

separate components for the axieme %$name|%codice|%description_1|%description_2
Breakdown.

together %$name|%codice|%description_1|%description_2
.titles file|code|description|description2|q.ta'|peso|tipo|%$name
.row %$name|%Code=%Description_1|%Description_2|%$quantity=%weight[.2]♪


.summary

================================================================================================================================================================================================================================================================
list of components for axieme %$name|%code|%description_1|%description_2

.titles file|code|description|description2|q.ta'|peso|tipo|%$name
.row %$name|%Code=%Description_1|%Description_2|%$quantity=%weight[.2]♪


Total number of components: No. %[$total($quantity)][-6d]

that generates 2 variants of the same distinction or a "consollidata" version or with the quantities of the added common pieces, and a "structured" version or with the sub-distinte of each sub-group. . .

p.s. "code" , "description_1" , "description_2" and "weight" are parameters customized by us...

 

[painaz]

I add:

.breakdown generates separate blocks for each sub-level

.summary generates a distinct with all the pieces of the axieme listed in a unique list.

There is an undocumented limitation: at most you can use 120 characters per line.
the limit is bypassable using more breakdown and more summary.

example below.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Breakdown.
%$type %$name contains:

.titles qta; code; file; type;

.row %$quantity[3d]; ;%[-15s]; ;%$name[-30.30s]; ;%$type[-15.15s]%$type %$name
n° components: %[$total($quantity)][-5d].summary
Total list on single level of %$type %$name

.titles qta; ;code; ;description; ;material; ;qta[mm]

.row %$quantity[3d]; ;%[-15s];[-35.35s];;% materials[-30.30s]; ; %qta[-5.0f].summary
Total list on single level of %$type %$name

.titles qta; code; file; type;

.row %$quantity[3d]; ;%[-15s]; ;%$name[-30.30s]; ;%$type[-15.15s]n° components: %[$total($quantity)][-5d]Total weight kg: %[$total(peso_kg)][-10.2f]

 

[Ghery]

interesting...

a question I didn't find around:

in all these boms I only see the $name parameter that corresponds to pdmlink/pro-e to the "filename" parameter which then appears in the model tree on the left.

in pdmlink/pro-e there are 2 other parameters for names or "name" and "number".

you know the corresponding parameter in bom of "number" and "name" ? I tried translating it into English "number" and does not work and the "name" parameter translated would always be "name" and is already used.

 

[tartufon80]

interesting...

a question I didn't find around:

in all these boms I only see the $name parameter that corresponds to pdmlink/pro-e to the "filename" parameter which then appears in the model tree on the left.

in pdmlink/pro-e there are 2 other parameters for names or "name" and "number".

you know the corresponding parameter in bom of "number" and "name" ? I tried translating it into English "number" and does not work and the "name" parameter translated would always be "name" and is already used.

the one called "name" corresponds to the ptc_common_name parameter.
But I never tried differently.

I don't know.

 

[Ghery]

with my usual luck is exactly the "number" parameter that I have to put in distinct base.....