Products

Use this field to identify the category of product to which this product is assigned.

 Some fields are associated with this code in the Product category table (ITMCATEG) and will influence fields in this function as you create the product details:

• Product sequence number - automatic generation or manual creation of the product code.
• Category type - product, service, tool, etc.
• Creation method - controls the initial status of the product.

The product status determines the availability of the product. The statuses are: Active, In development, On shortage, Not renewed, Obsolete and Not usable.

The default status when creating a new product is dependent on the creation method defined for the assigned product category:

• If the product category Creation method is set to Direct, the product status will be Active.
• If the product category Creation method is set to With validation, the product status submitted by default will be In development.

Impact of the product status in the sales and purchase modules

Sales

• An Active product can be entered and selected in all sales documents.
• An In development, On shortage, Not renewed or Obsolete product can be entered (a warning message is displayed) in all sales documents but it will not be submitted for selection.
• A Not usable product cannot be entered (blocking message) or submitted for selection.

Purchases

• An Active product can be entered and selected in all purchase documents.
• An In development, On shortage, Not renewed or Obsolete product can be entered (a non-blocking warning message is displayed) in all purchase documents but it will not be submitted for selection.
  Upon receipt of the product, an order or a delivery can be selected.
  A product with an In development status can be entered on a request for quote.
• A Not usable product can be entered in the following documents (a warning message is displayed) but will not be submitted for selection:
• Purchase orders
• Contracts
• Buyer plan
• Planning workbench - generation of orders or delivery requests only.
• Enterprise planning - generation of orders or delivery requests only.
• Grouping workbench - the orders for products with this status have the suffix "-".
• Purchase invoices.

Upon receipt of the product, an order or a delivery can be selected.

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

• Active. The product is available in all the processes.
• In development
• 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 creation method is With validation, the status cannot be accessed and its value is forced to the In development value.
• Not renewed
• Obsolete
• Not usable. The product does not appear in search results and cannot be used in scripts. It can however be used in purchase invoices, by directly entering its code. In that case, a non-blocking warning message is displayed.

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

• Context - Input
• Non-blocking message: In development, On shortage, Not renewed, Obsolete.
• Blocking message: Not usable.
• Issues - BOMs
• Non-blocking message: Not renewed, Obsolete, Not usable.
• Work order (component)
• Non-blocking message: In development, On shortage.
• Blocking message: Not renewed, Obsolete, Not usable (product not returned).
• Work order (parent product)
• Non-blocking message: In development, On shortage.
• Blocking message: Not renewed, Obsolete, Not usable.
• Sales order
• Non-blocking message: In development, On shortage, Not renewed, Obsolete.
• Blocking message: Not usable.
• Purchase order
• Non-blocking message: On hold.
• Blocking message: In development, Not renewed, Obsolete, Not usable.
• Assembly - On shortage
• Compound assembled:
• Non-blocking: In development, Not renewed, Obsolete.
• Component:
• Non-blocking: In development, Not renewed, Obsolete.
• Disassembly - On shortage
• Compound assembled:
• No message: In development, Not renewed, Obsolete.

This warning is displayed if this product is still in design mode, that is this product has been created from a product design BOM revision that has only been released as a prototype product. It is not yet released as a full production BOM.

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 automaticaly assigned and displayed at product creation end.

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

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.

Use this field to define the start-of-life date for this product. Sales orders cannot be raised for this product before its start-of-life date.

Use this field to define the end-of-life date for this product. Orders cannot be raised for this product after its end-of-life date.

This checkbox indicates that a manufacturing text exists for this product (via the Text / Manufacturing action). This text will be used with production transaction lines.

This checkbox indicates that a preparation text exists for the product/customer combination (via the Text / Pick ticket action). The text will be used on picking tickets and delivery notes.

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.

A product line is used to:

• Define specific identifiable 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.

Barcode identifying this product.

Enable the predictive or automatic entry by setting the AUTOSEL – Automatic selection parameter (SUP chapter, INT group) to Yes.

Start by entering a few characters contained in the reference or description (or other), and press Tab.

A window displays a list of results. Select the value you require.

  AUTOSEL – Automatic selection parameter (SUP chapter, INT group) for the conditions for implementing the automatic search.

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

Use this access code to specify a user that is in charge of the product quality for this product category (for correcting the product details).

This user can modify or cancel this product if this access code is associated with their profile and their modification indicator is set to Yes.

This field is displayed only 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).

Global Trade Item Number (GTIN) of the product This code contains 14 numerical characters. It must be the only one in the folder. It is not mandatory.

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.

