Object Codes and Recognize Mode - Intergraph Smart Materials - Version 10.2 - 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.2

In normal mode, OMI does not apply any special logic to the object code field on position records. You can specify, however, that you want to run the import job in recognize mode. The recognize mode (not for item rule SHP) then uses a fundamentally different import processing logic: in this mode, the object code has the purpose to uniquely identify existing BOM positions in the context of the current BOM path (and of course, in its substructure) and then to apply the data modifications from the import file to these positions. In comparison to the normal OMI import mode, the following processing rule differences are in effect when the recognize mode is used:

  1. Node Path descriptions - As soon as a valid BOM path is available by interpretation of the import data, all existing positions in the substructure of the current BOM node are checked for uniqueness of their object code fields. If there are duplicate object codes present, the processing of this part of the BOM is cancelled, and processing continues with the next NODE_BEGIN record. The central prerequisite for recognize mode operation is met: the ability to identify positions only by the object code.

  2. BOM positions - If for a specific node, there are positions in the import file, as a first step, all positions at this node that have an object code are marked. During subsequent steps, all import records for these nodes that also have an object code are processed and their marks are reset. As a consequence, after processing of this node is finished (that is, when another NODE_BEGIN or NODE record appears), all positions from this node that still have the mark from the first step set are not included in the import file. These positions are moved (operation move-out) to the temporary recognize mode "exchange" m_list_pos_objects table, thus logically deleting them from the current BOM node. On the other hand, if positions with an object code are encountered and processed, a matching position with the same object code is first searched for in this "exchange" table, before the object code is searched on the BOM. The net effect of this processing is that by means of an object code specification, specific BOM positions may be moved from one BOM node to another BOM node, using the m_list_pos_objects table as temporary storage (also referred to as an "exchange area" in the OMI import protocol).

    Positions that could not be recognized (that is, they could neither be found in the exchange area nor on the BOM) are simply created as a new position by OMI. If a position can be recognized in the exchange area, it is "moved in", that is, it is created at the current node, and then updated according to the current position record. If a position can be recognized at the current node, there is no need to move it, so it can simply be updated according to the current position record and location.

    Updated position fields in recognize mode are:

    • Quantity

    • Quantity Unit

    • Created By (will be set to 'OMI Recognize')

    • Spec Code

    • Short Code

    • Option Code

    • Group/Part/Commodity/Ident Code

    • Input 1 - Input 5

    • Tag Number

    • Object Code

    • recognize_id (only used internally for the recognize mode algorithm; it has no inherent meaning)

      Processing of position attribute records in recognize mode does not differ from normal mode processing.

      Positions at locked nodes are not processed (specifically, they are NOT moved) unless the import job parameters also allow a revision increment.

  3. Extended Logging in recognize mode - If the recognize mode is in effect, more detailed information on the operations taken (that is, move-in, move-out, update of recognized positions) is written to the OMI import protocol, additionally stating the BOM path, the object code, and the position number (as found for the import record). Furthermore, the main log statistics section displays the overall number of such operations.