Products

The product categories are used to classify and filter the products according to their use.

• Product sequence number: Automatic generation or manual creation of the product code.
• Category type: Product, service, tool.
• 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 depends 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 default product status 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 in all sales documents but it will not be submitted for selection. A warning message appears.
• A Not usable product cannot be entered or submitted for selection. A blocking message appears.

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 in all purchase documents but it will not be submitted for selection. A non-blocking warning message appears.
  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 but will not be submitted for selection. A warning message appears.

  • 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 be used in purchase invoices by directly entering its code. A non-blocking warning message appears.

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: Active, On shortage
  • 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

The product reference.

It’s generated by a sequence number counter that is set up in the Sequence number counters function when the product category has a sequence number counter code.

A product line is used to:

• Define specific identifiable fields for a product group
  
  Note - informationThe 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 the 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 that you require.

Use this access code to specify a user that is responsible for the quality of the product.

This user can modify or cancel the 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 needs to be the only one in the folder. It is not mandatory.

The customs bill of material associated with the product that's used when extracting intra-community EU movements.

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.

The Federal state or region where the product was originally manufactured.

This field is subject to the DEBR–Intrastat state/region activity code. The possible values contained in the 80—State/Region miscellaneous table are filtered based on the legislation of the site.
This information, only required for specific legislations, is used when extracting the data used to draw up the Intrastat declaration.
When it is not entered, the information entered for the product-site is used, if it’s linked to the same legislation as the document being extracted.

Alphanumerical code from the statistical group table.

Statistics groups are used in the statistical processings and as selection criteria in many programs.

There are a maximum of 5 statistical groups, and their number and their title can be set up when installing the software. Assignment of a statistical group representing the commercial group for a product is mandatory. It subdivides the product catalogue in the database. The CODEFAMCIA general setup determines which of the 5 product statistical groups is dedicated to this use.

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

It’s 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.

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 needs to be displayed automatically.
• Create multiple notes for the same product, and indicate if they need to be displayed as a priority.

Defines how stock of the product is managed.

Not managed: The product is not managed in stock. It’s 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.

Indicates if stock of the product that's 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.

The management mode for the product:

• Available stock
• By order

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

Defines if movements of the product need to update a log file.

Detailed traceability: Every movement of the 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.

No traceability: Stock movements for the product are not recorded on a log file.

The average potency in percentage to be defined for the active products.

It's 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.

The product code that can be used as an alternative for the product.

The product can be displayed on the material issue slip or suggested if there’s 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 the 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 product types published by Portuguese Fiscal Authorities and regulated for the fiscal year inventory declaration.

You need to select a value for this field when the KPO—Portuguese Localization activty code is active. The values are defined in the 2051—Product type local menu. The value you select is included in the XML fiscal year inventory export declaration generated by the Inventory extraction function (GESINVEXT).

Defines if the product is managed by lot. A lot number differentiates stock lines.

The 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. They're 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 the product, as follows:

• Not managed: The 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 the product can be defined with and without lots.
• Mandatory lot: Transactions for the product need to reference a lot number.
• Lot and sublot: A lot can be subdivided into sublots.

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

Controls serial number management for the product.

Not managed: The product does not require serial number management. This rule is applied to all transactions for the product.

Issued: Serial numbers are not managed in stock, but they’re used upon issue for customer tracking purposes.

Received / issued: Management of serial numbers is per unit. A serial number differentiates 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 1 stock line. Similarly, only 1 stock movement is generated for a range of n serial numbers for products with identical stock characteristics.

The calculation mode for the expiration date.

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

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 opens automatically when recording a stock receipt. The expiration date is initialized based on the reference date and lead time.

Manual entry: With this value, an entry window for the expiration date opens automatically when recording a stock receipt. The expiration date is blank.

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

The process used to change the status of a lot in stock when it expires.

A: The status of the product does not change on expiry.

Q: The product can be controlled on expiry, for a potential date extension or rejection.

