Product Categories

• Category (field TCLCOD)

The product categories are used to classify and filter the products according to their use. This step makes it possible to refine the selection prior to carrying out the adjustment process. This code is used in the Product record to enable selections.

• Description (field TCLAXX)

• Storage site (field STOFCY)

Enter or select the storage site where the selected product is active.

The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table.

• Short description (field TCLSHOAXX)

Enter the short description.

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.

• Product sequence (field ITMREFCOU)

The Product reference counter is a code of three alphanumerical characters selected in the ACODNUM counter table.
When a counter has been specified, the product reference cannot be entered in product creation: it is automatically generated based on the counter format.

• Creation method (field ITMCREMOD)

The product creation method is used to introduce a validation phase before making it available:

• Direct: the product is immediately available for all processes with status "Active",
  
• With validation: the product is created with status "In process". It will be necessary to validate the product in product management and to modify its status so as to make it available.
  

• Access code (field PLAACS)

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.

• Buyer (field BUY)

• Planner (field PLANNER)

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

• Service (field SCSFLG)

A Service type category with a Sold flow is a category relating to subcontract products.
A product of this category can be used in:

• a sucontract BOM,
• a subcontract routing operation.

If this particular flow type is Sold, then the product is always Deliverable (so it can be received).

However, with a Sold flow type only, the product does not always have to be Deliverable. In this case, the product is a sheer service product, which is not included in deliveries.
This product will be invoiced through invoicing open items.

• Phantom (field PHAFLG)

When ticked, this box indicates that the product can be called in BOMS in two cases:

• to manage the grouping of components used in various manufactured products.
  Only calling the phantom product in a BOM of a same type prevents the copy of all components in this BOM.
• to manage how the stock wears out
  When the product is managed in stock, the MRP calculation will consume the available stock on this product. The system then proposes suggestions on product of inferior levels once the stock wears out.

• Tools (field TOOFLG)

When ticked, this box is used to indicate that the product is used in routing operations to represent the tools.

• Generic (field GENFLG)

When ticked, this box is used to indicate that the product is of type 'Generic'.
 Generic products are not managed in stock (example: services, etc.).

• Maintenance (field MCEFLG)

Access to this box is submitted to the MMS - MMS - X3 Interface activity code.
When checked, this box specifies that the product belongs to the 'Maintenance' category.
During the interface processing with the AXEL - MMS product, only the products of this category will be exported.
This type of category must be associated to the flow type: 'Purchased'

• Bought (field PURFLG)

When ticked, this box indicates that the product is of type 'Purchased".

• Sold (field SALFLG)

When ticked, this box indicates that the product is of type 'Sold".

• Manufactured (field MFGFLG)

When ticked, this box indicates that the product is of type 'Manufactured".

• Deliverable (field DLVFLG)

This check box is selected by default when the flow type is Sold.

• You can also select this check box even if the product type is not Sold, in order to be able to perform deliveries.
• When the product category is Service or Generic, and the flow types are Sold, you can clear this check box. This setup applies to products that are not included in deliveries. These products are invoiced through invoicing open items. They cannot be used in sales loan orders or open orders.
• When the product category has the Service type, and the flow types are both Bought and Sold, it corresponds to subcontract products. It is mandatory that these products are deliverables. 
  

• Subcontracted (field SCPFLG)

When ticked, this box indicates that the product of of type subcontracted (subcontract BOM).

• ABC class (field ABCCLS)

• Product line (field CFGLIN)

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.
  
  

• SAF-T product type (field ITMSFTTYP)

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

• field TSICOD

Code of the product statistical group, comprised of three alphanumerical characters, to be entered for the chosen group. It is associated with a meaningful label.

• Stock management (field STOMGTCOD)

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.

• QC management (field QUAFLG)

This code is used to define whether this product must 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 modified manually.
• 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 in the order quality control is set to "Yes", quality control is mandatory and the receipt has one 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 in 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 one of the statuses defined in the receipt movement rule for this product.
• Periodic control. This control is automated according to the number of receipts for this supplier and this product. The stock status can still be modified during entry.
  
  

• Technical sheet (field QLYCRD)

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

