What are the relevant project/discipline defaults settings that I should know about? - Intergraph Smart Materials - 10.2 - Help - Hexagon

Intergraph Smart Materials Web Help (10.2)

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

The relevant project/discipline default settings that you should know about before an import job are given below:

Project Defaults

Descriptions

ZB_BOMHIER

Specifies whether free or fixed BOM hierarchies are allowed.

ZB_LPSTART

Starting BOM position number.

ZB_LP_INC

Increment for BOM position number.

ZB_LST_ID

Default list status for new BOM positions.

ZB_NODE_UK

If this project default is set to Yes, the node names for a node type must be unique within the project. When the software tries to import a node name that already exists for the node type in the project, this setting causes an error message to be written in the log file, and the node is not imported.

ZB_STAT_ID

Default issue status for new BOM positions.

ZB_TAGPART

Default commodity part for tagged items. May be overridden by a group/part specification in the import data.

ZB_SH_PART

Default commodity part for shape tagged items. Cannot be overridden by a group/part specification in the import data.

ZB_TAGQTY

Specifies whether for tagged Items any quantity other than 1 is allowed or not (not for item rule SHP).

ZB_VALNODE

If this project default is set to Yes, only the node names pre-defined on the Node Types page for the corresponding node types can be created during the BOM import. If a node name in the OMI file does not match any of the node names specified on the Nodes and Settings page, the node is not created and an error message is written to the log file. If the short description or the description for the node does not match the values pre-defined on the Nodes and Settings page, the pre-defined short description or description is used while creating the node. A warning is written to the log file.

ZI_OMI_CM

OMI company mapping option. Specifies whether in company mapping import mode, only company ident codes are accepted (option COMP), or company ident codes as well as Smart Materials ident codes (option BOTH) are accepted. The default is COMP. For the latter case, you can also specify a mapping priority with ZI_OMI_CMP.

ZI_OMI_CMP

OMI company mapping priority. For company mapping import mode with mapping option BOTH (see ZI_OMI_CM above), this option specifies which ident OMI should use if a company ident as well as a Smart Materials ident is available for a specific ident code. Available options are COMP (this option uses the company ident), MAR (this option uses the Smart Materials ident), and REJ, which disallows ambiguous ident codes, rejects the position record in such a case, and writes an error entry to the OMI log.

ZI_OMI_IN

Default directory for OMI files, defined on the project/discipline level. If it is not set up on this level, the global configuration parameter BOM_IMPORT_PATH value .is used. Please note that these configuration options only influence what value is returned when you click the Default Dir button on this page. You can at any time specify the directory and file location information manually, without needing to configure these settings at all. These settings just allow a Smart Materials application administrator to make the use of OMI more convenient for users.

ZI_OMI_OPT

This project default is now obsolete. Instead, you can specify a data source on a per-job basis directly on the BOM Import page.

ZI_OMI_POS

Specifies the method OMI should use for creation of position numbers for imported BOM positions. The AUTO setting means that OMI does not care about the data content of the position number column from the ASCII file, but instead builds position numbers automatically, based only on ZB_LPSTART and ZB_LP_INC. On the other hand, the DATA setting means that the position number is a required field in the ASCII file that OMI must use on the BOM. For position records where the position number is missing, an error message is generated and the position rejected.

ZI_OMI_DCC

Design Change Control option. This option only takes effect if the site qty transfer option (ZI_OMI_TSQ) is also enabled. If set to Y, OMI will perform automatic cancellation of over-reserved quantities, automatic re-issuing of design change quantities to appropriate design change warehouses, and automatic logging of reservation shortages, if it encounters such situations during load of a new highest issue status position data set into a BOM node.

ZI_OMI_DCA

Design Change Automatic Acknowledgment option. This option specifies how OMI should handle old unacknowledged design change control log entries it may encounter during loading of a new highest issue status position data set into a BOM node. Possible values are: ERR, ACK, and DEL. The default is ERR. These setting values have the following meanings:

ERR: Raise an error and reject the BOM node. This value implies that a new issue status cannot be loaded unless all design change log entries have been explicitly acknowledged.

ACK: Automatically acknowledge the design change for the old highest issue status and keep the log entry. ACK also implies that you cannot delete the OMI job on the BOM Import page after applying a design change, because this job then becomes part of the design change history. The software needs to keep the OMI job along with the design change log entry for future reference.

DEL: Ignore the unacknowledged design change for the old highest issue status and delete the log entry.

ZI_OMI_TBT

OMI batch lock timeout (maximum allowable lock wait time specified in minutes).

ZI_OMI_TON

online lock timeout (maximum allowable lock wait time specified in seconds).