Product categories

The initial status of the product.

Direct: The product is set to Active status. It's available immediately for all processes.

With validation: The product is set to In process status. The product status needs to be changed before the product is available.

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

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 subject to the MMS—MMS interface - X3 activity code.

Selected indicates that products assigned to the category are exported to the AXEL - MMS software.

This checkbox is selected by default for Sold flow types.

The category applies to subcontract products if the category type is Service and the flow type is Bought and Sold.

Clear the checkbox if the category type is Service or Generic and the flow type is Sold. The category applies to products that are not included in deliveries. The products are invoiced as open items. They cannot be used with sales loans or open orders.

The classification to use with the product with regard to its importance to the turnover or to the stock, for example.

The ABC category is used as a selection criterion in the stock count lists. Values between A and D can be entered manually or set up to update from the ABC statistical analysis. At the time of creation, the product is not associated with any statistical data and is classified in category D, by default.

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

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

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.

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.

The frequency of counts for products in this category.

Annual count

Cycle count

Not counted: This frequency is only available for products that are not managed in stock.

The stock issue mode. The mode can be defined at category level, then refined by site category.

You need to specify, for the product, when it’s defined as a material for a finished or semi-finished product:

• whether it’s consumed when tracking the work order (immediate consumption)
• or whether it’s consumed when closing the work order (post-consumption)

2 parameters from the material tracking transaction are associated with the issue mode. When tracking materials, the materials to be proposed for consumption in the transaction (post consumption / immediate / all stock issue in the Materials tab in the tracking transaction) can be filtered.

The parameters are:

Immediate: In the tracking transaction, it’s possible to impose a detailed entry of the material consumption (Strict manual issue parameter).

Post consumption: The products will be consumed when closing the work order. They can be excluded from a manual material issue entry for the work order.

No management: For a product not managed in stock.

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 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 products in the category are 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 products in the category. The lot number can be a maximum of 15 characters.

Controls serial number management for the product category.

Not managed: The category 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.

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

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.

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.

Provides access to the product for a quality control operator.

The user profile needs the access code defined to modify the status of a product and perform quality control.

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 Expiration 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 packaging code to use when delivering the product.

This code is used for automatic packing.

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.

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 that locations are managed for products in the category.

This field is subject to the LPN—License plate no. management activity code. The information is defined by default at product category level. You can modify it.

If this checkbox is selected, you can:

• Specify a default container
• Access the table used to draw up the list of containers associated with the product-site

The NMFC (National Motor Freight Codes) code 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.

The icon to link to the product category, by default.

The location type can be used with stock movements. You can enter a code with a generic character such as *, #, !, or ?.

The location to link to the product category, by default.

The location can be used with stock movements if the LOCSUG—Suggested locations parameter (STO chapter, MIS group) is set to Based on product setup.

You can enter a code with a generic character such as *, #, !, or ?. If the location is a dedicated location, an assignment needs to be defined for the product.

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 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 at quality status A, while other users might be associated with a transaction authorizing the receipt to stock of goods at quality status Q.

The substatuses that are authorized for this stock movement type.

This field is automatically populated with the substatus templates corresponding to the authorized statuses, if you leave this field blank.

Use this parameter to save an analysis request to be processed by the Quality control function (GESSTQ), in the event that the status is entered with a Q value.

The manual entry requirements of the lot code for the stock movement type.

Free: A lot code can be entered.

New lot: The lot code needs to be unique.

No: You cannot enter a lot code. The default value for the lot code is used and the number is assigned by the lot sequence number.

The default value for the lot.

None

Supplier lot: The supplier lot number.

Document number: The document number from the receipt transaction.

The following table summarizes the impact of the management rule on Receipt transactions.

(*) The lot counter linked to the product.

Within the framework of a global assignment, you can specify which statuses are regarded as available for the assignment. You need to select at least one checkbox in this section.

This checkbox indicates that products at A status can be assigned globally.

Within the framework of a global assignment, you can specify which statuses are regarded as available for the assignment. You need to select at least one checkbox in this section.

This checkbox indicates that products at Q status can be assigned globally.

Within the framework of a global assignment, you can specify which statuses are regarded as available for the assignment. You need to select at least one checkbox in this section.

This checkbox indicates that products at R status can be assigned globally.

The assignment rule to apply to material tracking, for components that are assigned to subcontract operations.

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 at quality status A, while other users might be associated with a transaction authorizing the receipt to stock of goods at quality status Q.

The substatuses that are authorized for this stock movement type.

This field is automatically populated with the substatus templates corresponding to the authorized statuses, if you leave this field blank.