R: When the product reaches its expiration date, it’s rejected.

The expiration lead time for the 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.

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’s entered in days or months.

The process used to change the status of a lot in stock when it reaches a new control date.

A: The status of the product moves to Q or R when the new control date is reached.

Q: The product can be controlled on expiry, for a potential date extension or rejection.

R: When the product reaches its new control date, it’s rejected.

The use-by date (UBD) conversion factor.

The conversion factor can only be accessed if the following conditions are met:

• The product is expiration managed.
• Expiration management (Management field (EXYMGTCOD)) is not based on a rounded value for the 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.

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 after the expiration date.

The use-by lead time, expressed in calendar days.

The lead time is calculated based on the UBD coefficient field (DLU). It is not available for entry.

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 needs to 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 needs to also be managed by lot. The Lot management field (LOTMGTCOD) needs to be 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 the product is created, if management of versions is activated, a message is displayed to suggest automatic creation of the first major version of the product. This version is assigned a To be activated status. To use the version, its status needs to be modified.

This field is only available if versions are managed at the stock level. The product needs to be managed by lot and management of versions is activated.

Major: Major versions might be used where there have been increased or significant changes to the original or previous version. The form, fit, or function has changed. You need to 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. Both major and minor versions of the product are managed. You need to assign 2 sequence number counters, 1 counter for a major versions and 1 counter for minor versions.

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

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

The current active major version code for the product. It's 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.

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

For example, each major version of the 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.

Indicates if routings for the 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 the 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 material (BOM) for the product.

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

Cost calculations are used to break down material costs. The field (subtotal) the material cost for the product is posted to.

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

This field is subject to the FOA–Food allergens activity code. It displays the allergen associated with the 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 the 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 UML–Link quantity in unit of measure activity code. The product density.

Density is the mass of the product, as measured in g (grams) or kg (kilograms), for example, divided by its volume, as measured in ml (milliliters) or cm³ (cubic centimeters), for example.

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

The product has 2 purchase units:

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

This purchase unit cannot be modified. It’s 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.

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

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.

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.

The unit associated with the supplier.

The product can have several packing units:

• A packing unit defined on the product record in 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.
• 2 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.

Defines 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 2 stock lines: 1 line with 3 boxes containing 12 units and 1 line with 6 units.

Adjust coefficient (recalc PAC coeff): The stock line conversion factor can be adjusted as needed, 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 2 stock lines: 1 line with 3 boxes containing 12 units and 1 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 needs to 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 accounting code of the site.

The accounting code is a default value used when setting up accounting entries.

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

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.

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

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.

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 therefore an analytical payment attribute within a dimension type.

This checkbox is used when the Fixed Assets module is managed.

When selected, it identifies the product as "capitalizable" and can be referenced on an expense saved by direct entry or automatically generated when posting a miscellaneous stock issue movement.

This field is only available if the product is "capitalizable".

It’s the Fixed asset Group for the product. It’s 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 the 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 Fixed asset groups definition window 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 need to be sold together. You cannot delete products from the BOM.
  
  Note - tipA product 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 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.

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

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’s 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 in the 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 available when the Price origin field (BASPRIORI) is set to Entered.

It 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, which is defined in the user's function profile.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

This amount is expressed in the company's management currency, which is defined in the user's function profile.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

The margin percentage below which it is not possible to descend during sales document entry.

This theoretical price is for information only.

This amount is expressed in the company's management currency, which is defined in the user's function profile.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

The minimum selling price that can be entered for the product on a sales document.

This amount is expressed in the company's management currency, which is defined in the user's function profile.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

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

The number of months of warranty for the product after its shipment.

When a product is defined as being managed by back-to-back order, the option to generate a back-to-back order when an order line is created is provided automatically.

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

• A purchase back-to-back order with receipt
• A direct purchase back-to-back order where the supplier delivers the goods to the customer
  
  Note - tipThis back-to-back order type cannot be used in an intercompany context.
