Oracle® Retail Enterprise Inventory Cloud Service Administration Guide Release 18.0 F13732-01 |
|
Previous |
Next |
Table 8-1 System Admin Parameters
Options | 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 |
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 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 Multiple Set of Books |
Values: Enabled/Disabled This parameter defines whether to limit the supplier selection based on the supplier sites associated with the location. Enabled: Multiple Sets of Books (MSOB) is enabled in merchandising system. Suppliers will be limited to only those locations corresponding to the operating unit for which they are set up. Disabled:- MSOB is disabled in merchandising system. No validation on the operating unit is performed. This parameter defines whether to limit the supplier selection based on the supplier sites associated with the location. Note This parameter is also applicable to Finishers (Transfer to Finisher, Lookup Finisher). |
0 |
ADMIN |
Integer |
Publish Non Inventory Items |
Values: Yes/No Default: Yes Topic: Admin Editable: Yes This parameter indicates whether the non-inventory items will be published in the outgoing messages or not. |
Yes |
ADMIN |
Boolean |
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 Maximum Threads |
Gives the maximum number of batch partitions for a batch to run. |
5 |
BATCH |
Integer |
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 |
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 |
Batch Scheduler Execution Interval |
Gives the batch scheduler execution delay interval duration to throttle batch execution calls. |
300 |
BATCH |
Integer |
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 |
Search Limit Default for latest job instances per batch job name |
Gives the default number for job instances search. |
50 |
BATCH |
String |
Customer Order Fulfillment Restriction |
Values: Restricted/Transaction Controlled Transaction 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 (with the exception of 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. |
0 |
CUSTOMER ORDER |
Integer |
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 |
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 there 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. |
0 |
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 |
Display Item Image for Inventory Adjustments |
Values: Yes/No Yes: The item image is displayed within Inventory Adjustments. No: The item image is not displayed in Inventory Adjustments. |
No |
INVENTORY_ADJUSTMENT |
Boolean |
Display Item Image for Item Lookup |
Values: Yes/No Yes: The item image is displayed within Item Lookup. No: The item image is not displayed in Item Lookup. |
No |
ITEM_LOOKUP |
Boolean |
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 |
Currency Default Type |
Gives the default currency for EICS and SOCS. |
USD |
MOBILE |
String |
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 |
Device Camera Scan |
Used for enabling device camera for scanning on SOCS |
No |
MOBILE |
Boolean |
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 |
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 |
Scan Focus Item Detail |
Determines if sticky focus is enabled on SOCS screens. |
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. |
330 |
NOTIFICATION |
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 |
PURGE |
Integer |
Days To Hold Batch Logs |
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 |
PURGE |
Integer |
Days to Hold Completed Inventory Adjustments |
Delete records in 'Complete' Status where the inventory complete date is less than or equal to the current date minus the days to hold. |
30 |
PURGE |
Integer |
Days to Hold Completed Purchase Orders |
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. |
30 |
PURGE |
Integer |
Days to Hold Completed Staging Records |
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 |
PURGE |
Integer |
Days to Hold Completed Stock Counts |
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'. |
30 |
PURGE |
Integer |
Days to Hold Customer Orders |
Indicates the number of days that Cancelled and Fulfilled Customer Orders will be held in the system before being purged. |
60 |
PURGE |
Integer |
Days to Hold Expired User Roles |
Values: 0-999 This will determine the number of days after which the expired roles will be purged from the system |
30 |
PURGE |
Integer |
Days to Hold Expired item price |
Indicates the number of days to hold the expired price changes in the system before being purged. |
30 |
PURGE |
Integer |
Days to Hold In Progress Ad Hoc Stock Counts |
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 |
PURGE |
Integer |
Days to Hold Locking Records |
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. |
3 |
PURGE |
Integer |
Days to Hold Notifications |
This parameter is used to purge notifications which are greater than or equal to this value. |
14 |
PURGE |
Integer |
Days to Hold Price Change worksheet records |
All price change worksheet records in Completed, Approved, and Rejected status are purged after this number of days, where the price change effective date is less than or equal to the current date minus the number of days to hold. |
30 |
PURGE |
Integer |
Days to Hold Price History |
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 |
PURGE |
Integer |
Days to Hold RTV |
Values: 0 - 999 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 |
30 |
PURGE |
Integer |
Days to Hold Received Shipment Records |
Values: 0 - 999 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 |
PURGE |
Integer |
Days to Hold Related Items |
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. |
60 |
PURGE |
Integer |
Days to Hold Sales Posting |
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 |
120 |
PURGE |
Integer |
Days to Hold Scan Lists |
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 |
PURGE |
Integer |
Days to Hold Shelf Adjustment Lists |
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 |
PURGE |
Integer |
Days to Hold Shelf Replenishments |
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 |
PURGE |
Integer |
Days to Hold Transaction History |
Determines the number of days after which store_item_stock_history records can be purged. |
30 |
PURGE |
Integer |
Days to Hold Transfer Documents |
Values: 0 -999 This parameter would decide the number of days after which a Transfer document, shipments, and deliveries can be purged. |
30 |
PURGE |
Integer |
Days to Hold Completed UINs |
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 |
120 |
PURGE |
Integer |
Days to Hold Resolved UIN Exceptions |
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. |
120 |
PURGE |
Integer |
Days to Hold UIN Audit Information |
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 |
PURGE |
Integer |
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. Note : "Email Alert - RTV Request Expiration Approaching", permission will be required to receive the alert. |
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 in SIM. 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 or not 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, SIM 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 SIM 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 |
Display Item Image for Stock Counts |
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 |
Stock Count Display Default Timeframe |
Values: Yes/No Yes: Image will be displayed. No: Image will not be displayed in that functional area. |
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. |
Yes |
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 RMS. 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 RMS for capturing the financial value. RMS is only capable of processing sales data on a daily bases and disregards the time value if included. |
0 |
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. |
0 |
STOCK_COUNTS |
Integer |
Updating 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 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 |
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 webservice call. |
1000 |
System Settings |
Integer |
JNDI Context Refresh Rate Milliseconds |
Determines the cache refresh rate for JNDI context for RIB message publisher in milliseconds. |
900000 |
System Settings |
Integer |
Merchandise Hierarchy Refresh Rate Milliseconds |
Determines the cache refresh rate for merchandise hierarchy in milliseconds. |
3600000 |
System Settings |
Integer |
POS Transaction Max. Size for Synchronous Processing |
Determines the maximum processing size for pos transaction records. All pos transaction records above this value are staged first. |
10 |
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 Non-Inventory Items |
Values: Yes/No 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 |
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 |
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. |
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 or not 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 or not 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 or not 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 or not 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 or not 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 or not 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 or not 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 Transfers |
Values: Yes/No This new system parameter will dictate whether or not the Transfer messages being loaded into the system from an external system has dates in GMT or not. Likewise, if SIM 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 Vendor ASN |
Values: Yes/No This parameter will dictate whether or not 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 or not 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 via RSL, 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 via RSL, 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 email 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 email 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: Yes/No Yes: Enables the ability to receive misdirected containers. No: Disables the ability to receive misdirected containers. |
0 |
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. |
2 |
TRANSFER_RECEIVING |
Integer |
Store Receiving Over/Under Notification |
Values: On / 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 email 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 Transfer requests generated in an external system and SIM sometimes require the transfer to be dispatched to warehouse, store or finisher before a certain date. This 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 SIM 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 SIM 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 SIM 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 |
Display Item Description |
Values: Short Description / Long Description 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. |
0 |
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 seperately. |
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 JET screen for problem line stock count product group. |
1500 |
UI |
Integer |
Search Limit Default for Container Lookup |
Values: 1-999 Indicates the default search limit for Container Lookup. |
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 Inventory Adjustments |
Values: 1-999 Indicates the default search limit for Inventory Adjustments. |
50 |
UI |
Integer |
Search Limit Default for Item Lookup |
Values: 1-999 Indicates the default search limit for Item Lookup. |
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 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 RTV |
Values: 1-999 Indicates the default search limit for Returns. |
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 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 Staged Message Lookup |
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 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 Indicates the default search limit for Supplier Lookup |
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 Transaction History |
Values: 1 - 999 Indicates the default search limit for the Transaction History Search Criteria. |
50 |
UI |
Integer |
Search Limit Default for Troubled Transaction List |
Values: 1 - 999 Indicates the default search limit for the Troubled Transaction Search Criteria. |
50 |
UI |
Integer |
Search Limit Default for UIN Lookup |
Values: 1 - 999 Indicates the default search limit on the UIN Lookup. |
50 |
UI |
Integer |
Shelf Replenishment UI Limit |
Gives recommended item count in product group component screen for shelf replenishment pick product groups. |
1500 |
UI |
Integer |
Unit Count UI Limit |
Gives the recommended item count in product group component screen for unit stock count product group. |
5000 |
UI |
Integer |
Unit and Amount Count UI Limit |
Gives the recommended item count in product group component screen for unit and amount stock count product group. |
1500 |
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 UIN Lookup |
Values: 1-999 Indicates the default search limit for UIN Lookup. |
50 |
UI |
Integer |
Search Limit Default for Troubled Transaction List |
Values: 1-999 Indicates the default search limit for Troubled Transactions |
50 |
UI |
Integer |
Allow Store UIN Relocation |
Values: Yes/No Indicates whether UIN can be relocated from one store to another. |
Yes |
UIN |
Boolean |
Display Item Image for UIN Lookup |
Values: Yes/No Yes: This parameter indicates that item image will be displayed in UIN Lookup. No: Images will not be displayed in UIN Lookup. |
Yes |
UIN |
Boolean |