Products

• Category (field TCLCOD)

Code identifying the product category that can be directly entered or chosen in the category table.
 Some fields are associated with this code in the categories table and influence the product creation:

• Sequence number counter: product coding,
• Category type: controls the entry of product unit,
• Creation mode: status default value
  

• Product status (field ITMSTA)

Notion of product status

The product status is used to make the product availability evolve. There are six different statuses possible: Active, In development, Not stocked, Not renewed, Obsolete and Not usable.
During product creation, the default of status depends on the creation mode for the category associated with the product. If the creation mode is Direct, the product status will be Active. If the creation mode is With confirmation, the product status suggested by default will be In development,

Impact of these different statuses in the logistic modules:

Sales Module

• When the product is Active, it can be entered and selected in all sales documents.
• When a product is In development, Not stocked, Not renewed or Expired, it can be entered (a warning message is displayed) in all sales documents, but it will not be suggested for selection.
• When a product is Non usable, it can neither be entered (Blocking message) nor suggested for selection.

Purchase Module

• When the product is Active, it can be entered and selected in all purchase documents.
• When a product is In development, Not stocked, Not renewed or Expired, it cannot be entered except in purchase invoices. It will not be suggested for selection in any document. On receipt, it will however be possible to select an order or shipment for a product having these statuses. For requests for quotation, it is possible to enter a product in the process of being developed if required.
• When a product is in shortage, it can only be entered in the following documents (with a warning message): purchase orders, contracts, buyer plan, workbench (generation of orders or delivery requests only), global planning (generation of orders or delivery requests only), grouping plan (the orders for product having this status have the suffix "-") and purchase invoices.
  It will not be suggested for selection in any document. On receipt, it will however be possible to select an order or shipment for a product having these statuses.
• When a product is Non usable, it can neither be entered (Blocking message) nor suggested for selection. It will also be impossible to select an order or shipment for a product having this status.

Use the status to change product availability. The titles in the local menu can be set up and managed as follows:

• First value: Active: The product is available in all the processes.
• Second value: In development
• Third value: On shortage: The product does not appear in search results, but it can be used by directly entering its code. A non blocking warning message appears. If the product category is associated with the With confirmation creation mode, the status cannot not be accessed and its value is forced to the second value, In development.
• Fourth value: Not renewed
• Fifth value: Expired
• Sixth value: Not usable: The product does not appear in search results and cannot be used in the scripts. If you enter the product code, a blocking message displays.

Non blocking and blocking messages according to the context and status:

• Contexts - Input
• Non blocking message: In development, On shortage, Not renewed, or Obsolete
• Blocking message: Not usable


• Issues - BOMs
• Non blocking message: Not renewed, Expired, or Not usable


• WO (Component)
• Non blocking message: In development, On shortage
• Blocking message: Not renewed, Expired, or Not usable (product not returned)


• WO (parent product)
• Non blocking message: On Shortage
• Blocking message: In development, Not renewed, Obsolete, or Not usable


• Sales order
• Non-blocking message: In development, On shortage, Not renewed, or Obsolete
• Blocking message: Not usable


• Purchase order
• Non-blocking message: On Shortage
• Blocking message: In development, Not renewed, Obsolete, or Not usable


• Assembly – On shortage
• Compound assembled:
• Non blocking: Obsolete, Not renewed, or In development
• Component:
• Non blocking: Obsolete, Not renewed, or In development


• Disassembly – On shortage
• Compound assembled:
• No message: Obsolete, Not renewed, or In development

• Product (field ITMREF)

This field indicates the product reference code. It is generated by a sequence number counter (set up in function Sequence number counters) in the case when the product category has a sequence number counter code.

The reference cannot be modified. It is automatically assigned and displayed when the product creation is complete.

• Description (field DES1AXX)

This long description is used as a title in screens and reports.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for the folder.

• Description 2 (field DES2AXX)

This long description is used as a title in screens and reports.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for the folder.

• Description 3 (field DES3AXX)

• Service life start (field LIFSTRDAT)

Product start-of-life date: it is not possible to enter sales orders for this product before its start-of-life date.

• Service life end (field LIFENDDAT)

Product end-of-life date: when this date is exceeded, it is not possible to enter orders to the supplier.

• Production text (field WMFGTEX)

• Picking text (field WITPTEX)

This flag is used to specify that a preparation text is defined for the product/customer combination. It is then used in picking tickets and delivery notes.

• Search key (field SEAKEY)

Alphanumeric field of 20 characters. This information is used as sort and selection criterion in the product search window and in the stock inquiry screens.

• Product line (field CFGLIN)

A product line is used to:

• define spcific indentifying fields for a product group,
    The 'Configurator' module is based on the item product lines, but product lines can be used separately from the configurator.
• define matching rules between products.
  

• UPC code (field EANCOD)

Barcode identifying this product

The auto-completion is available in this field.
Start to enter characters from the product code, the produc description or others and tab.
A screen displays a list of results. Select the right value.

 The auto-completion is only available if the value of parameter Automatic selection (chapter Sales/group Miscelaneous) is set to 'Yes'.

• Standard (field ITMSTD)

Specify here the standard with which the product complies (manufacturing or quality national or international standard).

• User access (field PLAACS)

This access code is used to specify the user in charge of the product quality function for the category (correction of the product).
The user can modify or cancel the product if this access code is associated with their profile with a Modification indicator set to 'Yes'.

• SAF-T product type (field ITMSFTTYP)

This field is only displayed when the KPO - Portuguese localization activity code is activated. It only applies to the SAFT file generation. This file is exported according to the type of product indicated:

• None
• Product
• Service
• Other (including fixed assets).

• field TSICOD

Alphanumerical code to choose in the statistical group table.
The statistics groups are used in the statistical processings as well as selection criteria in many programs.
There are a maximum of five statistical groups, and their number as well as their title can be set up when installing the software. The assignment of a statistical group representing the commercial group for a product is mandatory, it serves to sub-divide the product catalogue in the database. The CODEFAMCIA general setup makes it possible to determine which of the five product statistical groups is dedicated to this use.

• Sub Intrastat (field EECGES)

Used to indicate if the product is subject to an Intrastat declaration.

• Customs reference (field CUSREF)

Customs BOM associated with the product, used upon extraction of intra-community entries. It can only be entered if the product is subjected to the Intrastat file.

• Region/State (field STAFED)

This field is used to enter the state of origin where the product was manufactured.

• Product information (field PLMITMREF)

This field is submitted to the PLM (Interface PLM - X3) activity code.
It is only loaded if the product has been created by import from the PLM @UDROS product.
It contains, in that case, the original reference of the product in PLM.

• field BUTATTURL

This button is submitted to the PLM activity code (PLM Interface - X3.)
It is used to open the URL that gives access to a web page containing the PLM documents linked with the product.

• PLM history (field BUTHISURL)

This button is submitted to the following activity code: PLM (PLM Interface - X3.)
It is used to open the URL that gives access to a web page displaying the history of the product.

• Product notes (field ITMNOTE)

Click on this icon to display a screen where you can:

• Enter information on the product as a note. This information can relate to product availability, additional or substitute products, or a promotional message.
  This information is available for inquiry in the functions that have been selected at the Note category level.
• Define a validity period for the note.
• Specify it the note must be displayed automatically.
• Create multiple notes for the same product, and indicate if they must be displayed as a priority.

