Configure PDS BOM Import - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Web Help (10.1)

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

The Configure PDS BOM Import page is used to spool out your items to the file system using various formatted reports. This page allows you to configure where OMI can find the data. It is necessary that you define at least one configuration and reference to it in BOM Import page to enable the OMI reading from the appropriate report. Each configuration can be used system-wide. For each configuration set, you configure the items that are important for OMI to read.

What are the available configuration item types needed to define a new configuration?

When you define a new configuration item, you must assign a type from the select list in the Type field in the BOM Configuration Items block. The available values are as follows:

  1. Column (C) allows you to define the horizontal position of the item in fixed column numbers. The Digit from value is the first column to be read while the Digit to value is the last column to be read. Both these fields must be filled if you use this type for an item. The fixed column numbers are read before the sequential order information, which means that when you begin to specify an item as sequential (Sequence), you cannot return to fixed column numbers. If you use Column, you can use the same position in ASCII to feed multiple configuration items.

  2. Sequence (S) allows you to define the horizontal position of the item in sequence with the lowest first and highest last. The Seq field contains the sort order, which defines when the specified item is expected in the file. The step size of the sequence value can be different from 1, and the first sequence number can be different from 1. You can even use negative values. The Length field contains the last column to be read. The length is counted from the beginning of the new item. Leading blanks are not considered. While the Seq value is mandatory, the Length value can be omitted.

  3. Other (O) ensures that the configuration item has neither fixed-column nor sequential information.

What are the configuration items that are supplied with the parameters?