• A production back-to-back order

The back-to-back order type submitted by default depends on:

• The product category
• The reorder suggestion type defined on the Products-sites record
• The direct quantity specified on the Sales link of the product record

In the event of a purchase back-to-back order, it’s a direct back-to-back order with the supplier delivering the goods to the customer, when the quantity ordered is greater than the direct quantity, as expressed in the product sales units.

At Product-Site record level and for each site for which the 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 selected needs to be associated in the Planning link.

Activates the automatic generation, the installed base tracking, and the service contracts associated with the product when entering sales movements.

These 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

The warranty applied during the loan of the product.

The standard coverage of a product on loan is not carried out with a service contract template.

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 customer installed base is activated.

This field only concerns the products corresponding to the notion of a service contract.

The template will be used to support creation of a maintenance contract entered as a line in a sales order.

The point debit rule.

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 need to be entered on the points debit rule.

Blocks the tree of rules for debiting points during analysis of a service request coverage.

It's used to block any consumption of points for service requests concerning the product without cross-referencing with a particular skill.

The number of tokens that a customer can accumulate for each order for the product.

The value entered needs to be associated with a unit.

Values the number of tokens that a customer can credit to each order for the product.

It’s indispensable for carrying out any conversions needed for token credit calculations.

Associates a BOM designed with aftersales use.

For example, this BOM is used to facilitate the identification of the components forming a complete product and therefore which could potentially have defects.

Segments the product catalogue into large product categories.

This information is used when entering service request consumptions.

When creating the product record, the default product type is Other.

This is generally a physical product.

For the product type, the following features 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

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’re rarely subject to tracking via the customer base.

The following features are available:

• Definition of points deduction rules
• Definition of the token assignment rules
• Activation of stock issue by default functions
• Competitive product inquiry

The product type corresponds to the provision of a service.

For the product type, the following features 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

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.

The product type corresponds to generally to maintenance contracts that can be invoiced.

Only 1 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 opens, by default, the Stock issues entry window when the product is consumed as a service request.

All labor type items need to have a unit for each of the following:

• Day
• Hour
• Minute

These details are essential for the conversions carried out by automatic service requests time stamp records.

The customer code.

The product reference used for the customer.

It’s possible to enter a sales document directly with this reference. The system automatically replaces this reference with the internal reference of the product.

Indicates whether the customer referenced is a customer of the group or not.

The product sales unit used for the customer.

This unit can be different from the usual sales unit for the product. It’s 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.

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.

The packaging usually used to deliver the products to the customer.

The packaging code is used in the packing functions, but it can be modified in order line entry.

The use-by date (UBD) conversion factor.

The conversion factor can only be accessed if the following conditions are met:

• The product is expiration managed.
• Expiration management (Management field (EXYMGTCOD)) is not based on a rounded value for the 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.

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 after the expiration date.

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

UBD lead time = Shelf life x UBD coefficient.

For purchasing:
The number of calendar days, corresponding to the following:

• The order 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 subcontract operation suggestions when the product does not have a product-site record.

For a direct order or a purchase request:
The reorder lead time is used to calculate the planned receipt date when a lead time cannot be determined from the price lists or product-site record.

This lead time is also used in the MRP calculations to calculate the requirement start date.

The tolerance percentage used during the receipt of goods. It’s 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.

The match code for a given product.

For any new product, this field inherits from the code defined for the product category. This code can be edited.

This code originates from the Match tolerance function.

The operator responsible for replenishing the product.

This information is used to define the roles of the users that manage the product. According to the users entered here and the values of the BUYFLT and GPLNFLT parameters, restrictions can be applied when using these products in certain functions when users other than the users identified here use the products.

The base purchase price of the product.

This amount is expressed in the company's management currency, which is defined in the user's function profile.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

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 1 of the 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 1 method can be used, the choice of this method is performed at the level of the product management.

Use this field to enter the conversion factor to be included in the calculation of the purchase cost and stock cost.

