Common data > Product tables > Locations 

This function is used to manage the locations created by the location type management function:

  • inquiry,
  • modification of block code and assigned products,
  • deletion.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The location management function contains three tabs and a header.

Header

Presentation

The header displays:

  • the location code,
  • The location type,
  • the corresponding warehouse, if applicable,
  • the storage site to which it belongs.

Close

 

Fields

The following fields are present on this tab :

Enter or select the storage site where the selected product is active.

The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table.

Location number to select to carry out the following processings:

  • location assignment to products for the location types dedicated according to the put-away plan,
  • modification of the blocked status or occupied for the dynamic location types.

This is the reference of the location type to be selected for the inquiry.

This field, which can not be modified, displays the warehouse attached to the selected storage site.
SEEINFOA location is only associated to a warehouse when the location category is 'Internal' or 'Sub-contractor' and if the storage site manages warehouses.

Close

 

Tab Characteristics

Presentation

This first tab is used to:

  • View the location characteristics.
    These characteristics come from the Location type that was used to create it.
  • View availability information: blocked status and storage location.
  • Modify the status, in order to manually block or unblock a location (for locations managed on loading).

Close

 

Fields

The following fields are present on this tab :

Characteristics

The location types are used to codify the warehouse locations according to their storage characteristics: size, authorized statuses, technical constraints etc.
They are associated with the products by site, and are used in this way to geographically group the products with similar characteristics.
According to the stock transaction parameterization, the location type for the product is proposed by default and can be modified in the transaction entries.

  • Location category (field LOCCAT)

Specify the location type category.

  • Single-product (field MONITMFLG)

Tick if this location type must be occupied by a single product reference.

  • Dedicated (field DEDFLG)

Tick if products must be assigned to this type of location.

The non-assigned locations are not usable.

  • Replenish (field REAFLG)

This flag is used to define whether or not to select reorder locations.

  • Capacity managed (field FILMGTFLG)

Tick if the dynamic location management has to fill each location on a first-unit-used basis.

  • Release mode (field FRGMGTMOD)

This field is used to select the location release method.
The release method is only used with the dynamic put-away method. It is used to specify if a location can be immediately re-used after the issue of all of its stock:

  • - Immediate release. The location is immediately available for a new stock receipt.
  • - Delayed release. The location changes to a free status, but it is not used for stock receipt until after a certain time given by the Delay duration.
  • - Blocked status. The location changes to blocked status after its release. It is necessary to manually unblock it before reusing it.
  • Time delay (field TEMLTI)

If the management of location release is delayed, it is necessary to specify in this field the number of hours during which the location will be unavailable following its release.

This delay is strongly advised, in order to avoid disrupting the good functioning of the warehouse. In effect, a location that is not delayed is freed after the entry on the computer of an issue. If the physical movement has not yet taken place, the location

will be re-allocated with the next receipt even though it is not yet available. This risks to create unpleasant surprises for the storeroom operatives that are trying to place a new pallet in the store!

The delay is also used to protect the system against entry errors (cancellation of receipts or issues).

  • field HOU

 

Block number 2

  • Authorized substatuses (field AUZSST)