The Item field contains the name of the configuration item that you want to supply with parameters. The available items can be selected from the LOV. The LOV automatically fills some of the other fields with defaults, so you can easily achieve a default configuration.The configuration items in detail are as follows:

  • LINE_NUM: You can define the horizontal location of the line number. In the field 'Value' you can enter your line number title which can differ from the literal 'LINE NUMBER'. This is information is used to identify a physical line in the report as line number information. If you don't use this configuration item, the standard PDS defaults take place.

  • LINE_TYPE: This defines, which node type the line will have in the BOM. Choose from the available node types with LOV on field 'Value'. Notice, that the node type code is stored, and no internal id. So the node type for every project can be the same. This configuration item is required to be defined by you. There is no default by the system.

  • LINE_ATTR: You can have the interface interpreting you line number and making node properties of it. Specify the name of the property in the field 'Value' and enter the location in the digit-fields. You can have more than one usage of LINE_ATTR by selecting this Item for more than one row in the block. If you don't use this configuation item, the line number is stored in the short description, description of the node and no node properties are generated. Notice, that the property code is stored, and no internal id. So the property code for every project can be the same.

  • LINE_SEP: If you choose to define relative locations, you can herewith define the seperator symbol within the line number. If you omit this configuration item, the dash is taken per default. Refer to description of the field 'Type' for further information on defining relative or fixed locations.

  • POS_ATTR: You can transfer an unlimited number of position properties for each position. Enter the location of the position property in the digit-fields, and the name of the property in the value-field.

  • POS_CC: Enter the location of the Commodity Code in the digit-fields. Trailing and leading blanks are cut off automatically. If you omit this configuration item, the defaults from PDS piping_g take place.

    The piping_g control file is used for loading PDS BOM reports into Smart Materials.

  • POS_CIP1 ā€“ 3: This values will not be inserted by the standard-procedure into the BOM. You can use it e.g. for any customized code in m_pck_pds_bom_custom.

  • POS_IDENT: Enter the location of the Ident Code in the digit-fields. Trailing and leading blanks are cut off automatically.

  • POS_LSTAT: You can define the list status of the position. If there is no entry in the ASCII file, the default value of the configuration will be taken. If also the default value in the configuration is not filled the default value entered in the BOM Import page will be taken.

  • POS_MODEL: Model Code from PDS. This value will not be inserted by the standard-procedure into the BOM. You can use it e.g. for any customized code in m_pck_pds_bom_custom.

  • POS_LEVxN: The name of the node level x where the material is to be stored. You can create up to 10 levels (beginning from 0 to 9) from the start node defined in the BOM Import page. If the node does not exist in the BOM, it will be created.

  • POS_LEVxT: The type of the node level x where the material is to be stored. You can create up to 10 levels (beginning from 0 to 9) from the start node defined in in the BOM Import page. The node type is needed, when new nodes must be created within the BOM tree.

  • POS_OPTION: Enter the location of the option in the digit-fields. Trailing and leading blanks are cut off automatically.

  • POS_SHORT: Enter the location of the Short Code in the digit-fields. Trailing and leading blanks are cut off automatically. If you don't have a Short Code in your file, the program will search one with the Spec Code, Option Code and Commodity Code. If there is nothing found, the program will receive an error. It is a good idea to define a Short Code ERROR. The program will then assign this Short Code to the item, where no Short Code was found, and the import will succeed. You will be informed which line was not imported because ERROR was not in the spec.

  • POS_SPEC: Enter the location of the Specification Code in the digit-fields. Trailing and leading blanks are cut off automatically.

  • POS_RTYPE: Enter the location of the Record Type in the digit-fields. Trailing and leading blanks are cut off automatically. The Record Type influences the interpretation of the POS_QTY. This configuration item is normally not used with "piping_g"-like formats. If the RTYPE is PIPE or BOLT, missing quantities don't default to 1. If you do not specify an RTYPE it defaults to BOLT. If the RTYPE is PIPE, the program appends a ".0" to integer quantities, if no unit is specified. This ".0" makes the program assume a length unit for the quantity because of the decimal point. If the RTYPE is BOLT, and the program fetches commodity code with sizes from Smart Reference Data, the bolt also receives a second size (the bolt length) if the input2 is numeric - regardless whether the bolt is marked as one-size or two-size item. Additionally, if there is an input2 (bolt-length) in the ASCII file, the program will compare the input2 from ident with the input2 from ASCII. If they are different, the program will try to find another ident within the same Commodity Code which matches the bolt diameter and length. If an ident was found, it will be taken instead of the one originally coming with the ASCII. If no ident found, an error message is written to the job logfile, and the ident is erased. Instead, the BOM position will contain the commodity code, input 1 (bolt diameter) and the new bolt length.

    If the RTYPE is COMP, the program converts the quantity to number, if no unit is specified. This conversion cuts trailing zeros and makes the program assume a piece unit for the quantity because of the decimal point. To make the RTYPE being noticed, the RTYPE must be defined left from the quantity or size2 in the ASCII file.

  • POS_QTY: Enter the location of the position quantity in the digit-fields. Trailing and leading blanks are cut off automatically. If the Record Type (as far as existing) is BOLT or PIPE, the quantity is set to zero if none found on the line. If the Record Type is different, the missing quantity is defaulted to 1. If there is no Record Type, the missing quantities are left out. If you omit this configuration item (POS_QTY), the defaults from PDS piping_g take place.

  • POS_UNIT or POS_LUNIT: The OMI Pre-processor does not know if a quantity is a piece unit (POS_UNIT) or if it is a length unit (POS_LUNIT).

    If the RTYPE is PIPE or BOLT, missing quantities don't default to 1. If you do not specify an RTYPE it defaults to BOLT. If the RTYPE is PIPE, the program appends a ".0" to integer quantities, if no unit is specified. This ".0" makes the program assume a length-unit for the quantity because of the decimal point. If the RTYPE is COMP, the program converts the quantity to number, if no unit is specified. This conversion cuts trailing zeros and makes the program assume a piece-unit for the quantity because of the decimal point. To make the RTYPE being noticed, the RTYPE must be defined left from the quantity in the ASCII file.

    1. If the quantity is blank:

      • If the RTYPE is blank (i.e., it is set to PIPE or BOLT), the quantity is set to 1 and the unit defaults to 'EA'.

      • MM is used if POS_LUNIT is blank.

      • EA is used if POS_UNIT is blank.

    2. If the quantity is not blank:

      • MM, mm, or INAny unit is used if it is appended to the quantity in the ASCII file. If the quantity includes it You may also use '"' to get the unit IN. Note, that the unit is case sensitive.

      • POS_LUNIT is used if the quantity contains a decimal point as a separator (delimiter).

      • POS_UNIT is used is the quantity does not contain a decimal point as a separator (delimiter).

  • POS_SIZE1: Enter the location of the 1st size in the digit-fields. Trailing and leading blanks are cut off automatically. If you omit this configuration item, the defaults from PDS piping_g take place.

  • POS_SIZE2: Enter the location of the 2nd size in the digit-fields. Trailing and leading blanks are cut off automatically. If you omit this configuration item, the defaults from PDS piping_g take place. This field is used for diameters, not for schedules. If you transfer schedules for some reason, and you supply a commodity code (POS_CC), the BOM import will erase the schedule depending on the Zydex table in Smart Reference Data.

  • POS_SIZE3: Enter the location of the 3rd size in the digit-fields. Trailing and leading blanks are cut off automatically. You only need this item to find idents for material which has more than one end and is to be found by Commodity Code and sizes.

  • POS_SIZE4: Enter the location of the 4th size in the digit-fields. Trailing and leading blanks are cut off automatically. You only need this item to find idents for material which has more than one end and is to be found by Commodity Code and sizes.

  • POS_SEP: If you choose to define relative locations, you can herewith define the separator symbol within position line. If you omit this configuration item, the blank is taken per default.

  • POS_SUM_ID: If you want to summarize material which has the same ident within the same node/list status/issue status, set this item to the value Yes, Y, True, 1, or ON. If you don't want to sum up, you can omit this configuration item. Summarizing will only take place for material which is characterized by the same parameters. For example, if one position has only the ident code while the other has no ident but spec, short code and size information, these cannot be added, even if they refer to the same ident. They will remain as two separate positions. Summarizing will only supply the correct values, if they are of the same unit. The unit will not be converted to each other by the program. If you add 1 meter pipe to 3000 mm pipe the result will be unpredictable.

  • POS_TAG_NU: Enter the location of the tag number in the digit-fields. If a tag number occurs without ident on one ASCII line, it is treated as item rule TWM. User can submit CCL short/long to create CC. If a tag number occurs together with an ident, the item rule will be considered as SWT.

  • POS _TAG_SH: Enter the location of the tag number short layout in the digit-fields. This setting is only of interest, if you are working with POS_TAG_NU and create tags with item rule TWM.

  • POS _TAG_LO: Enter the location of the tag number long layout in the digit-fields. This setting is only of interest, if you are working with POS_TAG_NU and create tags with item rule TWM.

  • POS_CC_MAP: This item defines how to process the company and/or interface commodity codes on a position level. For Company Ident Codes, you also need to set POS_CC_MAP to indicate that you want to map, although the value of POS_CC_MAP is not relevant. Company Ident Codes are always looked up first. If not found in project/product group, a SRD Ident Code is assumed. Interface Ident Codes are not supported. If you plan to use only Smart Reference Data codes in your OMI load, do not include the POS_CC_MAP configuration item in your config, to save time which is spent looking up company- and interface-mapping tables.

  • POS_COMP: You can use this to consider the company codes provided in PDS BOM Import Configuration page while importing corresponding commodity codes when performing the PDS BOM import with Company commodity codes in SMAT. When POS_CC_MAP contains the value of C (Company CC), then company selected under POS_COMP value is considered for company commodity mapping during PDS BOM import.

  • POS_NATTR: You may specify an arbitrary number of node properties for each node of the BOM structure. Enter the location of the position property in the digit-fields, and the name of the property in the value-field. To transfer the properties correctly, the first position row which is on another (or on the very first) node must contain the node properties with their values. The node property information on all following position rows for the same node in the import file will be simply ignored.

  • POS_IATTR: You may specify an arbitrary number of ident properties for each position of the BOM structure. Enter the location of the ident property in the digit-fields, and the name of the property in the value-field. Using ident properties will cause the preprocessor relate the material to the item rule TAB, unless you specify otherwise with POS_ITR.

  • POS_ITR: You may specify the item rule explicitly in the ASCII file. Enter the location of the item rule in the digit-fields. If you don't specify the item rule, following rule applies: If a tag number occurs without ident on one ASCII line, it is treated as item rule TWM. If a tag number occurs together with an ident, the item rule will be considered as SWT. If there is no tag number specified, item rule will be SOT.

  • POS_CG: The commodity group can be submitted in the ASCII file. Enter the location of the commodity group in the digit-fields.

  • POS_CP: The commodity part can be submitted in the ASCII file. Enter the location of the commodity part in the digit-fields.

  • POS_NUM: The position number can be submitted in the ASCII file. Enter the location of the position number in the digit-fields. To transfer position numbers, you have to set the project default ZI_OMI_POS to DATA.

  • POS_PROJ: The destination project can be submitted in the ASCII file. Enter the location of the project in the digit-fields. If this does not match the Reference Data project the user starting the job is logged into, the OMI program aborts the import process with an error message. This helps to minimize the possibilities for user errors. It does not make sense to have different project names on different ASCII lines in the same file. The pre-processor will read the first project entry, and ignore all following occurrences.

  • POS_ISTAT: You can define the issue status of the node. It will be entered on the end node. If there is no entry in the ASCII file, the default value of the configuration will be taken. If also the default value in the configuration is not filled the default value entered in the BOM Import page will be taken.

PDS BOM Import Configurations