Use this field to indicate if the product is subject to Intrastat.

This field is subject to the DEB - EU exchange declaration (Intrastat) activity code. It can only be accessed if the product is subject to Intrastat.

Enter the Customs BOM associated with the product, used when extracting intra-community EU movements.

This field is subject to the DEBR - Intrastat state/region activity code. Use it to enter the Federal state or region where the product was originally manufactured. This information is only required for specific legislations.

When extracting the data used to draw up the declaration, the information in this field is used as the default value, if not entered at the Product-site level.

To be considered, its legislation must be identical to the legislation of the country specified on the document being extracted.

This field is subject to the PLM - PLM - X3 interface activity code.

It is only populated if the product has been created by import from the PLM @UDROS product when it will contain the original reference of the product from PLM.

This icon is subject to the PLM - PLM - X3 interface activity code. It opens the URL that gives access to a web page containing the PLM documents linked with the product.

This icon is subject to the PLM - PLM - X3 interface activity code. It opens the URL that gives access to a web page displaying the product history.

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

Use this field to select an image to display on this record.

Use this field to define how stock of this product is managed:

• Not managed. This product is not managed in stock. It is a service or a general purchase, for example.
• Managed
• Potency managed. A management rule is applied. Management of quantities in stock requires an active quantity and a physical quantity.

Use this field to specify if this product is managed by lot. A lot number will differentiate stock lines.

 Stock lines

This product can also be managed with sublots, which are subdivisions of a lot. A sublot number will also differentiate stock lines. Sublot numbers are free-format (a number or group of 5-characters, by default, with the first sublot upon receipt of stock receipt suggested as 00001).

Define the lot management method for this product, as follows:

• Not managed. This product is not managed by lot. This rule is applied to stock issues and receipts.
• Optional lot. A lot number is accepted. It is not mandatory. With this value, stock lines for this product can be defined with and without lots.
• Mandatory lot. Transactions for this product must reference a lot number.
• Lot and sublot. A lot can be subdivided into sublots.

This value can only be changed if this product has no stock.

Lot sequence number counter that defines the format of lot numbers for this product. The lot number can be a maximum of 15 characters.

 Management of lots and sublots is subject to the LOT - Lot management and SLO - Management by sub-lots activity codes.

Select this checkbox if stock of this product that is not yet present in the system can be issued.

Example:
Stock has physically been delivered or manufactured and needs to be issued to a customer, but the receipt details have not yet been input into the system. With this checkbox selected the system can generate a "pending" issue. This issue is adjusted upon input of the stock into the system.

Use this field to define the management mode for this product:

• Available stock
• By order

This value is used in the MRP and MPS reorder calculations.

Use this field to define if movements of this product must update a log file.

• Detailed traceability. Every movement of this product is recorded on a log file.
• Summary traceability. Movements that relate to a single product, lot, status, document and transaction are totaled and recorded on a log file.
  This value is recommended for work order receipts and issues so the returned log is only split once.
• No traceability. Stock movements for this product are not recorded on a log file.

This field indicates the 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 field (STOMGTCOD) is set to Potency managed.

Use this field to define a product code that can be used as an alternative for this product. This product can be displayed on the material issue slip or suggested if there is a shortage during manufacture (work order).

Defining an alternate product results in the following checks:

• Existence check - the product is available for selection.
• Loop check - to avoid using the same product during cascading replacements.

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

The Alternate product option is available from the action icon in the Ordered qty. field on sales order lines (Sales order function (GESSOH)). It is not available, however, if the order line has been allocated or partially delivered, billed, or prepared.

The description of the alternative product.

Use this field to control serial number management for this product. Select from the following serial number management methods:

• Not managed. This product does not require serial number management. This rule is applied to all transactions for this product.
• Issued. Serial numbers are not managed in stock, but they are used upon issue for customer tracking purposes.
• Received / issued. Management of serial numbers is per unit. A serial number will differentiate stock lines: n serial numbers of the same lot / sublot / status / location are present on n different stock lines. Similarly, a stock movement is generated for each serial number.
• Global received / issued. Management of serial numbers is global. The serial number will not differentiate stock lines: a range of n serial numbers of the same lot / sublot / status / location is present on one stock line. Similarly, only one stock movement is generated for a range of n serial numbers for products with identical stock characteristics.

• Negative stock is not authorized.
• The stock must be managed with stock units.
• You cannot enter the serial number of products which are on an Awaiting put-away location. You must enter them when storing them in stock.
• A product with serial numbers managed by Global received / issued cannot be used as a component in a subcontract BOM.
• Serial numbers are not automatically determined during the allocation automatic determination (GENSTOALL component), but they are during the automatic determination of the stock to be issued (GENSTOSORW component).
• The serial numbers can be identified on the detailed allocations of pick lists, deliveries and supplier returns. They cannot be identified on sales orders, work orders, subcontract orders and project tasks.

