Import files into the staging table

This scenario assumes that the engineering department works with a system that delivers files for changed products and bills of material (Windchill, Teamcenter). The file layout is either CSV or XML, and combinations of fields determine the type of change to be processed. The sequence of imports is important: to substitute an item with a new item, first import the new item before importing the substitute. The list below shows the supported transactions from the staging table with examples of the fields that the import file must provide.

Steps

Specific mapping rules:

1. Items, when new items are created, the item information is completed based on a template set in the Engineering Change Management Setup.

2. Item variants are supported, when specified, the system either creates a new variant or updates an existing one.

3. Item substitutions are supported, when a Substitution Type and No. are specified, it is assumed that the dependent line is a new item for which a separate ECO is created. When processing the ECO, a check is made whether the new item exists. If not, an error requests the user to first process the ECO for the new item.

4. When a Production BOM No. is specified, it is assumed that the Production BOM No. is the same as the parent item of the BOM. The lines that contain the Production BOM No. are then considered component lines and created with a line number.

5. Based on the settings in the Engineering Change Management Setup, a BOM is either replaced or created as a new version. When Create BOM Version is checked, the new version is created with the revision code as the version number. The same method applies to the routing.

Import a new or changed item

Import an item substitute

Import a Bill of Material

Import a Routing