Mass management
This screen is used to mass create, modify and delete addresses for a given store.
Note: The entry of addresses must comply with the address structure defined for the store.
Prerequisites
Refer to documentation Implementation
Screen management
How to use this screen
Step 1 (mandatory): enter the store for which the locations need to be updated
Step 2: choose the action type (Modification/Deletion/Creation) to be performed on locations.
For example, you can mass create locations having the same characteristics. You can also modify data common to several locations. Finally, if you want to reorganize the store structure, you can delete locations.
Step 3: choose the control code update. If the check box is selected, the location control codes will be recalculated based on the key previously defined in store management.
Step 4: Select addresses.
The entered store address structure is displayed (table of stores).
You can enter the following set of data:
- Start: Specify the start address for each address component.
- End: Specify the end address for each address component.
- Increment: Increment required to move from a current element value to the next value to process.
For instance: In order to create all the odd rows of an aisle, enter the first odd row in the start field "from" and enter an increment of 2.
The "Nb" field indicates the maximum number for each component of the store address structure, based on the entered range.
The "Number of locations" field specifies the total number of locations to be created/modified/deleted in the processing.
Step 5: selection criteria
When modifying or deleting the location, selection criteria are used to display the characteristics of one of the picking or reserve locations.
For instance, if you want to modify all reserve locations of class "A", enter the criteria: location type = reserve and ABC class = A.
Step 6: modification criteria
After validation, the first location found that matches the entered criteria is displayed.
You can then enter the criteria to be modified.
Finally, click "Save": the modification will be performed on all the locations in the selection (not only the example displayed) and a summary of all updated and deleted items will be displayed.
Header
Fields
The following fields are present on this tab :
Block number 1
| Code used to identify the store. This code is controlled in the store table. |
| The store type defines the logistical function of a store:
|
| 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. |
| Address of the location in the store. |
|
|
| This field is used to keep a second address for each location, to be used systematically during the search for input locations, with a view to obtaining a different filling mode from the address alphanumerical order. The structure of the storage address mirrors that which is set up in the store table. |
|
|
Block number 2
| The storage type defines the management characteristics of a group of locations. These management rules are implemented during an addressing phase on input. |
|
|
| Code representing the depositor. In logistics terms, the concept of depositor makes it possible to process separate flows or traffics within the same site. It covers the notion of order giving customer for the service provisions.
|
| A location can be assigned to a product in the following cases: - If the location has the "Picking" type, it must necessarily be assigned to a product to be activated. - If the location has the "Reserve" type, and the storage type forces said location to be reserved to a product. - If the location has the "Reserve" type, this field mentions the product code specific to the object stored at this address, it the storage type of the location forces said location to be single-product. - If several products are present at the same time in the lcoation or the latter is empty, the field is left blank. A location can only be dedicated to a product if it is reserved to a depositor. |
| The reference container of a location represents the priority container dedicated to the location and in which the occupancy concepts are expressed. The location can accommodate other containers than the planned reference container, by means of the "container matchings".
|
|
|
Close
Tab General
Fields
The following fields are present on this tab :
Block
| The location is blocked on input, it will be ignored by the location search algorithm during the input addressing phase. |
| The location is blocked on output, it will be ignored by the location search algorithm during the output addressing phase. As a matter of fact, the products stored there are not available. |
| Indicates that the "Outsize" stock object is overflowing on the given location and no other stock object can be stored. (See Outsize management for further information). |
Dimensions
| Vertical dimension of an entity. Mandatory. Two digits after the comma |
|
|
| Dimension of an entity along its shortest side (perpendicular to the depth). Mandatory. Two digits after the comma |
|
|
| Dimension of an entity along its longest side (perpendicular to the width). Mandatory. Two digits after the comma |
|
|
| 3-dimensional space occupied by the entity. If it is not entered, it is calculated by the system as the product of the 3 dimensions. |
|
|
Movements validation
| The system requires the entry of a control key upon movement validation if: |
| Value of the control code (alphanumerical code of 6 characters). A check will be performed upon entry of the control code in order to check that it is correct. |
Control of dimensions
| Indicates the dimension control type performed during the stock introduction (on input, transfer/replenishment) into this location:
|
| Maximum weight. |
|
|
Management
| 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. |
| Specifies if the location is under inventory. |
Time
| This value (optional) can be used to calculate the time necessary to store an object at the considered address. |
|
|
| This field, where the average location unstocking duration is filed, is used to split the POs if the latter are limited in time. |
|
|
Classes
| The ABC class is characteristic to the location and item container. The ABC class features one of the 5 criteria allowing optimization when putting items away in GEODE. |
| For each location, a priority assignment class is defined. It usually takes into account the caracteristics of the products that will be stored on said location: Lightweight product, heavy product, hazardous material, etc. |
| This parameter mentions one of the assigment classes, for which the sequencing will not be performed for this location. |
Mission management
|
|
|
|
| Specifies if the material type is "Handling". |
History
|
|
|
|
|
Close
Tab Picking
Fields
The following fields are present on this tab :
Stock objects
|
|
Quantities
|
|
|
|
| It is the maximum location capacity expressed in reference container. |
| If the available stock is lower than the replenishment threshold, the system will perform a preventive replenishment if the product output mode specifies it. |
|
|
|
|
|
|
|
|
|
|
Management
| Used to specify in which palletization program (or container), the system will express the output movements to be picked from the picking location. Conditions of use: (to express an output movement from a CU picking location in CC1 superior container) Here are a few examples:let us consider a product with the following palletization program: 1PP1= 2CC1= 24cu, 1 CC1= 6BB1= 12cu, 1 BB1= 2 cu Example 1b: uc picking, CC1 and BB1 modulus Example 2: 3 picking: CC1, BB1 and CU |
|
|
| This field is used to display, assign, and modify, a picking priority to a container + product pair. The assigned locations are sorted by priority (numerical field). The smallest number corresponds to the highest priority. |
Reorder
| This parameter induces the operation of the picking replenishment algorithm. Replenishments of this location will be carried out from locations having the selected type: picking or reserve. |
| In case of picking replenishments, this field informs the system from which level of containers the replenishment will have to be carried out. |
Dynamic Picking
| Stipulates if the handled picking location is temporary or permanent. The concept of temporary picking is used in the dynamic picking module in order to determine whether or not the the stock of the former picking location of a product container needs to be transferred to the new picking location. The stock transfer takes place if the new picking location is permanent. |
|
|
|
|
Close
Tab Reserve
Fields
The following fields are present on this tab :
Stock objects
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantities
|
|
|
|
|
|
|
|
| It is the maximum location capacity expressed in reference container. |
|
|
Close
Tab Dock
Fields
The following fields are present on this tab :
General
| Specifies the dock type(receiving dock,shipping dock orGeneral):
|
| Indicates if the dock address includes a dock levelling system (used to fill in the space between the truck and dock or to compensate for a difference in height). |
| Indicates the dock's height. (only available for entry if no dock leveler is used). |
| Indicates the maximum dock capacity in load unit (defined on the site). If this field is blank, the capacity is unlimited. This parameter is only considered when the load analysis is used. It is used to avoid assigning carrier appointments to docks that cannot support the related loads. |
|
|
|
| Indicates the carrier appointment currently used on the dock. |
| Indicates the current load for the carrier appointment present on the dock. |
|
|
Grid Carriers
|
|
|
|
Grid Client
|
|
|
|
Grid Supplier
|
|
|
|
Close
Reports
By default, the following reports are associated with this function :
LISTEMP : List of locations
This can be changed using a different setup.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Store field error, mandatory field
The store MUST be entered.
Store error, record does not exist.
An attempt has been made to enter a non-existent Store.
Store field error, Store with single address
The selected store must no be of the single address type
End field error, The range is inferior to the start range
The range must be greater than or equal to the start range. The format is defined in the store record.
Storage type field error, the storage type should be 'Main'
The storage type must correspond to the location type.
Storage type error, mandatory field.
The storage type MUST be entered.
Storage type error, record does not exist.
An attempt has been made to enter a non-existent storage type.
Reference cnt field error, mandatory field.
The reference container type MUST be entered.
Reference cnt field error, record does not exist.
An attempt has been made to enter a non-existent reference container.
Depositor field error, mandatory field
The depositor must be entered.
Depositor field error, Record does not exist.
An attempt has been made to enter a non-existent reference depositor.
ABC class field error, mandatory field.
The ABC class must be entered.
ABC class field error, Record does not exist.
An attempt has been made to enter a non-existent ABC class.
Assignment field error, mandatory field
The assignment class must be entered.
Assignment field error, Record does not exist.
An attempt has been made to enter a non-existent assignment class.
Error "Last location for the travel sequence (Inventory): X Please delete the travel sequence before deleting this location".
The last location of a X inventory travel sequence cannot be deleted as long as the sequence exists.
Error "Last location for the travel sequence (Picking): X Please delete the travel sequence before deleting this location".
The last location of a X picking travel sequence cannot be deleted as long as the sequence exists.
Error "Last location for the travel sequence (Replenishment): X Please delete the travel sequence before deleting this location".
The last location of a X replenishment travel sequence cannot be deleted as long as the sequence exists.