Notes are limited to a screen inquiry and cannot be printed.

For further information, see the documentation on Notes.

• Image (field IMG)

This field makes it possible to specify the type of graphic object that will be used :

• Check box : Only for a field of type Yes/No.
• Radio buttons : Only for a field of type local menu with a restricted number of choices.
• Spin button or slider : Only for the numeric fields.

On a field in the grid section, the authorized objects are : the check box and the icon.

• Stock management (field STOMGTCOD)

Several management methods can be selected, which influence the management of stock quantities:

• Not managed: the product is never transferred by the stock. This is the case for example, for services or general purchases. According to the category type, this value can be imposed (generic products or sub-contractor for example).
• Product managed: the product is normally managed, without any special feature.
• Product managed title: A product is managed in stock, with a rule. The management of the quantities in stock is carried out with an active quantity and a physical quantity.

• Lot management (field LOTMGTCOD)

Specify in this block whether the product will be lot managed. The lot can be mandatory or optional (in the latter, it will be possible to have for the same product, stock lines with and without lots). The lot number is a differentiating criterion for the stock line.
 See the description of a Stock line for further information.
It is also possible to make provision for management with sub lots, which are sub-divisions of a lot. The sublot number is also a differentiating criterion for the stock line. The numbering of sub-lots is free (number or group of characters for 5 places, by default, on stock receipt the first sub-lot for a lot will be suggested to 00001).

The lot management mode for the product stock entries depends on this parameter:

• 'Not management': the product is not managed by lot in stock. This rule is applied to entries as well as to issues,
• 'Optional lot': the product lot number is not mandatory. It is then possible to have for a same product stock lines with lot and stock lines without lot,
• 'Mandatory lot': the product lot number is mandatory,
• 'Lot and sub-lot': the sub-lot is a sub-division of the lot.

The choice of lot management mode can only be modified if the product has no stock.

• Lot sequence (field LOTCOU)

This field is used to specify a global lot counter (via the Sequence Number Counter Assignment function - stock section) that is used as default value for field "Lot sequence number counter" of the category Product.
The lot sequence number counter of the category Product is also used as a default value by the product lot sequence number counter. The lot code contains a maximum of 15 characters.
At the time of a receipt into stock for a product managed by mandatory lot, the system tries to number it with the help of the product sequence number counter.
 The management of lots and sub-lots in the folder is controlled by the activity codes LOT, for the management of lots and SLO, for the management of sub-lots.
 If the Lot management mode has been chosen with a product sequence number counter, the number of the sequence number counter must be specified here. It is possible to open the selection window in the sequence number counter table or to create a new one via the tunnel.

• Stock < 0 authorized (field NEGSTO)

This tickbox is used to indicate whether it is possible to issue stock that is not present in the system.
Example: to deliver stock that has physically been delivered or manufactured, but for which the computerized input to stock has not been entered yet.
The system then generates a "pending" issue. This issue is adjusted upon input of the stock into the system.

• Management mode (field STDFLG)

The product management mode is used to specify whether the products are:

• not managed,
• not managed in stock,
• managed by order,
• managed for the stock.

This indicator is used in the reorder calculation (MRP and MPS).

• Traceability (field TRKCOD)

Indicate if the stock movements of this product must update the log file.
Two types of update are available:

• Detailed Update: each movement is logged,
• Aggregated Update: the movements related to a single product, lot, status, document and transaction are totaled.

The aggregated update is recommended for work order receipts and issues so the returned log is split only once.

• Potency % (field DEFPOT)

Average potency in percentage, to be defined for the active products. it is used for receipt to stock as a default value, before the quality control measures the real potency. This field is accessible if the stock management mode of the product is "Potency managed".

• Alternate product (field RPLITM)

Enter an alternate product reference. This product can be displayed on the material issue slip or suggested if there is a shortage in the work order management function. Selecting an alternate product results in two checks:

• Existence check: the selection window of a product in the file is available
• Loop check: to avoid landing on the same product during cascading replacements

If you enter an alternate product, version numbers are determined with respect to this new product.

During line entry in the Order function (GESSOH), the Alternate product option is available from the action icon for the Ordered qty. field in the grid. It is not available if the line has been allocated or partially delivered, billed, or prepared.

• Description (field RPLITMDES)

This field indicates the substitution product.

• Product type (field INVPRODTYP)

• Serial no. management (field SERMGTCOD)

Use this field to indicate if the serial number management applies to the product. If yes, you can program a sequence number counter for the serial numbers (with a maximum of 10 characters).
Several management modes are available:

• On issue : serial numbers are not managed in stock, but only indicated upon issue for customer tracking purposes.
• Issue & Receipt : the management of the serial numbers is per unit. The serial number is a differentiating criteria for the stock line: X serial numbers of the same lot / sublot / status / location are present on X different stock lines.
• Global receipt & issue : the management of the serial numbers is global. The serial number is not a differentiating criteria for the stock line: a range of X serial numbers of the same lot / sublot / status / location is present on one stock line.

 The serial number management in the folder is subject to the SER activity code - Serial number management.

• Serial sequence (field SERCOU)

Sequence number code which is used for assigning serial numbers automatically.

• Management (field EXYMGTCOD)

Expiry management is subject to the activity code EXY - Expiry management.

The calculation mode of the expiry date can be set up according to the criteria:

• Not managed
  If there is no management, the fields status and lead time cannot be entered.
• Without rounding
  The expiry date is calculated based on the number of days.
• Rounding month end
  The expiry date is calculated based on a rounded value on the month's end.
• Rounding month start + 1
  The expiry date is calculated based on a rounded value on the next month's start.
• Mandatory entry
  If the option "Mandatory entry" is selected, an entry window for the expiry date will automatically open when recording of the stock receipt. The expiry date will be initialized based on the reference date and lead time.
• Manual entry
  If the option "Manual entry" is selected, an entry window for the expiry date will open automatically when recording the stock receipt. The expiry date will be blank.

 The expiry date management is only possible if the product is managed by lot.
In this case, the status of expired lots can be planned.
This set of information, defined at the category level, is used at the product level where the shelf life can also be specified.

• Status (field EXYSTA)

 This field cannot be accessed if field Management is set to "No management".

When a lot in stock is to expire, a process is used to automatically change its status based on a product setup.

• 'A': the product does not change status on expiry.
• 'Q': the product can be controlled again on expiry, for a potential date extension or rejection.
• 'R': the product is rejected when it has reached its expiry date.

• Lead time (field SHL)

This field can be accessed depending on the management mode used for the product expiry.
Enter the expiry lead time in days or months. It is used in the calculation of the expiry date and use-by date (UBD) of a lot upon stock receipt.

• field SHLUOM

Scroll-down list used to determine the time unit (day or month) associated with the previous field.

• Recontrol lead time (field SHLLTI)

The lead-time of the new control is used on stock receipt. It is used to calculated the new control date based on the reference date. It is entered in days or months.
 The new control date cannot go beyond the limit date of lot use.

• field SHLLTIUOM

Scroll-down list used to determine the time unit (day or month) associated with the previous field.

• Recontrol status (field NEWLTISTA)

When a lot in stock reaches a new control date the system automatically changes its status based on the controls defined on the product record.

• A. When the new control date is reached the status of the product can change to status Q or R.
• Q. The product can be resent through quality control for either an extension to the control date or for rejection.
• R. When the new control date is reached the product will be rejected.
  
  

