Products-sites

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

• Product status (field ITMSTA)

The product status determines how its availability has evolved. The different statuses are: Active, In development, On shortage, Not renewed, Obsolete and Not usable.

During product creation, the default status is dependent on the creation method defined for the assigned product category:

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

Impact of the product status in the sales and purchase modules

Sales

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

Purchases

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

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

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

• Active. The product is available in all the processes.
• In development
• On shortage. The product does not appear in search results, but it can be used by directly entering its code. A non-blocking warning message appears. If the product category creation method is With validation, the status cannot be accessed and its value is forced to the In development value.
• Not renewed
• Obsolete
• Not usable. The product does not appear in search results and cannot be used in scripts. It can however be used in purchase invoices, by directly entering its code. In that case, a non-blocking warning message is displayed.

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

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


• Issues - BOMs
• Non-blocking message: Not renewed, Obsolete, Not usable.


• Work order (component)
• Non-blocking message: In development, On shortage.
• Blocking message: Not renewed, Obsolete, Not usable (product not returned).


• Work order (parent product)
• Non-blocking message: On shortage.
• Blocking message: In development, Not renewed, Obsolete, Not usable.


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


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


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


• Disassembly - On shortage
• Compound assembled:
• No message: In development, Not renewed, Obsolete.

• Product (field ITMREF)

Product reference
The product reference is the "first" component of the product-site identifier.

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

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

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

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

This field is used to specify whether the stock must be displayed in the parcels (Lot, Serial number, Status, etc.)

• Serial detail (field PCKSERFLG)

Select this check box so serial numbers are taken into account in the packing.

This check box can only be accessed if:

• The serial numbers are managed in Global receipt & issue mode.

• The Stock detail check box is selected.

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

• ABC class (field ABCCLS)

The ABC category allows the classification of products with regard to their 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 by update from the ABC statistical analysis, which can be set up. At the time of creation, the product is not associated with any statistical data and is classified in category “D” by default.

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

• Product type (field INVPRODTYP)

• Location management (field LOCMGTCOD)

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

This information is defined by default at product category level. It can be modified.
If this check box is selected, you can:

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

• Default container (field TCTRDEF)

This field is subject to the LPN - License plate no. management activity code.

This field can only be entered if the Container management check box is selected.

Enter the default containers that you want to use when you create license plate numbers on the fly during a stock entry for this product-site. This default container must belong to the list of containers defined in the Container table.

• Recontrol lead time (field SHLLTI)

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

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

• field SHLLTIUOM

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

• Recontrol status (field NEWLTISTA)

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

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

• Recontrol quality record (field LTIQLYCRD)

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.

• UBD coefficient (field DLU)

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

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

This conversion factor is used to calculate, in calendar days, the use-by lead time, based on the shelf life defined at the product record level.

UBD lead time = Shelf life x UBD coefficient.

  The value of the conversion factor must be between 0.1 and 1. The UBD cannot exceed the expiration date.

This UBD lead time is used to determine the use-by date of the product, based on its stock receipt date.

UBD = Lot receipt date +UBD lead time

Defining a UBD provides the customer receiving the lot with the guarantee that the use-by date of their goods is more or less distant from the expiration date.

Example:

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

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

In creation mode, this value is initialized by default with the UBD coefficient entered in the Product record.

• UBD lead time (field DLULTI)

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

• field DLULTIUOM

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

• Description (field LOCNUM)

This table lists all the location categories which have been defined for the Product category.
You can use it to set up the Location type and Location linked to the product-site by default, for each location category.

• Type (field DEFLOCTYP)

