Common data > BOMs > Commercial BOMs 

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

    Presentation

    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.

    Close

     

    Fields

    The following fields are present on this tab :

    Parent

    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.

    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.

    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.

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

    Block number 2

    • Description (field BOMDESAXX)

    Use this field to identify this product.

    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.

    Close

     

    Tab Components

    Presentation

    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.

    Close

     

    Fields

    The following fields are present on this tab :

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

    • Addition (field BOMSEQNUM)

    Supplementary sequence number used for options and variants in Commercial BOMs. This number relates to the component type, enabling you to define a component as a variant or an option.

    The list of possible options or variants for the same component must have the same sequence number. You use the supplementary sequence number to classify component options and variants into a given order for sales transaction selection.

    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.

     The Deliverable or Cannot be delivered status of this component must match the status of the parent product.


    You can leave this field blank and instead use a formula in the field Selection formula (field FORSEL) to select components. The components selected by the formula are offered when this BOM is added to a sales transaction.

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

    You can only use this field if the Component (field CPNITMREF) field is blank. Instead of entering all the possible options/variants as individual components you can use a predefined 'Component selection' formula to select components. The components selected by the formula are offered when this BOM is added to a sales transaction. A filter on the Deliverable or Cannot be delivered status of the component is applied automatically to ensure the selected components match the status of the parent product.

    SEEINFO You can only use one selection formula per sequence number.

    • Link quantity (field LIKQTY)

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

    Alternatively, leave blank to use a formula to calculate the component quantities (field Qty formula (field FORQTY)).

     You can only use a formula to calculate component quantities if you have used a formula to load the components (field Selection formula (field FORSEL)).

    You can only use this field if you have used a predefined 'Component selection' formula in the field Selection formula (field FORSEL). Instead of entering a quantity per component option/variant you can use a predefined 'Component quantity' formula to calculate the quantity for each component that is needed to make the parent product.

     You can change the component quantities calculated by the formula when this BOM is added to a sales transaction.

    • Component type (field CPNTYP)

    Use this field to define what type of component this is. This field relates directly to the supplementary sequence number used for options and variants (field Sub (field BOMSEQNUM)). You can set it to one of the following values:

    • Normal. A standard component of this bill of materials. This type of component is always added to a sales transaction.
    • Option. An optional component of this bill of materials. It is not mandatory to add this type of component to a sales transaction.
    • Variant. A variant or alternative of a standard component. It is mandatory to add the standard or a variant of the component to a sales transaction.
    • Multiple option. When a value must be calculated for the provisional cost and the production cost price of the parent product.
    • Normal (with formula). This is the default value if you have used a 'Component selection' formula in the field Selection formula (field FORSEL). The components selected by the formula are not included in the list of components individually, however they are standard components of this bill of materials and added to a sales transaction.

     All components with the same sequence number must be the same type of component.

    • Link quantity code (field LIKQTYCOD)

    This value is always set to 'Proportional' for Commercial BOMs. The quantity of this component is multiplied by the quantity required for the parent product.

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

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

    SEEINFOThe connection language must be defined as a default language for thefolder.

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

     This component's validity dates must be within the date range defined for the parent product.

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

     This component's validity dates must be within the date range defined for the parent product.

    • Print acknowledgment (field OCNPRN)

    Use this field to specify if this component must be printed on sales order acknowledgements.

    • Print slip (field NDEPRN)

    Use this field to specify if this component must be printed on delivery notes.

    • Print inv (field INVPRN)

    Use this field to specify if this component must be printed on sales invoices.

    Close

     

    Action icon

    Record entry

    Fields

    The following fields are included in this window :

    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.

    • field BOMSEQNUM

    Supplementary sequence number used for options and variants in Commercial BOMs. This number relates to the component type, enabling you to define a component as a variant or an option.

    The list of possible options or variants for the same component must have the same sequence number. You use the supplementary sequence number to classify component options and variants into a given order for sales transaction selection.

    • Component type (field CPNTYP)

    Use this field to define what type of component this is. This field relates directly to the supplementary sequence number used for options and variants (field Sub (field BOMSEQNUM)). You can set it to one of the following values:

    • Normal. A standard component of this bill of materials. This type of component is always added to a sales transaction.
    • Option. An optional component of this bill of materials. It is not mandatory to add this type of component to a sales transaction.
    • Variant. A variant or alternative of a standard component. It is mandatory to add the standard or a variant of the component to a sales transaction.
    • Multiple option. When a value must be calculated for the provisional cost and the production cost price of the parent product.
    • Normal (with formula). This is the default value if you have used a 'Component selection' formula in the field Selection formula (field FORSEL). The components selected by the formula are not included in the list of components individually, however they are standard components of this bill of materials and added to a sales transaction.

     All components with the same sequence number must be the same type of component.

    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.

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

    You can only use this field if the Component (field CPNITMREF) field is blank. Instead of entering all the possible options/variants as individual components you can use a predefined 'Component selection' formula to select components. The components selected by the formula are offered when this BOM is added to a sales transaction. A filter on the Deliverable or Cannot be delivered status of the component is applied automatically to ensure the selected components match the status of the parent product.

    SEEINFO You can only use one selection formula per sequence number.

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

    Link

    • Link quantity (field LIKQTY)

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

    Alternatively, leave blank to use a formula to calculate the component quantities (field Qty formula (field FORQTY)).

     You can only use a formula to calculate component quantities if you have used a formula to load the components (field Selection formula (field FORSEL)).

    You can only use this field if you have used a predefined 'Component selection' formula in the field Selection formula (field FORSEL). Instead of entering a quantity per component option/variant you can use a predefined 'Component quantity' formula to calculate the quantity for each component that is needed to make the parent product.

     You can change the component quantities calculated by the formula when this BOM is added to a sales transaction.

    • Link quantity code (field LIKQTYCOD)

    This value is always set to 'Proportional' for Commercial BOMs. The quantity of this component is multiplied by the quantity required for 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.

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

    SEEINFOThe connection language must be defined as a default language for thefolder.

    Use

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

     This component's validity dates must be within the date range defined for the parent product.

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

     This component's validity dates must be within the date range defined for the parent product.

    • Print acknowledgment (field OCNPRN)

    Use this field to specify if this component must be printed on sales order acknowledgements.

    • Print packing slip (field NDEPRN)

    Use this field to specify if this component must be printed on delivery notes.

    • Print invoice (field INVPRN)

    Use this field to specify if this component must be printed on sales invoices.

    Text

    • field TEXTE

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

    Close

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

    Renumber

    Fields

    The following fields are included in this window :

    • Sequence (field BOMSEQ)

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

    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.

    Close

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

    Global renumbering

    Fields

    The following fields are included in this window :

    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.

    Close

    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 (field DATREF) is blank.

    Merge

    Fields

    The following fields are included in this window :

    Use this field to define the parent product assembly code to merge into or combine with this assembly. All components in the selected assembly will be added to this assembly code.

    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 define the specific BOM alternative of the parent product to be merged into or combined with this assembly.

    Close

    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

    Fields

    The following fields are included in this window :

    Block number 1

    • Formula type (field FORTYP)

    Use this field to assign the type of functionality in which this formula is to be used, for example in the calculation of overheads or tax, or in routing operations.

    Code used to identify the calculation formula. A calculation formula is a short code calling on an expression to evaluate a result used in various functions of the product.

    Block number 2

    • Description (field DES)

    This long description is used as a title in screens and reports.

    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.

    SEEINFOThe connection language must be defined as a default language for thefolder.

    • Short description (field DESSHO)

    Title used in some screens or reports when there is not enough space to view the long title.

    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.

    SEEINFOThe connection language must be defined as a default language for thefolder.

    Formula

    • field FORFOR1

    Use this field (and any subsequent fields, if available) to structure a calculation expression.

    The syntax is validated when you save the expression and when the formula is used. It can be defined over one or two lines.

     

    Close

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

     An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

    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.

     

    Close

     

    Actions menu

    Text / Header Text

    Click the Header text action to view, enter or modify text associated with this assembly.

    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