• Access code (field QUAACS)

• Negative stock (field NEGSTO)

Select this check box 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 ben input into the system. With this check box selected the system can generate a "pending" issue. This issue is adjusted upon input of the stock into the system.

• Management mode (field STDFLG)

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.

• Count mode (field CUNCOD)

Use this field to specify the frequency of counts for products in this category:

• Annual count
• Cycle count
• Not counted. This option is only available for selection for products that are not managed in stock.
  
  

• Stock withdrawal mode (field STOCOD)

The stock issue mode can be defined at category level, then refined by site category.
It is necessary to specify, for the product, when it is defined as material for a finished or semi-finished product:

• whether it has to be consumed upon tracking the work order (immediate consumption),
• or whether it can be consumed upon closing the work order (post-consumption).

Two parameters from the material tracking transaction are associated with the issue mode: upon material tracking, it is possible to filter the materials to be proposed for consumption in the transaction (« post consumption / immediate / all stock issue » in the materials tab in the tacking transaction).

These parameters are:

• Immediate: in the tracking transaction, it is possible to impose a detailed entry of the material consumption (parameter Strict manual issue).
• Post consumption: the products will be consumed upon closing the work order. They can be excluded from the manual material issue entry on WO.
• No management: for a product not managed in stock.

• Traceability (field TRKCOD)

• Product type (field INVPRODTYP)

• Expiration management (field EXYMGTCOD)

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.

• Expiration status (field EXYSTA)

 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.

• Location management (field LOCMGTCOD)

Select this check box to enable location management. You can then select location categories and enter, for each category, the location type and storage location which will be linked to this product category by default.

• Container management (field LPNMGTCOD)

This field is subject to the LPN - License plate no. management activity code.
Select this check box to enable location management. This management is only possible if locations are managed.

• Packing (field PCKFLG)

Select this check box to indicate that this product is taken into account in the packing.
This information can be defined at the product category level and then modified at the product-site level.

• Stock detail (field PCKSTKFLG)

• Packaging (field PCK)

Code on 3 alphanumerical characters.

Enter the packaging in which the product is to be delivered.
This code is used for automatic packing.
The user can open the selection window in the packaging table or create a new one via the tunnel.

• Packaging capacity (field PCKCAP)

It is the number of products, expressed in sales unit, that the packaging can contain.
This value is initialized by default with the quantity entered in the product-site record.

• Lot management (field LOTMGTCOD)

This field is used to define whether the products in the category must be lot managed or not.
The lot can be mandatory or optional (in the latter, it will be possible to have for the same product, stock lines with and without lots).
The lot number is a differentiating criterion for the stock line.
 See thestock line description for further information.

It is also possible to have a management with sublots, which are subdivisions of a lot.
The sublot number is also a differentiating criterion for the stock line. The numbering of sublots is free (number or group of characters for 5 places, by default, on stock receipt the first sublot for a lot will be proposed as 00001).

 The management of lots and sub-lots in the folder is controlled by the activity codes LOT, for the management of lots and SLO, for the management of sub-lots.

• Lot sequence number (field LOTCOU)

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.

• Serial no. management (field SERMGTCOD)

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.
  
  

• Serial sequence (field SERCOU)

• Version management (field ECCFLG)

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.

• Stock version (field ECCSTO)

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.

• Major sequence (field ECCMAJ)

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.

• Minor sequence (field ECCMIN)

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.

• Location category (field LOCDES)

You can only access this field when the location management flag is enabled.
Select each location category you want to link to the product category, line by line. These categories are displayed at the product-site level in the Default locations table. You can thus specify the Location type and Location linked to the product-site by default, for each category.

• Default icon type (field DEFLOCTYP)

• Default locations (field DEFLOC)

• Freight class (field FRTCLS)

Enter the freight class to use when creating a new product-site record for use in Bill of lading. The value is controlled by the legislation and site groupings.

• NMFC (field NMFC)

Enter the NMFC (National Motor Freight Codes) code to use when creating a new product-site record for use in Bill of lading. This field is only available if the 'KUS - Localization USA' activity code and the USABOL - Bill of Lading parameter (LOC chapter, USA group) are set to "Yes".

• Order (field ORDWRH)

Lorsque le site renseigné comporte des dépôts à gérer, il est possible de désigner dans cet onglet un dépôt préférentiel par type de flux.

• Shipment (field SHIWRH)

Lorsque le site renseigné comporte des dépôts à gérer, il est possible de désigner dans cet onglet un dépôt préférentiel par type de flux.

• Stock unit (field STU)

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

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

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

• STK label format (field STULBEFMT)

The stock labels can be printed at the time of movement entry or with the production folder. The label format can be set up an can vary according to the packing unit defined.
  A label format is also associated with a stock unit.

• Weight unit (field WEU)

The weight unit.

• STK weight (field ITMWEI)

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

• Volume unit (field VOU)

• STK volume (field ITMVOU)

• Purchase unit (field PUU)

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.

• PUR-STK conv. (field PUUSTUCOE)

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.

• Sales unit (field SAU)

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.

• SAL-STK conv. (field SAUSTUCOE)

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.

• Changeable (field DACSAUCOE)

Select this check box if modification of the conversion factor between the sales unit and the stock unit at order level is authorized.

• Statistical unit (field SSU)

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

• STA-STK conv. (field SSUSTUCOE)

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.

• Intrastat additional unit (field EEU)

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

• EU-STK conv. (field EEUSTUCOE)

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

• Unit (field PCU)

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

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

Only packing type units from the units of measure table can be selected.

• PAC-STK conv. (field PCUSTUCOE)

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

This conversion factor can be accessed if the packing Unit field (PCU) has been entered, and has a value different from the Stock unit field (STU). It can be initialized using the conversion factor table if the combination exists.

• Changeable (field DACPCUCOE)

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

• Label format (field LBEFMT)

The stock labels can be printed at the time of movement entry or with the production folder. The label format can be set up an can vary according to the packing unit defined.
  A label format is also associated with a stock unit.

• Issuing PAC (field PCURUL)

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.

• Movement type (field TRSTYPE)

Type of the transaction to be set up, to be chosen among the various proposed values. Each transaction type corresponds to an identified stock movement.
The access to some parameters of the transacrtion or to some values of local menus depends on the chosen transaction type.

• Movement code (field TRSCODE)

A stock transaction code is used to specify rules within a similar transaction type.

These codes must be created in the miscellaneous table number 14.

The movement code is used to define specific stock receipt and issue rules for some transactions. For example, a dedicated transaction associated with experienced users can authorize the receipt to stock of goods in A status while the other users may be associated with a transaction authorizing the receipt to stock of goods in Q status.
This will only be possible for product categories authorizing this type of receipt rules and having such a movement code (seeProduct category).

• Location (field LOCNUME)

Indicate via the local menu the location to be proposed for this stock movement.

• Authorized statuses (field AUZSTAE)

Indicate which statuses are authorized in this stock movement type.
A control is carried out upon frid validation so as to only display the chosen authorized statuses.

• Authorized substatuses (field AUZSSTE)

