Stock >  Internal flows >  Assembly  

Display all Hide all

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.

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

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

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

  • Entry (field VCRNUM)

The document type, the document number and the document line number are used to identify the origin of the stock movement:

  • Supplier receipt
  • Customer delivery
  • Work order
  • Receipt movement
  • Description (field VCRDES)

This is the description of the document.

  • Allocation date (field IPTDAT)

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.

SEEINFO You cannot enter a date later than today's date.

Movement group, initialized by the movement group of the transaction being used.
This statistical information is recorded in the stock journal when saving the receipt/disposal movements. This movement group comes from the miscellaneous table number 9. The value given in the transaction setup corresponds to a default value that can/cannot be visualized and/or modified according to the transaction setup (entered, displayed, hidden field).

This field contains the reference of the project for which the information has been entered.
This field is not controlled in a table.

  • In a request for quotes, this field is empty by default.
  • in a purchase order, this field can be initialized by default using the Project reference of the previous line or that of the request for quotes considered.

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:

  • the first contextual menu, Selection, is used to select a project from a selection list containing all the projects defined in object Projects,
  • the second contextual menu Projects is used to directly access the Projects object, according to the user's authorizations, and then to carry out a selection.

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.
Movement warehouse, suggested by default for all the document lines.
It must be entered if it is defined as mandatory at the level of the entry transaction.
It is loaded in priority with the warehouse defined for the user. If it fails to be set up at user lever, it is initialized with the warehouse defined, by default, at site level for this type of movement.

  • Disassembly (field VCRNUMORI)

Document number that generated the disassembly.
If the assembly has been disassembled, no modification is possible.

Grid Parent product

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 the same product reference.
They can be distinguished via the code, entered on two numbers.

The various BOM codes can be used to manage different product structures according to their use context such as:

  • MRP calculation,
  • Sales order entry
  • Manufacturing/production

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)

 

It is possible to specify a packing unit by supplier.
The product can have several packing units:

  • the packing units entered in the table of the product record ( Units tab). They are proposed during stock transaction entry.
    The number of packing units that can be entered is linked to the NUC activity code.
  • a packing unit linked to the supplier ( Product-supplier record).
  • two customer packing units ( Product-customer record). They can be used as sales units in order entry.

Only packing type units form the units of measure table can be chosen.

  • Quantity (field QTYPCU)

This field specifies the quantity to be processed expressed in PKU.

SEEINFO The quantity can be modified in part.

  • PAC-STK conversion (field PCUSTUCOE)

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 .
This coefficient can be accessed if the packing unit has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists.

 

  • STK quantity (field QTYSTU)

 

  • Warehouse (field WRH)

The presence of this field depends on the activity code WRH.
It is initialized with the warehouse present in the document header.

  • It can be modified if it is defined as enterable in the entry transaction.
    If it is entered, the warehouse will be automatically entered on the stock detail lines and can not be modified.
  • It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory and the warehouse cannot be entered either on the document lines or on the stock detail lines.
     
    To manage multi-warehouses on the lines, it is necessary, at entry transaction level, to set up the warehouse-line so that it can be entered. The split of a same line on several warehouses is carried out in the window Quantity detailed entry available by right-click.
    When a receipt line is distributed on various warehouses, this field is loaded on the slip line with character '$'.

SEEINFOThe warehouse entered on the line has priority over the warehouse entered in the header.

  • Status (field STA)

The stock status is used to define if a product is:

  • A: Accepted
  • Q: Pending Quality Control
  • R: Rejected
    A sub-status of two alphanumerical characters is used to further define the status.
    Example:
  • RD: Rejected products to be destroyed
  • SR: Supplier return

The statuses and sub-statuses authorized in a stock transaction can depend on various factors:
- the "subject to control" code of the product,
- the "subject to control" code of the received order,
- a list of configurable values associated with the stock transaction.

The stock totals for the product are updated according to the status entered in the movements:
- Physical stock: total of stocks with status "A"
- Stock under quality control: total of stocks with status "Q"
- Rejected stock: total of stocks with status "R"

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

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 location type of the product is suggested by default. It can be modified if it is defined as available for entry at the level of the entry transaction.

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

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.
This value can later be modified.

SEEINFO When the warehouses are managed, only a location linked to the specified warehouse can be entered.

  • Supplier lot (field BPSLOT)

