Data Management Capabilities > Using Excel to Export and Import Product Data > About Importing Product Data from Excel > About Importing Redline Product Data from Excel > Considerations for Importing Redline Product Data > Considerations for Importing Redline Product Structures or BOMs > File Format for Importing Redline Product Structures or BOMs
File Format for Importing Redline Product Structures or BOMs
The following table describes the format of data in a redline product structure or BOM import worksheet. It defines the column header, whether the column is required, and the description of the data that can be entered for each column.
* 
In a spreadsheet, all discrete values (a value that must be one of few fixed values) must be entered as an internal value, not the display value. For example, for the Default Unit attribute, use as_needed (internal), not As Needed (display).
Column Name
Required
Editable on Reimport
Description
Action
Yes
Yes (for deleting)
Includes Add, Delete, and Replace.
* 
The Replace action allows you to swap a child part in a BOM during bulk import using three optional columns—Original Number, Original Organization ID, and Original Container, to identify the part to be replaced. These columns are ignored for all actions other than Replace.
Level
Yes
Yes
The level of a component in the redline structure hierarchy.
For example, if a root part, part_1 with an open redline had child parts with open redline versions, part_2 and part_3 , and part_3 had a child part_4 as part master, then the level for each part is specified as follows:
• for part_1, level is 0
• for part_2, level is 1
• for part_3, level is 1
• for part_4, level is 2
* 
If you do not have the parent part with an open redline at Level 0, the Preview step in the Import from Redline Spreadsheet window does not display anything.
Number
Yes
No
The part number to be added, modified, or removed from the structure. For the Replace action, it is the replacing part number.
OrganizationID
No
No
The owning organization for the component part to be added, modified, or removed from the structure. For the Replace action, it is the owning organization of the replacing part. The default value is the organization of the change notice.
* 
Organization ID is required if you want to import parts that do not belong to the target organization.
Container
No
No
The container for the component part to be added, modified, or removed from the structure. For the Replace action, it is the container of the replacing part. The default value is the container of the change notice from which the import tool was launched.
The following example shows the full path to the container:
/wt.inf.container.OrgContainer=PTC/wt.pdmlink.PDMLinkProduct=Test_Product
where PTC is the name of the organization and the Test_Product is the name of the product.
Revision
No
Yes
Specifies which revision or redline version of the part is getting updated.
* 
When the column is omitted or a value is not defined for it, the redline version is used as a value for a part master that exists with an open redline on the change.
View
No
Yes
Specifies which view of the redline structure is getting updated. Enter Design or Manufacturing. If you have created a customized view using the View Administrator, it can also be listed as the value.
* 
When the column is omitted or a value is not defined for it, the value is empty for a part master that exists with an open redline on the change.
Quantity
No
Yes
Defines the number of parts in the assembly. The default value is 1.
Unit of Measure
No
Yes
Quantity unit for the parts in the assembly. The default value is ea. Other possible values are as follows:
• as needed: as_needed
• kilograms: kg
• meters: m
• liters: l
• square meters: sq_m
• cubic meters: cu_m
Reference Designators
No
Yes (but it must be unique)
Reference designators specified using shorthand format (for example: R1, R3, or R1-R10).
Use the following syntax rules for specifying reference designators:
• A reference designator consists of an alphanumeric string prefix, followed by a numeric integer suffix. For example: R57, PS1, A66A2.
• The first and last characters in the prefix must be alpha characters. For example: R1, RAX3, R4X5.
• Use a comma to separate sequences of reference designators. For example, R1, R2, R7.
• Reference designators can be specified as a sequence and as a range. For example: R1-R7, R10, R12.
* 
The number of occurrences must not exceed the quantity when using the unit of measure “Each”. If you modify the quantity or reference designators, the existing occurrences may also be updated accordingly.
Trace Code
No
Yes
The trace code value on the part usage link. Use the following values:
• untraced: 0
• serial number: S
• lot number: L
• lot/serial number: X
Find Number
No
Yes
Identifies the Find Number for the usage link.
Line Number
No
Yes
Identifies the line number of a part within a manufacturing bill of materials. Also known as position numbers that are used with enterprise resource planning (ERP) systems.
Component Id
No
No (for an existing usage link)
An internal alphanumeric key, commonly driven by CAD, uniquely identifying a child part for a parent part. The value should be empty for a new part usage and may be optionally used to identify an existing part usage.
* 
Component Id is not considered when com.ptc.windchill.ixb.importer.bom.oldBOMSheetImportLogic is enabled.
Quantity Option (for configurable parts)
No
Yes
Integer value parameter in the parent configurable part's logic base that controls the quantity of the component.
Inclusion Option (for configurable parts)
No
Yes
Boolean value parameter in the parent configurable part's logic base that controls the inclusion or exclusion of the component.
Type
No
No
Part usage link type WCTYPE|wt.part.WTPartUsageLink, which is the default value.
IBAs (soft attributes supported by the spreadsheet)
No
Yes
Attribute constraints and relationship constraints.
Original Number
Yes, when replacing a child part
No
For the Replace action, it is the number of the original child part to be replaced.
Original Organization ID
Yes, when replacing a child part
No
For the Replace action, it is the owning organization of the original child part. The default value is the organization of the change notice.
Original Container
Yes, when replacing a child part
No
For the Replace action, it is the container of the original child part. The default value is the container of the change notice from which the import tool was launched.
The following example shows the full path to the container:
/wt.inf.container.OrgContainer=PTC/wt.pdmlink.PDMLinkProduct=Test_Product
where, PTC is the name of the organization and the Test_Product is the name of the product.
Was this helpful?