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.

SEEWARNING Unlike for the production by work order, the traceabilityis not available.

Prerequisite

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

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. 

Local menus

In addition to the generic error messages, the following messages can appear during the entry :

Wrong type of alternative

This message appears if the selected BOM code is not of type Production.

Table full

The 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 0

A detail line cannot contain a null quantity. If you do not want to issue a component, delete the corresponding line.

Dock type location prohibited

You cannot receive parent products on a location of the ‘dock’ type.

Stock line incomplete

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

Tables used

SEEREFERTTO Refer to documentation Implementation