Use this function to define the structure of what is referred to as a "bill of materials" or a "BOM". A BOM contains structured information for making a product. It defines the components that make up a product, and given this, the cost of the product.

A BOM is an assembly, a finished product, made up of assemblies and components. If an assembly is used as a component of a final product it is referred to as a subassembly or semi-finished product. Any number of subassemblies can exist in an assembly's component list. Each subassembly will itself have a list of components, and this list can also contain subassemblies. Progressing in this way, you can create up to 999 levels of assembly below the final assembly (the product). The levels are counted from level 1 (the final assembly or parent product) down to the lowest level component.

You can use a generic BOM or reference model to define multiple BOMs for the same product. Each additional BOM is stored as an alternative, enabling a variety of different models of the same generic product to be created. You define alternative BOMs using the function BOM codes (GESTBO).

You assign the context in which a BOM code is used as the BOM "type" when you create the BOM code record. Once defined, the "type" cannot be amended.

  • Commercial BOMs are used on sales orders.
  • Production BOMs are used in cost calculations, work order management, Material Requirements Planning (MRP) and the Master Production Schedule (MPS).
  • Subcontracting BOMs are those used on subcontract orders, in cost calculations, MRP and the MPS.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Sub-contracting BOMs function contains three sections. One that describes the parent product, one that describes the details of the components that make up the parent product, and one that describes the service items required to assemble the product.

Header

The Home section provides the details of the parent product and key tracking information. The critical field in the Home section is the Use status field. This field indicates the current assembly status of this BOM.

Parent

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

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

 
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.

 
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.

Block number 2

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

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

 
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.

Tab Materials

You use this section to define the list of components that make up this product. You can include an assembly as a component. This will be referred to as a subassembly or semi-finished product. 

A single component can exist multiple times in a BOM by assigning a different sequence number to each instance of the component.

Linked information provides associated quantities and validity dates, rejection rates and the replenishment source for a component.

You can define a component as requiring valuation (Valuation field). This results in the provisional cost and cost price calculations providing the component cost from the cost of the finished product.

Grid

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.
Grp (field ECCRLEGRP)
Component (field CPNITMREF)

Use this field to define the component product code.

 
Major version (field ECCVALMAJ)

Use this field to indicate which major version of this component 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.
Minor version (field ECCVALMIN)

Use this field to indicate which minor version of this component 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.
Change request (field CRID)

This field displays a change request ID if this component, or the specific version or revision of this component 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 component 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.
Type of supply (field SCOFLG)

This field displays the replenishment source for this component. This might be 'Internal', made available to a subcontractor or supplied by a subcontractor.
Nonfinancial unit (field BOMUOM)

This field displays the unit of measure (volume or mass) for this component.
STK-OPE conversion fact. (field BOMSTUCOE)

This is the conversion coefficient between the operation unit for this component and the storage unit.

This coefficient is initialized from the conversion factor table if the combination exists.
UOM link quantity (field BOMQTY)

Use this field to define the quantity of this component in the selected unit (field BOMUOM) that is needed to make the parent product.

The sum of the quantity of each component must equal '100' if the defined management unit (field QTYCOD) for this BOM is 'Percentage'.
STK 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'.
STK (field STU)

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.
Link quantity code (field LIKQTYCOD)

Use this field to define how the quantity of this component in the stock unit that is needed to make the parent product is determined:

  • Proportional: The quantity of this component is multiplied by the quantity required for the parent product.
  • Fixed: The quantity of this component is fixed, regardless of the quantity required of the parent product.
Qty rounding (field QTYRND)

Use this field to define the rounding rule to be applied to adjust the calculated quantity of this component to the number of decimal places defined for the stock unit of the parent product. You can set this field to one of the following values:

  • Round to the nearest.
  • Greater than. Round up.
  • Less than. Round down.
Link description (field BOMSHO)

Type in a short description of the component.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for thefolder.
% scrap (field SCA)

Type in the percentage of the component that you expect to be scrap (lost during the production process).

Inquiries can display the following figures:

  • Net quantities. The loss (scrap) percentage is not included in calculations of the quantity required to produce a parent product.
  • Gross quantities. The loss percentage is included in calculations of the quantity required to produce a parent product.
Valid from (field BOMSTRDAT)

Use this field to define the start date of this component's validity period.

Alternatively, leave the default date. This is defined as the start date of the parent product's validity period.

 
Valid to (field BOMENDDAT)

Use this field to define the last date of this component's validity period.