• UBD coefficient (field DLU)

The use-by date (UBD) coefficient can only be accessed when the two following conditions are met:

• the expiry is managed at the product level,
• the expiry management mode is not based on a rounded value (start or end of the month).

This coefficient is used to calculate, in calendar days, the use-by lead time, based on the shelf life defined at the product record level.
UBD lead time = Shelf life x UBD coefficient.

The value of the coefficient must be between 0.1 and 1: the UBD cannot exceed the expiry date.

This UBD lead time is used to determine the use-by date of the product, based on its stock receipt date.
UBD = Lot receipt date + UBD lead time
Defining a Use-By Date provides the customer receiving the lot with the guarantee that the use-by date of their goods is more or less distant from the expiry date.

For example :

• Shelf life = 2 months (60 days)
• UBD coefficient = 0.5
• UBD lead time = 30 days
• UBD = receipt date + 30 days

A UBD coefficient can be entered in the Product record, in the Product-site record and in the Customer-product record. The UBD coefficient entered on the Customer-product record is used to determine the use-by date specific to one customer. In this case, when allocating a stock (order, stock issue, etc.), the UBD defined for the customer overrules the one defined for the Product-site.

• UBD lead time (field DLULTI)

This field cannot be entered. It displays the use-by lead time calculated based on the UBD coefficient.
This lead time is expressed in calendar days.

• field DLULTIUOM

This field cannot be entered. The UBD lead time is always expressed in calendar days.
UBD lead time = Shelf life x UBD coefficient.

• Version management (field ECCFLG)

The management of versions is subject to the EEC - Product version management activity code.

During the lifetime of a product, some of its characteristics can sometimes be modified. These modifications can be tracked back by activating the version management.
To do so, the product must be managed in stock. The tracking of versions will then be active at the Manufacturing module level. For the tracking of versions to be effectively managed at the stocks level, the product must also be managed in Lot (mandatory).

The choice of managing or not versions is initialized in the product Category. At product level, the management of versions is an option that can be modified, provided that the product has no stock.
In product creation, if the management of versions is activated, a message is displayed to suggest the automatic creation of the first major version. This version takes the To be activated status. In order to use the version, its status must be modified.

• Stock version (field ECCSTO)

This field can only be accessed if the tracking of versions is managed at the stocks level: the product is managed by lot and the management of versions is activated.
It is used to specify if only major versions or majors and minor versions are to be managed at the stocks level.

• Major: if you select this option, only the major versions of this product are managed at the stocks level. You must enter in the next field a counter code for major versions.
  
• Major and minor: if you select this option, both the major and minor versions of this product are managed at the stocks level. You must enter in the next fields a counter code for major versions as well as a counter code for minor versions.

A link can be used to directly access the management screen of Versions.

• Versions (field ECSMGT)

Click on the arrow for direct access to the Versions management screen.

• Major sequence (field ECCMAJ)

If the major versions are managed in stock, enter here the counter code used to automatically assign a code to each major version of the product.
For instance, the major versions can be identified by an alphanumeric code: A then B, then C, etc.

• Major version (field ECCVALMAJ)

This field displays the number of the last major version with the 'Active' status. Otherwise, the number of the last major version with the 'Stopped' status will be displayed.
If only versions with the 'Prototype' status exist, the version number will not be displayed.

• Status (field ECCSTA)

This field contains the status of the major version displayed.

• Minor sequence (field ECCMIN)

If the major and minor versions are managed in stock, enter here the counter code used to automatically assign a code to each minor version of the product.
For instance, the major versions can be identified by an alphanumeric code: A then B, then C, etc., and the minor versions by a numeric code: 01, 02, 03, etc.

• Minor version (field ECCVALMIN)

This field displays the last minor version number.

• Routing version (field ECCROUFLG)

Click this check box if routings for this product can be version managed. This check box is only available if a major version counter (field Major sequence) has been defined for this product and a major version is displayed.

With this check box selected routings versions (major and minor) can be managed independently of any stock or bill of materials (BOM) versions of this product.

Leave this check box blank if you do not require routing versions for this product.

 Routings versions for this product can only be managed if the product is version managed.

 You cannot amend this flag once the first major routing version has been assigned to this product.

• Family (field BRDCOD)

Cost calculations are used to break down material costs. Use this field to define which field (subtotal) the material cost for this product must be posted.

 Activity code MAT - Number of material groups defines how many family cost groups are available.

• Cost type (field PCCCOD)

Use this field to assign this product code to a specific cost type. Cost types are used by Project management. In a product context, a cost type defines the types of product that can affect a project such as the purchase of raw materials.

 You should only define a project cost type for products managed 'On stock' and for purchased products managed 'By order'. You do not need to define a cost type for manufactured products managed 'By order' as the products to be valued, as per their cost type, will be the components in the bill of materials (BOM), not the manufactured product itself. The components will either be managed 'On stock' or purchased 'By order'.

• Allergens (field ALG)

This field displays the allergen associated with this product. The product category determines the option that appears. This field is available only if the FOA activity code is active.

• If this is a manufactured product, you cannot edit this field because it displays the allergen codes based on the allergen rollup function performed for the parent product. The rollup explodes the BOM/Recipe and collects all unique allergen codes. This can be useful if there are concerns about the results or if the information is up to date.
• If this product is a purchased product, you can edit this field based on the allergen selection function. You can select multiple items per product.

• Rollup date (field ALGDAT)

This field is used to display the allergen total date. It is updated when modifications are applied to the allergens linked to the product.

This field is only available when the FAO activity code is activated.

• Rollup code (field ALGBOM)

This field is used to display the allergen total BOM. It is updated when modifications are applied to the allergens linked to the product.

This field is only available when the FAO activity code is activated.

