Product Engineering - Engineering Change Management
How To: Import files into the Staging Table
This scenario assumes that the engineering department works with a system which is capable of delivering files for changed products and bills of material (Windchill, Team center).
The file lay-out is either csv or xml and combinations of fields determine the type of change to be processed. Obviously the sequence of imports is important i.e. in order to substitute an item with a new item first the new item needs to be imported before the substitute can be imported. The list below mentions the supported transactions from the staging table with examples of the fields that have to be provided by the import file:
Specific mapping rules:
- Items, when new items are created the item information is completed based on a template set in the ECM Setup
- Item Variants are supported, when specified the system will either create a new variant or update an existing
- Item Substitutions are supported, when a Substitution Type and - No. are specified it is assumed that the dependant line is a new item for which a separate ECO is created. When processing the ECO a check is made if the new item does exist, if not an error will be thrown requesting the user to first process the ECO for the new item.
- 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 to be component lines and created with a line number.
- Based on the settings in the ECM Setup a BOM is either replaced or created as a new version. When the ?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 a changed Item
| Field | Example |
|---|---|
| Type | Item |
| No | 1002 |
| Variant code | |
| Description | New Bicycle |
| Description2 | |
| Unit Of Measure Code | PCS |
| Class | |
| Vendor No. | |
| Vendor Name | |
| Item Category Code | MISC |
Import an Item Substitute
| Field | Example |
|---|---|
| Type | Item |
| No | 1000 |
| Variant Code | |
| Description | Bicycle |
| Description2 | Substituted |
| Unit Of Measure Code | PCS |
| Class | |
| Vendor No | |
| Vendor Name | |
| Item Category Code | MISC |
| Substitution By Type | Item |
| Substitution By No | 1002 |
| Inter Changeable | |
| Substitution Condition | Upgraded |
Import a Bill of Material
| Field | Example | Example |
|---|---|---|
| Type | Production BOM | Production BOM |
| No | 1002 | 1100 |
| Variant Code | ||
| Description | Bicycle New | |
| Description2 | ||
| Unit Of Measure Code | PCS | PCS |
| Class | ||
| Vendor No | ||
| Vendor Name | ||
| Production Bom No | 1002 | |
| Production Bom Version No | 1000-2 | |
| Production Bom Version Date | 1-12-2015 | |
| Length | ||
| Width | ||
| Depth | ||
| Weight | ||
| Prod Bom No Series | ||
| Prod Bom Version No | ||
| Position | ||
| Position2 | ||
| Position3 | ||
| Lead Time Offset | ||
| Routing Link Code | ||
| Scrap | ||
| CalculationFormula | ||
| QuantityPer | 1 |
Import a Routing
| Field | Example | Example |
|---|---|---|
| Type | Routing | Routing |
| Routing Type | Serial | |
| Routing No | 1002 | |
| Routing Version No | ||
| Routing No Series | ||
| Routing Version Nos | ||
| Routing Operation No | 10 | |
| Routing Line Type | Work Center | |
| Routing Line Type No | 100 | |
| Routing Work Centre | ||
| Routing Setup Time | 80 | |
| Routing Run Time | 10 | |
| Routing Wait Time | ||
| Routing Move Time | ||
| Routing Setup Time Uom Code | ||
| Routing Run Time Uom Code | ||
| Routing Wait Time Uom Code | ||
| Routing Move Time Uom Code | ||
| Routing Minimum Process Time | ||
| Routing Maximum Process Time | ||
| Routing Concurrent Capacities | ||
| Routing Send Ahead Quantity | 1 | |
| Routing Routing Link Code | ||
| Routing Standard Task Code |
See also
Reference
Feedback
Submit feedback for