The stock issue rules for expired lots for this stock movement type.

No, expiration date control: The expiration date needs to be controlled before a lot is issued.

No, use by date control: The use-by date needs to be controlled before a lot is issued.

Yes: A lot can be issued, irrespective of the expiration date or use-by date.

The issue rules for stock of versioned-managed prototypes for this stock movement type.

No: Prototypes are not issued from stock.

Yes, except on hold: Prototypes can be issued from stock only if the stock is not on hold.

Yes: Prototypes can be issued from stock.

The issue rules for an active stock version for this stock movement type.

No: Stock is not issued.

Yes, except on hold: Stock can be issued only if the stock is not on hold.

Yes: Stock can be issued.

The issue rules for a discontinued stock version for this stock movement type.

No: Stock is not issued.

No, unless exception: A discontinued stock version can only be issued to meet an exception date or period.

Yes: A discontinued stock version can be issued.

The accounting code of the category.

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.

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.

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.

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.

The valuation method to apply to stock transactions or movements. The default value is defined for the valuation method specified at product category level.

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

The cost update indicator for each type.

Calculated: The existing entered or calculated cost will be overwritten by the next calculation run. The corresponding column can still be entered.

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.

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

The calculation type.

Total: The overhead calculation for the manufactured product does not include the overhead amount for the lower-level products.

Cascade: The overhead calculation for the manufactured product includes the overhead amount for the lower-level products.

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.

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.

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

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.

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

The fixed horizon (in lead time 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 (*).

The request horizon, expressed in the number of days.

The request horizon is used to calculate projected stock. The available stock is calculated using the customer order book below this horizon. Forecasts are calculated above this horizon.

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 included in the Material Requirements Planning calculations and in work order management. It's used to calculate the quantity to be reordered to obtain the quantity to cover the requirement.

The percentage threshold to apply to automatically close materials during production tracking.

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

The reordering mode.

Not managed: No reorder management

By MRP: Reordering is calculated by the MRP requirements

By MPS: Reordering is calculated by the MPS

By ROP: Reorder on threshold

By period: Reorder by periodic replenishment

The reorder policy used for the calculation mode of suggestions in the MRP calculations:

• Considering stock and stock under control
• Triggering suggestions
• Quantity calculations
• Splitting the calculated quantity

Coverage is an MRP parameter. If you need to define coverage, you need to express it in weeks.

With coverage expressed, you can work with changeable security and reorder lots depending on the order book or on the forecasts recorded during the coverage period.

The suggestion type is used when running Material Requirements Planning. It’s used to define if the product needs to be subject to:

• Intersite: a transfer
• Purchase
• Manufacturing: a production suggestion
• Subcontracting: a subcontract suggestion
• No suggestion

If the suggestion is an Intersite type, the reorder site needs to be specified in the Reorder site field (REFCY).

The supplier site from which a replenishment needs to be carried out for an Intersite type suggestion. The intersite suggestion is mirrored by a requirement at the replenishment site.

The security stock used in the Material Requirements Planning calculations.

It's additional stock implemented to be able to meet a longer deadline to obtain stock or a request for more than an average request.

The minimum stock level.

The reorder threshold is used with on order stock management. It's the stock level from which a reordering or a work order is triggered. It's generally equal to the total consumption during the reorder time to which security stock is added.

The maximum stock level.

The maximum stock is used in the reorder calculations.

The minimum reorder quantity

The minimum reorder quantity is used in the Material Requirements Planning calculations according to the selected reorder policy. It’s submitted as the calculation quantity in the cost calculations. It represents:

• An economical production quantity
• A minimum order quantity imposed by a supplier

The lot or batch size.

The lot size is used in the Material Requirements Planning calculations. According to the reorder policy, the lot size lets you perform the following actions:

• Split a global suggestion into several lots. Manufacturing constraints could be a container or pallet size.

• Round up the requirement to the minimum quantity when the lot size is fixed. Purchasing constraints could be boxes of a specific number of 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: 60 units need to be ordered

The assignment rule creates a link between a requirement such as a sales order or material requirement and a resource such as a work order or purchase order. It specifies the link to create.

If the Direct order (1 to 1) mode checkbox is selected, the system will authorize the assignment of a sales order to a purchase order, for instance, but not the assignment of a sales order to several purchase orders because it needs to be 1 to 1. This rule is applied during order update or creation.

If you do not specify a rule, the rule specified in the DEFPTO—Assignment rule MTO parameter (STO chapter, SCH group) applies by default in the Automatic assignment, Automatic deassignment, and WIP resynchronization functions.