• Stock unit (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• Density (field DTY)

Use this field to define the density of this product, where the density is the mass of this product (measured in, for example, g (grams) or Kg (kilograms)) divided by its volume (measured in, for example, mL (milliliters) or cm³ (cubic centimeters)).

This field is only available if Activity code UML - Link quantity unit of measure is active.

• STK label format (field STULBEFMT)

This fields corresponds to the format of the stock labels.

• Weight unit (field WEU)

The weight unit.

• STK weight (field ITMWEI)

Weight of a product stock unit, expressed in the displayed weight unit.

• Volume unit (field VOU)

This field indicates the product volume unit. It is particularly used when distributing invoicing elements on the lines according to the prorata calculation of product volumes.

• STK volume (field ITMVOU)

This field indicates the volume of a product stock unit in the volume unit displayed.

• Purchase unit (field PUU)

This is the purchase unit defined for the product-supplier pair or for the products that do not exist in the Product-supplier record.
The product has two purchase units:

• purchase unit defined at the level of the unit product record,
• purchase unit linked to the supplier.

The purchase unit cannot be modified.

This unit is used as the default value when entering an order, subcontract order or receipt, with the supplier unit suggested in priority when the product-supplier record exists.
The purchase units are accessible depending on the type of category.
 Upon invoicing of a product, the product PUR is used.

• PUR-STK conv. (field PUUSTUCOE)

Coefficient used to calculate the quantity in STK unit from a quantity entered in PUR: Qty in STK = Qty in PUR * coeff.
This coefficient can be accessed if a purchase 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.

• Sales unit (field SAU)

Sales unit of the product, to which is associated the sales price. Sales unit of the product, to which is associated the sales price. It is used by default upon sales document entry.
The sales unit entered here in the unit tab of the product record is reminded by default in the tab Sales and Customer.
 The sales unit can be accessed according to thecategory type.

• SAL-STK conv. (field SAUSTUCOE)

Coefficient used to calculate the quantity in stock unit, from a quantity entered in sales unit. Qty in STK = Qty in SAL* factor
This factor is available when a sales unit has been entered, and has a different value than the stock unit. It can be initialized using the conversion factor table if the combination exists.

• Changeable (field DACSAUCOE)

This flag is used to authorize the modification of the coefficient between the sales unit and the stock unit at the level of a sales document.

• Statistical unit (field SSU)

This unit is used for the calculation of statistics in quantity. It is used to carry out analyses with a unit that is common to all products, when the analysis criteria are of type customer or supplier, for example.

• STA-STK conv. (field SSUSTUCOE)

Coefficient used to calculate the quantity in stock units from a quantity expressed in statistical units Qty in STK = Qty in statU * coeff
This coefficient can be accessed if the statistical unit has been entered, and it has a different value from the stock unit.
It can be initialized using the conversion factor table if the combination exists.

• Intrastat additional unit (field EEU)

This is the additional EU unit in which is expressed the quantity issued for the Customs Document File.

• EU-STK conv. (field EEUSTUCOE)

Conversion coefficient EUU-STK
Coefficient used to calculate the quantity in stock units from a quantity expressed in additional EU unit Qty in STK = Qty in EUU * coeff
This coefficient can be accessed if the statistical unit has been entered with a value different from the stock unit.
It can be initialized using the conversion factor table if the combination exists.

• Unit (field PCU)

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.

• PAC-STK conv. (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.

• Changeable (field DACPCUCOE)

This indicator is used to authorize the modification of the coefficient between the packing unit and the stock unit at the level of the order or the receipt.

• Label format (field LBEFMT)

This filed indicates the label format.

• Issuing PAC (field PCURUL)

This local menu is used to chose the fashion in which the stock lines will be exploded in the case where unpacking takes place.

• Unpacking: it means that it is possible to smooth out the fraction of the stock line by causing a split if necessary (this choice is only possible if the entry of the coefficient is authorized).
  Example:
  Let us consider a stock line of 5 boxes each containing 12 units. 18 units are picked on this line.
  This results in 2 stock lines: one line with 3 boxes containing 12 units and one line with 6 units.
• Incomplete: it means that it is possible to vary the coefficient for the stock line by causing a split if necessary (this choice is only possible if the entry of the coefficient is authorized). Example:
  
  Let us consider a stock line of 5 boxes each containing 12 units. 18 units are picked on this line.
  This results in 2 stock lines: one line with 3 boxes containing 12 units and one line with 6 units.
• Splitting: this value means that it is possible to vary the quantities on the stock lines by division.
  The packing unit must as a consequence be decimalized.
  For instance:
  Let us consider a stock line of 5 boxes each containing 12 units. 18 units are issued from this line.
  This issue results in a stock line of 3 boxes and a half containing 12 units

 The sales and purchase units must occur in the packing units table if the unit entered in the document is to be kept in the resulting stock line. If this is not the case, the stock line generated by the document in sales or purchase units is managed in stock units.

 Stock issue modes Unpacking and Incomplete are not authorized for materials weighed with the weighing station.

• Accounting code (field ACCCOD)

The accounting code is a default value used in the setting up of accounting journals. It refers to a table in which a certain number of elements can be found (collectives, accounts or parts of accounts) that can be used to determine the accounting journals that will be posted.

• field VACITM

Use this field to specify the tax level.
Each country being ruled by its own tax rates, the tax level alone does not enable the rate to be applied to be determined. The tax is generally determined by crossing the tax rule associated with a BP and the tax level associated with a product.
 See the documentation on Tax determination for further information.
The tax level only displays the list of the different rates applied within a same rule.

• SST tax code (field SSTCOD)

Indicate the default value of the tax code Sage Sales Tax (SST). This tax code is recognized by the Avalara system and is used to identify line types for fiscal purposes.
All document costs are sent to SST in the form of document lines. For instance transport costs, handling costs and on-line product costs. This field is only available when the LTA activity code is activated.

• Capitalizable (field FLGFAS)

This check box is used when the Fixed Assets module is managed.
When it is activated, it is used to identify the product as capitalizable, that is to say, that can be referenced on an expense saved by direct entry or automatically generated upon the posting of a stock miscellaneous issue movement.

 When the expense is created by validating a purchase invoice, the product does not need to be set up for capitalization: if the product can effectively be capitalized, the expense creation will be carried out automatically.However, if the product is not fit for capitalization, the expense will be created only after validation of a confirmation message.In both cases, the creation is authorized only if the setup of the account on which the invoice line is allocated allows it (check boxes Fixed asset tracking and Expense creation activated).

• Dimension type code (field DIE)

This grid is automatically loaded with the default dimension types associated with the 'Product' basic data.

• Dimension (field CCE)

An analytical dimension is an element of the analytical chart of accounts on which accounting entries can be posted.
Each analytical dimension type represents a specific division of the company into a set of analytical payment attributes. An analytical dimension is thus an analytical payment attribute within a dimension type.

• Legislation (field LEGGRP)

This column displays as many lines as there are legislations defined in the folder, making it possible to differentiate the product group code by legislation.

• Family (field ACGGRP)

This field can only be accessed if the product is capitalizable.
It is used to enter the Fixed asset Group of the product. It is possible to enter a specific group by legislation. The use of each group can be limited to a given legislation.
This group is automatically assigned to the expense created on recording an expense related to this product. In the case where the section associations are set up for the Expense object, the fixed asset group can be used to define the values of the various sections, including the accounting allocations.

The definition screen of Fixed asset groups which can be accessed by right-clicking on the field, is used to:
- view the values determined by the associations, for the entered group code,
- access the entry/modification screen of the values of these associations.

• Type (field ITMTYP)

A sold product can be:

• a standard product,
• a BOM parent product: defines a group of products usually sold together. You can delete products from the BOM as required.
• a fixed kit: defines a group of products that must be sold together. You cannot delete products from the BOM.
  A product of the Service category and Not deliverable cannot be defined as Kit parent product.

A BOM or kit assembly directly defines a sales BOM.
On entry of a product of this type in a sales document, the system searches for the associated BOM (with the same name according to the sales alternative specified) and will note in the document the assembly and all the components, the options or variants comprising this sales BOM.

• Sales unit (field ITSSAU)

This is the sales unit for the product defined in the Units tab.

• Substitution product (field SBSITM)

This information is used to replace a product from a certain date.

During the entry of a product that should be substituted, the product code entered will automatically be replaced by the substitution product specified here.

If you enter a substitution product, version numbers will be determined with respect to this new product.

• field SBSITMDES

This field indicates the substitution product.

• Substitution date (field SBSDAT)

This is the date from which the substitute product will replace the current product in a sales document.

• Delivery tolerance % (field MINRMNPRC)

This is the tolerance percentage below which the order line will be closed in the case of a partial delivery.

• Minimum quantity (field MINQTY)

This is the minimum quantity expressed in sales unit that can be entered on a sales order.
 This control can be blocking depending on the SDACLOK user setup.

• Maximum quantity (field MAXQTY)

Maximum quantity of order, in sales units.

• Invoicing term (field INVCND)

This field can only be accessed when the following conditions are met:

• the category type is Service or Generic,
• the flow is Sold flow and not Deliverabletype.

You use this field to enter an Invoicing term. This information is optional. This information is used as the default invoicing term on the sales order lines when the header invoicing term is not entered and cannot be used to initialize the invoicing term on order lines.

• Price origin (field BASPRIORI)

This field is used when entering a sales document if no price list has been defined or if the price list search has been unsuccessful.
It is used to specify how the default base sales price is obtained.

• 'Entered': the base sales price is populated directly in the corresponding field.
• '% Purchase Price': the base sales price is determined according to the base purchase price specified in tab "Supply" and to the percentage entered in field "% applied", as follows: Base purchase price + (Base purchase price * % applied).

• % applied (field PURPRIPRC)

This field can be accessed only if field "Price origin" is set to 'Purchase Price %'. It is used to specify what percentage is to be applied to the base purchase price specified in tab "Supply" in order to obtain the base sales price.

• Base price (field BASPRI)

This field can only be accessed when the Price origin field is set to 'Entered'.

Indicate the tax-excluding base price of the product. This price is used as the sales price if no price list has been able to determine the gross price in the sales document.

This amount is expressed in the company's management currency to which the default site is associated for the Common data management. This setup is carried out at the level of the function profile assigned to the user.

 It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).

If no site is entered at the function profile level, the amount is expressed in the folder currency.

• field CUR

This amount is expressed in the company's management currency to which the default site is associated for the Common data management. This setup is carried out at the level of the function profile assigned to the user.

 It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).

