Define Column Mappings - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

Before you can start the import operation, you must map the columns so that Smart Materials can store the data in the correct manner.

Open the B.10.41 Flat Configurations screen to define the FLC config with the column mapping.

At the top of the screen in the Flat Configs block, you must enter a name for the configuration to identify the mapping when you start the import later on the B.40.01 BOM Import screen.

Enter a unique name in the Config Name field and a description in the Comment field.

Enter a character in the Delimiter field for the column separator in the csv file. Leave it empty if you use the default delimiter ‘;’ or if you are importing from Excel files.

The number of lines to be skipped during FLC Load must be entered in the Skip Lines field.

Select the Summarize Positions check box if equal positions of a node should be summarized. In this context, equal means not only the basic position data like ident, unit, and so forth must be the same, but also the attribute values. When working with tag description multi NLS feature, tagged items are not summarized. Tagged items are also not summarized if the project default ZB_TAGQTY is set to Y.

If you want the import operation to include a check for CMS (Component Management System) idents, select a CMS class system from the LOV in the Class System field. During BOM import using FLC, the FIND_IDENT procedure finds the corresponding CMS ident based on a given set of CMS ident property values and the class system. The ident property values are defined using the FLC items POS_CATTR (Attribute Property) and POS_CTAB (Table Property). These FLC items are not available when a class system is not associated. Similarly, the FLC items POS_SPEC, POS_SHORT, POS_OPTION, POS_CC, POS_SIZE1...4, POS_IATTR, POS_TAB, POS_CG, and POS_CP are not available when a class system is associated.

If the FLC load does not import quantity units, the unit entered in the Quantity Unit field is used. Select the unit from the list of values. All units of the unit group QUANTITY are available. If the FLC load does not import length units, the unit entered in the Length Unit field is used. Select the unit from the list of values. All units of the unit group QUANTITY are available. Both units can be used in the CIP procedure omi_set_unit in the package m_pck_omi_custom to fill the unit field of the table m_flat_pre_imports during the import.

To assign BOM procedures to the flat config, click the BOM Procedures button. Window 2 opens where you can select procedures defined on B.10.21 BOM Procedures/Macros.

With the selection of Pre or Post in the last field, you define if the procedure runs before the import starts (pre) or when it is completed (post).

The Post procedures are not executed automatically during the import. If you run the import job with an enabled Pit Stop option, you must click the Run Procedures button. For more information, see Start Flat Loading Config Import.

Back on the main window of B.10.41, you can define a sort option for BOM position data within each end node. The sort order can be defined on the configuration header level using the Define Sort Order button.

Window 4 opens where the sortable items of the current configuration are displayed. Double-click the items in the Item field in the order you want to add them to the Sort Positions By field. You can add the keyword DESC so this column is sorted in descending order. To add this keyword, select the Descending check box and then double-click in the Item field.

The following items can be used for sorting if they are used in the selected config:

  • POS_IDENT

  • POS_CC

  • POS_CG

  • POS_CP

  • POS_ITR

  • POS_LSTAT

  • POS_OBJECT

  • POS_OPTION

  • POS_SHORT

  • POS_SIZEn

  • POS_SPEC

  • POS_TAG_NU

When you have added the necessary sort items, click the Apply button to apply this sort order. Window 4 is closed, and the defined sort order is displayed in the Sort Positions By field on B.10.41. Click the Cancel button to return to the configuration without applying changes. To clear the sorting field, you can click the Remove button.

If no sort order is defined, the software uses the standard sort order, which is the order of position data of the import file (fload_id).

In the Flat Config Items block, you define the column mapping. All columns of the file to be imported must be entered in the correct order of the occurrence in the file, without any gaps. If a column is not used in the Excel sheet, just choose IGNORE from the list of values in the Item field, so this column is not read during the import. Select the item from the list of values. The available items with their meaning are listed below.

Item

Meaning

GUID

Unique identifier for the record

IGNORE

Dummy column

NODE_ATTR

Horizontal Location and Interpretation of Node Attribute

NODE_LEV0N

Horizontal Location of 0th Node Name in Hierarchy on Position Level

NODE_LEV1N

Horizontal Location of 1st Node Name in Hierarchy on Position Level

NODE_LEV2N

Horizontal Location of 2nd Node Name in Hierarchy on Position Level

NODE_LEV3N

Horizontal Location of 3rd Node Name in Hierarchy on Position Level

NODE_LEV4N

Horizontal Location of 4th Node Name in Hierarchy on Position Level

NODE_LEV5N

Horizontal Location of 5th Node Name in Hierarchy on Position Level

NODE_LEV6N

Horizontal Location of 6th Node Name in Hierarchy on Position Level

NODE_LEV7N

Horizontal Location of 7th Node Name in Hierarchy on Position Level

NODE_LEV8N

Horizontal Location of 8th Node Name in Hierarchy on Position Level

NODE_LEV9N

Horizontal Location of 9th Node Name in Hierarchy on Position Level

POS_ATTR

Horizontal Location and Interpretation of Position Attribute

POS_CC

Horizontal Location of Commodity Code on Position Level

POS_CG

Horizontal Location of Commodity Group on position level

POS_CP

Horizontal Location of Commodity Part on position level

POS_IDENT

Horizontal Location of Ident Code on Position Level

POS_ISTAT

Issue status per node

POS_ITR

Horizontal Location of item rule on position level

POS_LSTAT

Horizontal Location of item rule on position level

POS_MAIN

Horizontal Location of main assembly position

POS_NUM

Horizontal Location of the position number

POS_OPTION

Horizontal Location of Option Code on Position Level

POS_QTY