• You cannot change this value from Not managed or Issued to Global received / issued once stock transactions for this product have been recorded.
• You cannot change this value from Received / issued to Global received / issued. Use the Serial management modification function (FUNSERMGT) to do this instead.

Sequence number code which is used to automatically assign the serial numbers.

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

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

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

 Expiration date management is only possible if the product is managed by lot. In this case, the status of expired lots can be planned.

This information, if defined at the category level, is used at the product level where the shelf life can also be specified.

 This field is not available if the expiration Management field (EXYMGTCOD) is set to No management.

When a lot in stock is to expire, a process is used to automatically change its status:

• A. The status of this product does not change on expiry.
• Q. This product can be controlled on expiry, for a potential date extension or rejection.
• R. When this product reaches its expiration date it is rejected.

 This field is not available if the expiration Management field (EXYMGTCOD) is set to No management.

Enter the expiration lead time for this product in days or months. This value is used in the calculation of the expiration date and use-by date (UBD) of a lot upon stock receipt.

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

Type in the lead time of the new control to be used upon stock receipt. This value will be used to calculate the new control date based on the reference date. It is entered in days or months.

 The new control date cannot extended beyond the limit date of lot use.

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

When a lot in stock reaches a new control date, a process is used to automatically change its status:

• A. The status of this product moves to Q or R when the new control date is reached.
• Q. This product can be controlled on expiry, for a potential date extension or rejection.
• R. When this product reaches its new control date it is rejected.

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

• Expiration is managed for the product.
• Expiration management (Management field (EXYMGTCOD)) is not based on a rounded value (start or end of the month).

This conversion factor 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 conversion factor must be between 0.1 and 1. The UBD needs to be before the expiration 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 UBD provides the customer receiving the lot with the guarantee that the use-by date of their goods is more or less distant from the expiration date.

Example:

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

 A UBD conversion factor can be entered in the product record, in the product-site record and in the customer-product record. The UBD conversion factor entered in 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.

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.

This field cannot be entered. The UBD lead time is always expressed in calendar days.

UBD lead time = Shelf life x UBD coefficient

Management of versions is subject to the ECC - Product version management activity code.

During the lifetime of a product, some of its characteristics can be modified. These modifications can be tracked back by activating version management.

To use version management, the product must be managed in stock. Versions will then be active in Manufacturing functions. For the tracking of versions to be effectively managed at the stock level, the product must also be managed by lot (Lot management field (LOTMGTCOD) is set to Mandatory lot).

Version management can be initialized for the assigned product category then, provided the product has no stock, modified for individual products.

When this product is created, if management of versions is activated, a message is displayed to suggest automatic creation of the first major version of this product. This version is assigned a To be activated status. In order to use the version, its status must be modified.

This field can only be accessed if versions are managed at the stock level. That is, the product is managed by lot and management of versions is activated. Select from the following:

• Major. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the form, fit or function has changed. If you select this value you must assign a sequence number counter for major versions.
• Major and minor. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version. If you select this value, both major and minor versions of this product are managed. You must assign two sequence number counters, one counter for a major versions and one counter for minor versions.

 You can click the link icon to access the Versions management screen.

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

If major versions are managed for this product, use this field to assign the major version sequence counter to be used to automatically assign a code to each major version of this product.

For example, each major version of this product can be identified by an alphanumeric code, A then B, then C, etc.

This field displays the current active major version code for this product (the major version code with an Active status). If no major versions are currently active, this field displays the code of the last major version with a Stopped status.

If only versions with a Prototype status exist, the version number is not displayed.

This field contains the status of the major version displayed.

If major and minor versions are managed for this product, use this field to assign the minor version sequence counter to be used to automatically assign a code to each minor version of this product.

For example, each major version of this product can be identified by an alphanumeric code, A then B, then C, etc. with minor versions identified by a numeric code, 01, 02, 03, etc.

This field displays the current minor version code for this product.

Select this checkbox if routings for this product can be version-managed. This checkbox is only available when a sequence number of a major version (Major sequence field) has been defined for this product and if a major version is displayed.

Select this checkbox to manage (major and minor) routing versions independently of any stock version or bills of materials (BOM) for this product.

Leave this checkbox clear if you do not require routing versions for this product.

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

You cannot change this check box once the first major routing version has been assigned to this product.

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.