If no site is entered at the function profile level, the amount is expressed in the folder currency.

• Minimum margin (field MINPFM)

This is the margin percentage below which it is not possible to descend during sales document entry.
 This control can be blocking according to the value of the user parameter SDACLOCK-Price,margin,qty non-blocking ctrl (VEN chapter, AUZ group).

• Theoretical price (field THEPRI)

This theoretical price is for information only.

This amount is expressed in the company's management currency to which the default site is associated for the Common data management. This setup is carried out at the level of the function profile assigned to the user.

 It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).

If no site is entered at the function profile level, the amount is expressed in the folder currency.

• Minimum price (field MINPRI)

This is the minimum selling price that can be entered for this product on a sales document.
 This control can be blocking according to the value of the user parameter SDACLOCK-Price,margin,qty non-blocking ctrl (VEN chapter, AUZ group).

This amount is expressed in the company's management currency to which the default site is associated for the Common data management. This setup is carried out at the level of the function profile assigned to the user.

 It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).

If no site is entered at the function profile level, the amount is expressed in the folder currency.

• Warranty (month) (field GUAMON)

This is the number of months of warranty for the product after its shipment.
 This information is not used by the Customer support module. It remains purely for information purposes.

• Loan authorized (field LNDFLG)

This information is used to authorize the loans for a customer for a product.

• Back-to-back order (field CTMFLG)

When a product can be managed with a back-to-back order, the system will automatically suggests to generate a back-to-back order during the creation of an order line.
There are three types of back-to-back orders:

• Purchase back-to-back order with receipt
• Direct back-to-back order (the supplier delivers the goods to the customer)
• the production-type direct order.

The type of direct proposed by default depends on:

• The product category,
• The type of replenishment suggestion defined on the Product/Site record,
• the direct quantity defined in tab Sales of the product record.

In the event of a purchase back-to-back order, the system will determine that the back-to-back order is a direct order (delivery by the supplier to the customer) when the ordered quantity is larger than the direct quantity (expressed in the product sales units).
At the level of the Product-Site record, and for each site that requires the management of back-to-back orders for this product, a back-to-back order type allocation rule is activated (the Back to back method (1 to 1) check box is selected), and it must be associated in the Planning tab.

• Version preloading (field LOAECCFLG)

Check this box to specify that the last active version of the product must be preloaded by default in the Major version and Minor version fields of documents. This setup can be individualized by customer.

• PO direct qty. (field CTMQTY)

This field contains the quantity (expressed in sales units) from which the direct order will be straightforward.

• Sales text (field WITSTEX)

When checked, this information means that a sales text (used in the document lines) has been defined from the menu bar.

• Creation of customer base (field CREMAC)

This field is used to activate all the automatic mechanisms of generation, the installed base tracking and the service contracts associated with the product when it comes to entering sales movement.
These various mechanisms are implemented in the following functions:

• validation of the sales deliveries,
• validation of the sales invoices,
• entry of the sales returns,
• entry of loan returns.

• Voucher category (field FLYCAT)

This field is used to indicate the Crystal Report document that will be used to print the warranty coupon in case of a direct sale.

• Loan contract (field TPLCONLND)

This field is used to indicate the warranty applied during the loan of this product.
In fact, the standard coverage of a product on loan is not carried out thanks to a service contract but directly with a service contract template.

• Warranty contract (field TPLCONGUA)

This field indicates if the product benefits from a warranty.
It displays the warranty contract template that will be used as the basis of the service contract creation that will automatically benefit the customer at the time of acquiring the product.
This information is only used if the creation of the customer installed base is activated.

• Service contract (field TPLCONSRV)

This field only concerns the products corresponding to the notion of a service contract.
The template indicated will be used as a support for the creation of a maintenance contract entered as a line in a sales order.

• Points debit (field PITDEB)

It is possible to enter a point debit rule directly in a product record.
The entry of a value in this field leads to the creation of a point debit rule where only the product component is entered.
The debit indicated on the product only concerns direct debit. All the additional debits must be entered on the points debit rule.

• Include unassigned items (field NULPIO)

This option is used to block the tree of rules for debiting points during the analysis of a service request coverage.
In other words, it is used to block any consumption of points for service requests concerning this product without cross-referencing with a particular skill.

• Tokens to be credited (field PITCDT)

This field is used to indicate the number of tokens that a customer can accumulate for each order for this product.
The value entered MUST be associated with a unit.

• all the (field PITCDTUOM)

This unit is used to value the number of tokens that a customer can credit to each order for this
It is indispensable for carrying out any conversions necessary for the token credit calculations.

• BOM code for after-sales (field ALTBOMHDK)

This field is used to associate a BOM designed with after-sales use.
For example, this BOM is used to facilitate the identification of the components forming a complete product and therefore which may potentially have defects.

• Product type (field HDKITMTYP)

This field is used to segment the product catalogue into large product categories.
This information is notably used during the entry of the service request consumptions.
On the creation of the product record, the product type taken by default is 'Other'.

Product type = 'Other'

This is in general a product having a physical existence.
For this product type, the following functionalities are available:

• automatic generation of the product base on the sales entries,
• assignment of a loan contract,
• assignment of a warranty,
• assignment of a warranty voucher template,
• definition of points deduction rules,
• definition of the token assignment rules,
• assignment of an alternative BOM suitable for the identification of defective components,
• product base inquiry,
• competitive product inquiry,

Product type = 'Spare part'

This is a product possessing a physical existence that is either sold to the customer as an accessory or consumed by after-sales technicians for maintenance or repairs.
Characteristically for these products a BOM is rarely useful.
In the same way, they are rarely subject to tracking via the customer base.
The following functionalities are available:

