Basic parameters > Locations > Storage types 

Display allHide all

 

This table is used to define the management characteristics of a set of locations.

The storage type regroups all the management rules (related to the locations) implemented during an addressing phase on input.

Note: the storage type determines the reserve/picking nature of the location.

During exploitation, the modification of the setups of "Assignment" type (Product, Depositor) and "Single/Multi" type (Depositor, Item, Container, Origin, Lot, Date) is accepted by the system. Nevertheless, these changes will only be taken into account from the moment that the locations concerned are empty.

During exploitation, if a modification of the setups related to the management of the FIFO dates is introduced, only the "incoming" stock objects will follow the new management rules.

The number of storage types and their codifications is left totally free.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

To create a storage type, a code is assigned to it that identifies it in a unique manner with 3 character and a title. These two pieces of information are found in the header of the management screen. This screen also has 2 definition tabs:

Header

Fields

The following fields are present on this tab :

The storage type defines the management characteristics of a group of locations. These management rules are implemented during an addressing phase on input.

  • Description (field STYDESAXX)

 

  • Active (field ENAFLG)

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used (by recalling their code) on other records (documents, settings ...), or for mass processes.

The authorizations to a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature Workflow.

  • field DESSHO

 

  • Short description (field STYSHOAXX)

 

Close

 

Tab Page 1

Fields

The following fields are present on this tab :

Store type

  • Store type (field STOTYP)

The store type defines the logistical function of a store:

  • main store: picking, reserve, mass, junk
  • single address store: logical store in which the stock is located. A single address without fill control can be defined for this store.
  • splitting store: store type necessary to use the "merging of flows" functionality (preparation in 2 phases). The "splitting area" locations can be considered as reserve locations only used as temporary picking locations.
  • dock store (receipt, shipping): used by the "Carrier appointment" and "Stock on quay of logistical units" functionalities.
  • Cross-docking store: used by the "Cross-Docking" functionality.
  • Buffer store: Store for temporary storage.
  • 2-phase transfer store: used by the "2-phase transfer" functionality.

Type of location

  • Type of location (field SLOTYP)

The location type determines whether the locations are of the reserve type (the allocation and vacating of the locations are carried out in dynamic mode) or of the picking type (the locations are assigned to a container for the Depositor/Product pair).

  • Assembly (field BOMAUZ)

This parameter is reserved to the single-address type stores.

If it is checked, the locations on this storage type can be used for the assembling procedure (allocation of an assembling location to the assembling wave).

Picking

  • Picking pivot (field DYNPIC)

If the box is checked, the picking location is set to "pivot picking", which means it is not assigned to a Depositor/product pair; in that case, the assignment takes place upon wave launching. The use of a picking reserved for the product is a priority compared with the use of pivot pickings, irrespective of the setup of the product output mode.

  • Exceed maximum capacity (field MAXPIC)

Used to specify if the capacity overflow of a picking location is authorized within the framework of a manual or adjustment-type addressing. Upon automaticaddressing, the maximum capacity of a picking location will always be complied with, irrespective of the value of this parameter.

  • Undifferentiated stock object (field SNGSKO)

If this box is checked, there will be only one stock object in a picking location with this storage type. All incoming stock objects will take the characteristics and object number of the first object present in the location.

Otherwise, each stock object in a picking location with this storage type will keep its own characteristics and object number.

Prints

  • Object labels (field PALLBLEDT)

During the search for locations on input, the system prints a pallet label for the objects intended to be put away in locations featuring this type od storage.

Address

  • Address position management (field PSTMGT)

Non available function.

  • Automatic addressing authorized (field AUTALLAUZ)

Flag at Storage Type level: it is used to initialize the flag at location level upon entry of a storage type on the location.

Flag at location level: it is used to indicate whether the location can be selected by the automatic addressing. This value corresponds to the nominal operation code.

Depositor management

  • Depositor management (field DEPMGT)

Stipulates the management mode with respect to the depositor:
- Assigned: locations are reserved for the depositor entered when the locations were created; assignment to the depositor is mandatory if the "product assignment" parameter is active.

- Single: the location is unmarked as far as depositors are concerned; as soon as the location is occupied by a stock object belonging to the depositor, the location will be reserved for this depositor and as soon as the location is empty, an new depositor can occupy it.

- Multi-depositor: at a moment m, and depending on the maximum capacity of the location, several stock objects belonging to various depositors can be stored in the location.

 

Item management

  • Item management (field ITMMGT)

Stipulates the management mode with respect to the products:

- Product assignment: the location is reserved for a Product/Depositor pair. Entry of the depositor code and product code will be mandatory when creating addresses reserved for this storage type. Assignment to a depositor is mandatory if the "Product assignment" parameter is activated.

- Single product: a single product code can exist at a given moment in the location. A picking location is always single-product.

- Multi-product: several product codes can exist at a given moment in the location.

Characteristics

  • Single origin (field SNGORI)

A single origin can exist at a given moment in the location.

  • Single stock nature (field SNGSKN)

A single stock nature can exist at a given moment in the location.

  • Single reservation (field SNGRSA)

A single reservation number can exist at a given moment in the location.

  • Single lot (field SNGLOT)