For any new product, this field defaults to the landed cost conversion factor recorded for the assigned product Category. It can be modified. The value entered needs to be greater than 1.

When adding a new supplier, the entered value is used to load, by default, the landed cost conversion factor for the product-supplier record.

If no conversion factor is defined for the supplier, enter the value 1.

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 1 of the 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 1 method can be used, the choice of this method is performed at the level of the product management.

Use this field to enter a fixed cost per unit, expressed in the same currency as the Base price, that will apply to the purchase unit of the product, defined in the Units of measure section. The value entered needs to be a positive value.

When adding a new product, the default value is the fixed cost per unit defined for the assigned product Category.

When adding a new supplier, the entered value is used to load, by default, the fixed cost per unit for the product-supplier record.

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 1 of the 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 1 method can be used, the choice of this method is performed at the level of the product management.

Use this field to enter or select a Cost structure to be included in the calculation of the purchase cost and stock cost.

For new suppliers, this field inherits, by default, the cost structure recorded for the assigned product Category. It can be modified.

When adding a new supplier, the entered value is used to load by default the cost structure from the product-supplier record.

The table that declares each supplier for the product.

Add the associated code. You can also create a new supplier. Select the Actions icon to access the supplier record, according to your authorizations.

In the supply plans and in purchase entry documents, the ITMBPSFCY—Supplier-site referencing parameter (ACH chapter, REF group) controls references to the product for the supplier.

For the supply plans and purchase document entry, defines if the supplier:

• Is subject to any control actions
• Is subject to any blocking actions
• Has been issued a warning

Indicates if this supplier is a default supplier for the product.

When entering the supply plans and purchase entry transactions, the supplier priority level is cross-referenced with the blocking level to determine the default supplier for the product.

• The default supplier is defined as the supplier that's not "blocked" and that has the highest priority level (zero level).
• If 2 suppliers that are not blocked have the same priority level, the default supplier is determined alphabetically by supplier code.
• If only 1 supplier has the highest priority level but is blocked, the default supplier is a supplier with a lower priority level that's not blocked.

Indicates if this supplier is a default back-to-back order supplier for the product.

When generating a back-to-back purchase order and during bulk generation of back-to-back orders, the supplier priority level is cross-referenced with the blocking level to determine the default back-to-back order supplier for the product.

• The default supplier is defined as the back-to-back order supplier hat is not "blocked" and that has the highest priority level (zero level).
• If 2 back-to-back order suppliers that are not blocked have the same priority level, the default supplier is determined alphabetically by supplier code.
• If only 1 back-to-back order supplier has the highest priority level but is blocked, the default supplier is a supplier with a lower priority level that's not blocked.

The code the supplier uses for the product.

The supplier product code can be used when creating a purchase order for the product. The supplier product code replaces the product code.

Specifies the rule for the supply plans and purchase transactions.

No: The supplier is not subject to any controls.

Warning: The supplier is blocked. It will not be submitted as the default supplier and cannot be manually selected.

Hold: The supplier is suspended. It can still be submitted as the default supplier. Manually selecting this supplier will display a warning message.

The priority level assigned to the supplier. The closer to zero the value, the greater the priority that's given to the supplier. A zero value represents the maximum priority.

This information is used to sort suppliers in some selection windows. Cross-referencing the priority level with the blocking level used for the product-site-supplier combination also helps identify the default supplier to be suggested in some functions.

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

This conversion factor is used in the Intrastat declaration for the exchange of goods. It’s used in supplier invoices and applied to the fiscal value of the product line to obtain the statistical value.

It’s initialized by either the increase conversion factor entered on the product-supplier record or the supplier record.

Defines a match code for a given product and supplier.

For any new product-supplier, this field inherits from the code defined on the product Repl. tab.

This code is applied from the list created in the Matching tolerance function and can be modified.

The minimum quantity, expressed in purchase unit, below which the supplier orders can be subject to a control.