• definition of points deduction rules,
• definition of the token assignment rules,
• activation of stock issue by default functions,
• competitive product inquiry.

Product type = 'labor'

This product type corresponds to the provision of a service.
For this product type, the following functionalities are available:

• definition of points deduction rules,
• definition of the token assignment rules,
• definition of the time units used by default for time booking,
• competitive product inquiry.

Product type = 'task expenses'

This type is used to isolate from the product catalogue the task expenses that can be invoiced to the customers.
The quantity of products of this type is generally limited. Their definition essentially provides important ergonomic gains at the time of the entry of after-sales consumptions.
There is no additional information that is particularly useful for the product type.

Product type = 'service contract'

This product type corresponds to generally to maintenance contracts that can be invoiced.
Only one item of additional information is necessary in this case: the service contract template that will serve as the base for the contract creation from the sales order line entry.
The competitive product inquiry can also be useful to compare the formulas and price lists recorded for the market.

• Stock issue by default (field STOISSDEF)

This field only concerns products managed in stock.
It is used to activate by default the opening of the stock issues entry window when the product is consumed as a service request.

• Unit for days (field DAYUOM)

All item of the type labor MUST contain a unit for each of the following three notions:

• Day,
• Hour,
• Minute.

These three pieces of information are essential to the conversions carried out by the automatic records of service requests time stamp.

• Unit for hours (field HOUUOM)

• Days - hours coef. (field COEHOUDAY)

• Unit for minutes (field MNTUOM)

All item of the type labor MUST contain a unit for each of the following three notions:

• Day,
• Hour,
• Minute.

These three pieces of information are essential to the conversions carried out by the automatic records of service requests time stamp.

• Customer (field BPCNUM)

This field is used to enter the code used to identify the customer. It can be entered directly or selected from the Customer table.
 This customer list is not exhaustive, any customer not present in this list can still order the product.

• Customer (field XBPCNUM)

This is the code and the Company Name of the customer being viewed.

• Customer product (field XITMREFBPC)

Reference of this product for the customer.
It is possible to enter a sales document directly with this reference. The system automatically replaces this reference with the internal reference of the product.

• Customer description (field XITMDESBPC)

Description of this product for the customer.

• Intersites (field XBETFCY)

This field indicates whether the customer referenced is a customer of the group or not.
 When a customer is an inter-site customer type, the Inter-site tick box is automatically ticked.

• Sales unit (field XSAU)

This field indicates the sales unit of the product for this customer.
This unit can be different from the usual sales unit for this product. It is used by default in sales documents entry.

• SAL-STK conv. (field XSAUSTUCOE)

Coefficient used to calculate the quantity in stock unit, from a quantity entered in sales unit. Qty in STK = Qty in SAL* factor
This factor is available when a sales unit has been entered, and has a different value than the stock unit. It can be initialized using the conversion factor table if the combination exists.

• Packing 1 (field XPCU1)

This field is used to define a first packing unit, usually requested by the client.

• PAC1-SAL conv. (field XPCUSAUCO1)

PAC-SAL unit conversion coefficient
Coefficient used to calculate the quantity in SAL unit from a quantity entered in PAC unit: Qty in SAL = Qty in PAC * factor
This factor is available when a packing unit has been entered, and has a different value than the sales unit.
It can be initialized using the conversion factor table if the combination exists.

• Packing 2 (field XPCU2)

This field is used to define a second packing unit, usually requested by the client.

• PAC2-SAL conv. (field XPCUSAUCO2)

It is the PAK-SAL conversion coefficient. It is used to calculate the quantity in SAL, from a quantity entered in packing unit. Qty in SAL = Qty in PAK * coeff
This coefficient can be accessed if the packing unit has been entered with a different value from the sales unit.
I is initialized by the conversion coefficient table if the combination exists.

• Packaging (field XPCK)

This field displays the packaging usually used to deliver the products to the customer.
The packaging code is used in the packing function, but it can be modified in order line entry.

• Packaging capacity (field XPCKCAP)

It is the the number of products, expressed in sales units, that the package can contain.

• UBD coefficient (field XDLUBPC)

The use-by date (UBD) coefficient can only be accessed when the two following conditions are met:

• the expiry is managed at the product level,
• the expiry management mode is not based on a rounded value (start or end of the month).

This coefficient is used to calculate, in calendar days, the use-by lead time, based on the shelf life defined at the product record level.
UBD lead time = Shelf life x UBD coefficient.

The value of the coefficient must be between 0.1 and 1: the UBD cannot exceed the expiry date.

This UBD lead time is used to determine the use-by date of the product, based on its stock receipt date.
UBD = Lot receipt date + UBD lead time
Defining a Use-By Date provides the customer receiving the lot with the guarantee that the use-by date of their goods is more or less distant from the expiry date.

For example :

• Shelf life = 2 months (60 days)
• UBD coefficient = 0.5
• UBD lead time = 30 days
• UBD = receipt date + 30 days

A UBD coefficient can be entered in the Product record, in the Product-site record and in the Customer-product record. The UBD coefficient entered on the Customer-product record is used to determine the use-by date specific to one customer. In this case, when allocating a stock (order, stock issue, etc.), the UBD defined for the customer overrules the one defined for the Product-site.

In creation mode, the UBD coefficient is empty.

Example 2 with UBD defined for the client:
Sales order with requested delivery date (determined from the shipment date + lead time): 10/01/2014
Lot A

• Stock receipt date: 01/01/2014
• Shelf life: 20 days - Expiry date: 20/01/2014
• UBD coefficient for product-site: 0.6 - UBD lead time for product-site: 12 days - Product-site UBD date: 12/01/2014
• UBD coefficient for customer-product: 0.4 - UBD lead time for customer-product: 8 days - Customer-product UBD date: 08/01/2014

Lot B

• Stock receipt date: 01/01/2014
• Shelf life: 20 days - Expiry date: 20/01/2014
• UBD coefficient for product-site: 0.6 - UBD lead time for product-site: 12 days - Product-site UBD date: 12/01/2014
• UBD coefficient for customer-product: not specified

During the allocation:

• Lot A was not selected because the customer-product UBD was dated 08/01/2014, which is prior to the delivery date 10/01/2014.
• Lot B was selected because the product-site UBD was dated 12/01/2014, which is later than the delivery date 10/01/2014.

• UBD lead time (field XDLULTI)

This field cannot be entered. It displays the use-by lead time calculated based on the UBD coefficient.
This lead time is expressed in calendar days.

• field XDLULTIUOM

This field cannot be entered. The UBD lead time is always expressed in calendar days.
UBD lead time = Shelf life x UBD coefficient.

• Sales text (field WITSTEX)

This flag is used to specify that a sales text is defined for the product/customer combination. It is then used in the lines of sales documents.

• Picking text (field WITPTEX)

This flag is used to specify that a preparation text is defined for the product/customer combination. It is then used in picking tickets and delivery notes.

• Version preloading (field XLOAECCFLG)

Check this box to specify that the last active version must be preloaded by default in the Major version and Minor version fields of documents.

In creation, the setup of this checkbox is, by default, the same as the Salestab setup.

• Firm horizon (field FIMHOR)

Horizon for which the firm delivery requests must be carried out (based on a week, month or other unit).

• field FIMHORUOM

