PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
Import a CAD BOM
Most CAD applications can export a bill of materials (BOM) directly, usually in a convenient plain text format called "comma-separated values" (CSV). PDXpert uses a Data Transformations template to map the CAD file's headers and data to PDXpert's part records.
If you want to bulk-import many BOMs from a legacy data source like Excel or an ERP/MRP, use the External Data Importer tool.
An import file doesn't create any new items; it simply establishes relationships between an assembly and its immediate child items (a single-level BOM).
All items must already exist in the database, and are matched using the same Item uniqueness system rule that detects duplicate parts.
When an assembly is first released, its Find values are established as anchors for tracking row changes in later revisions of the assembly. Importing a BOM file into a later assembly iteration causes each imported row to be compared to the contents at the existing Find. Any changes in the row are marked as Add or Remove, as appropriate.
To minimize the number of irrelevant changes on a new assembly revision, do not arbitrarily change the Find value on revisions to an imported BOM file. For example, new BOM components should not be inserted into the middle of the list (which changes all subsequent Find values), but added at the end.
To import a BOM Markup from a file—
A BOM import can be performed only within the Markup list, and only before the pending assembly iteration is approved and released.
When you have your BOM file ready to be imported, create a new part record, or open an existing pending iteration. Select the part's BOM tab's Markup list.
Within the Markup area, open the context menu, select thecommand, and do one of the following:
Select Standard to import a file that conforms to PDXpert's standard import format as defined below.
Select an optional import Data Transformation template that matches your CAD export file. (This template must be added by your application administrator before you can use it for importing a file.)
The Import Markup from File dialog opens.
Browse to your import file, and then click the Markup list.button. Your file is imported into the
Import files must have data in every row. Empty rows may cause an import to fail.
When you import a new file, the current BOM markup is first reset; all edited rows (including manual edits) are cleared before the new import file is applied.
If you discover an error after you accept the import, you can edit the records that you've imported, or import a new file to replace all edited rows on the markup.
Standard import file format—
PDXpert also imports a BOM using the following standard format, which you may configure your CAD to export. This format doesn't require a custom template, and can accept BOM files with very little information. Most properties are optional; if the column is omitted or the row's value is empty, the system assigns values as shown.
A column name — which your exporting software may call the column header or label — is recognized only if it exactly matches the name shown. All non-matching column names are ignored.
|Column name||Data type||Assignment if empty||Description|
|ChildClass||string Part or Document||Part||
If not specified, then the child item's Class is assumed to be a part.
Only parts can be added to the BOM list; a document row is ignored.
|ChildOwner||Organizations member name||default member (always the Home organization)||Identifies the organization that is primarily responsible for the child item's specification and which issues the item Number. Unless the system rule is modified, this should always be the full name of the home organization.|
|ChildType||Part Types member name||default member||
If not specified, then the appropriate type collection is determined by the child item's Class, and the default member of the resulting type collection is used to match the record's Type selection.
Only parts can be added to the BOM list; a row with ChildClass of Document is ignored.
|ChildNumber||string||row is skipped||REQUIRED: If the value is empty, the row is not imported.|
|Find||integer ≥ 1||last find-item + 1||
This value is assigned to the Find row identifier. Values on rows assigned to a single parent cannot be duplicated; that is, a parent assembly cannot have two rows with the same Find number.
The import file's Find value provides an anchor for comparing the current BOM revision to the previous BOM. If the Find column is not included in the markup file, the ChildNumber is used to identify differences between the previous BOM and the new import rows.
If you include a Find column, do not leave the values empty. The Find column is optional only when using the standard import format. When using a custom Data Transformations member, the import file must include a Find column.
|Quantity||double ≥ 0||1.0||This value is assigned to the row's Quantity value, and represents the number of child parts required to produce a parent.|
|Unit||Unit of Measure||default member||If the value is empty, then the part's Default unit of measure is applied.|
|RefDes||string: length ≤ 32000 characters||no value assigned||This value is assigned to the child part's RefDes ("reference designator") area.|
|Notes||string: length ≤ 32000 characters||no value assigned||This value is assigned to the child part's Notes area.|
|Per||string||Per Assembly||Must be assigned as Per Assembly, Per Setup, As Needed or remain empty.|
A minimal CSV file can be quite simple if it relies on the default column value assignments, and your system rule Item uniqueness defined by: has only the Number and Organization checkboxes marked:
Help Guide Contents [PDF]
- 0001. Welcome!
- 0002. Help conventions
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. Program concepts
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. Manage documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Save your document
- 1006. Remove your document
- 1007. Release your document
- 1008. Manage a released document
- 1009. Revise a released document
- 1010. Cancel a released document
- 1100. How to work with parts
- 1101. Manage parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add or remove references
- 1208. Save your part
- 1209. Remove your part
- 1210. Release your part
- 1211. Revise a released part
- 1212. Manage a released part
- 1213. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1402. Originate a new change form
- 1403. Analyze a submitted change
- 1404. Fix change processing errors
- 1405. Remove your change form
- 1406. Review a routed change
- 1407. Resolve an on-hold change
- 1408. Analyze an accepted change
- 1409. Use a released change
- 1410. View a completed change
- 1411. Analyze a stopped change
- 1412. View a rejected change
- 1413. Remove a canceled change
- 1414. Return a submitted change
- 1500. How to work with file attachments
- 1600. How to report, import & export
- 1601. Create a report
- 1602. Export a PDX package
- 1603. Use the Report/Export Wizard
- 1700. Import & update items
- 1701. Initialize your PLM database
- 1702. Use the External Data Importer
- 1703. Item Master import
- 1704. Iteration-level relational imports
- 1705. Bill of materials import
- 1706. References import
- 1707. Revision files import
- 1708. Sources import
- 1709. Item-level relational imports
- 1710. Item files & links import
- 1711. Materials import
- 1712. Groups collection import
- 1713. Materials collection import
- 1714. Organizations collection import
- 1715. Persons collection import
- 1716. Custom collection import
- 1800. View & export via ODBC
- 1801. View database objects
- 1802. Create an ODBC connection
- 1803. ItemViews reference
- 1804. ReferencePairViews reference
- 1805. SourcePairViews reference
- 1806. SourceItemMasterView reference
- 1807. StructurePairViews reference
- 1808. ChangeViews reference
- 1809. ChangePairViews reference
- 1810. FilePairMasterView reference
- 1900. How to perform other tasks
- 2000. Menu reference
- 2100. Item Explorer reference
- 2200. Document window reference
- 2300. Part window reference
- 2400. Change Form window reference
- 2500. System Rules reference
- 2501. System Rules window
- 2502. General: Copy files to snapshot
- 2503. General: Item uniqueness definition
- 2504. General: Reviewer's comment required
- 2505. Default File Access
- 2506. Password Policy
- 2507. References Tabs
- 2508. BOM: Allow duplicate parts
- 2509. BOM: Lock part default unit of measure
- 2510. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices