====3.8. Silo/Tank settings====

At the level of silo or tank the settings  below can be defined. \\
The //Consumption Algorithm// is a mandatory setting, make sure that it is properly set.

===3.8.1. General===

{{ :implementation:wms:ose:silo_1.png |General Tab}}

**//Active //** \\
Set whether or not it is active.

**//Can be lined up//** \\
If the option is selected, the stock in the location is used directly and does not need to be picked. When there is a component to be lined up in the production order, the location can be selected during the [[implementation:wms:productionflows#select_lined_up_location|Production flow]].

**//Direct consumption of goods (Production manager)://** \\
If the option ‘Can be lined up’ is set to true, this option is visible. By default the lined up locations are not directly consumed when using the production manager //(ProductionReceipt flow)//. The stock is locked for the production order, and it is consumed when stopping the production order using the production manager. If this option is set to true, the goods that are lined up on this location, will be automatically consumed on the receipt from production.

**//Sequence//** \\
The order in which the products at this location will be used to compose a picking order. The pick locations with the lowest sequence number will be used first to complete the pick order.

**//Max quantity//** \\
The maximum quantity. This is for informational purposes. \\
This will not block a move when quantity will be exceeded.

**//Pick location//** \\
Set whether or not it can be used as a pick location

**//Block stock from being used for the picking process//** \\
If this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when a pick list gets the allocation on location level, these locations are not taken in account. \\
The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING

**//Block move when location is not empty.//** \\
If set, a move to this location when is not empty is not allowed.

**//Block on different item or batch//** \\
  * None: Nothing will happen
  * Warn: Display a warning message when a different item or a different lot number will be added to that location. This warning is only when using the RF terminals.
  * Block: Block the move when a different item or a different lot number will be added to that location.

**//Fixed//** \\
Set whether the silo/tank is reserved for a specific product and if so which are the minimum and maximum quantities.

===3.8.2. Consumption Algorithm===

{{ :implementation:wms:ose:silo_2.png |Consumption Algorithm}}

The consumption algorithm by which the contents of the silo/tank is consumed: differs for fluids or solids. Mandatory setting.

  * FEFO: First to expire, first out
  * Silo: Bottom layer (FIFO)
      * based upon the batch ID
      * based upon the move timestamp to the silo
  * Tank: Multi-layer (Consume a part from each batch)

===3.8.3. Cycle Count===

{{ :implementation:wms:ose:silo_3.png |Cycle Count}}

**//Allow location to be counted during cycle count//** \\
Is the location allowed to be counted?

**//Allow location to be counted during other operations//** \\
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.

**//Locations needs to be counted now//** \\
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)

**//Count after X days//** \\
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.

**//Count after X operations//** \\
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.

**//Locked by (read-only field)//** \\
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location. \\
When a location is locked, it cannot be used in other processes. \\
The location is released by clicking the ‘unlock’ button. \\
Stock on locked locations is not taken in account to create pick list (proposals).