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 Commercial BOMs function contains a section that describes the parent product and a section that describes the details of the components that make up the parent 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.

Tab Components

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. Components can be stocked and non-stocked items.

You can include multiple components with the same product code, with each one defined as a variant or option. To ease the entry of multiple similar components you can use a formula to select the components automatically. Components selected using a formula are not displayed in the list of components, however when the parent product is added to a sales transaction the component options and variants are offered for selection.

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.

 Low level codes > Inquiry to view the levels at which a specific component is currently being used.

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

Renumber

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

Global renumbering

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

Merge

Click Merge from the Actions icon to merge or combine the component data from a different parent product or version of this BOM with this set of components. Errors are reported and displayed in a Log file.

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.

Selection formula

Click the Selection formula action to enter, select or build an Sage X3 filter calculation expression using the formula editor.

 

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.

Barre de menus

Error messages

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.

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

"Components of the same sequence must be of the same type"

You have entered components with different types in the same sequence (option, variant or normal).

"Variant component must not be alone in a sequence."

You have entered a component as as variant but there is no component for the same type. A variant is a mandatory choice from a minimum of two components.

Tables used

SEEREFERTTO Refer to documentation Implementation