The level of control, which can be blocking, warning, or no control relating to this quantity is defined by the POHMINQTY–Minimum order qty control parameter (ACH chapter, AUZ group).

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.

Indicates that the last active version needs to, by default, be preloaded when a receipt is entered for the product.

When creating the product record this checkbox defaults to the same value as the Version preloading checkbox in the Purchasing section.

It’s possible to specify a packing unit by supplier.

The product can have several packing units:

• A packing unit defined on the product record in 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 that's defined on the product-supplier record.
• 2 customer packing units, from the product-customer record. These can be used as sales units in order entry.

You can only apply packing type units from the Units of measure table.

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

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.

Defines whether the product needs to be controlled on receipt into stock.

The assigned product Category determines the initial control value for the product-site record and the supplier-stock record. The supplier-stock record value provides the default value for purchase orders.

No control: The control is based on the management rules. It can be edited.

Non-changeable control: Quality control is mandatory for stock receipts. Q is the only valid status.

Changeable control: For a miscellaneous receipt into stock, the quality status is initialized to the value Q. This status can be changed to A or R.
The quality control code can also be defined at the purchase order level.

• If the order quality control is set to Yes, quality control is mandatory and the receipt has 1 of the sub-statuses Q* defined in the product management rule for receipt movements.
  If no sub-status is defined, the status cannot be entered at the time of receipt.
• If the order quality control is set to No, quality control is not mandatory.
  At the time of receipt, A is suggested as the default status. This can be changed to 1 of the statuses defined in the receipt movement rule for the product.

Periodic control: This control is automated according to the number of receipts for this supplier and the product. The stock status can still be modified during entry.

If the quality control is periodic, this field is the frequency of controls for the product and this supplier.

This value has priority over the value of the product-site.

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 entry number total for the product-site record is also reinitialized.

The quality control process for the product can be described using a technical record. These records contain text descriptions, but also a set of questions and answers used to carry out statistical analyses concerning the quality control results.

Landed costs management enables the routing costs of the goods ordered from a supplier to be quantified and allocated 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 1 of the following methods:

• Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is considered
• A method in which a set of costs detailed in a cost structure is considered

Only 1 method can be used. The choice of method is performed at the product management level.

Use this field to enter a conversion factor to be included in the calculation of the purchase cost and stock cost. This value needs to be greater than 1.

Since the different landed costs and especially the routing costs can vary according to the storage site, it’s possible to enter, for each product-supplier, different landed costs for each storage site. You can add these values directly in the Suppliers section in the Products-sites function (GESITF). You can also add these values via the Landed costs-supplier-site icon or using the Landed costs-site function (GESSTCITF).

Landed costs management enables the routing costs of the goods ordered from a supplier to be quantified and allocated 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 1 of the following methods:

• Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is considered
• A method in which a set of costs detailed in a cost structure is considered

Only 1 method can be used. The choice of method is performed at the product management level.

Use this field to add a fixed cost for each unit.

For any new supplier, the default value for this field is the supplier purchasing unit from the Purchasing section. This amount is expressed in the company's management currency for the default site, which is defined in the user's function profile. It refers to the display currency. The amount is stored in the folder currency, with the conversion from the average monthly exchange rate.

If a site is not entered on the function profile, the amount is expressed in the folder currency.

Since the different landed costs and especially the routing costs can vary according to the storage site, it’s possible to enter, for each product-supplier, different landed costs for each storage site. You can enter these values directly in the Suppliers section in the Products-sites function (GESITF). You can also enter these values via the Landed costs-supplier-site icon or using the Landed costs-site function (GESSTCITF).

Landed costs management enables the routing costs of the goods ordered from a supplier to be quantified and allocated 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 1 of the following methods:

• Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is considered
• A method in which a set of costs detailed in a cost structure is considered

Only 1 method can be used. The choice of method is performed at the product management level.

Use this field to add a cost structure used in the calculation of the cost price. You can manually enter this value or select Selection or Cost structure (access to the Cost structure function) from the Actions icon.

