Multilevel BOMs

• BOM type (field BOMALTTYP)

Select Manufacturing if you manufacture this bill of materials (BOM). If it is procured from a subcontractor select Subcontracting. This field is not available for selection if you have accessed this function directly from the Production BOMs or Sub-contracting BOMs function.

• Storage site (field STOFCY)

• Parent product (field PARITMREF)

This field indicates the ID of the component product.

• Code (field BOMALT)

Several BOMs can be defined for the same product reference.
They can be distinguished via the code, entered on two numbers.

The various BOM codes can be used to manage different product structures according to their use context such as:

• MRP calculation,
• Sales order entry
• Manufacturing/production

This field can be left empty (value = 0) to enable manual entry of the components. In this case, only the component is loaded.

• Reference date (field DATREF)

The reference date is used to select the products according to their validity start date and end date.
The entry of a date dated 00/00/00 is used to select all the products irrespective of their validity date.

 The reference date cannot be equal to zero or be earlier than the current date.

• Major version (field VBOGECCMAJ)

This field indicates which version of this product applies. Major versions might be used where there have been increased or significant changes in functionality.

To view the details of a different version of this product type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Parent product field is not version managed.

• Minor version (field VBOGECCMIN)

This field indicates which minor version of this product applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

To view the details of a different version of this product type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Parent product field is not version managed.

• Description (field BOMDES)

• 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)

The management unit is used to define the quantity of the BOM links on another basis than the product unit.
It is thus possible to enter a BOM for 1 product unit, 100 product units, 1,000 product units, in percentage or for a specific product lot size.
In the percentage definition, the total link quantities must be equal to 100.
The basic quantity section is initialized or entered depending on the chosen management unit.

• Base qty (field BASQTY)

The base quantity entry depends on the management unit chosen:

• the management unit is equal to 1, 100, 1000 or is expressed as a percentage. the base quantity is forced respectively to values 1, 100, 1000 or 100,
• The management of the unit is set by lot: the base quantity can be entered.
  If the BOM code is dedicated to a site, it is initialized by lot size of the product for the site.

• Validity start date (field BOHSTRDAT)

The BOM header shows validity start and end dates.
If the start date is not entered, it means that the BOM is valid for a date prior to the end date.
If the end date is not entered, it means that the BOM is valid for a date greater than the start date.
Validity dates are also associated with the links. They are initialized according to the dates in the header and must be within this date range.

• Validity end date (field BOHENDDAT)

• 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.

• Use status (field LIBUSESTA)

If you are creating a new non-versioned BOM you can manually set this field to 'Available to use' when the structure of the assembly is complete. This BOM cannot be added to work orders or included in cost calculations, for example, whilst at status 'In development'.

If you are creating a new version or revision of this BOM, this field defaults to status 'In development'. You cannot manually set it to status 'Available to use'. When the new version or revision has been approved you must validate this BOM (using the Validation action). Validation automatically sets this field to 'Available to use'.

You cannot change this field once a BOM version or revision has been validated, if the product code defined in the Parent product field is version managed.

 Tip: You can use this field in conjunction with the BOM alternative Code field (field BOMALT) to provide a clear distinction between those BOMs that are 'In development' and those that are 'Available to use'. For example, if this BOM is versioned, whilst the new version or revision of this BOM is being checked and is awaiting validation you could use one BOM alternative code (status is 'In development'); when the new version or revision has been approved you could assign a different BOM alternative code, validate it, then set this field to 'Available to use'.

• Level (field LEV)

• 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.

• Component (field GRPITMREF)

• 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.

• Description 1 (field DES1AXX)

• Link quantity (field LIKQTY)

This field displays the quantity of this component in the stock unit that is needed to make the parent product. The default quantity is calculated from the entered quantity using the UOM-STK coefficient (field BOMSTUCOE). You can amend it if necessary.

The sum of the link quantity of each component must equal '100' if the defined management unit (field QTYCOD) for this BOM is 'Percentage'.

 By-products are excluded from the total percentage calculations.

• Stock unit (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.

• Reorder (field LIBREOCOD)

• 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.
  
  

• Parent (field PARKEY)

• Key (field KEYC)

• Screentip (field LIBSH)

• Icon (field ICO)

• Expand (field EXPFLG)

• Component (field XCPNITMREF)

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.

• Description (field XITMDES1)

• Link description (field XBOMSHO)

• Major version (field ECCMAJX)

This field indicates which version of this component (material) applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the "form, fit or function" has changed.

This field is not populated if the component code defined in the Component or Material field is not version managed.

• Minor version (field ECCMINX)

This field indicates which minor version of this component (material) applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

This field is not populated if the component code defined in the Component or Material field is not version managed.

• Qty BOM UOM (field XBOMQTY)

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.

• field XBOMUOM

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

• STK link qty. (field XLIKQTY)

This field displays the quantity of this component in the stock unit that is needed to make the parent product. The default quantity is calculated from the entered quantity using the UOM-STK coefficient (field BOMSTUCOE). You can amend it if necessary.

The sum of the link quantity of each component must equal '100' if the defined management unit (field QTYCOD) for this BOM is 'Percentage'.

 By-products are excluded from the total percentage calculations.

• field XCPNSTU

• UOM-STK factor (field XBOMSTUCOE)

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.

• Link qty code (field XLIKQTYCOD)

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.
  

• Validity start date (field XBOMSTRDAT)

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.

• Validity end date (field XBOMENDDAT)

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.

• First valid lot (field XBOMSTRLOT)

If this component is managed by lot, use this field to define the first/last valid lot or batch of this component that can be used to make this parent product.

If the parent product is managed by lot, the From lot (field BOMSTRLOT) and To lot (field BOMENDLOT) fields determine which components are included on a work order.

 Components included on a work order do have have to be managed by lot.

Example: The parent product is released for production. Lot 'D' is assigned.

• Component 1. From lot = 'A'; To lot = 'C'
• Component 2. From lot = 'D'; To lot = 'F'

Only 'Component 2' will be included on the work order.

• Last valid lot (field XBOMENDLOT)

• Type (field XCPNTYP)

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.
  
  

• % scrap (field XSCA)

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.

• Routing oper (field XCPNOPE)

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).

• Operation lead time (field XBOMOFS)

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.

• Qty rounding (field XQTYRND)

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.

• Stock management (field STOMGTCOD)

• Reorder mode (field XREOCOD)

• field TEXTE

• Image (field IMG)