Horizontal Location of Quantity on Position Level

POS_RTYPE

Horizontal Location of Record Type on Position Level

POS_SHORT

Horizontal Location of Short Code on Position Level

POS_SIZ2WU

Horizontal Location of Size2 with Unit on Position Level

POS_SIZE1

Horizontal Location of Size1 on Position Level

POS_SIZE2

Horizontal Location of Size2 on Position Level

POS_SIZE3

Horizontal Location of Size3 on Position Level

POS_SIZE4

Horizontal Location of Size4 on Position Level

POS_SPEC

Horizontal Location of Spec Code on Position Level

POS_SUB01

Horizontal Location of Sub Position Number at assembly level 1

POS_SUB02

Horizontal Location of Sub Position Number at assembly level 2

POS_SUB03

Horizontal Location of Sub Position Number at assembly level 3

POS_SUB04

Horizontal Location of Sub Position Number at assembly level 4

POS_SUB05

Horizontal Location of Sub Position Number at assembly level 5

POS_SUB06

Horizontal Location of Sub Position Number at assembly level 6

POS_SUB07

Horizontal Location of Sub Position Number at assembly level 7

POS_SUB08

Horizontal Location of Sub Position Number at assembly level 8

POS_SUB09

Horizontal Location of Sub Position Number at assembly level 9

POS_SUB10

Horizontal Location of Sub Position Number at assembly level 10

POS_SUM_ID

Summarize equal idents on position level

POS_TAB

Horizontal Location of a table detail to identify commodity code

POS_TAG_LO

Horizontal Location of tag number long layout (standard/login language) on position level

POS_TAG_L2

Horizontal Location of tag number long layout (second language) on position level

POS_TAG_L3

Horizontal Location of tag number long layout (third language) on position level

POS_TAG_NU

Horizontal Location of tag number on position level

POS_TAG_SH

Horizontal Location of tag number short layout (standard/login language) on position level

POS_TAG_S2

Horizontal Location of tag number short layout (second language) on position level

POS_TAG_S3

Horizontal Location of tag number short layout (third language) on position level

POS_UNIT

Position Quantity Unit (NO LENGTH but pcs, EA, and so on)

If you have assigned a class system to the flat config in the Class System field, you must assign these items to your FLC config:

POS_CATTR

Attribute Property

POS_CTAB

Table Property

  • The POS_CATTR and POS_CTAB items are not available when you haven’t assigned a class system to the FLC config.

  • The FLC items POS_SPEC, POS_SHORT, POS_OPTION, POS_CC, POS_SIZE1...4, POS_IATTR, POS_TAB, POS_CG, and POS_CP are not available when a class system is assigned to the FLC config.

The Values field also offers a list of values. The available values depend on the selected item. You cannot enter any value in the Value field where it’s not applicable, that is, for items GUID, IGNORE, NODE_LEVxN, POS_CC, POS_CG, or POS_CP.

If you want to specify a default value for the column, you can enter it in the Default field.

With regard to POS_ISTAT, this setting is on the node level. If the first row belonging to a node does not have a value for the issue status, the value from the import job is used. An LOV is available in the Default field for the POS_ISTAT item. If a value is entered in the Default field, it is applied to records where a value for issue status is missing.

Enter a comment in the Comment field to explain the purpose of the item.

The Consider Delta check box allows you to define whether that column must be considered when importing the same file again with updated data.

To make the input of column mapping easier to do, you can mark the Propose Sequence check box at the top of the block. When this option is selected, the next sequence number is entered automatically when you enter a new column.

Click the Resequence button at the bottom of the block to rebuild the sequence order after you have deleted records that have caused gaps in the sequence.

When the mapping is complete and all config items are entered, click the Validate button to check if all items are valid. If not, a message appears, informing you about discrepancies and how to correct them. Some columns are mandatory and must be entered. There must be nodes without gaps, node values, exactly one item and attributes. If any of these elements is missing, you are prompted about the necessary action to solve it.

With the Reset button, you can delete all internal temporary data and backups of the flat loading config import concerning the actual configuration. This action does NOT delete any imported BOM.

Click the Templates button to create a new configuration from a standard FLC template delivered with the product. Window 3 opens, and all templates are listed.

The following standard FLC templates are available:

Tool Name

Report

Config Name

Comment

SmartMarine 3D

Plates

3D PLATES

SmartMarine 3D Plates Report

SmartMarine 3D

Profiles

3D PROFILES

SmartMarine 3D Profile Report

Intergraph Smart™ 3D

Cable Tray

3D CABLETRAY

Smart 3D Cable Tray Report

Smart 3D

Handrail

3D HANDRAIL

Smart 3D Handrail Report

Smart 3D

Piping

3D PIPING

Smart 3D Piping Report

Smart 3D

Steel Structure

3D STEELSTR

Smart 3D Steel Structure Report

Select the template you want to use, and click the Start button to copy the config items to the FLC config. If you create an FLC config by copying the items from a standard template, it is recommended that you do not change it.

In this template, each column expected to be loaded is configured by the following fields:

Sequence - The sequence of columns in the file.

Item - Defines the type of data being loaded from the current column.

Value - Value has an item-dependent meaning. A context-sensitive LOV is available.

Value required - This item needs a value defined if checked. If it is not defined, the template is not copied into the FLC configuration.

Auto Create - If this box is checked by the software, it tells the user that the item will be created automatically by the software in all relevant tables and screens. For example, an attribute, which at this point in time is not defined for BOM usage, but configured here in the template as such, will be created automatically. This auto-creation saves a lot of configuration time.

Report Column - An information field that lists the name of the column used in the MTO XLS report before the header was deleted.