The function Assembly is used to assemble components to create a parent product based on a manufacturing BOM without carrying out the work order.
The assembly translates into the stock receipt of the parent product and the stock issue of various components coming from the BOM or added by the user. These movements are gathered under a single assembly note code.
Unlike for the production by work order, the traceability is not available.
Refer to documentation Implementation
Presentation
Upon entering the function Assembly, you must choose a transaction among those that have been set up.
Depending on the setup of the selected transaction, it is possible to associate a movement code and/or a project code with the assembly note.
Parent product to be assembled:
A table enables to enter the parent product to be assembled. It must be noted that the assembly function only allows for one parent product to be assembled for each note.
Through the Selection icon, you can select this parent product (product and BOM code) among the list of products in the BOM header. The BOM code is then automatically entered.
Entering details for a product stock receipt is done in the same way as a receipt entry: depending on the setup of the chosen transaction, it is possible to enter the stock receipt information directly in the note line Parent Product.
The stock information is preloaded by default according to the the rule for the management of miscellaneous receipt movements defined at the level of the product category to which the parent product belongs. Moreover the default values can be modified (see the Product categories documentation).
It is always possible to detail the receipt information by clicking Enter detailed quantities from the Actions menu on the parent product line: it is possible to distribute the entry on several lots, sub-lots or serial numbers, or different warehouses, locations, statuses, or stock identifiers, if needed and depending on the parent product management method. Please refer to the documentation Stock Receipts for more information on the detailed entry of receipts.
If the parent product is managed by lot and a new lot is entered, click on Lot complement to enter the information relating to the lot (expiry date and potency, version number if the tracking of versions is active at the product setup level, user heading entry depending on the transaction).
Click on Lot Info from the Actions menu to know, during the entry, how the lot code can be loaded.
Finally, use the Actions menu at the parent product level to access its Stock by site, Stock by lot and Detailed stock.
During an assembly, the dock entries are not provided for.
The receipt movement carried out is a movement of the miscellaneous receipt type.
Assembly modification: it is not possible to delete an assembly or an assembly component. It is necessary to use a disassembly operation. However, the receipt movements can be modified by clicking on Modification on entries from the icon Actions on the parent product line, but only if the assembly concerned has never been subjected to a disassembly.
An assembly that has been subjected to a disassembly bears the related disassembly code in the note header.
Close
Fields
The following fields are present on this tab :
Block number 1
|
Enter or select a storage site at which the selected product is active. The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table. |
|
The document type, the document number and the document line number are used to identify the origin of the stock movement:
|
|
This is the description of the document. |
|
This is the date which is used when posting the movement. It defaults to today's date but can be changed to an earlier date, if the selected date is in an open period in the accounting calendar.
|
|
Movement group, initialized by the movement group of the transaction being used. |
|
This field contains the reference of the project for which the information has been entered.
It is possible to enter a free code or a project code defined in the Project object in the CRM activities module. In this latter case, the user has two possibilities to enter such a code:
If the order arises from a requirement and this requirement has a project code, the project code of the order will be initialized with this project code. |
|
The presence of this box is subject to the activity code WRH. |
|
Document number that generated the disassembly. |
Grid Parent product
|
Description of the product to be assembled. |
|
This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line. |
|
Several BOMs can be defined for the same product reference. The various BOM codes can be used to manage different product structures according to their use context such as:
This field can be left empty (value = 0) to enable manual entry of the components. In this case, only the component is loaded. |
|
  |
|
It is possible to specify a packing unit by supplier.
Only packing type units form the units of measure table can be chosen. |
|
This field specifies the quantity to be processed expressed in PKU.
|
|
The PAC-STK conversion factor is used to calculate the quantity in stock unit from a quantity entered in packing unit: Qty in STK = Qty in PAC * coeff . |
|
  |
|
  |
|
The presence of this field depends on the activity code WRH.
|
|
The stock status is used to define if a product is:
The statuses and sub-statuses authorized in a stock transaction can depend on various factors: The stock totals for the product are updated according to the status entered in the movements: |
|
Location types are used to codify warehouse locations according to storage characteristics such as their dimensions, authorized statuses and technical constraints. They are associated with the products by site (or the products by warehouse when warehouses are managed): you can thus geographically group the products that share similar characteristics.
|
|
The storage location is automatically displayed based on the location type, if specified. Otherwise, the location taken into account is by default the location defined in the Product-warehouse, if the warehouses are managed, or else the location defined in the product-site record.
|
|
The supplier lot number can be entered for information purposes in the receipt transactions. |
|
Lot concerned by the receipt transaction. |
|
This field contains the number of sub-lots concerned by the stock transaction. |
|
Sub-lot concerned by the stock transaction. |
|
  |
|
|
|
  |
