Assembly
Use the Assembly function to assemble components in order to create a parent product, based on a production Bill Of Material (BOM), without using work orders.
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 traceabilityis not available.
Prerequisite
Refer to documentation Implementation
Screen management
Header
When entering the Disassembly function, you need to choose a transaction among those 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 loaded.
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, you can enter the stock receipt information directly in the Parent product note line.
The stock information is preloaded by default according to the rule for the management of miscellaneous receipt movements defined at the level of the product category the parent product belongs to. 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 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 onModification 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.
Block number 1
Stock site (field STOFCY) |
Enter or select the storage site where the selected product is active. The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table. |
Entry (field VCRNUM) |
The document type, the document number and the document line number are used to identify the origin of the stock movement:
|
Description (field VCRDES) |
This is the description of the document. |
Allocation date (field IPTDAT) |
Date utilisée à la comptabilisation du mouvement. Elle est initialisée avec la date du jour et peut être changée pour une date antérieure, si la date sélectionnée se situe dans une période ouverte du calendrier comptable. Vous ne pouvez pas saisir une date supérieure à la date du jour. |
Transaction group (field TRSFAM) |
Movement group, initialized by the movement group of the transaction being used. |
Project (field PJT) |
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. |
Warehouse (field WRHE) |
The presence of this box is subject to the activity code WRH. |
Disassembly (field VCRNUMORI) |
Document number that generated the disassembly. |
Grid Parent product
Product (field ITMREF) |
Description of the product to be assembled. |
Product description (field ITMDES1) |
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. |
Alternative (field BOMALT) |
Several BOMs can be defined for a single 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. |
Type (field BOMALTTYP) |
Unit (field PCU) |
It is possible to specify a packing unit by supplier.
Only packing type units from the units of measure table can be selected. |
Quantity (field QTYPCU) |
This field indicates the quantity to be processed expressed in PAC. This quantity can be partially changed. |
PAC-STK conversion (field PCUSTUCOE) |
Conversion factor used to calculate the quantity in stock units from a quantity entered in packing units: Quantity in STK = Qty in PAC * conversion factor. This conversion factor can be accessed if the packing Unit field (PCU) has been entered, and has a value different from the Stock unit field (STU). It can be initialized using the conversion factor table if the combination exists. |
Stock unit (field STU) |
STK quantity (field QTYSTU) |
Warehouse (field WRH) |
The presence of this field is subject to the activity code WRH.
The warehouse entered on the line has priority over the warehouse entered in the header. |
Container (field TCTRNUM) |
This field is subject to the LPN - License plate no. management activity code. Indicate the container used. It is initialized based on the default container defined for the Product-site and can be modified if the entry in this field is enabled at the entry transaction level. |
License plate number (field LPNNUM) |
Help common to stock entry functions (Miscellaneous receipts, Receipts, Customer returns, etc.) and the Invoices function (in this case, the field is only displayed and editable for a credit memo or a direct invoice). The management of this field depends on the 'Mandatory' or 'Optional' nature of the license plate number, which is defined for the Product category on the Receipt flow section. In both cases, you can select the license plate number to be used. The selection list displays the active license plate numbers (both 'Free' or 'In stock') associated with the entered container. If no container is specified, the selection list displays all active license plate numbers attached to the site and available in stock. These containers are the ones you created previously, either by unit via the License plate number function or by batch via the License plate number creation function. You can also directly access the License plate numbers function in order to create a number and then switch back to entry mode on the document.
- The License plate number is set to 'Mandatory' for the Product category.
Inter-site / inter-company specificities: for an inter-site or inter-company receipt, the license plate number does not correspond to the one specified on the sales delivery, since the LPN is single-site. |
Status (field STA) |
The stock status is used to define if a product is:
A sub-status of two alphanumerical characters is used to further define the status. Example:
The statuses and sub-statuses authorized in a stock transaction can depend on various factors:
The stock totals for a product are updated according to the status entered in the transactions:
|
Location type (field LOCTYP) |
Location types are used to codify warehouse locations according to storage characteristics such as their dimensions, authorized statuses and technical constraints. The location type is automatically loaded from the location type associated with:
In all cases, the location type can be modified if its entry is enabled at the level of the entry transaction. You may only enter a ‘dock’ type location if the entry transaction authorizes receipts on dock. When warehouses are managed, entry of a location type is only permitted if at least one location is linked to the entered type and warehouse. |
Location (field LOC) |
Depending on the entry transaction setup, the information related to locations is accessible for entry at receipt note line level. The storage location is automatically loaded based on the location type, if it is specified. Otherwise, the location taken into account is the following (in order of priority):
When the warehouses are managed, only a location linked to the specified warehouse can be entered. Additionally, it is possible to enter on the same receipt note line using several different locations. In order to do this, you need to detail the line in the Quantity detail entry window.This window opens automatically if stock information is missing from the line entry. Otherwise, open it by clicking the Actions icon from the note line. |
Supplier lot (field BPSLOT) |
The supplier lot number can be entered for information purposes in the receipt transactions, and displayed in the stock issue transactions. It is recorded in the stock file and corresponds to the internal lot number. This ensures that the origin of goods can be tracked. |
Lot (field LOT) |
Lot concerned by the receipt transaction. |
No. (field NBSLO) |
This field contains the number of sub-lots concerned by the stock transaction. |
Sublot (field SLO) |
Sub-lot concerned by the stock transaction. |
Ending sublot (field SLOF) |
Serial number (field SERNUM) |
|
Last S/N (field SERNUMF) |
Identifier 1 (field PALNUM) |
Use this field to enter additional information, if necessary. |
Identifier 2 (field CTRNUM) |
This field indicates the first recorded identifier. |
Order price (field PRIORD) |
Order price. |
Movement description (field MVTDES) |
Enter a free description that will be registered in all the stock transactions associated with the delivery line. |
field CCE1 |
The analytical dimensions are initialized in compliance with the Default dimensions setup. Depending on the setup, they remain available for modification. |
Tab Components
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 the sub-product type are not considered.
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.
Grid
Product (field ITMREF) |
Component product reference. |
Product description (field ITMDES1) |
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. |
Major version (field ECCVALMAJ) |
Whether the version numbers are displayed or not depends on the setup of the entry transaction. |
Minor version (field ECCVALMIN) |
Whether the version numbers are displayed or not depends on the setup of the entry transaction. |
Unit (field PCU) |
Product storage unit. |
Quantity (field QTYPCU) |
Quantity to be issued on a stock line, expressed in physical stock unit. |
PAC-STK conversion (field PCUSTUCOE) |
Conversion factor used to calculate the quantity in stock units from a quantity entered in packing units: Quantity in STK = Qty in PAC * conversion factor. This conversion factor can be accessed if the packing Unit field (PCU) has been entered, and has a value different from the Stock unit field (STU). It can be initialized using the conversion factor table if the combination exists. |
Stock unit (field STU) |
|
STK quantity (field QTYSTU) |
Warehouse (field WRH) |
The presence of this field is subject to the WRH activity code.
The warehouse entered on the line has priority over the warehouse entered in the header. |
License plate number (field LPNNUM) |
This field is subject to the LPN - License plate no. management activity code. |
Lot (field LOT) |
Lot upon which the issue will be carried out. |
Sublot (field SLO) |
Sub-lot concerned by the stock transaction. |
Location (field LOC) |
This field indicates the stock issue location. |
Status (field STA) |
Status of the lots upon which the issue will be carried out. |
Serial number (field SERNUM) |
|
Last S/N (field SERNUMF) |
Identifier 1 (field PALNUM) |
Use this field to enter additional information, if necessary. |
Identifier 2 (field CTRNUM) |
This field indicates the first recorded identifier. |
Order price (field PRIORD) |
Movement description (field MVTDES) |
Enter a free description that will be registered in all the stock transactions associated with the delivery line. |
field CCE1 |
The analytical dimensions are initialized in compliance with the Default dimensions setup. Depending on the setup, they remain available for modification. |
Stock Issues |
Click this action to open the stock issue detail window. |
Issue modification |
Click this action to modify an issue. |
Stock Transactions |
Click this action to view the stock transactions. |
Menu Bar
Click this action to view the setup of the assembly transaction used. |
Click this action to view and, if needed, modify the analytical dimensions attached to the assembly note header. |
Local menus
In addition to the generic error messages, the following messages can appear during the entry :
Wrong type of alternativeThis message appears if the selected BOM code is not of type Production.
Table fullThe number of receipt and issue stock lines exceeds the limit set by the SLE (number of receipt stock lines) and SLS (number of issue stock lines) activity codes.
The detail quantity must not be equal to 0A detail line cannot contain a null quantity. If you do not want to issue a component, delete the corresponding line.
Dock type location prohibitedYou cannot receive parent products on a location of the ‘dock’ type.
Stock line incompleteThis message is displayed if you attempt 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.
Assign components?When creating the assembly note, if the quantity of the parent product to be assembled is modified, the system suggests that you assign this modified quantity to the quantity of each component to be issued.