Alternatively, leave the default date. This is defined as the end date of the parent product's validity period.

 
Reorder LT (field BOMOFS)

The operation lead-time is used during launch and in the MRP calculations. It is used to calculate the date of the component (material) requirement with respect to the production start date of the parent product.

It is expressed in calendar days. You can enter a negative value.

Example: A work order has a start date of the 26/06:

  • If the operation lead-time is 7 days, the material requirement date will be calculated on the 03/07 (26/06 + 7);
  • If the operation lead-time is -7 days, the material requirement date will be calculated on the 19/06 (26/06 - 7).
Record entry

Component product

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.
UOM-STK factor (field WBOMSTUCOE)

This is the conversion coefficient between the operation unit for this component and the storage unit.

This coefficient is initialized from the conversion factor table if the combination exists.
Component (field CPNITMREF)

Use this field to define the component product code.

 
field STU

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.
Major version (field ECCVALMAJ)

Use this field to indicate which major version of this component 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.
Minor version (field ECCVALMIN)

Use this field to indicate which minor version of this component 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.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the component code defined in the Component field is not version managed.
Change request (field CRID)

This field displays a change request ID if this component, or the specific version or revision of this component 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 component 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.
Revision group (field ECCRLEGRP)

Destination unit and factor

UOM (field BOMUOM)

This field displays the unit of measure (volume or mass) for this component.
UOM-STK factor (field BOMSTUCOE)

This is the conversion coefficient between the operation unit for this component and the storage unit.

This coefficient is initialized from the conversion factor table if the combination exists.
UOM link quantity (field BOMQTY)

Use this field to define the quantity of this component in the selected unit (field BOMUOM) that is needed to make the parent product.

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

Quantity

STK 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'.
Type of supply (field SCOFLG)

This field displays the replenishment source for this component. This might be 'Internal', made available to a subcontractor or supplied by a subcontractor.
Link quantity code (field LIKQTYCOD)

Use this field to define how the quantity of this component in the stock unit that is needed to make the parent product is determined:

  • Proportional: The quantity of this component is multiplied by the quantity required for the parent product.
  • Fixed: The quantity of this component is fixed, regardless of the quantity required of the parent product.
Quantity rounding (field QTYRND)

Use this field to define the rounding rule to be applied to adjust the calculated quantity of this component to the number of decimal places defined for the stock unit of the parent product. You can set this field to one of the following values:

  • Round to the nearest.
  • Greater than. Round up.
  • Less than. Round down.
Scrap factor % (field SCA)

Type in the percentage of the component that you expect to be scrap (lost during the production process).

Inquiries can display the following figures:

  • Net quantities. The loss (scrap) percentage is not included in calculations of the quantity required to produce a parent product.
  • Gross quantities. The loss percentage is included in calculations of the quantity required to produce a parent product.
Link description (field BOMSHO)

Type in a short description of the component.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for thefolder.

Use

Validity start date (field BOMSTRDAT)

Use this field to define the start date of this component's validity period.

Alternatively, leave the default date. This is defined as the start date of the parent product's validity period.

 
Validity end date (field BOMENDDAT)

Use this field to define the last date of this component's validity period.

Alternatively, leave the default date. This is defined as the end date of the parent product's validity period.

 
Valid lot from (field BOMSTRLOT)

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';  = 'F'

Only 'Component 2' will be included on the work order.
Valid lot to (field BOMENDLOT)
Reorder LT (field BOMOFS)

The operation lead-time is used during launch and in the MRP calculations. It is used to calculate the date of the component (material) requirement with respect to the production start date of the parent product.

It is expressed in calendar days. You can enter a negative value.

Example: A work order has a start date of the 26/06:

  • If the operation lead-time is 7 days, the material requirement date will be calculated on the 03/07 (26/06 + 7);
  • If the operation lead-time is -7 days, the material requirement date will be calculated on the 19/06 (26/06 - 7).
Mat. slip printing (field PICPRN)

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

Text

field TEXTE

Use this free-format text field to view, enter or modify text associated with this assembly.

Click Record entry from the Actions icon to add or amend the details for this component using the standard screen display mode.

Renumber
Sequence (field BOMSEQ)

This field identifies the sequence number of this component in the BOM (bill of materials).
field CPNITMREF

This field displays the component product code.
New sequence (field NEWSEQ)

Use this field to enter a different sequence number for this component. The sequence number identifies a component where multiple components with the same product code are defined as variants or options.

The new sequence number must be unique.

Click Renumber from the Actions icon to enter a different sequence number for this component. The new sequence number must be unique.

