Disassembly

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

• Supplier receipt
• Customer delivery
• Work order
• Receipt 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.
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).

Statistical information used in the stock transactions associated with the shipment. This value is fixed if the original document does not reference a movement group. Otherwise, the movement group of the document at the origin of the quality control is suggested in priority.

• Project (field PJT)

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.

• Assembly (field VCRNUMORI)

• Product (field ITMREF)

Description of the product to be disassembled.

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

The code type is used to draw the distinction between the BOMs intended for sales use, those used for manufacturing and those used for sub-contracting.
The BOM type is automatically entered with respect to the BOM code previously entered.

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

• Unit (field PCU)

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

• A packing unit defined on the product record (from the Packing units table). These units are proposed during stock transaction entry.
  The number of packing units that can be entered is subject to the NUC - Number of packing units activity code.
• A packing unit linked to the supplier (defined on the product-supplier record).
• Two customer packing units (from the product-customer record). These can be used as sales units in order entry.

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.
It is loaded with the warehouse displayed in the document header.

• It can still be changed if this field is set up so as to be entered at entry transaction level.
  When it is entered, the warehouse is automatically loaded on the stock detail lines and cannot 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 multiple warehouses and enter the same slip line on various warehouses, you must enable the entry of the warehouse-line at the entry transaction level. To split a line onto several warehouses, click, the Actions icon and select Enter detailed quantities.
  When a receipt line is distributed on various warehouses, this field is loaded on the slip line with character '$'.

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.
It refers to the license plate number of the container impacted by the issue.

• Lot (field LOT)

This field indicates the lot linked to the stock movement.

• Sublot (field SLO)

Sub-lot concerned by the stock transaction.

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

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

• Status (field STA)

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

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

• Movement description (field MVTDES)

Enter a free description that will be registered in all the stock transactions associated with the delivery 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.

• field CCE1

The analytical dimensions are initialized in compliance with the Default dimensions setup. Depending on the setup, they remain available for modification.
When an analytical dimension is used for project management tracking, any modification of the project code leads to the dimension code being reset based on the Default dimensions setup.

• Product (field ITMREF)

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.

• Unit (field PCU)

Product storage unit.

• Quantity (field QTYPCU)

This field indicates the quantity to process, expressed in STK.
 This quantity can be partially changed.

• PAC-STK conversion (field PCUSTUCOE)

This field displays the conversion factor used for the unit of measure of a quantity and the stock unit of the corresponding product.

• Stock unit (field STU)

• STK quantity (field QTYSTU)

• Warehouse (field WRH)

The presence of this field is subject to the activity code WRH.
It is loaded with the warehouse displayed in the document header.

• It can still be changed if this field is set up so as to be entered at entry transaction level.
  When it is entered, the warehouse is automatically loaded on the stock detail lines and cannot 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 multiple warehouses and enter the same slip line on various warehouses, you must enable the entry of the warehouse-line at the entry transaction level. To split a line onto several warehouses, click, the Actions icon and select Enter detailed quantities.
  When a receipt line is distributed on various warehouses, this field is loaded on the slip line with character '$'.

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.
The entered container is used to filter the license plate number selection list.

• 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).
This field is subject to the LPN - License plate no. management activity code.

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.
If you want to enter multiple license plate numbers on the same document line, leave this field blank and click Enter detailed quantities entry from the Actions icon available on the document line.
When you enter a license plate number, there is no restriction on the line quantity, as compared to the capacity of the container used.

• When the license plate number is 'Mandatory', you can leave this field blank and create the relevant license plate number(s) 'on the fly'. The number of containers is determined automatically based on:
  - The container capacity; This capacity is defined on the Product-site record, Management section, based on the packaging and/or stock unit of the product.
  - The line quantity; When multiple containers are required, the number of containers is displayed on the Enter detailed quantities window. This window opens automatically if stock information is missing from the line entry. Otherwise, click the Actions icon from the document line to open it.
  After the creation process, the '$' symbol is displayed in the License plate number field of the document line if the line has been distributed over different license plate numbers. To view the list of license plate numbers used, click the Actions icon on the document line and open the Receipt modifications window.
  You can only create numbers 'on the fly' when the following conditions are met:

- The License plate number is set to 'Mandatory' for the Product category.
- The entered container and unit must be defined in the containers setup table at the Product-site level.
- The container capacity must be defined in the same unit as the document line.
Once the numbers have successfully been created 'on the fly', the License plate number label printing window is automatically displayed if printing is authorized by the entry transaction.

• When the license plate number is 'Optional', no 'on the fly' creation is performed. If you want to use one or several containers, you need to manually enter their license plate number on the document line, or in detailed line entry mode. You may also use the License plate number assignment function afterwards.

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:

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

• the container (if entered); The location type can be modified if the status of the container is ‘Free’, which means it does not contain any stock lines yet.
• the products by warehouse (if warehouses are managed);
• the product-site.

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.
On the other hand, in all cases, these fields can be accessed from the detailed entry of the receipt note, provided that the product is managed by location. If the product is not location-managed, the detailed entry of the receipt does not display the Location type and Location fields.

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

• the location that may be associated to the entered license plate number. It can be modified if the status of the container is ‘Free’ and thus does not contain any stock lines yet.
• the default location defined in the Product-warehouses record, if warehouses are managed.
• the location defined in the Product-site record. This value can later be modified.

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.
If a receipt line is distributed over several location types and/or different locations, the corresponding fields on the document line display the '$' character.

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

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

Enter a free description that will be registered in all the stock transactions associated with the delivery 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.

• field CCE1

The analytical dimensions are initialized in compliance with the Default dimensions setup. Depending on the setup, they remain available for modification.
When an analytical dimension is used for project management tracking, any modification of the project code leads to the dimension code being reset based on the Default dimensions setup.

• Origin line (field LO)