Strategies
General
The strategy in COGLAS defines the flow of goods control. Each strategy can have n strategy items. Each strategy item contains settings for the source and target settings for the storage bin search.
Further properties can be set for the strategy, for example to specify the "Target loading aid type" or to set the "Characteristic purity" for the storage.
The strategy can also be set in COGLAS by the customer. Your COGLAS contact person should always be consulted if you have any questions.
[Transfer LE] with a strategy
Booking with and without a strategy also means observing different specifications for the storage location search. See the following table.
While various specifications are observed when booking with a strategy, the capacity of a block storage location can be exceeded if no strategy is used, for example.
Restrictions | Relocate [SU] by strategy | Transfer [SU] by storage bin | Transfer [SU] by barcode |
---|---|---|---|
Observe storage location / level Dimension | Yes | Yes | Yes |
Storage area Code from strategy | Yes | No | No |
Observe loading equipment specification | Yes | No | No |
Observance of ABC classification Specification | Yes | No | No |
Beachtung Kapazität beim Lagertyp Block | Yes | No | No |
Strategy
Add strategy" function
The strategy header and the strategy position are managed in the strategy area. It is possible to create, change and delete strategies. The position sequence can also be adjusted for the strategy positions.
Strategy creation header see "Strategy header fields maintenance"
Strategy creation position see "Strategy position fields maintenance"
Strategy Header Fields Maintenance:
Input field | Required | Description |
---|---|---|
Name | Yes | Unique strategy name |
Description | No | Free text. Description of the strategy. |
Kind | Yes | Defines the process in which the strategy is used. Make 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 at least one strategy is activated with "Is default=Yes" for each strategy type. |
Running routine | No | Specification for the sequence in the storage bin search. Examples:
|
Reserve with missing quantity | No | Yes / No. Determines whether the sales order may also reserve partial quantities for the "Start order" strategy. Sales order status "Shortage" can occur if an item has no stock when it is removed from storage. |
Deactivated | No | Yes / No. Indicates whether the strategy may be used. |
Strategy Position Fields Care:
Input field | Required | Description |
---|---|---|
Name | Yes | Unique name of the position within the strategy. |
Description | No | Free text. Description of the strategy. |
Transfer | No | Defines how the transport is to be generated. Make a selection:
|
Catch-up strategy | No | - |
Setting | Yes | Selection of a source or destination setting |
Dependent settings | No | Optional, multiple selection. Specification of alternative source zones or definition of target zone of the stock transfer |
Source settings
The source settings are the part of the strategy that specify the conditions for the source bin search.
Menu call "System - Warehouse structure - Strategies - Source settings"
Add strategy source] button
The source settings are used to validate the stock sources. They are used for the source storage bin search for the stock reservation. The following source setting fields can be entered for a profile.
Input field | Type | Description |
---|---|---|
Name | Pflichtfeld | Unique name of the source setting |
Description | Free text | Description of the source setting |
Zone type | Catalogue selection | Selection list:
|
Zone value | Catalogue selection | Selection list for zone type. The selection list corresponds to the maintained zone values (example: storage area code). |
Whole packaging units only | Yes/No | Refers to picking and transport. The stock allocations are made on the basis of the article master data (packaging levels). Partial quantities are not taken into account. For example, packaging level "Carton = 200 pcs". 200 units or a multiple thereof are assigned as stock allocations. |
Only suitable for forklift trucks | Yes/No | There are only transport orders for SUs whose LHMs have the "Suitable for forklift truck" flag set in the master data. |
Sorting | Catalogue selection | Multiple selection possible, selection sequence = test sequence Selection list:
|
Picking | Yes/No | Zone is to be used as a valid source for picking orders. |
Use quantity of packaging unit | Catalogue selection | This defines the quantity to be selected via the packaging unit. |
Optional access | Yes/No | If the source storage bin supports random access, the stock reservation is created with "random access". Enables the user to select a suitable item |
Force whole packaging units | Yes/No | During stock allocation, the LHMs in the "Loading equipment types" field and the article master data are compared. If a LHM in the "Loading equipment types" field matches the LHM in the packaging units, 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 remaining quantities that cannot be divided by a multiple of the packaging units (loading equipment types) are passed on. |
Loading equipment types | Selection list (multiple selection) | Selection of the loading equipment to be taken into account when reserving stock in the source zone. All loading aids from the master data are available for selection. Multiple selection possible. |
Reduction by packaging unit quantity | Selection list (multiple selection) | The required quantity is allocated to all LHMs (packaging units) entered in the planning and only the open "remaining quantity requirements" are taken into account in the source setting when allocating stock. Multiple selection possible. |
Equate alternative article with article | Yes/No | The stock reservation checks all alternative articles and the article number for the stock without sequence, i.e. in the same order. The "oldest BBD" via the pool of the article number should be reserved. Sorting by FEFO can be added (optional). |
Target settings
The destination settings are the part of the strategy that specify the conditions for the destination bin search.
Menu call "System - Warehouse structure - Strategies - Target settings"
Add strategy target] button
The following fields for target settings are added to a profile.
Input field | Type | Description |
---|---|---|
Name | Required | Unique name of the source setting |
Description | Free text | Description of the source setting |
Zone type | Select list | Specifies the destination area to which the transport is to be created. Make selection:
|
Zone value | Select list | If a list of values is stored for the zone type, the desired value can be selected here. |
Allowance | Yes/No | Determines whether an allowance should be possible.
|
New loading equipment type (storage not possible and separation) | Select list | If an LHM type is entered, an attempt is made to create an LE with the LHM at the target location if the replenishment is unsuccessful. |
Loading equipment type for height calculation | Select list | If a LHM type is entered, this is used for the height calculation. For the storage bin search, the height should be recalculated based on the article and packaging unit. Consolidation with effective storage bin search by actual height. |
Division into quantity | Numerical value | Separation of the transport into the entered quantity |
Customs transformation | Yes/No | Determines whether the article number is to be changed for a customs transformation.
Message type "StockTransformation_v1" is activated synchronously at the target LP during putaway. Must be activated in the service configuration. |
Separation according to LHM type | Select list | The value specifies the target loading aid (packaging unit) for the target storage bin shipment. Several loading aids can be entered. The first one that fits the item is used. |
Nesting according to LHM type | Selection list (multiple selection) | Creation of partial stocks in new storage units. The value specifies the target storage aid in which the quantity to be transferred is to be nested. The source storage unit is retained. Source = EURO with 4711 and 1000 pieces. |
Target loading aid types | Catalogue selection (multiple selection) | Optional. Specifies the LHM type to which the target booking should be made. Example - putaway to a fixed bin storage unit. The LHM type specifies the name. |
Time of storage bin search | Catalogue selection | Optional. Defines when the storage bin search should start. Make selection:
(1) The "On execution" selection only applies to the "Production" strategy type. |
Sorting | Catalogue selection (multiple selection) | Selection list:
|
Characteristic purity | Catalogue selection (multiple selection) | Optional. Determines the characteristic-pure storage. Selecting at least one value activates the characteristic-pure storage for the target setting strategy. The values selection and sequence can be arbitrary. Selection list:
|
Zone values
The zone values define the values for a zone type. Zone values can currently be entered for the following zone types:
Storage area Code
Loading area
Article area Code
The zone type including zone value is used in the zone allocation topology and in the source/destination setting strategy.
Storage with pure characteristics (Purity)
Purity storage includes the option of storing like-minded properties together. The specifications are set in the Target setting strategy for the storage bin search.
Storage with pure characteristics can take place in a storage bin with free capacity, a storage area with sufficient dimensions or in a storage unit.
The values for characteristic-free storage are displayed either in the storage overview node info or in the SU details of the carrier storage unit.
For the storage bin search, only the characteristic values are compared and, if they are the same, the addition is confirmed. The order of the characteristic fields is irrelevant.
→ back to COGLAS processes
→ back to COGLAS menu