Unit of time in which the firm horizon will be expressed.

• Planning horizon (field FRTHOR)

Horizon for which the planned delivery requests must be carried out (based on a week, month or other unit).

• field FRTHORUOM

Unit of time in which the planning horizon will be expressed.

• Reorder LT (field OFS)

For purchasing
This is the number of calendar days, corresponding to:

• the reorder lead-time for a purchased product,
• the production lead-time for a finished or semi-finished product.

This information is used for the calculation of net requirements only in order to calculate the start date of sub-contract operation suggestions when the product does not have a product-site record.

For an order direct creation or a purchase request
The reorder lead-time is used to calculate the planned receipt date when no lead-time can be determined from the price lists or product-site record.
This lead-time is also used in the MRP calculation to calculate the requirement start date.

• field JOURS1

The purchasing leads are always expressed in calendar days.

• Delivery tolerance % (field MINRMNPRC)

This is the tolerance percentage used during the receipt of goods. It is used to determine if the associated order line should be closed taking into account the remaining quantity to be received.
This value is combined with the value given by the POHCLE setup.

• Matching tolerance (field MATTOL)

Use this field to specify the match code for a given product.
For any new product, this field inherits from the code defined at the level of the associated product category. This code can be modified.
This code originates from the Match tolerance function.

Reminder: The Three-way match is a reconciliation process used to validate the payment of an invoice, with a minimum and a maximum tolerance threshold. The reconciliation is carried out:

• either between the invoice and the order,
• or between the receipt and the invoice,
• or in succession (order-receipt, then receipt-invoice).

• Received product (field RCPFLG)

This information is used to specify for a purchased product that is not managed in stock, if a receipt must be carried out.

• Mandatory PO request (field PRQFLG)

This information is used to specify if a product must be the object of a purchase request before being ordered.

• Version preloading (field LOAECCFLG)

Check this box in order to specify that the last active version must, by default, be preloaded when a product has a stock receipt.
This setup can be refined by supplier.

• Purchase text (field WPURTEX)

When checked, this box specifies that a purchase text (used in the purchase order lines) has been defined from the menu bar.
 This information is not directly accessible.

• Planner (field PLANNER)

Operator in charge of performing the production planning or product ordering.

• Buyer (field BUY)

It is the operator in charge of replenishing the product from the considered site.
This information is used to define the roles of the users in charge of the product. According to the users entered here and the values of the general setups BUYFLT and GPLNFLT, restrictions can be applied when using these products in certain functions when users other than the users identified here use the products.

• Purchase unit (field ITMPUU)

This non modifiable field recalls the purchase unit specified in the "Units" tab.

• Base price (field PURBASPRI)

This is the base purchase price of the product.

This amount is expressed in the company's management currency to which the default site is associated for the Common data management. This setup is carried out at the level of the function profile assigned to the user.

 It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).

If no site is entered at the function profile level, the amount is expressed in the folder currency.

• field CUR2

• Landed cost coef. (field ITMCPRCOE)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a coefficient included in the calculation of the purchase cost and stock cost.
For any new product, this field inherits by default the landed cost coefficient recorded in the Product category. It can be modified; the value entered must be greater than 1.
When adding a new supplier, the entered value is used to load by default the landed cost coefficient of the Product - Supplier record.
If no coefficient is requested for the supplier, enter the value 1.

Only one method can be selected to calculate the landed costs: if a cost structure is entered, entering a landed cost coefficient and/or a fixed cost per unit triggers the erasing of the cost structure, after validation of a warning message.

• Fixed cost per unit (field ITMCPRAMT)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a fixed cost per unit, expressed in the same currency than the Base price that will apply to the purchase unit of the product, defined in the "Units" tab. The value entered must be a positive value.
For any new product, this field inherits by default the fixed cost per unit recorded in the Product category.
When adding a new supplier, the entered value is used to load by default the fixed cost per unit of the Product - Supplier record.

Only one method can be selected to calculate the landed costs: if a cost structure is entered, entering a landed cost coefficient and/or a fixed cost per unit triggers the erasing of the cost structure, after validation of a warning message.

• Cost structure (field ITMSTCNUM)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a cost structure included in the calculation of the purchase cost and stock cost. It can be entered manually or via the right-click options "Selection" and "Cost structure" (tunnel to the Cost structure function).
For any new supplier, this field inherits by default the cost structure recorded in the Product category. It can still be modified.
When adding a new supplier, the entered value is used to load by default the cost structure of the Product - Supplier record.

Only one method can be selected to calculate the landed costs: if a landed cost coefficient or a fixed cost per unit are entered, entering a cost structure triggers their reinitialization, after validation of a warning message.

 If a cost structure with a unit not consistent with the units of the product is entered, a blocking message listing the different inconsistencies is displayed.
The purchase unit of the cost structure must be the same as either the purchase unit, the stock unit, or the packing unit. If it is a weight or volume unit, its conversion with respect to the units of the product must be defined in the table. Unit Conversion.

• Supplier (field BPSNUM)

Enter the supplier at the origin of the receipt. The selection lists specific to the intersite and intercompany orders and deliveries available for receipt are filered to those related to the entered supplier.

From the Selection icon, you can:

• Supplier (field XBPSNUM)

The supplier code is displayed in this screen to specify the product-supplier record displayed.
This list is not exhaustive. In the case where an order is passed to a supplier not referenced for the product, the system warns the user or blocks the entry as a function of the ITMBPS setup.

• field XDESBPSNUM

This is the customer's company name.

• Supplier product (field XITMREFBPS)

This field specifies the product reference at the supplier's.
Upon order entry, it is possible to directly enter the product code of the supplier. In this case, the system is replacing automatically the product code of the supplier with the internal code.

• field XITMDESBPS

Description of the product at the supplier's.

• Supplier UPC code (field XEANCODBPS)

Barcode identifying the product on the supplier.

• Blocking (field XDOUFLG)

This flag is used to:

• block the entry of purchase requests or orders (for the displayed supplier and product)
• Display a warning message in these various functions.

• Landed cost coef. (field XCPRCOE)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a coefficient included in the calculation of the purchase cost and stock cost.
The value entered must be greater than 1.
For any new supplier, this field inherits by default the landed cost coefficient recorded in the Supply tab.
 Only one method can be selected to calculate the landed costs. If a cost structure is entered, entering a landed cost coefficient and/or a fixed cost per unit triggers the erasing of the cost structure, after validation of a warning message.
 If parameter PIHCPR –Invoice price adjustment (chapter ACH, group INV) is set to 'With landed costs' there will be no compliancy with an Anglo-Saxon accounting. The Goods Received Not Invoiced (RNI) account will never be balanced. This is a limitation of the system.

Since the various landed costs and especially the routing costs can vary according to the storage site, it is possible to enter, for each product-supplier, different landed costs for each storage site. This entry is performed in the window that can be accessed via button . This window can also be accessed via function Landed costs - Site.

• Fixed cost per unit (field XCPRAMT)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a unit fixed cost. The value must be positive.
For any new supplier, this value inherits by default the value recorded in the "Supply" tab and applies to the purchase unit of the supplier.
This amount is expressed in the company's management currency to which the specified site is associated as the default site for the Common data management. This setup is carried out at the level of the Function profile assigned to the User.
It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate).
If no site is entered at the function Profile level, the amount is expressed in the folder currency.

