Warehouse structure
The strategy in COGLAS defines the flow of goods control. Each strategy can get strategy positions captured. Each strategy position contains source and destination settings for the storage location search.
Further properties can be set for the strategy, for example to preset the “target loading equipment type” or to set the “feature purity” for the addition to stock.
The strategy can also be set in COGLAS by the customer. In case of questions, your COGLAS contact person should be consulted in any case.
[LE umlagern] with a strategy
Booking with and without a strategy also means different attention to specifications for finding storage space. See the table below.
While booking with a strategy various specifications are observed, for example, the capacity of a block pitch can be exceeded if no strategy is used.
| Restrictions | [LE umlagern] by strategy | [LE umlagern] by storage location | [LE umlagern] by barcode |
|---|---|---|---|
| Observance storage space / level dimension | Yes | Yes | Yes |
| Storage area code from strategy | Yes | No | No |
| Observance of loading equipment specification | Yes | No | No |
| Observance ABC classification default | Yes | No | No |
| Attention capacity at warehouse type block | Yes | No | No |
”Add Strategy” Function
In the strategy area, the strategy head and the strategy position are managed. Strategy creation, modification and deletion is possible. For the positions of the strategy can be adjusted additional the position order.
Strategy plant head see “Strategy head fields care”.
Strategy plant position see “Strategy position fields care”.
Strategy head fields care:
| Input field | Mandatory field | Description |
|---|---|---|
| Name | Yes | Unique strategy name |
| Description | No | Free text. Description to Strategy. |
| Type | Yes | Defines in which process the strategy is used. Make a selection:
|
| Is standard | No | Yes/No. Determines whether this strategy is the default value in the list creation of the associated process. It is recommended that the at least one strategy has been activated with “Is default=Yes” for each strategy type. |
| Running routine | No | Default for the sequence in the storage bin search. Examples:
|
| Reserve with shortage | No | Yes/No. Defines whether the sales order may also reserve partial quantities when “Start order” is selected for the strategy. Sales order status “Shortage” can occur when a position has not found stock at stock removal. |
| Deactivated | No | Yes/No. Shows whether the strategy may be used. |
Strategy Position Fields Nursing:
| Input field | Mandatory field | Description |
|---|---|---|
| Name | Yes | Unique name of the position within the strategy. |
| Description | No | Free text. Description to Strategy. |
| Transport | No | Defines how the transport is to be generated. Make a selection:
|
| Advance strategy | No | |
| Setting | Yes | Selecting a source or destination setting |
| Dependent settings | No | Optional, multiple selection. Naming of alternative source zones or definition of target zone of the relocation. |
The source settings are the part of the strategy that specify the conditions for the source storage location search.
- Menu call “System – Warehouse structure – Strategies – Source settings”.
- Button [Strategiequelle hinzufügen]
The source settings are used for the validation of the inventory sources. They are used for source storage location search for inventory reservation. The following source setting fields are recorded for a profile.
| Input field | Type | Description |
|---|---|---|
| Name | Mandatory field | The following fields for target setting captured for a profile. |
| Description | Free text | Description of the source setting |
| Zone type | Catalog selection | Selection list:
|
| Zone value | Catalog selection | Selection list for zone type. The selection list corresponds to the maintained zone values (example storage area code). |
| Only whole packaging units | yes/no | Refers to picking and transport. The stock allocations are made on the basis of the article master data (packaging levels). Break-offs are not taken into account. For example, packing level “carton = 200 pcs. 200 pcs or multiples thereof are assigned as stock allocations. |
| Only suitable for forklift | yes/no | There are only transfer orders for SUs whose PRTs have the flag “Suitable for forklift” set in the master data. |
| Sorting | Catalog selection | Multiple selection possible, selection order = test order
Selection list:
|
| Picking | yes/no | Zone is to be used as a valid source for picking orders. |
| Use quantity of the packaging unit | Catalog selection | This sets the quantity to be selected via the packaging unit. |
| Random access | yes/no | If the source storage location supports random access, the inventory reservation is created with “Random access”.
Allows the user to select a suitable article |
| Force whole packaging units | yes/no | During inventory allocation, the PRTs in the “Loading equipment types” field and the article master data are compared. If a PRT in the loading equipment categories field matches the PRT in the packaging units, then the exact quantities from the packaging units are taken into account in the stock reservation.
If there are missing parts, the open order quantities are not passed on in descending order in the strategy. Only open residual quantities which are not separable by a multiple of the packaging units (loading equipment types) are passed on. |
| Loading equipment types | Selection list (multiple selection) | Selection of loading equipment, which will be taken into account during stock reservation in the source zone. All loading equipment accounts from the master data are available for selection. Multiple selection possible. |
| Reduction by packaging unit quantity | Selection list (multiple selection) | The requirement quantity is distributed by planning to all PRTs (packaging units) entered there and only the open “remaining quantity requirements” are taken into account in the source setting during stock allocation. Multiple selection possible. |
| Equate alternative article with article | yes/no | The stock reservation checks all alternative articles and the article number to the stock without order therefore equivalent.
The “oldest MHD” over the pool of the article number is to be reserved. Sorting to FEFO can be added (optional). |
The target settings are the part of the strategy that specify the conditions for the target bin search.
- Menu call “System – Warehouse structure – Strategies – Target settings”.
- Button [Strategieziel hinzufügen]
The following fields for target setting captured for a profile.
| Input field | Type | Description |
|---|---|---|
| Name | Mandatory field | The following fields for target setting captured for a profile. |
| Description | Free text | Description of the source setting |
| Zone type | Selection list | Specifies the destination area to which the transport is to be created. Make a selection:
|
| Zone value | Selection list/td> | If a list of values is stored for the zone type, the desired value can be selected here. |
| Allowance | yes/no | Defines whether an allowance should be possible.
|
| New type of loading equipment (storage not possible and separation) | Selection list | If an LHM type is entered, an attempt is made to create an SU with the LHM at the target location if replenishment is unsuccessful. |
| Loading equipment type for height calculation | Selection list | If an LHM type is entered, then this is used for the height calculation.
For the storage location search, the height is to be recalculated based on the article and packaging unit. Consolidation with effective storage location search according to real height. |
| Division in quantity | Numeric value | Separation of the transport into the entered quantity |
| Customs transformation | Yes/No | Defines whether the article number is to be changed to a customs transformation.
Message type “StockTransformation_v1” is activated synchronously at the target LP during storage. Must be activated in service configuration. |
| Separation according to LHM type | Selection list | The value indicates the destination loading equipment (packing unit) for the destination bin shipment. Several loading equipment can be entered. The first one that fits the article is used. |
| Nesting by LHM type | Selection list (multiple selection) | Formation of partial stocks in new storage units. The value specifies the target storage resource in which the quantity to be transferred is to be nested. The source location unit remains intact.
Source = EURO with 4711 and 1000 pieces. |
| Target-loading equipment types | Catalog selection (multiple selection) | Optional. Defines to which PRT type the destination posting should be made.
Example – storage on a fixed storage unit. The LHM type specifies the name. |
| Time storage location search | Catalog selection | Optional. Defines when the storage location search should start. Make a selection:
(1) The selection “On execution” is only valid for strategy type “Production”. |
| Sorting | Catalog selection (multiple selection) | Selection list:
|
| Feature purity | Catalog selection (multiple selection) | Optional. Sets the feature clean storage.
With the selection of at least one value, the feature clean storage for strategy target setting is activated. The values selection and order can be arbitrary. Selection list:
|
The zone values defines the values for a zone type. Zone values can currently be entered for the following zone types:
- Storage area code
- Load area
The zone type incl. Zone value is used in the topology zone assignment and in the source/destination setting strategy.
Feature-pure storage involves the possibility of like-minded features being stored together. The defaults are set at the strategy target setting for the storage location search.
Characteristic clean storage can take place on a parking space with free capacity, a storage area with sufficient dimension or on a storage unit.
The values for characteristic bearing are displayed either in the bearing overview Node info or in the SU details of the girder storage unit.
For the storage location search, only the characteristic values are compared and if they are equal, the addition is confirmed. The order of the feature fields does not matter.