For any new supplier, the default value for this field is the cost structure from the Purchasing section.

Since the different landed costs and especially the routing costs can vary according to the storage site, it’s possible to enter, for each product-supplier, different landed costs for each storage site. You can enter these values directly in the Suppliers section in the Products-sites function (GESITF). You can also enter these values via the Landed costs-supplier-site icon or using the Landed costs-site function (GESSTCITF).

Select to enter the landed costs for each storage site.

You can also enter these values directly in the Cost section in the Products-sites function (GESITF) or using the Landed costs-site function (GESSTCITF).

The default subcontract BOM code for the product and this supplier.

The default subcontract lead time for the product and supplier, in calendar days.

For a subcontract operation without a work order, the lead times used to calculate the planned receipt date of the service are applied in the following priority order:

• The lead time on the subcontract fee for the service associated to the supplier
• The service subcontract lead time for the subcontract BOM
• The subcontract lead time specified for the product-supplier for the service
• The purchase lead time specified on the product-site record for the service
• The reorder lead time specified on the product record for the service

If no lead time is associated to the service, the lead time for the subcontracted product is used, in the following priority order:

• The subcontract lead time specified for the product-supplier
• The purchase lead time specified for the product-site
• The reorder lead time specified for the product

Select the Purchasing action in the Text menu to view, enter, or edit the text associated with the supplier / product combination. This text is added to purchasing transactions and supplier reports.

A standard classification, or characteristic of the product that can be referenced by your web scheduling processes.

For example, if the product is painted during your manufacturing process, an attribute classification might be PAINT or COLOR.

An individual characteristic of the attribute classification that applies to the product.

For example, if your company manufactures bicycles and the attribute classification is COLOR, this attribute value is the color used in the manufacturing process with the product, such as BLACK or RED.

Select this action to enter or edit purchasing text associated with the product. This text can then be added to purchase documents for the product.

Select this action to enter or edit production text associated with the product. This text can then be added to manufacturing transactions for the product.

Select this action to enter or edit sales text associated with the product. This text can then be added to sales transactions for the product.

Select this action to enter or edit preparation text associated with the product. This text can then be added to pick tickets for the product.

Select this action to access the Quote line inquiry for the selected product.

To display lines, you need to add filters for customers and customer groups.

Select this action to access the Order line inquiry for the selected product.

To display lines, you need to add filters for customers and customer groups.

Select this action to access the Delivery line inquiry for the selected product.

To display lines, you need to add filters for customers and customer groups.

Select this action to access the Invoice line inquiry for the selected product.

To display lines, you need to add filters for customers and customer groups.

Select this action to access the Return line inquiry for the selected product.

To display lines, you need to add filters for customers and customer groups.

Select this action to access the Purchase requests inquiry for the selected product.

To display lines, you need to add filters for suppliers and supplier groups.

Select this action to access the Order lines inquiry for the selected product.

To display lines, you need to add filters for suppliers and supplier groups.

Select this action to access the Receipt lines inquiry for the selected product.

To display lines, you need to add filters for suppliers and supplier groups.

Select this action to access the Invoice lines inquiry for the selected product.

To display lines, you need to add filters for suppliers and supplier groups.

Select this action to access the Return lines inquiry for the selected product.

To display lines, you need to add filters for suppliers and supplier groups.

Select this action to access the Subcon. consumption inquiry for the product.

To display lines, you need to add filters for suppliers and supplier groups.

Use this action to automatically create product-site records using the default values of the product category or categories / sites if any.

Use the table to select the sites for which the product-site records need to be created. Only those sites that do not have any associated records are listed. It’s possible to exclude or include all the sites.

If your folder contains a single site, the product-site record is generated automatically. This action is optional.

Select this action to identify the products available on the market that share enough characteristics with the current product to be considered as competitor products.

The associated products are chosen from a list of competitor products defined in the corresponding function, where it’s also possible to create new competitor products.