|
Use this field to enter additional information, if necessary. |
|
This field indicates the first recorded identifier. |
|
Order price. |
|
A free description is entered in this field that will be registered in all the stock transactions associated with the shipment line. |
The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.
In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset. |
Close
Presentation
Entering a parent product and a BOM code automatically loads the components table by reading of the BOM.
The quantities to be issued for each component are calculated from the quantity to be assembled and the BOM link quantity for each component. This quantity can be modified.
When creating the assembly note, it is possible to delete a component planned on the BOM, or to add unexpected components by direct entry in the component table.
The components of type sub-product are not taken into consideration.
If a component is present several times in the BOM, the quantities are not aggregated; several issue lines are generated.
If there is a phantom component in the BOM: if the phantom component is managed in stock and has sufficient available stock to cover the parent product requirement, the phantom component remains on the component list in order to be consumed. If, on the contrary, the phantom component does not have sufficient available stock, it is passed over and its components are displayed for the assembly.
Addition of an unexpected phantom component: only possible if this phantom component has available stock.
Only the phantom stock has the status 'A' to calculate the available stock.
Click on BOM from the Actions menu on the component line to view the BOM of a component of the phantom type.
Determination of the stock lines to be issued: the determination of the stock lines to be issued is based on the detailed allocation rule dedicated to internal movements and on the dedicated management rules for miscellaneous issues. These rules are described at component product category level.
It is also possible to manually select the stock lines to be issued by clicking on Stock issues from the Actions menu accessible on the parent product line: the system displays a selection screen for the stock lines to be issued, with possible filters. Its functioning is described in the Stock issues documentation.
The component issue movements are movements of the miscellaneous issue type linked to an entry of the assembly type.
Valuation of assembly movements:
Receipts: if the parent product price is not entered, the value of the receipt movement is calculated as a sum of the issue values of its components.
Issues: The component issues are valued according to the retained valuation rule for the issues of each of the products.
Posting of the assembly movements :
The analytical dimensions of the assembly note are preloaded by default as follows:
Analytical dimensions in note header: they are loaded by default via the dimension code STKBBYH, and they can be modified if the transaction setup allows it.
Analytical dimensions in note lines: they are loaded by default via the dimension code STKBBYD, and they can be modified if the transaction setup allows it.
Analytical dimensions of parent product receipt movements: they are loaded by default using the dimension code STJEND, and they can be modified if the transaction setup allows it.
Analytical dimensions of component issue movements: they are loaded by default using the dimension code STJSOR, and they can be modified if the transaction setup allows it.
Modification of an assembly:
It is possible to modify the issue movements by clicking on Modification of issues, from the icon Actions. However, it is not possible to delete a component or an assembly: it is necessary to carry out a disassembly in this case.
An assembly that has been subjected to a disassembly bears the related disassembly code in the note header.
Close
Fields
The following fields are present on this tab :
|
Component product description |
|
This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line. |
|
Whether the version numbers are displayed or not depends on the setup of the entry transaction. |
|
Whether the version numbers are displayed or not depends on the setup of the entry transaction. |
|
Product storage unit. |
|
Quantity to be issued on a stock line, expressed in physical stock unit. |
|
The PAC-STK conversion factor is used to calculate the quantity in stock unit from a quantity entered in packing unit: Qty in STK = Qty in PAC * coeff . |
|
|
|
  |
|
The presence of this field is subject to the activity code WRH.
|
|
Lot upon which the issue will be carried out. |
|
Sub-lot concerned by the stock transaction. |
|
This field indicates the stock issue location. |
|
Status of the lots upon which the issue will be carried out. |
|
|
|
  |
|
Use this field to enter additional information, if necessary. |
|
This field indicates the first recorded identifier. |
|
  |
|
A free description is entered in this field that will be registered in all the stock transactions associated with the shipment line. |
The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.
In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset. |
Close
Action icon
This action opens the detail window of the stock issues.
Use this action to modify an issue.
Use this action to view the movements by product.
Close
Use this action to view the setup of the assembly transaction used.
Use this action to view and/or modify the analytical dimensions attached to the assembly note header.
In addition to the generic error messages, the following messages can appear during the entry :
This message appears if the selected BOM code is not of type Production.
The number of receipt and issue stock lines exceeds the limit provided for by the SLE (number of receipt stock lines) and SLS (number of issue stock lines) activity codes.
It is not possible to have a quantity of 0 on a detail line. If a component is not to be issued, the corresponding line must be deleted.
The parent product receipts for a location of type "pending storage" are not provided for.
This message is displayed if an attempt is made to select a stock line pending storage and the characteristics of the product to be stored have not yet been entered (lot, sub-lot, serial number) or if the stock information is not completely entered on the line of the parent product to be received.
When creating the assembly note, if the quantity of the parent product to be assembled is modified, the system suggests passing on this modified quantity onto the quantity of each component to be issued.