Global renumbering

Block number 1

Increment to apply (field BOMSEQINC)

Use this field to define the increment to be applied to the list of component sequence numbers.

Block number 2

Respect existing phases (field PHASE)

Click this check box if the current component order (sequence/phases) must be retained when renumbering the list of component sequence numbers.

Click Global renumbering from the Actions icon to renumber the list of components. You must define the increment to be applied to the component sequence numbers.

 This action is only available if there is no reference date for this parent product, that is, the field Reference date

Line text entry

Click Line text entry from the Actions icon to view or add extra information or comments pertinent to this component line such as assumptions the production manager has made or constraints they are aware of.

Product

Click Product from the Actions icon to view or amend the details of this component product.

Component where used

Click the Component where used action to view the list of assemblies in which the selected component is used.

Product notes

Click this action in order to open a window displaying the note(s) associated with this product.
This information can relate to product availability, additional or substitute products, or a promotional message.
This window could open automatically depending on the setup defined when creating the notes.

Notes are limited to a screen inquiry and cannot be printed.

For further information, see the documentation on Notes.

Line revision

 The following 'Line' actions are only available if this parent product is version managed and whilst this BOM is at status 'In development'.

Click Line revision from the icon to change details of this component. When you select this action this component is duplicated. You can enter your amendments into the new component line.

Line exclusion

Click Line exclusion from the Actions icon to exclude this component line.

Line reintegration

