Copy BOMs
Several types of BOM copies are necessary to facilitate the management of the technical data:
- first level BOM copy of a parent product to another parent product,
- first level BOM copy of the selected parent product to the other selected parent product,
- multi-level BOM copy of the selected parent product to the other selected parent product,
The first mentioned functionality is provided by the BOM management, by duplication or fusion.
The two other functionalities are possible via the BOM copy menu that is used to copy a source alternative to a destination alternative.
Prerequisites
Refer to documentation Implementation
Screen management
The BOM copy is divided into two steps:
- selection entry,
- creation of the BOM.
Header
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.
|
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.
|
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:
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:
|
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:
|
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.
|
Allergens (field ALG) |
This field displays allergen codes for the parent product.
|
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 BOM levels
First level copy
The screen displayed is identical to the BOM management screen: the header and link information can be changed. The controls and possibilities are identical to those present in the BOM management.
The [Validation] button is used to validate the creation of new links in the destination alternative, with consideration of the potential modifications brought to this screen.
multi-level copy
The result of the BOM multi-level copy of a given parent product is displayed on the screen. However, no header or link modification is possible.
The [Validation] button is used to validate the creation of all first level BOMs that are involved in the selected parent product. The BOMs already existing in the destination alternative (existing header) are not created and a message is written down in an execution report of the program.
Grid Component product
Lev. (field NIVBOM) |
Sequence (field BOMSEQ) |
This field identifies the sequence number of this component in this BOM (bill of materials). It identifies a component where multiple components with the same product code are defined as variants or options. The BOMSTE - Component sequence increment parameter (TC chapter, BOM group) defines the first sequence number and the increment applied to subsequent component sequence numbers. |
Component (field CPNITMREF) |
Use this field to define the component product code.
|
UOM (field BOMUOM) |
This field displays the unit of measure (volume or mass). |
UOM-STK factor (field BOMSTUCOE) |
This field indicates the UOM-S conversion coefficient used to calculate the quantity in US, from a quantity entered in UOM: Qty in US = Qty in UOM * coeff. |
UOM link quantity (field BOMQTY) |
The link quantity specifies the number of components required for the basic quantity of the parent product. The corresponding value is initialized from the one defined at BOM level. |
STK link quantity (field LIKQTY) |
The link quantity specifies the number of components required for the basic quantity of the parent product. |
STK (field STU) |
This field indicates the product management unit in which are expressed:
This information is always displayed, regardless of the transaction used. It cannot be modified. |
Component type (field CPNTYP) |
Use this field to define what type of component this is. You can set it to one of the following values:
|
Link quantity code (field LIKQTYCOD) |
The code of the link quantity can be:
|
Qty rounding (field QTYRND) |
The quantity of BOM links is entered with a maximum accuracy, which is not always useful for the stock management. |
Link description (field BOMSHO) |
This field displays the short description of the bill of material (BOM). |
% scrap (field SCA) |
The loss percentage is used to increase the link quantity in order to take into account the loss due to the production process.
|
Valid from (field BOMSTRDAT) |
The validity start date is the date from which the link is valid. |
Valid to (field BOMENDDAT) |
The validity end date is the date beyond which the link is no longer valid. |
From lot (field BOMSTRLOT) |
For components that are managed by lot, this is the first lot for which this link is valid. |
To lot (field BOMENDLOT) |
For components that are managed by lot, this is the last lot for which this link is valid. |
Routing oper (field CPNOPE) |
If you do not need this component to be readily available at the start of the production process, use this field to define the specific operation or stage in the manufacturing process at which this component must be available to it. Holding back availability of this component until it is needed can be particularly beneficial in some circumstances. For example, for cost savings if this component is an expensive purchased product or storage costs are expensive, for saving on warehouse floor space if it has a large volume or for catering for specific characteristics such as a cooling period. This becomes the default operation number and can be changed for an order if necessary.
|
Ope LT (field BOMOFS) |
The operation lead-time is used at the release and in the MRP calculation, in order to offset the component requirement with respect to the production start date of the parent product. This lead-time is expressed in business days. |
Mt. slip print. (field PICPRN) |
Use this field to specify if this component must be printed on work order material issue slips. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Message of the copy selection screen.
"The alternatives must be of the same type"
"The copy source alternative and destination alternative must be of the same type."
"The destination BOM is already existing"
Messages of the error log file
At the end of the processing, a log file is displayed on the screen with the selections, the keys of the records created and the potential errors, that are usually of technical type rather than functional type:
"Error when accessing the BOH file"
This problem occurs if the BOH file has not been found in read only access for example.
"Writing error on file ITMBOM"
Error if the file is downgraded in the database.
"Record locked"
"Locking error on..."
The record is being upgraded on another workstation and the program did not manage to access.
"BOD record already exists": ... "
The link to create by the copy is already existing in the link table.
"The destination BOM is already existing"
The BOM has not been copied because it existed already.