Specify here which sub-statuses are authorized for this stock movement type. To do so, click on Authorized statuses from the Actions icon. Entry is possible in grid mode by selecting the grids from the stock status table or by entering a sub-status template with generic characters (*,?,#,!). On validating this grid, a control is carried out to keep only those corresponding to the chosen authorized statuses.

If this field is left empty, it will be automatically populated with the sub-status templates corresponding to the authorized statuses.

Informational

  • Maximum weight (field MAXAUZWEI)

Maximum authorized weight

This field is not associated with any application process: It can be entered for information purposes on 6 integers + 1 decimal.

  • Width (field WID)

Width

  • Height (field HEI)

Height

  • Depth (field DTH)

Depth

Availability

  • Blocked (field LOKSTA)

Blocked status
A blocked status location is not assigned during the stock entry, even if no good is stored.
The location can be blocked manually or automatically during its release, according to the release management method of its location type.

  • Count in progress (field CUNLOKFLG)

 

  • Location status (field OCPCOD)

Free/Occupied report
The location status automatically changes from "free" to "occupied", when the products are received to stock and when it belongs to a dynamically managed type according to the storing mode. However, the status can be manually modified if a problem arises.

  • Available date (field AVADAT)

Availability date.

  • Available time (field AVAHOU)

Availability time

Close

 

Tab Assignments

Presentation

This tab is used to indicate the locations to be assigned and to view those that have already been assigned. These assignments can be manually entered or mass generated using the Location types function.

The grid contains the following information :

  • The assigned product, its description and its stock unit,
  • The replenish threshold: It is expressed in stock unit.
    The Consumption reorder areas function uses this reorder level to carryout location change suggestions. If the stock in a location is less than this threshold there will then be a suggestion.
  • The maximum quantity: expressed in sales unit.
    The Consumption reorder areas function uses this field to calculate the quantity to reorder. The system will attempt to reach the maximum quantity,
  • The packing unit and the PAC-STK coefficient :
    The Consumption reorder areas function expresses the requirements in PAC (packing unit). These requirements are then passed to the internal (if the location is of the internal type) and sub-contractor (if the location is of the sub-contractor type) allocation rules to suggest the stock lines to be moved in the Location replen. workbench function.
  • Economic quantity: the suggestions made by the replenishment will be multiples of this quantity.
Replenishment example:
  • Replen. threshold: 30 STK (stocking unit)
  • Maximum Qty : 120 STK
  • Replen. PAC: box of 10.
  • Economic Qty: 5 Boxes.

For a location stock of 20 STK, the system will create a requirement for 2*5 boxes = 100 STK. The location stock will be 120 STK (<Maximum quantity).
For a location stock of 25 STK, the system will create a requirement for 1*5 boxes = 50 STK. The location stock will be 75 STK (<Maximum quantity).

SEEINFOTo manage the replenishment of breaks, it is possible to specify a threshold and a maximum quantity of 0. In this case, the replenishment will only be suggested in case of break on the location (this can be useful to replenish for sub-contractors). It is the only case where the economic quantity can be greater than the maximum quantity.

 

Fields

The following fields are present on this tab :

Grid Assignments

This field specifies the reference of the product to to process.

 

  • Reorder threshold (field REOTSD)

STK quantity below which, a location re-supply should be triggered.

  • Maximum quantity (field MAXSTO)

Maximum quantity (STK units) to be achieved at the time of the location replenishment.

It is possible to specify a packing unit by supplier.
This product can have several packing units:

  • A packing unit defined on the product record (from the Packing units table). These units are proposed during stock transaction entry.
    The number of packing units that can be entered is subject to the NUC - Number of packing units activity code.
  • A packing unit linked to the supplier (defined on the product-supplier record).
  • Two customer packing units (from the product-customer record). These can be used as sales units in order entry.

Only packing type units from the units of measure table can be selected.

  • PAC-STK conv. (field PCUSTUCOE)

 

  • Economic qty (field QTYPCU)

Economic reorder quantity in PAC (packing unit of measure).
If this is assigned, the quantity to be reordered will be calculated as a multiple of this economic quantity.

 

Tab Content

Presentation

This tab is used to view the location contents: it gives a detailed list of the products, lots and unities stored in the location.

Close

 

Fields

The following fields are present on this tab :

Grid Contents

  • Product (field ITMREF)

 

  • Description 1 (field ITMDES1)

 

  • Lot (field LOT)

 

  • Sublot (field SLO)

 

  • Status (field STA)

 

 

  • PAC quantity (field QTYPCU)

 

 

  • STK quantity (field QTYSTU)

 

  • Serial number (field SERNUM)

 

  • Identifier 1 (field PALNUM)

 

  • Identifier 2 (field CTRNUM)

 

Close

 

Reports

By default, the following reports are associated with this function :

 STOCK03 : Empty locations

 STOCK04 : Occupied locations

 STOCK04B : Locations full

 STOCK05 : Blocked locations

This can be changed using a different setup.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation