Copy BOMs

• Parent product (field ITMREF)

This parent product code describes what is referred to as a "Bill of Materials" or a "BOM". A BOM contains structured information for making and costing a product. It defines the components that make up a product, and given this, the cost of the product.

The parent product code is a stock code. It is the assembly or finished goods code.

• New product in design mode (field NPIPROLAB)

This warning is displayed if this parent product is still in design mode, that is this parent product has been created from a product design BOM revision that has only been released as a prototype product. It is not yet released as a full production BOM.

• Site (field STOFCY)

A site code is displayed if defined for the selected BOM alternative code. If this field is blank the BOM alternative code is not site-specific indicating, therefore, that this assembly can be used at all sites.

• Code (field BOMALT)

Multiple bills of materials (BOMs) can be defined for a single product. Each BOM code can be assigned specific management features. For manufactured or subcontracted products this includes restriction of the BOM to a specific site and to specific areas of functionality (for costing or for capacity planning).

Use this field to assign a BOM alternative code to this parent product code.

 See the Use status field (field LIBUSESTA) for tips on using this field in conjunction with the assembly status of this BOM.

• Reference date (field DATREF)

Today's date becomes the reference date for this parent product. It is assigned when you create the record but can be amended. The reference date must fall between the defined validity start date and end date. It will be used when this product is being selected.

 The reference date cannot be equal to zero.

• Major version (field BOHECCMAJ)

Use this field to indicate if this assembly (BOM) is for a specific major version of this product. Major versions might be used where there have been increased or significant changes in functionality.

If you are creating a new BOM and this product code is version managed, type in a major version code. You can create a BOM for any version of this product you choose. You are not bound by the versions stored against the stock record as you are assembling this product. The format of your code, however, must match the format for the sequence number counter defined on the stock record.

If you are revising an existing BOM the version is incremented according to the selected revision type.

This field is not available for entry if the product code defined in the Parent product field is not version managed.

 Commercial BOMs are not version managed.

• Minor version (field BOHECCMIN)

Use this field to indicate if this assembly (BOM) is for a specific minor version of this product. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

If you are creating a new BOM and this product code is version managed, type in a minor version code. You can create a BOM for any version of this product you choose. You are not bound by the versions stored against the stock record as you are assembling this product. The format of your code, however, must match the format for the sequence number counter defined on the stock record.

If you are revising an existing BOM the version is incremented according to the selected revision type.

This field is not available for entry if the product code defined in the Parent product field is not version managed.

 Commercial BOMs are not version managed.

• Change request (field CRID)

This field displays a change request ID if this product, or the specific version or revision of this product is associated with an 'active' change request. An active change request is a change request at the planning or implementation stage of the processing cycle. A warning icon is displayed adjacent this field.

If a warning icon is displayed you should consider delaying the creation or amendment of this assembly (BOM) until the change request identified is closed. At that point a change to this product will have either been seen through to its conclusion and the change delivered, or the change request rejected. You will not, however, be prevented from creating or amending this BOM should you decide to do so.

• Description (field BOMDESAXX)

Use this field to identify this product.

• Stock unit (field BOMSTU)

This field displays the unit for the parent product, as defined on the Stock record. It cannot be amended.

• Management unit (field QTYCOD)

Use this field to define how the quantities of the components needed to make this parent product are made up:

• One. Single units.
• Per hundred. Components must be in multiples of a hundred.
• Per thousand. Components must be in multiples of one thousand.
• Percentage. Components must be defined as a specific percentage of the total list of components, where the total list of components is 100 percent.
   By-products are excluded from the total percentage calculations.
   'Percentage' is not available if this is a Commercial BOM.
• By lot. Components are defined by the size of a specified 'lot'.

The selected management unit determines if the field Base quantity (field BASQTY) is initialized or available for entry.

• Base quantity (field BASQTY)

Entry of a base quantity is determined by the defined Management unit, as follows:

• In effect, if the management unit is expressed for 1 unit, for 100 units or for 1000 units the base quantity is forced to 1, 100 or 1000 units respectively.
• If the management unit is expressed as a percentage, the base quantity is 100 units.
• If the management unit is expressed for a "lot" you specify the base quantity. However, if the selected BOM code is assigned to a site, the base quantity is initialized for the lot size for this product for that site.
  
  

• Validity start date (field BOHSTRDAT)

Use this field to define the start date of this parent product's validity period. Alternatively, leave blank if this BOM is valid until the defined validity end date.

 All component validity dates and the reference date for this parent product must be within this date range.

• Validity end date (field BOHENDDAT)

Use this field to define the final date this parent product is valid. Alternatively, leave blank if this BOM is valid indefinitely (from the defined validity start date).

 All component validity dates and the reference date for this parent product must be within this date range.

• Use status (field USESTA)

This field indicates the assembly status of this BOM. This field will be set to one of the following values:

• In development, whilst the components that make up the product are being defined.
• Available to use, if the structure of the bill (BOM) is complete and has been validated.

 A BOM can only be assigned to work orders when its status is Available to use.

• Version start date (field ECCSTRDAT)

This field displays the start date of the displayed version's (major and minor) validity period.

• Version end date (field ECCENDDAT)

This field displays the final date of the displayed version’s validity period. This field is blank if the displayed version is the current, or active version.

• PLM document (field BUTATTURL)

Click the PLM document icon to open a Uniform Resource Locator (URL) to the technical BOM data in the Product Life Management (PLM) directories from @UDROS.

 Activity code PLM - PLM-X3 interface must be activated to import data from @UDROS.

• Allergens (field ALG)

This field displays allergen codes for the parent product.

 Activity code FOA - Food allergens must be activated to use allergen codes.

• Rollup date (field ALGDAT)

This field displays a rollup date if the rollup code corresponds with this parent product code. If the rollup code and this parent product code are different this rollup date is blank.

• Rollup code (field ALGBOM)

This field displays the BOM value of the parent product. An unmatched value indicates that a rollup has not been carried out on the current structure of this BOM.

• Lev. (field NIVBOM)

• Sequence (field BOMSEQ)

This field identifies the sequence number of this component in this BOM (bill of materials). It identifies a component where multiple components with the same product code are defined as variants or options.

The BOMSTE - Component sequence increment parameter (TC chapter, BOM group) defines the first sequence number and the increment applied to subsequent component sequence numbers.

• Component (field CPNITMREF)

Use this field to define the component product code.

 If this component currently exists in this BOM you must ensure the sequence number for this component is unique.

• UOM (field BOMUOM)

This field displays the unit of measure (volume or mass).

• UOM-STK factor (field BOMSTUCOE)

This field indicates the UOM-S conversion coefficient used to calculate the quantity in US, from a quantity entered in UOM: Qty in US = Qty in UOM * coeff.
This coefficient is initialized from the conversion factor table if the combination exists.

• UOM link quantity (field BOMQTY)

The link quantity specifies the number of components required for the basic quantity of the parent product.
It is entered in a variable format (fluctuating number of decimals).
For a management unit of Percentage, the sum of the link quantities must be equal to 100.

The corresponding value is initialized from the one defined at BOM level.

• STK link quantity (field LIKQTY)

The link quantity specifies the number of components required for the basic quantity of the parent product.
It is entered in a variable format (fluctuating number of decimals).
For a management unit of Percentage, the sum of the link quantities must be equal to 100.

• STK (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• Component type (field CPNTYP)

Use this field to define what type of component this is. You can set it to one of the following values:

• Normal. A component of this bill of materials.
• By-product. An unplanned by-product or secondary product.
• Text. Free-format text to be displayed on a work order.
• Costing. When a value must be calculated for the provisional cost and the production cost price of the parent product.
  
  

• Link quantity code (field LIKQTYCOD)

The code of the link quantity can be:

• Proportional: the quantity is multiplied by the required quantity for the parent product used in the processing,
  
• Fixed: the quantity is fixed regardless of the quantity required for the parent product.
  

• Qty rounding (field QTYRND)

The quantity of BOM links is entered with a maximum accuracy, which is not always useful for the stock management.
This code is used to manage the quantity rounding mode, based on the stock unit decimal, in the processes using the BOM.
The rounding can be to the nearest, highest or lowest.

• Link description (field BOMSHO)

This field displays the short description of the bill of material (BOM).

• % scrap (field SCA)

The loss percentage is used to increase the link quantity in order to take into account the loss due to the production process.
In the various inquiries, two quantities can be displayed:

• Net quantity: calculation of the quantity necessary to produce a parent product, without taking the loss into account.
• Gross quantity: calculation of the quantity necessary to produce a parent product, when taking the loss into account.
  
  

• Valid from (field BOMSTRDAT)

The validity start date is the date from which the link is valid.
It is initialized by default with the validity start date of the header. It remains modifiable but it must fall between the start and end dates of the validity displayed in the header.

• Valid to (field BOMENDDAT)

The validity end date is the date beyond which the link is no longer valid.
It is initialized by default with the validity end date of the header. It remains modifiable but it must fall between the start and end dates of the validity displayed in the header.

• From lot (field BOMSTRLOT)

For components that are managed by lot, this is the first lot for which this link is valid.

• To lot (field BOMENDLOT)

For components that are managed by lot, this is the last lot for which this link is valid.

• Routing oper (field CPNOPE)

If you do not need this component to be readily available at the start of the production process, use this field to define the specific operation or stage in the manufacturing process at which this component must be available to it. Holding back availability of this component until it is needed can be particularly beneficial in some circumstances. For example, for cost savings if this component is an expensive purchased product or storage costs are expensive, for saving on warehouse floor space if it has a large volume or for catering for specific characteristics such as a cooling period. 

This becomes the default operation number and can be changed for an order if necessary.

 The routing operation is referred to as the weighing 'phase' within the Weighing functionality (if you use the Weighing module).

• Ope LT (field BOMOFS)

The operation lead-time is used at the release and in the MRP calculation, in order to offset the component requirement with respect to the production start date of the parent product. This lead-time is expressed in business days.

• Mt. slip print. (field PICPRN)

Use this field to specify if this component must be printed on work order material issue slips.