Common Replenishment Data Fields

In this article

Replenishment Data Fields for BOM and Components

Replenishment parameters break down from Item to Item Store Records

The Replenishment solution offers different Replenishment calculation types.

This article describes the Replenishment data fields that are common to all Replenishment calculation types.

Other Replenishment data fields that are specific to a Replenishment calculation type will be described in more detail in the corresponding articles.

Field Description
Replenishment Calculation Type A Replenishment calculation type can have one of the following values:
  • Average Usage
  • Manual Estimate
  • Stock Levels
  • Like-for-Like
Reorder Point If the Replenishment system has calculated a demand to replenish an item, the Reorder Point has been filled in and the suggested quantity is less than the Reorder Point, the system increases the quantity up to the Reorder Point.

Example:
The system suggests reordering 8 pieces and the field Reorder Point is 10, the System Suggested Quantity is changed to 10.

Maximum Inventory If this field is filled in, the system orders the stock up to Maximum Inventory level if the stock on hand gets below the Reorder Point.

Example:

  1. Replenishment Calculation Type is Stock Levels.
    The Maximum Inventory field is 20, the Reorder Point field is set to 10 and the actual inventory is 8. In this case the system will reorder 12.
    If the Maximum Inventory is 0, the system will order according to the Reorder Point and reorders 2.
  1. Replenishment Calculation Type is Average Usage or Manual Estimate.
    The calculated demand due to the historical sales is 30. The Maximum Inventory field is 20 and the Reorder Point field is set to 10 and the actual inventory is 8. The system suggests 30, but the system will only reorder 12 as the inventory cannot be more than 20.
    If the Maximum Inventory is 0, the system will order 22 (Suggested Qty – Inventory).
Reorder Point - Whse. If this field is filled in and the suggested quantity, combined with the warehouse inventory, is less than the Reorder Point - Whse., the system increases the order quantity to bring the warehouse stock level up to the Reorder Point - Whse. value. This field is only applicable for replenishment journals with Replenishment Type Purchase, Template Type Standard or Component, and Purchase Order Type One Purchase Order per Vendor.

Example:
The calculated demand due to the historical sales for store is 8 and the warehouse inventory is 6. If the field Reorder Point - Whse. is 30, the system suggests 8, but it will reorder 24, as the warehouse inventory needs to be filled up to 30 (24 + 6).

Maximum Inventory - Whse. If this field is filled in and the suggested quantity, combined with the warehouse inventory, is more than the Maximum Inventory - Whse., the system decreases the order quantity to bring the warehouse stock level down to the Maximum Inventory - Whse. value. This field is only applicable for replenishment journals with Replenishment Type Purchase, Template Type Standard or Component, and Purchase Order Type One Purchase Order per Vendor.

Example:
The calculated demand due to the historical sales for store is 150 and the warehouse inventory is 6. If the field Maximum Inventory - Whse. is 100, the system suggests 150, but the system will only reorder 94 as the warehouse inventory cannot be more than 100 (94 + 6).

Effective Inv. Sales Order

Effective Inv. Purchase Ord.

Effective Inv. Purch. Return Ord.

Effective Inv. Transfer Inb.

Effective Inv. Transfer Outb.

Effective Inv. Assembly Ord.

These fields specify if the quantities in the respective order documents will be considered as part of the Effective Inventory for the item during replenishment calculation.

The available options are:

  • Include - The quantities in the documents will be included.
  • Exclude - The quantities in the documents will be excluded.
  • Coverage - The quantities in the documents will be included but only for documents within the coverage days and historical days defined in Replenishment Setup. The coverage days define how far into the future the documents should be included, whereas the historical days define the time horizon fence for the historical period.

You can exclude Transfer Orders that are created from Customer Orders from the Effective Inventory calculation for Transfer Inbound by enabling the Effective Inv. Transfer Inb. Excl. Customer Ord. setting in the Replenishment Setup.

Note:
The settings for these fields apply to all Replenishment Calculation Types except Like-for-Like.

In Replenishment Setup, the same fields can be defined as global setup. When a new item is created, the initial values for these fields are copied from the corresponding fields in Replenishment Setup.

Replen. Data Profile This field contains the code of the Replen. Data Profile record to be used in the Replenishment calculation process.