Use this field to assign this product code to a specific cost type. Cost types are used in 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 as Available 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 as Available stock or purchased By order

This field is subject to the FOA - Food allergens activity code. It displays the allergen associated with this product. The product category determines the options available.

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

This field is subject to the FOA - Food allergens activity code. It 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 subject to the FOA - Food allergens activity code. It is used to display the allergen total BOM. It is updated when modifications are applied to the allergens linked to the product.

If necessary, enter or select the UN number of the product. This number always contains four characters. It identifies a type of dangerous goods which transportation is subject to regulations. This number is used in the electronic invoicing system SAFT-PT.

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.

This field is subject to the UML - Link quantity in unit of measure activity code. Use this field to define the product density. Density is the mass of the product (measured in g (grams) or Kg (kilograms), for example) divided by its volume (measured in ml (milliliters) or cm³ (cubic centimeters), for example).

This fields corresponds to the format of the stock labels.

The weight unit.

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

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.

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

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.

This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

Conversion factor used to calculate the quantity in stock units from a quantity entered in purchase units: Quantity in STK = Qty in PUR * conversion factor.

This conversion factor can be accessed if the Purchase unit field (PUU) 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.

The unit in which this product is sold. The sales price is attributed to this unit.

This sales unit is also displayed by default in the Sales and Customer sections.

The sales units are accessible depending on the type of category assigned.

Conversion factor used to calculate the quantity in stock units from a quantity entered in sales units: Quantity in STK = Qty in SAL * conversion factor.

This conversion factor can be accessed if the Sales unit field (SAU) 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.

Select this checkbox if modification of the conversion factor between the sales unit and the stock unit on sales transactions is authorized.

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.

Conversion factor used to calculate the quantity in stock units from a quantity entered in statistical units: Quantity in STK = Qty in statU * conversion factor.

This conversion factor can be accessed if the Statistical unit field (SSU) 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.

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

Conversion factor used to calculate the quantity in stock units from a quantity entered in additional EU units: Quantity in STK = Qty in EEU * conversion factor.

This conversion factor can be accessed if the EU unit field (EEU) 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.

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.

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.

Select this checkbox if modification of the conversion factor between the packing unit and the stock unit on purchase orders or receipts is authorized.

This filed indicates the label format.

Use this field to define how to split stock lines during the unpacking process.

• Unpack. The fractional part of the stock line is set back to stock units, and the line is split if necessary. This option is only available when conversion factor entry is authorized.
  Example:
  A stock line contains 5 boxes each containing 12 units. 18 units are taken from the stock line.
  This results in two stock lines: one line with 3 boxes containing 12 units and one line with 6 units.
• Adjust coefficient (recalc PAC coeff). The stock line conversion factor can be adjusted as required, and the line is split if necessary. This option is only available when conversion factor entry is authorized.
  Example:
  A stock line contains 5 boxes each containing 12 units. 18 units are taken from the stock line.
  This results in two stock lines: one line with 3 boxes containing 12 units and one line with 1 box containing 6 units.
• Fraction (calculate decimal PAC). The stock line quantities can be adjusted by division (split).
  As a consequence, the packing unit must be decimalized.
  Example:
  A stock line contains 5 boxes each containing 12 units. 18 units are taken from the stock line.
  This results in a stock line of 3.5 boxes containing 12 units.

The sales and purchasing units must exist in the packing units table if the transaction unit entered in the resulting stock line must be retained. Otherwise, the resulting stock line is managed in stock units.

Use this field to specify the accounting code of the site.

The accounting code is a default value used in the setting up of accounting entries.

It refers to a table that lists a certain amount of elements (collective accounts, accounts or parts of accounts) that can be used for the determination of the documents that will be posted.

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 Tax determination documentation for further information.

The tax level only displays the list of the different rates applied within a same rule.

Define the default value of the Sage Sales Tax (SST) tax code. 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. It can include for example transport costs, handling costs and on-line product costs. This field is only available when the LTA activity code is activated.

This checkbox 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 (checkboxes Fixed asset tracking and Expense creation activated).

This table is populated automatically with the default dimension types associated with this product.

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.

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.

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.

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 falling in the Service and Non-deliverable category cannot be defined as having the Fixed kit type.

A flexible kit or a fixed kit 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.

This is the sales unit defined for this product (in the Units of measure section).

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.

This field indicates the substitution product.

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

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

This is the minimum quantity expressed in the sales unit that can be entered on a sales order.

 This control can be blocked by the SDACLOK - Non block control price, profit, quantity parameter (VEN chapter, AUZ group).

