Table of Contents
3. Organizational Structure Element Settings
All Organizational Structure Elements have a Code and a Name field. Once the code is created, it cannot be changed.
3.1. Warehouse settings
On the warehouse level the following settings can be defined:
Warehouse
This is the link between the warehouse defined in Produmex and the warehouse in SAP Business One (Cfr. Administration → Setup → Inventory → Warehouses.)
Each SAP warehouse can only be linked once in Produmex warehouses.
Stor. Loc. logistic carriers
The location in the warehouse where the logistic carriers are located (in case you have indicated at the company level that logistic carriers have to be stored at one location per warehouse).
This location needs to be a pick location!
Stor. Loc. returnable items
The storage location for the returnable items. This is used when inventory returnable items are used.
Location ‘Lost and Found’
The ‘Lost and Found’ location for that warehouse.
All item differences counted during cycle counting (indirect cycle counting) will be moved to the Lost and found location in case this is set up on the CycleCountController.
Stock on storage locations set for Lost and found, logistic carriers, … are not taken in account to create pick list (proposals).
Use location suggestions?
Set whether location suggestions will be used for move in or to this warehouse.
This is used in the Location Suggestions functionality.
Organizational Structure: Zone settings
On the level of zones the following general settings and attributes can be defined.
General tab
Use for Zone Picking
If the setting is enabled, the zone can be selected during the Zone Picking Flow.
Zone Type
The Zone Type drop-down menu lists the zone types that are configured on the Zone Types tab of the Organizational Structure. More than one zone type can be added to the zone.
If the zone is the main zone and has one or more sub-zones, the zone type of the main zone also applies to its sub-zones. When a sub-zone is created, it automatically inherits the zone type of the main zone. For more information see Working with Zones and Zone Types.
Inherited
The Inherited column shows Yes if the zone type is inherited from the main zone. The inherited zone type cannot be deleted manually on the level of the sub-zone. If the zone type of the main zone is deleted, the system also deletes the given zone type of the sub-zones.
Attributes tab
On the Attributes tab you can add location attribute types and define attribute values for the zone.
Attribute Code
The Attribute Code drop-down menu lists those attribute types that are defined on the Produmex Location Attribute Types (PMX_OSAT) default form.
Attribute Value
In the attribute value field you can add values to the location attribute based on the convertor defined for the location attribute type.
- In case of location attribute types with convertor String, Int, Double and Date, you can manually add values in the Attributes Value field.
- In case of location attribute types with List convertor type, the Attribute Value drop-down menu lists the valid values for the selected location attribute type. The list of the drop-down menu can be defined on the Valid Values for Produmex Location Attributes (PMX_OAVV) default form.
Is Inherited Value
If the Is Inherited Value column shows True, the attribute type and the attribute value are inherited from the main zone.
For information on working with location attributes see Put Away Strategy and Move Restrictions.
3.3. Production line settings
In Produmex WMS a production line is always subordinate to a warehouse.
There are multiple ways of doing production:
- Production Flow: This flow handles the receipt from production and issue for production in the client
- Production Manager and Receipt from Production Flow: On the scanner/touchscreen the receipt for production is booked. The Production Manager handles the starting and stopping of the production order.
Note: Make sure you do not use the same production line for both flows.
The following settings can be defined for a production line:
3.3.1. General
Active
If it is enabled, the production line is active. A production line can only be active when the Input Location, Output Location and Rest Location fields are filled in.
Only 1 started production order allowed
If it is enabled, only one started production order is allowed for the production line.
The setting applies to the Production Manager and Receipt from Production Flow. The Production Flow always forces to have only one production order started on the production line.
Consume All Material on Production Line When Closing Production Order
With the end of the production all materials linked to the production line are issued, that is, no stock remains on the production line and the remaining quantity is 0.
The issued quantity can be equal to or higher than the planned quantity on the Issue for Production document.
Prerequisites:
- Only 1 started production order allowed setting on the level of the production line is enabled.
- The Production Type on the level of the production line is set to SPL_CONS_LOCK.
The setting applies to the following flows:
If the production order is closed on the Production Manager, by default the used quantity equals the on-line quantity and the remaining quantity is 0. The used quantities and the remaining quantities can be changed.
If the production order is closed during the Production Flow, by default the used quantity equals the on-line quantity and the rest quantity is zero on the Enter quantity to consume screen. The used quantities and the remaining quantities can be changed.
If the production order is closed during the Receipt from Production Flow, all materials on the production line are issued for the production order. The used quantity cannot be changed.
Note:
- The setting does not apply to the Put on Hold step during production.
- If the Use Waste? (Y/N) setting on the production controller is enabled, the remaining quantities are issued in a different document as waste materials.
Pick to location
The location where the needed ingredients are picked to. When this is not filled in, the system uses the input location. The Component Weighing Flow uses the Pick to location as input for the items to be weighed. The weighed items will be stored on the input location. Stock on a Pick to location is not taken in account to create picklist proposals.
Lock items picked to this location
If the setting is enabled, the Picking for Production Flow and the Picklist for Production Flow locks the items that are picked to this location. During the Component Weighing Production Flow the locked stock is moved to the input location after it was weighed.
On a Beas-WMS integration environment the stock is locked regardless the value of this setting.
Input location
The location where the needed ingredients are picked to. the production flows move stock from the input location to the production line. Stock on an input location is not taken in account to create picklist proposals.
Output location
The location where the finished products will be stored.
Rest location
Location to which the rest of used materials and ingredients are moved. It is possible to use the input location as rest location. In this case the remaining items will be ready to use for the next production order.
Parent production line
The parent production line is used if for instance the production is done in several steps. In this case the user can define the sequence of the production lines.
Production manager type
This is used when the processing of the production issues is done administratively. The setting is used only by the Production Manager.
It has two possible values:
- SPL_CONS_LOCK: When producing on the shop floor, the items to consume are not directly consumed, but they are locked. When processing the production order administratively, the system will use the locked stock as base for the consumption.
- MPL_CONS_INPUT: When the users do not want to perform the tasks to move the correct stock to the production line when producing, this option is used. When processing the production order administratively, all stock on the input location is used as base for the consumption. Furthermore, all production orders on production lines with the same input location will be processed in 1 time.
Current production order
The current production order for this production line (read-only)
Can be lined up
Some locations can be lined up. If a location is added here, it means the stock in this location is used directly, and does not need to be picked. This is usually used for tanks and/or silo’s.
However an output location of another production line can also be set as ‘lined up’. Now the produced items on the ‘previous’ (linked) production order can directly be used instead of picking the items.
Stock on possible lined up location is not taken in account to create pick list (proposals).
Produce ingredients
This option is used if a linked production order needs to automatically produce stock.
The prerequisites for this to work correctly, is that the lined up location is used as an output location on another production line. At the time of production on the shopfloor, a started production order needs to be found on the production line with as output location the lined up location.
Lined up locations
The current lined up locations
3.3.2. Cycle count
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
3.4. Packing line settings
On a packing line, items that have been picked on a movable location (picking cart) can be packed onto a logistic carrier to be shipped as a logistic unit with an SSCC.
Under the level of the packing line, a thin client element can be created directly (Mobile Client touchscreen mode).
3.4.1. General settings
Active
Set whether or not the packing line is active.
Block stock from being used for the picking process
If this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when a pick list gets the allocation on location level, these locations are not taken in account.
The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING
3.4.2. Cycle count
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
3.5. Dock settings
At the dock level the following settings can be made:
3.5.1. General
Active
Set whether or not the dock is active.
Loading & unloading
Whether the dock can be used for loading, unloading or both.
Pick location
Set whether a dock can also be a pick location (e.g. whether or not newly received goods that are still on the receiving dock can already be considered for picking)
Block stock from being used for the picking process
If this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when a pick list gets the allocation on location level, these locations are not taken in account.
The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING
Sequence
The order in which the products at this location will be used to compose a picking order. The pick locations with the lowest sequence number will be used first to complete the pick order.
This option is visible only if the checkbox of Pick location is checked in.
3.5.2. Cycle count
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
Organizational Structure: Bin location settings
On the level of bin locations the following settings can be defined.
General tab
Active
Enable the setting if the bin location is active.
Location Type
It is possible to define a location type and link it with a bin location. This information has no technical use, it is for information purposes only.
The location types to be displayed in the drop-down menu can be set in the Location types (PMX_LOTY) default form.
Pick Location
Enable the setting if the bin location is a pick location. If this is not the case the items that are stored at this location cannot be used for composing a shipment (order picking). A bin that is not used for picking (bulk location) can be used to store safety stock that is used to replenish various pick locations.
Priority Picking
If the bin location is a pick location, an additional Priority Picking checkbox is displayed. When this checkbox is checked, the bin location has a higher priority during stock allocation for picklists than other bin locations.
Can be Destination for Picking
Enable the setting if the bin location can be a destination destination location of the picking process. If the setting is enabled, it is possible to select this location as dock on the picklist.
Sequence
The order in which the products at this location are used to compose a picking order. The pick locations with the lowest sequence number are used first to complete the pick order.
Block Stock from Being Used for the Picking Process
If this setting is enabled, the stock on this location cannot be used to put on a proposal. When a picklist gets the allocation on a location level, these locations are not taken in account.
If the setting is enabled, replenishment orders do not take stock from locations.
If the setting is enabled, the location is added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING.
Can be Lined Up
If the option is selected, the stock in the location is used directly and does not need to be picked. When there is a component to be lined up in the production order, the location can be selected during the Production flow.
Direct Consumption of Goods (Production Manager)
If the option Can Be Lined Up is set to true, this option is visible. By default, the lined up locations are not directly consumed when using the production manager (Production Receipt flow). The stock is locked for the production order, and it is consumed when stopping the production order using the production manager. If this option is set to true, the goods that are lined up on this location, are automatically consumed on the receipt from production.
Block Move When Location Is Not Empty.
If this setting is enabled, a move to this location when it is not empty is not allowed.
Block On Different Item or Batch
- None: Nothing will happen.
- Warn: Display a warning message when a different item or a different lot number will be added to that location. This warning is only when using the RF terminals.
- Block: Block the move when a different item or a different lot number will be added to that location.
Max Logistic Units
The maximum number of allowed logistic units (SSCCs).
If the stock is not on an SSCC, the system considers all of the stock as one logistic unit.
This does not block a move, but it is used when proposing locations on the devices.
Quality Status
This option forces a certain quality status on the location.
When adding/moving stock to the location, the system will check whether the quality status of the stock matches with the quality status of the location. If the quality status does not match, the following can happen:
- When booking a move through the handheld device or the Produmex inventory report, the system will automatically set the quality status of the stock to the quality status of the location and then it will perform the move.
- When booking a move with other processes, the system will not change the quality status of the stock and the move will be blocked.
When performing a direct cycle count on a location with a quality status, newly created stock will get this quality status.
How to set up location where only released stock can be stored, but avoid the quality status change when non-released stock is moved on the location
On the Quality status tab disable the Can be put on a pick location setting for every quality status that is not allowed on the given location. Then enable the pick location setting for the given bin location. Set the reception/quality control area as a non-pick location.
This way only the allowed quality statuses can be stored on pick locations.
Verification Code
The verification code is a unique code which can be used for verifying bin locations in the different flows. It has the same function as a bin location code, but it is more complex and its use is optional.
By default, you can verify the correct bin location on your scanner by scanning the bin location code or entering it manually, in which case an incorrect code may be entered. With a verification code, you can make sure that the correct bin location is verified because verification codes are not shown on the scanner and force the user to scan the barcode instead of manually entering the code.
Providing a verification code is optional and you can either use the verification code or the bin location code for verifying the correct bin location in the different flows:
- If a verification code is added to a bin location, you need to verify the bin location by scanning its verification code or scanning its bin location code.
- If no verification code is provided to the bin location, you need to verify the bin location by providing its bin location code.
Note: The verification code must be unique. It cannot be used by another bin, and it cannot be an existing location code. If you want to add a verification code to more than one bin location, make sure that each bin location has its own, unique verification code. If you add a verification code which is already used by another bin location, the system displays an error message.
Fixed
Indicates that the storage location is used for specific products. In this case a minimum, maximum quantity is defined for the item on that location.
When a location is fixed, the system will block local moves for other products into that location.
Can Be Replenished
Enables this option if the bin location can be taken in account for replenishment orders.
A minimum, maximum and replenish quantity needs to be set.
This can only be set when the location is a pick location.
Cycle Count tab
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
Put Away tab
This is used in the Location Suggestions functionality.
Item Location Type
This can be used to link a location to an item.
An item can also have an item storage location type.
When locations need to be suggested, and an item has a location item type selected, only locations with the same item location type are allowed.
The list of item storage location types is stored in the PMX_ISLT default form.
Put Away Zone
This stores for a certain storage location:
- What the zones are where the items can be placed
- Or to what put away zone a location belongs to
The list of the Put Away Zone drop-down menu is defined by the Put away zone (PMX_PAZO) default form.
Sort the Pick Sequence Descending?
Locations belong to a put away zone. How are locations within this zone sorted? Pick sequence descending or ascending?
Location Belongs to Put Away Zone?
Does this location belong to a put away zone? If it is not checked, it means that when goods need to be put away for the current location, the system should look for locations that belong to this zone.
If it is checked, the location belongs to this put away zone.
Sequence number
This is the sequence number for the put away zones. It defines the order in which locations in a put away zone needs to be retrieved.
For more information see Location Suggestions.
Attributes tab
On the Attributes tab you can add location attribute types and define attribute values for the bin location.
Attribute Code
The Attribute Code drop-down menu lists those attribute types that are defined on the Produmex Location Attribute Types (PMX_OSAT) default form.
Attribute Value
In the attribute value field you can add values to the location attribute based on the convertor defined for the location attribute type.
- In case of location attribute types with convertor String, Int, Double and Date, you can manually add values in the Attributes Value field.
- In case of location attribute types with List convertor type, the Attribute Value drop-down menu lists the valid values for the selected location attribute type. The list of the drop-down menu can be defined on the Valid Values for Produmex Location Attributes (PMX_OAVV) default form.
Is Inherited Value
If the Is Inherited Value column shows True, the attribute type and the attribute value are inherited from the zone.
For information on working with location attributes see Put Away Strategy and Move Restrictions.
3.7. Movable location settings
A movable location is an intermediate storage location: this can be a cart, a movable rack, etc. A movable location allows the operator to pick one or more orders and pack them onto a logistic carrier at another location (packing station).
3.7.1. General
In the organization structure it is possible to set the code and name of a moveable location and define whether or not it is active.
Stock on movable locations is not taken in account to create pick list (proposals).
3.7.2. Cycle count
A moveable location can also be used in the cycle counting and has the same settings as a bin location.
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
3.8. Silo/Tank settings
At the level of silo or tank the settings below can be defined.
The Consumption Algorithm is a mandatory setting, make sure that it is properly set.
3.8.1. General
Active
Set whether or not it is active.
Can be lined up
If the option is selected, the stock in the location is used directly and does not need to be picked. When there is a component to be lined up in the production order, the location can be selected during the Production flow.
Direct consumption of goods (Production manager):
If the option ‘Can be lined up’ is set to true, this option is visible. By default the lined up locations are not directly consumed when using the production manager (ProductionReceipt flow). The stock is locked for the production order, and it is consumed when stopping the production order using the production manager. If this option is set to true, the goods that are lined up on this location, will be automatically consumed on the receipt from production.
Sequence
The order in which the products at this location will be used to compose a picking order. The pick locations with the lowest sequence number will be used first to complete the pick order.
Max quantity
The maximum quantity. This is for informational purposes.
This will not block a move when quantity will be exceeded.
Pick location
Set whether or not it can be used as a pick location
Block stock from being used for the picking process
If this setting is enabled, the stock on this location cannot be used to put on a proposal. Also when a pick list gets the allocation on location level, these locations are not taken in account.
The locations with this flag to true are added to the view PMX_DISALLOWED_LOCATIONS_FOR_PICKING
Block move when location is not empty.
If set, a move to this location when is not empty is not allowed.
Block on different item or batch
- None: Nothing will happen
- Warn: Display a warning message when a different item or a different lot number will be added to that location. This warning is only when using the RF terminals.
- Block: Block the move when a different item or a different lot number will be added to that location.
Fixed
Set whether the silo/tank is reserved for a specific product and if so which are the minimum and maximum quantities.
3.8.2. Consumption Algorithm
The consumption algorithm by which the contents of the silo/tank is consumed: differs for fluids or solids. Mandatory setting.
- FEFO: First to expire, first out
- Silo: Bottom layer (FIFO)
- based upon the batch ID
- based upon the move timestamp to the silo
- Tank: Multi-layer (Consume a part from each batch)
3.8.3. Cycle Count
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
Configure Mobile Client on Organizational Structure
A thin client is a fixed or mobile operator station (touchscreen, handheld terminal, etc.), by which the operator can interact and communicate with Produmex WMS. On the thin client level the following settings can be made:
1. Workflow tab
Workflow
Next you can also assign a thin client to a “workflow”. A workflow is a sequence of actions to execute a certain operation, e.g. Reception, Picking, Production, Shipping, …
Parameter set
For certain flows extra parameters can be set. When selecting a parameter set, the options to enter are available below.
Number of items in sales unit column name
Define here the column name of the column that stores the number of items in the sales unit, defined on the item master data. By default ‘NumInSale’ is used. If you have a UDF to store this value, you can provide the name of the UDF.
Admin password
Provide here the password that will be used to unlock the administrator functionality in the showroom application. By default the password is ‘produmex’
2. Warehouses tab
Thin clients created under a warehouse will see the warehouse locations and orders for the warehouse by default. On the ’Warehouse’ tab additional warehouses can be assigned for the thin client. If a warehouse is assigned for the thin client, its locations and orders can be seen on the client. It is not possible to disable the parent warehouse for the thin client by unticking the checkbox to the parent warehouse.
3. Users tab
By default every SBO user can use the thin client if there is a free license that can be allocated for the thin client. However it is possible to assign only certain users for a thin client.
If there is at least one assigned user, only assigned users can login on the thin client. In case no users are assigned, ALL users are allowed to access the flow.
On the Users tab every SAP Business One user is listed. Check the ’Assigned’ checkbox in to assign an user.
4. Default Scales tab
On the Default Scales tab you can set the default scales for users that they use during the Weighing Flow. For more information click here.
3.10. Printer settings
For printers the following settings can be set:
Windows printer name
The printer name by which the printer is referred to in Windows
Page size
The default page size for the printer
Active
Set whether or not the printer is active.
Default
Set whether it is the default printer
3.10.1. Printer search path
These printers are used in flows on the devices.
The system will get the printer with the same page size as the report that needs to be printed.
First the system looks for printers below the device (In the organizational structure). Next the system will look if it can find a printer in higher levels, starting from the device.
If the system still does not find a printer, the system will check for printers starting from a location.
Which location is taken will depend on the flow where the report will be printed.
Example: For a reception, the location will be the receiving dock.
The same search pattern as for the device is used. So first look for a printer below the location, next on higher levels.
When the system finds several printers on the same level, and there is 1 printer defined as default, it will take that printer. Otherwise the system will take the first printer it finds on that level.
Remark: When the system searches for printers on higher levels, it will not go back to a lower level to search for a printer.
3.11. Weighing room settings
At the level of a weighing room, the following settings can be defined:
3.11.1. General tab
Active
Set whether the weighing room is active or not.
Input location
The location where the ingredients that needed to be weighed are picked. During the weighing process, stock will be moved to the weighing room from the input location.
Output location
The location where the weighed goods will be moved.
A typical setup is when the input location of the weighing room is the pick to location or the input location of the linked production line and the output location of the weighing room is the input location of the linked production line.
Weigh strategy
The weigh strategy defines whether the stock to weigh can be selected based on the weigh order or the item code during the Weigh flow. For more information click here.
3.11.2. Cycle Count tab
Allow location to be counted during cycle count
Is the location allowed to be counted?
Allow location to be counted during other operations
Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count.
Locations needs to be counted now
When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …)
Count after X days
When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken.
Count after X operations
If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken.
Locked by (read-only field)
This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location.
When a location is locked, it cannot be used in other processes.
The location is released by clicking the ‘unlock’ button.
Stock on locked locations is not taken in account to create pick list (proposals).
3.12. Scale settings
Define the scale under a weighing room,dock or a packing station. One scale can only belong to a single weighing room/dock/packing station.
At the scale level the following settings can be defined:
Active
Set whether the weighing room is active or not.
Scale definitions
Define the scale on the Scale definitions field.
If the scale is connected without the ScaleComm service, define it with the one of the following formulas:
- Direct connection: com:/ /Port?Baudrate,Databits,Parity,Stopbits
Example:com://COM3?9600,8,N,1
- Local network: tcp:/ /IP address
Example:tcp://192.168.1.5:4001
If the scale is connected by using the ScaleComm service, tick the Use as a service checkbox and define the scale with the following formula:
- http:/ /URL of the server where the service runs/scale code (OSE)/communication parameters
Example:http://192.168.1.2:9991/SCL01/com://COM3?9600,8,N,1
Uom
Select the unit of measurement of the scale from the Uom dropdown list.
Minimum weight
Enter the minimum weigh of the scale in the Minimum weigh field.
Maximum weight
Enter the maximum weigh of the scale in the Maximum weigh field.
Accuracy
Enter the accuracy of the scale to the Accuracy field.
Example: If the number of decimals is 2 – Accuracy: 0.01
Scale commands
Define the scale commands. Select the command type. The following command types are supported:
- Set tare
- Set zero
- Get weight
- Weight return
The ‘Zero return’ and the ‘Tare return’ commands are not supported yet but are reserved for future use.
Add the description to the Description field and the command to the Command format field.
Command format
Please refer to the user manual of the scale to see the command.
The syntax of the Weight return result string should be a regular expression.
Example:
Weight return string from the scale manual:
<LF><p>w1w2w3w4w5w6<dp>w7w8u1u2<CR><LF>H1H2H3<CR><ETX>
Weight return string defined for the scale on the Organizational Structure:
\x0a *(?'weight'.+)(?'uom'..)\x0d\x0a.+\x0d\x03
3.12.1. Defining multiple scales through one port
Produmex WMS Organizational Structure
First create a ‘scale’ type element in the Organizational Structure of Produmex WMS for the port.
Add a unique code and name. Example:
PORT, Port for scale
Define the port on the Scale definitions field with one of the following formulas:
- Direct connection: com:/ /Port?Baudrate,Databits,Parity,Stopbits
Example:com://COM3?9600,8,N,1
- Local network: tcp:/ /IP address
Example:tcp://192.168.1.5:4001
Do not check the ‘Use as service’ checkbox.
The ScaleComm service will establish the connection to the port based on the configuration file of the ScaleComm service.
The scales connected through the port will be identified based on the sent command.
Select the command type and add the scale codes and the scale command to the Command format field using the following formula: scale code;command;scale code;command
Example:
Get weight command:
scale01;S6R$;scale02;S7R$
Where:
- ‘scale01’ = scale code of the first scale
- ‘S6R$‘= get weight command of the first scale
- ‘scale02’ = scale code of the second scale
- ‘S7R$’ = get weight command of the second scale
Weight Return command:
(?'weight'.+)\x0d\x0a;(?'weight'.+)\x0d\x0a
The order and the number of the scale commands must be the same as in the 'Get weight command'.
ScaleComm service
Open the configuration file of the ScaleComm Service.
Add the code of the port defined in the Organizational Structure as the value for ScalesCodes. Example:
<add key="ScalesCodes" value="PORT" />
Make sure that the ‘Skip Polling’ option is set to ‘False’ and adjust the ‘Polling Interval’ if needed.
Scale weigh result
Open the Scale Weigh Result user table via the following path: Tools> Default forms. Add the scale codes defined on the Command format field as the ‘Code’.
When the ScaleComm Service runs, it will add the weight to the ‘Weigh’ field of the matching scale.