For more information see the Replenishment Data Profile.

Vendor No. This field contains the number of the vendor that the item should be purchased from. If the Replenishment Data record found for the item has the Vendor No. field filled in, that vendor will be used. If the field is blank, however, the system first looks at the Stockkeeping Unit record and finally the Item record.

Example:
If the Vendor No. field in the selected Item Store record is blank, the system uses the Vendor No. from the Item record as a Stockkeeping Unit record is not found for the Item No and Location Code.

Purch. Order Delivery This field can have two values, To Warehouse or To Store. The value in this field determines whether the purchase orders are to be delivered to a warehouse or to the stores. It is used by the process that adds items to a Replenishment Journal to select the items for the journal.

The field is used when the function Adding Items to a Purchase Replenishment Journal is executed.

The table shows which conditions must be met if the item is to be selected:

Purchaser Order Type field - Replenishment TemplatePurch. Order Delivery Field - Replenishment Data
One Purchase Order per Vendor
One Purchase Order per Vendor with Cross Docking
To Warehouse
Purchase Orders for Receiving LocationTo Store
Transfer Multiple Transfer Multiple is used by the process that proposes transfer order quantities in the replenishment journals. If the Transfer Multiple field is filled in for an item, the quantity in the calculated transfer replenishment journal for that item is always a multiple of the Transfer Multiple. The system always uses the rounding defined in the Replen. Multiple Rounding page.

The Transfer Multiple also applies to the quantity to cross dock in purchase replenishment journal when cross docking is enabled.

It is possible to automatically update the Transfer Multiple field with Transfer Unit of Measure. See Order Multiple and Transfer Multiple Validation for more details.

Purchase Order Multiple Purchase Order Multiple is used by the process that proposes purchase order quantities in the replenishment journals. If the Order Multiple field is filled in for an item, the quantity in the calculated purchase replenishment journal for that item is always a multiple of the Order Multiple. The system always uses the rounding defined in the Replen. Multiple Rounding page.

It is possible to automatically update the Purchase Order Multiple field with Purchase Unit of Measure. See Order Multiple and Transfer Multiple Validation for more details.

Exclude from Replenishment If you want to temporarily exclude an item from Replenishment, you can select this field. The replenishment process will not consider this item. It is possible to update this field for a group of items via the Divisions, Retail Item Categories, and Retail Product Groups pages.
Exclude from OOS Calc. If you want to temporarily exclude an item from Out of Stock calculation, you can select this field. The Out of Stock calculation will not consider this item. It is possible to update this field for a group of items via the Divisions, Retail Item Categories, and Retail Product Groups pages.

Replenishment Data Fields for BOM and Components

A bill of materials (BOM) is a product that consists of multiple items, and these items that are needed to create the BOM are known as components. In the food and beverage sector within the hospitality industry, a BOM is more commonly known as a recipe, and the components are the ingredients that make up the recipe.

There are Replenishment data fields that need to be set up, in order to calculate the demand for the BOM items and the replenishment quantities of the components.

Field Description
Use BOM/Component Journal You can select this field, if you want the replenishment calculation of the BOM and components to be done in a two-step approach. The demand of the BOM items will first be calculated in the BOM replenishment journal, and then in the second step, the system will calculate the replenishment quantities of the components in the component replenishment journal, based on the demand of the BOM and the number of each component needed to assemble the BOM. The field must be selected for the BOM and all its components.

For BOM items, this field is only applicable if the BOM has its BOM Method set to Explode at Posting or Produce.

Calc. Sold Component in BOM Jrnl. If a component can be sold separately, independent from the sales of its BOM, selecting this field will consider such sales in the replenishment calculation.

If the component is an item modifier, it is not necessary to set up this field.

BOM Assembled In This field is only applicable if the BOM has its BOM Method set to Produce. It is used to define if the BOM will be assembled in Warehouse or Store.

Replenishment parameters break down from Item to Item Store Records

When you update the values of the Reorder Point and Maximum Inventory fields in the Replenishment Control Data page, for an item with variants, it is possible to automatically break down the values by Variant Weight or Dimension Pattern, and update the corresponding fields in the Item Store Records.

For more information see Replenishment Parameters Break Down from Item to Item Store Records.