3 Configuration
Overview
The configuration chapter covers functionality found within the configuration menu of the desktop application.
Features include:
System Administration
Figure 3-1 System Administration Screen
![System Administration Screen System Administration Screen](img/con_systemadmin.png)
The System Administration in the desktop application is an admin screen used to setup the system configurations for both the desktop application and the mobile application. You can access this screen by selecting System Administration from the Configuration menu within the Admin menu.
You need to have proper permissions to access this screen.
Some of the system configurations cannot be changed to protect the data integrity of the system.
Select the parameter and edit the settings on the detail portion and apply the changes. The details of the individual configuration settings are described in a separate section.
Store Administration
Figure 3-2 Store Administration Screen
![Store Administration Screen Store Administration Screen](img/con_storeadmin.png)
Store Administration in the desktop application is an admin screen used to setup the store level configurations. Access this screen by selecting the Store Administration from the Configuration menu within the Admin menu.
You need to have proper permissions to access this screen.
Select the parameter and edit the settings on the detail portion and apply the changes. The details of the individual configuration settings are described in a separate section.
The Restore Defaults option can be used to restore the default parameters for the store. The system will update all the store parameters of the current store to the default store parameters.
Figure 3-3 Store Administration Screen - Select Stores
![Store Administration Screen - Select Stores Store Administration Screen - Select Stores](img/con_storeselect.png)
Select Stores popup is accessed by selecting the Select Stores option on the Store Administration screen. It is used to define which stores the store admin configurations should be applied to. The list of stores will be those in which the user has security permissions. The user is able to select one or more stores from the list. Once saving and exiting the Store Administration screen, all of the selected stores will have their store admin configurations updated.
Store Administration Defaults
Figure 3-4 Store Administration Defaults Screen
![Store Administration Defaults Screen Store Administration Defaults Screen](img/con_storeadmindefaults.png)
The Store Administration Defaults in the desktop application is an admin screen used to set default values for store level configurations that control a variety of behavior in the desktop application and the mobile application. Access this screen by selecting Store Administration Default from the Configuration menu within the Admin menu.
You need to have proper permissions to access this screen.
Use the Reset Stores option to change the current value of a parameter to all the stores.
The changes done in this screen, with the exception of Reset Stores option, will not default automatically to the store parameters; it will only be considered to default the store parameters when a new store is data seeded.
Note:
Making changes to this screen does not impact already existing store administration values.
Ad Hoc Stock Count Tolerance
Figure 3-5 Ad Hoc Stock Count Tolerances Screen
![Ad Hoc Stock Count Tolerances Screen Ad Hoc Stock Count Tolerances Screen](img/con_adhoctolerances.png)
The Ad Hoc Stock Count Tolerances screen is an admin screen used to maintain tolerances which are used to determine discrepant items within Ad Hock stock counts. These tolerances are maintained on a per store basis. The screen is accessed from the Configuration menu within the Admin menu.
Note:
Ad Hoc stock counts can only be executed with the mobile application.
Tolerances are set up at the class hierarchy level, displaying only those departments that a user has data permissions for. The tolerances can be defined for variance percentages as well as variance standard unit of measures.There is a record for each class in the system, and initially upon install both variances will be set to zero. Variances must be whole numbers. At least one of the tolerances must be set up for each class, both cannot be left blank.
When counting an ad hoc stock count the system will look at the variances defined for the class that the item belongs too. If the difference between the counted quantity and the stock on hand exceeds the variance, the item will be considered discrepant. you must be within the lowest defined variance. A variance of zero for either field means that the count must be exact and cannot be discrepant.
Example: Item TV has SOH of 10 Units. Tolerance defined for 2 Variance SUOM and 10% Variance Percent. If you counts 8 that exceeds the variance and it would be considered discrepant.
Customer Order Picking Tolerance
Figure 3-6 Customer Order Picking Tolerances Screen
![Customer Order Picking Tolerances Screen Customer Order Picking Tolerances Screen](img/con_coptolerance.png)
The Customer Order Picking Tolerances screen is an admin screen used to maintain tolerances which are used within Customer Order Picking. These tolerances are maintained on a per store basis. Because variable unit of measure items can be difficult to pick exactly, tolerance can be needed. Tolerances define if and how much variable UOM items can be over picked. The screen is accessed the Configuration menu within the Admin menu.
Tolerances are set up at the class hierarchy level, displaying only those departments that a user has data permissions for. The tolerances can be defined for variance percentages as well as variance standard unit of measures.. There is a record for each class in the system, and initially upon install both variances will be set to zero. Variances must be whole numbers. At least one of the tolerances must be set up for each class, both cannot be left blank.
When performing a pick, the pick quantity cannot exceed the suggested pick quantity by more than the variances defined for the item's class. You must be within the lowest defined variance. This is applicable only to items that are not unit/each items, for example pounds. A variance of zero for either field means that the suggested pick quantity cannot be exceeded.
Example: Ordered 2 KG bananas. Tolerance defined for 1 Variance SUOM and 10% Variance Percent. User is not able to pick exactly 2 KG and picks 2.1 KG. This is acceptable as the .1 KG does not exceed the defined variances.
Barcode Processor
Figure 3-7 Barcode Processor
![Barcode Processor Barcode Processor](img/con_barcodeprocessor.png)
The Barcode Processor screen is an admin screen used to manage which barcode processors execute and the sequence in which they should be called. You can mark a barcode processor inactive or active. The Barcode Processor screen is accessed via the menu: Admin / Configuration / Barcode Processor. You must have Access Barcode Processor permission for the Barcode Processor menu option to display.
The screen will display a set of barcode processors that were created via the data setup script.
-
Processor Name: The name of the processor. This does not alter how the processor works. For example, Type 2 E will continue to parse Type 2 E, even if it is renamed to Type 2 K.
-
Sequence: Sequence indicates the order the barcode processors will attempt to analyze the item scanned. It starts with the lowest sequence number and proceeds upward. Items will be returned by the first barcode processor that finds a valid item within the barcode and then further processing is halted.
-
Active: Yes indicates that the barcode processor is active and will be used when scanning items. You can mark a barcode processor inactive or active. It is important to ensure barcode processors not used by the store are deactivated as this will significantly increase the performance of scans in the system.
List of Barcode Processors:
These barcode processors are inserted via data setup scripts at install time.
Name | Description | Active | Process Sequence |
---|---|---|---|
SKU |
SKU |
Y |
10 |
GS1 |
GS1 |
Y |
20 |
GS1 12 |
GS1 12 |
Y |
23 |
GS1 13 |
GS1 13 |
Y |
26 |
VPLU_A |
Type 2 A |
Y |
30 |
VPLU_B |
Type 2 B |
Y |
40 |
VPLU_C |
Type 2 C |
Y |
50 |
VPLU_D |
Type 2 D |
Y |
60 |
VPLU_E |
Type 2 E |
Y |
70 |
VPLU_F |
Type 2 F |
Y |
80 |
VPLU_G |
Type 2 G |
Y |
90 |
VPLU_H |
Type 2 H |
Y |
100 |
VPLU_I |
Type 2 I |
Y |
110 |
VPLU_J |
Type 2 J |
Y |
120 |
VPLU_K |
Type 2 K |
Y |
130 |
VPLU_L |
Type 2 L |
Y |
140 |
UPC_E |
UPC E |
Y |
150 |
UIN |
UIN |
Y |
160 |
VPN |
VPN |
Y |
170 |
RFID |
RFID |
Y |
180 |
RFID GTIN 12 |
RFID 12 |
Y |
183 |
RFID GTIN 13 |
RFID 13 |
Y |
186 |
Note:
Any changes to the Barcode Processor configuration will become effective after an approximately one-hour delay.Buddy Stores
Figure 3-8 Buddy Stores Screen
![Buddy Stores Screen Buddy Stores Screen](img/con_buddystores.png)
The Buddy Stores screen allows the store user to define stores that they normally transfer items to, in other words the store's "buddy". Each store can define their own list of buddy stores. Buddy stores presents a shortened list of stores to select from when creating a transfer/transfer shipment. You can still transfer items to stores that are not buddies; a buddy is simply a short list for ease of use.
The Buddy Stores screen is accessed by selecting Admin / Configuration / Buddy Store.
The list of stores to select from will be all stores for the same transfer zone as your store or no transfer zone. If your store does not have a transfer zone, then all stores will be displayed. Select the desired stores to move over to the buddy stores block to become buddy stores. It is not necessary to set up buddy stores.
Auto Receive Stores
Figure 3-9 Auto Receive Stores Screen
![Auto Receive Stores Screen Auto Receive Stores Screen](img/con_autorecstores.png)
The Auto Receive Stores screen allows you to select those stores to Auto-Receive transfer shipments from. Each store can define their own list of auto receive stores. If a store is defined as an auto receive store, the stock on hand of the receiving store is automatically adjusted as soon as the defined auto receive store dispatches the transfer. The receiving store will not be able to receive exceptions, or record damages to the transfer.
The Auto Receive Stores screen is accessed by selecting Admin / Configuration / Auto Receive Store.
Note:
In addition to this selection, the Auto Receive admin setting needs to be setup.
The list of stores to select from will be all stores for the same transfer zone as your store or no transfer zone. If your store does not have a transfer zone, then all stores will be displayed. Select the desired stores to move over to the auto receive stores block to become an auto receive store.
SIOCS Managed Stores
Figure 3-10 SIOCS Managed Stores Screen
![SIOCS Managed Stores Screen SIOCS Managed Stores Screen](img/con_managedstores.png)
The SIOCS Managed Stores screen allows you to select those stores that are using SIOCS for inventory management. The screen is accessed by selecting Admin/ Configuration/ SIOCS Managed Stores.
Upon initial install all stores will be defaulted to Assigned (selected) which means that they are SIOCS Managed. When a new store comes into SIOCS it too will default to assigned / SIOCS Managed. If a store is not using SIOCS, then it would need to be unassigned (un-selected).
The following areas are impacted for NON SIOCS Managed stores:
-
Users for NON SIOCS Managed stores will only have access to Admin screens in EICS, look ups, and view only access to transactions.
-
Messages will not be published out of SIOCS for NON SIOCS Managed stores.
-
Item Lookup Stock Locator will display stock only for SIOCS Managed Stores.
-
Product Group Schedules can only be scheduled for SIOCS Managed Stores.
In the SIOCS Managed Stores UI of the desktop (above), if a store goes from SIOCS Managed to NON SIOCS Managed, and there are open product group schedules for this store, the user will be prompted upon saving to delete the store(s) from the Product Group Schedule.
-
System will check system admin, Enable Inbound Transaction Integration for NON SIOCS Managed stores.
-
Yes - SIOCS will subscribe to all RIB messages.
-
No - subscriptions to RIB messages for transactions will only occur for stores that are marked as SIOCS Managed.
-
Those messages that are for NON SIOCS managed stores will not be subscribed too, and the messages will be silently dropped by the subscriber.
-
This is not applicable to Web services, except for the POS Transaction Web Service which will check for NON SIOCS managed stores.
-
This is not applicable for Foundation Data.
-
-
Details around Transfers: When dropping messages, SIOCS drops all transfer create messages if a non-SIOCS store is referenced.
This is for multiple reasons:
-
Shipping records from non-SIOCS managed stores do not flow into SIOCS, so a transfer would never be able to get completed, unless the retailer ships through a W-S simulating the shipment.
-
It would be very difficult for data migration when going live to exclude SIOCS transfers with non-SIOCS managed stores if a SIOCS managed store is involved. This is due to the issue that a transfer document is shared by both locations.
Retailers will need to leverage supply network and transfer zones to prevent these transfers from being created with the SIOCS managed stores.
-
-
-
The following batch modules will check system admin, Enable Inbound Transaction Integration for NON SIOCS Managed stores.
-
Yes – the batch will process the same for SIOCS and non SIOCS managed stores
-
‘No’ – non SIOCS managed stores will not be processed in the batch.
-
Third Party RFID File Import
-
POS Transaction Import
-
RESA Sales Audit Import
-
Inventory Export
-
-
Store Shipping Network
Figure 3-11 Store Shipping Network
![Store Shipping Network Store Shipping Network](img/con_storeshipnet.png)
The Store Shipping Network screen is an admin screen that enables the user to set up a shipping network for a store(s). That is, the list of stores that a store can ship to and the list of stores that a store cannot ship to. For example, if a list of stores gets excluded from the shipping network for Store A, those stores cannot be a destination store for Transfer documents and Transfers shipments originating from Store A, except for the transfers initiated by the Merchandising system.
The screen can be accessed through Admin/Configuration/Store Shipping Network. The user must have Access Store Shipping Network permission to access this screen.
Figure 3-12 Select Store Popup
![Select Store Popup Select Store Popup](img/con_storeshippopup.png)
With the Select Stores popup, user can set up excluded stores for more than one store at a time. User can also override the existing excluded stores setup if needed.
Carrier
Figure 3-13 Carriers Screen
![Carriers Screen Carriers Screen](img/con_carrier.png)
The Carriers screen is an admin screen in the desktop application for you to setup and maintain the Carrier data. This screen is accessed by selecting the Carrier option from the Admin/ Configuration menu.
The system has a default Carrier record 'Other' under the manifest type 'Other'.
Carrier codes that are marked as system cannot be deleted.
The data created is available on the BOL screens when the Carrier Type of Third Party is selected.
This information should be coordinated with the Order Management System and / or manifest system.
Carrier Service
Figure 3-14 Carrier Services Screen
![Carrier Services Screen Carrier Services Screen](img/con_carrierservice.png)
The Carrier Services screen is an admin screen in the desktop application to setup and maintain the Carrier Services data. This screen is accessed by selecting the Carrier Services option from the Admin/Configuration menu.
The system has a default Carrier Service record 'Other' under the 'Other' carrier.
Carrier Service codes that are marked as system cannot be deleted.
Capture the Average delivery days the carrier takes to deliver, indicate whether weight is required, whether container size is required, and indicate a carrier service as a default service when creating a carrier service record in the system.
This information should be coordinated with the Order Management System and / or manifest system.
Package Size
Figure 3-15 Package Size Screen
![Package Size Screen Package Size Screen](img/con_package.png)
The Package Sizes screen is used to setup and maintain Package dimensions for all shipments to supplier, finisher, warehouse, and store for the entire system.
Package Size is used within:
-
RTV Shipment and Transfer Shipment
-
Container Info and Edit Container
-
-
Customer Order Deliveries
-
BOL Info and Edit Delivery
-
The Package Size dialog is accessed via the menu: Admin / Configuration / Package Size. Since package sizes are very specific to the retailer, there will not be an initial default of package sizes on install. Package Sizes can be created, edited, and deleted. Values include description, height, widths, length, and Unit of Measure.
Extended Attributes
GS1 extended attributes allow users to capture manually or automatically using a GS1 data bar values at the item transaction level. This for example allows the capture of an expiration date during delivery. Only physical item dialogues allow this manual or automatic capture:
-
Inventory adjustments
-
Stock counts
-
Shipping / receiving (DSD, RTV, transfers customer orders)
Retailers have the ability to change the standard name of the GS1 attribute and define up to 10 attributes by subclass that should be captured.
Setup Extended Attributes
Figure 3-16 Setup Extended Attributes Screen
![Setup Extended Attributes Screen Setup Extended Attributes Screen](img/con_setupextatt.png)
The Setup Extended Attributes screen will be pre-populated with all the current GS1 Application Identifiers and enables the user to view and edit Name, Type and Description of the extended attributes, depending on the business needs for the entire system. The user must have appropriate permission to access the screen and edit extended attributes.
Assign Extended Attributes
Figure 3-17 Assign Extended Attributes Screen
![Assign Extended Attributes Screen Assign Extended Attributes Screen](img/con_assignextattscreen.png)
This screen lists the assignments made for the various sub-classes and their display order in the transactions. The assignment made here will be applicable to the stores selected in the select store list. All extended attributes for the current store will replace those of the selected stores. The user must have appropriate permissions to access the screen.
Figure 3-18 Assign Extended Attributes Popup
![Assign Extended Attributes Popup Assign Extended Attributes Popup](img/con_assignextatt.png)
The Assign Extended Attributes popup enables the user to assign the extended attributes to a department/class/sub-class hierarchy and identify the order in which they will be displayed in the data entry screens in the transactions.