For each location category, you can specify the Location type that will be linked to the product-site by default. When a Location type is entered, it can be used in stock movements.
By default, the location type is the one entered for the Product category. You can modify it. You can enter a code with a generic character (*,#,!,?) or a code from the Location types table.

• Default location (field DEFLOC)

For each location type, you can specify the Location that will be linked to the product-site by default. When a location is entered, it can be used in stock movements. However, the LOCSUG - Suggested locations parameter (STO chapter, MIS group) must be set to Based on product setup.

The location suggested by default is the location entered at the Product category level. You can modify it. You can enter a code with a generic character (*,#,!,?) or a code from the Locations table. If the location is of a dedicated type, an assignment must be established for this product.

• Container (field TCTRNUM)

This grid is subject to the LPN - Internal container management activity code. It can only be accessed if the Container management check box is selected.
Enter the list of containers that you want to use when you create container identifiers on the fly during a stock entry for this product-site.
At least one line must be entered for the creation on the fly to be authorized.
Only "internal" containers can be selected.

• Unit (field PCU)

Select the unit associated with the container. You can select either the stock unit or the packing unit defined for the product.

• No. of units/container (field TCTRPCUCOE)

Enter the quantity of possible units for this container.
This information is used to control the capacity when you create containers on the fly during a stock entry for this product-site.
Such a creation will not be authorized by default.

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

• Frequency (field QUAFRY)

If the quality control is periodic, then this field is used to enter the frequency of the controls.

• field QUANUM

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

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

Use this field to allow or prohibit access to this product by a quality control operator. The user can only modify the status of a product and execute quality control if the access code defined on their user profile permits modification.

• Sampling (field SMPTYP)

Use this field to define the sampling mode:

• None - Sampling has not been planned for.
• Single - A single sample is controlled.

The fields in the Sampling block are not available for entry if you select the value None.

• General level (field GENLEVINS)

This field indicates the general control level of products. The AFNOR standard defines three control levels. Level 2 : recommended by the AFNOR standard, is the regular level delivered by Sage.

This field is only available in inquiry mode.

• AQL (field NQA)

Reminder: The Acceptable Quality Level is the quality index of the manufactured products. It requires to pick a certain quantity of samples on a group of finished products, according to the AFNOR NF X06-021 and X06-022 standards. The AQL mathematically guarantees a potential maximum number of defective products defined by a determined units number. The lots of products are rejected if the number of defective parts exceeds the norm.

The AQL is calculated according to two criteria:

• the size of the sample (number of parts from the initial lot associated to the general level of approval), which indicated the sampling code
• the setups for approval and rejection of a lot, i.e. the value of the AQL.

 To determine the AQL, please see the documentation including the calculation tables.

Select the AQL. When entering the sampling, the section "Sample" brings back the size of the rejection and the approval limit according to the quantity entered and the size of the sample.

• Sampling mode (field SMPMOD)

Use this field to define the sampling target:

• Global - The grouping is carried out by product.
• Lot - The grouping is carried out by product and lot.
  
  

• Planner (field PLANNER)

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

• Buyer (field BUY)

• Region/State (field STAFED)

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

• Freight class (field FRTCLS)

This field displays the default value of the product category but it can be modified. The value is controlled by the legislation and site groupings, and it is used when generating new bill of lading detail lines.

• NMFC (field NMFC)

This field displays the default value from the product category when creating new records but it can be overwritten. The value entered in this field is used when generating new bill of lading detail lines.

This field is available only if the KUS - Localization USA activity code and the USABOL - Bill of Lading parameter (LOC chapter, USA group) are set to Yes.

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

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

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

• Stock for project (field PJMSTRSTK)

Select this check box if available physical stock of this product must be allocated to meet demand for a project.

Selecting this check box will ignore the Management mode (STDFLG) defined for this product (Available stockor By order) in the Products function (GESITM).

• Production (field MFGLTI)

Number of days corresponding to the production 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.

• Reduction factor (field MIC)

The declining conversion factor (in percentage) of the reorder lead time is used to calculate the start date of the suggestions in MRP. It is used correct the reorder lead time proportionally to the replenishment, when the planned or suggested quantity is greater than a lot:

Corrected lead time = RL * [1 + (qty/lot - 1) * factor / 100] where RL = reorder lead time.

This conversion factor is generally used for manufactured products. The supplier lead time is an average lead time, rarely in proportion with the lot size.

• Quality control (field QUALTI)

The quality control lead-time (in number of days) is used in MRP: It is inserted between the requirement date and the suggestion end date to take into account the time necessary to carry out the quality control.

• Multilevel (field TOTLTI)

Total reorder lead time for the product, expressed in a number of days: it is the cumulated lead time of all BOM levels (taking into account the quality control lead times).
This field can be entered and exists only for information purposes.

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

• Picking (field PRPLTI)

Number of working days delay applicable for inventory control purposes. That is, the number of days before this product can be used, such as in a manufactured product, a purchase or before it can be shipped for a sale.

This field is not included in MRP processing (FUNMRPG) calculations, MPS processing (FUNMPS) calculations or the Statistical reordering (FUNSTKB) calculations.

• Assignment rule (field PTOCOD)

The assignment rule is used to create a link between a requirement (sales order, material requirement, etc.) and a resource (work order, purchase order, etc.).
This function, which can be accessed via a tunnel or a right click, makes it possible to specify the link to be created: if box "Direct order (1 to 1) mode" is ticked, 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 (it must be 1 to 1).
This rule is applied upon requirement evolution (order update or creation).

If no rule is specified in this field, the rule specified in the DEFPTO - Assignment rule MTO parameter (STO chapter, SCH group) will be the one taken into account by default in the Automatic assignment, Automatic deassignment and WIP resynchronization functions.

• Availability date not applicable (field EXCFDMA)

• Protection in process (replan) (field WIPPRO)

Select this check box to deactivate the replanning of orders in process for the product concerned.

• Work order: in process if at least one production tracking exists.
• Purchase order: in process if partially received.

 This setup is taken into account if the corresponding setup in the requirements calculation setup has the value "according to product".

• Product notes (field ITMNOTE)

Click this icon to display a screen where you can:

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

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

For further information, see the documentation on Notes.

• Internal 'A' (field PHYSTO)

The physical stock field is formatted according to the stock unit. It represents the total of the lots whose status has been set to A (approved).

• Detail alloc. 'A' (field PHYALL)

• Internal 'Q' (field CTLSTO)

The stock in quality control is formatted according to the stock unit. It represents the total of the lots whose status has been set to Q (currently in quality control).

• Detail alloc. 'Q' (field CTLALL)

• Internal 'R' (field REJSTO)

The rejected stock is formatted according to the stock unit. It represents the total of the lots whose status has been set to R (rejected upon quality control).

• Detail alloc. 'R' (field REJALL)

• Detail shortage (field DETSHT)

• Global shortage (field GLOSHT)

• Global allocated (field GLOALL)

• Dock 'A' (field PLFPHYSTO)

• Dock 'Q' (field PLFCTLSTO)

• Dock 'R' (field PLFREJSTO)

• Subcon. 'A' (field SCOPHYSTO)

• Alloc. subcon. 'A' (field SCOPHYALL)

• Subcon. 'Q' (field SCOCTLSTO)

• Alloc. subcon. 'Q' (field SCOCTLALL)

• Subcon. 'R' (field SCOREJSTO)

• Alloc. subcon. 'R' (field SCOREJALL)

• Loan 'A' (field BPRPHYSTO)

• Loan 'Q' (field BPRCTLSTO)

• Loan 'R' (field BPRREJSTO)

• In-transit stock (field TRFSTO)

In-transit stock corresponds to the stock total which has not yet been received on the current site from an intersite transfer.
Click the Magnifying glass icon to directly access the In-transit stock inquiry.

• Transferred stock (field TRASTO)

Transferred stock corresponds to the stock total sent from the current site to a different site which has not yet been received on the ship-to site.
Click the Magnifying glass icon to directly access the Transferred stock inquiry.

• Stock on external sites (field EXTSTODET)

• BP stock (field SCCLNDSTO)

• BP stock allocated (field SCCALL)

• On reorder (field ORDSTO)

It is the replenishing stock count.

• Pending issues (field WAISTO)

Select this check box if the planning calculations should decrease quantities related to suspended transactions from the available stock quantity.

• On sales orders (field SALSTO)

The stock in customer order corresponds to the customer order total quantity and the inter-site demands for the product, not yet delivered.

• Fiscal year (field FIYNUM)

• Period start (field PERSTR)

• Period end (field PEREND)

• field SELPER

Button used to access in display mode the history of the product-site totals.

• Period number (field PERNUM)

• Last receipt (field LASRCPDAT)

Date of last entry in stock.

• Monthly qty. received (field MONRCPQTY)

This quantity represents the total of stock entries that have taken place since the last processing at the end of each month that updates the monthly statistics.

• Annual qty. received (field YEARCPQTY)

• Monthly amt. received (field MONRCPAMT)

This amount represents the total of stock entries that have taken place since the last processing at the end of each month that updates the monthly statistics.

• Annual amt. received (field YEARCPAMT)

• field RCPCUR

• Variance not absorbed (field AMTDEV)

• No. monthly receipts (field MONRCPMVT)

• No. annual receipts (field YEARCPMVT)

• Last issue (field LASISSDAT)

Date of last issue entered in stock.

• Monthly qty. issued (field MONISSQTY)

This quantity represents the total of stock issues that have taken place since the last processing at the end of each month that updates the monthly statistics.

• Annual qty. issued (field YEAISSQTY)

• Monthly amt. issued (field MONISSAMT)

This amount represents the total of stock issues that have taken place since the last processing at the end of each month that updates the monthly statistics.

• Annual amt. issued (field YEAISSAMT)

• No. monthly issues (field MONISSMVT)

• No. annual issues (field YEAISSMVT)

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

• Safety stock (field SAFSTOCLC)

Checked if a safety stock recalculation previously carried out must be used as the basis of the reorder calculation.

Formula: Security stock = K * sigma * lead time

Where:

• K = given coefficient according to the service rate associated with the ABC class if consumption uses a standard law.
• sigma = standard deviation of the average daily consumption - monthly standard deviation/root (number of days).
• lead time = purchase lead time or production lead time. The calculation is only carried out if there is a minimum history available. The number of months in the history used has a ceiling with a maximum number or months defined (the most recent months).
  
  

• Reorder threshold (field REOTSDCLC)

Checked if a preliminary recalculation of the replenishment threshold must be used at the calculation basis.

Formula: Replenishment threshold = Average consumption during the reorder lead-time + security stock (according to parameters).

The calculation is only carried out if there is a minimum history available. The number of months in the history used has a ceiling with a maximum number or months defined (the most recent months).

• Maximum stock (field MAXSTOCLC)

Checked in the event where a safety stock recalculation previously carried out must be used as the basis of the reorder calculation.

Formula: Average consumption / day * (reorder lead time + reorder time)

The calculation is only carried out if there is a minimum history available. The number of months in the history used has a ceiling with a maximum number or months defined (the most recent months).

• EOQ (field REOMINCLC)

Checked if a preliminary recalculation of the replenishment economic quantity must be used at the calculation basis.

Formula (WILSON): Q = root of (24 * R * Oc) / (Sc * Pc)

Where:

• R = Average monthly request.
• Oc = Order placing cost.
• Sc = Stock handling cost.
• Pc = Product cost.

The calculation is only carried out if there is a minimum history available. The number of months in the history used has a ceiling with a maximum number or months defined (the most recent months).

• Production (field MFGROU)

This routing is used in work order management.
It must be present in a code authorized for the site, with a checked "manufacturing" indicator.

• Code (field MFGROUALT)

The alternative selected must be authorized for the site, and have the Manufacturing check box selected. This is the alternative used in transactions where there is no default alternative.

• Cost (field CSTROU)

The standard costs calculation determines the added value by the production, from the range specified here. The range selected must exist in the alternative authorized for the site, with a checked "manufacturing" indicator.

• Code (field CSTROUALT)

The alternative selected must be authorized for the site and have the Cost check box selected. It will be used as a default value for the cost calculation.

• RCCP (field RCCROU)

At the end of the MPS calculation, a global charge calculation can be required from the routing specified here. Rough Cut Capacity Planning is the translation of the French abbreviation "PGC" (for "Planification Globale des Capacités"). The routing selected must exist in the alternative authorized for the site, with a checked "RCCP" indicator.

• Code (field RCCROUALT)

The alternative selected must be authorized for the site and have the RCCP check box selected. This is the alternative used in processings where there is no default alternative.

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

• Shrink with release (field RELSCATIA)

This parameter is used to manage two loss management modes upon production release.
It applies to the parent product. When the check box is not selected, the loss percentages for those components defined in the BOM are not taken into consideration,

• Component sequence control (field COMSEQCON)

• Access code (field WGRACS)

Access code used to restrict access to data for certain users. If the field is entered, only the users that have this access code in their profile can use this product in weighing...

• Storage/Handling (field ISM)

ISM record that will be used for this product.

• Method of correction (field REDMODFLG)

• Weighing tolerance +(%) (field ITMTOLPOS)

This field displays the percentage used to calculate the weight variance.

You can only modify this field if the Setup level is set to BOM.

If the Setup level is SHI record or Product-site, this value is based on the product-sites record (GESITF).

This field is only available when the MWM - Weighing station activity code is active.

• Weighing tolerance -(%) (field ITMTOLNEG)

Use this field to define the permitted "below weight" tolerance percentage for this component.

 You can only modify this field if the Setup level (field LEVSET) field is set to BOM. If the Setup level is SHI record or Product-site this value will be based on the product-site record.

 Activity code MWM-Weighing station must be activated to use the Weighing module to provide real time weight data.

• Method (field VLTCOD)

Use this field to define the valuation method to be applied to stock transactions, or movements.

This field is mandatory. Its value is initialized using the valuation method specified at product category level.

A history of the last three changes to the valuation method is kept in the Products-sites table (ITMFACILIT), with the date and time of each change.

Once set, you are advised not to change the valuation method. Changing the valuation method can affect the value of work orders currently in progress.

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

• Prorata qty. adjust. (field PROPER)

The percentage of the quantity below which the adjusted amount will be distributed in two parts: remaining stock and the stock already issued.

This percentage is compared with respect to the physical stock remaining and the global stock quantity produced by a WO.

This is used to distribute the adjusted price amounts to the appropriate accounts.

If this field is de-activated, the distribution is made without taking into account this limit.

• field PERCENT

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

This field is used to select the calculation type.

Total

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

Cascade

The overhead calculation for the manufactured product takes into account the overhead amount for the lower-level products.

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

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

• Revised std. cost update (field CUTCSTUPD)

• Budgeted std. cost update (field BUDCSTUPD)

• Simulated cost update (field SIMCSTUPD)

• Landed costs-site (field STCNUMITF)

This button opens a window used to enter the landed costs for each product-supplier linked to the site.
It is also possible to enter the landed costs by site from tab "Suppliers" of the Product record or directly from function Landed costs - Site.

• Average cost (field AVC)

Moving average price. This is calculated according to the formula (value received - value issued) / (quantity received - quantity issued) in a given period, or in dynamic fashion.

• field AVCDET

• Currency (field CUR)

• AUC base quantity (field AVCBASQTY)

Quantity serving for the calculation of the moving average price.

• AUC base amount (field AVCBASAMT)

Base amount serving for the calculation of the moving average price.

• Last receipt cost (field LASRCPPRI)

Price of last entry in stock.

• field LASDET

• Last purchase price (field LASPURPRI)

This field is available for display but not for modification.
It is updated with the purchase cost of the line:

• with every receipt,
• with every validation of a purchase invoice linked to a receipt or purchase order.

The following invoices are not taken into account:

• Direct invoices
• Credit memos
• Additional invoices
• Invoices without quantity, related to a purchase order or a receipt.

Example:

• Invoice with a quantity of 10 and a price of €11. The last purchase price is €11
• Credit memo with a quantity of 1 and a price of €4. The last purchase price is still €11
• New invoice with a quantity of 1 and a price of €5. The last purchase price is €5

• Standard cost (field ITCSTD)

This field can only be displayed and it cannot be modified.

• field ITCSTDDET

• Validity start date (field ITCSTRDAT)

This field can only be displayed and it cannot be modified.

• Validity end date (field ITCENDDAT)

• Revised std. cost (field ITCACT)

This field can only be displayed and it cannot be modified.

• field ITCACTDET

• Validity start date (field ITCSTRDATA)

This field can only be displayed and it cannot be modified.

• Validity end date (field ITCENDDATA)

• Count in progress (field CUNLISNUM)

Stock count list number.

• Last global stock count (field LASCUNDAT)

This field displays the date of the last stock count.

• Last global list (field LASCUNLIS)

Stock count list number.

• Stock last count (field CUNSTO)

Last stock - This quantity represents the actual stock recorded during the last stock count.

• Receipts since last count (field CUNRCPMVT)

Quantity according to the stock conversion factor. This quantity represents the positive correction made to the stock after the stock count.

• Issues since last count (field CUNISSMVT)

Quantity according to the stock conversion factor. This quantity represents the negative correction made to the stock after the stock count.

• Next count (field NEXCUNDAT)

This field indicates the next stock count date.

• No. of counts (field CUNNBR)

For products in cycling count, a number of counts (number of products of each class to be counted in stock) is suggested based on:

• the number of counts that has already been made,
• the number of annual counts planned (defined in the Stock parameters, Stock count parameters tab),
• and the stock count date.

It is necessary to either confirm this number or enter another value.
After generation of the stock count lists, the system updates the number of counts eventually selected taking into account the count number requested for each class and any product filters added.

• No. of accurate counts (field CUNNBREQU)

• Count date (field CUNDAT)

• Net accuracy (field NETACC)

• Absolute accuracy (field ABSACC)

• Expected count quantities (field CUNQTYCLC)

• Actual count quantities (field CUNQTYNEW)

• Count variance (field CUNQTYDEV)

• Order (field ORDWRH)

When the product-site authorizes the management of locations, you can enter a preferred warehouse by type of flow.

• Shipment (field SHIWRH)

When the product-site authorizes the management of locations, you can enter a preferred warehouse by type of flow.

• Supplier (field BPSNUM)

Use this table to declare each supplier for the product-site, on each line.
Only those suppliers referenced at the Products-Suppliers level can be entered or selected.

1/Enter the associated code or click Select supplier-product using the Actions icon to select the code from the list of referenced products-suppliers.

The other data in the table cannot be entered.

2/ Below the table, enter the various fields relating to the management of this product-site for this supplier. In creation mode, fields inherit the setup defined at Product-Supplier level.

Once the fields have been entered, you can at a glance view the full list of the possible suppliers for this product-site: What is the priority level for each supplier? Which is the default supplier? Which is the default back-to-back order supplier? Is this a blocked supplier? A back-to-back order supplier?

In the supply plans and on document entry in the purchasing flows, the type of control performed on the referencing of the product-site with the supplier is dependent on the value of the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group).

• Priority (field PIO)

This field displays the priority level assigned to the supplier: the closer to zero the value, the more priority the supplier is given. The zero value represents the highest priority.

• Blocking (field DOUFLG)

This field specifies in the supply plans as well as upon document entry in the purchasing flows whether the supplier:

• Is not subject to any control action
• Is not subject to any blocking action
• Has been issued a warning.
  
  

• Back-to-back order (field CTMBPSFLG)

Select this check box if this is a potential supplier for the back-to-back order.

• Default supplier (field DEFBPSFLG)

Select this check box if this supplier is a default supplier for this product at this site.

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

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

A supplier that has received a warning can still be a default supplier if it has the highest priority level.

• Default back-to-back (field DEFCTMBPSF)

Select this check box if this supplier is a default back-to-back order supplier for this product at this site.

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

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

A back-to-back order supplier that has received a warning can still be the default back-to-back order supplier if it has the highest priority level.

For the transactions:

• The default back-to-back order supplier is the supplier defined at the product-supplier level if no supplier has been defined on the products-sites record, or the supplier is "blocked".
• If no default supplier has been defined on the products-sites record the default back-to-back supplier is not selected.
  
  

• Supplier (field XBPSNUM)

Use this field to define the code of the supplier for this product.

• Blocking (field XDOUFLG)

Specify whether the following rules are applied in the supply plans as well as in purchase transaction entry:

• No. The supplier is not subject to any controls.
• Warning. The supplier is blocked. It will not be submitted as the default supplier and cannot be manually selected.
• Hold. The supplier is suspended. It can still be submitted as the default supplier. Manually selecting this supplier will display a warning message.

• Priority (field XPIO)

Enter the priority level assigned to the supplier: the closer to zero the value, the more priority the supplier is given. The zero value represents the maximum priority.

Use this information to sort suppliers in some selection windows. The crossing of the priority level with the blocking level used for the Product-Site-Supplier combination also lets us identify the default supplier to be suggested in some functions.

• Back-to-back order (field XCTMBPSFLG)

Select this check box if this is a potential supplier for the back-to-back order.

• Landed cost coef. (field XCPRCOE)

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

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

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

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

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

When the PIHCPR - Invoice price adjustment parameter (ACH chapter, INV group) is set to With landed costs, the configuration is not compliant with an Anglo-Saxon accounting. The Goods Received Not Invoiced (RNI) account will not be balanced. This is a limitation of the system.

You can enter these values directly in the Suppliers section in the Products function (GESITM). You can also enter these values via the Landed costs-supplier-site icon or using the Landed costs-site function (GESSTCITF).

• Fixed cost per unit (field XCPRAMT)

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

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

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

Use this field to enter a cost structure used in the calculation of the cost price. You can manually enter this value or click Selection or Cost structure (access to the Cost structure function) from the Actions icon
Only one method can be selected to calculate the landed costs: if a landed cost coefficient and/or a fixed cost per unit are entered, entering a cost structure triggers the reinitialization of these elements (you will need to validate a warning message first).
You can also enter the Product-Site-Supplier landed costs in a dedicated window which can be accessed from the Products function: click the button available from the Suppliers section. This window can also be accessed via theLanded costs - Site function.

• field CUR3

No help linked to this field.

• Cost structure (field XSTCNUM)

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

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

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

Use this field to enter a cost structure used in the calculation of the cost price. You can manually enter this value or click Selection or Cost structure (access to the Cost structure function) from the Actions icon
Only one method can be selected to calculate the landed costs: if a landed cost coefficient and/or a fixed cost per unit are entered, entering a cost structure triggers the reinitialization of these elements (you will need to validate a warning message first).
You can also enter the Product-Site-Supplier landed costs in a dedicated window which can be accessed from the Products function: click the button available from the Suppliers section. This window can also be accessed via theLanded costs - Site function.

• Attribute (field ATTCOD)

Use this field to identify a standard classification, or characteristic of this product - site combination that can be referenced by your web scheduling processes.

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

• Attribute description (field ATTDESAXX)

This field identifies the standard characteristic that you have assigned to this product - site combination as an attribute.

• Attribute value (field ATTVALCOD)

Use this field to identify an individual characteristic of the attribute classification that applies to this product - site combination.

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

• Attribute value description (field ATTVALDESA)

This field identifies the individual characteristic of this attribute classification that you have assigned to this product for this site.