Fields

Backflush Item

Window Name: ‘Backflush Item’

Changing this field checks the Item Type, and if the Item is Misc Charges, Services or Flat Fee it gives a warning “You must backflush Service, Miscellaneous, and Flat Fee items.”.  The PPN field (Item Number) does not allow selecting those types of items and gives a warning “This Item cannot be built”, so there is no need to perform this check on the Backflush Item field.  It also sets a flag that the Backflush Status has Changed.

BOM Cost

Window Name: ‘(L) New Total’

Updated by clicking the Calculator button.

If PPN is FIFO/LIFO Periodic: BOM Cost is set to Item Master Standard Cost field.

If PPN is FIFO/LIFO Perpetual: BOM Cost is set by calculating the cost.  The routine explodes the BOM and calculates the cost based on the current cost of the components.  Phantom subassemblies are exploded and the cost rolled-up from the components within the Phantom.  It does not include labor from the routing.  Also, if there are Regular subassemblies, the cost for those comes from the Current Cost on Item Maintenance.

If PPN is Average: BOM Cost calculated from Purchase Receipts records.

BOM Name

Window Name: ‘BOM Name’

Change to this field runs Handle_Changes (see below).

If an existing BOM is displayed, changing BOM Name will release the lock on the old BOM and add a lock on the new BOM.

BOM Type

Window/Table Names: ‘BOM Cat’ / BOMCAT_I

The label on the window is “BOM Type” but the field is ‘BOM Cat’.

The Note next to this field is attached to the “BOM Type” field.  So a Note attached to “MFG BOM” when viewing 100XLG will also appear as a note when viewing the MFG BOM for CHAIR.  It is not linked to the Item Number.

Changing this field calls Handle_Changes (see below).

If BOM Type is changed to CONFIG, it checks the Fulfillment Method on Item Engineering.  If it is “Make To Stock” it will prompt: The recommended fulfillment method for an item with a super bill of materials is Make To Order-Manual. Do you with to continue or Cancel?  If you cancel, it sets the BOM Type to MFG BOM.

BUG: Select an Item with a MFG BOM.  Set the view to Where Used.  If BOM Type is changed to ARCH or CONFIG from any other BOM Type, and there are one or more named BOMs for ARCH or CONFIG, the window will retrieve the FIRST record.  You will see that the values Effective Date, Rev Level, BOM Category, and Backflush Item will populate, but the BOM Name field does not. (As of 27-AUG-2018)

Component

Window/Table Names:  CPN / CPN_I

The Note next to this field is the Item Master note.

Description (PPN)

Window/Table Names:  ‘Item Description’ / ITEMDESC

Displays the Item Description from Item Maintenance.  The button to the right of this field opens the View Drawings window.

Effective Date

Window Name: ‘Effective Date0’ (that is a zero)

Changing this field sets a flag that the BOM Header has been changed.

Item Number

Window/Table Names: PPN / PPN_I

The Item Number cannot be marked Inactive on Item Maintenance.

The Item Type on Item Maintenance can be Sales Inventory or Discontinued.  If the Item is Discontinued, you will be asked to confirm you want to proceed with a Discontinued item.

It calls Handle_Changes to address saving a previously displayed BOM (see below).

There must be an Item Engineering Record, and it must have a “BOM should treat as” setting of “Make” or “Make or Buy”.

It checks for Engineering Change Orders on the PPN and first level Components.  If there is, you will be asked to confirm you want to continue working with this BOM.

Defaults Revision Level to “1” if no BOM Header record exists.  Note that the “BOM Header” is stored in table BOM Revision.

It places a Lock on the BOM in BOM Security.

It calculates BOM Cost. See the BOM Cost field.

Quantity (Component)

Window Name: ‘(L) I_Quantity’

The note adjacent to this field is attached to the BOM Component, and is stored in BM010115.MFGNOTEINDEX_I.

When adding a Component, the Component’s Item Engineering Note is copied to the Quantity Note.  Changes to the Quantity Note do not affect the Item Engineering Note.

Quantity to Build

Window Name: ‘(L) QTY To Build’

If the Item Valuation is a Perpetual method, the BOM Cost field is updated via a SQL stored procedure called mbomExplodeBOMandRemovePhantoms.

If the Item Valuation is a Periodic method, the BOM Cost field is the PPN Item’s Standard Cost * Quantity to Build.

Rev Level

Window Name: ‘Revision Level’

PRE script – runs when entering the field.  It checks if the BOM Cat = 2 (Engineering BOM) and if the Company ID exists in ADConfiguration (ADSK0600).  If so, a warning is displayed (“Engineering BOM Revision Level cannot be modified”) and it prevents entering the field.

This is related to an obsolete AutoDesk PLM integration.  You can manually add a shortcut to access a Manufacturing window called Engineering Integration Setup.

If “Integrated with Engineering” is marked, it adds a record to ASDK0600.

CHANGE script: Checks if the entered Rev. Level already exists in the BOM_Revision_HIST table (BM010416), and if so, asks if you want to view the historical Bill of Materials.  If you answer YES, it opens the BOM in the BOM View window.  If you answer NO, it reverts to the original Rev. Level.

If the new Rev. Level does not exist, you will be asked if you want to save the current revision, or continue without saving it.  Saving the “current revision” makes a copy of the BOM Header and first level components into the BOM_Revision_HIST table (BM010416) and BOM_Line_HIST table (BM010116).

Processes

Handle_Changes

Called by: PPN when the PPN is changed, Treeview button.

Save_Record

Called by: Handle Changes when it detects a change to the window that needs to be saved.

Checks for any open Notes windows and will ask you to close them.

BUG: There is a bug with how the window handles open Item Engineering Note window (the note attached to the PPN).  It will prompt you to close the Notes window, but it does not stop itself from displaying the BOM for the newly entered Item.  

If you view the 100XLG BOM and add a note to the Item Number (PPN), it is the Item Engineering note.  If you then enter CHAIR, you will receive several warnings about needing to close the note window, but ultimately it will display the BOM for CHAIR and the note attached to 100XLG will still be open.  If you then save the note, it will be attached to CHAIR and 100XLG.

The Item Engineering Note index is stored in IVR10015.MFGNOTEINDEX_I, and it will be the same for both items.  The only way to fix this is to update IVR10015 to set MFGNOTEIDEX_I = 0 for one of the two affected items.  If you make frequent use of that note field, and repeatedly have it open when changing Item Numbers, it would be possible to duplicate the same Note Index on many items.

You can have a similar issue if the note next to Component Quantity is open and you click the Treeview button.

To prevent this problem you should establish a process where all notes windows are closed before saving/moving to another BOM. (As of 27-AUG-2018)

If Floor Stock is marked, it checks there is a Floor Stock Account assigned in Manufacturing Order Preference Defaults.

It checks that Position Number is not zero.  If the Position Number is the same as another component on the BOM, it will prompt to renumber the components.  It will be able to renumber the other components as long as renumbering does not push one or more components above 9999 (the maximum Position Number).

If BOM Type is ENG, ARCH or CONFIG, it requires a BOM Name.

If BOM Routing Links are present, and the Position Number changed, it will renumber the BOM Routing Links.  Also, if a Component Quantity was changed from positive to negative, or negative to positive, that change is applied to the BOM Routing Links.

Tables

BOM Revision (BM010415)

BOM Security (BMS10000)

Item Engineering (IVR10015)

MFG Notes (MN010000)