Click Line reintegration from the Actions icon to reintegrate this component back into the list of components. This action is only available for a component you had previously selected to amend (via the Line revision action). The new component is deleted and the end date of the reintegrated component removed.

 This action is only available whilst a component is being amended (via the Line revision action). It is not available after you have selected to save the BOM details (via the Save

Tab Service

You use this section to define the list of service items required to assemble this product.

All items must be defined as service items, that is the Service check box on the product category is selected, and they are not managed in stock. A single service item can exist multiple times in a BOM by assigning a different sequence number to each line.

Linked information provides associated quantities and validity dates.

You can define a service item as requiring valuation (Valuation field). This results in the provisional cost and cost price calculations providing the component cost from the cost of the finished product.

Grid

Sequence (field BOMSEQ)

This field identifies the sequence number of this service item in this BOM (bill of materials). It identifies a service item where multiple service items with the same product code are defined.

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

Use this field to define the service item product code.

 
Valid from (field BOMSTRDAT)

Use this field to define the start date of this service item's validity period.

Alternatively, leave the default date. This is defined as the start date of the parent product's validity period.

 
Valid to (field BOMENDDAT)

Use this field to define the last date of this service item's validity period.

Alternatively, leave the default date. This is defined as the end date of the parent product's validity period.

 
Subcontract lead time (field BOMOFS)

The subcontract lead-time is used during launch and in the MRP calculations. It is used to calculate the time required to manufacture the outsourced item.

It is expressed in calendar days. If this field is zero the following priority order is applied:

  • The subcontract period defined on the Supplier record if it exists, otherwise
  • The purchasing period defined on the Service item record if it exists, otherwise
  • The supply period defined for the service item is applied.
Link quantity code (field LIKQTYCOD)

Use this field to define how the quantity of this component in the stock unit that is needed to make the parent product is determined:

  • Proportional: The quantity of this component is multiplied by the quantity required for the parent product.
  • Fixed: The quantity of this component is fixed, regardless of the quantity required of the parent product.
Qty BOM UOM (field BOMQTY)

Use this field to define the quantity of this service item in the selected unit (field BOMUOM) that is needed to make the parent product.
Nonfinancial unit (field BOMUOM)

This field displays the unit of measure (volume or mass) for this component.
UOM-STK factor (field BOMSTUCOE)

This is the conversion coefficient between the subcontract unit and the operation unit for this service item.

This coefficient is initialized from the conversion factor table if the combination exists.
STK link qty. (field LIKQTY)

This field displays the quantity of this service item 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.
STK (field STU)

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.
Qty rounding (field QTYRND)

Use this field to define the rounding rule to be applied to adjust the calculated quantity of this component to the number of decimal places defined for the stock unit of the parent product. You can set this field to one of the following values:

  • Round to the nearest.
  • Greater than. Round up.
  • Less than. Round down.
Link description (field BOMSHO)

Type in a short description of the component.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for thefolder.
Record entry

Subcon prod

Sequence (field BOMSEQ)

This field identifies the sequence number of this service item in this BOM (bill of materials). It identifies a service item where multiple service items with the same product code are defined.

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

Use this field to define the service item product code.

 

Block number 2

Valid from (field BOMSTRDAT)

Use this field to define the start date of this service item's validity period.

Alternatively, leave the default date. This is defined as the start date of the parent product's validity period.

 
Valid to (field BOMENDDAT)

Use this field to define the last date of this service item's validity period.

Alternatively, leave the default date. This is defined as the end date of the parent product's validity period.

 
Link description (field BOMSHO)

Type in a short description of the component.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for thefolder.

Block number 3

Link quantity code (field LIKQTYCOD)

Use this field to define how the quantity of this component in the stock unit that is needed to make the parent product is determined:

  • Proportional: The quantity of this component is multiplied by the quantity required for the parent product.
  • Fixed: The quantity of this component is fixed, regardless of the quantity required of the parent product.
Qty rounding (field QTYRND)

Use this field to define the rounding rule to be applied to adjust the calculated quantity of this component to the number of decimal places defined for the stock unit of the parent product. You can set this field to one of the following values:

  • Round to the nearest.
  • Greater than. Round up.
  • Less than. Round down.
STK link qty. (field LIKQTY)

This field displays the quantity of this service item 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.
STK (field STU)

This field displays the unit in which the product is stored. It provides the key to prices, costs, volumes etc.
Qty BOM UOM (field BOMQTY)

Use this field to define the quantity of this service item in the selected unit (field BOMUOM) that is needed to make the parent product.
Nonfinancial unit (field BOMUOM)

This field displays the unit of measure (volume or mass) for this component.
UOM-STK factor (field BOMSTUCOE)

This is the conversion coefficient between the subcontract unit and the operation unit for this service item.

This coefficient is initialized from the conversion factor table if the combination exists.

Block number 4

Operation lead time (field BOMOFS)

The subcontract lead-time is used during launch and in the MRP calculations. It is used to calculate the time required to manufacture the outsourced item.

It is expressed in calendar days. If this field is zero the following priority order is applied:

  • The subcontract period defined on the Supplier record if it exists, otherwise
  • The purchasing period defined on the Service item record if it exists, otherwise
  • The supply period defined for the service item is applied.

Click Record entry from the Actions icon to add or amend the details for this service item using the standard screen display mode.

Renumber
Sequence (field BOMSEQ)

This field identifies the sequence number of this service item in the BOM (bill of materials).
field CPNITMREF

This field displays the service item product code.
New sequence (field NEWSEQS)

Use this field to enter a different sequence number for this service item. The sequence number identifies a service item where multiple service items with the same product code are defined as variants or options.

The new sequence number must be unique.

Click Renumber from the Actions icon to enter a different sequence number for this service item. The new sequence number must be unique.

Global renumbering

Block number 1

Increment to apply (field BOMSEQINC)

Use this field to define the increment to be applied to the list of component sequence numbers.

Block number 2

Respect existing phases (field PHASE)

Click this check box if the current component order (sequence/phases) must be retained when renumbering the list of component sequence numbers.

Click Global renumbering from the Actions icon to renumber the list of service items. You must define the increment to be applied to the service item sequence numbers.

 This action is only available if there is no reference date for this parent product, that is, the field Reference date

Line text entry

Click Line text entry from the Actions icon to view or add extra information or comments pertinent to this component line such as assumptions the production manager has made or constraints they are aware of.

Services where used

Block number 1

BOM code (field ALTAFF)

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

Grid

Sequence (field BOMSEQ)

This field identifies the sequence number of this service item in this BOM (bill of materials). It identifies a service item where multiple service items with the same product code are defined.

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

This field displays the level at which this subcontract service item is found in the bill of materials.
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.
Valid from (field BOMSTRDAT)

Use this field to define the start date of this service item's validity period.

Alternatively, leave the default date. This is defined as the start date of the parent product's validity period.

 
Valid to (field BOMENDDAT)

Use this field to define the last date of this service item's validity period.

Alternatively, leave the default date. This is defined as the end date of the parent product's validity period.

 
Link quantity code (field LIKQTYCOD)

Use this field to define how the quantity of this component in the stock unit that is needed to make the parent product is determined:

  • Proportional: The quantity of this component is multiplied by the quantity required for the parent product.
  • Fixed: The quantity of this component is fixed, regardless of the quantity required of the parent product.
Link description (field BOMSHO)

Type in a short description of the component.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

  • Click Translation from the Actions icon in the corresponding field.
  • In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

SEEINFO The connection language must be defined as a default language for thefolder.
Valuation (field CSTFLG)

Leave as 'Yes' if the value of this component must be taken into account when calculating the standard cost of the parent product; if the value of this component must not be included in the standard cost, set to 'No'.

Click the Services where used action to view the list of assemblies in which the selected service item is used.

Specific actions

Click the Multilevel action to view details of this assembly (bill of materials) and the components that make up this assembly.

Error messages

[<<<

Barre de menus

Click the Codes action to allocate the BOM codes that are to be used for this assembly if this BOM is version managed. You allocate a BOM code to be used whilst the "bill" is being defined and when it is available to use.

This 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 BOM code matches the product code.

Use this field to define the BOM code to be used whilst the components that make up the product are being defined (field Use status='In development').

This field defines the site at which this product (BOM) is assembled (made). The 'In development' and 'Available to use' sites must be identical.

Use this field to define the BOM code to be used for versions of this product (BOM) that have been validated and are at status 'Available to use'.

This field defines the site at which the assembled product (BOM) has been made 'available to use'. The 'In development' and 'Available to use' sites must be identical.

Click the Revision action to create a revised version of this BOM. You can choose to increment the major or the minor version. The new BOM will be created with the In development status as this will enable you to change the BOM details as required. For example, to correct a component's details you might create a new minor version; to add another component you might create a new major version.

 You cannot change any key elements of a BOM once it has been made Available to use

Block number 1

  • BOM type (field TYPALT)

The context in which a BOM code is used. The 'type' cannot be amended.

  • Sales (Kit) BOMs are the Commercial BOMs used on sales orders.
  • Manufacturing BOMs are the Production BOMs used in cost calculations, Work order management, Material Requirements Planning (MRP) and the Master Production Schedule (MPS).
  • Subcontracting BOMs are those used on subcontract orders, in cost calculations, MRP and the MPS.

This 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 BOM code matches the product code.

Last version

  • Major version (field ECCVALMAJ)

This field displays the current or latest major version of this BOM. 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.

  • Minor version (field ECCVALMIN)

This field displays the current or latest minor version of this BOM. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

  • From (field STRDAT)

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

  • To (field ENDDAT)

This field is blank to show that the final date of the validity period for the current or latest version of this BOM has not yet been defined.

New version

  • Start date (field DATCRE)

Use this field to define the start date of the new version’s validity period. The start date can be today’s date. The default date is tomorrow.

 You cannot change this date after you create this new version (by clicking OK

  • Revision type (field TYPCRE)

Use this field to create a revised version of this BOM. Leave as 'Minor' to create a new minor version of this BOM. To create a new major version, click 'Major'.

 Availability of these fields is determined by the Version management fields on the product record.

Block number 4

  • Default BOM version (field REVVERD)

Block number 5

  • Major version (field NEWVALMAJ)

This field indicates which major version of this BOM currently applies. The default code displayed is incremented automatically if you choose to create a new major version (Revision type='Major'). The format of the new code will match the format for the sequence number counter defined on the product record.

  • Minor version (field NEWVALMIN)

This field defaults to the next incremental minor version of this BOM. The format of the new code will match the format for the sequence number counter defined on the product record.

If you increment the major version (Revision type='Major'), this field will default to the first code in the sequence defined by the product sequence number counter.

Block number 6

  • Stock version (field REVVERS)

Block number 7

  • Major version (field STOVALMAJ)
  • Minor version (field STOVALMIN)

Block number 8

  • Manual (field REVVERM)

Block number 9

  • Major version (field MANVALMAJ)
  • Minor version (field MANVALMIN)

Click the Validation action to validate this BOM. This will check the definition is correct and enable you to return to the definition to correct it if necessary. Once validation is complete this BOM is activated and its status changed to Available to use. The stock record and a log file are updated accordingly.

Click the Management action to view and manage all versions of this BOM. You can use this action to do the following:

  • Set the final date of the validity period for the current version of this BOM
  • Add an exception date to a specific version (major or minor) of this BOM, so the version can be used outside its validity period.

Multiple major versions indicate that there has been a significant change to the original BOM, that is, the "form, fit or function" changed. Where a minor version is displayed compatibility with the major version has been maintained, there has simply been a minor change to the associated major version.

 To add new versions (major or minor) of this BOM, use the Revision action.

Block number 1

This 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 BOM code matches the product code.

Grid

  • Major version (field ECCVALMAJ)

This field indicates which version of this product 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 product code defined in the Product field is not version managed.

   
  • Minor version (field ECCVALMIN)

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.

This field is not populated if the product code defined in the Product field is not version managed.

  • 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

  • Start date (field STRDAT)

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

  • End date (field ENDDAT)

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

 

  • Exception (field EXNFLG)

Use this field to indicate if there is an exception to the period of validity for this version of this BOM.

  • Excp. date (field EXNDAT)

Use this field to define a specific date outside the defined validity period that this version of this BOM is available for use.

 

  • Flow (field ECCTYP)

The context in which a BOM code is used. The 'type' cannot be amended.

  • Manufacturing (Production) BOMs are those used in cost calculations, Work order management, Material Requirements Planning (MRP) and the Master Production Schedule (MPS).
  • Sub-contract BOMs are those used on subcontract orders, in cost calculations, MRP and the MPS.

Limitations

You cannot use a serial numbered product as a component that has the Global received/issued management mode.

 Products

[>>>>MENU_FLOTTANT_DIV]

In addition to the generic error messages, the following messages can appear during the entry :

"Product: xx...x Record does not exist"

The product number that you have entered does not exist in the product table.

"BOM: ## Record does not exist"

The requested BOM does not exist in the BOM table.

The product must be a received product to create a subcontract BOM.

This message is displayed if the product cannot be received into stock. The Received product check box is not selected on the Product-site record.

"Record already exists"

This message only appears on record creation or copy. The BOM code that you have attempted to create already exists in the table.

"Record does not exist"

This message only appears when searching for a record. The BOM code (product + code) that you have entered does not exist in the BOM table. To make the search for a code easier, a selection window is available.

"This BOM is not valid at the date indicated"

You have selected a BOM for which the validity dates in the header do not include the reference date requested for the display.

"No change authorization on this alternative"

The user profile does not have the modification rights for this code, according to the access code managed in the code table.

"Creation not possible: maximum number of levels is reached!"

The parent product requested for the creation of a new BOM is already used as a component and has a code for a lower level equal to the maximum level defined by the BOMLEV-Maximum BOM level parameter (TC chapter, BOM group).

"Caution! There are links with some dates not included in this range"

You have modified the validity dates in the header and links in this BOM have dates that do not fall within this range.

"Caution! Check link quantities"

You have modified the management unit in the header, for which link quantities have been defined. As there is no automatic conversion of the quantities you must verify and potentially revert your decision.

Messages appearing upon link entry"Product: xxx Record does not exist"

The component product entered does not exist in the product table.

"There is no Product-Site on the site of this alternative"

(Non-blocking) warning when the parent product code has a dedicated site and there is no product-site record for the component at the code site.

"This link exists in another valid bracket"

The component product entered for the creation of a new link already exists with the same sequence number (it cannot be displayed due to its validity date not matching the reference date).

"This link causes a loop in the BOM"

The selected component has this parent product as a component in its BOM.

"Incorrect date"

You have entered a validity end date prior to the start date.

"Link validity must be included in the Retention Period of Header."

The validity date entered for the link does not fall within the validity date range of the header.

"End range is less than Start range"

You have entered an end lot number which is less than the start lot number.

Controls upon validation (after entry of all the fields)"BOM does not have a single link"

You cannot create a header without component lines. You have tried to validate the link table although it is empty.

"BOM no longer has a link. Do you want to delete it ?"

You have deleted all the component lines, thereby removing all links in the table. This message identifies this and suggests you delete the header as well.

"Cancellation is only possible with a null reference date"

It is only possible to delete a complete BOM (header and links) if the reference date (field DATREF) is blank. This is to prevent links from being accidentally deleted.

"Total must not exceed 100 %"

The sum of the quantity of each component must equal "100" if the defined management unit (field QTYCOD) for this BOM is Percentage. Component types defined as by-products, that is the field Component type (field CPNTYP) is set to By-product are not included in the total percentage calculations.

"Distribution does not reach 100%"

The defined management unit (field QTYCOD) for this BOM is Percentage but the sum of the quantity of each component is not yet equal to "100". Component types defined as by-products, that is the field Component type (field CPNTYP) is set to By-product are not included in the total percentage calculations.

"The planned version start date has already passed. Do you want to change the version start date to today?"

If this message is displayed you can select Yes to change the Start date (DATECRE) of the new version to today’s date. The valid From / To dates for the revised BOM components and deleted components will be changed accordingly. Only when "validation" is complete is the version status set to Available to use.

Tables used

SEEREFERTTO Refer to documentation Implementation