A single lot number can exist at a given moment in the location.

Close

 

Tab Page 2

Fields

The following fields are present on this tab :

Container management

  • Single container (field SNGCTR)

A single container type and code can exist at a given moment in the location. As soon as the location is occupied by a stock object, the location will be reserved for the container type and code of this object; then, when the location is empty again, another container (the same or a new one) can occupy the location.

  • Container correspondence (field CTRCSP)

The container matching can be used for the locations with this storage type. The location can thus contain containers different from the reference container.

  • Fill Control (field SLOMES)

Used to define the method to calculate the fill rate of a location.
- No: there is no calculation rule, which means that the available space in the location is never calculated. This value is assigned by the system for a storage type without control of the location fill rate (for instance, location with an unlimited capacity).

- In reference containers: the available space is calculated with respect to the maximum number of reference containers for the location. This calculation thus incorporates the matching of the containers defined for the store, based on the containers already present on the location.

For instance: multi-container location with a capacity equal to 20 P1 pallets. Matching rule for containers, 2 P2 = 3 P1. Input of 4 P1 pallets + 2 P2 pallets. The occupancy rate of the location will be equal to 7/20.

- In number of containers: the occupancy is calculated with respect to the number of containers present on the location, even if they are different containers. This option can be useful to define 'junk' locations.

If we consider the same example as previously, the occupancy rate will be 6/20.

- In reference containers on the ground: this parameter is used for the so-called "mass" locations; the number of containers on the ground matches the maxi number of containers of the location. Depending on the incoming product, the maximum capacity of the location is calculated by taking into account the number of containers on the ground, the stacking height and the correction defined for the incoming product container (concept of pallet straddling the last level).

For instance: on the ground capacity, 10; stacking coeff. = 5 (non stackable product =1 ) ; stacking correction = 2. The maximum capacity is equal to (10 * 5) - 2 = 48 pallets of this product.

  • Homogeneous object (field HMGPAL)

Used to define whether or not the locations will be able to receive objects that are non-complying with respect to the palletization program defined for the product::
- No: the location can receive non-homogeneous stock objects, in other words, which are not complying with the palletization standard drawn up for the considered product container. A standard pallet rack can accommodate incomplete or over-palletized pallets.

- Homogeneous standard: the location can only accommodate pallets complying with the palletization standard in force. This option is well adapted to the management of mass bays.

- Homogeneous: the location can only accommodate pallets that are identical to those already contained in the location.

FIFO date management

  • Input FIFO date reset to 0 (field RESFIFDAT)

Those products entering this location lose their FIFO date and are guaranteed to exit first (eg. Picking, Allocated Advanced Reserve, ...).

  • FIFO by location (field FIFSLOMGT)

If the box is not checked, the system does not take into account the FIFO date of the location. This value is selected by default in the case of a "Picking" type location. In effect, a location can accommodate different FIFO dates (depending on the replenishments, for instance) at any given moment. In that case, each object put on this location keeps its own FIFO date.

If the box is checked, the system takes into account the FIFO date of the location (instead of the FIFO date of the stock object) in the output search algorithm. The FIFO date of the location is equal to the date of the first object put in this location. All the stock objects then take the the FIFO date of the location.

  • Entry of anterior FIFO date allowed (field OLDDATINP)

This rule corresponds to the authorization granted to fill a location with products having an older FIFO date.

If the box is not checked, any input to the location of a product having a FIFO date prior to the FIFO date of the oldest stock object on the location is prohibited.

If the box is checked, the operator may place an object with a past FIFO date in a location that is not supposed to accommodate it. This parameter is namely used to free high-capacity locations, only occupied by one or two objects with an old date.

  • Control gap in FIFO in input (field FIFDEV)

If the box is not checked, no check is carried out on the FIFO date before entry is authorized for this location.
If the box is checked, a check on the FIFO date of the input product is carried out before storage is authorized for this location. The checks on the FIFO date are carried based on the duration defined at the level of each product ("Maxi FIFO gap" parameter in the Annex Product Record). They consider: the FIFO date of the input (Input Date) and the FIFO date of the oldest object on the location (Location Date).
For instance: let us consider (FIFO date of the incoming object) > (date of the oldest object on the location + duration of the maximum FIFO gap) => entry to this location is prohibited.

  • Single date (field SNGDAT)

Authorization or not for a location to contain objects with varying FIFO dates (with respect to the day, month or year).

Allocation Seq

  • Unstocking (field TOOMGT)

Concerning objects whose other criteria are equal, this specifies which object will be issued first: the first object in (FIFO) or the last objet in (LIFO).

Swap management

  • Lot swapping (field SWAPLOT)
  • Auto movement split (field SPLITMVT)

RF grouping

  • Stock object (field GRUMVTSKO)
  • FIFO date (field GRUMVTFIF)

Close

 

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

 

Depositor management error, incorrect value.

The value entered in the depositor management is not compatible with the other criteria.

Item management error, incorrect value.

The value entered in the product management is not compatible with the other criteria.

Filling control error, incorrect value.

The value entered in the filling control is not compatible with the other criteria.

Tables used

SEEREFERTTO Refer to documentation Implementation