Only one method can be selected to calculate the landed costs: if a cost structure is entered, entering a landed cost coefficient and/or a fixed cost per unit triggers the erasing of the cost structure, after validation of a warning message.

Since the various landed costs and especially the routing costs can vary according to the storage site, it is possible to enter, for each product-supplier, different landed costs for each storage site. This entry is performed in the window that can be accessed via button This window can also be accessed via function Landed costs - Site.

• Cost structure (field XSTCNUM)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

This field makes it possible to enter a cost structure used in the calculation of the cost price. It can be entered manually or via the right-click options "Selection" and "Cost structure" (tunnel to the Cost structure function).
For any new supplier, this field inherits by default the cost structure recorded in the "Supply" tab.

Only one method can be selected to calculate the landed costs: if a landed cost coefficient or a fixed cost per unit are entered, entering a cost structure triggers their reinitialization, after validation of a warning message.
Since the various landed costs and especially the routing costs can vary according to the storage site, it is possible to enter, for each product-supplier, different landed costs for each storage site. This entry is performed in the window that can be accessed via button . This window can also be accessed via function Landed costs - Site.

If a cost structure with a unit not consistent with the units of the supplier product is entered, a blocking message listing the different inconsistencies is displayed.
Indeed, the purchase unit of the cost structure must be the same as either the purchase unit, the stock unit, or the packing unit. If it is a weight or volume unit, its conversion with respect to the units of the supplier product must be defined in the table Unit conversion.

• field STCNUMITF

This button opens a window used to enter, for each product-supplier, landed costs that are different in terms of method and/or amounts, for each storage site.
This window can also be accessed from tab "Cost" of the Product-Site record or directly from function Landed costs - Site.

• Matching tolerance (field XMATTOL)

Use this field to specify a match code for a given product/supplier.
For any new supplier/product, this field inherits from the code defined on the Repl. tab of the product.
This code is chosen from the list created in the Matching tolerance function and can be modified.

Reminder: The Three-way match is a reconciliation process used to validate the payment of an invoice, with a minimum and a maximum tolerance threshold. The reconciliation is carried out:

• either between the invoice and the order,
• or between the receipt and the invoice,
• or in succession (order-receipt, then receipt-invoice).

• Intersites (field XBETFCY)

• Purchase unit (field XPUU)

It is the specific purchase unit of a supplier for this product.

• Minimum PO qty. (field XPURMINQTY)

This is the minimum quantity, expressed in purchase unit, below which the supplier orders can be subject to a control.
The level of control (blocking, warning or no control) relating to this quantity is defined by the parameter POHMINQTY - Minimum order qty control (ACH chapter, AUZ group).

• field XPUU2

This field recalls the purchase unit for this supplier according the purchase minimum quantity.

• PUR-STK conv. (field XPUUSTUCOE)

Coefficient used to calculate the quantity in STK unit from a quantity entered in PUR: Qty in STK = Qty in PUR * coeff.
This coefficient can be accessed if a purchase 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.

• Version preloading (field XLOAECCFLG)

Check this box in order to specify that the last active version must, by default, be preloaded when a product has a stock receipt.
In creation, the setup of this checkbox is, by default, the same as the Supply tab setup.

• Packing unit (field XPCU)

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.

• PAC-PUR conv. (field XPCUPUUCOE)

PAC-PUR unit conversion coefficient
Coefficient used to calculate the quantity in PUR unit from a quantity entered in PAC unit: Qty in PUR = Qty in PAC * factor
This factor is available when a packing unit has been entered, and has a different value than the purchase unit. It can be initialized using the conversion factor table if the combination exists.

• PAC-STK conv. (field XPCUSTUCOE)

Conversion coefficient PAC/STK.
From the conversion coefficient expressed between the PAC and the PUR, the conversion coefficient is deducted between the PAC and the STK to make the reading of the stock unit easier.

• Priority (field XPIO)

Indicator used to assign a priority to the supplier. This information is useful in some functions to determine the supplier to be submitted by default or to sort the suppliers in some selection windows. The nearer to zero the value, the more the supplier should be considered in priority. The zero value represents the highest priority.

• Quality rank (field XQLYMRK)

Grade given to the supplier for quality compliance for this product.

• QC management (field XQUAFLG)

This code is used to define whether the product must be controlled on stock receipt.
The setup defined in the Product category is used to initialize the level of control of the Product-site record and Supplier-product record.The level of stock control on the Supplier-product record represents the finest level of setup and is used to initialize the level of control by purchase order. 

• No control
  The control is defined according to the management rules. It can be modified manually.
• Non modifiable control
  The quality control is mandatory in stock receipt: only a 'Q' status can be entered.
• Modifiable control
  In a miscellaneous receipt into stock, the quality status is initialized to the value 'Q', modifiable by 'A' or 'R'.
  The quality control code can also be defined at the purchase order level.
  • If in the order the quality control is set to 'Yes', the quality control is mandatory and the receipt is made with one of the sub-statuses Q* defined in the product management rule for movements of receipt type.
    If no sub-status is defined, the status cannot be entered upon receipt.
  • If in the order the quality control is set to NO, the quality control is not mandatory.
    At the time of receipt, the default value of the suggested status is 'A' and it is possible to enter or select all the statuses defined in the rule for the management of the receipt type movement for the product.
• Periodic control 
  The control is automated according to the number of receipts for this supplier and this product. In that case, the stock status can still be modified upon receipt.

• Frequency (field XQUAFRY)

If the quality control is periodic, this field is used to enter the frequency of controls for this product and this supplier.
This value has priority over the value of the product-site.

• Control number (field XQUANUM)

Number of entries carried out since the latest control.
This total is reinitialized at each control. When a periodic control is carried out for the supplier-product pair, the total of entry number carried out on the product-site record is also reinitialized.

• field XQUALIB

• Technical sheet (field XQLYCRD)

The quality control process for the product can be described via a technical record, to be chosen from the technical record table. These records contain text descriptions, but also a set of questions and answers used to carry out statistical analyses concerning the quality control results.
 It is possible to specify this record for a product and a supplier.

• Intrastat increase (field XEECINCRAT)

This field is subject to the Exchange of goods declaration (Intrastat).

This increase coefficient is used in the Intrastat declaration for the exchange of goods. It is used in supplier invoices and applied to the fiscal value of the product line to obtain the statistical value.
It is initialized by the increase coefficient entered on the Product-supplier record; otherwise, by the one of the Supplier record.

• Back-to-back order (field XCTMBPSFLG)

This flag is used to define for each supplier if they are a potential supplier for the production direct order.

• Text (field WTEXFLG)

• Subcontract BOM (field XBOMALT)

This field is used to enter the reference of a default sub-contract BOM code for this product and this supplier.
It can be entered only if the product belongs to the category: Sub-contracted

• Subcontract lead time (field XSCOLTI)

This field is used to enter the sub-contract lead-time by default for this product and supplier.
This lead-time, expressed in calendar days, can only be entered if the product is of the category: Sub-contracted.
In a sub-contract operation without WO, the lead-times used to calculate the planned receipt date of the service are used in the following priority order:

• service lead-time set up in the price lists,
• lead-time of the supplier-product record of the finished product,
• lead-time of the sub-contracting BOM of the service,
• lead-time of the site-product record of the finished product,
• lead-time of the product record of the finished product.