General

The General tab presents general information on the Replenishment Strategy.

The following fields are available:

Field Description
Strategy Name The name of the strategy.

This field is mandatory.
Strategy Type Defines the type of strategy to be used. There are three types:
  • E-Kanban – a Kanban Card is to be created in the system
  • Physical Kanban – a Kanban Card is to be created in the system but with a physical copy that will be printed and used
  • Replenishment Order – a specific order for Replenishment is to be created
Strategy Status The status of the strategy. There are four types of status:
  • Draft
  • Final
  • Approved
  • Canceled
Employee No A specific employee who is linked to this Replenishment Strategy.
Trigger Type How the Replenishment Strategy is triggered. There are four types:
  • Min-Qty – when the quantity reaches a certain level, information is sent to the source location
  • Order Status – when the order attains a certain status (e.g., when a sales order is approved), the Replenishment process can be triggered
  • Operation Decision – lets the operator decide when to send information to the source location
  • Plan Based – information can be sent according to a plan (e.g., every hour)
Source Type The type of source location for the Replenishment. There are four types:
  • Vendor
  • Production
  • Warehouse
  • External Source
Priority The priority can be set with the numeric value set in the PRIORITY table.

The priority must be greater than 0.
Order Type Various order types are available to be chosen, e.g., Production Order, Maintenance Order, Inspection Order, Requisition. These order types are determined from the WIP_ORDER_TYPE table.
Description A description of the strategy.
Lead Time (in Seconds) How much time is needed to replenish the location.
Valid From/To The validity dates of the strategy.

The Valid To must be later than the Valid From.

These are the suggested uses of these fields. If necessary, the fields can be used in different ways (i.e., with slightly different interpretations) depending on the implementation and flow.