Maximum quantity of order, in sales units.

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

• The category type is Service or Generic,
• The flow type is Sold and not Deliverable.

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.

This field is used when entering a sales transaction 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 (Purchasing section) and to the percentage entered in the purchase % applied field (PURPRIPRC), as follows: Base purchase price + (Base purchase price * % applied).

This field is only accessible if the Price origin field (BASPRIORI) is set to Purchase price %. It is used to specify what percentage is to be applied to the base purchase price specified in the Purchasing section in order to obtain the base sales price.

This field can only be accessed when the Price origin field (BASPRIORI) is set to Entered.

Indicates the tax-exclusive 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.

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.

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

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.

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.

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.

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

When a product is defined as being managed by back-to-back order, the system will automatically provide the option to generate a back-to-back order during the creation of an order line.

There are three types of back-to-back orders:

• The purchase back-to-back order with receipt
• The direct purchase back-to-back order (the supplier delivers the goods to the customer)
  This back-to-back order type cannot be used in an intercompany context.
• The production back-to-back order

The back-to-back order type submitted by default is dependent on:

• The product category
• The reorder suggestion type defined on the Product/Site record
• The direct quantity specified on the Sales link of the product record.

In the event of a purchase back-to-back order, the system will determine that it is a direct back-to-back order (the supplier delivers the goods to the customer) when the quantity ordered is greater than the direct quantity (expressed in the product sales units).

At Product-Site record level and for each site for which this product should be managed with back-to-back orders, an allocation rule with the back-to-back order type (and the Back to back method (1 to 1) checkbox activated) must be associated in the Planning link.

Select this checkbox to specify that the last active version of this product must be preloaded by default in transactions referencing the Major version and Minor version. This setup can be individualized by customer.

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

This checkbox indicates that a sales text exists for this product (via the Text / Sales action). The text will be used with sales transaction lines.

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

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.

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.

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.

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.

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.

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.

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.

This unit is used to value the number of tokens that a customer can credit to each order for this product.

It is indispensable for carrying out any conversions necessary for the token credit calculations.

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.

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 default product type 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.

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.

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.

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.

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.

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

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.

Description of this product for the customer.

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 checkbox is automatically selected.

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.

Conversion factor used to calculate the quantity in stock units from a quantity entered in sales units: Quantity in STK = Qty in SAL * conversion factor.

This conversion factor can be accessed if the Sales unit field (SAU) 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.

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

Conversion factor used to calculate the quantity in sales units from a quantity entered in packing units: Quantity in SAL = 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 Sales unit field (SAU). It can be initialized using the conversion factor table if the combination exists.

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

Conversion factor used to calculate the quantity in sales units from a quantity entered in packing units: Quantity in SAL = 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 Sales unit field (SAU). It can be initialized using the conversion factor table if the combination exists.

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.

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

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

• Expiration is managed for the product.
• Expiration management (Management field (EXYMGTCOD)) is not based on a rounded value (start or end of the month).

This conversion factor 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 conversion factor must be between 0.1 and 1. The UBD cannot exceed the expiration 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 UBD provides the customer receiving the lot with the guarantee that the use-by date of their goods is more or less distant from the expiration date.

Example:

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

 A UBD conversion factor can be entered in the product record, in the product-site record and in the customer-product record. The UBD conversion factor entered in 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 blank.

Example 2 with UBD defined for the client:
Sales order with requested delivery date (determined from the shipment date + lead time): November 1.
Lot A

• Stock receipt date: January 1
• Shelf life: 20 days - Expiry date: January 20
• UBD coefficient for product-site: 0.6 - UBD lead time for product-site: 12 days - Product-site UBD date: December 1
• UBD coefficient for customer-product: 0.4 - UBD lead time for customer-product: 8 days - Customer-product UBD date: August 1

Lot B

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

During the allocation:

• Lot A was not selected because the customer-product UBD was dated August 1, which is prior to the delivery date November 1.
• Lot B was selected because the product-site UBD was dated December 1, which is later than the delivery date November 1.

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.

This field cannot be entered. The UBD lead time is always expressed in calendar days.

UBD lead time = Shelf life x UBD coefficient.

This checkbox indicates that a sales text exists for the product/customer combination. The text will be used with sales transaction lines.

This checkbox indicates that a preparation text exists for the product/customer combination (via the Text / Pick ticket action). The text will be used on picking tickets and delivery notes.

Select this checkbox to specify that the last active version of this product must be preloaded by default in transactions referencing the Major version and Minor version. The default value for this checkbox is the same as the checkbox in the Sales section.