Fabrication Tracking - Spool Import Mode - Intergraph Smart Materials - Version 10.2 - Help - Hexagon

This import mode has been implemented based on the following requirements:

• The ability to build a single identifier for each spool piece

• The ability to receive a list of spool numbers associated to a BOM node from fabricators

• The ability to associate spool numbers to BOM nodes via OMI import

• The ability to process spool numbers throughout the complete Smart Materials workflow, which includes Expediting and Traffic in the Procurement module, as well as Receiving and Issuing in the Site module

The basic solution to these requirements is three-fold:

1. Distinguish spool number BOM items from all other BOM items by means of the item rule that is attached to the item type. Spool number BOM items always have an item type with item rule TFM, whereas "normal" BOM items use item rules as outlined in Tagged Items.

2. For TFM (Spool) BOM items, interpret the physical BOM tag number as the spool number.

3. Completely separate TFM item processing by OMI from non-TFM item processing.

This approach makes it possible to manage the complete cycle of expediting traffic, and receiving and issuing spools using Smart Materials standard functionality for tag number processing throughout the complete workflow.

The OMI interface therefore implements the following behavior with respect to BOM item types:

OMI allows import to existing nodes based on the TFM item type. In Fab spool import mode, only TFM items can be imported. In normal import mode, only non-TFM items can be imported. There cannot be a mixture of these item types in the same OMI job run; although, of course, there can be a mixture of these item types located at the same BOM nodes. The OMI import mode is specified by a check box for the job definition on the B.40.01 screen.

• When using the "Fab Spool Import" mode (that is, only TFM spool items are to be imported), it is necessary that the ZB_TFMPART project default parameter be set to a valid commodity part; otherwise, job execution fails with an error message.

• When TFM (non-TFM) items are to be imported with a specific issue status, and TFM (non-TFM) items present on the BOM in this issue status have Site quantities (that is, reserved qty, issued qty, or both), this BOM position data set is rejected. In this case, only importing with a higher issue status is allowed.

• When TFM (non-TFM) items are to be imported with a specific issue status, and TFM (non-TFM) items present on the BOM with a lower issue status (that is, one with a lower order sequence number) have Site quantities, it is necessary that the ZI_OMI_TSQ project default parameter be set to 'Y' in order to allow OMI to apply the Site Quantity Transfer algorithm. Otherwise, this BOM position data set is rejected.

• When importing TFM (non-TFM) items to a present BOM node with a new highest issue status, present non-TFM (TFM) items at this BOM node (that is, items of a type with the opposite rule) with the current highest issue status are moved up to the new highest issue status (which means that they are updated; please be especially aware that they are NOT COPIED to the new status, they are MOVED) in order not to change the MTO or Forecast/reservation job's view at the BOM data.