Specify here which sub-statuses are authorized for this stock movement type. To do so, click on Authorized statuses from the Actions icon. Entry is possible in grid mode by selecting the grids from the stock status table or by entering a sub-status template with generic characters (*,?,#,!). On validating this grid, a control is carried out to keep only those corresponding to the chosen authorized statuses.

If this field is left empty, it will be automatically populated with the sub-status templates corresponding to the authorized statuses.

• Default status (field DEFSTA)

It is possible to specify a sub-status by default to facilitate the entry of stock movements. The latter must respect one of the templates defined previously.

• Analysis request (field QLYCTLFLG)

Use this parameter to save an analysis request to be processed by the Quality control function, in the event that the status has been entered with the 'Q' value.

If the value of this parameter is "No", the switching of statuses to "A" or "R" cannot be performed in the Quality control function. It is necessary to use the Stock change transactions function.

• Lot entry (field DACLOT)

Use this field to specify the manual entry conditions of the lot code for the stock movement type.

Free entry

It is possible to enter an existing lot code.

New lot

The entered lot code must not exist in the base.

No

It is impossible to enter a lot code. In this case, the set up default value for the lot code is used again and the lot sequence number is activated.

• Lot by default (field LOTSUPINH)

In this field, you can set up a default value for the entered lot:

None
Supplier lot

The system submits the entered supplier lot number as the internal lot number.

Document number

The system submits the document number that triggered the receipt to stock as the lot number default value .

The table shown below summarizes the impact of the management rule setup on the Receipt type movements in a mandatory lot management context.

In an optional lot management context, use the Actions icon to access an additional function from the Lot field, when performing the receipt to stock: with this function, you can indicate that you want to save a blank lot.

(*) To assign a lot to each counter, the system uses the lot counter linked to the product.

• License plate number (field DACCTR)

Specify whether the license plate number is mandatory or not.

• Order (field ALLRULORD)

A code is attached to each rule. This code is defined in the allocation rules table.

• Work order (field ALLRULMAT)

Specify the allocation rule to be applied to work orders. This code refers to the allocation and issue rules table.

• Shipment (field ALLRULSHI)

Specify the assignment rule to be applied to deliveries and pickings.

• Material consumption (field ALLRULMFG)

Specify the assignment rule to be applied to work orders and material tracking (for materials not attached to subcontract operations).

• Internal movement (field ALLRULTRF)

Specify the assignment rule to be applied to internal movements (miscellaneous issues, assembly/disassembly, transfers).

• Subcontract dispatch (field ALLRULSCO)

Specify the assignment rule to be applied to subcontract deliveries and consumption field reorder plan for subcontractor-type locations.

• Subcon. consumption (field ALLRULSCC)

Specify the assignment rule to be applied to material tracking (for the materials assigned to subcontract operations).
 This rule is also used in the subcons without WO (when allocating materials on a sub-contracting order).

• Allow A (field GLOAAAFLG)

Within the framework of a global assignment, it is possible to specify which statuses are regarded as available for the assignment.
If this indicator is ticked, it will be possible to globally assign products with status "A".
At least one box has to be ticked in this section.

• Allow Q (field GLOQQQFLG)

Within the framework of a global assignment, it is possible to specify which statuses are regarded as available for the assignment.
If this indicator is ticked, it will be possible to globally assign products with status "Q".
At least one box has to be ticked in this section.

• Allow R (field GLORRRFLG)

Within the framework of a global assignment, it is possible to specify which statuses are regarded as available for the assignment.
If this indicator is ticked, it will be possible to globally assign products with status "R".
At least one box has to be ticked in this section.

• Movement type (field TRSTYPS)

Type of the transaction to be set up, to be chosen among the various proposed values. Each transaction type corresponds to an identified stock movement.
The access to some parameters of the transacrtion or to some values of local menus depends on the chosen transaction type.

• Movement code (field TRSCODS)

A stock transaction code is used to specify rules within a similar transaction type.

These codes must be created in the miscellaneous table number 14.

The movement code is used to define specific stock receipt and issue rules for some transactions. For example, a dedicated transaction associated with experienced users can authorize the receipt to stock of goods in A status while the other users may be associated with a transaction authorizing the receipt to stock of goods in Q status.
This will only be possible for product categories authorizing this type of receipt rules and having such a movement code (seeProduct category).

• Location 1 (field LOCNUM)

Indicate via the local menu the location to be proposed for this stock movement.

• Location 2 (field LOCNUM2)

• Location 3 (field LOCNUM3)

• Authorized statuses (field AUZSTAS)

Indicate which statuses are authorized in this stock movement type.
A control is carried out upon frid validation so as to only display the chosen authorized statuses.

• Authorized substatuses (field AUZSSTS)

Specify here which sub-statuses are authorized for this stock movement type. To do so, click on Authorized statuses from the Actions icon. Entry is possible in grid mode by selecting the grids from the stock status table or by entering a sub-status template with generic characters (*,?,#,!). On validating this grid, a control is carried out to keep only those corresponding to the chosen authorized statuses.

If this field is left empty, it will be automatically populated with the sub-status templates corresponding to the authorized statuses.

• Output lot (field SHLLOT)

This field is used to display the stock issue conditions of a lot with an exceeded Use-By-Date:

No, UBD control

The use by date has to be controlled before lot issue.

No, expiry control

The expiry date has to be controlled before lot issue.

Yes

The lot can be issued, irrespective of the use by date and expiry date.

• Prototype version (field AUZPRO)

Specify whether the versions that have the Prototype status are authorized or not for this type of stock issue movement.
You can also specify that they are authorized unless they are on hold.

• Active version (field AUZACT)

Specify whether the versions that have the Active status are authorized or not for this type of stock issue movement.
You can also specify that they are authorized unless they are on hold.

• Version stopped (field AUZSTP)

Specify whether the versions that have the Stopped status are authorized or not for this type of stock issue movement.
You can also specify they are not authorized unless they are subject to a derogation.

• Exclusive entry version (field ORDVER)

Specify whether the version entered in the issue line should be exclusive or not.

• When the entered version is exclusive:
• In the case of an automatic determination of the stock to be issued, only the stock lines with this version will be selected.
• When the stock to be issued is not automatically determined, only the stock lines with this version will be suggested in the picking window of the detailed stock.
• When the entered version is not exclusive : 
• In the case of an automatic determination of the stock to be issued, the entered version will prevail on the other stock lines assigned to another version.

• Accounting code (field ACCCOD)

• field VACITM

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

• SST tax code (field SSTCOD)

• Valuation method (field VLTCOD)

Use this field to initialize at product-site level the valuation method defining the valuation options of the stock transactions.

For more information on stock valuation, see the related documentation: Basic principles for the valuation of the stocks.

• Cost group (field BRDCOD)

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

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

• Standard cost update (field STDCSTUPD)

Use this field to enter the cost update indicator (for each type):

• Entered. The cost calculation does not modify the data entered for this type of cost, and it is not passed on to the lower levels of the BOM.
• Calculated. The existing costs (entered or calculated) will be overwritten by the next calculation run.
  The corresponding column can still be entered.
  
  

• Capitalizable (field FLGFAS)

This check box is used when the Fixed Assetsmodule 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.

• Cost type (field PCCCOD)

Use this field to associate this product category with 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.

• Dimension type (field DIE)

• Dimension (field CCE)

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

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

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

• Movement type (field OTRSTYP)

• Overhead (field OVECOD)

Select an overhead code.

Overhead codes are used as follows:

• To value selected stock movement types.
  The column that defines the formula or fixed rate to be used for the calculation is defined by the OVECOLSTK - Stock overhead column parameter (STO chapter, VAL group).
• To determine the cost price or the production cost price calculation.
  Selected functions use the overhead code for the following:
• To value work center overheads associated with the valuation dimension.
• To value overheads for materials or semi-finished products.

The overheads column that contains the formula or fixed rate to be used in the cost price calculation functions is defined by parameters. For standard cost calculations the OVECOLSTD - Standard calc overhead column parameter (GPA chapter, COS group) applies.

You can modify the column to be applied before running the calculation.

• Include lower level ovrh. (field OVECPNFLG)

Use this field to select the calculation type.

• No. The overhead calculation for the manufactured product does not take into account the overhead amount for the lower-level products.
• Yes. The overhead calculation for the manufactured product takes into account the overhead amount for the lower-level products.

 Lower-level products are products that are not finished products, in other words, the semi-finished products and the raw materials.

• Firm horizon (field FIMHOR)

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

• field FIMHORUOM

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

• Planning horizon (field FRTHOR)

This is the period, expressed in number of days, weeks or months, during which the provisional delivery requests can be completed.

• field FRTHORUOM

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

• Reorder LT (field OFS)

Number of days corresponding to:

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

It is in general fixed for a given lot size, and is used to calculate the start date for the MRP suggestions.

• field JOURS1

• Delivery tolerance % (field MINRMNPRC)

Balance tolerance in percentage
This is the quantity on the order, in purchasing units, below which the closure of the order can be carried out after partial delivery.

• Matching tolerance (field MATTOL)

Use this field to specify the match code for a given product category.
This code is chosen in the list created in the Matching tolerance function.
It corresponds to the code defined by default for any new product associated with this product category.

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

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

• Received product (field RCPFLG)

This flag determines whether the product will be subject to a receipt or not.

A product managed in stock is necessarily received into stock.

• Mandatory PO request (field PRQFLG)

This indicator determines if the entry of a product is prohibited on a direct order. It is in this case mandatory to use a purchase request.

• Version preloading (field LOAECCFLG)

• Purchase unit (field ITMPUU)

This field displays the purchase unit defined in the Units of measure section.

• Type (field ITMTYP)

This is the product type, which can be:

• standard product,
• BOM product: an order line will be generated for the parent product and for each component of the kit. These lines will be independent.
• Kit product: an order line will be generated for the parent product and for each component of the kit. The order lines of this kit are linked.

• Delivery tolerance % (field SALRMNPRC)

This is the quantity on the order, in purchasing units, below which the closure of the order can be carried out after partial receipt.

• Minimum quantity (field MINQTY)

Minimum quantity of order, in sales units.

• Maximum quantity (field MAXQTY)

Maximum quantity of order, in sales units.

• Loan authorized (field LNDFLG)

if this box is not checked, this product cannot be the subject of a loan.

• Back-to-back order (field CTMFLG)

If this box is checked, the product is subject to a direct order management and the operation is as follows:

• If it is a purchased product, the system will propose, from the customer order, the generation of a purchase order for this product,
• If it is a purchased/manufactured product whose suggestion type is "Purchase", the system will propose, from the customer order, the generation of a purchase order for this product,
• If it is a manufactured product, the system will propose, from the customer order, the generation of a work order for this product,
• If it is a purchased/manufactured product whose suggestion type is "Manufactured", the system will propose, from the customer order, the generation of a work order for this product.

• Back-to-back direct qty. (field CTMQTY)

Quantity (expressed in sales units) from which the back-to-back order will be straightforward.

• Price origin (field BASPRIORI)

• % applied (field PURPRIPRC)

• Invoicing term (field INVCND)

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

• The category type is Service or Generic,
• The flow 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.

• Landed cost coef. (field CPRCOE)

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

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

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

This field makes it possible to enter a coefficient included in the calculation of the cost price.
The value entered must be greater than 1.
This value makes it possible to load, by default, the landed cost coefficient recorded in the "Product" record, at the level of the reordering cost.

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

• Fixed cost per unit (field CPRAMT)

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

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

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

This field makes it possible to enter a unit fixed cost.
The value entered must be a positive value. This value makes it possible to load, by default, the unit fixed cost recorded in the "Product" record, at the level of the reordering cost.
This amount applies to the purchase unit of the product category defined in the "Units of measure" tab.
This is expressed in the company's management currency to which the specified site is associated as the default site for the Common data management. This setup is carried out at the level of the Function profile assigned to the User.
It refers to the display currency, the amount being always stored in the folder's currency (the conversion is carried out, if necessary, from the average monthly exchange rate). If no site is entered at the function Profile level, the amount is expressed in the folder currency.
Only one method can be selected to calculate the landed costs: if a cost structure is entered, entering a landed cost coefficient and/or a fixed cost per unit triggers the erasing of the cost structure, after validation of a warning message.

• Cost structure (field STCNUM)

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

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

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

Use this field to enter a cost structure used in the calculation of the cost price. The entry can be performed manually. From the Actions icon, you can also click Selection or Cost structure (access to the Cost structure function).
The cost structure saved on the Product record at supply cost level defaults to the value of this field.

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

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

• Firm horizon (field PLH)

The fixed horizon (in leadtime unit) is used in the calculation of the Master Production Schedule (MPS) and Material Requirements Planning (MRP). It can be used to freeze the production plan on a given period: the suggestions used to cover the shortages located within this horizon are transferred onto the first period beyond this horizon.

These suggestions are subject to a specific marking in the MRP results and MPS results inquiries: in the Order column, the order code is followed by an asterisk (*).

• field PLHUOT

Planning horizon lead-time unit (weeks, fortnights or months).

• Demand horizon (field FOH)

The request horizon, expressed in number of days, is used to calculate the projected stock: the available stock is calculated using the customer order book below this horizon, and the forecasts above this horizon.

• field FOHUOT

Request horizon lead-time unit (weeks, fortnights or months).

• Trend profile (field SESCOD)

Seasonality - This is an allocation curve used to create forecasts, based on a seasonality variation structure that can be parameterized. Seasonality curves are created in the seasonality table.

• Shrinkage percent (field SHR)

The loss percentage corresponds to the production or storage loss.

The production loss corresponds to the totaled loss generated for each routing operation.

This percentage is taken into account in the material requirements planning and in the work order management. it is used to calculate the quantity to be reordered to obtain the quantity to cover the requirement.

• Reorder mode (field REOMGTCOD)

Use this field to define the reordering mode:

• Not managed - No reorder management.
• By MRP - Reorder calculated by the MRP requirements.
• By MPS - Reorder calculated by the MPS.
• By ROP - Reorder on threshold.
• By period - Reorder by periodic replenishment.

• Reorder frequency (field REOPER)

For a periodic reorder mode, indicate here the number of calendar days between two reorders.

• field JOURS8

• Reorder policy (field REOPOL)

The reorder policy is used to set up the calculation mode of suggestions in the MRP processing:

• Taking into account of the stock and stock under control.
• Triggering of the suggestion.
• Quantity calculation.
• Splitting of the calculated quantity.
  It must be chosen from the reorder policy table.
  

• Coverage (field DAYCOV)

The coverage, expressed in weeks, is one of the MRP parameters. It makes it possible to work with changeable security and reorder lots depending on the order book or on the forecasts recorded during the coverage period.

• field SEMAINE

• Suggestion type (field REOCOD)

This suggestion type is used when running material requirements planning. It is used to define if the product has to be subject to:

• Intersite - a transfer.
  
• Purchase
  
• Manufacturing - a production suggestion.
• Subcontracting - a subcontract suggestion.
• No suggestion

If the suggestion is of type Intersite, the reorder site must be specified in the Reorder site field (REFCY).

• Reorder site (field REOFCY)

When the suggestion is of the type inter-site, this field serves to indicate the supplier site from which the replenishment must be carried out. The inter-site suggestion is coupled with a requirement at the replenishment site.

 The inter-site reorder is a flow between two sites in a single company.

• Safety stock (field SAFSTO)

The security stock is used in the material requirements planning. It features an additional stock implemented to be able to face a longer deadline to obtain stock or a request higher than the average request.

• Reorder threshold (field REOTSD)

The reorder treshold is used in the stock management on order. This is the stock level from which a reordering (or work order) is triggered. It is generally equal to the consumption sum during the reorder time, to which the security stock is added.

• Maximum stock (field MAXSTO)

The maximum stock is taken into account in the reorder calculations.

• EOQ (field REOMINQTY)

Minimum reorder quantity
The minimum reorder quantity is used in the material requirements planning according to the selected reorder policy. It is submitted as the calculation quantity in the cost calculation. In general it represents:

• a production economical quantity,
  
• a minimum order quantity imposed by the supplier.
  

• Technical lot (field MFGLOTQTY)

Lot size
The lot size is used in the MRP (Materials Requirements Planning) calculation. According to the reorder policy, the lot size lets you perform the following actions:

• Split a global suggestion into several lots (manufacturing constraint: vat size, etc.)
  
• Round up the requirement to the minimum quantity when the lot size is fixed (purchase constraint such as boxes of n units).
  For example:
  
• Production suggestion of 500 units, to be divided into 5 suggestions of 100 units
  
• Purchasing suggestion of 52 units with a lot size of 12: it is necessary to order 60 units.
  

• Release if shortage (field MFGSHTCOD)

Select this check box to block this product with respect to the printing of the manufacturing folders and production tracking if there is a shortage of physical stock.

• Automatic closing % (field CLEPCTAUT)

This percentage defines the threshold being applied to automatically close the materials during production tracking.

For instance, if the value is 95% and the material requirement is 200 UN, the system will suggest to close the material if the consumed quantity is greater than or equal to 190 UN.

• Assignment rule (field PTOCOD)