8 Configuration
This chapter describes how you can configure functionality usage.
Configuration can be achieved by adjusting:
System Admin Parameters
Table 8-1 System Admin Parameters
Option | Description | Default Value | Topic | Type |
---|---|---|---|---|
Allow Non-Range Item |
Values: Yes/No This parameter is to determine to give stores the ability to add non ranged items to functional areas in the application. |
Yes |
Admin |
Boolean |
Allow Item Lookup for Non-Ranged Items |
Values: Yes/No Yes:user can look up non-ranged items in item lookup. This is the case even if the system is configured to not allow for non-ranged items, Allow Non-Ranged items = 'No' |
Yes |
Admin |
Boolean |
Auto ranging of items for U&A Stock Counts |
Values: Allow auto ranging items, Allow auto ranging UINs, Allow Auto ranging items & UINs and Not Allowed. Allow auto ranging items: This setting will allow auto ranging for items but not UINs. Allow auto ranging UINs:This setting will allow auto ranging for UINs but not Items. Allow Auto ranging items & UINs: This allows auto ranging for items and UINs. Only if item is previously ranged, UIN will be allowed to range. Not Allowed : With this setting, the system will allow neither. |
Allow Auto ranging items & UINs |
Admin |
Integer |
Barcode Scan/Entry Log - Receiving |
Values: Yes/No Yes: Captures, on the mobile, all container and item scans or manual entries by user, location, and time at the point of receiving deliveries. Containers are captured in the quick receiving dialog when item level is captured in the Item Receiving function of the Container Summary for DSD and Transfer Receiving. No: Does not capture any container or item information in the mobile receiving dialogs. |
Yes |
Admin |
Boolean |
Default UOM |
Values: Standard UOM / Cases Standard UOM the system will default to the standard UOM until the UOM is changed. Cases the system will default to cases until the UOM is changed. |
2 |
Admin |
Integer |
Disable Custom Flexible Attributes |
Values: Yes/No Yes: CFAs are disabled on MAF No: CFAs will be available on MAF |
Yes |
Admin |
Boolean |
Disable Pack Size |
Values: Yes/No Yes: Pack size is disabled and cannot be changed. No: Pack size is editable and can be updated. |
No |
Admin |
Boolean |
Enable Sub-buckets |
Values: Yes/No Yes: Sub-buckets will be used throughout the application. No: Sub-buckets will not be used in the application. |
Yes |
Admin |
Boolean |
Filter Merchandise Hierarchy |
Values: Yes/No Yes: Hierarchies / departments will be filtered to those that are for the user's permissions. No: Hierarchies / departments will not be filtered for the user's permissions, all will be available. |
No |
Admin |
Boolean |
File Transfer Service Bucket Name |
The object storage bucket name for file transfer service. |
- |
Admin |
String |
File transfer storage archives prefix |
Object storage archives prefix, |
Archives |
Admin |
String |
File transfer storage exports prefix |
Object storage exports prefix. |
Exports |
Admin |
String |
File transfer storage imports prefix |
Object storage imports prefix. |
Imports |
Admin |
String |
File transfer storage rejects prefix |
Object storage rejects prefix. |
Rejects |
Admin |
String |
Initial Data Load Display Summary Count |
Values: Yes/No Yes: The record count in the Module List table on the Initial Data Load screen is displayed. For large volume tables, loading the count summary might take longer time on loading the UI. No: The record count in the Module List table on the Initial Data Load screen will not be displayed. |
No |
Admin |
Boolean |
Initial Data Load Seed |
Values: Yes / No Yes: It indicates that Initial Data Load screen will be used for initial data seeding from MFCS to SIOCS (where they reside in the same pluggable database) and also in case of Standalone SIOCS (through file imports). No: The Initial Data Load screen will not be used for initial data seeding. |
No |
Admin |
Boolean |
Initial Data Load Seed Foundation Data |
Values: Yes/No Yes: Foundation Data Groups (Item, Miscellaneous, Supplier and Warehouse) will be available for seeding. No: Foundation Data Groups will not be available for seeding. |
Yes |
Admin |
Boolean |
Initial Data Load Seed Store Data |
Values: Yes/No Yes: Store Data will be available for data seeding. No: Store Data will not be available for data seeding. |
Yes |
Admin |
Boolean |
Item Description Translation Preference |
Values: System/User System: The Item description displayed in the application would be the item description from STORE_ITEM table (store description) or from ITEM table if the item is not ranged. This is existing functionality. User: The Item description will be displayed in the user's preferred language if translation is available. If the translation is not available in the user's preferred language, then the item description will be displayed in the store locale language if it is available. If the translation is not available in the store locale language, then the item description displayed will be item description from STORE_ITEM (store description). If the item is a non ranged item, then the item description displayed will be from the ITEM table. |
System |
Admin |
Boolean |
Maintain RFID History |
Values: Yes/No Yes: will create history records in the history table for every transaction occurred for the RFID Tag. No: will not create the history records however the integration with the RFID solution and RFID tag tracking could still be on. |
Yes |
Admin |
Boolean |
Maximum number of Tickets to use synchronous call |
This is to determine the integration method with the printing service for the ticket printing based on the number of tickets set. 0 indicates to use the MPS staging process only. Regardless of mobile or desktop, SIOCS will send the ticket to the MPS table for processing. This is needed to keep supporting live customers who have currently only deployed the staged method. >0: If the value set here is greater than zero, the system will do a direct synchronous call to the printer service when the number of tickets is equal or less than the number of tickets set in this parameter. Example: If the value set here is 5 and the number of tickets submitted to print is anything from 1 to 5, the system will do a direct synchronous call to the printer service bypassing the MPS staging process. If the number of tickets printed is above five, it will be MPS staged process. This behavior is regardless of mobile or desktop application. |
0 |
Admin |
Integer |
Publish available inventory for customer order enabled stores |
Parameter to publish the inventory updates (COINVAVAIL message) to external system (OB/OMS) for customer order enabled stores. |
No |
Admin |
Boolean |
Server Repave Pending Continue |
The batch process checks if the server is about to be repaved for batch unit of work, if this configuration value is set to true, the batch will continue to process next unit of work; if the value is set to false, the batch will skip process the next unit of work, the remaining un-processed works will be marked as stopped and exit the batch process. |
Yes |
Admin |
Boolean |
Shopfloor Out of Stock Items Critical Percentage |
Values: 0.01 - 100% If the percentage of out of stock items on shop floor to total items is greater than this percentage, then there will be an '!' alert with the number of items out of stock on the tile report. |
0.01% |
Admin |
Integer |
Stop Job On Over Max Duration |
Internal batch scheduler configuration reserved for future use, currently not used. |
No |
Admin |
Boolean |
System Code |
Code identifying the application for integration with an external system. This often is a company ID. This is only used for outbound integration. |
INV |
Admin |
String |
Audit Direct Store Delivery |
Audit Records are log of activities and usage information in the system. This parameter is to determine whether activity records for actions (confirm/submit/update and so on) performed on vendor delivery and vendor delivery carton will be created. |
Yes |
Audit |
Boolean |
Audit Publish Message |
Audit Records are log of activities and usage information in the system. This parameter is to determine whether activity records for outbound messages will be created. |
Yes |
Audit |
Boolean |
Audit Receive Message |
Audit Records are log of activities and usage information in the system. This parameter is to determine whether activity records for inbound messages will be created. |
Yes |
Audit |
Boolean |
Audit RTV Update |
Values: Yes/No Yes: Enables activity logging for rtv request and rtv shipments. No: Disables activity logging for rtv request and rtv shipments. |
Yes |
Audit |
Boolean |
Audit Security |
Values: Yes/No Yes: Enables activity logging for security events. It includes login success/failure, security management changes (roles, user assignments, and so on). No: Disables activity logging for security events. |
Yes |
Audit |
Boolean |
Audit Stock Count Completed |
Audit Records are log of activities and usage information in the system. This parameter is to determine whether activity records will be created for count or recount complete for stock count child. |
Yes |
Audit |
Boolean |
Audit Transfer Dispatch |
Values: Yes/No Yes: Enables activity logging for transfer shipments. No: Disables activity logging for transfer shipments. |
Yes |
Audit |
Boolean |
Audit Transfer Receiving |
Values: Yes/No Yes: Enables activity logging for transfer receiving. No: Disables activity logging for transfer receiving. |
Yes |
Audit |
Boolean |
Audit Transfer Update |
Values: Yes/No Yes: Enables activity logging for transfer requests. No: Disables activity logging for transfer requests. |
Yes |
Audit |
Boolean |
Batch max files per job run |
Batch max files per job run. |
20 |
Batch |
Integer |
Batch Maximum Threads |
Gives the maximum number of batch partitions for a batch to run. |
5 |
Batch |
Integer |
Batch Scheduler Execution Interval |
Gives the batch scheduler execution delay interval duration to throttle batch execution calls. |
300 |
Batch |
Integer |
Compress inventory extract files into zip file |
This system parameter indicate whether to compress the inventory extract files into zip. When the compress is true, then the export files will be placed into zip (each zip file will be limited to max 50 MB), multiple zip files maybe generated with the naming conversion as below: zipFileName = filePrefix + "_" + partNum + "_" + <datetime> + “.zip” |
No |
Batch |
Boolean |
Days to Hold Archived and Rejected Files |
Gives the days to hold rejected and archived batch files before deleting them from the batch directory. |
30 |
Batch |
Integer |
Initial Data Load Chunk Limit |
The commit frequency in number of records during Initial Data Seeding process. |
1000 |
Batch |
Integer |
Initial Data Load Chunk Log Limit |
The number of errors allowed before terminating the Initial Data Seeding process. |
15 |
Batch |
Integer |
Inventory Extract Omnichannel Store only |
Values: Yes/No Yes: Among the SIOCS Managed Stores, the Inventory Extract Batch would consider only the Omnichannel stores to extract the inventory data of the items. |
No |
Batch |
Boolean |
Maximum Job Instances Per Scheduler Execution |
Gives the maximum number of jobs allowed per run of the scheduler. |
100 |
Batch |
Integer |
Maximum Processing Hours For Scheduled Job |
Determines the maximum processing time for a batch job. After this time, the batch schedule record is updated to failed status. |
5 |
Batch |
Integer |
Merge Data During Initial Data Load |
Values: Yes/No Yes: Data from the Standalone IDLS staging tables will be merged into the SIOCS master tables. No: Data from the Standalone IDLS staging tables will be inserted into the SIOCS master tables. |
Yes |
Batch |
Boolean |
Pricing Max Events Per Job Run |
Indicating the maximum pricing events to poll from pricing event Integration Change Log (ICL) table per Item Price ICL Import batch run. |
5 |
Batch |
Integer |
Procedure Log Purging Info Enabled |
Determines whether the procedure log purging info is enabled. |
Yes |
Batch |
Boolean |
Search Limit Default for Batch Job Days |
Gives the default number of days in past for batch job records to be displayed on Batch Job Admin screen on EICS. |
7 |
Batch |
Integer |
Days to Hold Areas |
Values: 0-30 Purge all areas that are greater than or equal today's date minus the days to hold value. |
30 |
Clean Up |
Integer |
Days to Hold Audit Records |
Values 45-120 Audit Records are log of activities and usage information in the system. This parameter is to determine the number of days to hold the audit records. The batch will delete all records where the create date is less than or equal to current date minus the days to hold. |
45 |
Clean Up |
Integer |
Days To Hold Batch Logs |
Values: 0-30 Delete all logs where the log date is less than or equal to the current date minus the days to hold for any records. |
30 |
Clean Up |
Integer |
Days to Hold Closed Warehouse Containers |
Values : 0-999 This parameter holds the number of days after which the closed warehouse containers and associated deliveries will be deleted. |
30 |
Clean Up |
Integer |
Days to Hold Completed Inventory Adjustments |
Values: 0-120 Delete records in 'Complete' Status where the inventory complete date is less than or equal to the current date minus the days to hold. |
120 |
Clean Up |
Integer |
Days to Hold Completed Purchase Orders |
Values: 0-120 Purge all records in 'Closed' status after 'x' number of days defined by user, where the complete date (the date of when all items were received on the order) is less than or equal to the current date minus the days to hold. |
120 |
Clean Up |
Integer |
Days to Hold Completed Staging Records |
Values: 1-3 Delete all records that have been processed successfully or deleted where the update date is less than or equal to the current date minus the days to hold for any records. |
3 |
Clean Up |
Integer |
Days to Hold Completed Stock Counts |
Values: 0-90 Purges any records 'x' days after the last stock count event has occurred. In other words, when the schedule date is less than or equal to the current date the system will subtract the days to hold completed stock counts from the date and delete when this date is reached. The purging will occur when the stock count has a status of 'Complete'. |
90 |
Clean Up |
Integer |
Days to Hold Completed UINs |
Values: 0-30 Indicates how long completed UINs are kept in the system. Completed UINs are defined as any UIN that is in one of the following statuses: Sold Shipped to Warehouse Shipped to Vendor Shipped to Finisher Removed from Inventory Customer Fulfilled |
30 |
Clean Up |
Integer |
Days to Hold Customer Orders |
Values: 0-30 Indicates the number of days that Cancelled, and Fulfilled Customer Orders will be held in the system before being purged. |
30 |
Clean Up |
Integer |
Days to Hold Expired item price |
Values: 0-90 Indicates the number of days to hold the expired price changes in the system before being purged. |
90 |
Clean Up |
Integer |
Days to Hold Expired User Roles |
Values: 0-30 This will determine the number of days after which the expired roles will be purged from the system |
30 |
Clean Up |
Integer |
Days to Hold In Progress Ad Hoc Stock Counts |
Values: 0-7 Ad hoc stock counts that are In Progress will be deleted through the purge process. Any ad hoc count with a creation date/time stamp older than this parameter value will be deleted. For example, the default value of 1 would delete all in progress counts more than 24 hours old when the batch is run. |
1 |
Clean Up |
Integer |
Days to Hold Item Basket |
Values: 1-30 This will determine the number of days to hold 'Canceled' and 'Completed' Item Baskets. |
30 |
Clean Up |
Integer |
Days to Hold Locking Records |
Values: 0-3 Locking records will be purged through a batch process and the batch process will account for all locking activity across all functional areas. This is to determine the number of days to hold the locking records. The batch will delete all locking behavior around all functional areas where the lock date is less than or equal to the current business date minus the days to hold. |
1 |
Clean Up |
Integer |
Days to Hold Notifications |
Values: 0-14 This parameter is used to purge notifications which are greater than or equal to this value. |
3 |
Clean Up |
Integer |
Days to Hold Price Change Worksheet Records |
Values: 0-30 Records in the price change staging / worksheet table will be purged based upon this parameter. |
30 |
Clean Up |
Integer |
Days to Hold Price History |
Values: 0-90 The 'Days to Hold Price History' parameter allows the user to keep records beyond the 4 most recent historical prices for 'x' number of days if desired. Prices in the future will not be deleted and will not be included as part of the four historical prices that will remain on the database. |
90 |
Clean Up |
Integer |
Days to Hold Received Shipment Records |
Values: 0 - 30 Purge all PO and DSD Delivery records in ‘Received’ and ‘Cancelled’ status after ‘x’ number of days defined by user, where the inventory completed date is less than the current date minus the days to hold. There is a receipt record that will be deleted along with any record that is in ‘Received’ status. |
30 |
Clean Up |
Integer |
Days to Hold Recently Edited Transactions |
Values: 0-15 Purge all Recently Edited transactions on mobile where the post date is less than or equal to the current date minus the days to hold. |
7 |
Clean Up |
Integer |
Days to Hold Related Items |
Values: 0-10 To determine when a related item should be purged. Program will purge Related items that have an end date in the past. The system will purge the related items after 'x' number of days defined by user, where the related items End Date is less than the current date minus the days to hold. |
0 |
Clean Up |
Integer |
Days to Hold Resolved UIN Exceptions |
Values: 0-30 Indicates how long resolved UIN exceptions are kept in the system. The date the exception was resolved is the date the system uses to determine if the exception is ready to be purged. |
30 |
Clean Up |
Integer |
Days to Hold RFID |
Values: 0-7 Indicates how long the RFID data that are not present in the store is kept in the system. |
3 |
Clean Up |
Integer |
Days to Hold RFID History |
Values: 0-120 This parameter will purge RFID history that is greater than or equal today's date minus the days to hold value. |
120 |
Clean Up |
Integer |
Days to Hold RTV |
Values: 0-90 This parameter will decide that which RTV documents and Shipments need to be purged. The value in this parameter will decide the number of days after a RTV document or shipment gets into cancelled or completed status for document and cancelled or shipped for shipment. |
90 |
Clean Up |
Integer |
Days to Hold Sales Posting |
Values: 1-30 The audit trail for the sales posting will be purged on a periodic basis based on the specified parameter. The system will purge all records from the database after the configurable number of days, where the processed date is less than or equal to current date minus the days to hold |
30 |
Clean Up |
Integer |
Days to Hold Scan Lists |
Values: 0-60 Purge any records in 'Complete' or 'Cancelled' status where the post date is less than or equal to the current date minus the days to hold |
60 |
Clean Up |
Integer |
Days To Hold SFTP Log File |
Indicating number of days to keep the sFTP log files before the log files to be deleted. |
7 |
Clean Up |
Integer |
Days to Hold Shelf Adjustment Lists |
Values: 0-30 Purge any records in 'Complete' or 'Cancelled' status where the post date is less than or equal to the current date minus the days to hold |
30 |
Clean Up |
Integer |
Days to Hold Shelf Replenishments |
Values: 0-3 Purge any records in 'Complete' or 'Cancelled' status where the post date is less than or equal to the current date minus the days to hold. |
1 |
Clean Up |
Integer |
Days to Hold Store Orders |
Values: 0-60 Purge any records in 'Approved' or 'Canceled' status where the post date is less than or equal to the current date minus the days to hold. |
60 |
Clean Up |
Integer |
Days to Hold Temporary UINs |
Values: 0-10 To indicate how long the temporary UINs must stay in the system. |
10 |
Clean Up |
Integer |
Days to Hold Ticket History |
Values: 1-30 To indicate how long the tickets that printed and persisted in the history table must stay. |
30 |
Clean Up |
Integer |
Days to Hold Transaction History |
Values: 0-30 Determines the number of days after which store_item_stock_history records can be purged. |
30 |
Clean Up |
Integer |
Days to Hold Transfer Documents |
Values: 0 -120 This parameter would decide the number of days after which a Transfer document, shipments, and deliveries can be purged. |
30 |
Clean Up |
Integer |
Days to Hold UIN Audit Information |
Values: 0 -120 Indicates how long UIN audit information is kept in the system. Audit information can be purged for a UIN within the system. The date the audit transaction was captured is used to determine if the record needs to be purged. |
120 |
Clean Up |
Integer |
Days To Hold Unexecuted Stock Counts |
Range: 0 - 90 Gives the number of days after which an unexecuted stock count can be deleted via a batch |
30 |
Cleanup |
Integer |
Display Item Image For Container Lookup - Operations |
Values: Yes/No Yes: Indicates item image will be displayed in Container Lookup on EICS. No: Image will not be displayed in Container Lookup on EICS. |
No |
Container Lookup |
Boolean |
Customer Order Fulfillment Restriction |
Values: Restricted/Transaction Controlled/Line ControlledTransaction Controlled: The Allow Partial Delivery indicator that comes in on the customer order will be used as it was sent. Restricted: The Allow Partial Delivery Indicator will be updated to 'No' on the Customer Order or Transfer Request upon coming into the system.- Customer Order Deliveries and Transfer Request/Shipment will validate the Allow Partial Delivery indicator as usual, however, it will be set to 'No' and force the user to have a full delivery (except for a user override in customer order deliveries).- Customer Order Picking: When creating a pick, the user will not be able to create the pick if there is not enough available to pick. When confirming a pick, everything must be picked on the customer order.- Reverse Picking: when creating a reverse pick, the user must reverse pick everything that was picked. Line Controlled: If an item is getting delivered, it must be delivered in its entirety- Customer Order Deliveries and Transfer Request/Shipment will validate the Allow Partial Delivery indicator as usual. When Allow Partial Delivery indicator is set to 'Yes', the system will force the user to approve/ship an item fully, if it is getting approved/shipped. When Allow Partial Delivery indicator is 'No', the system will force the user to ship the full order to the customer (except for a user override in customer order deliveries). In case the user has override permission, the customer order can be shipped partially however an item getting shipped should be shipped fully.- Customer Order Picking: When creating a pick, the user will not be able to create the pick if there is not enough available to pick at least one item. When confirming a pick, if an item is getting picked, it must be picked fully. |
Transaction Controlled |
Customer Order |
Integer |
Customer Order Pickup Notification |
Values: Yes/No Yes: A new notification alert is generated that a customer is ready to pickup their order. No: A notification is not generated. |
No |
Customer Order |
Boolean |
Customer Order Receipt Notification |
Values: Yes/No Yes: A receipt notification will be generated when a customer order related transfer receipt or Direct Store Delivery (DSD) has been confirmed. No: The notification will not be generated. |
No |
Customer Order |
Boolean |
Customer Order Reauthorization Notification |
Values: Yes/No Yes: User will get a notification if a customer order has been reauthorized successfully, that is, when SIOCS successfully consumes and processes a RIB message from OBCS that a customer order has been released from on hold, a notification will be sent to the user. No: User will not get a notification if a customer order has been reauthorized successfully. |
No |
Customer Order |
Boolean |
Customer Order Tracking ID Required |
Values: Yes/No Yes: If the store parameter 'Manifest Customer Order Deliveries' is set to No, the Tracking ID must be captured before dispatching the Customer Order Delivery. If 'Manifest Customer Order Deliveries' is set to Yes, then it is not required. No: Capturing Tracking ID becomes optional while dispatching the Customer Order Delivery. |
No |
Customer Order |
Boolean |
Display Item Image for Customer Order Delivery |
Values: Yes/No Yes: This parameter indicates that item image will be displayed in Customer Order Deliveries. No: Images will not be displayed in Customer Order Deliveries |
No |
Customer Order |
Boolean |
Display Item Image for Customer Order Picking |
Values: Yes/No Yes: This parameter indicates that item image will be displayed in Customer Order Picking. No: Images will not be displayed in Customer Order Picking. |
No |
Customer Order |
Boolean |
Display Item Image for Customer Order Reverse Picking |
Values: Yes/No Yes: This parameter indicates that item image will be displayed in Customer Order Reverse Picking. No: Images will not be displayed in Customer Order Reverse Picking. |
No |
Customer Order |
Boolean |
Display Item Image for Customer Orders |
Values: Yes/No Yes: Indicates item image will be displayed in Customer Orders. No: Image will not be displayed in Customer Orders. |
No |
Customer Order |
Boolean |
Minutes To Hold New Customer Order Before Sending Notification |
Values: 0-999 This system parameter indicates the time interval in minutes to send a follow-up message to a store associated after a customer order (web order) has arrived, but no user has accessed the customer order. |
5 |
Customer Order |
Integer |
Minutes To Hold Open Customer Order Pick Before Sending Notification |
Values: 0-999 This system parameter dictates the time interval in minutes to send a follow-up message to a store associate after a pick list has been created but no one has started the pick list. |
15 |
Customer Order |
Integer |
New Customer Order Notification |
Values: Yes/No Yes: This parameter generates a notification for a new cross channel (web order) customer order. No: No notification is generated. |
No |
Customer Order |
Boolean |
New Customer Order Reverse Pick Notification |
Values: Yes/No Yes: A notification alert is generated when a new system generated reverse pick comes into the system. No: A notification is not generated upon getting a new system generated reverse pick. |
No |
Customer Order |
Boolean |
Always Send DSD Receipt Cost |
Values: Yes/No Yes: When the receipt is published, the unit cost will be sent if there is not an override cost. No: When the receipt is published, only the override cost will be sent if it exists. |
No |
DSD Receiving |
Boolean |
Display Unit Cost for Direct Deliveries |
Values: Yes/No Yes: Display Unit Cost and allow editing when receiving. If On, the system displays the original cost and allows entering the new cost for the on-the-fly and Dex/Nex deliveries. For the delivery with PO and ASN, it displays the unit cost. Display the Unit Cost on the Direct Delivery Report when printing. No: Do not display this data to the user in the DSD Receiving Containers screen. Do not display the unit cost on the Direct Delivery Report. If No, the system does not display the unit cost and does not allow editing or entering new cost. |
Yes |
DSD Receiving |
Boolean |
Displays Item Image for DSD Receiving |
Values: Yes/No Yes: This parameter indicates whether the item image will be displayed in Container Items and Item detail screens. No: Image will not be displayed in that functional area. |
No |
DSD Receiving |
Boolean |
Displays Item Image for Purchase Order |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in Purchase Order Items screen. No: Image will not be displayed in that functional area. |
No |
DSD Receiving |
Boolean |
DSD Receiving Preferred Currency |
Values: Store Currency/Supplier Currency This parameter will default the store or supplier currency to newly created POs depending on preference. |
Store Currency |
DSD Receiving |
Integer |
Ignore the Supplier DSD indicator to create a PO on the fly |
Values: Yes/No Allows the system to ignore the supplier level indicator when creating a PO in the system. Yes: The system ignores the supplier level flag and will always allow stores to create purchase orders for any supplier based on the receipt. No: The system will verify creating a purchase order on the fly is allowed based on the supplier level flag. |
Yes |
DSD Receiving |
Boolean |
Number of days received direct deliveries can be adjusted |
Values: 0-999 0: no adjustment 1: allowed to adjust until the end of today 2: allowed to adjust until the end of tomorrow X: allowed to adjust until X number of days starting with today as day 1 This parameter specifies the number of days received direct deliveries can be reopened and adjusted. If a direct delivery falls within the number of days, the system allows to adjust the received delivery. The user will be allowed to edit values and confirm the delivery. |
0 |
DSD Receiving |
Integer |
Over Received Quantity Notification |
Values: Yes/No This parameter will generate a notification when more than the expected quantity has been received and the store parameter Direct Delivery Auto Remove Over Received Quantity is set to yes. |
Yes |
DSD Receiving |
Boolean |
Days Beyond PO Not After Date |
This parameter is used to determine the Purchase Orders returned in the deliveries on Item Detail as well as calculating the On Order Qty. 1. Planned Deliveries Ordered Qty needs to be taking the Not After Date into account. Purchase Order – only include those PO’s where Not After Date >= Today + Days Beyond PO Not After Date Transfer – only include those transfers where Not After Date >= Today 2. Deliveries – Only display deliveries where: Purchase Order – only include those PO’s where Not After Date >= Today + Days Beyond PO Not After Date Transfer – only include those transfers where Not After Date >= Today |
50 |
DSD Receiving |
Integer |
Display Item Image for Inventory Adjustments - Execution |
Values: Yes/No Yes: The item image is displayed within Inventory Adjustments in SOCS. No: The item image is not displayed in Inventory Adjustments. |
No |
Inventory Adjustment |
Boolean |
Display Item Image for Inventory Adjustments - Operations |
Values: Yes/No Yes: The item image is displayed within Inventory Adjustments in EICS. No: The item image is not displayed in Inventory Adjustments. |
No |
Inventory Adjustment |
Boolean |
Display Item Image for Item Baskets - Execution |
Values: Yes/No Yes: The item image is displayed within Item Basket on the mobile. No: The item image is not displayed in Item Basket on the mobile. |
No |
Item Basket |
Boolean |
Display Item Image for Item Baskets - Operations |
Values: Yes/No Yes: The item image is displayed within Item Basket on the desktop. No: The item image is not displayed in Item Basket on the desktop. |
No |
Item Basket |
Boolean |
Display Item Image for Item Lookup - Execution |
Values: Yes/No Yes: The item image is displayed within Item Lookup on SOCS. No: The item image is not displayed in Item Lookup. |
No |
Item Lookup |
Boolean |
Display Item Image for Item Lookup - Operations |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in Item Lookup in EICS. It is in the list and the details. No: Image will not be displayed in Item Lookup. |
No |
Item Lookup |
Boolean |
Display Price in Search Result - Operations |
Values: Yes/No This parameter decides whether Price and Pricing Type will be displayed in the search results in the Item Lookup screen in the desktop application. Yes: Price and Price Type will be displayed in the search results. No: Price and Price Type will not be displayed in the search results. |
Yes |
Item Lookup |
Boolean |
Display SOH/Price in Search Result - Execution |
Values: Yes/No This parameter decides whether Price and Pricing Type will be displayed in the search results in the Item Lookup screen in the mobile application. Yes: Price and Price Type will be displayed in the search results. No: Price and Price Type will not be displayed in the search results. |
Yes |
Item Lookup |
Boolean |
Related Items Group by for Item Lookup - Execution |
This parameter is used to determine how to group related items together in item lookup on the mobile. This paramter is used on JET Mobile |
Diff 1 |
Item Lookup |
String |
Background Thread Count |
Gives the thread count for background tasks in SOCS. |
1 |
Mobile |
Integer |
Barcode Attribute Refresh Rate Milliseconds |
Determines the cache refresh rate for barcode attribute labels in milliseconds. |
3600000 |
Mobile |
Integer |
Configuration Refresh Rate Milliseconds |
Determines the cache refresh rate for system configurations, store configurations, batch scheduler and MPS work type in milliseconds. |
3600000 |
Mobile |
Integer |
Date Output Chinese China |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output Chinese Hong Kong |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output Chinese Taiwan |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output English Australia |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output English Canada |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output English India |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output English Ireland |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output English South Africa |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output English United Kingdom |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output English United States |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output French Belgium |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output French Canada |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output French France |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output French Luxembourg |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output French Switzerland |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output German Austria |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output German Germany |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output German Luxembourg |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output German Switzerland |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Italian Italy |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Japanese Japan |
This is to determine the date format based on the locale. |
yy-MM-dd |
Mobile |
String |
Date Output Korean South Korea |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output New Zealand |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Portuguese Brazil |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Portuguese Portugal |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Russian Russia |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Argentina |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Bolivia |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Chile |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Columbia |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Costa Rica |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Dominican Republic |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Ecuador |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish El Salvador |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Guatemala |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Honduras |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Mexico |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Nicaragua |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Panama |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Paraguay |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Peru |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Puerto Rico |
This is to determine the date format based on the locale. |
MM-dd-yy |
Mobile |
String |
Date Output Spanish Spain |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Uruguay |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Date Output Spanish Venezuela |
This is to determine the date format based on the locale. |
dd-MM-yy |
Mobile |
String |
Display Images |
Values: Yes/No Yes - The Display Images user preference will be available No - The Display Images user preference will NOT be available. |
Yes |
Mobile |
Boolean |
Enable Device Camera Barcode Scan |
Used for enabling device camera for scanning on SOCS. |
No |
Mobile |
Boolean |
External Scanner Refresh Rate Milliseconds |
Determines the cache refresh rate for external scanner in milliseconds. |
3600000 |
Mobile |
Integer |
Inventory Adjustment Reason Refresh Rate Milliseconds |
Determines the cache refresh rate for inventory adjustment reason in milliseconds on SOCS. |
3600000 |
Mobile |
Integer |
Item Image Refresh Rate Milliseconds |
Determines the cache refresh rate for item image in milliseconds on SOCS. |
3600000 |
Mobile |
Integer |
Manual Quantity Entry Default Mode |
Values: Scan Mode/Override Scan Mode: The numeric entry popup on mobile will have its mode defaulted per the scan mode (as it has always done) Override: The numeric entry popup on mobile will have its mode always defaulted to override, and it will not look at the scan mode. |
Scan Mode |
Mobile |
Integer |
Non-Sellable Quantity Type Refresh Rate Milliseconds |
Determines the cache refresh rate for non-sellable quantity types in milliseconds on SOCS. |
3600000 |
Mobile |
Integer |
Notification Count Refresh Rate Milliseconds |
Determines the cache refresh rate for notifications in milliseconds on SOCS. |
300000 |
Mobile |
Integer |
RFID Zone Refresh Rate Milliseconds |
Determines the cache refresh rate for RFID zones in milliseconds in the system. |
3600000 |
Mobile |
Integer |
Scan Focus Item Detail |
Determines if sticky focus is enabled on SOCS screens. Yes: Focus will automatically be in the Scan field when on a screen with the scan bar. The system will retain focus in the scan bar field until an error arises or until the user/system moves focus to somewhere else.The keyboard will display on the mobile device while scanning/entering the scan bar field. This is because the system believes you are typing into the field.No: Focus will not stay in the scan bar. |
No |
Mobile |
Boolean |
Sound Error Enabled |
Determines if severe error sound will be played in case of severe errors on SOCS. |
Yes |
Mobile |
Boolean |
Sound Information Enabled |
Determines if information sound effect will be played on SOCS. |
Yes |
Mobile |
Boolean |
Sound Scan Enabled |
Determines if beep sound will be played on scan on SOCS. |
Yes |
Mobile |
Boolean |
Sound Warning Enabled |
Determines if a business error sound will be played on business errors on SOCS. |
Yes |
Mobile |
Boolean |
Store Printer Refresh Rate Milliseconds |
Determines the cache refresh rate for store printer in milliseconds on SOCS. |
3600000 |
Mobile |
Integer |
Store Refresh Rate Milliseconds |
Determines the cache refresh rate for notifications in milliseconds on EICS and SOCS. |
3600000 |
Mobile |
Integer |
Tablet Mode Screen Size |
Determines the screen size for tablet mode for SOCS. |
16,5 |
Mobile |
.Double |
UOM Conversion Refresh Rate Milliseconds |
Determines the cache refresh rate for UOM conversion in milliseconds |
3600000 |
Mobile |
Integer |
Vibration Enabled |
Determines if vibration is enabled on errors on SOCS. |
No |
Mobile |
Boolean |
MPS Enabled |
Determines if MPS is enabled which in turn determines if MPS work types can be enabled. |
Yes |
MPS |
Boolean |
MPS Increment Threads |
Determines the allowed thread increment factor for MPS work types. |
2 |
MPS |
Integer |
MPS Maximum Queue Age Seconds |
Determines the maximum seconds before MPS work queue needs to be refreshed. |
180 |
MPS |
Integer |
MPS Maximum Queue Size |
Determines the maximum size limit for generating MPS work queues. |
1000 |
MPS |
Integer |
MPS Maximum Threads |
Determines the maximum thread count for MPS work types. |
8 |
MPS |
Integer |
MPS Refresh Rate Seconds |
Determines the MPS work queue refresh rate after checking for the system parameter MPS Maximum Queue Age Seconds. If the MPS Maximum Queue Age Seconds has not exceeded, then this parameter is checked to determine if MPS work queue needs to be refreshed. |
15 |
MPS |
Integer |
Seconds to Check for Notifications |
Defines how many seconds the system will check for new notifications. This applies to any notification inserted into the system. |
300 |
Notification |
Integer |
Days to Hold Areas |
Values: 1-999 Purge all areas that are greater than or equal today's date minus the days to hold value. |
60 |
Clean Up |
Integer |
Days to Hold Audit Records |
Audit Records are log of activities and usage information in the system. This parameter is to determine the number of days to hold the audit records. The batch will delete all records where the create date is less than or equal to current date minus the days to hold. |
45 |
Clean Up |
Integer |
Display Item Image for RFID Locator |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the RFID Locator dialog in mobile application. No: The image will not be displayed. |
No |
RFID Locator |
Boolean |
Days to send Notification before not after date for return requests |
Values: 0-999 RTV requests generated in an external system sometimes require the RTV to be dispatched to supplier before a certain date. This option prompts the recipient of the e-mail the specified number of days before the not after date is reached, if the RTV was not dispatched. |
2 |
RTV |
Integer |
Displays Item Image for RTV Requests |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in that transaction. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
RTV |
Boolean |
DSD delivery supplier for RTV |
Values: Yes/No This indicator will check to see if the DSD allowed indicator needs to be set in addition to the return allowed values when creating a supplier return. Yes: If the “DSD delivery supplier for RTV” system option is set to ‘On’, then the system needs to check both the DSD indicator (Indicator on Supplier table which determines whether a supplier can create a new Purchase Order) and the return allowed indicator (also an indicator on the supplier table). No: If the “DSD delivery supplier for RTV” system option is set to ‘No’, then only the return allowed indicator needs to be validated for supplier returns. Note: Regardless of the indicator, the system should always be able to dispatch the RTV if it was created in an external system. |
Yes |
RTV |
Boolean |
RTV Unavailable Request Qty Notification |
Values: Yes/No This system parameter will generate notification when “Auto Approve RTV request” parameter is set to On and the request has unavailable quantity greater than the stock. |
Yes |
RTV |
Boolean |
Displays Item Image for RTV Shipment |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in that transaction. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
RTV Shipment |
Boolean |
Display Item Image for Replenishment Pick |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the replenishment pick. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
Shelf Replenishment |
Boolean |
Display Item Image for Scan List |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the scan list. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
Shelf Replenishment |
Boolean |
Display Item Image for Shelf Adjustment |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the shelf adjustment. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
Shelf Replenishment |
Boolean |
Auto Save number of items threshold |
This parameter is to determine the number of items after which the system must auto save the items counted. When “Unguided Stock Counts Automatic Save “is set to Yes, SOCS will look at the number of items counted, when it hits the number configured, the system will auto save all the counted values of the user and refresh. If the user saves themselves, the counter of scanned items will be set to 0 again. If the configured value is 1, the system will auto save every item. |
1 |
Stock Counts |
Integer |
Display Item Image for Stock Counts - Execution |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the stock counts. It is in the item list and the details of the transaction. No: The image will not be displayed. |
No |
Stock Counts |
Boolean |
Display Item Image for Stock Counts - Operations |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in the stock counts functionality in EICS. No: The image will not be displayed. |
No |
Stock Counts |
Boolean |
Enable Adhoc Stock Count Locking |
This parameter will determine whether a stock count can be locked or not from adding additional item. Yes - User will have the ability to lock an adhoc stock count. i.e., the user will not be able to add additional items after the initial import. No - User will be able to add any number of items until the adhoc stock is completed. Values: Yes/No |
No |
Stock Counts |
Boolean |
Stock Count Display Default Timeframe |
This parameter is to determine whether the system must prompt the user to select to whether it is performed before store open or after store close. |
No |
Stock Counts |
Boolean |
Stock Count Lockout Days |
Stock Count Lockout Days is used to determine when a Unit and Amount Stock Count can be generated. The system will take this value plus the system date and enforce a start date of the schedule to be greater than or equal to that date. Note: If the system is integrated with the merchandising system, the values in the two systems must be the same. |
1 |
Stock Counts |
Integer |
Stock Count Null Count Quantity = 0 |
Values: Yes/No Yes: The system changes the quantity to zero for items not counted (null quantity to zero), which makes the items appear as though they were counted. No: The system does not change the quantity to zero for items not counted, but rather leaves the value as null. These items will still appear as though they were not counted. Note This parameter does not apply to Unit and Amount stock counts. |
No |
Stock Counts |
Boolean |
Unguided Stock Count Allow Multiple Users |
Values: Yes/No This parameter controls whether more than one user can scan simultaneously again the same child stock count for an unguided count. Yes: The system will allow more than one user to access the same stock count, child count. No: The system will allow more than one user to access the same stock count, but only one user may access a child stock count at a time. |
No |
Stock Counts |
Boolean |
Unguided Stock Counts Automatic Save |
Values: Yes/No Yes: The physical count timestamp and item count quantity are automatically saved when the next item on the count is scanned. No: The physical count timestamp and item count quantity are saved when the user manually saves the count. It is assumed with this option: the user frequently saves. Note: The physical count timestamp is taken when the user scans the item for the first time. |
No |
Stock Counts |
Boolean |
Unit and Amount Stock Count Sales Processing |
Values: Timestamp Processing, Daily Sales Processing Timestamp Processing: This option is used when sales data is available near real-time with a date and time available on the transaction. The user is not prompted to select Before Store Open or After Store Close when starting the stock count since the sales timestamp will be used to compare with the timestamps taken during the stock count. Daily Sales Processing: This option is used when sales data is only available with a date and no time is provided and/or when integrated with RMFCS. The user is either prompted or the store parameter determines when the stock count is performed, (before store opens or after store close). The date is used to determine if a sale is late or not. Note: Unit and Amount stock counts require some dual processing in RMFCS for capturing the financial value. RMS is only capable of processing sales data daily and disregards the time value if included. |
Timestamp |
Stock Counts |
Integer |
Unit Stock Count Sales Processing |
Values: Timestamp Processing, Daily Sales Processing Timestamp Processing: This option is used when sales data is available near real-time with a date and time available on the transaction. The user is not prompted to select Before Store Open or After Store Close when starting the stock count since the sales timestamp will be used to compare with the timestamps taken during the stock count. Daily Sales Processing: This option is used when sales data is only available with a date and no time is provided. The date is used to determine if a sale is late or not. |
Timestamp |
Stock Counts |
Integer |
Update Stock On Hand |
Values: Yes/No Yes: Will update SOH. No: Will not update SOH. |
No |
Stock Counts |
Boolean |
Update Stock On Hand |
Values: All/Discrepant Discrepant Items only: The system will update only items identified as discrepant when the Update Auth Qty button is selected and when the stock count has been authorized, only the SOH is updated for the discrepant items only. All Items: The system will update all items regardless of if they are discrepant or not when the Update Auth Qty button is selected and when the stock count has been authorized, the SOH is updated for all items, including the non-discrepant. Note: Discrepant items are defined as items having a counted to actual variance greater than the pre-configured allowed variance. Non-discrepant items have a difference between the counted and actual qty, but they are within a tolerated variance. Unit and Amount stock counts will disregard this setting since all items will always be updated for that type of stock count. |
1 |
Stock Counts |
Integer |
Auto Approve Store Orders |
Values: Yes/No Yes: external store orders will be auto approved based upon the Days before auto approving Store Orders parameter No: external store orders will not be auto approved. |
Yes |
Store Order |
Boolean |
Days to hold before Auto Canceling Store Orders |
Values: 0-999 The number of days before setting store orders to canceled status. |
0 |
Store Order |
Integer |
Default Minimum Store Order Search Quantity |
Values: 0–999 Defines the default that will be set for the Minimum ROQ quantity on the search screen. User can override this quantity. |
0 |
Store Order |
Integer |
Display Item Image Store Orders - Execution |
Values: Yes/No Yes: This parameter indicates that item image will be displayed in Store Orders. No: Images will not be displayed in Store Orders. |
No |
Store Order |
Boolean |
Default Minimum Store Order Search Quantity |
Values: 0–999 Defines the default that will be set for the Minimum ROQ quantity on the search screen. User can override this quantity. |
0 |
Store Order |
Integer |
Minimum Store Order Quantity |
Values: 0–999 Defines the minimum quantity that must be ordered by the user in store orders. |
0 |
Store Order |
Integer |
Number of hours after create date in SIOCS to approve store orders |
Values: 0-999 This parameter will be used to set external store orders to auto approve store orders on an hourly basis. |
0 |
Store Order |
Integer |
Store Order Default UOM |
Values: SUOM/Cases/System Cases - it will always display cases in store orders. UOM in preferences will be ignored. SUOM - will always display SUOM in store orders. UOM in preferences will be ignored. System - will use the system / preferences UOM in store orders and user can change UOM in preferences and the UI will be updated. This applies to Quick Orders on mobile. |
System |
Store Order |
String |
Carrier Service Refresh Rate Milliseconds |
Determines the cache refresh rate for carrier service in milliseconds |
3600000 |
System Settings |
Integer |
Carton Type Refresh Rate Milliseconds |
Determines the cache refresh rate for carton type in milliseconds. |
3600000 |
System Settings |
Integer |
Context Type Refresh Rate Milliseconds |
Determines the cache refresh rate for context type in milliseconds |
3600000 |
System Settings |
Integer |
Database Clock Refresh Rate Milliseconds |
Determines the cache refresh rate for database clock in milliseconds. |
10800000 |
System Settings |
Integer |
Default POS transaction max size |
Determines the max size of pos transaction records that can be processed in one pos transaction web service call. |
1000 |
System Settings |
Integer |
Enable Inbound Integration for Non SIOCS Managed Stores |
Values: Yes/No Yes: Inbound integration for stores marked as Non SIOCS Managed will occur when subscribing as well as in batch processing. No: Inbound integration for stores marked as Non SIOCS Managed will NOT occur when subscribing as well as in batch processing. Web services and foundation data are not impacted. |
No |
System Settings |
Integer |
Item Image Request Timeout Milliseconds |
When loading an item image from an external server, the amount of time before we time out the request. |
25000 |
System Settings |
Integer |
Merchandise Hierarchy Refresh Rate Milliseconds |
Determines the cache refresh rate for merchandise hierarchy in milliseconds. |
3600000 |
System Settings |
Integer |
OAuth2 Authorization Cache Refresh Rate Milliseconds |
OAuth2 Authorization Cache Refresh Rate Milliseconds. |
900000 |
System Settings |
Integer |
Price History Refresh Rate Milliseconds |
Determines the cache refresh rate for item price history in milliseconds. |
3600000 |
System Settings |
Integer |
Price default extract size |
Determines the default extract size for price change import file for Regular, Promotion and Clearance price change batch jobs. |
1000 |
System Settings |
Integer |
Print Format Refresh Rate Milliseconds |
Determines the cache refresh rate for print format types in milliseconds. |
3600000 |
System Settings |
Integer |
Publish 3 Character Country Code |
Values: Yes, No Yes: The system will publish all the outgoing messages that involves country code with the 3 characters ISO country code. No: The system will publish all the outgoing messages that involves country code with the 2 characters ISO country code. |
No |
System Settings |
Boolean |
Publish Non Inventory Items |
Values: Yes/No This parameter indicates whether the non-inventory items will be published in the outgoing messages or not. |
Yes |
System Settings |
Boolean |
Serialization Label Refresh Rate Milliseconds |
Indicates serialization label refresh rate in milliseconds. |
3600000 |
System Settings |
Integer |
Server Repave Check Refresh Rate Milliseconds |
Server Repave Check Refresh Rate Milliseconds. |
300000 |
System Settings |
Integer |
Server Repave Pending Minimum Minutes |
Server Repave Pending Minimum Minutes. |
60 |
System Settings |
Integer |
Shipment Reason Refresh Rate Milliseconds |
Determines the cache refresh rate for finisher shipment reason in milliseconds. |
3600000 |
System Settings |
Integer |
Store Shipment Reason Refresh Rate Milliseconds |
Determines the cache refresh rate for store shipment reason in milliseconds. |
3600000 |
System Settings |
Integer |
Supplier Refresh Rate Milliseconds |
Determines the cache refresh rate for supplier in milliseconds. |
3600000 |
System Settings |
Integer |
Supplier Shipment Reason Refresh Rate Milliseconds |
Determines the cache refresh rate for supplier shipment reason in milliseconds. |
3600000 |
System Settings |
Integer |
Translation Refresh Rate Milliseconds |
Determines the cache refresh rate for locale and translations in milliseconds. |
3600000 |
System Settings |
Integer |
Uda Details Refresh Rate Milliseconds |
Determines the cache refresh rate for UDA details in milliseconds. |
3600000 |
System Settings |
Integer |
User Authorization Cache Refresh Rate Milliseconds |
Determines the cache refresh rate for user authorization cache in milliseconds. |
600000 |
System Settings |
Integer |
Warehouse Refresh Rate Milliseconds |
Determines the cache refresh rate for warehouse in milliseconds. |
3600000 |
System Settings |
Integer |
Warehouse Shipment Reason Refresh Rate Milliseconds |
Determines the cache refresh rate for warehouse shipment reason in milliseconds. |
3600000 |
System Settings |
Integer |
Display Item Image for Ticket - Execution |
This indicates whether the item image must be displayed in the ticketing dialog in mobile application. |
No |
Ticketing |
Integer |
Display Item Image for Ticket - Operations |
This indicates whether the item image must be displayed in the ticketing dialog in desktop application. |
No |
Ticketing |
Integer |
Daily GMT Batch Run |
Values: Yes/No Yes: Program will only be run once a day. The server is running on GMT and the dates for processing are still stored in GMT. The batch will process everything for the GMT day the server is in, including future records for the same day as the server GMT day. This only applies for the Transfer Delivery Auto Receive batch. |
Yes |
Time Zone |
Boolean |
Enable GMT for Customer Orders |
Values: Yes/No This is to determine whether the customer orders uploaded in the system are in GMT. |
No |
Time Zone |
Boolean |
Enable GMT for Dex/Nex |
Values: Yes/No This parameter will dictate whether the DEX/NEX data being loaded into the system is in GMT. |
No |
Time Zone |
Boolean |
Enable GMT for Direct Deliveries |
Values: Yes/No This parameter will dictate whether the Direct Delivery messages published by an external system should have dates in GMT or not. Yes: When publishing the Direct Delivery messages, it means that the dates in the message should be written in GMT. When subscribing to the purchase order messages, it means that the dates are coming in, in GMT time and no conversion needs to occur. When publishing a purchase order message, it means that the dates in the message should be written in GMT. No: When publishing the direct delivery messages, it means that the dates in the message should be converted from GMT and written in the store's local date/time. When subscribing to the purchase order message, it means that the dates are coming in, in are in the store's local date/time and must be converted to GMT prior to persisting the date in the database. When publishing the purchase order message, it means that the dates in the message should be converted from GMT and written in the store's local date/time. |
No |
Time Zone |
Boolean |
Enable GMT for Foundation Data |
Values: Yes/No This parameter will dictate whether any foundation data messages being loaded into the system are in GMT. |
No |
Time Zone |
Boolean |
Enable GMT for Inventory Adjustments |
Values: Yes/No This new system parameter will determine which date/time stamp is used in the inventory adjustment message when it is being published. Yes: When publishing the inventory adjustment message, it means that the dates in the message should be written in GMT. No: When publishing the inventory adjustment message, it means that the dates in the message should be converted from GMT and written in the store's local date/time. |
No |
Time Zone |
Boolean |
Enable GMT for POS sale import process |
Values: Yes/No This parameter will dictate whether or not the POS data being loaded into the system are in GMT. |
No |
Time Zone |
Boolean |
Enable GMT for Price Changes |
Values: Yes/No This parameter will dictate whether the price changes being subscribed to by the system are time zone sensitive. Yes: When subscribing to a price change, it means that the effective date is coming in GMT time and no conversion needs to occur. No: The effective date must be converted prior to storing the price change in the system. |
No |
Time Zone |
Boolean |
Enable GMT for RTVs |
Values: Yes/No This system parameter will dictate whether the RTV message being loaded into the system is in GMT. Likewise, if the system publishes any RTV message this will determine which date/time stamp is used on the message as well Yes: When subscribing to the RTV message, it means that the dates are coming in, in GMT time and no conversion needs to occur. When publishing the RTV message, it means that the dates in the message should be written in GMT. No: When subscribing to the RTV message, it means that the dates are in the store's local date/time and must be converted to GMT prior to persisting the date in the database. When publishing the RTV message, it means that the dates in the message should be converted from GMT and written in the store's local date/time |
No |
Time Zone |
Boolean |
Enable GMT for ReSA sale import process |
Values: Yes/No This parameter will dictate whether the ReSA data being loaded into the system are in GMT. |
No |
Time Zone |
Boolean |
Enable GMT for Receiving |
Values: Yes/No This parameter will dictate whether receiving messages need to be published in GMT or not. |
No |
Time Zone |
Boolean |
Enable GMT for Stock Counts |
Values: Yes/No This parameter will determine which date/time stamp is used in the stock count message when it is being published. Yes: When publishing the stock count message, it means that the dates in the message should be written in GMT. No: When publishing the stock count message, it means that the dates in the message should be converted from GMT and written in the store's local date/time. |
No |
Time Zone |
Boolean |
Enable GMT for Store Orders |
Values: Yes/No This parameter will determine which date/time stamp is used in the store order message when it is being published. Yes: When publishing the store order message, it means that the dates in the message should be written in GMT. No: When publishing the store order message, it means that the dates in the message should be converted from GMT and written in the store’s local date/time. |
No |
Time Zone |
Boolean |
Enable GMT for Store Transfers |
Values: Yes/No This new system parameter will dictate whether the Transfer messages being loaded into the system from an external system has dates in GMT or not. Likewise, if the system publishes any Transfer messages to an external system this will determine which date/time stamp is used on the message as well. Yes: When subscribing to the Transfer messages, it means that the dates are coming in, in GMT time and no conversion needs to occur. When publishing a transfer message, it means that the dates in the message should be written in GMT. No: When subscribing to the transfer message, it means that the dates are coming in, in are in the store’s local date/time and must be converted to GMT prior to persisting the date in the database. When publishing the transfer message, it means that the dates in the message should be converted from GMT and written in the store’s local date/time. |
No |
Time Zone |
Boolean |
Enable GMT for Third Party Stock Counts |
Values: Yes/No his parameter will determine whether the date/time stamp in the Third party stock count file (DSLDAT) is in GMT or not. |
No |
Time Zone |
Boolean |
Enable GMT for Initial Inventory Import |
Values: Yes/No This parameter will determine whether the date/time stamp in the Initial Inventory Import file (.DAT file) is in GMT or not. |
No |
Time Zone |
Boolean |
Enable GMT for Vendor ASN |
Values: Yes/No This parameter will dictate whether the Vendor ASN messages being loaded into the system have dates in GMT or not. |
No |
Time Zone |
Boolean |
Enable GMT for Warehouse Transfers |
Values: Yes/No This new system parameter will dictate whether the transfer messages being loaded into the system have GMT dates or not. Likewise, if the system publishes any transfer message to an external system this will determine which date/time stamp is used on the message as well. Yes: When subscribing to the transfer messages, it means that the dates are coming in, in GMT time and no conversion needs to occur. When retrieving transfer data, it means that the dates are in GMT time and no conversions needs to occur. This includes both reading and writing data. When publishing a transfer message, it means that the dates in the message should be written in GMT. No: When subscribing to the transfer message, it means that the dates are coming in, in are in the store’s local date/time and must be converted to GMT prior to persisting the date in the database. When retrieving transfer data, it means that the dates are not in GMT time and must be converted to GMT. This includes both reading and writing data. When publishing the transfer message, it means that the dates in the message should be converted from GMT and written in the store’s local date/time. |
No |
Time Zone |
Boolean |
Damaged Delivery Notification |
Values: Yes/No Yes: Sends a notification to the receiving store when damaged items are received on the delivery. No: No alert is sent. This parameter generates a notification for transfers with items marked as damaged (Warehouse, Store, Finisher). |
Yes |
Transfer Receiving |
Boolean |
Days Shipped Delivery Overdue Notification |
Values: 1-999 This parameter generates a notification when the delivery is overdue. The delivery will be considered overdue when the create date of the delivery plus the days from this parameter have passed. This will include only deliveries from source type store. |
7 |
Transfer Receiving |
Integer |
Display Item Image for Transfer Receiving |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in that transaction. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
Transfer Receiving |
Boolean |
External Finisher UIN Qty Discrep Notification |
Values: Yes/No This system parameter will generate notification when there is a discrepancy with the number of UINs on the ASN and the UINs received when auto receiving with a Source Type of 'Finisher'. Yes: Whenever the transaction cannot be auto received, the system generates a notification when there is a discrepancy with the number of UINs on the Finisher Return and the UINs received. Auto Received by batch Auto Received thru RIB Injector. No: No alert is generated. |
Yes |
Transfer Receiving |
Boolean |
Misdirected Container Notification |
Values: On / No Yes: Sends a notification when a location receives a container belonging to another location. No: No notification is sent. This system parameter will generate a notification when there is a misdirected container that has been received in another location. |
Yes |
Transfer Receiving |
Boolean |
Number of Days Received Transfer Deliveries can be Adjusted |
Values: 0-999 This parameter controls the number of days a container can be adjusted within a receipt after (Warehouse, Store, Finisher) are received. 0: no adjustment allowed 1: allowed to adjust until the end of today 2: allowed to adjust until the end of tomorrow X: allowed to adjust until x days starting from today |
0 |
Transfer Receiving |
Integer |
Quick Receiving - Receive misdirected containers |
Values: Not Allowed, Automatic, Prompted Not Allowed: Misdirected container cannot be received, no messaging. Automatic: Receives the misdirected container without prompting the user. Prompted: User is prompted to receive the misdirected container. |
Not Allowed |
Transfer Receiving |
Integer |
Quick Receiving - Receive missing containers |
Values: Yes/No Yes: Enables the ability to receive missing containers. No: Disables the ability to receive missing containers. |
Yes |
Transfer Receiving |
Boolean |
Receive Entire Transfer |
Values: Yes/No Yes: User is ONLY allowed to receive the entire delivery. It is not allowed to add any items, only confirmation of the receipt is allowed (Warehouse, Store, Finisher). No: The user is not limited to only receiving the entire delivery. |
No |
Transfer Receiving |
Boolean |
Store Receiving Force Close Indicator |
Values: RL / SL / NL This parameter applies to deliveries with a Source Type of 'Store'. RL: (Receiver Loss) Any shipped quantity that was not received is a loss at the receiving store. SL: (Sending Loss) Any shipped quantity that was not received is a loss at the sending store. NL: (No Loss) Any shipped quantity that was not received does not affect the receiving or the sending store. |
Receiving Loss |
Transfer Receiving |
Integer |
Store Receiving Over/Under Notification |
Values: Yes / No This parameter generates a notification to the receiving store when items on a transfer receipt with a Source Type of 'Store' is greater than or less than the expected quantity or if the expected quantity is null or zero. A notification should not be sent in the case of a manually created container or a copied misdirected container. On: Sends a notification when the receiving store over or under receives goods. No: No alert is sent. |
Yes |
Transfer Receiving |
Boolean |
Warehouse/Store UIN Qty Discrep Notification |
Values: Yes/No This system parameter will generate notification when there is a discrepancy with the number of UINs on the ASN and the UINs received when auto receiving a warehouse or store delivery with a Source Type of 'Warehouse' or 'Store'. Yes: Sends a notification when there is a discrepancy with UINs on the ASN. The number of UINs on the ASN and the Qty received do not match and cannot be auto received. Auto Received by batch (Store), (Warehouse) Auto Received thru RIB Injector No: No notification is generated. |
Yes |
Transfer Receiving |
Boolean |
Display Item Image for Transfer Shipment |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in that transaction. It is in the item list and the details of the transaction. No; Image will not be displayed in that functional area. |
No |
Transfer Shipment |
Boolean |
Days to send Notification before not after date for transfer requests |
Values: 0-999 For transfer requests generated in an external system (warehouse, store or finisher), his option sends a notification the specified number of days before the not after date is reached, if the transfer was not dispatched. |
2 |
Transfers |
Integer |
Display Item Image for Transfer |
Values: Yes/No Yes: This parameter indicates if the item image will be displayed in that transaction. It is in the item list and the details of the transaction. No: Image will not be displayed in that functional area. |
No |
Transfers |
Boolean |
Transfer Request Approve Notification |
Values: Yes/No Yes: A notification will be generated when a requested transfer is approved. No: No notification will be generated. Note: The notification will only be generated for SIOCS initiated store to store requests. |
No |
Transfers |
Boolean |
Transfer Request Notification |
Values: Yes/No Yes: A notification will be generated when a transfer is requested. No: No notification will be generated. Note: The notification will only be generated for SIOCS initiated store to store requests. |
No |
Transfers |
Boolean |
Transfer Request Reject Notification |
Values: Yes/No Yes: A notification will be generated when a transfer is rejected. No: No notification will be generated. Note: The notification will only be generated for SIOCS initiated store to store requests. |
No |
Transfers |
Boolean |
Unavailable Qty Discrepancy Notification |
Values: Yes/No Yes: A notification will be generated when a transfer request fails auto-approval. No: No notification will be generated. Note: Auto Accept External Generated Request is set to On and Unavailable quantity requested is more than the sending store has. |
No |
Transfers |
Boolean |
Currency Default Type |
Gives the default currency for EICS and SOCS. |
USD |
UI |
String |
Display Item Description |
Values: Short Description / Long Description On Mobile the description will be short or long based upon this configuration. Short Item Description: The description displayed everywhere will be the short item description. Note that when integrated with Oracle Retail's merchandising system, the short description of an item is a product of the first 20 characters of the long description. Long Item Description: The description displayed everywhere will be the long item description. Note that when integrated with Oracle Retail's merchandising system, the Merchandising system concatenates the diff descriptions with the long item description, so the user is able to view all diff information. The diffs display in order from Diff 1 to Diff 4. On the desktop the system will always use the long description. |
Short Description |
UI |
Integer |
Display Item Description Diffs |
Values: Yes/No Yes: A second item description line for diffs will be used wherever an item description is displayed where applicable. No: The second line will not be displayed for the item description and the diffs will not be displayed separately. |
Yes |
UI |
Boolean |
Maximum Manual Quantity Entry |
Values: 1-100,000,000 The value set here will be the maximum value a user can enter for a quantity via the Numeric Entry on the mobile. |
999 |
UI |
Integer |
Problem Line UI Limit |
Gives the recommended item count in product group component screen for problem line stock count product group. |
1500 |
UI |
Integer |
Search Date Range Default for Container Lookup |
Values: 0-99 This holds the default number of days for which the Container records need to be listed in the Container Lookup screen. |
0 |
UI |
Integer |
Search Date Range Default for Transaction History |
Values: 0-99 This holds the default number of days for which the transaction history records need to be listed in the Transaction History List screen. |
0 |
UI |
Integer |
Search Limit Default for Area |
Values: 1-999 This parameter indicates the default search limit for the Area List screen on EICS. |
50 |
UI |
Integer |
Search Limit Default for Container Lookup - Execution |
Values: 1-999 Indicates the default search limit for Container Lookup on SOCS. |
50 |
UI |
Integer |
Search Limit Default for Container Lookup - Operations |
Values: 1-999 This parameter will determine the number of records to be displayed on container lookup list screen. The default value on container lookup list screen should be set to the value for the system parameter. |
50 |
UI |
Integer |
Search Limit Default for Customer Order Picking |
Values: 1-999 Indicates the default search limit for Customer Order Picking. |
50 |
UI |
Integer |
Search Limit Default for Customer Orders |
Values: 1-999 Indicates the default search limit for Customer Orders. |
50 |
UI |
Integer |
Search Limit Default for DSD Receiving |
This is to determine the default search limit for DSD receiving list. |
50 |
UI |
Integer |
Search Limit Default for Finisher Lookup - Operations |
Values: 1-999 Indicates the default search limit for Finisher Lookup. |
50 |
UI |
Integer |
Search Limit Default for Format Assignment - Operations |
Values: 1-999 This parameter will determine the number of records to be displayed on the Format Assignment List screen in desktop application. The default value on the search screen should be set to the value from this parameter. |
50 |
UI |
Integer |
Search Limit Default for Inventory Adjustments - Execution |
Values: 1-999 Indicates the default search limit for Inventory Adjustments on SOCS. |
50 |
UI |
Integer |
Search Limit Default for Inventory Adjustments - Operations |
Values: 1-999 Indicates the default search limit for Inventory Adjustments on EICS. |
50 |
UI |
Integer |
Search Limit Default for Item Baskets - Execution |
Values: 0-999 Indicates the default search limit for Item Baskets on SOCS. |
50 |
UI |
Integer |
Search Limit Default for Item Baskets - Operations |
Values: 0-999 Indicates the default search limit for Item Baskets on EICS. |
50 |
UI |
Integer |
Search Limit Default for Item Lookup - Execution |
Values: 1-999 Indicates the default search limit for Item Lookup on SOCS. |
50 |
UI |
Integer |
Search Limit Default for Item Lookup - Operations |
Values: 1-999 Indicates the default search limit for Item Lookup on EICS. |
50 |
UI |
Integer |
Search Limit Default for Item Scan Number Lookup |
Values: 1-999 This parameter will determine the number of records to be displayed on the Item Scan Number Lookup screen. The default value on the ISN Lookup search screen should be set to the value from this parameter. |
500 |
UI |
Integer |
Search Limit Default for MPS Staged Messages |
Values: 1-999 Indicates the default search limit for MPS staged messages on MPS staged message screen in EICS. |
50 |
UI |
Integer |
Search Limit Default for Notifications |
Values: 1-999 Indicates the default search limit for Notifications. |
50 |
UI |
Integer |
Search Limit Default for Open Transaction |
Values: 1-999 Indicates the default search limit for Open Transactions. |
50 |
UI |
Integer |
Search Limit Default for Operational Views - Operations |
Values: 1-999 This parameter will determine the number of records to be displayed on various operational view screens. The default value on various operational views screens should be set to the value from the system parameter. |
50 |
UI |
Integer |
Search Limit Default for POS Transaction Resolution |
Values: 1-999 This parameter will determine the number of records to be displayed on the POS Transaction resolution dialog in desktop application. The default value on the search screen should be set to the value from this parameter. |
50 |
UI |
Integer |
Search Limit Default for Purchase Order |
This parameter will determine the default number of records to be displayed on PO list screen. |
50 |
UI |
Integer |
Search Limit Default for Replenishment Pick |
Values: 1-999 Indicates the default search limit for shelf replenishment. |
50 |
UI |
Integer |
Search Limit Default for RTV |
Values: 1-999 Indicates the default search limit for Returns. |
50 |
UI |
Integer |
Search Limit Default for Scan List |
Values: 1-999 Indicates the default search limit for scan lists. |
50 |
UI |
Integer |
Search Limit Default for Shelf Adjustment |
Values: 1-999 Indicates the default search limit for shelf adjustments. |
50 |
UI |
Integer |
Search Limit Default for Store Order |
Values: 1-999 Indicates the default search limit for Store Orders. |
50 |
UI |
Integer |
Search Limit Default for Stock Count |
Values: 1-999 Indicates the default search limit for Stock Counts. |
50 |
UI |
Integer |
Search Limit Default for Supplier Lookup |
Values: 1-999 This parameter will determine the number of records to be displayed on supplier lookup list screen. The default value on supplier lookup list screen should be set to the value for the system parameter. |
50 |
UI |
Integer |
Search Limit Default for Supplier Lookup - Operations |
Values: 1-999 This parameter will determine the number of records to be displayed on supplier lookup list screen. The default value on supplier lookup list screen should be set to the value for the system parameter. |
50 |
UI |
Integer |
Search Limit Default for Ticket - Operations |
Values: 1-999 This parameter will determine the number of records to be displayed on the ticketing dialog in desktop application. The default value on the search screen should be set to the value from this parameter. |
50 |
UI |
Integer |
Search Limit Default for Transaction History |
Values: 1-999 Indicates the default search limit for Transaction History. |
50 |
UI |
Integer |
Search Limit Default for Transfer Receipts |
Values: 1-999 Indicates the default search limit for Transfer receipts. |
50 |
UI |
Integer |
Search Limit Default for Transfer Shipment |
Values: 1-999 Indicates the default search limit for Transfer shipments. |
50 |
UI |
Integer |
Search Limit Default for Transfers |
Values: 1-999 Indicates the default search limit for Transfer documents. |
50 |
UI |
Integer |
Search Limit Default for Troubled Transaction List |
Values: 1-999 Indicates the default search limit for Troubled Transactions |
50 |
UI |
Integer |
Search Limit Default for UIN Lookup |
Values: 1-999 Indicates the default search limit for UIN Lookup. |
50 |
UI |
Integer |
Shelf Replenishment UI Limit |
Values: 1-99999 Gives recommended item count in product group component screen for shelf replenishment pick product groups. |
1500 |
UI |
Integer |
Store Order UI Limit |
Values: 1-99999 This parameter indicates the UI limit for store orders, used in generation of the store orders. It is also used in the Recommended # of Items in Product Group Components. |
1500 |
UI |
Integer |
Ticketing UI Limit |
Values: 1-99999 This parameter indicates the UI limit for ticketing, used in generation of the auto ticket print. It is also used in the Recommended # of Items in Product Group Components. |
1500 |
UI |
Integer |
Auto Inventory Adjustment UI Limit |
Values: 1-99999 This parameter indicates the UI limit for the auto inventory adjustment, used in the generation of auto inventory adjustment records. It is also used in the recommended # of items in the Product Group components. |
1500 |
UI |
Integer |
Unit and Amount Count UI Limit |
Values: 1-99999 Gives the recommended item count in product group component screen for unit and amount stock count product group. |
1500 |
UI |
Integer |
Unit Count UI Limit |
Values: 1-99999 Gives the recommended item count in product group component screen for unit stock count product group. |
5000 |
UI |
Integer |
Allow Store UIN Relocation |
Values: Yes/No Indicates whether UIN can be relocated from one store to another. |
Yes |
UIN |
Boolean |
Store Admin Parameters
Table 8-2 Store Admin Parameters
Options | Description | Default Value | Topic | Type |
---|---|---|---|---|
Display Shopfloor/ Backroom Quantity in Header |
Values: Yes/No Yes: This parameter indicates if the shop floor and back room SOH should be displayed in various areas of the system including item lookup as well as transactions. No: Shop floor and back room SOH will not be displayed in various areas of the system. |
No |
Admin |
Boolean |
Manifest Weight UOM |
Values: List of UOMs from the Weight UOM table The UOM selected for this store admin will be used as the Weight UOM for the weight on the BOL in store to store transfer shipments, customer order deliveries and returns. |
LBS |
Admin |
String |
SSCC Shipping Label ID Generation |
Values: Yes/No Yes: The system will generate an identifier for printing on the shipping label. No: The user will need to enter an identifier for printing on the shipping label. This store parameter will be used for RTV Shipping and Transfer Shipping. |
Yes |
Admin |
Boolean |
UIN Processing Enabled |
Values: Yes/No Yes: Enables UIN processing for the store. No: UIN functionality is disabled for the store. |
No |
Admin |
Boolean |
Use Extended Attribute Entry |
This will turn on and off the feature for editing transaction item level attributes, the capturing of Extended Attributes will be skipped. Values: Yes/No Yes: If set to ‘Yes’, the Extended Attributes can manually be entered, scanned and viewed. This is for mobile and desktop.. No:If set to ‘No’, the Extended Attributes capture screen is not available. User cannot manually enter, view or scan extended attributes on mobile or desktop. |
No |
Admin |
Boolean |
Allow Picking By Area |
Values: Yes/No Yes: Picking by Area is allowed. The user will be able to select an Area when creating a pick if the Customer Order Fulfillment Restriction is set to 'Transaction Controlled'. The system will narrow down the customer order to those items within an area when creating the pick. No: Picking by Area is not allowed, and the system will always look at all items on the customer order when creating a pick. |
Yes |
Customer Order |
Boolean |
Auto Pick Mixed Containers |
Values: Yes/No Yes: If a container has items in it that are for both customer orders and non-customer orders, the system will auto pick the container. It will mark those items that exist on the customer order as picked. No: If there is a mixed container of customer order and non-customer order items, it will not get auto picked and the picked quantities will not be updated. |
No |
Customer Order |
Boolean |
Auto Pick On Receive - Direct Delivery |
Values : Yes/No Yes: The system will automatically fill in the pick quantities on the customer order when receiving. This can only happen if the customer order record has already come into the system. If there is no customer order, the auto picking will not happen at the time of receiving, rather it will occur when the customer order comes in. No: The system will not pick when receiving goods. |
No |
Customer Order |
Boolean |
Auto Pick On Receive - Transfer Receiving |
Values: Yes/No Yes: The system will automatically fill in the pick quantities on the customer order when receiving. This can only happen if the customer order record has already come into the system. If there is no customer order, the auto picking will not happen at the time of receiving, rather it will occur when the customer order comes in. No: The system will not pick when receiving goods in transfer receiving. |
No |
Customer Order |
Boolean |
Capture Vehicle Details on Submit |
Values: Yes/No Yes: The details regarding the vehicle/driver who is handling the shipment, should be captured before submitting a customer order delivery No: The shipment can be submitted without the details regarding the vehicle/driver |
No |
Customer Order |
Boolean |
Default Customer Order Picking Method |
Values: Bin / Store Customer Order This parameter is used to define the default picking method when creating a customer order pick, bin or store customer order. Note this is just a default and the user can still switch the picking method. |
Store Customer Order |
Customer Order |
Integer |
Default Number of Bins |
Values: 1-999 This parameter will determine the number of bins to default into the 'Bin Qty' field if the user selects 'Bin' as the pick type when creating the pick. |
1 |
Customer Order |
Integer |
Dispatch Validate |
Values: Ship Direct, Ship Submit Ship Direct: System will control all processes. The user will be able to go from create/edit directly to dispatch. There will not be a submit option. Ship Submit: This option will require the user to press the Submit option and require a specific press of the dispatch button. |
Ship Direct |
Customer Order |
Integer |
Holding Location Required |
Values: Yes/No Yes - In the Customer Order Quick flow on mobile, the holding location will be required in the Customer Order Pick. No - In the Customer Order Quick flow on mobile, the holding location will not be required in the Customer Order Pick. |
No |
Customer Order |
Boolean |
Generate Bins |
Values: System / Manual System: The system will automatically generate the bin IDs when the pick is created. Manual: The system will require the user to enter the bin IDs upon acting on the created pick. This option removes the need for printing out labels since the labels already exist on the bin. For both System and Manual, the user will still have the option to print labels for the bins. |
Manual |
Customer Order |
Integer |
Item Substitution - Store Discretion |
Values: Yes/No This store parameter is used to determine if the user can use their own discretion when doing substitute items in the picking process. Yes: The user can choose any item to be used as a substitute item. No: Only those items that are defined as substitutes can be substituted. |
No |
Customer Order |
Boolean |
Navigate to Shipment |
Values: Yes/No Yes - In the Customer Order Quick Flow on mobile, for those orders that are shipment type, the user will navigate to the shipment upon completing the pick. No - In the Customer Order Quick Flow on mobile, for those orders that are shipment type, the user will navigate to the Open Transactions screen. |
No |
Customer Order |
Boolean |
Override Bin Quantity |
Values: Yes/No This store parameter determines whether the user is allowed to override the default bin quantity when creating a pick by bin. The Bin Quantity is defaulted based upon the store parameter for Default Number of Bins. |
No |
Customer Order |
Boolean |
Picking Required for Customer Orders |
Values: Yes/No Yes: Requires that manual picking be performed on the customer order prior to being able to create a delivery for it. No: Picking is not necessary to create a delivery. |
Yes |
Customer Order |
Boolean |
Pre-shipment Notification |
Values: Yes / No This parameter will drive the following functionality: Yes: The system will publish a pre-shipment message No: The system will not publish a pre-shipment message |
No |
Customer Order |
Boolean |
Reserve Customer Order Inventory Upon Receiving |
Values: Yes/No This store parameter will dictate when inventory for a web order customer order should be reserved. Yes: Inventory will be reserved upon receiving a delivery in the store which contains the customer order (Store to store transfer, DSD, Warehouse to Store transfer). If the retailer wishes to fulfill the customer orders from deliveries, for example getting the goods from the warehouse, then this option would be set to Yes to reserve upon receiving. No: Inventory will be reserved upon getting the customer order into the store. If the retailer chooses to mainly fulfill customer orders from within the stock in the store, this parameter would be set to No, thus reserving inventory right away when the customer order is received. |
No |
Customer Order |
Boolean |
Restrict Shipment Dispatch After Submit |
Values: Yes/No . Yes: This restriction will not allow the user to move an Customer Order Deliveries from Submitted to Dispatched status unless the Fiscal Doc ID/E-way Bill ID has been filed in No: The shipment can be dispatched without Fiscal Doc ID/E-way Bill ID |
No |
Customer Order |
Boolean |
Allow Multiple Deliveries against PO with No ASN |
Values: Yes/No Yes: The user is able to create more than one delivery for the same PO when the PO does not have an associated ASN. No: The user can only create a single delivery against a PO when the PO does not have an associated ASN. The PO will be closed when the delivery is confirmed. |
Yes |
DSD Receiving |
Boolean |
Auto close days after expected date |
Values: 0-999 Number of days after the expected delivery date the ASN will be closed. |
5 |
DSD Receiving |
Integer |
Direct Delivery Auto Remove Over Received Quantity |
Values: Yes/No Yes: If set to Yes, the user is allowed to add any quantity for the DSD, but any quantity above the expected quantity will be removed from the transaction. After the user confirms the transaction, they are prompted that any over received quantities will be removed. The user can create more than one delivery for the same PO when the PO does not have an associated ASN. No: The over received quantities will stay in the delivery transaction. |
No |
DSD Receiving |
Boolean |
Direct Delivery Default to ShopFloor Receiving |
Values: Yes/No This parameter determines whether the DSD receiving dialog will default to receive inventory into the shop floor instead of automatically receiving into the back room or delivery bay. Yes: The DSD Receiving Container workflow will default the option to receive inventory into the shop floor. The shop floor inventory bucket will be incremented instead of the backroom or delivery bay bucket. If a capacity is defined for the item and Direct Delivery Receive Item Capacity is set to yes, the maximum shop floor quantity will equal the capacity; otherwise, the shop floor will be updated to the entire receipt amount. If the capacity is used and if the receiving quantity is excess, the balance is incremented to delivery bay or back room depending on the Replenishment - Delivery Bay Inventory parameter. No: The option will be defaulted to back room or delivery bay depending on the Replenishment - Delivery Bay Inventory parameter. If this parameter is on, the system will increment the delivery bay bucket instead of back room. |
No |
DSD Receiving |
Boolean |
Direct Delivery Invoice Entry |
Values: Enabled/Disabled/Unique Enabled: This option allows the user to enter any value for the invoice number, including duplicates. Disabled: The Invoice Number and date fields are disabled. Unique: The Invoice Number field will allow entry; however, the user will not be able to enter a duplicate invoice number based upon the supplier. Upon entering an Invoice Number, the system will validate if the invoice already exists for the supplier defined on the DSD. If a duplicate exists, there will be an error. If no duplicate exists, the invoice number will be accepted. |
Enabled |
DSD Receiving |
Integer |
Direct Delivery Receive Item Capacity |
Values: Yes/No This parameter determines whether the capacity will be considered while receiving the deliveries. Yes: While receiving, the capacity will be considered. For example: If capacity is 50, delivery is for 100, and Available SOH is 10 on the shop floor, if this parameter is on and receive in shop floor is checked, 40 (un-damaged) will be moved to shop floor and the rest to the backroom. No: While receiving, the capacity will not be considered. Damaged inventory will not move to the shop floor. |
No |
DSD Receiving |
Boolean |
DSD Receiving Auto Remove Damaged Quantity |
Values: Yes/No Yes: All damaged items on the delivery are removed automatically when confirming the transaction. No: All damaged items remain on the delivery when confirming the transaction. |
No |
DSD Receiving |
Boolean |
Vehicle Number Required for Transfer Shipment |
Values: Yes/No Yes: Capturing of vehicle number of the vehicle transporting the shipment is mandatory before Submitting a transfer shipment No: Capturing of vehicle number of the vehicle transporting the shipment is not mandatory before Submitting a transfer shipment |
No |
Fiscal Document |
Boolean |
Vehicle Number Required for RTV Shipment |
Values: Yes/No Yes: Capturing of vehicle number of the vehicle transporting the shipment is mandatory before Submitting a RTV shipment No: Capturing of vehicle number of the vehicle transporting the shipment is not mandatory before Submitting a RTV shipment |
No |
Fiscal Document |
Boolean |
Vehicle Number Required for Customer Order Delivery |
Values: Yes/No Yes: Capturing of vehicle number of the vehicle transporting the shipment is mandatory or not before Submitting a customer order delivery No: Capturing of vehicle number of the vehicle transporting the shipment is mandatory or not before Submitting a customer order delivery |
No |
Fiscal Document |
Boolean |
Vehicle State or Country Required for Transfer Shipment |
Values: Yes/No Yes: Capturing of vehicle country/state/county of the vehicle transporting the shipment is mandatory before Submitting a transfer shipment No: Capturing of vehicle country/state/county of the vehicle transporting the shipment is not mandatory before Submitting a transfer shipment |
No |
Fiscal Document |
Boolean |
Vehicle State or Country Required for RTV Shipment |
Values: Yes/No Yes: Capturing of vehicle country/state/county of the vehicle transporting the shipment is mandatory before Submitting a RTV shipment No: Capturing of vehicle country/state/county of the vehicle transporting the shipment is not mandatory before Submitting a RTV shipment |
No |
Fiscal Document |
Boolean |
Vehicle State orCountry Required for Customer Order Delivery |
Values: Yes/No Yes: Capturing of vehicle country/state/county of the vehicle transporting the shipment is mandatory or not before Submitting a customer order delivery No: Capturing of vehicle country/state/county of the vehicle transporting the shipment is mandatory or not before Submitting a customer order delivery |
No |
Fiscal Document |
Boolean |
Driver Name Required for Transfer Shipment |
Values: Yes/No Yes: Capturing of driver name of the vehicle transporting the shipment is mandatory before Submitting a transfer shipment No: Capturing of driver name of the vehicle transporting the shipment is not mandatory before Submitting a transfer shipment |
No |
Fiscal Document |
Boolean |
Driver Name Required for RTV Shipment |
Values: Yes/No Yes: Capturing of driver name of the driver transporting the shipment is mandatory before Submitting a RTV shipment No: Capturing of driver name of the driver transporting the shipment is not mandatory before Submitting a RTV shipment |
No |
Fiscal Document |
Boolean |
Driver Name Required for Customer Order Delivery |
Values: Yes/No Yes Capturing of driver name of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery No: Capturing of driver name of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery |
No |
Fiscal Document |
Boolean |
Driver License Number Required for Transfer Shipment |
Values: Yes/No Yes: Capturing of driver license number of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery No: Capturing of driver license number of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery |
No |
Fiscal Document |
Boolean |
Driver License Number Required for RTV Shipment |
Values: Yes/No Yes: Capturing of driver license number of the driver transporting the shipment is mandatory before Submitting a RTV shipment No: Capturing of driver license number of the driver transporting the shipment is not mandatory before Submitting a RTV shipment |
No |
Fiscal Document |
Boolean |
Driver License Number Required for Customer Order Delivery |
Values: Yes/No Yes Capturing of driver license number of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery No: Capturing of driver license number of the driver transporting the shipment is mandatory or not before Submitting a customer order delivery |
No |
Fiscal Document |
Boolean |
Context Type required for Inventory Adjustments |
Values: Yes/No This configuration decides whether the capturing of context type is mandatory or not for Inventory Adjustments. |
No |
Inventory Adjustments |
Boolean |
Days Before Item Basket Expiration |
Values: 0-999 This parameter will be used to add to the system date when defaulting the expiration date on an item basket. A value of 0 would set the expiration date to today. A value of 1 will set the expiration date to tomorrow (today + 1). |
1 |
Item Basket |
Integer |
Auto Accept External Generated RTV Request |
Values: Yes/No This parameter determines whether system automatically approves the return request and defaults the requested quantity to the accepted quantity for externally generated RTV requests. |
No |
RTV |
Boolean |
Not After Date Default days |
Values: 0-999 This parameter would decide the number of days after which a RTV document can be closed After not after date is passed. All status documents would be marked cancelled once this criterion is met. |
30 |
RTV |
Integer |
Capture Vehicle Details on Submit |
Values: Yes/No Yes: The details regarding the vehicle/driver who is handling the shipment, should be captured before submitting an RTV shipment No: The shipment can be submitted without the details regarding the vehicle/driver |
No |
RTV Shipment |
Boolean |
Dispatch Validate |
Values: Ship Direct, Ship Submit Ship Direct: SIOCS will control all processes. The user will be able to go from create/edit directly to dispatch. Ship Submit: This option will require the user to press the Submit button and require a specific press of the dispatch button. An additional option is that an external system will generate a dispatch message through a standard web service. |
Ship Direct |
RTV Shipment |
Integer |
Pre-shipment Notification |
Values: Yes/No Yes: The system will publish a pre-shipment message. No: The system will not publish a pre-shipment message. |
No |
RTV Shipment |
Boolean |
Restrict Shipment Dispatch After Submit |
Values: Yes/No Yes: This restriction will not allow the user to move an RTV Shipment from Submitted to Dispatched status unless the Fiscal Doc ID/E-way Bill ID has been filled in. No: The shipment can be dispatched without Fiscal Doc ID/E-way Bill ID |
No |
RTV Shipment |
Boolean |
RTV Shipment Carrier Default |
Values: Sender / Receiver / Third Party When creating a return, the Carrier Type on the BOL will default initially based upon this parameter. The user can still change this value and if so, that will be the value used on the return. Sender: Sender will be selected for Carrier Type on BOL Receiver: Receiver will be selected for the Carrier type on BOL. Third Party: Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to "Other". |
Third Party |
RTV Shipment |
Integer |
Display Sequence Fields |
Values: Yes/No Yes: Will display sequencing information throughout the application including guided stock count option, capacity, and an item's locations including primary location. No: Sequence information will not be displayed in the system. |
No |
Sequencing |
Boolean |
Allow Delivery Bay Quantity to Move to Shop Floor |
This is to determine whether the user is allowed to move the delivery bay quantities to shop floor. If allowed, the system will provide an option for the user to select shop floor or back room to move the inventory. If not allowed, it moves the quantity entered to back room. The system will show a pop up to select the option in the Manage Delivery Bay dialog. Values : Yes/No |
No |
Shelf Replenishment |
Boolean |
Replenishment - At Case Level |
Yes: The standard UOM will default to Cases on the shelf replenishment screens. No: The standard UOM will default to Units on the shelf replenishment screens. Note: This parameter will determine whether to replenish shelves at the Case or standard unit of measure. This will override the 'Default UOM' system parameter. |
Yes |
Shelf Replenishment |
Boolean |
Replenishment - Delivery Bay Inventory |
Values: Yes/No Yes: The delivery bay will be used for replenishment. No: The delivery bay will not be used. |
Yes |
Shelf Replenishment |
Boolean |
Replenishment - End of Day max. fill % |
This parameter will determine the percentage the stock can fall to before creating the end of day replenishment list. |
100 |
Shelf Replenishment |
Double |
Replenishment - Item Substitution Store Discretion |
Values: Yes/No Yes: The user is allowed to choose any item to substitute. An item lookup feature will allow the user to search for an item to select. No: The user is restricted to scanning/entering an item that exists on the list of approved substitute items defined by the merchandising system. Note: If there are no items defined for item substitution, the dialogue will be displayed with the original item in the header with no substitutes. |
No |
Shelf Replenishment |
Boolean |
Replenishment - Within Day Max. fill % |
This parameter will determine the percentage the stock can fall to before creating the within day replenishment list. |
75 |
Shelf Replenishment |
Double |
Display Late Inventory Adjustment Message |
Yes: When the user is confirming a Stock Count in the Authorization phase and there are items on the stock count with In Progress Inventory Adjustments, the user may return to the stock count to complete the inventory adjustments or to continue and ignore the adjustments. When the user is approving an inventory adjustment with items on an open stock count, a message is displayed allowing the user to determine if further processing should be undertaken. Similar logic to how late sales is processed will be used for these adjustments. No: When the user is confirming a Stock Count in the Authorization phase and there are items on the stock count with In Progress Inventory Adjustments the system ignores the inventory adjustments and allows the user to complete the count. When the user is approving an inventory adjustment, there is no additional processing. Note: The system will process the inventory adjustment like how late sales are processed and determine if the stock count should be adjusted or not. The update to the stock count is not immediate but rather is at the time of authorization if there are reversing entries created. |
No |
Stock Counts |
Boolean |
Stock Count Default Timeframe |
Values: Before Store Open/After Store Close This parameter defines when the stock count is performed in relation to the store opening hours for Daily Sales Processing. This value may be overridden at the time of the stock count if the system is configured to allow the override. If an override is allowed, this setting will determine the default value displayed. Before Store Open: The stock count is performed before the opening of the store. All sales on the day of the stock count will only update SOH. It will not update any counted quantities. After Store Close: The stock count is performed after the closing of the store. All sales on the day of the stock count will update both SOH and any counted quantities. If using RMS, After Store Close must be selected. Note: Timestamp processing does not use this parameter. |
Before Store Open |
Stock Counts |
Integer |
Display Delivery Timeslot |
Values: Yes/No Yes: The Delivery Timeslot fields will display throughout Store Orders as well as the Admin screen Delivery Timeslots. No: The Delivery Timeslot fields will NOT display throughout Store Orders as well as the Admin screen Delivery Timeslots. |
Yes |
Store Order |
Boolean |
DSD Delivery Supplier for Store Order |
Values: Yes/No This indicator will check to see if the DSD allowed indicator needs to be yes when adding a supplier restriction when creating a store order. Yes: The system needs to check the DSD indicator (Indicator on Supplier table which determines whether a supplier can create a new Purchase Order) when creating a new Store Order. If the indicator is set to 'Yes' the supplier can be added. If it is set to 'No', the supplier cannot be added. No: The DSD indicator on the supplier does not need to be checked. |
Yes |
Store Order |
Integer |
Enable Area for Store Order |
Values: Yes/No Yes: The Area will display throughout Store Orders. No: The Area field will NOT display throughout Store Orders. |
Yes |
Store Order |
Boolean |
Supplier Restriction for Store Order |
Values: Enabled / Required / Disabled Enabled: Supplier will be available as a restriction when creating and searching for a store order. Required: Supplier will be available as a restriction when creating and searching for a store order. When creating it will also be required. Disabled: Supplier will not be available as a restriction when creating a store order. |
Enabled |
Store Order |
Integer |
Warehouse Restriction for Store Order |
Values: Enabled / Required / Disabled Enabled: Warehouse will be available as a restriction when creating and searching for a store order. Required: Warehouse will be available as a restriction when creating and searching for a store order. When creating it will also be required. Disabled: Warehouse will not be available as a restriction when creating a store order. |
Enabled |
Store Order |
Integer |
Auto Generate Item Tickets for Clearance Price Changes |
Values: Yes/No Yes: When a clearance price event comes from the pricing system, a new item ticket is sent to the ticketing dialogue. No: When a clearance pricing event comes from the pricing system, the system does not generate an item ticket. This determines whether the system must auto generate item tickets in the system when there is a clearance price event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Generate Item Tickets for Description Changes |
Values: Yes/No Yes: When a new description comes from the merchandising system, a new item ticket is sent to the ticketing dialogue. No: When a new description comes from the merchandising system, the system does not generate an item ticket. This configuration will be used to auto send item tickets to ticketing when an item description is updated and sent to EICS. |
No |
Ticketing |
Boolean |
Auto Generate Item Tickets for Promotion Price Changes |
Values: Yes/No Yes: When a promotion price event comes from the pricing system, a new item ticket is sent to the ticketing dialogue. No: When a promotion pricing event comes from the pricing system, the system does not generate an item ticket. This determines whether the system must auto generate item tickets in EICS when there is a promotion price event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Generate Item Tickets for Regular Price Changes |
Values: Yes/No Yes: When a regular price change comes from the pricing system, a new item ticket is sent to the ticketing dialogue. No: When a regular price change comes from the pricing system, the system does not generate an item ticket. This determines whether the system must auto generate item tickets in EICS when there is a regular price change event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Generate Shelf Edge Labels for Clearance Price Changes |
Values: Yes/No Yes: When a clearance price event comes from the pricing system, a shelf edge label is sent to the ticketing dialogue. No: When a clearance pricing event comes from the pricing system, the system does not generate a label. This determines whether the system must auto generate item tickets in the system when there is a clearance price event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Generate Shelf Edge Labels for Description Changes |
Values: Yes/No Yes: When a new description comes from the merchandising system, a shelf edge label is sent to the ticketing dialogue. No: When a new description comes from the merchandising system, the system does not generate a label. This configuration will be used to auto generate labels when an item description is updated and to send to EICS. |
No |
Ticketing |
Boolean |
Auto Generate Shelf Edge Labels for Promotion Price Changes |
Values: Yes/No Yes: When a promotion price event comes from the pricing system, a new shelf edge label is sent to the ticketing dialogue. No: When a promotion pricing event comes from the pricing system, the system does not generate a label. This determines whether the system must auto generate labels in EICS when there is a promotion price event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Generate Shelf Edge Labels for Regular Price Changes |
Values: Yes/No Yes: When a regular price change comes from the pricing system, a new shelf edge label is sent to the ticketing dialogue. No: When a regular price change comes from the pricing system, the system does not generate a label. This determines whether the system must auto generate labels in EICS when there is a regular price change event coming in from the pricing system. |
No |
Ticketing |
Boolean |
Auto Ticket Generate Future Days |
Values: 0 – 99 This parameter indicates the number of days the system must consider for future day events for generating tickets when the batch is run. If it is set to 0, it means the system will not consider the future events. If the value is above zero, the system will consider the price events that are falling in the range of current date plus the number of days set in this parameter to generate the tickets. |
0 |
Ticketing |
Integer |
Item Print Events |
This is to determine the default item price events for the ticket printing. Values: Always, Clearance, Promotion, Permanent, Clearance or Permanent and Any Price Event Always: This option will always print a ticket regardless of if there is a price change. Clearance: Only print a ticket if on the specific date any clearance event is effective. So, for Clearance 2, that means today's date + 2 days, if the item on that day has a clearance going on, print the clearance ticket. Promotion: Only print a ticket if on the specific date any promotion event is effective. Regular or Clearance: Only print a ticket if on the specific date any Regular or Clearance event is getting effective. Permanent: Only print a ticket if on the specific date any Regular event of getting effective. Any Price Event (Promotion, Clearance or Permanent (Regular)): Based on the date selected, if any price event goes into effect (clearance, promotion or regular price a ticket. If no price event goes into effect, print nothing). |
Always |
Ticketing |
String |
Maximum Ticket Quantity to Print |
This is to determine the maximum ticket size to print in one command. This is used in auto ticket printing batch and ticketing dialogue. |
500 |
Ticketing |
Boolean |
Auto Close Receipt |
Values: 1-99 0: close the receipt immediately 1: close the receipt the end of day today 2: close the receipt end of day tomorrow X: close end of day x days starting from today the batch program will auto close any transfer receipts and marks all non-received containers to missing. Partially received containers will be marked as damaged. |
1 |
Transfer Receiving |
Integer |
External Finisher Auto Receive |
Values: Not Allowed, External Message, Date Driven Not allowed will make the system work as today. External message will receive the full external finisher delivery with a Source Type of 'Finisher', the moment an ASN transaction arrives that indicates that the delivery needs to be auto received. Date Driven will look at a secondary store option (External Finisher Auto Receive number of Days) to determine how many days the transaction stays open before it is fully received. If it is set to 0, it will auto-receive on the ETA date. |
Not Allowed |
Transfer Receiving |
Integer |
External Finisher Auto Receive Number of Days |
Values: 0-999 A batch program will auto receive any external finisher deliveries with a Source Type of 'Finisher', that have not been closed x-days after the ETA date or the create date depending on if the ETA date is set or not and if the auto receive external delivery parameter is set 0 means immediate receiving 1 means today (EOD) 2 means EOD tomorrow x means EOD x days starting from today |
0 |
Transfer Receiving |
Integer |
Store Auto Receive |
Values: Not allowed / External message / Date Driven Not allowed: Auto receiving is not allowed for the store. External message: Receives the full store delivery the moment an ASN transaction arrives when the indicator on the ASN identifies this as an auto receive delivery and the Source Type is 'Store'. This parameter works with the Store Auto Receive screen. Date Driven: Receives the delivery automatically when the date is reached. A second options, 'Store Auto Receive Number of Days' is used to determine how many days the transaction stays open before it is fully received. If it is set to 0, it will receive immediately when the transfer is shipped. This parameter works with the Store Auto Receive screen. |
Not Allowed |
Transfer Receiving |
Integer |
Store Auto Receive Number of Days |
Values: 0-99 0: immediate receiving 1: end of day today 2: end of day tomorrow X: end of day x days starting from today The batch program will auto receive any transfers with a Source Type of 'Store' not previously closed x-days after they have been shipped. This parameter is only used when the Store Auto Receive parameter is enabled. |
0 |
Transfer Receiving |
Integer |
Store Transfer Default to ShopFloor Receive |
Values: Yes/No This parameter determines whether the receiving will default to receive inventory into the shop floor instead of automatically receiving into the back room or delivery bay when the source type is 'Store'. Yes: The Transfer workflow will default to receive inventory into the shop floor when the Source Type is 'Store'. The shop floor inventory bucket will be incremented instead of the backroom or delivery bay bucket. If a capacity is defined for the item, the maximum shop floor quantity will equal the capacity; otherwise, the shop floor will be updated to the entire receipt amount. If the capacity is used and if the receiving quantity is excess, the balance is incremented to delivery bay or back room depending on the Replenishment. No: This will default to back room or delivery bay depending on the Replenishment -Delivery Bay Inventory parameter and all inventory will be automatically received into the back room or delivery bay when Source Type is 'Store'. Note: With the proper permissions, the user will still have the option to receive onto the shop floor while receiving the delivery by changing the default to Shop Floor. Damaged inventory will not move to shop floor. |
No |
Transfer Receiving |
Boolean |
Store Transfer Receive Item Capacity |
Values: Yes/No This parameter will determine whether the capacity will be considered while receiving the deliveries. Yes: If the value is set to YES, then while receiving and Source Type of 'Store', the capacity will be considered. For example: If capacity is 50, receipt is for 100 and Available SOH is 10 on shopfloor, then if this parameter is on and receive in shop floor is checked then 40 (un-damaged) will be moved to shop floor and rest to back room. No: If the value is set to NO, then while receiving the capacity will not be considered. Damaged inventory will not move to shop floor. |
No |
Transfer Receiving |
Boolean |
Warehouse Auto Receive |
Values: Not Allowed, External Message, Date Driven This parameter will drive the following functionality. Not Allowed will make the system work as today. External message will receive the full warehouse delivery the moment an ASN transaction arrives that indicates that the delivery needs to be auto received and the Source Type is 'Warehouse'. Date Driven will look at a secondary store option (Warehouse Auto Receive number of Days) to determine how many days the transaction stays open before it is fully received. If it is set to 0, it will auto-receive on the ETA date. |
Not Allowed |
Transfer Receiving |
Integer |
Warehouse Auto Receive Number of Days |
Values: 0-99 0: immediate receiving 1: end of day today 2: end of day tomorrow X: end of day x days starting from today The batch program will auto receive any transfers with a Source Type of 'Warehouse' not previously closed x-days after they have been shipped. This parameter is only used when the Warehouse Auto Receive parameter is enabled. |
0 |
Transfer Receiving |
Integer |
Warehouse Default to ShopFloor Receive |
Values: Yes/No This parameter determines whether the receiving will default to receive inventory into the shop floor when source type is 'Warehouse' instead of automatically receiving into the back room or delivery bay when the source type is 'Warehouse'. Yes: The Transfer receiving workflow will default to receive inventory into the shop floor when the Source Type is 'Warehouse'. The shop floor inventory bucket will be incremented instead of the backroom or delivery bay bucket. If a capacity is defined for the item, the maximum shop floor quantity will equal the capacity; otherwise, the shop floor will be updated to the entire receipt amount. If the capacity is used and if the receiving quantity is excess, the balance is incremented to delivery bay or back room depending on the Replenishment - Delivery Bay Inventory parameter. No: This will default to back room or delivery bay depending on the Replenishment -Delivery Bay Inventory parameter and all inventory will be automatically received into the back room or delivery bay when Source Type is 'Warehouse'. Note: With the proper permissions, the user will still have the option to receive onto the shop floor while receiving the delivery by changing the default to Shop Floor. Damaged inventory will not move to shop floor. |
No |
Transfer Receiving |
Boolean |
Warehouse Receive Item Capacity |
Values: Yes/No This parameter will determine whether the capacity will be considered while receiving the deliveries. Yes: If the value is set to YES, then while receiving and Source Type of 'Warehouse', the capacity will be considered. For example: If capacity is 50, receipt is for 100 and Available SOH is 10 on shopfloor, then if this parameter is on and receive in shop floor is checked then 40 (un-damaged) will be moved to shop floor and rest to back room. No: If the value is set to NO, then while receiving the capacity will not be considered. Damaged inventory will not move to shop floor |
No |
Transfer Receiving |
Boolean |
Dispatch Validate |
Values: Ship Direct, Ship Submit Ship Direct: SIOCS will control all processes. The user will be able to go from create/edit directly to dispatch. Ship Submit: This option will require the user to press the Submit button and require a specific press of the dispatch button. An additional option is that an external system will generate a dispatch message through a standard web service. |
Ship Direct |
Transfer Receiving |
Integer |
Capture Vehicle Details on Submit |
Values: Yes/No Yes: The details regarding the vehicle/driver who is handling the shipment, should be captured before submitting a transfer shipment No: The shipment can be submitted without the details regarding the vehicle/driver |
No |
Transfer Shipment |
Boolean |
Pre-shipment Notification |
Values: Yes/No This parameter will drive the following functionality: Yes: The system will publish a pre-shipment message. No: The system will not publish a pre-shipment message. |
No |
Transfer Shipment |
Boolean |
Restrict Shipment Dispatch After Submit |
Values: Yes/No Yes: This restriction will not allow the user to move a transfer Shipment from Submitted to Dispatched status unless the Fiscal Doc ID/E-way Bill ID has been filed in. No: The shipment can be dispatched without Fiscal Doc ID/E-way Bill ID |
No |
Transfer Shipment |
Boolean |
Ship to Finisher Carrier Default |
Values: Sender / Receiver / Third Party Sender: Sender will be selected for Carrier Type on BOL Receiver: Receiver will be selected for the Carrier type on BOL. Third Party: Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to "Other". When creating a store to Finisher transfer the Carrier Type on the BOL will default initially based upon this parameter. The user can still change this value and if so, that will be the value used on the transfer. |
Third Party |
Transfer Shipment |
Integer |
Ship to Store Carrier Default |
Values: Sender / Receiver / Third Party Sender: Sender will be selected for Carrier Type on BOL Receiver: Receiver will be selected for the Carrier type on BOL. Third Party: Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to "Other". When creating a store to store transfer the Carrier Type on the BOL will default initially based upon this parameter. The user can still change this value and if so, that will be the value used on the transfer. |
Third Party |
Transfer Shipment |
Integer |
Ship to Warehouse Carrier Default |
Values: Sender / Receiver / Third Party Sender: Sender will be selected for Carrier Type on BOL Receiver: Receiver will be selected for the Carrier type on BOL. Third Party: Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to "Other". When creating a store to WH transfer the Carrier Type on the BOL will default initially based upon this parameter. The user can still change this value and if so, that will be the value used on the transfer. |
Third Party |
Transfer Shipment |
Integer |
Auto Accept External Generated Request |
Values: Yes/No This parameter automatically approves the requested transfer and defaults the requested quantity to the accepted quantity for externally generated requests. |
No |
Transfers |
Boolean |
Auto Accept Store Transfer Request |
Values: Yes/No This parameter automatically approves the requested transfer and defaults the requested quantity to the accepted quantity for store to store requests. |
No |
Transfers |
Boolean |
Context Type/Value required for Transfer |
Values: Yes/No Yes: Capturing of context type and value is mandatory before requesting a transfer No: Capturing of context type and value is not mandatory before requesting a transfer |
No |
Transfers |
Boolean |
Not After Date Default Days |
Values: 0-999 This parameter adds a value to the current date and uses the value to default the 'Not After Date' when creating a transfer or requesting a transfer. Documents will be closed via batch when this date is reached. |
30 |
Transfers |
Integer |
Manifest Customer Order Deliveries |
Values: Yes/No Yes: The Manifesting system will be called. No: The Manifesting system will not be called. |
No |
Web Service Enablement |
Boolean |
Manifest RTV to Supplier |
Values: Yes/No Yes: The Manifesting system will be called for return to supplier. No: The Manifesting system will not be called. Note: The interface will still need to be implemented; this just is to determine if it will be called. |
No |
Web Service Enablement |
Boolean |
Manifest Transfer to Finisher |
Values: Yes/No Yes: The Manifesting system will be called for transfer to Finisher. No: The Manifesting system will not be called. Note: The interface will still need to be implemented; this just is to determine if it will be called. |
No |
Web Service Enablement |
Boolean |
Manifest Transfer to Store |
Values: Yes/No Yes: The Manifesting system will be called for transfer to store. No: The Manifesting system will not be called. Note: The interface will still need to be implemented; this just is to determine if it will be called. |
No |
Web Service Enablement |
Boolean |
Manifest Transfer to Warehouse |
Values: Yes/No Yes: The Manifesting system will be called for transfer to warehouse No: The Manifesting system will not be called. Note: The interface will still need to be implemented; this just is to determine if it will be called. |
No |
Web Service Enablement |
Boolean |
OBCS Customer Order Delivery Validation |
Values: Yes/No Yes: SIOCS-OBCS Integration will be enabled No: SIOCS-OBCS Integration will not be enabled |
No |
Web Service Enablement |
Boolean |
OBCS Customer Order Delivery Validation |
Values: Yes/No Yes: SIOCS-OBCS Integration will be enabled No: SIOCS-OBCS Integration will not be enabled |
No |
Web Service Enablement |
Boolean |
OMS Customer Order Delivery Query Address |
Values: Yes/No Yes: query the address from an external service as part of processing in: submitting an order, delivering an order, or reading the address for usage in UI. No: address will not be queried from external system. |
No |
Web Service Enablement |
Boolean |
OMS Customer Order Delivery Validation |
Values : Yes/No Yes: When confirming the delivery, the system will make a call out to an external system (such as an OMS) to validate the delivery status and delivery quantities before completing the dispatch. No: external system will not be called. |
No |
Web Service Enablement |
Boolean |
Sales Forecast Data |
Yes: The web service for Sales Forecast Data will be called. No: The web service for Sales Forecast Data will NOT be called. |
No |
Web Service Enablement |
Boolean |
Send Event Alert External |
Values: Yes / No Yes: Notification event alerts (non ad hoc notifications) will be sent externally via web service. No: Notification event alerts (non ad hoc notifications) will not be sent externally. Web service is not called. |
No |
Web Service Enablement |
Boolean |
Permissions
Table 8-3 Security Permissions
Permission | Topic | Usage |
---|---|---|
Access Ad Hoc Stock Count Tolerances |
Admin |
With this permission, the user will have access to the Ad hoc Stock Count Tolerance dialog. |
Access Admin |
Admin |
With this permission, the user will have access to the Admin menu. |
Access Auto-Receive Stores |
Admin |
With this permission, the user will have access to the Auto Receive Stores admin dialog. |
Access Barcode Processor |
Admin |
With this permission, the user will have access to the Barcode Processor dialog. |
Access Buddy Stores |
Admin |
With this permission, the user will have access to the Buddy Store dialog. |
Access Carrier Services |
Admin |
With this permission, the user can access the Carrier Service dialog to add and edit the carrier service data. |
Access Carriers |
Admin |
With this permission, the user can access the Carrier dialog to add or edit the carrier data. |
Access Code Info |
Admin |
With this permission, the user can access the Code Info dialog to add, edit and delete code information. |
Access Container Lookup |
Admin |
With this permission, the user will have access to the Container Lookups dialog. |
Access Credential Administration |
Admin |
With this permission, the user will have access to the Credential Administration Screen. Without this permission, the user will not have access to the Credential Administration Screen. |
Access Customer Order Picking Tolerances |
Admin |
With this permission, the user will have access to the Customer Order Picking Tolerance dialog. |
Access Data Seed |
Admin |
With this permission the user will have the ability to start the data seeding job via the batch job admin. |
Access Delivery Timeslot |
Admin |
User must have this permission in order for the Delivery Timeslot menu option to be available within the Data Setup menu. With this permission the user will be able to do all operations on this screen. |
Access DCS Work Types |
Admin |
With this permission, a sysop user will have access to the DCS Work Type screen in the desktop application. |
Access Extended Attribute |
Admin |
With this permission, the Extended Attributes Menu option is displayed under Admin/Configuration and the user gets the ability to setup and assign extended attributes. |
Access Extended Attribute Dept Assign |
Admin |
With this permission, the Assign Extended Attributes Menu option is displayed under Admin/Configuration and the user gets the ability to assign new extended attributes and also remove the existing assignments. |
Access Extended Attribute Setup |
Admin |
With this permission, the Setup Extended Attributes Menu option is displayed under Admin/Configuration and the user gets the ability to view and edit extended attributes. |
Access External Service Administration |
Admin |
With this permission, the user will have access to the External Service Admin screen. |
Access File Transfer Service |
Admin |
With this permission, the user will be able to access File Transfer Service screen |
Access Finisher Lookup |
Admin |
With this permission, the user will have access to the Finisher Lookup functionality. |
Access Fiscal Document External Reference Link URL |
Admin |
With this permission, the user will be able to view the Fiscal Doc URL |
Access Flexible Attributes |
Admin |
With this permission, the user will have access to the Custom Flexible Attributes dialog and can setup (Create) and Delete flexible attributes. Note that CFAs are not editable once created due to data integrity. |
Access Future Price Events |
Admin |
Desktop: With this permission, 'Future Price Events' will also be listed in the Price Events screen in Item Lookup. Without this permission, 'Future Price Events' will not be listed in the Price Events screen. Mobile: With this permission, the user will be able to view future price events in Pricing of Item Lookup. Without this permission, the user will only be able to see current and past events. |
Access Initial Data Load |
Admin |
With this permission the user will have access to the Initial Data Load dialog. Without this permission the user will not have access to the Initial Data Load dialog. |
Access Integration Dashboard |
Admin |
On desktop application, with this permission, the user can access the Integration dashboard. |
Access Inventory Adjustment Reasons |
Admin |
With this permission, the user will have access to the Inventory Adjustment Reason admin dialog and the ability to setup and maintain inventory adjustment reason codes. |
Access Fiscal Doc URL |
Admin |
With this permission, the user will be able to view the Fiscal Doc URL |
Access Inventory Management |
Admin |
With this permission, the user will have access to the Inventory Management. |
Access ISN Types |
Admin |
With this permission, user will be able to access the ISN Types dialog in the desktop application. |
Access Item CFAs |
Admin |
With this permission, the CFAs will be available on Item Detail in Item Lookup |
Access Item Lookup |
Admin |
With this permission, the user will have access to the Item Lookup functionality. |
Access Item Maintenance |
Admin |
With this permission the user will be able to access the Item Maintenance screen in JET Mobile |
Access Item Scan Number Lookup |
Admin |
With this permission, the user can access the Item Scan Number Lookup. |
Access Job Admin |
Admin |
With this permission, the user can access the Job admin dialog. |
Access Job Scheduler |
Admin |
With this permission, the user can access the Job scheduler dialog. |
Access Lookup |
Admin |
With this permission, the user will have access to functionality within Lookups. |
Access MPS Staged Messages |
Admin |
User must have this permission in order to access the MPS Staged Messages screen to view or edit the inbound and outbound messages. |
Access MPS Work Types |
Admin |
User must have this permission in order to Access or Edit the Worker Type settings. |
Access Operational Issues |
Admin |
With this permission, the user can access the Operational Issues dialog. |
Access Operational Views menu |
Admin |
On EICS, with this permission, the operational views main menu is displayed, and user is allowed to view the different operational views. |
Access Package Size |
Admin |
With this permission the user will have access to the Package Size admin dialog. |
Access POS Transaction Resolution List |
Admin |
On desktop application, with this permission, the user can access the Transaction Resolution dialogue. |
Access Price Events |
Admin |
With this permission, 'View Price Events' button will be available in the Item Detail screen hence the user will be able to access the Price Events screen. |
Access Printer Setup |
Admin |
With this permission, the user can access the printer setup dialog. |
Access Product Group Schedules |
Admin |
With this permission the user will have access to the Product Group Schedule dialog. |
Access Product Groups |
Admin |
With this permission, the user will have access to the admin Product Group and Product Group Component functionality |
Access Reports |
Admin |
With this permission, the user can access the Reports dialog. |
Access RFID Locator |
Admin |
With this permission, the user can access the RFID Locator dialog in mobile. |
Access Sequence Admin |
Admin |
With this permission the user will have the Sequence Admin menu option under Technical Maintenance menu. |
Access SIOCS Managed Stores |
Admin |
With this permission, the user will have access to the SIOCS Managed Stores screen in EICS. |
Access Shipment Reasons |
Admin |
With this permission, the user will have access to the Shipment Reason admin dialog and the ability to setup and maintain shipment reason codes. |
Access Shipping Receiving |
Admin |
With this permission, the user will have access to functionality within Shipping/Receiving. |
Access Store Administration |
Admin |
With this permission, the user will have access to Store Administration dialog. |
Access Store Administration Default |
Admin |
With this permission, the user will have access to Store Administration default dialog. |
Access Store Shipping Network |
Admin |
With this permission, the user will have access to the Store Shipping Network screen in the desktop application. |
Access Sub Buckets |
Admin |
With this permission, the user can access the Sub bucket dialog. |
Access Supplier CFAs |
Admin |
With this permission, the CFAs will be available on Supplier Detail in Supplier Lookup. |
Access Supplier Lookup |
Admin |
With this permission the user will have access to Supplier Lookup and the Supplier Lookup menu option will appear in the drawer (main menu). |
Access System Administration |
Admin |
With this permission, the user will have access to the System Administration dialog. |
Access Technical Maintenance |
Admin |
With this permission, the user will have access to Technical Maintenance dialog. |
Access Transaction History |
Admin |
With this permission the user will have access to the Transaction History dialog. |
Access Translation Setup |
Admin |
With this permission, the user can access the Translation Setup dialog. |
Access Troubled Transaction |
Admin |
With this permission, the user can select the Troubled Transaction List from the Inventory Management menu. |
Access UDAs |
Admin |
With this permission, in Item Lookup the user will be able to search for an item by a search type of UDA. Also, the UDAs will be available on Item Detail in Item Lookup. |
Access UDA Print Setup |
Admin |
With this permission, the user can access the UDA Print Setup dialog in the desktop application. |
Access UIN Label Setup |
Admin |
With this permission, the user can access the UIN Label Setup dialog in the desktop application. |
Access Unit of Measure |
Admin |
User must have this permission in order for the Unit of Measure menu option to be available within the Configuration menu. With this permission the user will be able to do all operations on this screen. (Add ""+"", Remove ""-"" and Edit). |
All Stores Product Groups |
Admin |
With this permission, Product Groups for All Stores can be created as well as edited. Without this permission, Product Groups cannot be created for all stores, and they can only be viewed for all stores. |
Allow Bulk Scan |
Admin |
With this permission, the user will have access to the Bulk Scan dialog. The Bulk Scan menu option will be in the footer menu of applicable transaction item list screens. The Bulk scan type will be available as a scan mode in the mode bar. |
Allow Operational Issue Batch Execution Delete |
Admin |
With this permission, the user will be able to delete the issues in Bulk Import, Transaction Execution and Data Purge tasks via Operational Issues Dialog. |
Create Item Scan Number |
Admin |
With this permission, the user is allowed to create a new item scan number in the system. |
Create Notes |
Admin |
With this permission, the user will be able to add notes within the notes dialog. |
Create Product Group Schedules |
Admin |
With this permission, the user can create new Product Group Schedules. |
Create Product Groups |
Admin |
With this permission, the user will be able to create a new Product Group. |
Create Translations |
Admin |
With this permission, the user can create new translations. |
Delete Initial Data Load |
Admin |
With this permission the user will have the Delete Data button. Without this permission the user will not have the Delete Data button. |
Delete Item Scan Number |
Admin |
With this permission, the user is allowed to delete an existing Item Scan Number. |
Delete MPS Staged Messages |
Admin |
User must have this permission in order to delete the inbound and outbound messages. |
Delete Product Group Schedules |
Admin |
With this permission, the user can delete Product Group Schedules. |
Delete Product Groups |
Admin |
With this permission, the user can delete a Product Group. |
Display Stock Locator |
Admin |
With this permission, the user will have access to Stock Locator within Item Lookup. |
Edit Item Scan Number |
Admin |
With this permission, the user is allowed to edit an existing Item Scan Number. Applicable for webservice operation. |
Edit Item Scan Number CDA |
Admin |
This is required for web service action to edit the Item Scan number CDAs. |
Edit Job Schedules |
Admin |
With this permission the user can edit Job Schedules. |
Edit POS Transaction |
Admin |
On desktop application, with this permission, the user can edit the troubled pos transaction message. |
Edit Product Group Schedules |
Admin |
With this permission, the Product Group Schedule will be editable. |
Edit Product Groups |
Admin |
With this permission, the user can Edit an existing Product Group which also includes adding and removing Product Group Components. |
Edit UDA Print Setup |
Admin |
With this permission, the user can edit the UDA Print Setup values in the desktop application. |
Submit Initial Data Load |
Admin |
With this permission the user will have the Submit Seed button. Without this permission the user will not have the Submit Seed button. |
Update Resolution Status |
Admin |
With this privilege the Resolve/Reset button on the Troubled Transactions List screen will be displayed and enabled. |
Update UIN Status |
Admin |
With this permission, the user can update the status of the UIN from the history screen. |
View UIN History |
Admin |
With this permission, the user will be able to access the UIN Lookup feature and view the history in EICS. |
Warehouse Inventory Access |
Admin |
With this permission, the warehouse inventory details will be included in the Stock Locator Item Lookup section. |
Access Area |
Area |
With this permission, the user will have access to the Area dialog. |
Confirm Area |
Area |
With this permission, the user will be able to Confirm an Area. |
Create Area |
Area |
With this permission, the user will be able to create Areas. |
Delete Area |
Area |
With this permission, the user will be able to delete an Area. |
Edit Area |
Area |
With this permission, the user will be able to edit active Areas. |
Access Customer Details |
Customer Order |
With this permission the user will have access to the Customer Details (name, address, and so on) associated with the customer order. |
Access Customer Order |
Customer Order |
With this permission, the user will have access to Customer Orders dialog. |
Access Customer Order Delivery |
Customer Order |
With this permission, a user can access the Customer Order Delivery dialog. |
Access Customer Order Delivery Attribute |
Customer Order |
With this permission, the user is allowed to view the extended attributes in the functional dialog.. |
Access Customer Order Management |
Customer Order |
With this permission, the user will have access to the Customer Order Management operations within the drawer/menu. |
Access Customer Order Pick |
Customer Order |
With this permission, the user will have access to the Customer Order Picking dialog. |
Access Customer Order Quick Flow |
Customer Order |
With this permission, Customer Orders will display on the Open Transaction. This is for JET Mobile Quick Flow. Go to Transaction option will exist in Notifications. |
Access Customer Order Reverse Pick |
Customer Order |
With this permission, the user will have access to the Customer Order Reverse Picking dialog. |
Allow dispatch without Fiscal Document IDL |
Customer Order |
With this permission, the user will be able to dispatch the shipment without the Fiscal Doc ID/E-way bill ID being available. |
Cancel Submit Customer Order Delivery |
Customer Order |
With this permission, the user will be able to Cancel Submit a “Submitted” status Customer Order Delivery that is a “web order. |
Confirm Customer Order Pick |
Customer Order |
With this permission, the user can Confirm a customer order pick. |
Confirm Customer Order Reverse Pick |
Customer Order |
With this permission, the user will be able to Confirm a customer order reverse pick. |
Create Customer Order Delivery |
Customer Order |
With this permission, the user can create a new delivery for a Customer Order that is a “web order”. Used in conjunction with Create Customer Order Delivery for Shipment or Create Customer Order Delivery for Pickup permission. This permission must also exist in order to create a delivery that is not a web order from an external system. |
Create Customer Order Delivery for Pickup |
Customer Order |
With this permission, the user will be able to create Customer Order Deliveries which are of type store pickup. Used in conjunction with the Create Customer Order Delivery permission. |
Create Customer Order Delivery for Shipment |
Customer Order |
With this permission, the user will be able to create Customer Order Deliveries which are of type store shipment. Used in conjunction with the Create Customer Order Delivery permission. |
Create Customer Order Pick |
Customer Order |
With this permission, the user will be able to create customer order picks. Picks can be created from within a Customer Order (for a single customer order pick). Picks can be created from within Customer Order Picking. |
Create Customer Order Reverse Pick |
Customer Order |
With this permission, the user will be able to create customer order reverse picks. |
Delete Customer Order Delivery |
Customer Order |
With this permission, the user will be able to delete a customer order delivery that is a “web order”. |
Delete Customer Order Pick |
Customer Order |
With this permission, the user will be able to delete a customer order pick. |
Delete Customer Order Reverse Pick |
Customer Order |
With this permission, the user will be able to delete a customer order reverse pick. |
Dispatch Customer Order Delivery |
Customer Order |
With this permission, the user can Dispatch a Customer Order Delivery that is a “web order". |
Dispatch Incomplete Customer Order Delivery |
Customer Order |
When dispatching a delivery that requires full delivery (Allow Partial Delivery = ‘No’), the entire delivery must be delivered in full. With this permission, the user will get a warning message and will be able to continue the dispatch without full delivery. Without this permission the delivery must be in full. |
Edit Customer Order BOL |
Customer Order |
With this permission, the user will be able to edit the details of the Bill of Lading associated with a customer order delivery. This is done in the Edit Delivery screen. User must also have Edit Customer Order Delivery permission. |
Edit Customer Order CFA |
Customer Order |
With this permission, the user will be able to capture CFAs for a customer order. |
Edit Customer Order Delivery |
Customer Order |
With this permission, the user can edit an existing delivery for a Customer Order that is a “web order”. |
Edit Customer Order Delivery Attribute |
Customer Order |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit Customer Order Delivery CFA |
Customer Order |
With this permission, the user will be able to capture CFAs for a Customer Order Delivery |
Edit Customer Order Pick |
Customer Order |
With this permission, the user will be able to edit active customer order picks. |
Edit Customer Order Pick CFA |
Customer Order |
With this permission, the user will be able to capture CFAs for a Customer Order Pick. |
Edit Customer Order Reverse Pick |
Customer Order |
With this permission, the user will be able to edit active reverse picks |
Edit Customer Order Quick Flow |
Customer Order |
With this permission the user will be able to edit (assuming proper status) in the customer order quick flow, which may include picking, rejecting, and pickup / shipment. |
Edit Customer Order Quick Flow Quantity |
Customer Order |
With this permission the user will be able to click on the item quantity and the quantity widget will open to edit the quantity. Without this permission, the quantity is not editable and only scanning is allowed. |
Edit Customer Order Reverse Pick CFA |
Customer Order |
With this permission, the user will be able to capture CFAs for a Customer Order Reverse Pick |
Edit Quantity Delivery |
Customer Order |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity.User must also have Edit Customer Order Delivery permission as well.Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Quantity Picking |
Customer Order |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity.User must also have Edit Customer Order Pick permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Quantity Reverse Picking |
Customer Order |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity.User must also have Edit Customer Order Reverse Pick permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Item Substitution For Picking |
Customer Order |
With this permission, the user will have access to the Item Substitution dialog within Customer Order Picking. |
Reject Customer Order |
Customer Order |
With this permission, the user will be able to Reject a Customer Order. |
Submit Customer Order Delivery |
Customer Order |
With this permission, the user will be able to Submit a Customer Order Delivery that is a “web order”. Used in conjunction with Modify Customer Order Delivery permission. |
View Customer Order BOL |
Customer Order |
With this permission, the user can access and view the details of the Bill of Lading associated with a customer order delivery. |
Container Items Limited To |
Data |
With this permission, the user can access data criteria associated with adding items to a container. This is selected by each individual criterion. |
Counting Method |
Data |
With this permission, the user can access specific counting methods. This is selected by each individual counting method. |
Department |
Data |
With this permission, the user can access specific department. This is selected by each individial department code. |
Display List Diff Types |
Data |
With this permission, the user can access the display of diff types. This is selected by each individual diff type. |
Inventory Adjustment Reason Code |
Data |
With this permission, the user can access specific inventory adjustment reason codes. This is selected by each individual reason code. |
Item Basket Types |
Data |
With this permission, the user can access specific item basket types. This is selected by each individual basket types. |
Location Types |
Data |
With this permission, the user can access specific location types. This is selected by each individual location type. |
Print Format Type |
Data |
With this permission, the user can access specific print format types. This is selected by each individual format type. |
Product Group Type |
Data |
With this permission, the user can access specific product group types. This is selected by each individual product group type. |
Role Type |
Data |
With this permission, the user can access specific role types. This is selected by each individual role type. |
RTV Reason Code |
Data |
With this permission, the user can access specific RTV reason codes. This is selected by each individual reason code. |
RTV Shipment Reason Code |
Data |
With this permission, the user can access specific RTV shipment reason codes. This is selected by each individual reason code. |
Scan List Type |
Data |
With this permission, the user can access specific scan list types. This is selected by each individual scan list type. |
Shelf Adjustment Type |
Data |
With this permission, the user can access specific shelf adjustment types. This is selected by each individual adjustment type. |
Shelf Replenishment Type |
Data |
With this permission, the user can access specific shelf replenishment types. This is selected by each individual type. |
Store Order Delivery Timeslots |
Data |
With this permission, the user can access specific delivery timeslots. This is selected by each individual timeslot. |
Transaction Type |
Data |
With this permission, the user can access specific transaction types. This is selected by each individual transaction type. |
Transfer Destination Type |
Data |
With this permission, the user can access specific transfer destination types. This is selected by each individual transfer destination type. |
Transfer Shipment Reason Code |
Data |
With this permission, the user can access specific transfer destination types. This is selected by each individual transfer destination type. |
Access Adjust Container DSD Receiving |
DSD Receiving |
With this permission, the user will be able to adjust the container in a delivery. |
Access Confirm Container DSD Receiving |
DSD Receiving |
With this permission, the user can confirm the container receipt from the supplier. |
Access Confirm DSD Receipt |
DSD Receiving |
With this permission, the user will be able to confirm the Direct store delivery. |
Access Create Container |
DSD Receiving |
With this permission, the user can create a new container in the DSD receipt. |
Access Delete Container |
DSD Receiving |
With this permission, the user can delete a container. |
Access Delete Receipt |
DSD Receiving |
With this permission, the user will be able to delete a direct store delivery. |
Access Document DSD Receiving |
DSD Receiving |
With this permission, the user will be able to select the PO to apply items on the receipt.User must also have Edit container and Modify container permissions in order to do this operation. |
Access DSD Receiving |
DSD Receiving |
With this permission, the user will have access to the DSD Receiving dialog. |
Access DSD Receiving Ext. Attribute |
DSD Receiving |
With this permission, the user is allowed to view the extended attributes in the functional dialog.. |
Access Purchase Order |
DSD Receiving |
With this permission, the user will be able to access the Purchase Orders. |
Access Reject Delivery |
DSD Receiving |
With this permission, the user will be able to reject a direct store delivery. |
Activate Container Edits |
DSD Receiving |
User needs this permission combined with the other respective permission(s) to update any information on the container. |
Add Unexpected Item |
DSD Receiving |
With this permission, the user will be able to add the unexpected items to the container. |
Allow ASN Over Receiving |
DSD Receiving |
For PO's with an ASN: With this permission, when entering a received quantity, it is OK, to exceed the ASN quantity. Without this permission, the received quantity cannot exceed the ASN quantity. |
Allow DSD Receiving With PO |
DSD Receiving |
With this permission, the user will be able to create a receipt against a PO but without ASN. |
Allow DSD Receiving Without PO |
DSD Receiving |
With this permission, the user will be able to create a receipt without PO. |
Allow PO Over Receiving |
DSD Receiving |
For PO's with and without an ASN: With this permission, when entering a received quantity, it is OK, to exceed the PO quantity. Without this permission, the received quantity cannot exceed the PO quantity. |
Allow Receiving Damages |
DSD Receiving |
With this permission, the user will be able to receive damaged items and make all remaining quantity to be received as damaged.User must also have Edit container and Modify container permissions in order to do this operation. |
Default Qty in All Containers |
DSD Receiving |
With this permission, the user will be able to default the received quantity for all the containers in the delivery. |
Default Qty in Container |
DSD Receiving |
With this permission, the user will be able to default the received quantity with the remaining quantity in the container.User must also have permission to ‘Modify container’ in order to do this operation. |
Display Expected Quantity |
DSD Receiving |
With this permission, the user will be able to view the expected quantity during the receipt. |
Edit Container |
DSD Receiving |
With this permission, the user can edit the container line items, modify the line item quantities or delete the item.User must also have permission to ‘Modify container’ in order to do this operation. |
Edit Container CFA |
DSD Receiving |
With this permission, the user will be able to capture CFAs for a Container in DSD Receiving. |
Edit Container Info DSD Receiving |
DSD Receiving |
With this permission, the user will be able to edit the container information.User must also have permission to ‘Modify container’ in order to do this operation. |
Edit Delivery CFA |
DSD Receiving |
With this permission, the user will be able to capture CFAs for a DSD. |
Edit Delivery Info |
DSD Receiving |
With this permission, the user will be able to edit the delivery information. |
Edit DSD Receiving Ext. Attribute |
DSD Receiving |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit Quantity |
DSD Receiving |
With this permission, the user will be able to edit the quantity of the item in the delivery. User must also have Edit container and Modify container permissions in order to do this operation. |
Override Not After Date Check |
DSD Receiving |
With this permission, the user can override the not after date check. This permission will allow the user to receive delivery where the receipt date passed the not after date in PO. |
Override Supplier Discrepancies |
DSD Receiving |
With this permission, the user will be able to override the supplier discrepancies when quantity is validated. |
Receive Direct Delivery on Shop Floor |
DSD Receiving |
With this permission, the user will be able to receive delivery on shop floor directly. |
Access Inventory Adjustment |
Inventory Adjustments |
With this permission a user will have access to the Inventory Adjustment dialog. |
Access Inventory Adjustment Attribute |
Inventory Adjustments |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Complete Inventory Adjustment |
Inventory Adjustments |
With this permission, the user can Confirm an inventory adjustment. User must also have data permissions for each adjustment reason on the adjustment. |
Create Inventory Adjustment |
Inventory Adjustments |
With this permission, the user can create a new inventory adjustment. This permission must exist as well for a user to copy a “completed” inventory adjustment. User must also have data permissions for each adjustment reason on the adjustment. |
Create Quick Adjustment |
Inventory Adjustments |
With this permission, the Adjust Inventory menu option will be available on JET Mobile in Item Lookup. Without this permission, the Adjust Inventory button will not be displayed. |
Delete Inventory Adjustment |
Inventory Adjustments |
With this permission, the user will be able to delete an inventory adjustment. User must also have data permissions for each adjustment reason on the adjustment. |
Edit Inventory Adjustment |
Inventory Adjustments |
With this permission, the user will be able to edit existing inventory adjustments. User must also have data permissions for each adjustment reason on the adjustment. |
Edit Inventory Adjustment Attribute |
Inventory Adjustments |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit Inventory Adjustment CFA |
Inventory Adjustments |
With this permission, the user will be able to capture CFAs for an inventory adjustment. |
Edit Quantity |
Inventory Adjustments |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Edit Inventory Adjustment permission as well as data permissions for each adjustment reason on the adjustment. |
Access Item Basket |
Item Basket |
With this permission, the user will have access to the Item Basket dialog. |
All Stores Item Basket |
Item Basket |
With this permission, Item Baskets for All Stores can be created as well as edited. Without this permission, Item Baskets cannot be created for all stores, and they can only be viewed for all stores. |
Confirm Item Basket |
Item Basket |
With this permission, the user will be able to Confirm an Item Basket. |
Create Item Basket |
Item Basket |
With this permission, the user will be able to create Item Baskets. |
Delete Item Basket |
Item Basket |
With this permission, the user will be able to delete an Item Basket. |
Edit Item Basket |
Item Basket |
With this permission, the user will be able to edit active Item Baskets. |
Edit Item Basket CFA |
Item Basket |
With this permission, the user will be able to capture CFAs on an Item Basket. |
Edit Quantity Item Basket |
Item Basket |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Edit Item Basket permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Import Item Basket |
Item Basket |
With this permission, the user will have the Import Item Basket menu option within an Item Basket on mobile. |
Investigate Item Basket |
Item Basket |
With this permission, the investigate menu option in item lookup will be available and the user will be able to add an item to an existing item basket or create a new item basket if one doesn't exist for investigation in item lookup. Without this permission, the investigate menu option in item lookup will not be available. |
Access Notifications |
Notifications |
With this permission, the bell notification icon will be displayed in the drawer/menu as well as on the Open Transactions header. The view on the notification will also be displayed. |
Customer Order Pickup |
Notifications |
With this permission, the user will be notified, if the pick list has been created but not actioned. |
Customer Order Pick Reminder |
Notifications |
With this permission, the user will be notified, if the pick list has been created but not actioned. |
Customer Order Reauthorization |
Notifications |
With this permission the user will receive a notification when the payment reauthorization for a customer order is successful. |
Customer Order Receipt |
Notifications |
With this permission, the user will be notified when customer orders are received. |
Customer Order Reminder |
Notifications |
With this permission, the user will be notified when the customer order has not been fulfilled. |
Damaged Delivery |
Notifications |
With this permission, the user will be notified when the delivery includes damaged items. |
Display External Scanner Notifications |
Notifications |
With this permission, the user will be notified with a popup that appears when a scanner is connected or disconnected or has a low battery for that event. |
Display Notification Warning |
Notifications |
With this permission, the user will receive a notification warning when a new notification is created / inserted into the system. |
Finisher Delivery Unable to Auto-Receive |
Notifications |
With this permission, the user will receive a notification warning when a finisher delivery is not auto received. |
Finisher UIN Discrepancy |
Notifications |
With this permission, the user will be notified when a finisher return received quantity does not match the number of serial numbers on the return. Without this permission, the user will not be notified. |
Misdirected Container |
Notifications |
With this permission, the user will be notified when a container has been received in another location. |
New Customer Order |
Notifications |
With this permission, the user will be notified when customer orders are created. |
New Customer Order Reverse Pick |
Notifications |
With this permission, the user will be notified when a new cross channel customer order reverse picks arrives. |
Over Received Quantity |
Notifications |
With this permission, the user will be notified when the number of pre-populated serial numbers exceeds the received quantity. Without this permission, the user will not be notified. |
Receiving UIN Discrepancy |
Notifications |
With this permission, the user will be notified when the number of pre-populated serial numbers does not match the received quantity. Without this permission, the user will not be notified. |
RTV Request Expiration Approaching |
Notifications |
With this permission, the user will be notified if the supplier return request expiration date is approaching. |
RTV Unavailable request quantity |
Notifications |
With this permission, the user will be notified if there is not enough inventory in the unavailable bucket to send back to supplier from a return request. |
Shipped Delivery Overdue |
Notifications |
With this permission, the user will be notified when the shipped delivery has not been received and has passed the expected date. |
Store Delivery Unable to Auto-Receive |
Notifications |
With this permission, the user will be notified when a store delivery has discrepancies and cannot be auto received. |
Store Receiving Over/Under |
Notifications |
With this permission, the user will be notified when a store transfer has over/under received quantities. |
Transfer Request |
Notifications |
With this permission, the user will be notified when a transfer request is created. |
Transfer Request Approved |
Notifications |
With this permission, the user will be notified when a transfer request is approved. |
Transfer Request Expiration Approaching |
Notifications |
With this permission, the user will be notified when a transfer request has not been approved and the request is about to expire. This is based on the not after date set. |
Transfer Request Rejected |
Notifications |
With this permission, the user will be notified when a transfer request is rejected. |
Transfer Unavailable Request Quantity |
Notifications |
With this permission, the user will be notified when the requested quantity is no longer available at the requested source location. |
UIN Items on Incoming ASN Failed |
Notifications |
With this permission, the user will be notified if an Auto Generated SN item is on the ASN with pre-generated numbers when processing thru the RIB. Without this permission, the user will not be notified. |
Unexpected UIN (Store Changed) |
Notifications |
With this permission, the user will be notified when UINs are discovered at a store where they should not be. Without this permission, the user will not be notified. |
Warehouse Delivery Unable to Auto-Receive |
Notifications |
With this permission, the user will be notified when the delivery includes pre-populated serial numbers and cannot be automatically received. |
Access Open Transactions |
Open Transactions |
If the user has this permission, the Open Transactions menu option will be available in the drawer/menu and Quick Actions. Upon logging in the user will go to Open Transactions. If the user does not have this permission, the menu option will not be available in the drawer/menu or Quick Actions. Upon logging in the user will navigate to Quick Actions. . This permission is applicable only to JET mobile |
Send Transaction Notification |
Open Transactions |
With this permission the user will be able to send a notification. This is done from within the Open Transactions dialog; the user will be able to swipe an open transaction and send a notification. |
View Transactions |
Open Transactions |
With this permission the user will have the potential to view all the open transactions for the user's store (depending on data permissions). Without this permission, the Open Transactions dialog will still display (just without the transactions listed); however, the list of open transactions will be empty. This permission is applicable only to MAF Mobile. |
Access Out of Stock Lookup |
Operational Views |
On EICS, with this permission, the Out of Stock operational view menu is displayed and user is allowed to view the out of stock operational view. |
Access New Received Items |
Operational Views |
On EICS, with this permission the user will be able to access the Access New Items view in Operational Views. |
Access Expiring Items Lookup |
Operational Views |
On EICS, with this permission the user will be able to access the Expiring Items view in Operational Views. |
Access Stock Counts - Ready to Authorize |
Operational Views |
On EICS, with this permission the user will be able to access the Stock Counts - Ready to Authorize view in Operational Views. |
Access Shopfloor Out of Stock |
Operational Views |
On EICS, with this permission the user will be able to access the Access Shopfloor Out of Stock view in Operational Views. |
Accept RTV |
RTV |
With this permission, the user will be able to approve a return request. User must also have data permissions for each return reason on the return. |
Access RTV |
RTV |
With this permission, a user will have access to the RTV dialog and the RTV menu option will appear in the Drawer. |
Activate RTV Edits |
RTV |
User is required to have Activate RTV Edits permission in order for Edit RTV or Edit RTV Info to activate. That is, the changes made on the RTV, because the user had Edit RTV and Edit RTV Info permissions, cannot be committed unless the user has Activate RTV Edits permission. |
Add Items To RTV |
RTV |
With this permission, the user will be able to add items to a return. User must also have Modify RTV and Edit RTV permissions as well as data permissions for each return reason on the RTV |
Allow Over Accepting |
RTV |
With this permission, the user will be allowed to accept quantity more than the Requested quantity in the RTV Request. |
Close RTV |
RTV |
With this permission, the user will be able to close an RTV. User must also have data permissions for each return reason on the return. |
Create RTV |
RTV |
With this permission, the user can create a new return. User must also have data permissions for each return reason on the return. |
Delete RTV |
RTV |
With this permission, the user can delete a return. User must also have data permissions for each return reason on the return. |
Edit Quantity |
RTV |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Modify RTV and Edit RTV permissions as well as data permissions for each return reason on the RTV. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit RTV |
RTV |
With this permission, the user will be able to edit existing RTV like line item details, qty, and so on. User must also have data permissions for each Return reason on the RTV. |
Edit RTV CFA |
RTV |
With this permission, the user will be able to capture CFAs for an RTV document. |
Edit RTV Info |
RTV |
With this permission, the user will be able to edit the header information of an RTV. |
Reject RTV |
RTV |
With this permission, the user will be able to reject a return request. User must also have data permissions for each return reason on the return. |
Access RTV Shipment |
RTV Shipment |
With this permission, the user can access shipments from RTV requests. Without this permission, the user will not be able to access the shipments from RTV requests. |
Access RTV Shipment Attribute |
RTV Shipment |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Activate RTV Shipment Container Edits |
RTV Shipment |
With this permission, the user will be allowed to commit any changes made to the shipment. |
Add Unexpected Items to RTV Shipment |
RTV Shipment |
With this permission, the user will be allowed to add items that are not present in the RTV Document, into the shipment. User must also have Modify Container and Edit Container permission as well as data permissions for each return reason on the container. |
Adjust Carrier |
RTV Shipment |
With this permission, the user will be able to update the BOL details of a shipment even after at least one container has been confirmed. |
Adjust Container RTV Shipment |
RTV Shipment |
With this permission, the user will be allowed to bring the container back to editable status. User must also have data permissions for each return reason on the container. |
Allow dispatch without Fiscal Document ID |
RTV Shipment |
With this permission, the user will be able to dispatch the shipment without the Fiscal Doc ID/E-way bill ID being available |
Allow over shipping RTV Shipment |
RTV Shipment |
With this permission, the user will be allowed to go over Approved quantity in the RTV document User must also have Modify Container and Edit Container permission as well as data permissions for each return reason on the container. Without this permission, the user will not be allowed to enter qty more than Approved qty. |
Cancel Submit RTV Shipment |
RTV Shipment |
With this permission, the user can cancel submit RTV shipments. |
Close RTV Shipment |
RTV Shipment |
With this permission, the user can close RTV shipments. Without this permission, the user will not be able to close RTV shipments. |
Confirm RTV Shipment Container |
RTV Shipment |
With this permission, the user can confirm containers in the shipments. User must also have data permissions for each return reason on the container. |
Create RTV Shipment |
RTV Shipment |
With this permission, the user can create shipments for RTV requests. |
Create RTV Shipment Container |
RTV Shipment |
With this permission, the user will be allowed to create a container for the shipment. |
Default Items to RTV Shipment |
RTV Shipment |
With this permission, the user will be allowed to add items from the RTV document into shipment. User must also have data permissions for each return reason on the shipment. Without this permission, the user will not be allowed to add items from the RTV document into shipment |
Delete RTV Shipment |
RTV Shipment |
With this permission, the user can delete RTV shipments. |
Delete RTV Shipment Container |
RTV Shipment |
With this permission, the user can delete containers in the shipments. User must also have data permissions for each return reason on the container. |
Dispatch Shipment |
RTV Shipment |
With this permission, the user can dispatch RTV shipments. |
Edit Container CFA |
RTV Shipment |
With this permission, the user will be able to capture CFAs for a container in RTV shipment. |
Edit Container RTV Shipment |
RTV Shipment |
With this permission, the user will be allowed to edit the line item details, update qty, remove item, restore item, cancel the current edits, and so on, User must also have Modify Container permission as well as data permissions for each return reason on the container. Without this permission, the user will not be allowed to edit any line item details, update qty, remove item, restore item, cancel the current edits, and so on. |
Edit Quantity |
RTV Shipment |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Modify Container and Edit Container permission as well as data permissions for each return reason on the container. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit RTV Container Info |
RTV Shipment |
With this permission, the user will be allowed to edit the container header details. User must also have Activate Container Edits permission. |
Edit RTV Shipment Attribute |
RTV Shipment |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit RTV Shipment BOL |
RTV Shipment |
With this permission, the user will be allowed to edit the shipment BOL details. |
Edit RTV Shipment Info |
RTV Shipment |
With this permission, the user will be allowed to edit the shipment header details. |
Edit Shipment CFA |
RTV Shipment |
With this permission, the user will be able to capture CFAs on an RTV shipment. |
Submit RTV Shipment |
RTV Shipment |
With this permission, the user can submit RTV shipments. |
View RTV Shipment BOL |
RTV Shipment |
With this permission, the user will be allowed to view the shipment BOL details. |
Access Role Maintenance |
Security |
User must have this permission for the Role Maintenance menu option to be available under Security in EICS. |
Access Security |
Security |
With this permission the user will have access to the Security dialog in EICS. |
Access User Maintenance |
Security |
User must have this permission for the User Assignment menu option to be available under Security in EICS. |
Delete Role |
Security |
User must have this permission in order to delete roles. |
Delete User |
Security |
User must have this permission in order to delete user profiles. |
Edit User |
Security |
User must have this permission in order to assign roles and stores to a user. |
Access Scan List |
Shelf Replenishment |
With this permission, the user will have access to Item Scan List dialog. |
Access Shelf Adjustment |
Shelf Replenishment |
With this permission, the user will have access to Shelf Adjustment dialog. |
Access Shelf Replenishment |
Shelf Replenishment |
With this permission, the user will have access to the in-store replenishment dialog. |
Confirm Shelf Adjustment |
Shelf Replenishment |
With this permission, the user can confirm the shelf adjustment. |
Confirm Shelf Replenishment |
Shelf Replenishment |
With this permission, the user can confirm the replenishment pick. |
Create Scan List |
Shelf Replenishment |
With this permission, the user can create a new item scan list. User must also have data permissions for each scan list type to create a new scan list of that type. |
Create Shelf Adjustment |
Shelf Replenishment |
With this permission, the user can create a new shelf adjustment. |
Create Shelf Replenishment |
Shelf Replenishment |
With this permission, the user can create a new shelf replenishment pick. User must have the data permission for each shelf replenishment pick type to do this operation. |
Default Shelf Replenishment Quantity |
Shelf Replenishment |
With this permission, the user can default the quantity on replenishment pick. The user must also have the Edit replenishment permission to do this operation. |
Delete Scan List |
Shelf Replenishment |
With this permission, the user will be able to delete a scan list. |
Delete Shelf Adjustment |
Shelf Replenishment |
With this permission, the user can delete the shelf adjustment. |
Delete Shelf Replenishment |
Shelf Replenishment |
With this permission, the user can delete the shelf replenishment pick. |
Edit Scan List |
Shelf Replenishment |
With this permission, the user will be able to edit and save the scan list. |
Edit Scan List CFA |
Shelf Replenishment |
With this permission, the user will have the ability to capture CFAs for a Scan List. |
Edit Scan List Quantity |
Shelf Replenishment |
With this permission, the user will be able to edit the quantity on the UI using the widget. User must also have the Edit Scan List permission to do this. |
Edit Shelf Adjustment |
Shelf Replenishment |
With this permission, the user can edit and save the shelf adjustment. |
Edit Shelf Adjustment CFA |
Shelf Replenishment |
With this permission, the user will have the ability to capture CFAs for a Shelf Adjustment. |
Edit Shelf Adjustment Quantity |
Shelf Replenishment |
With this permission, the user can edit the quantity using the widget on the UI. |
Edit Shelf Replenishment |
Shelf Replenishment |
With this permission, the user will be able to edit the existing shelf replenishment pick. |
Edit Shelf Replenishment CFA |
Shelf Replenishment |
With this permission, the user will have the ability to capture CFAs for Replenishment Pick List. |
Edit Shelf Replenishment Quantity |
Shelf Replenishment |
With this permission, the user can edit the quantity using the quantity widget on the UI. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Replenishment Item Substitution |
Shelf Replenishment |
With this permission, the user can substitute the pick items. The user must also have the Edit replenishment permission to do this operation. |
Access Quick Count |
Stock Counts |
With this permission, the user will have access to Quick count dialog in JET mobile application. |
Access Stock Count |
Stock Counts |
With this permission, the user can access the Stock Counts dialog. |
Access Stock Count Attribute |
Stock Counts |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Apply Late Sales |
Stock Counts |
With this permission, Apply Late Sales button will be available to the user in the Stock Count Authorization Detail screen. |
Complete All Stock Count Children |
Stock Counts |
On JET mobile, with this permission, the user will be able to access the complete all option on the child stock count list to complete all the child stock counts under the master stock count. |
Complete Child Stock Count |
Stock Counts |
With this permission, the user can complete the child stock count. |
Confirm Authorization Stock Count |
Stock Counts |
With this permission, the user can confirm the authorization. |
Create Ad Hoc Stock Count |
Stock Counts |
With this permission, the user can create a new adhoc stock count. |
Delete Stock Count |
Stock Counts |
With this permission, the user can delete a stock count. |
Edit Adhoc Stock Count |
Stock Counts |
With this permission, the user can edit the ad hoc stock count. |
Edit Adhoc Stock Count Lock |
Stock Counts |
With this permission, the user will have the ability to enable and disable the Adhoc Stock count Lock for an adhoc stock count. |
Edit Authorizaton Stock Count |
Stock Counts |
With this permission, the user can access the Stock count authorization dialog on the desktop. Ability to apply late sales. |
Edit Stock Count Attribute |
Stock Counts |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit Stock Count CFA |
Stock Counts |
With this permission, the user will have the ability to capture CFAs in Stock Count and Recount. |
Edit Stock Count Quantity |
Stock Counts |
With this permission, the user can edit the quantity using the quantity widget. |
Edit Unit Amount Stock Count |
Stock Counts |
With this permission, the user is allowed to do update for the stock counts that are of type unit and amount |
Edit Unit Stock Count |
Stock Counts |
With this permission, the user can update the stock count of unit or problem line stock count types. |
Recount Stock Count |
Stock Counts |
On Mobile, with this permission, when the user selects a stock count in the Stock Count List screen and the stock count is in 'Recount' status, the Recount Items screen will open in edit mode. Without this permission, the screen will open in view-only mode. |
Rejected Item Stock Count |
Stock Counts |
With this permission, the user will have access to the Rejected Items dialog. |
Snapshot Stock Count |
Stock Counts |
With this permission, the user is allowed to take a snapshot at the master stock count level. |
Snapshot Stock Count Child |
Stock Counts |
With this permission, the user is allowed to take the snapshot at the child stock count level. |
Stock Count Import Basket |
Stock Counts |
With this permission, the user will have the Import Item Basket footer menu option in the Bulk Scan screen within Stock Counts. |
Update Authorization Quantity |
Stock Counts |
With this permission, the user can update the authorization quantity and default the last count quantity to authorized quantity while in the process of authorization. |
View Variance |
Stock Counts |
With this permission, the user will be able to view the variance (difference) between the snapshot quantity and the total quantity counted during counting. |
Access Store Orders |
Store Order |
With this permission, the user will have access to the Store Orders dialog. |
Approve Store Orders |
Store Order |
With this permission, the user will be able to Approve a Store Order. |
Cancel Submit Store Order |
Store Order |
This permission will be needed in order for the Cancel Submit option to be available in the footer menu of the Delivery Items screen. |
Create Store Orders |
Store Order |
With this permission, the user will be able to create Store Orders. |
Delete Store Orders |
Store Order |
With this permission, the user will be able to delete a Store Order. |
Display Sales Forecast |
Store Order |
With this permission, the Sales Forecast on the Sales Data screen will be displayed. |
Display Sales History |
Store Order |
With this permission, the Sales History on the Sales Data screen will be displayed. |
Display Store Order Cost |
Store Order |
With this permission the Total Estimated Cost will be displayed on the Info screen in store orders. The unit cost will be displayed on the Store Orders Item Detail. The Refresh Cost button will be displayed in the Store Order Items footer menu. |
Edit Quantity |
Store Order |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Edit Store Orders permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Store Order CFA |
Store Order |
With this permission, the user will be able to edit CFAs on the store order. The Edit CFA menu option will be available in the footer menu. |
Edit Store Orders |
Store Order |
With this permission, the user will be able to edit active Store Orders. |
Edit Submitted Status |
Store Order |
This permission will allow a user to edit a store order that is in 'submitted' status. Without this permission, 'submitted' status will be noneditable/view only. |
Submit Store Order |
Store Order |
This permission will be needed in order for the Submit option to be available in the footer menu of the Store Order Items screen. |
Access DCS Work Type |
Technical Maintenance |
With this permission, users will have access to the DCS Work Type screen in the desktop application. |
Access Format Assignment |
Ticketing |
With this permission, the user is allowed to access the format assignment dialog in the desktop application. |
Access Print Format |
Ticketing |
With this permission, the user is allowed to access the ticket print format dialog. |
Access Print Item |
Ticketing |
With this permission, the user is allowed to access the print item dialog. |
Access Ticket List |
Ticketing |
With this permission, the user can access the Ticket List. |
Access Ticket Template Upload |
Ticketing |
With this permission, the user can access the Upload Ticket Templates screen to upload the ticketing layout. |
Allow Override Ticket Price |
Ticketing |
With this permission, the user can override the ticket price on the ticket detail screen. |
Create Format Assignment |
Ticketing |
With this permission, the user is allowed to create a new item basket based format assignment. |
Create Ticket |
Ticketing |
With this permission, the user is allowed to create a new ticket in the ticketing dialog. |
Delete Format Assignment |
Ticketing |
With this permission, the user is allowed to delete a format assignment. |
Delete Ticket |
Ticketing |
With this permission, the user is allowed to delete a ticket in the ticketing dialog. |
Delete Ticket Template |
Ticketing |
With this permission, the user is allowed to delete a ticket template screen. |
Edit Format Assignment |
Ticketing |
With this permission, the user is allowed to edit an existing format assignment. |
Edit Ticket |
Ticketing |
With this permission, the user can edit an existing ticket. |
Print Ticket |
Ticketing |
With this permission, the user can print the tickets in the ticketing dialog. |
Print Tickets from Container Items |
Ticketing |
With this permission, the user is allowed to generate and print tickets from the container items screen both in transaction and lookup |
Accept Transfer Request |
Transfer |
With this permission, the user will be able to accept a transfer request. |
Access Transfer |
Transfer |
With this permission, a user will have access the transfers. |
Access Transfer context |
Transfer |
With this permission, a user will be able to view the Context type details in a transfer. |
Access Transfer Request |
Transfer |
With this permission, a user will have access to the Transfer dialog in the application |
Approve Transfer |
Transfer |
With this permission, the user will be able to approve a transfer document. |
Close Transfer |
Transfer |
With this permission, the user will be able to close a transfer. |
Create Request |
Transfer |
With this permission, the user will be able to create a transfer request. |
Create Transfer |
Transfer |
With this permission, the user will be able to create a transfer document. |
Delete Request |
Transfer |
With this permission, the user will be able to delete a transfer request. |
Delete Transfer |
Transfer |
With this permission, the user will be able to delete a transfer document. |
Edit Quantity Transfer Request |
Transfer |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Transfer |
Transfer |
With this permission, the user will be able to edit a transfer document. |
Edit Transfer Request |
Transfer |
With this permission, the user will be able to edit a transfer request. |
Edit Transfer Request CFA |
Transfer |
With this permission, the user will be able to capture CFAs in transfer request documents. |
Reject Transfer Request |
Transfer |
With this permission, the user will be able to reject a transfer request. |
Request Transfer |
Transfer |
With this permission, the user will be able to submit a transfer request. |
Access Quick Receiving |
Transfer Receiving |
With this permission, a user will have access to Transfer Quick Receiving. |
Access Transfer Receiving |
Transfer Receiving |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Access Transfer Receiving Attribute |
Transfer Receiving |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Activate Container Edits |
Transfer Receiving |
With this permission, the user will be allowed to commit any changes made to the container. The user will be able to edit the details with the Edit permission however for the changes to be saved to the DB, the Activate Container Edits permission is needed. |
Add Unexpected Item to Transfer Receiving |
Transfer Receiving |
With this permission, the user will be allowed to receive items that are not present in the original delivery. User must also have Modify Container and Edit Container permission. Without this permission, the user will not be allowed to receive items that are not present in the original delivery. |
Adjust Container |
Transfer Receiving |
With this permission, the user will be able to bring back a confirmed container to editable status. |
Allow Default Zero at Confirmation |
Transfer Receiving |
With this permission, the user will be able to confirm a transfer receipt with the option to set all non received items to zero. Without this permission, if there are any non received items on the container, the user will get a hard stop and not be able to confirm the delivery. |
Allow Over Receiving Store to Store ASN |
Transfer Receiving |
With this permission, the user will be able to over receive an ASN from store to store.. |
Confirm Container |
Transfer Receiving |
With this permission, the user will be able to confirm a container. |
Confirm Receipt |
Transfer Receiving |
With this permission, the user will be able to confirm a transfer delivery. |
Create Container |
Transfer Receiving |
With this permission, the user will be able to create a container. |
Default Qty in All Containers |
Transfer Receiving |
With this permission, the user will be able to default the expected qty in received qty field in all the containers. |
Default Quantity in Container |
Transfer Receiving |
With this permission, the user will be able to default the expected qty in received qty field for the items in the container. User must also have Modify Container and Edit Container permission. |
Delete Container |
Transfer Receiving |
With this permission, the user will be able to delete a container. |
Display Expected Qty |
Transfer Receiving |
With this permission, the user will be able to view Expected Qty of an item in the containers. |
Edit Container |
Transfer Receiving |
With this permission, the user will be allowed to edit the line item details, update qty, remove item, restore item, cancel the current edits, and so on. User must also have Modify Container permission for the changes to be committed to the DB. Without this permission, the user will not be allowed to edit any line item details, update qty, remove item, restore item, cancel the current edits, and so on. |
Edit Container CFA |
Transfer Receiving |
With this permission, the user will be allowed to capture CFAs in the containers of transfer deliveries. |
Edit Container Info |
Transfer Receiving |
With this permission, the user will be allowed to edit the container header details. User must also have Modify Container permission for the changes to be committed to the DB. |
Edit Delivery CFA |
Transfer Receiving |
With this permission, the user will be allowed to capture CFAs in the transfer deliveries. |
Edit Quantity |
Transfer Receiving |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Modify Container and Edit Container permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Receiving Info |
Transfer Receiving |
With this permission, the user will be able to edit the header details of a transfer delivery |
Edit Transfer Receiving Attribute |
Transfer Receiving |
With this permission, the user is allowed to add/remove the extended attributes. |
Misdirected Container |
Transfer Receiving |
With this permission, the user will be allowed to copy the items from a misdirected container. |
Receive On Shop Floor |
Transfer Receiving |
With this permission, the user will be able to receive the container on the shopfloor. User must also have Modify Container and Edit Container Info permission. Without this permission, user will not be able to receive the container on the shopfloor. |
Record Receipt Damages |
Transfer Receiving |
With this permission, the user will be able to receive damaged items in a transfer delivery. |
Access Container Attribute |
Transfer Shipment |
With this permission, the user is allowed to view the extended attributes in the functional dialog. |
Access Shipment |
Transfer Shipment |
With this permission, a user will have access to the Transfer Shipment dialog for the user in the application. |
Activate Container Edits |
Transfer Shipment |
With this permission, the user will be allowed to commit any changes made to the shipment. The user will be able to edit the details with the Edit Container permission however for the changes to be saved to the DB, the Activate Container Edits permission is needed. Without this permission, the user will not be allowed to commit any changes made to the shipment. |
Add Items with No Document |
Transfer Shipment |
With this permission, the user will be allowed to create an adhoc document through Shipments and add items to it. This controls the visibility of ‘No document’ button on the Select Document screen. Without this permission, the user will not be allowed to create an adhoc document through shipments and add items to it. |
Add Unexpected Item to Transfer Shipment |
Transfer Shipment |
With this permission, the user will be allowed to add items that are not present in the Transfer Document, into the shipment. User must also have Modify Container and Edit Container permissions. Without this permission, the user will not be allowed to add items that are not present in the Transfer document, into the shipment. |
Adjust Carrier |
Transfer Shipment |
With this permission, the user will be able to update the BOL details of a shipment even after at least one container has been confirmed. Without this permission, the user will not be able to update the BOL details of a shipment after at least one container has been confirmed. |
Adjust Container |
Transfer Shipment |
With this permission, the user will be allowed to bring the container back to editable status. |
Allow dispatch without Fiscal Document ID |
Transfer Shipment |
With this permission, the user will be able to dispatch the shipment without the Fiscal Doc ID/E-way bill ID being available |
Cancel Submit Shipment |
Transfer Shipment |
With this permission, the user can cancel submit Transfer shipments. |
Confirm Container |
Transfer Shipment |
With this permission, the user can confirm containers in the shipments. |
Create Shipment |
Transfer Shipment |
With this permission, the user can create shipments for Transfer documents. Without this permission, the user will not be able to create shipments for Transfer documents. |
Delete Container |
Transfer Shipment |
With this permission, the user can delete containers in the shipments. |
Delete Shipment |
Transfer Shipment |
With this permission, the user can delete transfer shipments. |
Dispatch Shipment |
Transfer Shipment |
With this permission, the user can dispatch shipments. |
Edit Container |
Transfer Shipment |
With this permission, the user will be allowed to edit the line item details, update qty, remove item, restore item, cancel the current edits, and so on., User must also have Modify Container permission. Without this permission, the user will not be allowed to edit any line item details, update qty, remove item, restore item, cancel the current edits, and so on. |
Edit Container Attribute |
Transfer Shipment |
With this permission, the user is allowed to add/remove the extended attributes. |
Edit Container CFA |
Transfer Shipment |
With this permission, the user will be able to capture CFAs in the containers of transfer shipments. |
Edit Container Info |
Transfer Shipment |
With this permission, the user will be allowed to edit the container header details. User must also have Modify Container permission. |
Edit Quantity |
Transfer Shipment |
With this permission, the user will be able to tap on the item quantity and the quantity widget will open to edit the quantity. User must also have Modify Container and Edit Container permission. Without this permission, the quantity is not editable via the manual dialog and only scanning is allowed. |
Edit Shipment BOL |
Transfer Shipment |
With this permission, the user will be allowed to edit the shipment BOL details. |
Edit Shipment CFA |
Transfer Shipment |
With this permission, the user will be able to capture CFAs in transfer shipments. |
Edit Shipment Info |
Transfer Shipment |
With this permission, the user will be allowed to edit the shipment header details. |
Override Exclude Shipping Network |
Transfer Shipment |
With this permission, user will be able to override Shipping Network exclusion and will be able to dispatch to the stores that are not in the network. |
Select Container Document |
Transfer Shipment |
With this permission, the user will be allowed to select transfer documents to be added to the shipment. User must also have Modify Container and Edit Container permission. |
Submit Shipment |
Transfer Shipment |
With this permission, the user can submit shipments. |
Create UIN on the Fly |
UIN |
With this permission, the user is allowed to create a UIN on the fly when creating an inventory adjustment using a reason code of Disposition Movement from Out (Dist) to Available to Sell (ATS) = UIN Status in Stock. User must also have Edit Inventory Adjustment permission as well as data permissions for each adjustment reason on the adjustment. |
Data Permissions
Data permissions need to be created for the following:
-
Container Items Limited To
-
Counting Method
-
Departments
-
Display List Diff Types
-
Inventory Adjustment Reason Code
-
Item Basket Types
-
Location Type
-
Print Format Type
-
Product Group Type
-
Role Type
-
RTV Reason Code
-
RTV Shipment Reason Code
-
Scan List Type
-
Shelf Adjustment Type
-
Shelf Replenishment Type
-
Store Order Delivery Timeslots
-
Transaction Type
-
Transfer Destination Type
-
Transfer Shipment Reason Code