The supplier lot number can be entered for information purposes in the receipt transactions.
It is stored in the stock file, and it matches the internal lot number, which guarantees the traceability of the origin of the goods.
It can be displayed on the screen for information purposes in the stock issue transactions.

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

  • Enter the first serial number concerned by the movement.
    When the issue applies to the stock line of a product managed in Issue/receipt and including discontinuous serial numbers or differentiators such as the lot, status or location, the serial number selection is performed in the stock issue Detailed entry window. This window opens automatically at the end of a line entry or from the Actions icon.
    If an issue line is distributed over several serial numbers, the Serial number and Ending serial number fields of the document line are loaded with the $ character.
  • When the issue applies to the stock line of a product managed in Global issue/receipt, you can enter the first serial number. If the system automatically determines a stock line including the quantity to be issued, the ending serial number is automatically loaded. Otherwise, this first serial number is deleted automatically and the Detailed entry window of the stock issue opens automatically at the end of the line entry so you can select the serial number sequences to be issued.
    The issue table will then be loaded with as many issue lines as sequences of issued serial numbers.

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

A free description is entered in this field that will be registered in all the stock transactions associated with the shipment line.
This description is also accessible from the stock issue detail window. If it has been modified by this function, it will be automatically recovered and registered on the shipment line in this field.

The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

In creation mode, if no order line has been entered and the project code is modified, analytical dimensions are reset based on the setup of the default dimensions.

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

 

Tab Components

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 :

Grid

Component product description

  • 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.
They are only managed at the level of the window Lot complement.

  • Minor version (field ECCVALMIN)

Whether the version numbers are displayed or not depends on the setup of the entry transaction.
They are only managed at the level of the window Lot complement.

Product storage unit.

  • Quantity (field QTYPCU)

Quantity to be issued on a stock line, expressed in physical stock unit.

  • PAC-STK conversion (field PCUSTUCOE)

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 .
This coefficient can be accessed if the packing unit has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists.

  • Enter the first serial number concerned by the movement.
    When the issue applies to the stock line of a product managed in Issue/receipt and including discontinuous serial numbers or differentiators such as the lot, status or location, the serial number selection is performed in the stock issue Detailed entry window. This window opens automatically at the end of a line entry or from the Actions icon.
    If an issue line is distributed over several serial numbers, the Serial number and Ending serial number fields of the document line are loaded with the $ character.
  • When the issue applies to the stock line of a product managed in Global issue/receipt, you can enter the first serial number. If the system automatically determines a stock line including the quantity to be issued, the ending serial number is automatically loaded. Otherwise, this first serial number is deleted automatically and the Detailed entry window of the stock issue opens automatically at the end of the line entry so you can select the serial number sequences to be issued.
    The issue table will then be loaded with as many issue lines as sequences of issued serial numbers.

  • STK quantity (field QTYSTU)

 

  • Warehouse (field WRH)

The presence of this field is subject to the activity code WRH.
It defaults to the value of the warehouse specified in the header.

  • This field can be modified if it is defined as available for entry at the level of the entry transaction.
    When this field is entered, it is used as a filter for stock detail line selection and cannot be modified.
    When this field is not entered, the warehouse defined by default for this type of movement in the product-site record is used as the selection filter.
  • It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory and the warehouse cannot be entered either on the document lines or on the stock detail lines.
    To manage multiple warehouses on the lines, the entry must be set up at the entry transaction level. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantites from the Actions icon.
    If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

SEEINFO The warehouse entered on the line has priority over the warehouse entered in the header.

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

  • Enter the first serial number concerned by the movement.
    When the issue applies to the stock line of a product managed in Issue/receipt and including discontinuous serial numbers or differentiators such as the lot, status or location, the serial number selection is performed in the stock issue Detailed entry window. This window opens automatically at the end of a line entry or from the Actions icon.
    If an issue line is distributed over several serial numbers, the Serial number and Ending serial number fields of the document line are loaded with the $ character.
  • When the issue applies to the stock line of a product managed in Global issue/receipt, you can enter the first serial number. If the system automatically determines a stock line including the quantity to be issued, the ending serial number is automatically loaded. Otherwise, this first serial number is deleted automatically and the Detailed entry window of the stock issue opens automatically at the end of the line entry so you can select the serial number sequences to be issued.
    The issue table will then be loaded with as many issue lines as sequences of issued serial numbers.

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

A free description is entered in this field that will be registered in all the stock transactions associated with the shipment line.
This description is also accessible from the stock issue detail window. If it has been modified by this function, it will be automatically recovered and registered on the shipment line in this field.

The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

In creation mode, if no order line has been entered and the project code is modified, analytical dimensions are reset based on the setup of the default dimensions.

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

Stock Issues

This action opens the detail window of the stock issues.

Issue modification

Use this action to modify an issue.

Stock Transactions

Use this action to view the movements by product.

 

Close

 

Menu Bar

Options/View Transaction

Use this action to view the setup of the assembly transaction used.

Options/Dimensions

Use this action to view and/or modify the analytical dimensions attached to the assembly note header.

Error messages

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 provided for 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!

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.

Dock type location prohibited

The parent product receipts for a location of type "pending storage" are not provided for.

Stock line incomplete!

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.

"Assign components?" 

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.

Tables used

SEEREFERTTO Refer to documentation Implementation