Functional Overviews

This chapter provides information concerning the various aspects of SIM’s functional areas.

Store Inventory Management Overview

SIM empowers store personnel to sell, service, and personalize customer interactions by providing users the ability to perform typical back office functionality on the store sales floor. The results are:

§ Greatly enhanced customer conversion rates

§ Improved customer service

§ Lower inventory carrying costs

§ Fewer markdowns

Store Inventory Management ensures that all available salespeople are on the sales floor selling to customers.

The benefits of the Store Inventory Management solution include:

§ Improve customer service and coverage

§ Improve perpetual inventory levels by enabling floor-based inventory management through handheld devices and store PCs

§ Minimize the time required to process a receipt and check-in of incoming merchandise

§ Receive, track, and transfer merchandise accurately, efficiently, and easily

§ Reduce technology costs by centralizing hardware requirements

§ Easy to use GUI interface guiding users through the required transactions

§ Extensible technology platform that allows customizations to the product. This ensures the retailer’s modifications are isolated during product upgrades and lowering the total cost of ownership.

Store Inventory Management has been specifically designed to meet the needs of a high turnover labor force by providing easy to use screens that guide a user through processing a transaction.

Store Inventory Management also provides Store managers and personnel with the ability to easily perform an array of in store operations:

§ Receive merchandise

§ Replenish stock

§ Manage physical inventories

§ Look up product information

§ Transfer or return stock

§ Adjust inventory

§ Stock counts

§ Order stock

§ Fulfillment Customer Orders

§ Printing Item Tickets and Shelf Edge Labels

Store Inventory Management provides store employees with the information and flexible capabilities that are needed to maintain optimal inventory levels in the store and convert shoppers into buyers.

Solution and Business Process Overview

Store Inventory Management manages the inventory movement of merchandise within the store and provides users with detailed Item/SKU information needed to perform key tasks. The functionality in SIM includes:

§ Lookups – Item, Supplier, Container, Finisher, Transaction History

§ Unique Identification Number (UIN) Support

§ Receiving – Warehouse, Supplier, Store, Finisher

§ Shipping – Warehouse, Supplier, Store, Finisher

§ Transfers/Transfer Requests

§ RTV (Return to Vendor)/RTV Requests

§ Receipt Adjustments

§ Stock Counts

§ Store Ordering

§ Item Requests

§ Sequencing

§ Shelf Replenishment

§ Inventory Adjustments

§ Wastage

§ Price Changes

§ Ticketing

§ Customer Orders - lookup, picking, delivery, and reverse picks

§ Item Basket

§ E-mail Alerts

§ Printing Reports

SIM also has System Administration functionality, which enables users to configure different parameters within the system based on their business processes. The system administration screens also contain the ability to create product groups. A product group is a collection of departments, classes, subclasses, or items, which can be used to schedule stock counts, order product, replenish store shelves, and for addressing wastage.

SIM is fully integrated with the Oracle Retail Merchandising System (RMS), a warehouse management system, an invoice matching system, and Oracle Retail Sales Audit (ReSA) is through flat file. Most transactions are direct updates, with only a few using batch processes and some using direct update integration. Any store using SIM, maintains its own inventory and reports those numbers to the merchandising system. Most foundation data within SIM can be populated using the data-seeding program provided.

Deploying SIM as part of the Oracle Retail enterprise ensures the accuracy and timeliness of all inventory information across the retailer’s supply chain.

The SIM UI is split up in six parts, each focused on a particular function in the system:

§ Administration: All administrative information can be found under this section.

§ Shipping/Receiving: This dialogue concerns itself with all shipping and receiving matters at the store. It includes, warehouse, finisher, store and supplier deliveries as well as returns to these entities.

§ Inventory Management focuses on all the elements that can affect inventory positions within the store (excluding point-of-sale).

§ Customer Order Management all functions pertaining to the fulfilling of an order to the customer.

§ Lookups: Under this dialogue the user can find detailed information regarding items, suppliers and containers.

§ Print: The print functions help you manage printing tickets, labels and reports.

Most of the inventory features discussed in this section is applicable to both Oracle Retail Mobile Store Inventory Management (the handheld devices) and the Oracle Retail Store Inventory product (the PC).

The handheld device enables the user to register items for the different inventory transactions with more accuracy by scanning barcodes and validating transactions against centrally deployed reference data.

Inventory Management

This section details inventory management.

Inventory Adjustments Functional Overview

To assist in maintaining perpetual inventory, SIM provides the ability to create inventory adjustments for all items within a store. SIM conveys changes to the merchandising system. Inventory adjustment functionality within the SIM system can be accomplished on a PC-based deployment, on a wireless handheld device, or on a combination of the two deployment methods.

Inventory adjustment processing within SIM includes the following features:

§ Reason codes, which correspond to dispositions, can be assigned to inventory adjustments, thus moving stock to various inventory buckets. This code not only is used for reporting purposes, but also indicates to the system whether the amount is to be incremented or decremented and in which inventory buckets are impacted based upon the disposition associated with the reason code.

§ Sub-buckets allow for the unavailable inventory to be broken down further into smaller buckets. Sub-buckets can be assigned to reason codes that have dispositions moving inventory to or from unavailable stock. Sub-buckets are configurable per store and can be turned on or off.

– Example 1:

A reason code of Removed for repair would indicate to the system that the inventory for the selected item is to be decremented from the available stock on hand (SOH) bucket and incremented in the unavailable SOH bucket which is for trouble sub-bucket.

– Example 2:

A reason code of Return from repair instructs the system to move the selected inventory by decrementing the unavailable SOH bucket (trouble sub-bucket) and incrementing the available SOH bucket.

§ Inventory Adjustments can be saved as In Progress to continue working on later or confirmed which will move it to a Completed status.

§ All items on an inventory adjustment are grouped together under a single header transaction. However, the inventory adjustments are sent as individual line items to the merchandising system.

§ Stock on Hand and Unavailable inventory are not only used to indicate to a store user what is available to sell, but it also ensures proper replenishment ordering for all the stores through the central replenishment system.

§ Manual or automatic adjustments can be made to the SOH inventory level for an item.

§ System-generated inventory adjustments will not write actual inventory adjustments within SIM, they will appear as transaction history records. However, an adjustment will be published to the merchandising system.

– Example: Receive a DSD with damaged goods. An inventory adjustment is made behind the scenes to move the goods from available stock to unavailable stock for the damaged quantity, and this will be used to send on to the merchandising system. The inventory adjustment will not appear in SIM, rather a transaction history record for the receipt of damages.

§ The system notifies the merchandise system of all inventory adjustments, unless otherwise specified in the table below.

§ Templates:

– Templates allow for quick application and adjusting of the same items, reasons, and quantities over and over.

– The template can be created and then it can be applied to an inventory adjustment. It will default in the items, reasons and quantities from the template.

– A multiplier can be used when applying the template. It will take all quantities on the template times the multiplier.

– Once a template is applied, the quantities can be updated and items can be added or removed.

§ Serialization support:

– Users are allowed to move serialized inventory into unavailable inventory positions or out of unavailable.

– When using auto generated UINs, it is possible to add new serialized inventory into the store when selecting a disposition that would normally increase SOH.

– Moving serialized inventory out of inventory is permitted.

– Serialized inventory cannot be added on templates.

A Summary of Reason Codes and Dispositions

The following table (shown for example purposes) provides a list of SIM’s reason codes that are preloaded, their descriptions, dispositions, and sub-bucket (if configured) that are linked to the reason code.

System reason codes are those used within the SIM system for making stock on hand updates.

The publish indicator will be used for publishing purposes. All reason codes have this indicator set to ‘Yes’ by default on the UI. If it is set to ‘Yes’, then SIM will publish the adjustments that have that reason code. If it is set to ‘No’, those adjustments for that reason code will not be published. This indicator can only be modified for those reason codes that are not system reason codes. For system reason codes, this indicator is ignored as there instances in the system where things may or may not need to be published.

Note: These need to be set up in an identical manner in RMS

Table: Preloaded Reason Codes

Code	Reason Description	Disposition	Sub-bucket	UI	System	Transaction	Publish
1	Wastage	-Stock on Hand		No	Yes	Wastage	Yes
2	Shrinkage	-Stock on Hand		Yes	No		Yes
3	Repair - In	-Unavailable	Trouble	Yes	No		Yes
75	Stock Count Unavailable to Missing	-Unavailable	Trouble	No	Yes	Stock Count (UIN)	Yes all types except Unit and Amount
76	Unit Late Sales Increase	+Stock on Hand		No	Yes	Late Sales	Yes
77	Unit Late Sales Decrease	-Stock on Hand		No	Yes	Late Sales	Yes
78	Unit and Amount Late Sales Increase	+Stock on Hand		No	Yes	Late Sales	No
79	Unit and Amount Late Sales Decrease	-Stock on Hand		No	Yes	Late Sales	No
81	Damaged - out	-Stock on Hand		Yes	No		Yes
82	Damaged - Hold	+Unavailable	Trouble	Yes	Yes	Receiving: Store Transfer, DSD, Wh Delivery
83	Theft	-Stock on Hand		Yes	No		Yes
84	Store Use	-Stock on Hand		Yes	No		Yes
85	Repair - Out	+Unavailable	Trouble	Yes	No		Yes
86	Charity	-Stock on Hand		Yes	No		Yes
87	Stock Count In	+Stock on Hand		No	Yes	Stock Count	Yes all types except Unit and Amount
88	Stock Count Out	-Stock on Hand		No	Yes	Stock Count	Yes all types except Unit and Amount
89	Dispose from on Hold	-Stock on Hand & -Unavailable	Trouble	Yes	No		Yes
90	Dispose from SOH	-Stock on Hand		Yes	No		Yes
91	Stock -Hold	+Unavailable	Trouble	Yes	No		Yes
92	Admin	-Stock on Hand		Yes	No		Yes
93	Store Customer Return	+Stock on Hand		Yes	No		Yes
96	Ready to Sell	-Unavailable	Trouble	Yes	Yes	Receiving: Store Transfer, DSD, Wh Delivery	Yes
180	Customer Order Reservations In	+Customer Order		No	Yes	Reserve POS (pickup) Customer Order	Yes
181	Customer Order Reservations Out	-Customer Order		No	Yes	Cancel Fulfil POS (Pickup) Customer Order	Yes
182	Stock In	+Stock on Hand		Yes	Yes	Moving UIN from another store in Inventory Adjustments	Yes
183	Stock Out	-Stock on Hand		Yes	No		Yes
184	Unit Late Inventory Adjustment Increase SOH	+Stock on Hand		No	Yes	Late Inventory Adjustments	Yes
185	Unit Late Inventory Adjustment Decrease SOH	-Stock on Hand		No	Yes	Late Inventory Adjustments	Yes
186	Unit and Amount Late Inventory Adjustment Increase	+Stock on Hand		No	Yes	Late Inventory Adjustments	Yes
187	Unit and Amount Late Inventory Adjustment Decrease	-Stock on Hand		No	Yes	Late Inventory Adjustments	Yes

Updating Reason Codes

SIM provides a UI which allows the user to add new reason codes to synchronize with those setup in RMS. It is also possible to hide them from users, and it will indicate which are system controlled. A brief description indicates the disposition of the item for easier setup.

Inventory Adjustment Reason Maintenance UI will allow for Inventory Adjustment Reasons to be maintained in a UI versus directly through the database:

§ This screen lists external code, description, disposition, sub-bucket (if configured) use in UI and system required indicator of all the available reason codes in SIM.

§ All the system required reason codes would have its system required indicator checked. Any reason that is marked as system required can not have its reason code, disposition, sub-bucket, and system required indicator changed through this UI. Only description and the use UI indicator are allowed to be modified.

§ The user will not be allowed to delete the inventory adjustment reason codes that are marked as system required.

Note: Some reason codes are flagged as system-required. Do not remove these reason codes. If they are removed, SIM will not function properly.

§ Only records that have a checked value for the use in UI will be allowed for use in the inventory adjustment screen.

§ The change made through this UI is not integrated with RMS. Retailers have to make sure that the changes done in this screen are in sync with RMS.

Figure: Business Process Flow – Inventory Adjustments PC

Figure: Business Process Flow - Inventory Adjustment Reason Maintenance PC

Wastage Functional Overview

Wastage is the process through which inventory is lost over time (for example, bananas turning black).

In order to maintain more accurate inventory values, SIM uses two methods to control wastage:

§ The first method provides users in stores the ability to create wastage product groups. Variance percentage or standard UOM amounts can be set up on the wastage product group. Individual items and item hierarchies can be associated into a product group.

A user can schedule the date when a wastage product group batch process is run, and inventory adjustments are automatically made based upon the variances setup on the product group. Inventory adjustments are sent over the Oracle Retail Integration Bus (RIB) to the merchandising system.

§ The second method is controlled through the sales process. The external audit system provides a percentage or quantity in its sales upload file that indicates by how much the inventory needs to be reduced in addition to the sold quantity.

Each of these methods has a specific use or need. The first method is usually used when an item’s size is reduced because of not being sold over time. For example, meat will become lighter as fluids evaporate. Other items, such as cheese or ham, will only be reduced when the outside layers are cut off to sell the item.

Figure: Business Process Flow (non-sale bases)

Store Orders Functional Overview

Store orders are used to create, change and approve orders to a supplier or transfers requests to a warehouse. When there is a shortage of items, or demand for particular items increases, store users need to have the ability to create store orders. The user selects either a warehouse or a supplier and adds the items and quantities. It then calls order in RMS.

Store ordering functionality is very similar to item request functionality. Unlike item request functionality, which is only valid for items that are on the store order replenishment process, store order functionality is valid for all items, cannot be scheduled and is only available on the PC.

Store Orders also create the purchase order or the warehouse transfer immediately, while Item Requests depend on replenishment attributes and the nightly batch run from RMS.

Store order processing within SIM includes the following features:

§ Create orders for the supplier or the warehouse.

§ Save the creation of the order without approving it.

§ Amend items and orders in SIM that were created either manually or through replenishment in RMS.

§ Delete pending orders.

§ Approve store orders.

§ Query off-invoice deals when editing an existing Store Order to a Supplier.

§ Query item's sales and store orders when editing an existing Store Order.

Figure: Store Orders Business Process Flow – PC

Item Requests

The item request functionality gives the user the ability to request inventory for individual items using the replenishment and sourcing parameters of the merchandising system (RMS) from within the SIM application directly. It is integrated with RMS, whether it is through RIB or Web-service. This functionality empowers the store by giving the store user the ability to manage stock shortages and increased demand using the SIM application.

This functionality differs from that of Store Orders Functional Overview. In terms of item requests, SIM sends a request to the merchandising system that is generally processed using the merchandising system replenishment and sourcing parameters. Store orders functionality, on the other hand, allows the user direct access to the merchandising system (RMS) and does not enforce the replenishment or sourcing parameters of the merchandising system.

A SIM user is able to use item request functionality to request items regardless of the replenishment type normally used by the merchandising system to replenish the item.

All items are sourced from either a warehouse or through a supplier depending on the sourcing parameters for the item specified in the merchandising system. Items specified as using Store Order replenishment (or items that are not set up for auto-replenishment at all) are sourced through the creation of one-off purchase orders or warehouse transfer requests only after the store has requested inventory using the Item Request functionality.

Any quantities requested for items that have a replenishment type other than Store Order are added above and beyond the quantity that is normally sourced through the merchandising system on the item’s next replenishment review date. However, if the requested delivery date falls prior to such an item’s next replenishment review date, the request is sourced through the creation of a one-off purchase order or warehouse delivery request instead. All inventory requested is sourced to the store at the earliest possible date given the replenishment review date, the supplier or warehouse lead time, and any other factors that may influence the time it takes a delivery to reach the store.

For store order replenishment items, the user can specify a time slot during the day by which the ordered items are to be delivered to the store. This is useful for ordering breakfast items early morning (doughnuts), lunch items (sandwiches), and hot meals for the evening. Item requests can be created with timeslot deliveries for as early as today’s date. Security exists on the delivery timeslot fields, at both the store level and the user level. The user cannot delete line items or the master item request if the user does not have data permissions for a selected timeslot.

In addition to being able to manually create Item Requests, the SIM user is able to schedule Item Requests for review through front-end product group screens on a cyclical basis. This functionality facilitates the request of items that are specified as using Store Order replenishment by allowing the user to add individual items, as well as entire sections of the merchandise hierarchy, to an Item Request Product Group. When the Item Request Product Group is scheduled for review, SIM automatically generates a blank Item Request and adds all items within the specified merchandise hierarchies that have a Store Order replenishment type to the Item Request, along with any individual items specified as part of the Item Request Product Group. The user can then enter the actual quantities of the items necessary, and submit the request. Note that the user also has the ability to add items that do not have a Store Order replenishment type to an Item Request Product Group, but only on an individual item-by-item basis.

The following list summarizes the Item Request functionality that is available in SIM. Because of this functionality, the SIM user has the ability:

§ To create an item request product group and schedule it for review.

§ To manually create an unscheduled item request.

§ To search for and view an item request whether created manually by a user or automatically by the product group scheduler.

§ To edit a pending item request.

§ To delete a pending item request.

§ To request a pending item request.

§ To save changes to a Pending Item Request without requesting it.

§ To print an Item Request Report.

The SIM database contains a view called the Item_Request_Report_V that contains all of the data for this report.

Figure: Item Requests Business Process Flow – PC

Price Changes Functional Overview

The retailer uses price changes to change the price of a particular item at a location. Price changes are performed only on the PC.

In the merchandising system (such as RMS), users create the initial retail prices for items that will flow into SIM. After the initial prices have been set, ensuing control of prices is handled through a price management system. The price management system uses price zone structures or different levels to ensure consistent pricing within an area. Regardless of the level at which the initial prices are set, all prices in RMS and SIM are held at the item/location level.

Once users are managing prices in a price management system, they can use a flexible structure to control the retail prices through permanent, promotion or clearance changes. This functionality allows the user to use different sets of locations to control the retail prices of items without being locked into a zone structure. As a result of this flexibility, all prices are held at the item/location level, while they can be managed at higher levels.

In RMS, an indicator at the item/location level determines whether SIM users can request changes to an item’s retail price at a specific location. This indicator is editable and controls behavior going forward but not in the past.

If SIM users have control of the retail price for an item at a location, they are able to send price change requests for permanent price changes, clearances or simple promotions to a price management system. The price management system checks for any conflicts and provides a response to SIM regarding the status of the request. If the request is accepted, the price management system also sends a price change event back to SIM.

SIM users are able to edit and create price events given the following assumptions and restrictions:

§ The item/location store control-pricing indicator must be set to Y for an item.

§ The price event must not be a complex promotion (such as multiple promotions or regular price changes on the same day, buy/get, threshold, min/max).

§ Any change requests, if approved, update the existing price event in the price management system.

§ SIM can modify the retail price and effective dates for a price event. If a user requests a new price change for the same item/location/date instead of changing/correcting the existing price event, the request is sent to a price management system as a new event request. It undergoes conflict checking in the price management system. If any conflicts are found with existing price events, a rejected response is communicated to SIM.

§ If an item/location is not set up for store controlled pricing in RMS, SIM users view all price events that are sent from a price management system, but they have no control over them. SIM is unable to create new price change requests to be sent to a price management system.

§ Communication between SIM and a price management system is handled by Web service call (providing a direct update connection between the applications). Normal operation of pricing assumes that a price management application is available. No manual override is provided within SIM.

§ Time based promotions created in the pricing system can be interfaced with SIM, but these promotions cannot be created through SIM price change request.

§ Prices are interfaced to SIM through the RIB or the bulk price batch.

It is recommended to only run one of the two interfaces at the time.

Figure: Price Changes Business Process Flow – PC

Sequencing Functional Overview

Sequencing functionality provides users the ability to know the relative location of an item in a store. Sequencing a store improves store processes and reduces the time that employees spend looking for items (during a stock count, for example). The retailer can sequence all items in the store and create unique locations to hold the items. The system can prompt users to a specific location to look for a specific item. Sequencing functionality within the SIM system can be accomplished on a PC based deployment, on a wireless handheld device, or on a combination of the two deployment methods.

Sequencing functionality includes two means by which items can be assigned to places within a store: Macro sequencing and micro sequencing. When ordering, the system follows this pattern.

Macro sequences represent the highest level of locations that are set up in the store. The user can create macro locations, assign items to macro locations, remove items from macro locations, move items within macro locations and re-sequence an entire macro location (wireless only).

A micro sequence is the lowest (most granular) item location level.

The following table provides an example of sequencing:

Table: Micro Versus Macro Sequencing

Macro Sequence	Micro Sequence
Produce	Oranges Apples Bananas Oranges
Frozen foods	TV dinners Burritos Burritos
Cereal	Toasted oats

Sequencing is used within Stock Counts and Shelf Replenishment to aid the user in proceeding to the next item during a count.

Figure: Sequencing Business Process Flow – PC

Shelf Replenishment Functional Overview

The replenishment process attempts to ensure that the shop floor inventory is set at a level best suited for customers.

Shelf replenishment functionality within SIM is related to the movement of goods from the back room to the shop floor & backroom to shop-floor. For example, when a user sees that a certain soda quantity is low, he or she can instigate a replenishment process so that more of the soda is moved from the back room when moving goods from backroom to shop-floor.

Shelf replenishment-related processing within SIM includes the following features:

§ The system calculates what should be held on the shop floor to ensure that customers’ expectations of availability are maintained. Store employees are driven to replenish the most urgently needed items first.

§ The system offers a display of the location from which stock can be replenished to ease the search for stock when the shelf replenishment lists are being filled.

§ The system allows shelf replenishment requests to be generated on demand.

§ The system leads the user around the back room in micro sequence order, so that items can be picked in the most efficient matter.

Replenishment requires the available SOH be divided into three buckets: shop floor, back room, and delivery bay. Because of these buckets, shelf replenishment affects almost every area in the application. For example, inventory adjustments and transfers are affected because the system must take the inventory buckets into account when engaging in these areas of functional processing. The system’s available inventory is the sum of the three buckets.

When merchandise becomes available (enters the store through a transfer, a DSD, and so on), the merchandise is always placed in the back room bucket.

The user can create a within-day or an end-of-day shelf replenishment list for capacity based and sales based replenishments. The two different types of shelf replenishment lists have store level configurations for the fill level. Typically an end-of-day shelf replenishment list would have a higher fill level than a within-day shelf replenishment list, as there would be more time to stock the shelves. The difference between capacity based and sales based replenishment is that capacity considers the sequencing to fulfill shop-floor while sales based considers the sales of the item for the day for replenishments.

When the user creates a capacity based shelf replenishment list, the system runs a replenishment calculation that checks for those items that belong to shelf replenishment list product groups. The system takes those items and compares their capacity to their shop floor SOH. The system then generates a shelf replenishment list in order of the items that need replenishment the most and orders them in sequential order for the user. For within-day shelf replenishment lists the system will stop when the amount to shelf replenishment is equal to the amount suggested by the system. For end-of-day shelf replenishment lists the system continues until all items that need replenishing are replenished.

There are 2 more types of shelf replenishments other than capacity based and sales based replenishments, they are Display list and AdHoc Replenish. Adhoc replenishment simply moves the item mentioned on shelf adjustment list from back room to shop-floor, defining capacity is not a mandatory feature for this type of shelf replenishment. Display list is a replenishment method specifically geared towards single unit display items that are used to sell to customers and are related to each other by style. It replenishes goods from backroom/ Delivery Bay to shop-floor using Product group and Display List.

Shelf replenishment lists can be created on the PC or the handheld and can be fulfilled on either device. If they are created on the PC, the user is able to action them on the handheld.

Replenishment Calculation Summary

Once the calculation is started, the system engages in the following processing:

§ The system gets all the items that are sequenced on the shop floor with capacity in the product group.

§ If a previous shelf replenishment list exists for the selected group and it is in progress, the system assumes that all of the items on the shelf replenishment list will be completed. If a previous shelf replenishment list exists and is not started, the system deletes the old shelf replenishment list and creates a new one.

§ The system checks and gets the configuration parameters established through the GUI (group unit of measure, fill percentage, and so on).

§ The system gets the shelf quantities and available SOH for the items found.

§ The system converts the quantities to the correct group default unit of measure.

§ The system compares the shelf quantity to the summed shop floor capacity for every item to determine the percentage the item is out of stock.

§ Once the out of stock percentage is calculated for every item, the system orders the items from the highest out of stock percentage to the lowest. If any of the items have the same out of stock percentage, the system uses the item that has the least amount on the shelf. For example, if item A has 10 out of 100 on the shelf, and item B has 1 out of 10 on the shelf, they both have the same out of stock percentage. However, the system considers item B a higher priority because there is less of it on the shelf.

§ For each item, the system calculates the replenishment amount that should be brought from the back room/delivery bay to the shop floor. Keeping the items in priority order, the system looks at the available SOH, the items in the back room/delivery bay, and to what percentage the shop floor needs to be filled. The system takes the inventory from the back room first and then takes the inventory from the delivery bay. The shop floor quantity can only be equal or less than the capacity.

§ If the shelf replenishment list type is within day, the system stops when the amount to replenish is equal to the summed replenish amount calculated by the system.

§ If the shelf replenishment list type is end of day, the system continues until all of the items are completed.

§ If the system generated replenishment amount is a decimal, the system rounds down to the nearest whole number.

§ The system generates and displays the list in sequence order to the user. If the items are not sequenced in the back room, the system displays the items in item ID order.

Figure: Shelf Replenishment Business Process Flow – PC

Stock Counts Functional Overview

SIM provides the ability to schedule, perform, and authorize stock counts. SIM includes the following types of stock counts, each of which is described in this section:

§ Ad hoc

§ Unit

§ Unit and Amount

§ Problem line

Note: The counting processing is identical among the unit only, unit and amount, and problem line stock count types. What differs among these three stock count types is either the setup or the items being counted.

SIM includes the following types of counting methods for stock counts, each of which is described in this section:

§ Un-guided

§ Guided

§ Third Party

Portions of the stock count functionality, such as the setup of product groups, schedules, and authorizations, are performed on the PC only. The actual counting of inventory can be performed on both the PC and the wireless device. A master count is created for a single product group and is then broken down into one or more child counts based on the counting method or hierarchy breakdown chosen during the product group setup. The user is able to save the child stock count on the PC or handheld and resume at a later time.

Future Stock Counts

Future stock counts are stock counts for which the scheduled date has not yet arrived. The user can view a list of future stock counts, and the user also has the option to generate a future count to view the count details. The user cannot take any action on a future stock count, the purpose is to allow the store to view future workload so that the store can plan ahead for staffing.

Unscheduled Counts – Ad Hoc Stock Counts

An ad hoc stock count is performed by a user walking through the store scanning any items that need to be counted. They have no group or schedule functionality associated with them.

Ad hoc stock count processing within SIM includes the following features:

§ The system creates an inventory snapshot as each item is identified and added to the stock count.

§ Ad hoc counts can only be initiated on the handheld. Once the count has been saved on the handheld, it can be completed later on the handheld or PC; any existing ad hoc stock count can be retrieved and resumed on the handheld and PC.

§ The system utilizes discrepancy thresholds (established in administration setup by the retailer) based on a percentage or standard unit of measure by the item’s class in the merchandise hierarchy.

§ On the PC, the system allows for the authorization of items that are discrepant (based on the percentage or standard unit of measure thresholds).

§ Where the authorized item quantities entered by the user differ from the SOH, the system creates inventory adjustments that are sent to the merchandising system. See Inventory Adjustments Functional Overview in this chapter.

§ It is possible to have multiple users scan for the same ad hoc stock count.

§ Since the user determines the order the items are scanned in, and no predefined list exists, sequencing has no impact to these counts.

Scheduled Stock Counts

Several different scheduled stock counts exist, each with their own specific differences. They do however have common setup pieces.

§ Individual items or item hierarchies are associated into a single unit product group for the purpose of scheduling a stock count.

§ Stock Count product groups can be scheduled for a stock count on a specified day or on scheduled intervals (for example, daily, weekly, monthly, or annually).

§ One or more stores can be assigned to the scheduled stock count, and each store will complete their stock count individually.

§ A group of valid stock count items is generated at the store level using batch processes.

§ Users with proper security are prompted of any discrepancies outside of set tolerances, and the system can automatically force a recount if the discrepancies are too high. The system utilizes discrepancy thresholds (established in administration setup by the retailer) based on a percentage or standard unit of measure by the item’s class in the merchandise hierarchy.

§ An auto-authorization feature can be selected during the product group setup. If set up for auto authorization, SIM automatically authorizes the stock count after the count or re-count has been completed. In this case, no user intervention is needed to confirm the count. For Sarbanes-Oxley Act or auditing process requirements, this can be the optimal way to process a unit and amount count.

§ Retailers can perform their Unit, Problem Line or Unit and Amount stock counts using different counting methods:

Third Party Stock Counts

These stock counts are scheduled in SIM, but the actual counting process is performed using the third-party system. Once the physical stock counting process has been completed, the third-party system exports the results of the count to SIM.

SIM compares the count information with the stock-on-hand (SOH) value currently held in SIM. In SIM, users can view all items in the stock count that are discrepant and non-discrepant when compared to the SOH figure. Pre-defined variance limits (units, percent, and value difference) are used to determine which items fall outside the acceptable level and are therefore considered discrepant.

Any items SIM does not recognize can be added through the Rejected Items dialogue. Items that require UINs can also be assigned UINs through the Rejected Items dialogue.

The items associated to a product group will be associated to a master stock count when generated, which in turn can be broken down based on the hierarchy selected by the user during the product group setup (for example Department, Class, Sub-class).

It is possible to create Third Party Stock Counts for any merchandise hierarchy level supported in SIM.

For Third Party Stock Counts to work, the third party counter needs to receive an extract of the items, quantities and UINs to count from SIM.

This report can be printed to the screen and subsequently saved by a user. The report only needs to be accessible in the stock count dialogue.

The Third Party Stock Count Extraction Report allows a retailer to extract the snapshot value and in store UINs in an XML format that should be counted for a specific stock count. This report may need to be modified by individual retailers for different third parties when performing a stock count, and is only meant as a starting point.

If this report is generated before a snapshot is taken, the UIN and snapshot quantity field will be empty, and so the assumption is that the extract will be created after the snapshot is taken.

Note: This will most often be used to print reports for third party stock counts, however it should work for all stock count types.

This XML report contains the following information:

§ Header:

– Stock Count ID

– Store ID

§ Detail

– Item number (SIM SKU number)

– Item description

– Total snapshot quantity for the item

– UINs for the item

Unguided Stock Counts

When performing a scheduled stock count (unit or unit and amount), the user is able to scan items on the handheld without being prompted for which item to scan. This feature is controlled through the product group setup by choosing Unguided for the counting method. Multiple employees are able to scan items for the same stock count. This feature is controlled through a system option.

Unguided stock counts cut down the time it takes to completely scan a count and provides more flexibility. This process applies to both count and recount processes.

For unguided counts, the retailer can configure SIM to save the item count automatically when the user moves on to count a different item. For example, if the user scans item A three times and then scans item B, the count value for item A is saved when scanning item B. This automatic save reduces the need for store personnel to remember to save count values manually and it allows longer scan times without interrupting the scanning of items for the count. Users might forget to save, and if the system experiences a problem, the data recorded up to that point will be saved if SIM is configured to do so.

Guided Stock Counts

Guided stock counts prompt the user for the next item in sequence. This feature is available for scheduled Unit, Problem Line and Unit and Amount counts and is controlled through the product group setup by choosing Guided count method.

SIM generates a master count that is broken down by location. A Child count is created for every macro location and the user is prompted to scan the next item based on its location within the store. If an item exists in multiple locations, the user is warned if the item has not been counted in all locations.

If sequencing is not set up for the items, the user is prompted in item order.

It is also possible to have these counts automatically processed, ensuring no store interference. This automatic third-party process does not require any counting or approval from store personnel.

Unit-Only Stock Counts

Unit-only stock counts are usually small stock counts setup on a recurring pattern every few weeks or monthly. Unit-only stock count processing within SIM includes the following specific features:

§ Setup of the stock count can be done at the item, merchandise hierarchy level.

§ On the PC, the system allows for the authorization of items that are discrepant (based on the percentage or standard unit of measure thresholds) or non-discrepant, or both.

Unit and Amount Stock Counts

Unit and amount stock counts are usually only done once or twice a year. They are often required by law to be performed once a year and are done for the entire store or specific merchandise hierarchies. They give the retailer the ability to consolidate the actual counted quantities for merchandise and the booking numbers at year end.

Unit and Amount stock count processing within SIM includes the following features:

§ Setup of the stock count can only be done at merchandise hierarchy level.

§ Unit and amount counts are scheduled and counted within SIM and then sent to RMS. RMS accepts the unit variances and the user inputs the variance amounts in Central Office.

§ Unit and amount product groups are scheduled for a specified day.

The stock count schedule for unit and amount stock counts is sent to the merchandising system anytime it is created, updated or deleted.

§ One or more stores can be assigned to the scheduled stock count.

§ A stock count item list is generated at the store level using a batch process that runs daily.

§ On the PC, the system requires the authorization of all items (based on the value, percentage, or standard unit of measure thresholds).

§ Upon completion of authorization, a flat file is sent to the merchandising system with a header that contains the stock count ID, stock count date, and the store number that executed the count. The file contains details for each item and the quantity counted. This information is then staged in the merchandising system and can be used for reporting purposes.

Note: The Export Results button has been removed and results will automatically be exported to the merchandising system upon confirmation of the last child count. The user no longer needs to manually export the results to the merchandising system using the GUI.

Stock Counts UIN Tracking

For items that require UINs, the user must capture the UIN when performing a stock count on the PC or handheld. The count quantity will always equal the number of UINs captured for the item.

The count/re-count stages only allow the user to count UINs that already exist in the store. If a UIN does not exist in the store, the UIN can be added during the Authorize stage. When the count is confirmed, the UIN is created for the current store and the status moves to In Stock.

For UINs that have a status of In Stock after the initial count but move to another status before the count is authorized, SIM does not update the UIN to In Stock upon confirmation. In order to achieve this, a snapshot of the status is taken at the time the snapshot is taken. The snapshot will always be taken at the beginning of the child count, including Unit and Amount counts.

For UINs that exist for the item in the current store but are not counted on the stock count, the status gets updated to Missing upon confirmation of the count.

For AGSN items, SIM requires the user to scan the UINs to capture the quantity as it does for regular serial numbers. During the authorization process, the user is able to adjust the authorized quantity to account for items that are missing UIN labels. The user can auto generate UINs during the authorization process by selecting Auto Generate from the UIN pop-up.

An audit record is created when the stock count is authorized.

The UIN status at the time of authorization is captured and a UIN status results file is created for use in other systems.

Problem Line Stock Counts

This functionality gives stores the ability to create automated stock counts according to predefined criteria (for example, the retailer could decide to count all of the items that have negative SOH values).

Once stores have established the criteria (based upon problematic areas), a batch process runs to find any items that meet the criteria. The found items are added to the scheduled stock count. They are counted in the same way as in a scheduled unit stock count. Note that problem line stock counts will be executed every day.

Problem line stock count processing within SIM includes the following features:

§ Individual items and item hierarchies are associated into a single problem line product group for the purpose of scheduling a stock count.

§ Problem Line product groups schedules will be defaulted to daily, every 1 day and cannot be changed.

§ On the PC, the system allows for the authorization of items that are discrepant (based on the percentage or standard unit of measure thresholds) and non-discrepant.

Note: With the exception of the extraction criteria, the execution (counting, snapshot taking, authorization) is the same as with a regular unit count.

Figure: Business Flow (Unit, Problem Line, Unit and Amount and Third Party)

Note: Third Party count/re-count process is not performed in SIM, it is performed through the third party system.

Figure: Business Flow – Ad Hoc (PC only)

Note: Ad hoc count process is initiated on the handheld by scanning an item. Once the count has been saved on the handheld, the user is allowed to complete the count from the handheld or PC. There is no re-count for Ad Hoc and an Ad Hoc will only have one child count. Authorization occurs on the PC only.

Figure: Business flow – Third Party

Figure: Business Flow - Future Stock Count

Item Basket

Item Basket functionality allows the user on the handheld to scan a list of items. This list of items can be interfaced to other applications through a web service to aid them in specific tasks. These tasks can range from line busting at any third-party POS, using it for wedding list generation or simply identifying trouble items.

Specific features include:

§ Identifying a specific type of basket

§ Scanning or entering quantity for the item

§ Entering or auto generating a unique ID for calling it up

§ Edit, delete and add functionality

§ Print ticket functionality for register scanning

The following is an example of a possible business flow for line busting that can be implemented by the retailers implementing any third-party POS and SIM:

Items are scanned into the Store Inventory Management handheld and the basket is created in Store Inventory Management. Optionally, the customer can be presented with a printed ticket containing a barcode, which can then be presented at checkout.

At any third-party POS terminal, the operator must enter the unique Item Basket ID or scan the barcode from the ticket printed by the Store Inventory Management handheld, and the basket details are retrieved from Store Inventory Management and displayed on POS for item tender.

If a UIN needs to be captured for an item, POS will have this responsibility.

Shipping and Receiving Functional Overview

SIM has six distinctive shipping and receiving dialogs:

§ Transfer Document: Creating, Updating, Deleting and Approving transfer documents.

§ Transfer Shipment: Creating Shipments, Containers, Shipping Documents, and Dispatch.

§ Transfer Receiving: Receiving Internal Deliveries, Containers and Unexpected Containers.

§ DSD Receiving: Receiving Vendor Deliveries by Advanced Shipment Notice (ASN), PO, DEX/NEX, or Unexpected (On the Fly).

§ RTV: Creating, Updating, Deleting, Approving, Vendor Return documents.

§ RTV Shipment: Creating Vendor Shipments, Containers, Shipping Documents, and Dispatch.

Transfer Document Functional Overview

Store, merchandising and supply chain systems create logical documents indicating to systems, like SIM or a warehouse system, what needs to be shipped or received. These logical documents give an intent of what needs to be shipped. To facilitate this inventory control process, SIM includes a transfer document dialogue.

Figure: Transfer Document Dialogue

The transfer document dialogue has the following features:

§ Request creation from both SIM and an external system like a merchandising system for outbound shipments from a store.

§ A formal approval or rejection of transfer requests.

§ A handheld workflow to facilitate the processing of requests. It allows the user to pick inventory based on the requested quantities. This picking flow follows the same pattern as customer order picking or in store replenishment, ensuring a consistent process. This can be especially useful for commerce. Any shipping requests, where the user pre-packages the shipment by printing out a picking report, picking the items from the shelf and actually physically confirming that the store has the inventory available.

§ Transfer requests can be auto-approved in case of tight inventory control from corporate. This will auto-approve the request for the requested quantities.

§ External systems can also generate transfers and transfer requests for unavailable inventory. In some cases inventory is marked as unavailable, because it is defective, recalled or needs to be re-allocated. In those cases the external system could ask SIM to ship directly from the inventory marked unavailable. This shipment can be either to a store, external finisher or warehouse.

§ It is possible to create transfer documents with a not after ship date that is auto defaulted and has several notifications in place to ensure that the transaction is fulfilled in time.

§ Requesting users are able to indicate, if the whole transfer needs to be shipped, or if partial shipments are allowed.

§ An overview is available on what has been shipped, received and details about the shipment record, like which item was shipped on which container.

§ Automatic document close when the not after date is reached.

Transfer Shipment Functional Overview

Shipments to store, warehouse or external finishers are under a single dialogue. This dialogue focuses on building a single shipment to a single entity, containing one or more containers.

Figure: Transfer Shipment Dialogue

Each container is considered as its own logical unit of work and has specific features:

§ Each container can be managed by a different user. This allows multiple people to work on a single shipment at one time.

§ Containers can be marked for available or unavailable inventory. The user can select specific reason codes for each unavailable container in a shipment.

§ Labels for containers can be generated by SIM, or can be manually entered. SIM follows the SSCC-18 standard, when generating labels. The retailer can define different container labeling formats and print them as needed.

§ If the retailer is not printing internal labels, it is possible to get a tracking ID from a manifesting system or manually enter one.

§ It is possible to have multiple transfer documents on a single container, or to reference the same transfer document across multiple containers.

§ Different business processes to build a container are supported.

– Users can enter items on the fly without pre-selecting a transfer.

– Users can select an approved transfer document and have different options to apply the items.

* Just select the document and add items to the container validating against the document.

* Select items and pre-fill in the container without quantities.

* Add items with the remaining quantities from the transfer document.

– Each container will have its own status and user tracking.

– Containers can be restricted by merchandise hierarchy.

– The user can set the entire transaction quickly to cases or standard unit of measure.

Transfer Receiving Functional Overview

Similar to the shipping dialogue, the receiving dialogue holds store, warehouse and external finisher receiving in a single dialogue. The dialogue is fully container enabled, which means that any inbound shipment will have containers.

The receiving dialogue has the following features:

§ The ability to receive at ASN, container or item level depending on the business process.

§ Delivery level information like freight ID, carrier name, type, and address and license plate can be captured.

§ The number of containers can be validated against those physical counted, before container or detailed receiving is required.

§ SIM inventory is updated when receiving the container. The merchandising system is also notified at a container receipt level.

§ Configurations have been added to perform blind receiving. In a blind receiving environment the user does not have the option to see the expected inbound quantities. An exception report and filter will be created to allow a manager or user to review the possible discrepant items.

§ The handheld quick receiving workflow has been updated to receive containers across any ASN, be it store, warehouse, or external finisher.

§ The handheld container barcode scanner allows the user to find containers to receive, based on the internal SIM container ID, the external container ID, and EAN128 barcode or the external tracking ID.

§ Receiving containers marked as unavailable automatically moves inventory to the unavailable bucket.

§ Container exception processing has been added. It is possible to add a completely new container, in case containers, which previously were not on the delivery, are delivered. It is also possible to replicate misdirected containers to the delivery record. In both cases it is possible to reference an original container ID.

§ Tracking can be enabled which will record every container scan for quick receiving and item container scan for detailed receiving by user.

§ Additional smaller features for container level processing include:

– The ability to indicate at container level, if the container should be received on the shop floor or not.

– Indicate a damaged reason.

– Mark a whole container as damaged.

– Enter an external tracking ID or SSCC number.

– Define at the container header level if the units are displayed at the item or case level.

– A Quality Control indicator (backend only) forcing a user to receive in detail.

Allocations are handled as true transactions, which mean they are not deleted automatically when the ASN is consumed.

DSD Receiving and Purchase Order Document

Similar to the logical transfer document and physical delivery document of transfers, the supplier delivery functionality has two dialogues. The logical Purchase Order document, which can be transferred from an external system or be based on a delivery and the physical DSD delivery document.

Deliveries from a supplier include:

– DSD Receiving with PO and an ASN

– DSD Receiving with a PO, but no ASN

– DSD Receiving on the fly (no PO or ASN)

– DSD Receiving Dex/Nex (no PO, but delivery document)

All of these types support multiple containers per receipt and each of these containers can contain one or more purchase orders. DSD receiving has mostly the same features as transfer receiving:

– Receive at delivery, container or individual item level

– Allow multiple users to work in a single delivery with locking at the container level (only single user in a container)

– Perform blind receiving

– Ability to add unexpected containers on the fly

– Identify containers by scanning GS1-EAN128, SSCC, tracking ID or container ID

– Capture header information for delivering entity, license plate, freight ID

– Automatically close the delivery after a certain number of days, and mark the non-received containers as missing

– Receive individually marked containers on the shop floor

– Capture item and container scan entry by user, location and time of receiving

Specific features, which do not exist on the transfer receiving dialogue are listed below:

– PC scan screen that allows quick entry for PO on the fly deliveries, by allowing the user to identify a PO number, a quantity and optional cost by scanning an item

– Restrict the ability to receive against a single PO multiple times

– Depending on supplier restrictions, allow to receive and update inventory in SIM at the container level, or wait until the entire delivery has been received

– Capture a total invoice amount

– Country cost and override cost display for Dex/Nex and delivery on the fly

– Display of primary VPN

– Automatic creation of a SIM PO for deliveries on the fly and Dex/Nex

RTV (Return to Vendor) Functional Overview

The section describes the RTV Third Party count/re-count process. It is not performed in SIM. It is performed through the third party system and RTV requests.

RTV

SIM allows a store user to look up, create, edit, delete, and complete returns directly to the vendor. RTV functionality within the SIM system can be accomplished on a PC-based deployment, on a wireless handheld device, or on a combination of the two deployment methods. Returns to the Warehouse or Finisher are handled in the Transfer and Transfer Shipment dialogues.

The user enters the vendor number or uses the search option to identify the vendor for which the items should be shipped. The user is prompted to enter an authorization code for the return if the supplier requires a return authorization code.

For return to supplier, the user may return available and unavailable items on the same return transaction, thus all return to vendor reason codes will be provided.

To complete an RTV, the user creates an RTV document through the RTV dialogue and approves this document. Once an RTV is approved, it is ready to be shipped. The shipment is created, the user places the items into containers for the shipment, and confirms the containers. The RTV shipment is now ready for dispatch. The shipment needs to be dispatched before the not after date of the RTV. Once an RTV shipment is dispatched, the available/unavailable stock on hand is adjusted.

Item quantities can be entered in eaches or cases. Once the applicable quantities are entered, the user is prompted to enter a reason code for the return. The reason codes are retailer defined. After the reason code is selected, the user may either complete the return or save it to be completed at a later date. Submitting a return is an interim process to save the return and potentially send off a pre-shipment message. Submitting and
pre-shipment are configurable.

Once a return is dispatched, inventory buckets, available or unavailable, will be updated based upon the inventory status associated to the reason code.

Once the return is completed, a return document can be printed to be used both as a report and/or a packing slip for the shipment.

Note: It is only possible to return merchandise directly to the vendor (RTV) from SIM if the vendor is allowed to receive returns. It may be a requirement the vendor is also allowed to deliver items directly to the store; this is based on a configuration.

RTV UIN Tracking

For Return to Vendor transactions, the system will check if the capture time is store receiving for the item. If it is, the user will be required to enter or scan UINs and the quantity field will be equal to the number of UINs entered/scanned for the item. Saving the transaction will move the UINs to Reserved for Shipping status.

If the UIN added to the return is in unavailable status, SIM assumes the user wants to use unavailable inventory for the return. A separate check for unavailable inventory is not needed for UINs.

If the UIN is not assigned to the current store, the UIN is not allowed to be added to the return.

Once dispatched, the UIN will move to Shipped to Vendor for RTVs.

An audit record is captured for each status change.

RTV Requests

Return requests functionality enables return requests to be fulfilled from a store to a vendor (RTV) that were generated using the merchandising system.

A return request might be generated by a safety concern (for example, glass shards are discovered in a product). The functionality can be summed up as a return generated by the merchandising system that can be edited and approved in SIM. Return requests functionality within the SIM system is accomplished only on the PC-based deployment.

Once SIM receives the return request data, it takes over the request and allows store users to add, edit, delete, save, and dispatch the return request. Once the request is deleted or dispatched, a message is sent back to the merchandising system.

Updating Reason Codes

SIM provides a UI (Shipment Reason) which allows the user to add new reason codes to synchronize with those set up in RMS. System required reasons will be indicated and defaulted per data seeding. Shipment reasons are used to indicate the reason an item is being returned to the supplier, warehouse or finisher. Supplier returns are handled thru the RTV/RTV Shipment dialogues and warehouse or finisher returns are handled thru the Transfer Shipment dialogue.

Those reasons that have an inventory status of unavailable may also have a sub-bucket assigned if system configured to use sub-buckets. This can be done through Shipment Reason maintenance.

Customer Order Management

Upon entering the Customer Order Management dialogue, the user will see all open transactions that are pertaining to customer orders for the user's store. Customer Order may be the POS pick up type of customer order, or they maybe the web order customer orders. The user can use the filter dialogue to filter the criteria further. From this screen the transactions can be accessed by double clicking on any of the records in the list.

Transactions will include:

§ Customer Order

§ Pick

§ Delivery

§ Reverse Pick

§ Transfer

§ Transfer Receiving

§ Transfer Shipment

§ DSD Receiving

This screen also allows access to the Customer Order and Customer Order Picking dialogues.

Customer Orders

Customer Orders can be viewed from either the Item Detail screen for a particular item, or from the Customer Order dialogue within Customer Order Management. Customer Orders are view only and provide information to the user about the customer order including:

§ Customer Order ID

§ Fulfillment Order ID

– Can have multiple fulfillment orders per customer order. Only for web order reservation types.

§ SIM Customer Order ID (internal unique ID)

§ Order Status

§ Reservation Type

§ Order Create Date

§ Order Release Date

§ Order Delivery Date

§ Delivery Type (pick up or shipment)

– Pick Up for non “web order” reservation types

§ Carrier

§ Service

§ Allow Partial Delivery

§ Notes

– Notes can be maintained on the customer order, delivery or reverse pick and be stored on the customer order.

§ Item

§ Item Description

§ UOM

§ Pack Size

§ Remaining Quantity (quantity left to be shipped or picked up)

§ Order Quantity

§ Picked Quantity

§ Delivered Quantity

§ Canceled Quantity

§ Last Update Date

§ Comments

§ Substitute

– The original item that the current line item was substituted for.

Customer Orders that are “web orders” will have inventory reserved either upon getting the customer order into SIM from the OMS or it will happen when receiving a delivery that contains the customer order (store, warehouse, or DSD delivery). This is dependent upon a configuration. In both cases, the customer order must be in the system in order to reserve the inventory. When reservation occurs a message is published out from SIM.

Customer Order Picking

Some retailers will want to have a formal customer order picking process in place to pick the customer orders and set them aside for the customer. Other retailers will find that this is not necessary and they will just go and get the items informally when the customer order comes into the system. Picking is a process that can be configured to be required or optional. Picking is only used for "web order" reservation type of customer orders.

In the manual picking process, a retailer may choose to pick by bin or by customer order. When picking by bin the retailer can pick multiple customer orders at a time. The retailer will tell the system how many bins to pick and the system will apply an algorithm to find the oldest customer orders where there are items with available stock and items left to be picked. The system will fetch one customer order per bin. When picking by customer order, the user will tell the system what customer order to be picked and that single order will be added to the pick.

Once the pick is created the user will walk the store picking the items prompted on the pick based upon a system suggested pick quantity. As the items get picked the user would set them aside. Upon completion of the pick, the pick quantity on the customer order would be incremented and SIM would publish out a pick message.

During the picking process, it may be necessary to substitute an item. In order for this to happen, the item on the customer order must first allow for substitute items. If substitutes are allowed, there are two options for choosing substitute items based upon configurations. One, the system does not allow for user discretion and only a list of substitute items provided from RMS can be used. Second, the system allows for user discretion and the user can choose from a list of RMS provided substitutes, or choose any substitute item at will.

There may also be items that are difficult to pick the suggested pick amount. These items are typically variable weight, each item, such as Lbs, KG, meters. It is possible to setup tolerances at a sub-class level for customer order picking, similar to those for Adhoc stock counts. The tolerances will allow the user to over pick within the defined tolerance. Example: Ordered 2 LBs Bananas. The Fruit sub-class has a tolerance of 10%. User picks 2.1 LBs which is within the 10% tolerance of 0.2 Lbs.

Customer Order Deliveries

Customer Order Deliveries allows for the user to fulfill the customer order by creating a delivery for a customer order. A delivery may be a shipment to the customer or it can be a pick up for the customer order. For the POS pick up customer orders, deliveries cannot be created by the user, rather they will be created upon receiving a customer order fulfillment record from POS and they will be in a “completed” status and view only. For “web order” customer orders, the user can create and edit customer order deliveries.

It is possible to create multiple deliveries per customer order so long as there is a remaining quantity left to be fulfilled. Each delivery will be listed for the customer order. If picking is configured to be required, it will be necessary to have everything picked prior to creating the delivery. When creating the delivery, the user will enter the quantity to be delivered that is less than what is remaining .The system will validate if a partial delivery is allowed per the customer order. If it is not the user will be prompted and the delivery must be delivered in full (unless user has special security permission to override).

The delivery can be saved, submitted or dispatched. Submitting a delivery is an interim process to save the transfer and potentially send off a pre-shipment message. Submitting and pre-shipment are configurable. Once a delivery is dispatched the stock on hand and reserved quantities will be decremented from the user's store. The deliveries which are shipments will publish and ASNOut message.

Customer Order Reverse Picks

Canceling of “web order” customer orders might also come into SIM from an external OMS system. If all of the items being canceled have not been picked, then a completed status reverse pick will be generated and no action is needed from the user. The canceled quantity on the customer order will be incremented. When a cancelation comes into SIM, if there are items to be physically unpicked, then a reverse pick list will be generated. The reverse pick will require action. The system will suggest the quantity needed to reverse pick based upon the cancellation that came into SIM. Upon completion of the reverse pick, the pick quantity and reserved quantities will be decremented as well as incrementing the canceled quantity.

A manual reverse pick might also be necessary. This would happen, for example, when the user discovers that something was picked and has been damaged. A manual reverse pick may be created in SIM which would reduce the pick quantities. In this case the reserved quantity and canceled quantity does not get updated. This is because the items are not canceled, they are just un-picked.

Reverse picks can be saved to be completed later or completed now. Reverse Picks are an exception process and therefore they are only available on the PC application.

Figure: Customer Order Management Business

Lookups

This section describes lookups.

Item Lookup

SIM provides store users the ability to query basic item information and search for stock in other store locations. All of the lookup functions have filter status on which to search. For example, a user can search for items by item number, description, supplier, and/or merchandise hierarchy. The information that can be searched on and displayed to the user is as follows:

§ Search Criteria will always allow for:

– Item Number (for example, UPC, SKU, UIN, GS1, VPN)

– Unique Identification Number (UIN)

– Item Description

– Brand

– (Primary) Supplier Name

– (Primary) Supplier Number

– Warehouse

– Finisher

– Style (Parent id)

– Merchandise Hierarchy

– Ranged indicator

– User-Defined Attribute (UDA): UDA Text, Value, or Date

– Inventory Status (Available or Unavailable inventory)

§ Information Displayed:

– Item Number (SKU)

– Item Description

– Item Image

– Supplier Name

– Supplier Number

– Primary UPC/EAN Number

– Brand

– VPN

– Primary Supplier

– UIN Detail

– Item/Location ranging

– Primary Sequence Location

– Unit Of Measure

– Store Pack Inventory

– Concession/Consignment Item

– Inventory – defaults to the store the user is logged on to and displays the following categories in units:

* Total Stock on Hand

* Available Stock on Hand

* Shop Floor

* Backroom

* Unavailable Stock

* Transfer Reserved

* RTV Reserved

* Customer Order

* Nonsellable

* Delivery Bay

– Stock on hand at other store locations (Stock Locator)

– Expected Deliveries (Deliveries)

– Customer Orders

– Nonsellable (if sub-buckets are configured):

* Department, Class, and Subclass

– Item differentiators and their related items

– Primary Pack Size

– Pricing – Current and Regular Retail Price

– Price Status – Clearance, Promotional, Market

– Regular Multi Price information

– Price History

– Item Status – active/inactive

– Next Planned Deliveries (allocations, transfers, supplier):

* Received Today

* Ordered Qty

* Inbound Qty

* Next Delivery Date

* Next Delivery Type (transfer or purchase order)

* Next Delivery Qty

– Replenishment Method

– Reject Store Orders – for store orders

– Next Delivery Date- for auto replenishment items

– UDA Detail

In an effort to reduce the number of keystrokes, if a lookup on an item is done during the processing of a separate function (that is, a transfer), the ability to use the item directly from the search is enabled. For example, the user can search for an item or supplier directly from the transfer screen, select Apply, and the information will default into the transfer currently being created.

The handheld will display the same information but also has a walk through lookup function. This feature allows the user to scan a specific item and walk through the different differentiators of the item. The user is then presented with the on hand positions and details of the found item. This is especially useful when a customer cannot find the item, but the store has a very similar item. For example, the user presents a black large T-shirt, but the item the customer actually wants is a red medium sized T-shirt.

The user will also find in this dialogue some rudimentary information on customer orders.

Figure: Item Lookup PC Screen Flow

Item Image URLs

SIM enables a customer to define a URL to an image for an item. When the application server is inside a firewall and the referenced images are outside the firewall, the managed server that runs within the application server might need to be started with JVM options defining the proxy server through which URL requests must pass to get outside the firewall, to access images.

The following is an example of these settings:

export JAVA_OPTIONS="-Dhttp.proxyHost=myproxy.mycompany.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|127.0.0.1|*mycompany.com|10.141.* -Djava.net.preferIPv4Stack=true"

These settings must be passed to the managed server JVM during startup. This is usually done within the shell script that launches the managed server.

Supplier Lookup

SIM provide users with the ability to query information on suppliers. Search criteria include: Supplier ID and Supplier Name.

The following is displayed after a search is performed:

§ Supplier Name

§ Supplier Number

§ Supplier HQ Address, Phone, Fax, Contact, E-mail Address

§ Supplier Returns Address, Phone, Fax, Contact, E-mail Address

§ Status of the supplier

§ Returns Allowed indicator

§ Return Authorization Required indicator

§ Allow Discrepancy

As with the item lookup functionality, if a lookup on a supplier is done during the processing of a separate function (that is, a transfer), the ability to use the supplier directly from the search is enabled. When accessed from other areas of the application, item will also be available as a search criteria.

Supplier Lookup functionality is available on both the handheld and the PC.

Figure: Supplier Lookup PC Screen Flow

Container Lookup

SIM provides users with the ability to query shipping container information and displays both incoming and outgoing containers and the following:

§ Container ID

§ Type

§ Location

§ Incoming/Outgoing

§ Container Status (Received, Shipped, and so on)

§ Item information

§ Receipt or Dispatch Date and Time

§ Number of SKUs – unique SKUs

§ Customer Order flag – yes/no/mix (mix indicates not everything in the container is a customer order.

This functionality is available on both the handheld and the PC.

Figure: Container Lookup Business Process Flow – PC

Transaction History Lookup

SIM provides users with the ability to query the transaction history for a store. It will display all transactions that increase or decrease stock on hand.

Search criteria will include:

§ From Date

§ To Date

§ Tran Type (for example, DSD Receiving, RTV)

§ Reason

§ Item

§ User

The display will include the following:

§ Date

§ Transaction type

§ Transaction ID

§ Item

§ Item Description

§ Reason

§ SOH

§ Unavailable

§ User

Figure: Transaction History Lookup PC Screen Flow

Ticketing Functional Overview

SIM allows stores to print shelf edge labels and item tickets for stock manually or by scheduling printing using product groups. Groupings of item tickets (batches) can be managed on the PC for mass printing. Tickets and labels can also be auto-generated when price changes, description or QR changes are introduced to SIM from external systems.

Tickets can be created on the PC in the following ways:

1. Manual:

a. Individual ticket—When creating an item ticket, the user provides the quantity of the item to print and an override price (if necessary). The override price in ticketing is used to indicate the old price or a special promotion allowing the user to show the mark down on the tag.

Note: This override price does not generate a price change.

b. Pricing dialogue —Users can also send tickets to the Print dialogue to print at a later time by selecting price changes from the price change list screen and then and having it added to the Print dialogue.

c. Regular price changes - Users can also create item tickets for regular price changes: the price event is selected and the corresponding price event on the Add Transaction screen is accessed from the Item Ticket Batch List screen. Item Tickets would then be generated for the items on the price event.

d. Clearance price events - Users can also create item tickets for clearance price changes: the price event is selected and the corresponding price event on the Add Transaction screen is accessed from the Item Ticket Batch List screen. Item Tickets would then be generated for the items on the price event.

e. Promotion price events – Users can also create item tickets for promotion price changes: the price event is selected and the corresponding price event on the Add Transaction screen is accessed from the Item Ticket Batch List screen. Item Tickets would then be generated for the items on the price event.

f. Expected Containers - Users can also create item tickets for expected containers for a delivery: the ASN is selected and the corresponding containers on the Add Transaction screen is accessed from the Item Ticket Batch List screen. Item Tickets would then be generated for the items expected in the container.

g. Received Containers —Users can also create item tickets for received deliveries: the ASN is selected and the corresponding received shipment on the Add Transaction screen is accessed from the Item Ticket Batch List screen. Item Tickets would then be generated for the items on the receipt for the received quantities.

2. Automatic:

a. Item description changes – The system may be configured to automatically generate a ticket when item description changes come in from a merchandising system.

b. Price changes received from an external system – The system may be configured to automatically generate a ticket when regular price, clearance and promotional price changes come into SIM from an external price management system.

c. UDA changes for an item – The system may be configured to automatically generate a ticket when a UDA is changed for an item from a merchandising system.

d. QR Code changes - The system may be configured to automatically generate a ticket when a QR code is changed for an item from a merchandising system.

e. Sequence Location Change - The system may be configured to automatically generate a ticket when a sequence location is changed for an item from an external system.

f. Web Service – The system may be configured to automatically generate tickets when a third party ticketing service imports the tickets into SIM.

The handheld can only print manual individual created tickets. It is possible to use belt printers as long as they have their own unique printer network ID.

Label formats and label quantities will be maintained at the micro sequence location level for items setup in sequencing. This allows for defaulting label types based on Primary Location.

Formats are templates created in external systems that define the layout of how a ticket is printed. Formats are setup in the output tools or devices used to produce them. An output tool could be a printer or a software tool such as Oracle Business Intelligence Publisher. SIM only references the name of the format so it can be referenced by the external printing application.

Formats may then be assigned to various price events based on merchandise hierarchy.

Figure: Ticketing PC Screen Flow

Print PC Screen Flow.jpg

Ticketing UIN Support

SIM automatically prints tickets when a serial number is auto-generated. A ticket for the AGSN can also be printed using the Item ticketing dialogue. Serial numbers cannot be printed.

Unique Identification Number (UINs)

The section describes the UINs.

Functional Overview

Retailers who sell items such as electronics, cell phones, weapons, medication, and fresh items often have to track unique numbers or attributes for a single item or a group of items. These numbers are often called serial numbers, batches, unique identification numbers, FCC ID, expiration ID, and so on.

SIM now supports unique identification number logic. The retailer can track the individual instance of an item in SIM from the moment it enters the store until the moment it leaves the store, resulting in better inventory control. UIN tracking is expected to reduce shrinkage, hold stores accountable for individual items, and increase customer satisfaction.

In SIM, UIN functionality allows the user to:

§ Lookup a UIN

§ View audit trail of UINs

§ Resolve UIN discrepancies

§ Update UIN status

§ Receive UINs (Direct Delivery, Warehouse Delivery, Transfer)

§ Count UINs (Stock Counts)

§ Perform Inventory Adjustments on UINs

§ Prints (Ticketing)

UINs can be captured at the time of sale (Oracle Retail Point-of-Service) or at the time of store receiving (SIM). If the UIN is captured at the time of the sale, Point-of-Service captures the UIN and the UIN is not tracked in SIM. If the UIN is captured at the time of receiving, SIM captures the serial number when it arrives in the store using a direct store delivery or warehouse delivery. UINs can also be pre-populated on the delivery.

UINs are not allowed for type 2 items, non-inventory items, notional packs, non-sellable simple packs, concession items and consignment items.

Auto Generated Serial Numbers (AGSNs)

SIM also has the ability to auto generate UINs and track the item with that UIN number. The UINs are created during the receiving process and a label is generated for each of these units.

Auto-generated serial numbers will be generated during the receiving process or while performing a stock count or inventory adjustment. If auto generation is being used during the receiving process, the UIN is captured and the UIN information is provided to the user after receipt confirmation.

An auto generation process generates UINs in a sequenced order and assigns to items as needed during DSD receiving, Warehouse Delivery, Transfer Receiving, Stock Counts and Inventory Adjustments.

The default process uses a sequence generated number and is configurable so the customer can enter a desired starting point or hook it into an external service (through customizations).

An audit record is captured for each UIN that has a status updated.

When an item is scanned during the receiving process, the system checks to see if a UIN is required to be captured for the item. If the UIN type is set to Auto Generation (AGSN), the Auto Generation routine will be called and the generated number is displayed on the UIN pop-up after the items have been confirmed for the warehouse delivery, DSD, or transfer.

SIM will automatically print an item ticket with the newly generated UIN number.

Note: The print option will only be available for generated UINs. The user will not be able to print UINs that are not auto generated by the system.

§ UINs are auto-generated upon receipt confirmation of a warehouse delivery or direct store delivery and labels are printed for each UIN

§ UINs are auto-generated for incoming transfers that are received from a store that does not capture UINs

§ UINs are auto-generated for inventory adjustments with disposition movement of OUT -> ATS and a ticket prints automatically

§ Ability to print/re-print AGSN from Item Ticket Detail screen and UIN Detail screen

§ UINs are auto-generated for receiver unit adjustments where the quantity has increased

Note: For externally created adjustments, manual intervention is needed.

AGSN Auto-Ticket Printing

When a new AGSN item is received, SIM automatically prints a ticket.

To improve performance while receiving serialized items, the generated UINs are stored in a print batch table, grouped by a batch ID. This batch ID is pushed to a staging queue. This ends the receiving operation.

A polling timer picks the staged UIN print batch message and prints the UINs as a batch through a UIN print batch consumer.

Instead of printing AGSN item tickets directly upon the receipt, the printing goes through the polling timer. Printing is done asynchronously, depending on the frequency of the polling timer.

The AGSN report template prints multiple pages (batch UINs) or a single page (single UIN).

UIN AutoNumber

To facilitate the application of serial numbers (UIN), SIM adds a new process that creates the UIN and tracks the item with that number.

During the receiving process, SIM registers how many units are received and generates a label for these units. The process will be identical to how a user receives without capturing UINs, but units are tracked.

The benefits for such a model is the speed of the receiving, which can be done at container level, and removes difficulties some users encounter, for example, trying to find the barcode on large items such as a refrigerator, or determining how to track an item such as a cell phone, which has three barcodes.

For auto-generated serial numbers, SIM bypasses entering individual specific serial numbers at the time of receiving and simply accepts a quantity. This operation is the opposite of normal serial number operations. The quantity entered is then used to generate serial numbers and assign them to the particular item.

AutoGenerateSerialNumberDao contains APIs to retrieve a number of new IDs (or serial numbers) based on the count parameter. This is handled by getting the next values from the AUTO_GENERATE_SN_SEQ sequence. SIM can be modified to generate any sort of serial number the user needs by changing dao.cfg. The user can plug in any class in the AUTO_GENERATE_SERIAL_NUMBER_DAO=xxx line and implement any process to generate serial numbers.

If a previously existing auto generated serial number is scanned, it is treated identical to regular serial numbers.

Table: Enumerations

Enumeration	Description
FunctionalArea	Describes the business functional area and sometimes phase of the business process.
UINType	Describes the type of a UIN. Currently only SERIAL and AGSN are available.
UINStatus	Describes the status of the UIN.
UINCaptureTime	For the specific item and store, it defines the time when a new UIN may be captured and inserted into the data store. Either SALE or STORE_RECEIVING.
UINAvailability	Used as a parameter when searching for records based on availability.
UINActionType	This represents action type that triggered a UIN update (namely from a web service).

Table: UINStatus

Name	Code	Description	Comment
IN_STOCK	0	In Stock	This status can be sold, inventory adjusted, stock counted, shipped, reserved for shipping and reserved for sale.
SOLD	1	Sold	This status is considered a final status and can only be changed through a stock count, return or inventory adjustment.
SHIPPED_TO_WAREHOUSE	2	Shipped To Warehouse	This status is considered a final status and can only be changed through another receipt or special inventory adjustment.
SHIPPED_TO_STORE	3	Shipped To Store	This status can be changed to in stock when the item is received, unavailable if the item is damaged during return or removed from inventory in case it is short received.
RESERVED_FOR_SHIPPING	4	Reserved For Shipping	This status indicates UIN on return or transfer.
SHIPPED_TO_VENDER	5	Ship To Vendor	This status is considered a final status and can only be changed through another receipt or special inventory adjustment.
REMOVED_TO_INVENTORY	6	Remove From Inventory	Set when an item is removed from stock. Only can be changed if item is moved back into inventory.
UNAVAILABLE	7	Unavailable	Set when inventory adjustment is made to unavailable, damaged received quantities or when item is reserved for customer orders.
MISSING	8	Missing	Will be set when a stock count can not find the serial number or the item goes missing during a shipment.
IN_RECEIVING	9	In Receiving	This means that a receipt is In Process but has not yet been confirmed. This can occur during DSD Receiving, Warehouse Receive or Transfer Receiving.
CUSTOMER_RESERVED	10	Customer Reseved	This status will be set when Oracle Retail Point-of-Service uses the customer order Web service to communicate a UIN that is reserved for a customer order.
CUSTOMER_FULFILLED	11	Customer Fulfilled	This status will be set when Oracle Retail Point-of-Service uses the customer order web service to communicate a UIN that is fulfilled for a customer order.
SHIPPED_TO_FINISHER	12	Shipped To Finisher	The state which an item should be in when receiving from a Finisher.
UNCONFIRMED	99	Unconfirmed	This means a UIN has been scanned or entered but has not yet been processed. The UIN is in a temporary state and can move from None to any other state during validation. Note: The functional identifier will not exist until the transaction has been completed.

Note

UIN Open Status = IN_STOCK, RESERVED_FOR_SHIPPING, UNAVAILABLE, CUSTOMER_RESERVED and IN_RECEIVING.

UIN Closed Status = SOLD, MISSING, SHIPPED_TO_STORE, SHIPPED_TO_WAREHOUSE, SHIPPED_TO_VENDOR, SHIPPED_TO_FINISHER, REMOVE_FROM_INVENTORY and CUSTOMER_FULFILLED.

Table: UINAvailability

Name	Description
OPEN	Open
CLOSED	Closed
ALL	All

Used as a parameter when searching for records based on availability.

Table: UINActionType

Name

SALE

RETURN

VOID_SALE

VOID_RETURN

This represents action type that triggered a UIN update (namely from a web service).

Auditing

Any time a status change occurs for a UIN, an audit record is captured and is available for viewing on the UIN History screen.

UIN Setup

A store parameter allows the user to turn on/off UIN functionality by store. Multiple system parameters control the purging of UIN information.

SIM provides a store/class level setup for UIN attributes. These attributes can be auto-defaulted in based on a system parameter. When attributes are added or modified at the class level, the attributes will be applied to each item/location level for all items that belong to the specified department/class.

The UIN attributes screen is required for standalone implementations of SIM. The UIN Attributes screen should not be used if the retailer plans to pull attributes from an external system.

UIN attributes include the following:

§ Type of UIN (AGSN/Serial Number)

§ Capture Time (Store Receiving/Sale)

§ UIN Label

§ Ticket Format (AGSNs)

§ External system create UIN

UIN Status

Each time an item with a UIN is scanned, SIM captures the status of that item. Depending on the functional area for which that item is scanned, a different status will be assigned. This feature allows SIM to ensure data integrity and provide an audit trail of the life of the item.

Before any transaction is completed (dispatched or confirmed), SIM validates that the status of the items on the transaction are still valid.

For example, a UIN on a transfer might be invalid if a stock count cannot find the item and move the Reserved for Shipping status to missing. The item will stay on the transaction, but the user must remove it before dispatching. SIM lets the user know the item is not in a valid status anymore.

UIN Statuses

Unconfirmed

A UIN has been scanned or entered but has not yet been processed. The UIN is in a temporary state and can move from Unconfirmed to any other state during validation.

In Stock

The item is in stock and can be sold. This status is usually achieved after an item is received, returned or when it is fixed from a repair.

In Receiving

A receipt is In Process but has not yet been confirmed. This can occur during DSD Receiving, Warehouse Receive or Transfer Receiving.

Sold

The item has been sold to a customer. The UIN status can get set to Sold through the new Point-of-Service Web service.

Reserved For Shipping

Any time a transfer or a return is created and saved the UIN is marked as Reserved For Shipping. Only UINs in “In Stock” and “Unavailable status” will be allowed to be shipped.

Shipped To Store

When a store-to-store transfer is dispatched, the status of the UIN is set to Shipped To Store. In order to update the UIN to Shipped to Store a UIN must be In Stock or Reserved for Shipping.

Shipped To Warehouse

When a warehouse shipment is dispatched, the status of the UIN is set to Shipped to Warehouse. In order to update the UIN to Shipped to Warehouse a UIN must be In Stock, Reserved for Shipping, or Unavailable status.

Shipped To Vendor

When a vendor return shipment is dispatched, the status of the UIN is set to Shipped to Vendor. In order to update the UIN to Shipped to Vendor a UIN must be In Stock, Reserved for Shipping, or Unavailable status.

Shipped To Finisher

When a finisher shipment is dispatched, the status of the UIN is set to Shipped to Finisher. In order to update the UIN to Shipped to Finisher a UIN must be In Stock, Reserved for Shipping, or Unavailable status.

Removed From Inventory

A UIN will be updated to Removed From Inventory using either an Inventory Adjustment or a Short Receipt. In order to update the UIN to Removed From Inventory a UIN must be In Stock, Shipped to Store or Unavailable status.

Missing

A UIN will be updated to Missing when performing a stock count. If an item is not found that is currently In Stock, Reserved for Shipping or Unavailable, the UIN will be updated to Missing.

Unavailable

A UIN will be updated to Unavailable either through an Inventory Adjustment or a Damaged Receipt. A UIN must be in either In Stock, Sold, Shipped to Store, Customer Fulfilled, Removed from Inventory, or Missing Status before it can be moved to this status.

Customer Reserved

This status will be set when the Oracle Retail Point-of-Service uses the customer order Web service to communicate a UIN that is reserved for a customer order:

§ The selling service to validate the item is valid to be sold will be used to validate that the UIN is available to be reserved.

§ A UIN must be in either In Stock, Customer Order Fulfilled before it can be moved to this status.

Customer Fulfilled

This status will be set when Oracle Retail Point-of-Service uses the customer order web service to communicate a UIN that is fulfilled for a customer order:

§ The selling service to validate the item is valid to be sold will be used to validate that the UIN is available to be fulfilled.

§ A UIN must be in either In Stock or Customer Order Reserved before it can be moved to this status.

Resolving UIN Discrepancies

UINs can be resolved in multiple ways, depending on what the discrepancy is.

The user can view discrepancies on the Resolution List screen. The UIN Resolution screen will display all exception records that were created due to attempting a status change that is not allowed using one of the following:

§ UIN Update Status Web Service

§ Customer Order Web Service

§ Externally generated Receipt Adjustments

When a UIN store mismatch occurs, an e-mail notification is sent to the store with which the UIN was originally associated. This applies to Transfers, Inventory Adjustments and Stock Counts. These discrepancies do not appear on the Resolution list screen, instead the notification will occur through an e-mail and can be resolved by adding the item to a Problem Line stock count or resolving it through an inventory adjustment.

Resolving the UIN record on the UIN Resolution screen does not resolve the discrepancy on the transaction. The recommendation is to resolve the discrepancy by fixing the issue on the transaction or by doing an inventory adjustment:

§ The UIN discrepancy can be resolved directly through the transaction from where the discrepancy originated. This is the recommended business process.

§ The user can check the UIN Discrepancies flag when creating a Problem Line count using Product Group setup. This will add discrepant UINs to the count and resolve the discrepancy through completion of the stock count.

§ The status of the UIN can be updated directly from the UIN resolution screen. This automatically marks the record as resolved. This does not resolve the inventory discrepancy.

§ The UIN record can be moved to resolved on the Resolution screen by clicking Resolve from the UIN (without updating the status or the inventory).

For Third Party stock counts, UIN discrepancies can be resolved through the Rejected Items screen. If the UIN is not present for an item that requires a UIN when the third party count is uploaded to SIM, the record will be written to the Rejected Items table for later resolution. The Rejected Items screen allows the user to assign a serial number for those items.

Whenever an invalid UIN is scanned on any type of stock count, the invalid UIN will appear on the Rejected Items screen. A user with the proper permissions can review the invalid scans and assign a valid UIN to bring the UIN back into the stock count if desired.

Examples of Resolving Discrepancies

The following includes examples of resolving discrepancies.

Example 1 – Store Mismatch: Allow Unexpected UINs parameter is Set to Yes

1. Transfer Shipment/Delivery sent from Store A to Store B.

2. Store B receives the transfer Delivery. Item 1 was not on the transaction, however it did get shipped on the truck so Store B receives the unexpected UIN.

3. The UIN is now associated with Store B and an e-mail will be sent to Store A to notify them of the discrepancy. The item/UIN was not on the transaction and therefore the item/UIN is still reflected in Store A's inventory.

4. The user can create a problem line stock count at Store A and check the UIN Discrepancies flag. This action will place Item 1 on the stock count and resolve the inventory discrepancy once the count is completed. The discrepancy could also instead be resolved using an inventory adjustment to move the UIN out of stock.

Example 2 – Store Mismatch: Allow Unexpected UINs Parameter is Set to No

1. Transfer Shipment/Delivery sent from Store A to Store B.

2. Store B receives the transfer Delivery Container. Item 1 was not on the Container transaction, however it did get shipped on the truck so Store B attempts to receive the unexpected UIN but SIM does not allow it.

3. The UIN is still associated with Store A. Store B will have to call Store A and have them create a new transfer Shipment so Item 1 moves out of Store A and into Store B. An exception record is not created on the Resolution List screen for either store since SIM never allowed the UIN to change status from one store to another.

Note: If the user chooses to update the status using the Resolution list screen, they still must create the transfer so that the inventory gets updated correctly.

4. Once the status has been updated by Store A, the Store B user can now receive the item.

Example 3 – Resolution List Screen: Customer Order Web Service

1. Customer Order Web service calls SIM to move item to Customer Order Reserved and the item/UIN is not in stock.

2. SIM records a discrepancy error on Resolution List screen.

3. The user creates an inventory adjustment to bring the UIN In Stock.

4. The user can log in to the store called by the web service and update the status to Customer Order Reserved using Resolution List screen.

Example 4 – Update UIN Status Web Service Processing ACTION = SALE or VOID-RETURN

1. UIN is found and is in one of the following statuses:

§ Unavailable

§ Sold

§ Reserved for Shipping

§ Shipped to Store

§ Shipped to Warehouse

§ Shipped to Vendor

§ Missing

§ Customer Order Reserved

§ In Receiving

§ Removed from inventory

2. UIN cannot be updated to Sold if it is in one of the statuses from Step 1, so an exception record is created and appears on the Resolution List screen for the store.

3. Depending on the integration, the user must update the status of the UIN manually from the UIN Resolution List screen and re-process the transaction, or just update the status of the UIN.

The unified web service will not update the SOH if the status does not match. The UIN status update web service, on the other hand, will fail independently from the sales transaction web service or ReSA upload file. Fixing the problem for the UIN status update web service will only require a status update. The unified web service call might require a status update to In Stock and a re-process of the entire record.

Note: User might need to remove the UIN from the physical transaction. Depends on what status it was in. For example, if it was in Shipped to Store, the user should, from a business perspective, go to the transfer and remove the item/UIN from the transfer.

Example 5 – Update UIN Status Web Service Processing ACTION = RETURN or VOID-SALE

1. UIN is found and is in a state other than Sold.

2. Status cannot be updated since it is not in sold status and exception is created and appears on Resolution List screen.

3. Access exception record from Resolution List screen and update the status.

Extended Attributes (including GS1)

The section describes the Extended Attributes.

Functional Overview

Extended Attributes are available on both the PC and the HH. If extended attributes are enabled, these attributes can hold additional data about an item on a particular transaction. Some of the attributes available are Batch/lot numbers, expiration/use by dates, best before/sell by dates and country of origin. The GS1 DataBar standards include many other attributes. All of the GS1 DataBar attributes are available for use by the customer if so desired.

The extended attributes are assigned by Department/Class/Sub-Class in order to configure which attributes are applicable for an item belonging to the appropriate merchandise hierarchy. Once configured, the user is able to add these attributes by scanning a GS1 DataBar on the HH. If the GS1 DataBar is not scan able or not available, the data may be entered manually on the HH or the PC.

In addition to manually entering the information on the PC, the information may also be removed and re-entered. Additionally, the feature will have the capability to define information mutually agreed between trading partners using AI 90 and other company internal information using AI’s 91 to 99. This will provide additional flexibility to track custom pieces of information.

In SIM, Extended Attributes maybe be captured in the following functional areas:

§ Creating/Editing a Container

§ Receiving a Container

§ Creating an Inventory Adjustment

§ Performing a Stock Count

§ Receiving a Customer Order Delivery

Figure: Extended Attribute Setup PC Screen Flow – PC

Attributes-Configuration

The list of extended attributes is pre-populated based on the industry standards for the GS1 DataBar. The Name and Description will be defaulted based on the standards but can be changed to a more meaningful name for the client. Since the client will likely only use a subset of the available GS1 codes they will scan on the product, the client may repurpose some of the codes for capturing data manually.

With the appropriate security permissions, the user is able to assign the extended attributes to capture for a particular item hierarchy. This allows the user entering the extended attribute data on the transaction to capture only the necessary information and provides a more efficient and more accurate way to manage the data entry. This is especially helpful when entering the data from the handheld.

The user will also have the ability to assign the order in which the fields will display for data entry purposes.

A maximum of 10 extended attributes can be assigned to a department/class/sub-class item hierarchy.

Attributes-Processing

The attributes can either be added by scanning a GS1 DataBar by using a handheld or the Advanced Item Entry Popup or manually adding the information from this screen. The attributes captured for the item can also be removed for either manual capture or from scanning.

The pre-configured fields displayed on this screen will be based on the item displayed on the top of this screen. The system will display the extended attributes assigned to this item hierarchy.

There are no validations on the data entered with the exception of dates entered in date format and fields defined as a number must contain numbers. These field level definitions are based on the GS1 Industry Standards. For example, the GS1 Standards define the country of origin to contain a 3 digit number (ISO) industry standard country code. However, the system will not validate the 3 digit number is one that is defined by ISO, but only that the user has entered a number in that field. The client will need to understand which 3 digit codes to use when manually entering the data in the form.

The system will only store the unique combination of all fields on this screen. If the user scans more than one item with the same attribute values, the quantity will be increased by 1. For example: the user scans each unit for the same item. There are three units, but two of them have the same batch, country of origin, and sell by dates, etc. There will be two records added, one record will have a scan quantity of 1 and the other will have a scan quantity of 2.

System and Store Administration

This chapter includes information on system and store administration.

Overview

Under the administration section, the user can find all system setup tasks and often corporate executed tasks:

§ Product Group and Product Group Scheduler

This feature allows customers to set up recurring events with sets of items.

§ UIN Resolution

The UIN Resolution screen allows the user to view and resolve UIN status discrepancies. The user can also view an audit trail of the discrepant item’s UIN history.

Note: Resolving discrepancies from the UIN Resolution list screen does not resolve the inventory discrepancy. See "Resolving UIN Discrepancies" for more detail.

§ Security

The user can create and modify roles. When creating a new role, it is possible to add a variety of permissions for the handheld or PC. In addition to general restrictions for functional areas, the user is also able to secure the different types of product groups that exist and the reason codes a user has access to for creating inventory adjustments or return shipments.

§ Technical Maintenance

Several technical functions can be controlled under this header:

– UI Configuration

This feature allows the user to configure font type and size, color scheme and icons by theme. In addition translated values can be modified through this dialogue as well.

– MPS Worker Types

MPS Worker Types allow the user to identify how often the system will check the SIM integration layer for new messages generated by external systems.

– MPS Staged Messages

The MPS staged messages UI allows a user to validate the content of message and if needed manually restarts the message for polling purposes.

§ Print Setup

– Print Formats

Tickets and labels can be setup here and a default printer can be assigned to them. In addition, it is possible to assign a default printer to print reports.

Note: Tickets and labels need to be created in the printing tool used to print them. These screens are just for printer and type setup.

– Hierarchy Format

Formats can be assigned to specific price events (regular price changes, clearance and promotions) by merchandise hierarchy. The format assignments can be managed for multiple stores at one time.

– UDA Print Setup

SIM can automatically generate tickets and labels for items when user-defined attribute (UDA) values change. The UDA Print Setup function allows you to define whether new tickets or labels, or both, should be printed automatically when particular UDA values change.

– Printers

Includes a list of printers, such as the routing code or network address for a printer, description by which you can identify the printer within your organization, and the type of printer.

§ Setup

– SIM Stores

Management of SIM managed stores, setup of buddy stores, and auto receiving for store transfers.

– SIM Managed Stores

User can setup those stores that will use SIM. This prevents the store from publishing RIB Messages to the external system when auto-receiving.

– Buddy Stores

SIM allows for the concept of Buddy Stores. Buddy Stores can be set up to indicate groups of stores that can transfer merchandise from one store to another. The concept does enforce transfer zones if used in the Oracle Retail Merchandising System.

– Auto Receive Stores

SIM allows users to set up Stores at which transfers are automatically received when shipped.

– Administration Parameters

SIM has many application parameters that allow clients to customize the product according to their business. The application parameters are split into system and store options. System option parameters allow a user to change the parameter for the entire system and all stores. Store option parameters are only specific to the store the current user is logged in to. Additionally, when a new store is added to the enterprise, the store defaults admin may be used to quickly configure the store.

– UIN Attributes

Unique Identification Numbers also referred to as UIN’s, are used to identify pre-defined or system generated serial numbers. There are various rules based on the type of UIN. If the UIN is system generated, the label used to print the auto generated SN, may be identified by merchandise hierarchy.

– Inventory Adjustment Reason

Inventory adjustment reason codes help control the loss or unexpected gain of items for the general ledger and stock ledger. SIM has the ability for the user to set these up to match the external merchandising system. It is also possible to hide or modify the disposition of the existing reason codes.

– Shipment Reason Codes

Users can add, change, and delete reason codes used for return shipments. In addition to showing the reasons for return shipments, reason codes also specify how returns affect stock on hand, unavailable inventory, or customer order reserve inventory. Users can also use sub-buckets, which allows users to segregate the unavailable inventory bucket into various slots for specific reasons. The shipment reason codes are used in the RTV Shipment and Transfer Shipment dialogues.

– Tolerances

This section allows for tolerances for Adhoc Stock Counts as well as Customer Order Picking.

– Extended Attributes

Retailers may have a need to capture additional data about an item such as Batch/lot numbers, expiration/use by dates, best before/sell by dates and country of origin. The list of extended attributes is pre-populated based on the industry standards for the GS1 DataBar. These attributes can hold additional data about an item on a particular transaction. The extended attributes are assigned by Department/Class/Sub-Class in order to configure which attributes are applicable for an item belonging to the appropriate merchandise hierarchy.

Figure: Store Administration PC Screen Flow

Product Groups/Scheduler

Within the System Administration screens is the ability for a store user, with the proper security, to create any number of groups of items to be used within the SIM application. These groups can be comprised of entire areas of the merchandise hierarchy (for example, an entire subclass) or can be simply a group of individual and unrelated items. Depending on the product group, the user can setup additional details such as:

§ Tolerances

§ Counting Method (Guided/Unguided/Third Party)

§ Hierarchy Breakdown

§ Recounts

§ Item Status

§ Stock on Hand

§ Expiration

§ Delivery Dates

§ Auto Authorize

§ Problem Line Parameters

Product groups can be created for:

§ Unit Stock Counts

§ Unit and Amount Stock Counts

§ Problem Line Stock Counts

§ Shelf Replenishment

§ Wastage

§ Item Requests

§ Auto Ticket Print

Once the groups are created, the user has the ability to schedule how often each group is to be counted or ordered. Using a calendar wizard, the user selects the count group and whether it is to be counted daily, weekly, monthly, or yearly. One or more stores can be assigned to the schedule, depending on stores the user has access to. SIM maintains these schedules and automatically prompts users to complete the counts at their scheduled times. Product group schedules can be used for:

§ Unit Stock Counts

§ Unit and Amount Stock Counts

§ Problem Line Stock Counts

§ Wastage

§ Item Requests

§ Auto Ticket Print

§ Shelf Replenishment Lists

Store Administration

The store administration functionality allows you to set values for options that control a variety of system behaviors. The values of these system options apply only to your location.

Set Store Options

Navigate: Main Menu > Admin > Setup > Store Admin

The Store Admin window opens.

Figure: The Store Admin Window

StoreAdmin

1. Select the option that you want to modify.

2. Double-click the Value field and set the option value in either of these ways:

§ Select a value from the list.

§ Enter an appropriate value in the field.

3. Click Save. You return to the Setup menu. Click Save again to return to the Admin menu.

Store Administration Options Table

The following table lists the store administration options in alphabetical order and describes each option.

Table: Store Administration Options

Topic	Store Administration Option	Valid Values	Default Value	Description
Admin	Auto Apply Advanced Item Entry	Yes, No	No	If Yes, auto application to the transaction occurs. Items are added and UINs are captured, if necessary. If No, when the item is entered, the item will not be added to the transaction.
Admin	Enable Item Disposition in Transaction Updates	Yes, No	Yes	If Yes, the system reads the reason code in the web service message and performs the inventory adjustment. If the reason code is not present, the system processes the return/void and increments the SOH. If No, the system does not look for the reason code in the web service message.
Admin	Manifest Weight UOM	List of weight UOMs from the weight table in DB		The UOM selected for this configuration will be used as the Weight UOM for the weight on the BOL in store to store transfers, customer order deliveries and returns.
Admin	SSCC Shipping Label ID Generation	Automatic / Manual	Automatic	When Automatic is selected the system will generate an identifier for printing on the shipping label. This will be done at the time of clicking Create Container. When Manual is selected the user will need to enter an identifier for printing on the shipping label. Used for RTV Shipping and Transfer Shipping.
Admin	UIN Processing Enabled	Yes, No	No	Dictates whether any of the UIN functionality is available within SIM for each store. If the parameter is No, then none of the UIN buttons or fields will be present in the application.
Admin	Use Advanced Item Entry	Yes, No	Yes	If Yes, the Advanced Item Entry popup window will automatically be open when entering the functional areas that use the popup. If No, the Advanced Item Entry popup window will not automatically be open. The user can still use the 'Scanner' button to open it.
Admin	Use Extended Attribute Entry	Yes, No	No	If Yes, the user may edit or capture the extended attributes manually. If No, the user is not able to edit or manually capture extended attributes on either the PC, tablet, or HH.
Customer Order	Auto Pick Mixed Containers	Yes, No	No	If Yes, SIM will auto pick if the containers mixed with customer orders and non-customer orders. If No, SIM will not auto pick if the containers mixed with customer orders and without customer orders.
Customer Order	Auto Pick On Receive - Direct Delivery	Yes, No	No	If Yes, SIM will automatically fill in the pick quantities on the customer order when receiving the DSD. If No, SIM will not do anything related to picking at the time of receiving.
Customer Order	Auto Pick On Receive – Transfer Delivery	Yes, No	No	If Yes, SIM 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. If No, SIM will not pick when receiving goods in transfer receiving.
Customer Order	Default Customer Order Picking Method	Bin, SIM Customer Order	SIM Customer Order	Determines the default picking method displayed when Creating a Customer Order Pick transaction.
Customer Order	Default Number of Bins	1-999	1	Determines the number of bins to default into the Bin Qty field if the user selects Bin as the pick type when creating the pick.
Customer Order	Dispatch Validate	Ship Submit, Ship Direct	Ship Direct	If Ship Direct, SIM will control all processes. The user will be able to go from create/edit directly to dispatch. If 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.
Customer Order	Generate Bins	Manual, System	System	If System, SIM will automatically generate the bin/order numbers when the pick is created. If Manual, SIM will need to prompt the user to capture the bin/order numbers that are being used for the labels on the bins
Customer Order	Handheld Picking Mode	Scan Every Item, Enter Pick Quantity	Enter Pick Quantity	If Enter Pick Qty, the user will need to manually enter the pick quantity and then scan the item to validate it is the correct item. If Scan Every Item, on the HH the user will be required to scan each instance of the item on the pick and then scan the bin, if required, instead of manually entering a pick quantity for all items picked. This method ensures every item is validated as the correct item to pick.
Customer Order	Item Substitution - Store Discretion	Yes, No	No	If Yes, the user will be allowed to choose any item to substitute. An item lookup feature on the PC will allow the user to search for an item to select. If No, the user will be restricted to scanning/entering an item that exists on the list of approved substitute items defined by RMS.
Customer Order	Override Bin Quantity	Yes, No	No	Determines whether or not the user will be allowed to override the number of bins displayed in the 'Bin Qty' field as defined in the 'Default Number of Bins' parameter.
Customer Order	Picking Required for Customer Orders	Yes, No	Yes	If Yes, it defines if the customer order must be picked first in order for it to be delivered. If No, picking is not required in order to create a delivery.
Customer Order	Pre-shipment Notification	Yes, No	No	If Yes, SIM will publish a pre-shipment message. If No, SIM will not publish a pre-shipment message.
Customer Order	Reserve Customer Order Inventory Upon Receiving	Yes, No	No	If Yes, then the customer order reserved will be incremented upon receiving a delivery (warehouse delivery, store transfer, or DSD) for a customer order. This is assuming the customer order already exists in the system. If No, the customer order reserved is incremented upon the customer order entering the system.
DSD Receiving	Allow Multiple Deliveries against PO with No ASN	Yes,No	Yes	If Yes, SIM allows the user to create more than one delivery for the same PO that does not have an associated ASN. If No, the user can only create a single delivery against a PO, when the POS does not have an associated ASN. The POS will be closed when the delivery is confirmed.
DSD Receiving	Auto close days after expected date	0-999	5	Number of days to close the ASN after the expected date.
DSD Receiving	Direct Delivery Auto Remove Over Received Quantity	Yes, No	No	Yes: The user is allowed to add any quantity for the DSD ASN, but any quantity above the expected quantity is removed from the transaction. After the user confirms the transaction, the user is prompted that any over-received quantities are removed. No: Follows standard DSD receiving process.
DSD Receiving	Direct Delivery Default to Shopfloor Receiving	Yes, No	No	If Yes, SIM defaults the Receive to Shop floor checkbox to marked on the Direct Store Delivery Detail screen. If No, SIM defaults the checkbox to blank.
DSD Receiving	Direct Delivery Invoice Entry	Unique	Enabled, Disabled, Unique	If Enabled, entry of invoice numbers is allowed. If Disabled, invoice numbers will not be allowed to be entered and will not be displayed on the screen. If Unique, entry of invoices is allowed, but not duplicates. Duplicates are checked by supplier.
DSD Receiving	Direct Delivery Receive Item Capacity	Yes, No	No	If Yes, SIM considers shelf capacity when receving the delivery to the shopfloor. Excess capacity will be received in the backroom. If No, SIM does not consider shelf capacity.
DSD Receiving	DSD Receiving Auto Remove Damaged Quantity	Yes, No	No	Yes: When confirming the transaction, all damaged items are removed and put on the audit trail. No: Any damaged quantities recorded for the delivery stay on the transaction.
Item Basket	Item Basket Printing	Manual, Automatic	Manual	If the value of this option is Automatic, Item Basket ticket is printed when the transaction is complete. If the value is Manual, SIM does not automatically print the ticket.
Item Request	Display Item Request Delivery Timeslot	Yes, No	No	If the value of this option is Yes, SIM displays the timeslot information in Item Request and Item Lookup.
RTV	Auto Accept External Generated RTV Request	Yes, No	Yes	If Yes, the RTV request is immediately accepted for the requested quantity. If No, the user must manually accept the RTV request. Note: When auto-approve is yes, the return allowed and DSD return allowed restrictions are ignored and the request is accepted.
RTV	Not After Date Default days	0-999	30	This parameter determines how long an RTV document is available for shipment. Documents in any open status are marked cancelled, once the date is reached.
RTV Shipment	Dispatch Validate	Ship Submit, Ship Direct	Ship Direct	If Ship Direct, SIM will control all processes. The user will be able to go from create/edit directly to dispatch. If 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.
RTV Shipment	Pre-shipment Notification	Yes, No	No	If Yes, SIM will publish a pre-shipment message. If No, SIM will not publish a pre-shipment message.
RTV Shipment	RTV Shipment Carrier Default	Third Party, Sender, Receiver	Third Party	If Sender, sender will be selected for Carrier Type on BOL. If Receiver, receiver will be selected for the Carrier type on BOL. If Third Party, third party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to Other.
Sequencing	Assign Shelf Edge Labels	Yes, No	No	If the value of this option is Yes, users are required to assign shelf edge labels for sequencing.
Sequencing	Display Sequence Fields	Yes, No	No	Indicates whether or not sequencing fields are displayed in: Item Lookup (PC, tablet, and HH) Operational Views (tablet) Customer Order Picking (PC & HH) Shelf Replenishment (PC & HH) Transfer Picking (HH)
Shelf Replenishment	Replenishment – At Case Level	Yes, No	No	If Yes, the UOM, for replenishing the shelves, will default to Cases on both the PC and HH. If No, the UOM will default to eaches. Note: the user may toggle between cases and standard UOM regardless of the parameter setting.
Shelf Replenishment	Replenishment – Delivery Bay Inventory	Yes, No	Yes	This option allows you to turn on or off the delivery bay functionality.
Shelf Replenishment	Replenishment – End of Day max. fill %	Numeric 0 to 100	100	This configurable percentage allows each store to set its own fill percentage for creating end-of-day shelf replenishment lists.
Shelf Replenishment	Replenishment – Handheld Picking Mode	Enter Pick Quantity, Scan Every Item	Enter Pick Quantity	If Enter Pick Quantity, the quantity is entered and then the item is scanned during the pick process. If Scan Every Item, the item is scanned every time and the quantity will be determined by the number of times scanned.
Shelf Replenishment	Replenishment – Item Out of Stock (Standard UOM)	Numeric	2 (standard unit of measure)	Use this option to set a variance for out-of-stock items on the shelf. The out-of-stock field is used when receiving warehouse deliveries. If the quantity on the shelf is less than the amount in this field, the item appears as an out-of-stock item.
Shelf Replenishment	Replenishment – Item Out of Stock %	Numeric	10	Stores can set a variance for out-of-stock items on the shelf. The out-of-stock field is used when receiving warehouse deliveries. If the percentage on the shelf (shopfloor divided by capacity) is less than the percentage specified by this option, the item appears as an out-of-stock item.
Shelf Replenishment	Replenishment – Item Substitution Store Discretion	Yes, No	No	If Yes, any item may be selected to substitute. If No, only an approved substitute item may be selected.
Shelf Replenishment	Replenishment – Shopfloor to Capacity	Yes, No	No	If Yes, the shopfloor is set to equal the capacity at the beginning of each day. If No, the shopfloor is not reset.
Shelf Replenishment	Replenishment – Within Day Max. fill %	Numeric 0 to 100	75	This configurable percentage allows each store to set its own fill percentage for creating within-day shelf replenishment lists.
Shelf Replenishment	Shelf Adjustment List Printing	Manual, Automatic	Manual	If Automatic, the report and tickets will print automatically when performing a shelf adjustment. If Manual, the user will need to intiate the printing of the shelf adjustment.
Stock Counts	Display Late Inventory Adjustment Message	Yes, No	Yes	If the value is Yes, when the user is confirming a Stock Count in the Authorization phase and In Progress Inventory Adjustments exist with items on the Stock count, a message is displayed alerting the user. Additionally, if a user is confirming or approving an inventory adjustment with items on an open stock count, a message is also displayed to the user. If the value is No, the user is not prompted and the system will ignore any In Progress inventory adjustments.
Stock Counts	Stock Count Default Timeframe	Before Store Open, After Store Close	Before Store Open	The setting of this option determines when the stock count is performed in relation to store opening hours for daily sales processing. It defines the default value for the Stock Count screen. If RMS is implemented with SIM, this setting must be set to After Store Close because of the way transactions are processed during a Unit and Amount Stock Count.
Ticketing	Auto Generate Item Tickets for Clearance Price Changes	Yes, No	No	If Yes, a new item ticket is sent to the ticketing dialogue when a clearance price event comes from the pricing system. If No, a new item ticket is not generated.
Ticketing	Auto Generate Item Tickets for Promotion Price Changes	Yes, No	No	If Yes, a new item ticket is sent to the ticketing dialogue when a promotion price event comes from the pricing system. If No, a new item ticket is not generated.
Ticketing	Auto Generate Item Tickets for Regular Price Changes	Yes, No	No	If Yes, a new item ticket is sent to the ticketing dialogue when a regular price event comes from the pricing system. If No, a new item ticket is not generated.
Ticketing	Auto Generate Shelf Edge Labels for Clearance Price Changes	Yes, No	No	If Yes, a new shelf label is sent to the ticketing dialogue when a clearance price event comes from the pricing system. If No, a new shelf label is not generated.
Ticketing	Auto Generate Shelf Edge Labels for Promotion Price Changes	Yes, No	No	If Yes, a new shelf label is sent to the ticketing dialogue when a clearance price event comes from the pricing system. If No, a new shelf label is not generated.
Ticketing	Auto Generate Shelf Edge Labels for Regular Price Changes	Yes, No	No	If Yes, a new shelf label is sent to the ticketing dialogue when a clearance price event comes from the pricing system. If No, a new shelf label is not generated.
Ticketing	Maximum Ticket Quantity to Print	1-10000	500	This determines the maximum ticket size to print in one command and is used in auto ticket printing batch and Ticketing dialogue. If the ticket quantity is exceeded on the UI, a warning message is displayed. If the ticket quantity is exceeded when printing, the tickets are sent in multiples of the maximum defined.
Ticketing	Send Item Tickets to Ticketing for Description Change	Yes, No	No	If the value of this option is Yes, a ticket is generated to be printed when the description of an item changes.
Ticketing	Send Item Tickets to Ticketing for QR Code Change	Yes, No	No	Indicates SIM generates a new ticket if the QR code changes based on the optional time/date. If no time/date is defined, it is generated immediately; if a time/date exists, it will be generated by a batch program.
Ticketing	Send Shelf Edge Labels to Ticketing for Description Change	Yes, No	No	If the value of this option is Yes, a label is generated to be printed when the description of an item changes.
Ticketing	Send Shelf Edge Labels to Ticketing for QR Code Change	Yes, No	No	Indicates SIM generates a new label if the QR code changes based on the optional time/date. If no time/date is defined, it is generated immediately; if a time/date exists, it will be generated by a batch program.
Transfer Receiving	Auto Close Receipt	1-99	1	Defines how long to keep a receipt open, once it has been created. 0 means immediately closes receipt 1 means today (EOD) 2 means EOD tomorrow x means EOD x days starting from today
Transfer Receiving	External Finisher Auto Receive	Not allowed, External Message, Date Driven	Not allowed	This parameter drives the following functionality: Not allowed follows standard receiving process. External message receives the full finisher delivery the moment an ASN transaction arrives which indicates that the delivery needs to be auto-received. Date Driven looks at a secondary store option (External Finisher Auto Receive number of Days) to determine how many days the transaction stays open before the transaction is fully received. If the parameter is set to 0, the transaction auto-receives on the ETA date.
Transfer Receiving	External Finisher Auto Receive Number of Days	0-99	0	SIM auto-receives any external finisher delivery ASN that has not been closed x days after the ETA date or the create date, depending on whether the ETA date is set or whether the auto-receive External Finisher delivery parameter is set. 0 means immediate receiving 1 means today (EOD) 2 means EOD tomorrow x means EOD x days starting from today
Transfer Receiving	Store Auto Receive	Not Allowed, External Message, Date Driven	Not Allowed	This parameter drives the following functionality: Not allowed follows standard Transfer receive process. External message receives the full store delivery the moment a transaction arrives which indicates that the delivery needs to be auto-received. This feature works in correlation with the store auto-receive screen information configured under Admin > SIM Store > Auto-Receive Stores. Date Driven uses a secondary store option (Store Auto Receive Number of Days) to determine how many days the transaction stays open before the transaction is fully received.
Transfer Receiving	Store Auto Receive Number of Days	0-99	0	A batch program auto-receives any store transfers that have not been closed x days after they have been shipped, if the store auto-receive parameters are set. 0 means immediate receiving 1 means today (EOD) 2 means EOD tomorrow x means EOD x days starting from today
Transfer Receiving	Store Transfer Default to ShopFloor Receive	Yes, No	No	If Yes, SIM defaults the Receive to Shopfloor checkbox to marked on the Transfer Receiving Container Detail screen. If No, SIM defaults the checkbox to blank. Note: Damaged inventory does not move to shopfloor.
Transfer Receiving	Store Transfer Receive Item Capacity	Yes, No	No	If Yes, SIM considers shelf capacity when receiving the delivery to the shopfloor. Excess capacity will be received in the backroom. If No, SIM does not consider shelf capacity.
Transfer Receiving	Warehouse Auto Receive	Not Allowed, External Message, Date Driven	Not Allowed	This parameter drives the following functionality: § Not allowed follows the standard Warehouse receiving process. § External message receives the full warehouse delivery the moment an ASN transaction arrives. The external message indicates that the delivery needs to be auto-received. § Date Driven looks at a secondary store option (Warehouse Auto Receive number of Days) to determine how many days the transaction stays open before the transaction is fully received. If the parameter is set to 0, the transaction will auto-receive on the ETA date.
Transfer Receiving	Warehouse Auto Receive Number of Days	0-99	0	A batch program auto-receives any warehouse deliveries that have not been closed x days after the ETA date or the create date, depending on whether the ETA date is set and whether the auto-receive warehouse delivery parameter is set. 0 means immediate receiving 1 means today (EOD) 2 means EOD tomorrow x means EOD x days starting from today
Transfer Receiving	Warehouse Default to Shopfloor Receive	Yes, No	No	If Yes, SIM defaults the Receive to Shopfloor checkbox to marked on the Transfer Receiving Container Detail screen. If No, SIM defaults the checkbox to blank. Note: Damaged inventory does not move to shopfloor.
Transfer Receiving	Warehouse Receive Item Capacity	Yes, No	No	If Yes, SIM considers shelf capacity when receiving the delivery to the shopfloor. Excess capacity will be received in the backroom. If No, SIM does not consider shelf capacity.
Transfers	Auto Accept External Generated Request	Yes / No	No	If yes, the externally generated request is automatically accepted. If no, the user must manually accept the request.
Transfers	Auto Accept Store Transfer Request	Yes / No	No	If yes, the store transfer request is automatically accepted. If no, the user must manually accept the request.
Transfers	Not After Date Default Days	0-999	30	A batch program sets the transfer not after date when the date is null. This date is set x days after the create date. 0 means today 1 means tomorrow x means EOD x days starting from today
Transfers	Transfer Handheld Picking Mode	Enter Pick Quantity / Scan Every Item	Enter Pick Quantity	If Enter Pick Quantity, the user scans the item once with the quantity to pick. If Scan Every Item, the user scans each item and the system keeps track of the quantity for them.
Transfer Shipment	Pre-shipment Notification	Yes, No	No	If Yes, SIM will publish a pre-shipment message. If No, SIM will not publish a pre-shipment message.
Transfer Shipment	Ship To Finisher Carrier Default	Third Party, Sender, Receiver	Third Party	If Sender, sender will be selected for Carrier Type on BOL. If Receiver, receiver will be selected for the Carrier type on BOL. If Third Party, Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to Other.
Transfer Shipment	Ship To Store Carrier Default	Third Party, Sender, Receiver	Third Party	If Sender, sender will be selected for Carrier Type on BOL. If Receiver, receiver will be selected for the Carrier type on BOL. If Third Party, Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to Other.
Transfer Shipment	Ship To Warehouse Carrier Default	Third Party, Sender, Receiver	Third Party	If Sender, sender will be selected for Carrier Type on BOL. If Receiver, receiver will be selected for the Carrier type on BOL. If Third Party, Third Party will be selected for the Carrier type on the BOL. The type (drop down) will be defaulted to Other.
Transfer Shipment	Transfer Shipment Dispatch Validate	Ship Submit, Ship Direct	Ship Direct	If Ship Direct, SIM will control all processes. The user will be able to go from create/edit directly to dispatch. If 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.
Web Service Enablement	Manifest Customer Order Deliveries	Yes, No	No	If Yes, the Manifesting system will be called. If No, the Manifesting system will not be called.
Web Service Enablement	Manifest Returns - Finisher	Yes, No	No	If Yes, the Manifesting system will be called for Return to Finisher. If No, the Manifesting system will not be called.
Web Service Enablement	Manifest Returns - Supplier	Yes, No	No	If Yes, the Manifesting system will be called for Return to Supplier. If No, the Manifesting system will not be called.
Web Service Enablement	Manifest Returns - Warehouse	Yes, No	No	If Yes, the Manifesting system will be called for Return to Warehouse. If No, the Manifesting system will not be called.
Web Service Enablement	Manifest Store to Store Transfer	Yes, No	No	If Yes, the Manifesting system will be called for Store to Store Transfers. If No, the Manifesting system will not be called.
Web Service Enablement	OMS Customer Order Delivery Validation	Yes, No	No	If Yes, the OMS system will be called for validating delivery status and quantities before completing the dispatch. If No, the OMS system will not be called.

System Administration

The system administration functionality allows you to set values for options that control a variety of system behaviors. The values of these system options are applied to all locations.

The system options are in these general categories:

§ Receiving and shipping options

§ Audit options

§ Transaction adjustment options

§ Days-to-hold options

§ System usability options

§ Customer order

§ E-mail options

§ Stock count options

§ Transfer options

§ Time Zone options

§ Miscellaneous options

Set System Options

Navigate: Main Menu > Admin > Setup > System Admin.

The System Admin window opens.

Figure: The System Admin Window

1. Select the option that you want to modify.

2. Double-click the Value field and set the option value in either of these ways:

§ Select a value from the list.

§ Enter an appropriate value in the field.

3. Click Save. You return to the Setup menu. Click Back to return to the Admin menu.

System Administration Options Tables

The following tables list the system administration options in each general category and describe each option.

Table: Topic: Admin Options

System Administration Option	Valid Values	Default Value	Description
Allow Non-Range Item	Yes, No	Yes	This option gives stores the ability to add non-ranged items to functional areas in the application.
Auto Default UIN Attributes	Yes/No	No	Dictates whether SIM auto-defaults in the UIN attributes. If the parameter is Yes, then when a new item is created using the RIB, SIM auto-defaults UIN attributes that were set up at the department class from the SIM UIN Attributes screen. If the parameter is No, then the UIN attributes are not defaulted in. Instead, the UIN attributes are defaulted from the external system. The parameter should be set to No if an external system controls the setup of item UIN attributes. In this case, SIM must not auto-default the UIN values as this action can override the intent of the external system.
Barcode Scan/Entry Log – Receiving	Yes, No	No	If Yes, all item scans or manual entries on the handheld are captured by user, location and date/time at the point of receiving the delivery. If No, item scans are not captured. Note: Comtainers are captured in the quick receiving dialogue, which item level is captured in the item receiving function of the Container Summary for DSD and Transfer Receiving.
Default for date field in external files	yyyyMMddHHmmss	Date (14)	Indicates date/time item was physically counted by the third party.
Default UOM	Cases, Standard UOM	Cases	This option allows the store to select the default unit of measure that the store will normally use. This system option is ignored in the stock counts functional area.
Delete completed staging price change worksheet records	True, False	True	This option is used by a DBA or other type of administrator role to control clearing of the temporary pricing staging tables. This is used when companies first go live and may have a large amount of price changes initially in production. Refer to the Oracle Retail Store Inventory Management Operations Guide for additional details on temporary tables.
DexNex Error Directory	Editable text field	NA	Dictates where the error directory is located for Direct Delivery DexNex files. For example: /u00/webadmin/product/10.1.3_9/OAS/user_projects/domains/java_domain/error n
DexNex Input Directory	Editable text field	NA	Dictates where the input directory is located for Direct Delivery DexNex files. For example: /u00/webadmin/product/10.1.3_9/OAS/user_projects/domains/java_domain/input See the Oracle Retail Store Inventory Management Operations Guide for details on DexNex batch file processing.
Disable Pack Size	Yes, No	No	This option allows the user to edit the pack size in the application.
EMail From Name	Editable text field	simAlert@my Company.com	When the system sends e-mail alerts, the specified e-mail address is displayed in the from name.
Enable Extended Attributes	Yes, No	No	If Yes, the system will capture the extended attributes when scaning a GS1 DataBar. If No, the Ext. Attribute button and menu option will not be available on the PC, Tablet, orHH.
Enable Multiple Set of Books	Enabled, Disabled, SIM Only	Disabled	If the option is Enabled, SIM is expected to be in sync with RMS for the purpose of MSOB. If Disabled, MSOB functionality is disabled. If SIM Only, SIM uses the organization unit to limit the suppliers available to the store.
Enable sub buckets	Yes, No	Yes	If Yes, Sub-buckets will be used throughout the application (PC, HH and Tablet). The Adjust Unavailable Qty bucket will be divided into sub-buckets and the sub-buckets will be updated appropriately when inventory updates are made. If No, Sub-buckets will not be used in the system, and they will not be displayed. The adjust unavailable qty will be used.
Online Help URL	Editable text field	NA	@online.help.url@

Table: Topic: Audit Options

System Administration Option	Valid Values	Default Value	Description
Price default extract size	0-9999	1000	This option is used by a DBA or other type of administrator role to control size of the temporary pricing staging tables. This is used when companies first go live and may have a large amount of price changes initially in production. Refer to the Oracle Retail Store Inventory Management Operations Guide for additional details on temporary tables.
Audit Direct Store Delivery	Yes, No	Yes	Direct store deliveries are tracked with process ID 8 (Direct_Delivery).
Audit Inventory Adjustment Create	Yes, No	Yes	The creation of inventory adjustments is tracked with process ID 12 (Inventory_Adjustment_Create).
Audit Inventory Adjustment Dispatch	Yes, No	Yes	The dispatch of an inventory adjustment is tracked with process ID 14 (Inventory_Adjustment_Complete).
Audit Inventory Adjustment Update	Yes, No	Yes	The updating of an inventory adjustment is tracked with process ID 13 (Inventory_Adjustment_Update).
Audit Item Requests	Yes, No	Yes	Completed item requests are tracked with process ID 201 (Store_Order_request).
Audit Price Adjustment	Yes, No	Yes	Price adjustments in the store are tracked by tracking printing of the tickets. Process ID 15 is used (Price_label_printed).
Audit Publish Message	Yes, No	Yes	The publishing of Retail Integration Bus (RIB) messages is tracked using process ID 16 (Publish_Message).
Audit Receive Message	Yes, No	Yes	The subscription to RIB messages is tracked using process ID 17 (Receive_Message).
Audit Return Stock Update	Yes, No	Yes	A return that updates inventory is tracked using process ID 10 (Return_Stock_Dispatch).
Audit RTV Update	Yes, No	No	Indicates if RTV information created and changed within SIM should be audited.
Audit Security	Yes, No	Yes	Indicates if security information that is created and changed within SIM should be audited. If Yes, create/edit roles and failed/successful login attempts are audited.
Audit Session Timeout	Yes, No	Yes	A session time-out is tracked with process ID 4 (Session_Timeout).
Audit Stock Count Completed	Yes, No	Yes	Completed stock counts are tracked using Process ID 18 (Stock_Count_Completed).
Audit Stock Count Processed	Yes, No	Yes	The completion of a recount is tracked using process ID 101 (Stock_Recount_Completed).
Audit Transfer Dispatch	Yes, No	Yes	When a transfer is dispatched, it is logged using process ID 5 (Transfer_Dispatch).
Audit Transfer Receiving	Yes, No	Yes	When a transfer is received, it is logged using process ID 6 (Transfer_receive).
Audit Transfer Update	Yes, No	Yes	When a transfer is updated, it is logged using process ID 7 (Transfer_update).
Record an audit record for adjust delivery request	Yes, No	Yes	If this option is set to Yes, the system writes an audit record to the database when an adjust delivery request is made.

Table: Topic: Customer Order Options

System Administration Option	Valid Values	Default Value	Description
Customer Order Receipt Email Alert	Yes, No	No	If Yes, generate notification for customer order receipts.
Minutes to Hold New Customer Order Before Sending Email Alert	0-99	5	Dictates the time interval in minutes to send a follow-up message to a store associated after a customer order has arrived, but no-one has accessed the customer order.
Minutes to Hold Open Customer Order Pick Before Sending Email Alert	0-99	15	Dictate the time interval in minutes to send a follow-up message to a store associated after a pick list has been created but no-one has started the pick list.
New Customer Order Email Alert	Yes, No	No	If Yes, generates notification for new cross channel customer orders.

Table: Topic: DSD Receiving Options

System Administration Option	Valid Values	Default Value	Description
Always Send DSD Receipt Cost	Yes,No	No	If Yes, SIM will publish the unit cost or the overridden cost. If No, SIM will publish only the overridden cost.
Disable Discrepancy Checks in DSD	Yes,No	No	If Yes, the user will not have to do the discrepancy review while receiving. If No, the user will have to review the discrepancy checks while receiving.
Display Unit Cost for Direct Deliveries	Yes, No	Yes	If yes, SIM displays the original cost and allows to enter the new cost for the on-the-fly and Dex/Nex deliveries. For the delivery with PO and ASN it displays the unit cost. If No, SIM does not display the unit cost and does not allow to edit or enter a new cost.
DSD Receiving Preferred Currency	Store Currency, Supplier Currency	Store Currency	This option defaults the store or supplier currency to newly created POs depending on preference.
DSD Receiving Search Default	ASN, Container, Item, Supplier and PO	Container	This is to determine the default method to identify the delivery on the HH.
Enable DSD Pack Receiving	Yes, No	Yes	This option allows packs to be received in direct store deliveries.
Ignore the Supplier DSD indicator to create a PO on the fly	Yes,No	Yes	If Yes, the system ignores the supplier indicator and will always allow stores to create a PO. If No, the system will allow only if the supplier level flag allows to create.
Number of days received direct deliveries can be adjusted	Numeric	0	This option specifies the number of days received direct deliveries can be reopened and adjusted. If a direct delivery falls within the number of days, an Adjust button is displayed on the received container. The user can edit values and confirm the container.
Over Received Quantity Email Alert	Yes,No	Yes	If Yes, SIM generates notification for the over received quantity. If No, No email alert is generated.

Table: Topic: Inventory Adjustment Options

System Administration Option

Valid Values

Default Value

Description

Display Item Image for Inventory Adjustments - Mobile

Yes, No

If Yes, this parameter indicates if the item image will be displayed in Inventory Adjustments. It is in the list and the details of Inventory Adjustment Detail.

If No, the Image will not be displayed in inventory adjustments.

Table: Topic: Item Lookup Options

System Administration Option

Valid Values

Default Value

Description

Display Item Image for Item Lookup – Mobile

Yes, No

Yes

If Yes, this parameter indicates if the item image will be displayed in Item Lookup. It is in the list and the details of Item Detail.

If No, the Image will not be displayed in item lookup.

Table: Topic: Purge Options

System Administration Option	Valid Values	Default Value	Description
Days to Hold Audit Records	Numeric	30	Records are deleted in which the create date is less than or equal to the current date minus the number of days to hold.
Days to hold cancelled templates	Numeric	30	Indicates the number of days that Canceled Templates will be held in the system before being purged.
Days to Hold Completed Customer Orders	Numeric	4	Indicates the number of days that Canceled and Fulfilled Customer Orders will be held in the system before being purged.
Days to Hold Completed Inventory Adjustments	Numeric	30	Records in Complete status are deleted, where the inventory complete date is less than or equal to the current date minus the number of days to hold.
Days to Hold Completed Purchase Orders	Numeric	30	All records in Closed status are purged after this number of days, 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 number of days to hold.
Days to Hold Completed Staging Records	Numeric	5	All successfully processed or deleted records will be purged where the update date is less than or equal to the current date minus the days to hold.
Days to Hold Completed Stock Counts	Numeric	30	Purge any records this number of 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, SIM subtracts the number of days to hold completed stock counts from the date and deletes when this date is reached. A record is purged if the stock count has a status of Complete, except in the case of Unit and Amount stock counts. Unit and Amount stock counts are deleted only when the status is Authorize Completed.
Days to Hold Completed UINs	Numeric	120	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
Days to Hold Customer Orders	Numeric	180	Indicates the number of days to hold a customer order in the system.
Days to Hold Deleted Users	Numeric	30	This will determine the number of days users with a Deleted status will be held in the system. When the status of the user is updated to Deleted, the system should capture the date in GMT and use that as a basis for determining when the user should be purged from the system. All role, store, password history, and so forth should be purged as well.
Days to hold expired item price	Numeric	30	Indicates the number of days to hold an expired item price in the system.
Days to Hold Expired User Roles	Numeric	30	Store managers have the ability to assign temporary roles to users in the store. For roles that require an expiration date, after the number of days as defined by this new parameter, the temporary roles should be purged from the user.
Days to Hold In Progress Ad Hoc Stock Counts	Numeric	1	Any ad hoc count with a creation date/time stamp older than this number of days is deleted.
Days to Hold Item Requests	Numeric	30	Records are deleted in which the process date is less than or equal to the current date minus the number of days to hold, for item requests in Completed or Cancelled status. Any requests in Pending status are not purged.
Days to Hold Item Tickets	Numeric	15	After this number of days, all records in Printed or Cancelled status are purged from the database, where the status date is less than or equal to the current date minus the number of days to hold.
Days to Hold Locking Records	Numeric	3	Locking records are sometimes left behind because of system crashes or incorrect logout functionality. After this number of days, these records are deleted.
Days to Hold Notifications	Numeric	14	This parameter will be used to purge notifications.
Days to Hold Price Change worksheet records	Numeric	30	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.
Days to Hold Price History	Numeric	90	The LE_HST_ITM_SLS_PRC table is purged so that it contains at least four historical prices for the item/store. This is consistent with the four historical prices the user is able to view in Price History within Item Lookup on the handheld. The Price History table could potentially contain more than four records, because a minimum of one regular price record is required to be held in the database. The purge program needs to restrict these records from being deleted. The Days to Hold Price History parameter allows the user to keep records beyond the four most recent historical prices for this number of days, if desired. Prices in the future are not deleted and are not included in the four historical prices that remain in the database.
Days to Hold Received Shipment Records	Numeric	30	All records in Complete and Canceled status are purged after this number of days, where the inventory completed date is less than the current date minus the number of days to hold.
Days to Hold Received Shipment Records	Numeric	10	All records in Received, or Canceled status are purged after this number of days, where completed date is less than or equal to the current business date minus the number of days to hold.
Days to Hold Related Items	Numeric	60	Indicates how long related items are kept in the system.
Days to Hold Resolved UIN Exceptions	0 - 999	120	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.
Days to Hold RTV	Numeric	30	This parameter will decide 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.
Days to Hold Sales Posting	0 - 999	120	Indicates how long Point-of-Service transactions uploaded from either Oracle Retail Point-of-Service (ORPOS) or Oracle Retail Sales Audit (ReSA) are kept in the system.
Days to Hold Shelf Adjustment Lists	Numeric	30	Indicates how long shelf adjustments should be kept in the system.
Days to Hold Shelf Replenishments	Numeric	30	Indicates how long shelf replenishments should be kept in the system.
Days to Hold Transaction History	Numeric	10	Indicates how long transaction history should be kept in the system.
Days to Hold Transfer Documents	Numeric	30	Indicates how long closed transfer documents should be kept in the system.
Days to Hold UIN Audit Information	0 - 999	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.

Table: Topic: Reporting Options

System Administration Option	Valid Values	Default Value	Description
Reporting Tool URL			http://<bip_host>:<bip_port>/<bip_deployment>. This URL is used as the reference to the BIP deployment for printing reports and viewing reports from the SIM PC client in a browser.

Table: Topic: RTV Options

System Administration Option	Valid Values	Default Value	Description
Add Item to Return Requests	Yes, No	Yes	This option gives the user the ability to add items to a return request (a return generated by an external system).
DSD delivery supplier for RTV	Yes, No	Yes	This new 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. Note: Regardless of the indicator, SIM should always be able to dispatch the RTV if it was created in an external system. If the DSD delivery supplier for RTV system option is set to Yes, then the system needs to check both the DSD indicator and the return-allowed indicator. 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.
RTV Unavailable qty discrepancy Email Alert	Yes , No	No	This parameter generates a notification when a RTV request is not auto-accepted if “Auto Approve RTV request” is set to Yes and the un-available quantity on the request is more than in SIM.
RTV Unavailable request Qty Email Alert	Yes , No	Yes	This new system parameter will generate notification when “Auto Approve RTV request” parameter is set to Yes and the request has an unavailable quantity greater than the SIM stock.

Table: Topic: Security Options

System Administration Option	Valid Values	Default Value	Description
Default Days for Temporary Role End Date	0-999	7	When setting up a temporary role, the system will default the end date based on the current date + x days set by this parameter.
Maximum Days for Temporary Users End Date	0 -999	5	For users that are defined as temporary, this will limit the time before Deactivating a temporary user. If the value is set to 0, then the temporary user account can have any end date.
User Security Mode	Internal Authentication/ Authorization	Internal Authentication/ Authorization	Internal Authentication/Authorization: SIM has full control of Authentication, user creation and store/role assignments. Internal Authentication/Authorization: Indicates that a hybrid approach will be used for authentication that allows users to be managed in an internal systems. SIM will try to authenticate the user internally with the password that was used during the last successful authentication.

Table: Topic: Stock Count Options

System Administration Option	Valid Values	Default Value	Description
Stock Count Display Default Timeframe	Yes, No	No	This option determines whether the Stock Count Default Time Frame value is a selectable option on the stock count screens on both the handheld and the PC.
Stock Count Lockout Days	Numeric	If RMS is not installed, 1 If RMS is installed, set to agree with the RMS value for lockout days	This option specifies the lead time required by RMS to create a unit and value stock count schedule.
Stock Count Null Count Quantity = 0	Yes, No	No	This option determines whether or not items with a null count quantity will be interpreted as a zero quantity for Unit, Problem Line and Ad Hoc stock counts.
Unguided Stock Count Allow Multiple Users	Yes, No	No	If unguided stock counts are used, this option allows more then one user to scan simultaneously against the same stock count.
Unguided Stock Counts -- Automatic Save	Yes, No	No	If the parameter is set to Yes, the physical timestamp is taken as soon as the item is scanned for the first time, and is saved to the database along with the count value once the user scans the next item on the count. If the parameter is set to No, SIM records the physical timestamp in memory once a user begins counting. The timestamp and count value are posted to the database when the user manually saves the count. With this option, it is assumed the user manually saves the count on a frequent basis, particularly when moving from one area in the store to another.
Unit & Amount Stock Count Sales Processing	Timestamp Processing, Daily Sales Processing	Timestamp Processing	This parameter will determine what kind of sales processing will be used for sales that are uploaded during a unit and amount stock count process. If Timestamp Processing, the user will not have to select a time period for the stock count. Sales data will have a timestamp on when the sale or return happened. This sales data timestamp will be compared against the timestamps taken during the stock count. If Daily Sales Processing, a timestamp will not be used and the user will need to select whether the stock count will occur before or after business hours so that SIM will know how to handle late sales. If RMS is implemented with SIM, the setting must be set to Daily Sales Processing to correspond with the way RMS processes the transactions occurring during a Unit and Amount Stock Count.
Unit Stock Count Sales Processing	Timestamp Processing, Daily Sales Processing	Timestamp Processing	This parameter will determine what kind of sales processing will be used for sales that are uploaded during a unit stock count process. If Timestamp Processing, the user will not have to select a time period for the stock count. Sales data will have a timestamp on when the sale or return happened. This sales data timestamp will be compared against the timestamps taken during the stock count. If Daily Sales Processing, a timestamp will not be used and the user will need to select whether the stock count will occur before or after business hours so that SIM will know how to handle late sales.
Updating Stock On Hand	Discrepant Items Only, All Items	Discrepant Items Only	This option determines whether the stock on hand will be updated for all items, both discrepant and non-discrepant items, or for discrepant items only when authorizing a Unit, Problem Line or Ad Hoc stock count.

Table: Topic: Store Orders Options

System Administration Option	Valid Values	Default Value	Description
Restrict Store Purchase Orders to Store-Orderable Items	Yes, No	Yes	This option prevents items that are not store-orderable from being on regular store purchase orders.

Table: Topic: Time Zone Options

System Administration Option	Valid Values	Default Value	Description
Daily GMT Batch Run	Yes, No	Yes	Indicates if the batch programs can be run multiple times a day.
Enable GMT for Customer Orders	Yes, No	Yes	Dictates whether the Customer Order data being loaded into the system is in GMT.
Enable GMT for Dex/Nex	Yes, No	No	Dictates whether or not the Dex/Nex data being loaded into the system is in GMT.
Enable GMT for Direct Deliveries	Yes, No	No	Indicates whether or not the Direct Delivery messages published by an external system should have dates in GMT or not.
Enable GMT for Foundation Data	Yes, No	No	Indicates whether or not any foundation data messages is being loaded into the system are in GMT.
Enable GMT for Inventory Adjustments	Yes, No	No	Indicates which date/time stamp is used in the inventory adjustment message when it is being published.
Enable GMT for Item Requests	Yes, No	No	Indicates whether or not the Item Request message being published should contain date/time stamps in GMT or not.
Enable GMT for POS Sale Import process	Yes, No	No	Indicates whether or not the POS Sales data is being loaded into the system are in GMT.
Enable GMT for Price Changes	Yes, No	No	Indicates whether price change messages being loaded into the system are in GMT or not. This also determines if the pricing date fields need to be converted when pushing data to a price management application.
Enable GMT for Receiving	Yes, No	No	Indicates whether or not receiving messages need to be published in GMT or not.
Enable GMT for ReSA sale import process	Yes, No	No	Indicates whether or not ReSA sales data is being loaded into the system in GMT.
Enable GMT for RTVs	Yes, No	No	Indicates whether or not the RTV message being loaded into the system is in GMT. Likewise, if SIM publishes any RTV message this will determine which date/time stamp is used on the message as well.
Enable GMT for Stock Counts	Yes, No	No	Indicates which date/time stamp is used in the stock count message when it is being published.
Enable GMT for Store Orders	Yes, No	No	Indicates whether or not the purchase order messages being loaded into the system has dates in GMT or not. Likewise, if SIM publishes any purchase order message this will determine which date/time stamp is used on the message as well.
Enable GMT for Store Transfers	Yes, No	No	Indicates 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.
Enable GMT for Third Party Stock Counts	Yes, No	No	Indicates whether the date/time stamp in the Third party stock count file (DSLDAT) is in GMT or not.
Enable GMT for Vendor ASN	Yes, No	No	Indicates whether or not the Vendor ASN messages being loaded into the system have dates in GMT or not.
Enable GMT for Warehouse Transfers	Yes, No	No	Indicates whether or not the transfer messages being loaded into the system have GMT dates or not. Likewise, if SIM publishes any transfer message to an external system this will determine which date/time stamp is used on the message as well.

Table: Topic: Transfer Receiving Options

System Administration Option	Valid Values	Default Value	Description
Damaged Delivery Email Alert	Yes, No	Yes	If Yes, an email notification is generated when the receipt is confirmed with one or more items received as damaged. If No, an email notification is not generated.
Days Shipped Delivery Overdue email alert	1-999	7	When a delivery record displays in SIM, the system will default the overdue date based on the current date + x days set by this parameter. If the delivery is not received by the date set, an email alert will be sent out.
Disable Discrepancy Checks in Transfer Receiving	Yes, No	No	If Yes, the system will not perform discrepancy checking and whatever, the user enters as a received quantity will not be validated against the expected quantity. If No, the system will perform discrepancy checking.
External Finisher UIN Qty Discrep Email Alert	Yes, No	Yes	If Yes, an email notification is generated when there is a discrepancy with the number of UINs on a Finisher Return Shipment and the received quantity. If No, an email notification is not generated.
Misdirected Container Email Alert	Yes, No	Yes	If Yes, an email notification is generated when a location marks a container to received that is meant for another destination. The notification will go to the original destination to inform them the container will be marked as missing. If no, an email notification is not generated.
Number of Days Received Transfer Deliveries can be Adjusted	0-999	30	When a receipt is created in SIM, the system will allow adjustments to a confirmed receipt until the number of days has passed.
Quick Receiving – Prompt for received containers	Yes, No	Yes	If Yes, if the user scans a container that has already been received, prompt the user. If No, if the user scans a container that has been received, do not prompt the user and ignore the scan.
Quick Receiving – Receive missing containers	Yes, No	Yes	If Yes, if the user scans a container with a status of missing, update the status to received. If No, if the user scans a container with a status of missing, do not change the status.
Secondary ASN UIN Qty Discrep Email Alert	Yes, No	Yes	If Yes, an email notification is generated when there is a discrepancy with the number of UINs on the secondary ASN and the received quantity. If No, an email notification is not generated.
Store Receiving Force Close Indicator	No Loss, Sending Loss, Receiving Loss	Receiving Loss	This parameter applies to deliveries with a source type of ‘Store’. No Loss – Any shipped quantity not received, does not affect either the receiving or sending store. Sending Loss – Any shipped quantity not received, is a loss at the sending store. Receiving Loss – Any shipped quantity not received, is the loss at the receiving store.
Store Receiving Over/Under Email Alert	Yes, No	Yes	If Yes, an email notification is generated when the user confirms a receipt with an over or under expected quantity. This is only applicable for transactions with a source type of ‘Store’. If No, an email notification is not generated.
Warehouse/Store UIN Qty Discrep Email alert	Yes, No	Yes	If Yes, an email notification is generated when the ASNin is injected thru the RIB or the AutoReceiveTransfershipment batch runs and the number of UINs on the ASN does not match the quantity received. This will inform the user that the delivery cannot be auto received. This is only applied for transactions with a source type of ‘Store’ or ‘Warehouse’. If No, an email notification is not generated.

Table: Topic: Transfers Options

System Administration Option	Valid Values	Default Value	Description
Add Item to Transfer requests	Yes, No	Yes	This option allows the user to add items to a transfer request sent from RMS (or external system).
Days to send Email alert before not after date for transfer requests	0-999	2	This option specifies the number of days prior to the not after date to send a notification. This applies to any transfer in a ‘Requested’ status.
Transfer Request Approve EMail Alert	Yes, No	Yes	If this option is set to Yes, an e-mail alert is sent when a transfer request has been approved. If No, an email notification is not generated.
Transfer Request Email Alert	Yes, No	Yes	If this option is set to Yes, an e-mail alert is sent when a transfer request has been made. If No, an email notification is not generated.
Transfer Request Reject E-mail Alert	Yes, No	Yes	If this option is set to Yes, an e-mail alert is sent when a transfer request has been rejected. If No, an email notification is not generated.
Unavailable Qty Discrepancy EMail Alert	Yes, No	No	If this option is set to Yes, an e-mail alert is sent when the quantity requested to transfer, is more than the quantity available to ship.

Table: Topic: User Interface Options

System Administration Option	Valid Values	Default Value	Description
Display HH Length: Diff 1	Numeric	6	This option sets the display of the first differentiator on the handheld to the specified number of characters. Because of space restrictions, no more than 21 total characters can be displayed on a single line on the handheld. The priority of display is Diff 1, Diff 2, Diff 3, and Diff 4. If Diff 1 takes up 20 characters, only one character of Diff 2 can be displayed.
Display HH Length: Diff 2	Numeric	6	This option sets the display of the second differentiator on the handheld to the specified number of characters. Because of space restrictions, no more than 21 total characters can be displayed on a single line on the handheld. The priority of display is Diff 1, Diff 2, Diff 3, and Diff 4. If Diff 1 takes up 20 characters, only one character of Diff 2 can be displayed.
Display HH Length: Diff 3	Numeric	6	This option sets the display of the third differentiator on the handheld to the specified number of characters. Because of space restrictions, no more than 21 total characters can be displayed on a single line on the handheld. The priority of display is Diff 1, Diff 2, Diff 3, and Diff 4. If Diff 1 takes up 20 characters, only one character of Diff 2 can be displayed.
Display HH Length: Diff 4	Numeric	6	This option sets the display of the fourth differentiator on the handheld to the specified number of characters. Because of space restrictions, no more than 21 total characters can be displayed on a single line on the handheld. The priority of display is Diff 1, Diff 2, Diff 3, and Diff 4. If Diff 1 takes up 20 characters, only one character of Diff 2 can be displayed.
Display Item Description	Long Description, Short Description	Short Description	This option specifies whether the long or short item description is displayed in SIM. This option applies to both the handheld and the PC.
Display Item Image Button	Yes, No	No	If Yes, an Image button is displayed on the Item Lookup Detail screen. If No, the button is not displayed. This allows the retailer to hide the button if the retailer does not support displaying images.
Item Request UI Limit	Not to exceed the value of the UI performance limitation configuration setting.	2890	This option will determine the maximum number of items allowed on an Item Request.
Problem Line UI Limit	Not to exceed the value of the UI performance limitation configuration setting.	1500	This option will determine the maximum number of line items allowed on a Problem Line stock count.
Search Limit Default for Container Lookup	1 - 999	500	This parameter indicates the default search limit for Container Lookup.
Search Limit Default for Customer Order Management	0-999	500	This parameter indicates the default search limit for Customer Order Management.
Search Limit Default for Home Page – Mobile	0-999	50	This parameter indicates the default search limit for the Home Page and Notification List screens (mobile).
Search Limit Default for Inventory Adjustments	1 - 999	500	This parameter indicates the default search limit for the Inventory Adjustment List screen and Filter.
Search Limit Default for Inventory Adjustments – Mobile	0-999	50	This parameter indicates the default search limit for the Inventory Adjustment List screen (mobile).
Search Limit Default for Item Lookup	1 - 999	500	This parameter indicates the default search limit for Item Lookup.
Search Limit Default for Item Lookup – Mobile	1-999	50	This parameter indicates the default search limit for the Item Lookup results (mobile).
Search Limit Default for Price Changes	1 - 999	500	This parameter indicates the default search limit for the Price Change Filter.
Search Limit Default for Sequencing	1 - 999	500	This parameter indicates the default search limit for the No Location List screen filter.
Search Limit Default for Staged Message Lookup	1 - 999	500	This parameter indicates the default search limit on the Filter screen for Staged Messages.
Search Limit Default for Supplier Lookup	1 - 999	500	This parameter indicates the default search limit for Supplier Lookup.
Search Limit Default for Supplier Lookup – Mobile	1-999	50	This parameter indicates the default search limit for the Supplier Lookup results (mobile).
Search Limit Default for Ticketing	1 – 999	500	This parameter indicates the default search limit for Ticket Lookup.
Search Limit Default for Transaction History	1-999	500	This parameter indicates the default search limit for Transaction History.
Search Limit Default for UIN Resolution	1 - 999	500	This parameter indicates the default search limit on the UIN Resolution List Screen and Filter.
Shelf Replenishment UI Limit	Not to exceed the value of the UI performance limitation configuration setting.	1500	This option will determine the maximum number of line items allowed on a Shelf Replenishment List. This check will occur in addition to and after the application limits the transaction based on the pick list system parameters.
Unit and Amount Count UI Limit	Not to exceed the value of the UI performance limitation configuration setting.	10	This option will determine the maximum number of line items allowed on a Unit and Amount stock count. This check will occur in addition to the Product Group variances values.
Unit Count UI Limit	Not to exceed the value of the UI performance limitation configuration setting.	10000	This option will determine the maximum number of line items allowed on a Unit stock count.

Table: Topic: UIN Options

System Administration Option	Valid Values	Default Value	Description
Allow Unexpected UINs	Yes, No	Yes	If No, SIM rejects the UIN in the following situations by prompting the user with an error message (EM14r): § Unexpected UIN for a Transfer § Inventory adjustment when UIN was not assigned to the current store § Stock Counts, when the item was not originally assigned to the current store If Yes, SIM allows the unexpected UIN for the previous situations and sends an e-mail alert and adds the item to problem line stock count. Completing the transaction updates the UIN Status and updates the store the UIN is assigned to.

System Administration Option

Valid Values

Default Value

Description

Allow Unexpected UINs

Yes, No

Yes

If No, SIM rejects the UIN in the following situations by prompting the user with an error message (EM14r):

§ Unexpected UIN for a Transfer

§ Inventory adjustment when UIN was not assigned to the current store

§ Stock Counts, when the item was not originally assigned to the current store

If Yes, SIM allows the unexpected UIN for the previous situations and sends an e-mail alert and adds the item to problem line stock count.

Completing the transaction updates the UIN Status and updates the store the UIN is assigned to.

Reporting

SIM has the ability to produce reports that retailers can customize to reflect the unique requirements of their business.

In SIM 15 reports will be accessed through BI Publisher 11g.

Operational Reports

Operational reports are generated from within the functional areas of SIM and include information about pick lists, stock count reports, shipping documentation, and so on. SIM uses a reporting tool when generating these reports in order to provide the user with a report formatting/layout mechanism.

The reporting tool allows the end user to specify the exact data fields to be displayed on the report (although this data is limited to the SIM data that is available for the specific operational report). Modifications to the formatting and data displayed on the report are made using the reporting tool.

SIM provides the user with a way to identify a single default report template to use for each of the different operational reports. When the user generates an operational report from within SIM, the application requests the report template that matches the default specified for that report.

Analytical (and Ad Hoc) Reports

Analytical reports leverage data in SIM for historical analysis. Retailers can develop their own and use these reports to make decisions on key business processes within the store (such as previous days deliveries, number of items replenished on a given day, and so on).

The reporting tool provides the retailer with a report formatting/layout mechanism and allows the user to specify the exact data fields to be displayed on the report. All report metrics and parameters are defined using the reporting tool (although this data is limited to the SIM data that is available for the specific report).

Assumptions

§ SIM does not reference any other external security to enforce privileges for the reporting tool. If a user is given the ability to generate a report or to launch the reporting tool within SIM, it is assumed that the user is given the necessary level of access for the reporting tool as well.

§ SIM does not manage any scheduling requirements for analytic (and ad hoc) reports. Such scheduling should be handled by the reporting tool itself.

SIM Reporting Framework

The following section describes the SIM reporting framework.

Printing to Local Printers in a Store

SIM is able to print to local printers in a store using BIPublisher, as long as the printers are network-enabled printers that support internet protocol printing (IPP). SIM uses BIPublisher as the printing engine. The printers must be network-enabled in order to communicate with BIPublisher.

Figure: Local Printing in a Store

The following is the workflow for the process of printing locally in a store:

1. A retailer makes a request on the HH or PC to print an item.

2. That request goes to the centrally installed BIPublisher server.

3. The BIPublisher server receives URLs or parameters, runs a query to retrieve data to be printed, and formats the data.

4. That data is then sent back to the store’s network-enabled printers.

SIM tables (STORE_PRINTER) refer only to the logical name of the printer. That logical name is setup using BIP-admin, for example, myPrinter1. Use BIPublisher to configure myPrinter1 with specifics.

SIM Operational Reports

The following are the SIM Operational Reports.

Table: Operational Reports

Report Name	Report Parameters	Primary Views or Tables
CustomerOrderBinLabelReport	BIN_ID, SIM_CUSTOMER_ORDER_ID, COPIES	FUL_ORD, FUL_ORD_BIN
CustomerOrderDeliveryBOLReport	Delivery_Id, Store_Timezone, COPIES	RPRT_FUL_ORD_DLV_BOL_V
CustomerOrderDeliveryReport	Delivery_Id, Store_Timezone, COPIES	RPRT_FUL_ORD_DLV_V
CustomerOrderPickDiscrepancyReport	Store_Timezone, Pick_Id, COPIES	RPRT_FUL_ORD_PICK_DISC_V
CustomerOrderPickReport	Store_Timezone, Pick_Id, COPIES	RPRT_FUL_ORD_PICK_V
CustomerOrderReport	Order_Id, Store_Timezone, COPIES	RPRT_FUL_ORD_V
CustomerOrderReversePickReport	Reverse_Pick_Id, Store_Timezone, COPIES	RPRT_FUL_ORD_RV_PICK_V
DirectDeliveryDiscrepantItemsReport	RECEIPT_ID, Store_Timezone, COPIES	RPRT_DSD_DISCREPANT_ITM_V, RPRT_DSD_V
DirectDeliveryReport	Receipt_ID, Store_Timezone, COPIES	RPRT_DSD_V, NOTES
InventoryAdjustmentReport	Inv_Adj_ID, Store_Timezone, COPIES	RPRT_INV_ADJUST_V, CONFIG_SYSTEM
ItemBasketDefaultReport	ITEM_BASKET_ID, CUST_REF, COPIES	No view, report is rendered using pass through parameters
ItemDetailReport	ITEMID, STOREID, Store_Timezone, COPIES	STORE_SEQUENCE_ITEM, STORE_SEQUENCE_AREA, PRINT_FORMAT, TSF_ALLOCATION, ITEM, WAREHOUSERPRT_ITEM_DETAIL_V
ItemRequestReport	Item_Request_ID, Store_Timezone, COPIES	RPRT_ITEM_REQUEST_V
PurchaseOrderReport	Purchase_order_id, store_timezone, copies	RPRT_PURCHASE_ORD_V
RTVReport	RETURN_ID, Store_Timezone, COPIES	RPRT_RTV_V
ShelfAdjustmentReport	SHELF_ADJUST_ID, Copies, Store_Timezone	RPRT_SHELF_ADJUST_V
ShelfReplenishmentReport	SHELF_REPLENISH_ID, Store_Timezone, Copies	RPRT_SHELF_REPLENISH_V
StockCountAllLocReport	STORE_ID, STOCK_COUNT_ID, COPIES	RPRT_STOCK_COUNT_V
StockCountExportReport	STOCK_COUNT_ID, COPIES	STOCK_COUNT_LINE_ITEM, STOCK_COUNT, STOCK_COUNT_LINE_ITEM_UIN
StockCountRejectedItemReport	STORE_ID, COPIES	RPRT_STOCK_COUNT_NOF_V
StockCountReport	STOCK_COUNT_ID, LOCATION_ID, Store_Timezone, PHASE, COPIES	RPRT_STOCK_COUNT_V
StoreOrderReport	STORE_ORDER_ID, COPIES	PRINT_STORE_ORDER, PRINT_STORE_ORDER_ITEM, STORE
TransferDeliveryExceptionReport	DELIVERY_ID	TSF_DELV, TSF_DELV_CARTON, TSF_DELV_LINE_ITEM, ITEM, STORE, WAREHOUSE, PARTNER, CONFIG_SYSTEM
TransferDeliveryReport	DELIVERY_ID	TSF_DELV, TSF_DELV_CARTON, TSF_DELV_LINE_ITEM, ITEM, STORE_ITEM_STOCK, STORE, WAREHOUSE, PARTNER, CONFIG_SYSTEM, NOTES
TransferReport	Transfer_ID, Store_Timezone, COPIES	RPRT_TRANSFER_V
TransferShipmentBolReport	SHIPMENT_ID, STORE_TIMEZONE, Copies	TSF_SHIP, TSF_SHIP_CARTON, TSF_SHIP_LINE_ITEM, ITEM, CONFIG_SYSTEM, SHIPMENT_BOL, SHIPMENT_CARTON_DIM, SHIPMENT_CARRIER_SERVICE, SHIPMENT_CARRIER, STORE, ADDRESS, NOTES
TransferShipmentCartonReport	Store_Timezone, CARTON_ID, COPIES	TSF_SHIP,TSF_SHIP_CARTON, TSF_SHIP_LINE_ITEM, ITEM, STORE, WAREHOUSE, PARTNER, CONFIG_SYSTEM, SHIPMENT_REASON
TransferShipmentReport	SHIPMENT_ID, Copies, Store_Timezone	RPRT_TSF_SHIP_V, NOTES
VendorShipmentBOLReport	Store_Timezone, SHIP_NUMBER, Copies	RPRT_RTV_SHIP_BOL_V, NOTES
VendorShipmentCartonReport	Store_Timezone, Carton_ID, COPIES	RPRT_RTV_SHIP_V
VendorShipmentReport	Store_Timezone, SHIP_NUMBER, Copies	RPRT_RTV_SHIP_V

Report Formats

The following section describes the report formats.

Figure: Customer Order Bin Label Report

Figure: Customer Order Delivery BOL Report

Figure: Customer Order Delivery Report

Figure: Customer Order Pick Discrepancy Report

Figure: Customer Order Pick Report

Figure: Customer Order Report

Figure: Customer Order Reverse Pick Report

Figure: Direct Delivery Discrepant Items Report

Figure: Direct Delivery Report

Figure: Inventory Adjustment Report

Figure: Item Basket Default Report

Figure: Item Detail Report

Figure: Item Request Report

Figure: Purchase Order Report

Figure: RTV Report

Figure: Shelf Adjustment Report

Figure: Shelf Replenishment Report

Figure: All Location Stock Count Report

Figure: StockCountExportReport [XML Format]

Stock_Count_Export

Figure: Rejected Items Report

Figure: Stock Count Report

Figure: Store Order Report

Figure: Transfer Receiving Exception Report

Figure: Transfer Receiving Report

Figure: Transfer Report

Figure: Transfer Shipment BOL Report

Figure: Transfer Shipment Container Report

Figure: Transfer Shipment Report

Figure: RTV Shipment BOL Report

BOL

BOL1

Figure: RTV Shipment Container Report

Figure: Shelf Adjustment List Report

Configuring a Report Printer in SIM

To configure a report printer in SIM, go to Admin > Print Setup > Printers. A screen opens, displaying a list of retail store printers. Users can add, delete, and edit printers for the user’s store. The system will allow a user to use the routing code to setup third party printing systems. The system can be configured to use either BI Publisher or a third party printing system, but not both at the same time.

Defining a Session Printer in SIM

SIM can be setup to automatically print a manifest or pre-shipment ticket or label to a printer at another location. To configure a session printer in SIM, go to Print > Session Printer. A screen opens, displaying the Manifest and Pre-Shipment format. Users can set printers for the user’s store.

Uploading Reports

The directory sim/bip_reports holds all SIM reports. For every report, there would be two folders<report_name>Report.xdm and <report_name>Report.xdo. These folders can be readily imported to the BI publisher (BIP) server. All the reports are pre-configured with datasource name BIP-SIM-DATASOURCE. A datasource with this exact name and appropriate jdbc connection string will have to be set up on the BIP server. In addition, all SIM operational reports need to be uploaded to the specific user’s folder that is accessing SIM reports. They may also be placed in the Guest folder to provide shared access.

The .rtf templates may be modified or customized as needed using the BI Publisher Template builder plug-in for Word.

Setting up the BI Publisher Server

1. Create a user and assign the BI Publisher Scheduler role, in addition to other reporting roles.

2. Create a new jdbc connection with datasource name BIP-SIM-DATASOURCE.

3. If you will print directly to a printer, create the printer in BIP. This printer server name will be used in STORE_PRINTER.NETWORK_ADDRESS in SIM. If a CUPS server is used, this will be set as <cups_server_name>/<printer_name> in STORE_PRINTER.NETWORK_ADDRESS.

4. When STORE_PRINTER.NETWORK_ADDRESS is set to browser (case insensitive), for any report in SIM, press Print to launch the report in a browser instead of printing to a physical printer. This is only possible when using the SIM PC client. This feature is useful in initial stages of implementation, or if it is preferred to view the report in a browser.

5. If STORE_PRINTER.STORE_PRINTER_TYPE_CODE is set to 1 (for postscript printing), the BI Publisher server will output the report in PDF format. If the STORE_PRINTER_TYPE_CODE is set to 2 (for ticket printing), the BI Publisher server will output the report in raw XML format (also known as DATA format in BI Publisher). This is to enable printing to a label printer, like Zebra printer, using a Custom Filter in BI Publisher.

Printing Labels and Tickets on a Label Printer

SIM was tested for printing labels and tickets on a Zebra label and ticket printer. This is achieved by using ZebraLink Enterprise Connector (ZEC) for Oracle BI Publisher. ZEC intercepts raw XML data coming from Oracle BI Publisher and applies a ZPL (Zebra Programming Language) template to create a ZPL stream understood by Zebra printers. For testing, BI Publisher was configured to output reports in raw XML format, which was redirected to ZEC to print to Zebra printer. ZEC works with a wide range of Zebra printers.

Printing Labels and Tickets on a Third Party Printing System

See the Oracle Retail Store Inventory Management Implementation Guide 4 (Extension Solutions) for suggestions on configuring SIM to use a third party printing solution.

Setting up SIM

Select the Reporting topic on the SIM System Admin Config screen. The following options need to be set up:

Table: Setting Up SIM Reports

Option	Value
Reporting Tool URL	http://<bip_host>:<bip_port>/<bip_deployment>. This URL is used as the reference to the BIP deployment for printing reports and viewing reports from the SIM PC client in a browser.

Note: <BIP_REPORTS_USER> is the reports user that has been created in BI Publisher server to access SIM reports.

UDA Print Setup

Go to Admin > Print Setup > UDA Print Setup.

If the UDA is defined on this screen, then when an item UDA is changed, the item UDA is sent to ticketing for a label, ticket or both, based upon definition on this screen.

Setting up Report Formats in SIM

Report Formats are configured in SIM through Admin> Print Setup > Print Format screen. See the Oracle Retail Store Inventory Management User Guide to add/modify/delete report formats. Multiple formats can be defined for each report type. For a report type, the formats screen enables the user to assign at least one format as the default format. This screen is also used to manage ticket and label formats. The user will select Reporting Formats from the Format Category drop down to work with report formats.

Figure: Report Formats Screen

After the SIM reports are uploaded to BI Publisher, the URL location for each report type must be set as follows:

Table: Report URL Locations

Type	URL Location
Customer Order Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderReport/CustomerOrderReport.xdo
Customer Order Bin Label Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderBinLabelReport/CustomerOrderBinLabelReport.xdo
Customer Order Delivery Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderDeliveryReport/CustomerOrderDeliveryReport.xdo
Customer Order Delivery BOL Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderDeliveryBOLReport/CustomerOrderDeliveryBOLReport.xdo
Customer Order Pick Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderPickReport/CustomerOrderPickReport.xdo
Customer Order Pick Discrepancy Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderPickDiscrepancyReport/CustomerOrderPickDiscrepancyReport.xdo
Customer Order Reverse Pick Report	<BIP_SIM_REPORTS_FOLDER>/SIM/CustomerOrderReversePickReport/CustomerOrderReversePickReport.xdo
Direct Delivery Report	<BIP_SIM_REPORTS_FOLDER>/SIM/DirectDeliveryReport/DirectDeliveryReport.xdo
Direct Delivery Discrepant Items Report	<BIP_SIM_REPORTS_FOLDER>/SIM/DirectDeliveryDiscrepantItemsReport/DirectDeliveryDiscrepantItemsReport.xdo
Inventory Adjustment Report	<BIP_SIM_REPORTS_FOLDER>/SIM/InventoryAdjustmentReport/InventoryAdjustmentReport.xdo
Item Detail Report	<BIP_SIM_REPORTS_FOLDER>/SIM/ItemDetailReport/ItemDetailReport.xdo
Item Basket Default Report	<BIP_SIM_REPORTS_FOLDER>/SIM/ItemBasketDefaultReport/ItemBasketDefaultReport.xdo
Item Request Report	<BIP_SIM_REPORTS_FOLDER>/SIM/ItemRequestReport/ItemRequestReport.xdo
Purchase Order Report	<BIP_SIM_REPORTS_FOLDER>/SIM/PurchaseOrderReport/PurchaseOrderReport.xdo
RTV Report	<BIP_SIM_REPORTS_FOLDER>/SIM/RTVReport/RTVReport.xdo
Stock Count Export Report	<BIP_SIM_REPORTS_FOLDER>/SIM/StockCountExportReport/StockCountExportReport.xdo
Stock Count All Loc Report	<BIP_SIM_REPORTS_FOLDER>/SIM/StockCountAllLocReport/StockCountAllLocReport.xdo
Shelf Adjustment Report	<BIP_SIM_REPORTS_FOLDER>/SIM/ShelfAdjustmentReport/ShelfAdjustmentReport.xdo
Shelf Replenishment Report	<BIP_SIM_REPORTS_FOLDER>/SIM/ShelfReplenishmentReport/ShelfReplenishmentReport.xdo
Stock Count Report	<BIP_SIM_REPORTS_FOLDER>/SIM/StockCountReport/StockCountReport.xdo
Stock Count Rejected Item Report	<BIP_SIM_REPORTS_FOLDER>/SIM/StockCountRejectedItemReport/StockCountRejectedItemReport.xdo
Store Order Report	<BIP_SIM_REPORTS_FOLDER>/SIM/StoreOrderReport/StoreOrderReport.xdo
Transfer Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferReport/TransferReport.xdo
Transfer Receiving Exception Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferDeliveryExceptionReport/TransferDeliveryExceptionReport.xdo
Transfer Receiving Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferDeliveryReport/TransferDeliveryReport.xdo
Transfer Shipment BOL Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferShipmentBolReport/TransferShipmentBolReport.xdo
Transfer Shipment Container Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferShipmentCartonReport/TransferShipmentCartonReport.xdo
Transfer Shipment Report	<BIP_SIM_REPORTS_FOLDER>/SIM/TransferShipmentReport/TransferShipmentReport.xdo
RTV Shipment BOL Report	<BIP_SIM_REPORTS_FOLDER>/SIM/VendorShipmentBOLReport/VendorShipmentBOLReport.xdo
RTV Shipment Container Report	<BIP_SIM_REPORTS_FOLDER>/SIM/VendorShipmentCartonReport/VendorShipmentCartonReport.xdo
RTV Shipment Report	<BIP_SIM_REPORTS_FOLDER>/SIM/VendorShipmentReport/VendorShipmentReport.xdo

Note: <BIP_SIM_REPORTS_FOLDER> is the folder where SIM reports have been uploaded on the BI Publisher server. For example, if SIM reports have been uploaded to the Guest folder, the folder is /Guest.

SIM Reports Internationalization

Create a translation (XLIFF) file. For different supported locales, a separate XLIFF file is provided to the BI Publisher. During run time, BI Publisher picks up the default template (RTF) file and the corresponding XLIFF (xlf) file.

Do the following to create an XLIFF file:

1. Install Oracle BI Publisher Desktop. You will see the following options in Microsoft Word:

§ Data

§ Insert

§ Preview

§ Tools

§ Help

Figure: Oracle BI Publisher Desktop Options in Word

2. Open any existing template in Word, for example, TransferReport.rtf.

Figure: TransferReport.rtf

3. Localize the template by selecting Tools> Option> Preview>Locale.

Figure: Localize the Template

This locale name will appear in the source-language attribute of the XLIFF file.

4. From the Template Builder menu, select Tool → Translate Template → Extract Text.

Figure: Extract Text for Export to XLIFF File

Template Builder extracts the translatable strings from the template and exports them to an XLIFF (.xlf) file.

5. Save the XLIFF file.

Figure: Save the XLIFF File

xlifsaveas

6. The XLIFF file generated by XML Publisher has the following structure:

<?xml version = '1.0' encoding = 'utf-8'?>

<file source-language="en_US" target-language="en_US" datatype="XDO"

original="orphan.xlf" product-version="orphan.xlf" product-name="">

<body>

<trans-unit id="e67afb09" maxbytes="4000" maxwidth="23" size-unit="char" translate="yes">

<source>Transfer Report</source>

<target>Transfer Report IN ENGLISH LANGUAGE</target>

<note>Text located: header/table</note>

</trans-unit>

<trans-unit id="7f65664e" maxbytes="4000" maxwidth="23" size-unit="char" translate="yes">

<source xml:space="preserve">Printed: </source>

<target xml:space="preserve">Printed: </target>

<note>Text located: footer/table</note>

</trans-unit>

<trans-unit id="b230538" maxbytes="4000" maxwidth="26" size-unit="char" translate="yes">

<source xml:space="preserve">Page Number: [&0] </source>

<target xml:space="preserve">Page Number: [&0] </target>

<note>Text located: footer/table</note>

</trans-unit>

The <file> element includes the attributes source-language and target-language.

The valid value for source-language and target-language is a combination of the language code and country code:

§ Language Code: the two-letter ISO language code (in lowercase).

§ Territory Code: the two-letter ISO country code (in uppercase).

The <source> element contains a translatable string from the template in the source language of the template.

The <target> element contains the translated string as per locale.

Different XLIFF (xlf) files can be created by providing translated strings to each <target> element and by specifying a target-language value as per naming convention.

Template/XLIFF(xlf) File Locale Selection Logic

At run time, BI Publisher picks up the default template provided in <ReportName>.xdo, then applies a translation based on the user’s selected Report Locale. First, BI Publisher tries to match an XLIFF file named for the locale, and if an exact match on language-territory is not found, then BI Publisher tries to match on language only.

For example, if you have a report for which the base template is TransferReport.rtf, and the locale is Japanese (ja_JP), then the order of preference in descending order is:

§ TransferReport_ja_JP.rtf

§ TransferReport_ja_JP.xlf

§ TransferReport_ja.rtf

§ TransferReport_ja.xlf

§ TransferReport.rtf

As soon as BI Publisher finds a matched template (RTF)/XLIFF file, it applies the translation and layout for the report.

Number, Date & Currency Format Support

BI Publisher supports number, date and currency formats by specifying BI Publisher format tasks.

1. Open any existing template in Word, for example, TransferReport.rtf.

Figure: Template and Placeholder of the XML Tag

2. Click the <ITEM> tag.

3. In the Text Form Field Options window, select Regular Text in the Type list.

Figure: Text Form Field Options Window

4. Click Add Help Text.

5. In the Form Field Help Text window, enter the formats for number, currency or date.

Figure: Form Field Help Text Window

The following are example formats for number, currency and date:

Example: Number Format

<?format-number; ‘NUMBER’;'999g999D99'?>

Where NUMBER is the <XML> tag.

Example: Currency Format

<?format-currency;CURRENCY;'CurrencyCode'?>

Where CURRENCY is the <XML> tag, and Currency Code should be ISO specific (‘JPY’,’USD’).

Example: Date Formats

<?format-date:date_string; ’ABSTRACT_FORMAT_MASK’;’TIMEZONE’?>

<?format-date-and-calendar:date_string; ’ABSTRACT_FORMAT_MASK’;’CALENDAR_NAME’;’TIMEZONE’?>

Where:

§ TimeZone is optional.

§ If no format mask is specified, the abstract format mask "MEDIUM" is used as default.

Additional Setting for Currency Format

The following format should be specified in the xdo.cfg file.

Example: Currency Format in xdo.cfg File

/*********************************************************************/

<currency-formats>

</currency-formats>

/**********************************************************************/

</config>

The xdo.cfg file should be uploaded to BI Publisher Server in zipped format along with the xdo, RTF and XLIFF files. See “Uploading Reports” for more information.

Report Engine Functional Specification

It is possible on the PC to print multiple reports at the same time to different individual printers or browser sessions.

The handheld will print the report that has been setup as the default option. If no default printer has been set up, the user is prompted to select the printer to print to.

The reporting functionality incorporates error handling when reports are printed. Error handling allows the user to continue in the event that the printing effort fails.

Detailed Report Information

The following includes detailed report information for commonly used reports.

Direct Delivery Report

Direct Delivery occurs when the supplier drops off merchandise directly to the retailer’s store. This report allows the retailer to print a delivery receipt once all items have been received and the delivery has been finalized.

It consists of the following information broken into three sections:

Header

§ Receipt Date – Date on which the receipt was created

§ Supplier – Supplier for the PO/ASN received

§ Store – Store at which goods were received

§ PO Number – PO against which goods were received

§ Invoice – Invoice number for the receipt

§ Invoice Date – Invoice date for the receipt

§ Comments

Detail

§ Item ID – Item number for each line item received

§ Item Description– Description of item

§ Unit of Measure – Unit of measure for quantity (Cases or Eaches)

§ Quantity Ordered– Quantity ordered according to the PO

§ Quantity Shipped – Quantity shipped according to the shipment record

§ Quantity Received – Quantity actually received

§ Unit Cost – Unit cost of the direct delivered item; this column is displayed based on the set system parameter (DISPLAY_UNIT_COST_FOR_DIRECT_DELIVERIES)

Totals

Totals are provided for the Ordered/Shipped and Received quantities.

A section is also provided as a space holder to collect the signatures of the persons involved in the transaction.

Item Request Report

The item request functionality allows users to request inventory for individual items to manage stock shortages and increased demand. The requests are processed by the RMS using the replenishment parameters and sourcing information setup in RMS. The report allows the store users to print the details of item requests that have been generated.

The report consists of two sections with the following information:

Header

§ Store – Store ID and name

§ Request ID – Request ID referencing the request in the SIM system

§ Expiration Date – Date setup to automatically close item requests that have been automatically generated by the product group scheduler, if no action has been taken

§ Request Delivery date – Date on which requested product is wanted at the store

§ User – User who generated the item request

§ Comments – Additional information

Detail

§ Item– Item number for each line item requested

§ Short Description– Description of item

§ SOH – Current available on hand inventory for the item

§ In Transit – Current inventory in transit to the store

§ UOM – Unit of measure for the request

§ Pack Size – Pack size for the item

§ Quantity – Quantity requested

Shelf Adjustment Report

The shelf adjustment report is related to shelf adjustment functionality in shelf replenishment supported by SIM. Shelf adjustment in SIM facilitates the creation of item lists for ad-hoc shelf replenishment along with facilitating movement of product between the back room and the shop floor and vice versa. Shelf Adjustment list can also be used to create replenishments of items for display purpose at a store. The shelf adjustment report allows the users to print the shelf adjustment list for operational purposes especially in case of on-the-fly movement of products from back room to shop floor and vice versa.

The report consists of two sections with the following information:

Header

§ Store - Name and identifier of the store for which the shelf adjustment was created

§ ID–Shelf adjustment list identifier used to uniquely identify a shelf adjustment list

§ Type – the type of shelf adjustment list, the types can move to shop-floor, move to backroom, ad-hoc and display list.

§ Create Date/Time–Date/Time when the shelf adjustment list was created

§ Update Date/Time–Date/Time when the shelf adjustment list was last updated

§ User – User who generated the shelf adjustment list

§ Status– Current status of the shelf adjustment list

Detail

§ SKU– Item number for each line item on the shelf adjustment list

§ Description– Description of item

§ UOM – Unit of measure for the item on the shelf adjustment list

§ Pack Size – Pack size for the item on the shelf adjustment list

§ Qty – Suggested quantity of the item on the shelf adjustment list

Shelf Replenishment Report

The shelf replenishment report is related to the shelf replenishment functionality supported by SIM. Shelf replenishment in SIM facilitates movement of product between the back room and the shop floor, for the purpose of display or for sale. The shelf replenishment lists generate replenishment items and quantities that need to be replenished to the shop floor. The shelf replenishment list report allows the users to print the generated shelf replenishment list for operational purposes (for example, to use as a reference for the actual replenishing of product by the store associate).

The report consists of two sections with the following information:

Header

§ Store - Name and identifier of the store for which the shelf replenishment was created

§ ID–Shelf replenishment list identifier used to uniquely identify a shelf replenishment list

§ Shelf replenishment Type - The type of shelf replenishment- capacity, sales, Ad-hoc, Display List

§ Replenishment Mode - Whether the mode of replenishment is End of day or Within Day

§ Product Group – Description of the product group, if, used to generate the shelf replenishment list

§ Hierarchy – Hierarchy details which is populated only for a sales based replenishment list

§ Shelf adjustment list – Identifier of the shelf adjustment list if it was used for replenishment list creation

§ Create Date/Time–Date/Time when the shelf replenishment list was generated

§ User – User who generated the shelf replenishment list

§ Status – Current status of the shelf replenishment list

§ Quantity – Total quantity to be replenished for the items in the shelf replenishment list.

Detail

§ Item Id– Item number for each line item to be replenished

§ Item Description – Description of item

§ Pick From Area – Identifies where the product is to be replenished from, could be either the back room or the delivery bay

§ Type – Replenishment Type

§ SUOM – Selling Unit of measure for the item to be replenished

§ Pack Size – Pack size for the item to be replenished

§ Qty – Requested quantity of the product to be replenished

§ Actual Qty – Actual quantity which was replenished for the product

Customer Order Report

The Customer Order Report in SIM displays all created picks and will allow the user to print a report, create a new pick, filter pick records and delete a pick.

Header

The report header consists of information for the pick and contains the following information:

§ Pick ID– Unique identifier for the pick record

§ Status – The status of the customer order

§ Create Date – The date the customer order was created

§ Complete Date – The date the customer order was complete

§ Create User – Name of the user who created the customer order

§ Complete User – Name of the user who completed the customer order

Detail

§ Item– Unique identifier for the item

§ Description– Description of item

§ Primary Loc– The macro sequence location for the item

§ SIM Customer – The customer order ID number

§ Bind ID – identifier number for the bind

§ Fulfillment– ID number that does not need to be unique, the same ID can exist for more than one customer order ID

§ UOM – The transaction unit of measure for the item on the customer order

§ Pack Size – The size of the pack

§ Substitute–Y indicates the line item has substitutes and N indicates the item does not have any substitutes

§ Adjusted Pick Qty – If cancellations/deliveries have occurred while the user picked, this field will populate with the adjusted pick quantity based on those order updates

§ Pick Qty – Suggested pick quantity generated by the system

§ Quantity – Actual amount being picked by the user

§ Type – Displays the type of pick

§ Pick Qty – Quantity of the product to be picked

§ Actual Qty – Actual quantity which was picked for the product

Stock Count Report

SIM provides the functionality to schedule, perform and authorize stock counts. The stock counts report provides the store users with the ability to print out scheduled stock counts and use the printed list of record results of the counting on the printed list before entering them into the system.

The report consists of two sections with the following information:

Header

§ Description– Master stock count description

§ Date – Scheduled date for the master stock count

§ Total Items – Total number of items in the master stock count

§ Stock count user – User who last saved/completed the stock count

§ Recount user – User who last saved/completed the recount

Detail

§ Child Count Description– Description of the child count appears as a header to the detail section (separate header for each child count). For guided counts, this will be the macro location name along with shopfloor/backroom if sequencing is being used.

§ Item– Item number for each line item in the stock count

§ Description– Description of item

§ UOM– Unit of measure for the item

§ Count – Physical count results entered for the stock count

Store Order Report

Store orders provide the store users the ability to create and approve orders to a supplier or transfer requests to the warehouse directly in the merchandising system. The store orders report allows the users to print out the report of the order that had been created from the store.

The report consists of two sections with the following information:

Header

§ Store – Store requesting the order

§ Store Order Number – Unique reference ID in SIM for the store order

§ Status– Current status of the store order. Valid values are Pending, Approved and Cancelled

§ Supplier/Warehouse – Source location for the store order

§ Creation Date – Date on which the store order was created

§ Not before date – Earliest date on which the order can be delivered at the store

§ Not after date – Expiration date for the order

§ User – User who created the store order

§ Comments – Additional information

Details

§ Item– Item number for each line item in the store order

§ Description– Description of item

§ UOM– Unit of measure for the item (part of the quantity heading)

§ Qty – Requested quantity for the item

§ Unit cost– Unit cost of the requested item

Transfer Report

Transfer functionality allows stores to transfer stock from one store to another within a company. The transfer report allows the store users to print out the details of either a transfer or a transfer request. The printed report can be used either as a dispatch slip for the transfer shipment or for the store records.

The report consists of two sections with the following information:

Header

§ Transfer from– Origin store location for the transfer

§ Transfer to – Destination store location for the transfer

§ Transfer number – Unique reference number for the transfer

§ Status/Date–Status of the transfer and the date on which the status changed

§ Comment– Additional information

§ Dispatched – Date on which the transfer was dispatched

Details

§ Item– Item number for each line item in the transfer

§ Description– Description of item

§ UOM– Unit of measure for the item

§ Dispatched– Quantity of product dispatched

§ Received– Quantity of product received

Item Detail Report

This is an Items report that is printed from the item detail screen and the handheld. The report is based on the view Itemlocstock. This report displays the following information:

§ SKU number/UPC

§ Description (long or short depending on parameter setting)

§ Diffs (if any)

§ Merchandise Hierarchy

§ Inventory Position (Available, unavailable, SOH, reserved)

§ Current price

§ Forward looking Delivery information (In transit, on order)

Inventory Adjustment Report

The inventory adjustment report allows the user to select an item that has been adjusted, and print information out for this. The report could be used to help as reference why inventory is unavailable (for example, loaning out for a demo or photoshoot), and confirmation that someone has ownership of that item.

The report consists of two sections with the following information:

Header

§ Store – The store ID

§ Adjustment Number – Unique inventory adjustment number in SIM

§ Create Date – Date of creation

§ Complete Date – Date of completion

§ User – User requesting inventory adjustment

§ Status – Status Pending or Completed

§ Comments – Comments, if any

Details

§ Item– Item number

§ Item Description– Item description

§ UOM– Unit of measure

§ Pack Size– Pack size

§ Quantity – Quantity adjusted

§ Reason– Inventory adjustment reason

Bill of Lading Report

SIM users can print the Bill of Lading. The printed Bill of Lading displays the status of the Bill of Lading through the appearance or absence of watermarks on the Bill of Lading. A generic template for the Bill of Lading is created and inserted into the format table.

The Bill of Lading report process is designed to allow retailers to create a Bill of Lading report during a Returns or a Transfer dialogue and print it.

The Bill of Lading consists of information that identifies the sender, the receiver and the carrier of the goods. It also lists the goods and their quantities that are being shipped. It identifies if the shipment is a result of a return or a transfer.

The process consists of two parts, creating the Bill of Lading and printing the Bill of Lading.

The Bill of Lading creation occurs in two stages. During the first stage, the Bill of Lading is automatically created when a shipment is created and saved. During the second stage, the Bill of Lading is updated when the retailer adds additional information to the transaction for the purpose of the Bill of Lading report such as requested pickup date, change of destination address, carrier name and address and change of motive for the shipment. Detailed information for a Return or Transfer such as the quantity being shipped or the items being shipped can be modified at any time prior to the dispatching of a shipment. The Bill of Lading is updated to reflect these changes.

The second part of the process occurs when the retailer prints the Bill of Lading. The Bill of Lading can be printed at anytime during the creation of a transfer or return. It is printed from the Return List screen or the Transfer List screen. It can be printed after the Return or Transfer is canceled (status = canceled) or after the transfer is dispatched. Each of these scenarios results in a variation of the Bill of Lading report. For example, if a Bill of Lading is printed prior to dispatching, the Bill of Lading will have a watermark across the page that reads DRAFT.

If the Bill of Lading is printed after dispatching it will have no watermark on it. If the Bill of Lading is printed after the Transfer or Return has been deleted (status = canceled), the Bill of Lading will have a watermark across the page that reads Canceled.

Printing the RTV Shipment Bill of Lading

Print the Bill of Lading from the RTV Shipment List screen.

The default filter for the RTV Shipment List screen will be changed to include displaying dispatched RTV Shipments with the current session.

1. If the RTV is in the In Progress state, the Bill of Lading prints with the watermark DRAFT on each page of the Bill of Lading.

2. If the RTV Shipment has been dispatched and it no longer appears on the List screen. use the filter to display the dispatched RTV Shipment.

3. The Bill of Lading prints without any watermarks.

4. If the RTV Shipment has been cancelled, use the filter to display the cancelled RTV Shipment.

The Bill of Lading will print with the watermark CANCELED on each page of the Bill of Lading.

Printing the Transfer Shipment Bill of Lading

The Bill of Lading can be printed from the Transfer Shipment List screen. If the Transfer Shipment does not appear on the Transfer Shipment List Screen, the filter must be used to display the Transfer Shipment.

1. If the transfer shipment is in the In Progress state, the Bill of Lading prints with the watermark DRAFT on each page of the Bill of Lading.

2. If the transfer shipment is in the Dispatched state, the Bill of Lading prints without any watermarks.

3. If the transfer shipment has been cancelled, the Bill of Lading prints with the watermark CANCELED on each page of the Bill of Lading.

A Appendix

SIM Permissions

The table below describes the permissions supported by SIM.

Table: SIM Permissions

Permission		Type		Topic		Usage
Access Admin		PC		Admin		With this permission, the Admin button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access Auto-Receive Stores		PC		Admin		With this permission, the Auto-Receive Stores button on the Store Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Buddy Store		PC		Admin		With this permission, the Buddy Store button on the Store Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Container Lookups		Handheld		Admin		With this permission, the Container Lookup menu option on the Lookups menu is displayed. Without this permission, the menu option is not displayed.
Access Container Lookup		PC		Admin		With this permission, the Container Lookup button on the Lookups screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customize Translations		PC		Admin		With this permission, the Customize Translations button on the UI Config screen is displayed and enabled. Without this permission, the button is not displayed.
Access Extended Attribute		PC		Admin		With this permission, the Ext. Attribute button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Extended Attribute Dept. Assign		PC		Admin		With this permission, the Assign to Dept. button on the Extended Attributes screen is displayed and enabled. Without this permission, the button is not displayed.
Access Extended Attribute Setup		PC		Admin		With this permission, the Setup Attributes button on the Extended Attributes screen is displayed and enabled. Without this permission, the button is not displayed.
Access Finisher Lookup		PC		Admin		With this permission, the Finisher Lookup button on the Lookups screen is displayed and enabled. Without this permission the button is not displayed.
Access Formats		PC		Admin		With this permission, the Print Format button on the Print Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Hierarchy Format		PC		Admin		With this permission, the Hierarchy Format button on the Print Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Inventory Adjustment Reason		PC		Admin		With this permission, the Inv. Adj. Reason button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Inventory Management		Handheld		Admin		With this permission, the Inv. Management menu option on the Main menu is displayed. Without this permission, the menu option is not displayed.
Access Inventory Management		PC		Admin		With this permission, the Inventory Mgmt button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access Item Lookups		Handheld		Admin		With this permission, the Item Lookups menu option on the Lookups menu is displayed. Without this permission, the menu option is not displayed.
Access Item Lookup		PC		Admin		With this permission, the Item Lookup button on the Lookups screen is displayed and enabled. Without this permission, the button is not displayed.
Access Lookups		Handheld		Admin		With this permission, the Lookups menu option on the Main menu is displayed. Without this permission, the menu option is not displayed.
Access Lookup		PC		Admin		With this permission, the Lookups button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access MPS Staged Messages		PC		Admin		With this permission, the MPS Staged Messages button on the Technical Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Access MPS Work Types		PC		Admin		With this permission, the MPS Worker Types button on the Technical Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Access Print		PC		Admin		With this permission, the Print button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access Printers		PC		Admin		With this permission, the Printers button on the Print Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Product Groups		PC		Admin		With this permission, the Product Group button on the Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Product Group Schedules		PC		Admin		With this permission, the Product Group Schedule button on the Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Report		PC		Admin		With this permission, the Reports button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access Session Printer		Handheld		Admin		With this permission, the Session Printer menu option on the Main menu is displayed. Without this permission, the menu option is not displayed.
Access Session Printer		PC		Admin		With this permission, the Session Printer button on the Print Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Setup		PC		Admin		With this permission, the Setup button on the Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Shipment Reasons		PC		Admin		With this permission, the Shipment Reason button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Shipping and Receiving		Handheld		Admin		With this permission, the Shipping/Receiving menu option on the Main menu is displayed. Without this permission, the menu option is not displayed.
Access Shipping Receiving		PC		Admin		With this permission, the Shipping/Receiving button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access SIM Managed Store		PC		Admin		With this permission, the SIM Managed Stores button on the SIM Stores screen is displayed and enabled. Without this permission, the button is not displayed.
Access SIM Store		PC		Admin		With this permission, the SIM Stores button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Store Admin		PC		Admin		With this permission, the Store Admin button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Store Defaults Admin		PC		Admin		With this permission, the Store Defaults Admin button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Supplier Lookup		Handheld		Admin		With this permission, the Supplier Lookup menu option on the Lookups menu is displayed. Without this permission, the menu option is not displayed.
Access Supplier Lookup		PC		Admin		With this permission, the Supplier Lookup button on the Lookups screen is displayed and enabled.It also is required to display the Primary Supplier button on the Item Detail screen. Without this permission, the button is not displayed.
Access System Admin		PC		Admin		With this permission, the System Admin button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Technical Maintenance		PC		Admin		With this permission, the Technical Maintenance button on the Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Access Tolerances		PC		Admin		With this permission, the Tolerances button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access Transaction History		PC		Admin		With this permission the Tran History button on the Lookups screen is displayed and enabled. Without this permission, the button is not displayed.
Access UDAs		Handheld		Admin		With this permission, the View UDAs menu option is enabled on the Item Lookup menu. Without this permission, the menu option is not displayed.
Access UDAs		PC		Admin		With this permission, the UDA option button on the Item Lookup screen is displayed and enabled. Without this permission, the option button is not displayed. With this permission, the UDA Print Setup button on the Print Setup screen is displayed and enabled. Without this permission the screen is not displayed. With this permission, the UDA Detail button on the Item Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access UI Configuration		PC		Admin		With this permission, the UI Configuration button on the Technical Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Activate Debugging in Client Log		PC		Admin		With this permission, the Repository tab on the Client Status dialogue is displayed, and the debug-activated check box on the Stats tab will be enabled. Without this permission, the repository tab is not displayed and the debug-activated check box will be disabled.
Add Extended Attribute Department		PC		Admin		With this permission, the Add, Save and Cancel buttons on the Assign Attributes screen are displayed and enabled. Without this permission, the buttons are not displayed.
Add Inventory Adjustment Reason		PC		Admin		With this permission, the Add button on the Inventory Adjustment Reason Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Add Shipment Reasons		PC		Admin		With this permission, the Add button on the Shipment Reason Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Create Product Groups		PC		Admin		With this permission, the Create button on the Product Group List screen is displayed and enabled. Without this permission, the button is not displayed.
Create Product Group Schedules		PC		Admin		With this permission, the Create button on the Product Group Schedule List screen is displayed and enabled. Without this permission, the button is not displayed.
Create Translations		PC		Admin		With this permission, the Create button on the Translation Details screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Extended Attribute Department		PC		Admin		With this permission, the Remove button on the Assign Attributes screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Inventory Adjustment Reason		PC		Admin		With this permission, the Delete button on the Inventory Adjustment Reason Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Product Groups		PC		Admin		With this permission, the Delete button on the Product Group List screen with be displayed and enabled. Without this permission, the button is not displayed. If the button is displayed, the user must also have the necessary data permission for the product group the user is attempting to delete. If the user is not authorized for the product group type, User is not authorized to delete this type of Product Group.
Delete Product Group Schedules		PC		Admin		With this permission, the Delete button on the Product Group Schedule List screen is displayed and enabled. Without this permission, the button is not displayed. If the button is displayed, the user must also have the necessary data permission for the product group that is associated to the product group schedule that is attempted to be deleted. If the user is not authorized for the product group type, User is not authorized to delete this type of Product Group Schedule.
Delete Shipment Reasons		PC		Admin		With this permission, the Delete button on the Shipment Reason Maintenance screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Staged Messages		PC		Admin		With this permission, the Delete button on the MPS Staged Message Lookup screen is displayed and enabled. Without this permission, the button is not displayed.
Display Stock Locator		Handheld		Admin		With this permission, the Stock Locator option on the Item Lookup menu is displayed and enabled. Without this permission, the menu option is not displayed.
Display Stock Locator		PC		Admin		With this permission, the Stock Locator button on the Item Lookup screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Extended Attribute Setup		PC		Admin		With this permission, the Save and Cancel buttons on the Setup Attributes screen are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Product Groups		PC		Admin		With this permission, when a user double-clicks on an existing Product Group, the Product Group Detail screen will open. If the user also has the correct data permission for the product group type, the screen will open in Edit mode. Without the necessary data permission for the type, the screen will open in View-only mode. The user must also have this permission for each store that is included on the product group. If the user does, then the user can edit the product group; if the user does not, then the screen will open in View-only mode.
Edit Product Group Schedules		PC		Admin		With this permission, when a user double-clicks on an existing Product Group Schedule, the Product Group Schedule Detail screen will open. If the user also has the correct data permission for the product group type, the screen will open in Edit mode. Without the necessary data permission for the type, the screen will open in View only mode. The user must also have this permission for each store that is included on the schedule. If the user does, then the user can edit the schedule; if the user does not then the screen will open in View-only mode.
Override Price		Handheld		Admin		With this permission, the override price on the Ticket Detail screen is enabled. Without this permission, the override price is not displayed.
Access Customer Details		PC		Customer Order		With this permission, the Customer button on the Customer Order Detail screen. This permission is needed to access the customer details such as name, address for a customer order. Without this permission, the button is not displayed.
Access Customer Order		Handheld		Customer Order		With this permission, the Customer Orders menu option on the Cust Ord Mgmt menu is displayed. Without this permission the option is not displayed. With this permission, the Customer Orders menu option on the Item Lookup menu is displayed. Without this permission, the option is not displayed.
Access Customer Order		PC		Customer Order		With this permission, the Customer Order button on the Customer Order Management List screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, when a user double-clicks on an existing customer order on the Customer Order Management List screen, the Customer Order Detail screen will open. Without this permission, when a user double clicks on an existing customer order on the Customer Order Management List screen, the user is not allowed to access the transaction. With this permission, the Customer Orders button on the Item Lookup pop-up search screen is displayed and enabled. Without this permission the tab will be disabled. With this permission, the Customer Orders button on the Item Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customer Order Delivery		Handheld		Customer Order		With this permission, the Deliver Cust Order menu option on the Cust Ord Mgmt menu is displayed. Without this permission, the option is not displayed.
Access Customer Order Delivery		PC		Customer Order		With this permission, the Delivery button on the Customer Order List screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, the Delivery button on the Customer Order Detail screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, when a user double-clicks on an existing customer order delivery on the Customer Order Management List screen, the Customer Order Detail screen will open. Without this permission, when a user double clicks on an existing customer order on the Customer Order Management List screen, the user is not allowed to access the transaction.
Access Customer Order Delivery Attribute		Handheld		Customer Order		With this permission, the Add Ext Attribute menu option on the Customer Order Summary menu is displayed. Without this permission, the menu option is not displayed.
Access Customer Order Delivery Attribute		PC		Customer Order		With this permission, the Ext. Attributes button on the Delivery Summary screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customer Order Management		Handheld		Customer Order		With this permission, the Customer Order Mgmt menu option on the Main menu is displayed. Without this permission the option is not displayed.
Access Customer Order Management		PC		Customer Order		With this permission, the Customer Order Mgmt button on the SIM Login screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customer Order Pick		Handheld		Customer Order		With this permission, the Customer Order Pick menu option on the Cust Ord Mgmt menu is displayed. Without this permission the option is not displayed.
Access Customer Order Pick		PC		Customer Order		With this permission, the Pick button on the Customer Order Management List screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customer Order Reverse Pick		PC		Customer Order		With this permission, the Reverse Pick button on the Customer Order Detail screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, the Reverse Pick button on the Customer Order List screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, when a user double-clicks on an existing customer order reverse pick record on the Customer Order Management List screen, the Customer Order Detail screen will open. Without this permission, when a user double clicks on an existing customer order reverse pick record on the Customer Order Management List screen, the user is not allowed to access the transaction.
Cancel Submit Customer Order Delivery		Handheld		Customer Order		With this permission, the Cancel Submit menu option on the Delivery Summary menu is displayed. Without this permission the option is not displayed.
Cancel Submit Customer Order Delivery		PC		Customer Order		With this permission, the Cancel Submit button on the Customer Order Delivery Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Customer Order Pick		Handheld		Customer Order		With this permission, the Confirm Now menu option on the Pick Summary menu is displayed. Without this permission, the option is not displayed.
Confirm Customer Order Pick		PC		Customer Order		With this permission, the Confirm button on the Customer Order Pick List Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Customer Order Reverse Pick		PC		Customer Order		With this permission, the Confirm button on the Customer Order Reverse Pick Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create Customer Order Delivery For Pickup		Handheld		Customer Order		With this permission, the Create Delivery menu option on the Deliver Cust Order menu is displayed. In addition, the option will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Pickup'. Without this permission, the option is not displayed.
Create Customer Order Delivery For Pickup		PC		Customer Order		With this permission, the Create button on the Customer Order Delivery List screen is displayed and enabled. In addition, the button will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Pickup'. Without this permission, the button is not displayed.
Create Customer Order Delivery for Shipment		Handheld		Customer Order		With this permission, the Create Delivery menu option on the Deliver Cust Order menu is displayed. In addition, the option will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Shipment'. Without this permission the option is not displayed.
Create Customer Order Delivery for Shipment		PC		Customer Order		With this permission, the Create button on the Customer Order Delivery List screen is displayed and enabled. In addition, the button will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Shipment'. Without this permission, the button is not displayed.
Create Customer Order Pick		Handheld		Customer Order		With this permission, the Create Pick menu option on the Customer Order Pick menu is displayed. Without this permission the option is not displayed.
Create Customer Order Pick		PC		Customer Order		With this permission, the Create button on the Customer Order Pick List screen is displayed and enabled. Without this permission, the button is not displayed.
Create Customer Order Reverse Pick		PC		Customer Order		With this permission, the Create button on the Customer Order Reverse Pick List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Customer Order Delivery		Handheld		Customer Order		With this permission, the Delete Delivery menu option on the Delivery Summary screen is displayed. Without this permission, the option is not displayed.
Delete Customer Order Delivery		PC		Customer Order		With this permission, the Delete button on the Customer Order Delivery List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Customer Order Pick		Handheld		Customer Order		With this permission, the Delete Pick menu option on the Pick Summary screen is displayed. Without this permission, the option is not displayed.
Delete Customer Order Pick		PC		Customer Order		With this permission, the Delete button on the Customer Order Pick List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Customer Order Reverse Pick		PC		Customer Order		With this permission, the Delete button on the Customer Order Reverse Pick List screen is displayed and enabled. Without this permission, the button is not displayed.
Dispatch Customer Order Delivery		Handheld		Customer Order		With this permission, the Dispatch Now menu option on the Delivery Summary screen is displayed. Without this permission, the option is not displayed.
Dispatch Customer Order Delivery		PC		Customer Order		With this permission, the Dispatch button on the Customer Order Delivery Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Dispatch Incomplete Customer Order Delivery		Handheld		Customer Order		With this permission, when the Dispatch Now has been selected on the Delivery Summary screen and the customer order is incomplete a warning message is displayed to the user and allowed to cancel or continue. Without this permission, when the Dispatch Now has been selected on the Delivery Summary screen when the customer order is incomplete, an error message is displayed to the user and the user cannot continue.
Dispatch Incomplete Customer Order Delivery		PC		Customer Order		With this permission, when the Dispatch button on the Customer Order Delivery Detail screen has been selected and the customer order is incomplete, a warning message is displayed to the user and allowed to cancel or continue. Without this permission, when the Dispatch button has been selected on the Delivery Summary screen when the customer order is incomplete, an error message is displayed to the user and the user cannot continue.
Edit Customer Order BOL		PC		Customer Order		With this permission, the BOL Detail screen will open in Edit mode. In addition, the View Customer Order BOL permission is required to gain access to the screen. Without this permission, the BOL Detail screen is View-only.
Edit Customer Order Delivery Attribute		PC		Customer Order		With this permission, the Apply, Add, Remove and Cancel buttons on the Extended Attribute Data Entry screen are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Customer Order Delivery For Pickup		Handheld		Customer Order		With this permission, the Edit Delivery menu option on the Deliver Cust Order menu is displayed. In addition, the option will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Pickup'. Without this permission, the option is not displayed.
Edit Customer Order Delivery For Pickup		PC		Customer Order		With this permission, when a user double-clicks on an existing Customer Order Delivery record, the Customer Order Delivery Detail screen will open. In addition, only the orders with a Reservation Type 'Web Orders' and Delivery Type 'Pickup' will be editable. Without this permission, the screen will open in View-only mode.
Edit Customer Order Delivery For Shipment		Handheld		Customer Order		With this permission, the Edit Delivery menu option on the Deliver Cust Order menu is displayed. In addition, the option will only be available for orders with a Reservation Type 'Web Orders' and Delivery Type 'Shipment'. Without this permission, the option is not displayed.
Edit Customer Order Delivery For Shipment		PC		Customer Order		With this permission, when a user double-clicks on an existing Customer Order Delivery record, the Customer Order Delivery Detail screen will open. In addition, only the orders with a Reservation Type 'Web Orders' and Delivery Type 'Shipment' will be editable. Without this permission, the screen will open in View-only mode.
Edit Customer Order Pick		Handheld		Customer Order		With this permission, the Review Pick menu option on the Pick Summary screen is displayed. Without this permission, the option is not displayed.
Edit Customer Order Pick		PC		Customer Order		With this permission, when a user double-clicks on an existing Customer Order Pick record, the Customer Order Pick Detail screen will open in an edit mode. Without this permission, the screen will open in View-only mode.
Edit Customer Order Reverse Pick		PC		Customer Order		With this permission, when a user double-clicks on an existing Customer Order Reverse Pick record, the Customer Order Reverse Pick Detail screen will open in edit mode. Without this permission, the screen will open in View-only mode.
Item Substitution For Picking		Handheld		Customer Order		With this permission, the Item Substitution option on the Pick Detail screen is enabled. Without this permission, the option is not displayed.
Item Substitution for Picking		PC		Customer Order		With this permission, the Item Substitution button on the Customer Order Pick Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Reject Customer Order		PC		Customer Order		With this permission, the Reject button on the Customer Order Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Submit Customer Order Delivery		Handheld		Customer Order		With this permission, the Submit menu option on the Delivery Summary screen is displayed. Without this permission, the option is not displayed.
Submit Customer Order Delivery		PC		Customer Order		With this permission, the Submit button on the Customer Order Delivery Detail screen is displayed and enabled. Without this permission, the button is not displayed.
View Customer Order BOL		PC		Customer Order		With this permission, the BOL button on the Customer Order Delivery Detail screen is displayed and enabled. The BOL Detail screen will open in View-only mode. Without this permission, the button is not displayed.
Access Adjust Container DSD Receiving		Handheld		DSD Receiving		With this permission, the Adjust menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Adjust Container DSD Receiving		PC		DSD Receiving		With this permission, the Adjust button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Confirm Container DSD Receiving		Handheld		DSD Receiving		With this permission, the Confirm menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Confirm Container DSD Receiving		PC		DSD Receiving		With this permission, the Confirm button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Confirm DSD Receipt		Handheld		DSD Receiving		With this permission, the Confirm menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Confirm DSD Receipt		PC		DSD Receiving		With this permission, the Confirm button on the DSD Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Container Additional Details		Handheld		DSD Receiving		With this permission, the Additional Details option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Create Container		Handheld		DSD Receiving		With this permission, the Create Container menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Create Container		PC		DSD Receiving		With this permission, the Create Container button on the DSD Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Customer Order		PC		DSD Receiving		With this permission, the Customer Orders button on the DSD Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Default Quantity DSD Receiving		Handheld		DSD Receiving		With this permission, the Default Qty menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Default Quantity DSD Receiving		PC		DSD Receiving		With this permission, the Default Qty button on the DSD Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Delete Container		Handheld		DSD Receiving		With this permission, the Delete Container menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Delete Container		PC		DSD Receiving		With this permission, the Delete button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Delete Receipt		Handheld		DSD Receiving		With this permission, the Delete Receipt menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Delete Receipt		PC		DSD Receiving		With this permission, the Delete Delivery button on the DSD Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Delivery Additional Details		Handheld		DSD Receiving		With this permission, the Additional Details menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Document DSD Receiving		PC		DSD Receiving		With this permission, the Document button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access DSD Receiving		Handheld		DSD Receiving		With this permission, the DSD Receiving menu option on the Shipping/Receiving screen is displayed. Without this permission, the menu option is not displayed.
Access DSD Receiving		PC		DSD Receiving		With this permission, the DSD Receiving button on the Shipping/Receiving screen is displayed and enabled. Without this permission, the button is not displayed.
Access DSD Receiving Ext. Attribute		Handheld		DSD Receiving		With this permission, the Add Ext Attribute menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access DSD Receiving Ext. Attribute		PC		DSD Receiving		With this permission, the Ext. Attributes button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Item Receiving		Handheld		DSD Receiving		With this permission, the Item Receiving menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Purchase Order		Handheld		DSD Receiving		With this permission, the Purchase Order menu option on the DSD Receiving screen is displayed. Without this permission, the menu option is not displayed.
Access Purchase Order		PC		DSD Receiving		With this permission, the Purchase Order button on the Shipping/Receiving screen is displayed and enabled. Without this permission, the button is not displayed.
Access Reject Delivery		Handheld		DSD Receiving		With this permission, the Reject Delivery menu option on the Receipt Summary screen is displayed. The menu option is only displayed when applying an ASN to a delivery. Without this permission, the menu option is not displayed.
Access Reject Delivery		PC		DSD Receiving		With this permission, the Reject Delivery button on the DSD Receiving Detail screen is displayed and enable. The button is only displayed when applying an ASN to a delivery. Without this permission, the button is not displayed.
Access Remove Item DSD Receiving		Handheld		DSD Receiving		With this permission, the Remove Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Remove Item DSD Receiving		PC		DSD Receiving		With this permission, the Remove Item button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Review Items		Handheld		DSD Receiving		With this permission, the Review Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Un-Receive All DSD Receiving		PC		DSD Receiving		With this permission, the Clear Qty menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Add New Item DSD Receiving		Handheld		DSD Receiving		With this permission, the Add New Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Add New Item DSD Receiving		PC		DSD Receiving		With this permission, the Add/Scan Item button on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed. The Add/Scan Item button will always be available when creating a receipt.
Allow DSD Receiving Without PO		Handheld		DSD Receiving		With this permission, the Create Receipt menu option on the DSD Receiving screen is displayed. Without this permission, the menu option is not displayed.
Allow DSD Receiving Without PO		PC		DSD Receiving		With this permission, the Create Receipt menu option on the DSD Receiving List screen is displayed and enabled. Without this permission, the button is not displayed.
Allow DSD Receiving With PO		Handheld		DSD Receiving		With this permission, the Create Receipt menu option on the PO Detail screen is displayed. Without this permission, the menu option is not displayed.
Allow DSD Receiving With PO		PC		DSD Receiving		With this permission, the Create Receipt button on the Purchase Order Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Allow Over Receiving		Handheld		DSD Receiving		With this permission, the user is allowed to over-receive quantities for a DSD Receipt. Without this permission, the user is not allowed to over-receive quantities and a message is displayed.
Allow Over Receiving for DSD Receiving		PC		DSD Receiving		With this permission, the user is allowed to over-receive quantities. Without this permission, the user is not allowed to over-receive quantities and will be prompted when damaged and received quantity is larger than the expected quantity.
Allow Receiving Damages		Handheld		DSD Receiving		With this permission, the Record Damages menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Allow Receiving Damages		PC		DSD Receiving		With this permission, the damaged column on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the damaged column is not displayed.
Display Expected Quantity		Handheld		DSD Receiving		With this permission, the expected quantity on the Item Detail screen is displayed. Without this permission, the quantity is not displayed.
Display Expected Quantity		PC		DSD Receiving		With this permission, the expected quantity column on the DSD Receiving Container Detail screen is displayed and enabled. Without this permission, the column is not displayed.
Edit Container		Handheld		DSD Receiving		With this permission, the Edit Container menu option on the Receipt Summary screen is displayed. Without this permission, the menu option is not displayed.
Edit Container		PC		DSD Receiving		With this permission, when the user double-clicks on an existing Container in the DSD Receiving Detail screen, the DSD Receiving Container Detail screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit Container Info DSD Receiving		PC		DSD Receiving		With this permission, the Container Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit Delivery Info		PC		DSD Receiving		With this permission, the Direct Delivery Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit DSD Receiving		PC		DSD Receiving		With this permission, when the user double-clicks on an existing Receipt in the DSD Receiving List screen, the DSD Receiving Detail screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit DSD Receiving Ext. Attribute		PC		DSD Receiving		With this permission, the Apply, Add, Remove and Cancel buttons on the Extended Attributes Entry screen are displayed and enabled. Without this permission, the buttons are not displayed.
Override Supplier Discrepancies		Handheld		DSD Receiving		With this permission, the user can override the supplier discrepancies check during the DSD receipt. Without this permission, the message “Quantity received is larger than expected, reduce the quantity received” is displayed.
Override Supplier Discrepancies		PC		DSD Receiving		With this permission, the user can override the supplier discrepancies check during the DSD receipt. With this permission, the user can override the supplier discrepancies check during the direct delivery receipt. Without this permission, the message “Quantity received is larger than expected, reduce the quantity received” is displayed.
Receive DSD Receiving on Shop Floor		Handheld		DSD Receiving		With this permission, the Receive on Shop Floor prompt on the DSD Receiving Detail screen will be displayed. Without this permission the prompt is not displayed.
Receive Direct Delivery on Shop Floor		PC		DSD Receiving		With this permission, the Receive on Shop Floor check box on the DSD Container Info screen is displayed and enabled. Without this permission, the check box is not enabled.
Review Direct Delivery		Handheld		Direct Delivery		With this permission, the Review Items menu option on the Direct Delivery screen is displayed. Without this permission, the menu option is not displayed.
Email Alert – AGSN UIN Items on Incoming ASN Failed		Server		Email		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.
Email Alert - Customer Order Pick Reminder		Server		Email		With this permission, the user will be notified, if the pick list has been created but not actioned. Without this permission, the user will not be notified.
Email Alert - Customer Order Receipt		Server		Email		With this permission, the user will be notified when customer orders are received. Without this permission, the user will not be notified.
Email Alert - Customer Order Reminder		Server		Email		With this permission, the user will be notified when the customer order has not been fulfilled. Without this permission, the user will not be notified.
Email Alert – Damaged Delivery		Server		Email		With this permission, the user will be notified when the delivery includes damaged items. Without this permission, the user will not be notified.
Email Alert – Finisher Delivery Unable to Auto-Receive		Server		Email		With this permission, the user will be notified when the finisher delivery UIN qty discrepancy exists on an incoming ASN during batch processing. Without this permission, the user will not be notified.
Email Alert – Finisher UIN Discrepancy		Server		Email		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.
Email Alert – Misdirected Container		Server		Email		With this permission, the user will be notified when a container has been received in another location. Without this permission, the user will not be notified.
Email Alert - New Customer Order		Server		Email		With this permission, the user will be notified when customer orders are created. Without this permission, the user will not be notified.
Email Alert – Over Received Quantity		Server		Email		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.
Email Alert – Receiving UIN Discrepancy		Server		Email		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.
Email Alert –RTV Request Expiration Approaching		Server		Email		With this permission, the user will be notified if the supplier return request expiration date is approaching. Without this permission, the user will not be notified.
Email Alert – Shipped Delivery Overdue		Server		Email		With this permission, the user will be notified when the shipped delivery has not been received and has passed the expected date. Without this permission, the will not be notified.
Email Alert – Store Delivery Unable to Auto-Receive		Server		Email		With this permission, the user will be notified when a store delivery has discrepancies and cannot be auto received. Without this permission, the user will not be notified.
Email Alert – Store Receiving Over/Under		Server		Email		With this permission, the user will be notified when a store transfer has over/under received quantities. Without this permission, the user will not be notified.
Email Alert – Transfer Delivery Finisher UIN Qty Mismatch		Server		Email		With this permission, the user will be notified when a finisher delivery has a UIN Qty Mismatch between the expected qty and the number of UINs included on the ASN. Without this permission, the user will not be notified.
Email Alert – Transfer Delivery Store UIN Qty Mismatch		Server		Email		With this permission, the user will be notified when a store transfer delivery has a UIN Qty Mismatch between the expected qty and the number of UINs included on the ASN. Without this permission, the user will not be notified.
Email Alert – Transfer Delivery Warehouse UIN Qty Mismatch		Server		Email		With this permission, the user will be notified when a warehouse delivery has a UIN Qty Mismatch between the expected qty and the number of UINs included on the ASN. Without this permission, the user will not be notified.
Email Alert - Transfer Request		Server		Email		With this permission, the user will be notified when a transfer request is created. Without this permission, the user will not be notified.
Email Alert – Transfer Request Approved		Server		Email		With this permission, the user will be notified when a transfer request is approved. Without this permission, the user will not be notified.
Email Alert – Transfer Request Expiration Approaching		Server		Email		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. Without this permission, the user will not be notified.
Email Alert – Transfer Request Rejected		Server		Email		With this permission, the user will be notified when a transfer request is rejected. Without this permission, the user will not be notified.
Email Alert – Transfer Unavailable Request Quantity		Server		Email		With this permission, the user will be notified when the requested quantity is no longer available at the requested source location. Without this permission, the user will not be notified.
Email Alert - Unexpected UIN (Store Changed)		Server		Email		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.
Email Alert – Warehouse Delivery Unable to Auto-Receive		Server		Email		With this permission, the user will be notified when the delivery includes pre-populated serial numbers and cannot be automatically received. Without this permission, the user will not be notified.
Access Notifications		Mobile		Home Page		With this permission, the bell notification icon will be enabled. Without this permission, it will be disabled.
Send Notification		Mobile		Home Page		With this permission, the user will be able to swipe an open transaction and send a notification. Without this permission, the notify function will not be available.
View Transactions		Mobile		Home Page		With this permission, the user will be able to view all of the open transactions on the home page (depending on data permissions). Without this permission, the home page will still display (just without the transactions listed) allowing for changing the store and the access to notifications; however the list of open transactions will be empty.
Access Inventory Adjustments		Handheld		Inventory Adjustments		With this permission, the Inventory Adjustments menu option on the Inv. Management menu is displayed. Without this permission the menu option is not displayed.
Access Inventory Adjustment		PC		Inventory Adjustments		With this permission, the Inventory Adjustment button on the Inventory Management screen is displayed and enabled. Without this permission, the button is not displayed.
Access Inventory Adjustment Attribute		Handheld		Inventory Adjustments		With this permission, the Add Ext Attribute menu option on the Inventory Adj. Summary menu is displayed. Without this permission, the menu option is not displayed.
Access Extended Attribute Data on Inv Adj		Mobile		Inventory Adjustments		With this permission, the Attributes panel on the Inventory Adjustment Detail screen is displayed and enabled. Without this permission, the Attributes panel is not displayed.
Access Inventory Adjustment Attribute		PC		Inventory Adjustments		With this permission, the Ext. Attributes button on the Inventory Adjustment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Complete Inventory Adjustment		Handheld		Inventory Adjustments		With this permission, the Confirm Now menu option on the Inventory Adjustment Summary screen is displayed. Without this permission, the menu option is not displayed. The Confirm Later menu option will be available to save the transaction.
Complete Inventory Adjustment		Mobile		Inventory Adjustments		User must have this permission in order for the Confirm action to appear on the footer menu on the Inventory Adjustment Detail Screen. Without this permission, the user will not be able to confirm the transaction, but only be able to Save the transaction.
Complete Inventory Adjustment		PC		Inventory Adjustments		With this permission, the Confirm button on the Inventory Adjustment Detail screen is displayed and enabled. Without this permission, the button is not displayed. The Save button will be enabled to save the transaction.
Create Inventory Adjustment		Mobile		Inventory Adjustment		With this permission, the Create button on the Inventory Adjustment List Screen will be displayed and enabled. Without this permission, the button will not be displayed. The permission must exist in order for the Copy action to be available to the user. This action is available in the footer menu and allows the user to copy ‘Completed’ adjustments.
Create Inventory Adjustment		PC		Inventory Adjustments		With this permission, the Create button on the Inventory Adjustment List screen is displayed and enabled. The Copy button is also enabled with this permission when the user is copying completed adjustments. Without this permission, the button is not displayed.
Create UIN on the Fly		Mobile		Inventory Adjustments		With this permission, the user will be 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. Without this permission, the user will not be able to create a new UIN.
Delete Inventory Adjustment		Handheld		Inventory Adjustments		With this permission, the Delete Inv. Adj. menu option on the Inventory Adj. Summary screen is displayed. Without this permission, the menu option is not displayed.
Delete Inventory Adjustment		Mobile		Inventory Adjustments		User must have this permission for the Delete Action to appear in the footer menu on the Inventory Adjustment List screen to delete inventory adjustments.
Delete Inventory Adjustment		PC		Inventory Adjustments		With this permission, the Delete button on the Inventory Adjustment List screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Inventory Adjustment		Handheld		Inventory Adjustments		With this permission, the Edit Inv. Adj. menu option in the Inventory Adj. menu is displayed. Without this permission, the menu option is not displayed.
Edit Inventory Adjustment	Mobile		Inventory Adjustments		With this permission, when the user double-clicks on an existing Inventory Adjustment on the Inventory Adjustments List Screen the Inventory Adjustment Detail screen will open with the Inventory Adjustment and allow the user to make changes. Without this permission, when the user double-clicks on an existing Inventory Adjustment, the Inventory Adjustment Detail screen will open and the user will only be allowed to view the information, but not to make any changes. This will require all fields and actions to be disabled, except for the Cancel, Info, Notes and Print.
Edit Inventory Adjustment	PC		Inventory Adjustments		With this permission, when the user double-clicks on an existing Inventory Adjustment in the Inventory Adjustment List screen, the Inventory Adjustment Detail screen will open in edit mode The Add Item button is also displayed and enabled. Without this permission, the screen will open in View-only mode.
Edit Inventory Adjustment Attribute	PC		Inventory Adjustments		With this permission, the Apply, Add, Remove and Cancel buttons on the Extended Attributes Entry screen are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Extended Attribute Data on Inv Adj	Mobile		Inventory Adjustments		With this permission, Attributes can be added/removed: The Add Attributes and Remove Attributes (Trash can) buttons will be available on the Attributes panel of the Inventory Adjustment Detail. Without this permission, attributes cannot be added or removed.
Edit Quantity	Mobile		Inventory Adjustments		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.
Access Item Basket	Handheld		Item Basket		With this permission, the Item Basket menu option on the Inv. Management menu is displayed. Without this permission, the menu option is not displayed.
Add Item to Item Basket	Handheld		Item Basket		With this permission, the Add Item option on the Item Basket summary menu is displayed. Without this permission, the menu option is not displayed.
Create Item Basket	Handheld		Item Basket		With this permission, the Create Item Basket menu option on the Item Basket menu is displayed. Without this permission, the menu option is not displayed.
Delete Item Basket	Handheld		Item Basket		With this permission, the Delete Item Basket option on the Item Basket summary menu is displayed. Without this permission, the menu option is not displayed.
Delete Item from Item Basket	Handheld		Item Basket		With this permissio,n the Delete Item option on the Item Basket summary menu is displayed. Without this permission, the menu option is not displayed.
Print Item Basket	Handheld		Item Basket		With this permission, the Print Ticket option on the Item Basket summary is displayed. Without this permission, the menu option is not displayed.
Save Item Basket	Handheld		Item Basket		With this permission, the Save Basket option on the Item Basket summary is displayed. Without this permission, the menu option is not displayed.
View Item Basket	Handheld		Item Basket		With this permission, the View Details option on the Item Basket summary is displayed. Without this permission, the menu option is not displayed.
Access Item Requests	Handheld		Item Requests		With this permission, the Item Requests menu option on the Inv. Management menu is displayed. Without this permission, the menu option is not displayed.
Access Item Request	PC		Item Requests		With this permission, the Item Request button on the Inventory Management screen is displayed and enabled. Without this permission, the button is not displayed.
Add Items to Item Request	PC		Item Requests		With this permission and the Edit Item Requests permission, the Add Item button on the Item Request Detail screen is displayed and enabled when editing an existing Item Request. Without this permission, the button is not displayed. This permission does not apply when creating an Item Request. Add Item button will always be available when creating.
Add or Edit Item For Item Request	Handheld		Item Requests		With this permission, the Edit Item Request menu option on the Item Request menu is displayed. Without this permission, the menu option is not displayed. With this permission, the Add/Edit Item menu option on the Item Requests Summary screen is displayed. Without this permission the menu option is not displayed when editing an Item Request. With this permission, the message “Item is not on the request. Would you like to add it?” and the Yes and No menu options are displayed. Without this permission, the message screen is not displayed. This permission does not apply when creating an item request. Users will always be able to add and edit items when creating an item request.
Create Item Request	Handheld		Item Requests		With this permission, the Create Item Request menu option on the Item Requests menu is displayed. Without this permission, the menu option is not displayed.
Create Item Request	PC		Item Requests		With this permission, the Create button on the Item Request List screen is displayed and enabled. The Add Items button will also be enabled on the Item Request Detail screen. Without this permission, the button is not displayed.
Delete Item Request	Handheld		Item Requests		With this permission, the Delete Item Request menu option on the Item Requests menu is displayed. Without this permission, the menu option is not displayed.
Delete Item Request	PC		Item Requests		With this permission, the Delete button on the Item Request List screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, the Item Remove button on the Item Request Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Item Request	Handheld		Item Requests		With this permission, the Edit Item Request menu option on the Item Requests menu is displayed. Without this permission, the menu option is not displayed.
Edit Item Request	PC		Item Requests		With this permission, when the user double clicks on an existing Item Request in the Item Request List screen, the Item Request Detail screen will open in edit mode. Without this permission, the screen will open in View-only mode.
Request Item Request	Handheld		Item Requests		With this permission, the Request Item Request menu option on the Item Requests menu is displayed. Without this permission the menu option is not displayed. With this permission, the Request Now menu option on the Item Requests Summary screen is displayed. Without this permission the menu option is not displayed.
Request Items	PC		Item Requests		With this permission, the Request button on the Item Request Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Item Ticket	Handheld		Item Tickets		With this permission, the Ticket Printing menu option on the Main menu is displayed. Without this permission, the menu option is not displayed.
Access Item Ticket	PC		Item Tickets		With this permission, the Item Ticket button on the Print Menu screen is displayed and enabled. Without this permission, the button is not displayed.
Access Item Ticket Batch	PC		Item Tickets		With this permission, the Item Ticket Batch button in the Print Menu screen is displayed and enabled. Without this permission, the button is not displayed.
Access Item Ticket Price Override	Handheld		Item Tickets		With this permission the Ticketing Price Override menu is displayed and the user can override the price on the Ticket Detail screen. Without this permission, the menu is not displayed and the user cannot override the price.
Create Item Ticket	PC		Item Tickets		With this permission, the Create button on the Item Tickets List screen and the Add Ticket button on the Item Ticket Batch Detail screen are displayed and enabled. Without this permission, the buttons are not displayed.
Create Item Ticket Batch	PC		Item Tickets		With this permission, the Create Batch button on the Item Ticket Batch List screen and Generate Tickets button on the Add Transaction screen are displayed and enabled. Without this permission, the button is not displayed.
Delete Item Ticket	PC		Item Tickets		With this permission, the Delete button on the Item Tickets List, Item Ticket Batch List screens and the Remove Ticket button on the Item Ticket Batch Detail screens are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Item Ticket	PC		Item Tickets		With this permission, when the user double clicks on an existing Item Ticket in the Item Ticket List or Item Ticket Batch Detail screen, the Item Ticket Detail screen will open in edit mode. With this permission, when the user double clicks on an existing item ticket batch on the Item Ticket Batch List screen, the Item Ticket Batch Detail screen will open in edit mode. Without this permission, the screens will open in View-only mode.
Print Item Ticket	PC		Item Tickets		With this permission, the Print Tickets button on the Item Ticket List, Item Ticket Detail, Item Ticket Batch List and Item Ticket Batch Detail screens are displayed and enabled. Without this permission, the button is not displayed. Note: If the format type is Auto Generated SN, the Print Tickets button is controlled by the Print UIN Auto Generate Serial Number permission.
Update Format Item Ticket	PC		Item Tickets		With this permission, the Update Format button on the Item Ticket List, Item Tickets Batch List and Item Ticket Batch Detail screens are displayed and enabled. Without this permission, the buttons are not displayed.
Update SOH Item Ticket	PC		Item Tickets		With this permission, the Refresh Qty button on the Item Tickets List, Item Ticket Batch List and Item Ticket Batch Detail screens are displayed and enabled. Without this permission, the buttons are not displayed.
Access Price Change	PC		Price Changes		With this permission, the Price Change button on the Inventory Management screen is displayed and enabled. Without this permission, the button is not displayed.
Create Price Change	PC		Price Changes		With this permission, the Create button on the Price Change List screen is displayed and enabled. Without this permission, the button is not displayed.
Print Item Tickets For Price Changes	PC		Price Changes		With this permission, the Item Tickets button on the Price Change List screen is displayed and enabled. Without this permission, the button is not displayed.
Print Shelf Labels For Price Changes	PC		Price Changes		With this permission, the Shelf Labels button on the Price Change List screen is displayed and enabled. Without this permission, the button is not displayed.
Accept RTV	PC		RTV		With this permission, the Accept button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access RTV	PC		RTV		With this permission, the RTV button on the Shipping/Receiving screen is displayed and enabled. Without this permission, the button is not displayed.
Add Items To RTV	PC		RTV		With this permission, the Add Item button on the RTV Detail screen is displayed and enabled. Without this permission, the button will not display. If the user is creating an RTV, the Add Item button will always be available.
Approve RTV	PC		RTV		With this permission, the Approve button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Close RTV	PC		RTV		With this permission, the Close RTV button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create RTV	PC		RTV		With this permission, the Create RTV button on the RTV List Screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Items from RTV	PC		RTV		With this permission, the Remove Item button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Delete RTV	PC		RTV		With this permission, the Delete button on the RTV Detail Screen is displayed and enabled. Without this permission, the button is not displayed.
Edit RTV	PC		RTV		With this permission, when the user double-clicks on an existing RTV in the RTV List screen, the RTV Detail screen will open in edit mode. Without this permission, the RTV Detail screen will open in view-only mode.
Reject RTV	PC		RTV		With this permission, the Reject button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Shipment Create RTV	PC		RTV		With this permission, the Ship button on the RTV Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access RTV Shipment	Handheld		RTV Shipment		With this permission, the RTV Shipment button on the Shipping/Receiving menu is displayed. Without this permission, the button is not displayed.
Access RTV Shipment	PC		RTV Shipment		With this permission, the RTV Shipment button on the Shipping/Receiving screen is displayed and enabled. Without this permission, the button is not displayed.
Access RTV Shipment Attribute	Handheld		RTV Shipment		With this permission, the Add Ext Attribute menu option on the RTV Container Detail screen is displayed. Without this permission, the menu option is not displayed.
Access RTV Shipment Attribute	PC		RTV Shipment		With this permission, the Ext. Attributes button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Add Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Add Container menu option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Add Items to RTV Shipment	PC		RTV Shipment		With this permission and the Edit RTV Shipment permission, the Add Item button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed. If the user is creating an RTV, the Add Item button is always available.
Add Or Edit Items To RTV Shipment	Handheld		RTV Shipment		With this permission, the Add/Edit Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed. If the user is creating an RTV, the Add/Edit Item menu option is always displayed.
Adjust Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Adjust Container menu option on the RTV shipment Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Allow Non Document Items RTV Shipment	Handheld		RTV Shipment		With this permission, the user is allowed to add items not existing on the RTV selected. Without this permission, the user can only ship items already existing on the RTV document.
Allow Non Document Items RTV Shipment	PC		RTV Shipment		With this permission, the user is allowed to add items not existing on the RTV selected. Without this permission, the user can only ship items already existing on the RTV document.
Allow over shipping RTV Shipment	Handheld		RTV Shipment		With this permission, the user is allowed to ship more products than approved on the RTV. Without this permission, the user will not be allowed to overship.
Allow over shipping RTV Shipment	PC		RTV Shipment		With this permission, the user is allowed to ship more products than approved on the RTV. Without this permission, the user will not be allowed to overship.
Cancel Submit RTV Shipment	Handheld		RTV Shipment		With this permission, the Cancel Submit menu option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Cancel Submit RTV Shipment	PC		RTV Shipment		With this permission, the Cancel Submit button on the RTV shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Confirm Container menu option on the RTV shipment Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Confirm RTV Shipment Container	PC		RTV Shipment		With this permission, the Confirm button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create RTV Shipment	Handheld		RTV Shipment		With this permission, the Create menu option on the RTV Shipment menu is displayed. Without this permission, the menu option is not displayed.
Create RTV Shipment	PC		RTV Shipment		With this permission, the Create button on the RTV Shipment List screen and the Add Item button on the RTV Shipment Detail screen is displayed and enabled. Without this permission, the buttons are not displayed.
Default Items to RTV Shipment	Handheld		RTV Shipment		With this permission, the Default Item menu option on the RTV Shipment menu is displayed. Without this permission, the menu option is not displayed.
Default Items to RTV Shipment	PC		RTV Shipment		With this permission, the Default Item button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the menu option is not displayed.
Delete Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Delete container menu option on the RTV shipment Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Delete Container RTV Shipment	PC		RTV Shipment		With this permission, the Delete button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Item from RTV Shipment	Handheld		RTV Shipment		With this permission, the Delete Item menu option on the RTV shipment Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Delete Items from RTV Shipment	PC		RTV Shipment		With this permission, the Remove Item button on the RTV shipment Container Detail screen is displayed and enabled. Without this permission, the menu option is not displayed.
Delete RTV Shipment	Handheld		RTV Shipment		With this permission, the Delete option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Delete RTV Shipment	PC		RTV Shipment		With this permission, the Delete button on the RTV Shipment Detail screen is displayed and enabled. Without the permission, the button is not displayed.
Dispatch Now RTV Shipment	Handheld		RTV Shipment		With this permission, the Dispatch Now menu option on the RTV Shipment Summary menu is displayed. Without this permission, the menu option is not displayed.
Dispatch RTV Shipment	PC		RTV Shipment		With this permission, the Dispatch button on the RTV Shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Edit Container menu option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Edit RTV Shipment	Handheld		RTV Shipment		With this permission, the Edit menu option on the RTV Shipment screen is displayed. Without this permission, the menu option is not displayed.
Edit RTV Shipment	PC		RTV Shipment		With this permission, when the user double-clicks on an existing RTV Shipment on the RTV Shipment List screen, the RTV Shipment Detail screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit RTV Shipment Attribute	PC		RTV Shipment		With this permission, the Apply, Add, Remove and Cancel buttons on the Extended Attribute Entry screen is displayed and enabled. Without this permission, the buttons are not displayed.
Edit RTV Shipment BOL	PC		RTV Shipment		With this permission, the BOL button on the RTV Shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Header Info for RTV Shipment	Handheld		RTV Shipment		With this permission, the Header Info menu option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Open RTV Shipment	PC		RTV Shipment		With this permission, the Open button on the RTV Shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Review Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Review Container menu option on the RTV Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Save Container RTV Shipment	Handheld		RTV Shipment		With this permission, the Save menu option on the RTV Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Save RTV Shipment	Handheld		RTV Shipment		With this permission, the Save menu option on the RTV Shipment Summary screen is displayed.
Submit RTV Shipment	Handheld		RTV Shipment		With this permission, the Submit menu option on the RTV Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Submit RTV Shipment	PC		RTV Shipment		With this permission, the Submit button on the RTV Shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
View RTV Shipment BOL	PC		RTV Shipment		With this permission, the BOL button is displayed and enabled. The BOL Detail screen is view only. Without this permission, the button is not displayed.
Access Password Configuration	PC		Security		With this permission, the Password Configuration button on the Security menu is displayed and enabled. Without this permission, the button is not displayed.
Access Role Maintenance	PC		Security		With this permission, the Role Maintenance button on the Security menu is displayed and enabled. Without this permission, the button is not displayed.
Access Security	PC		Security		With this permission, the Security button on the Admin menu is displayed and enabled. Without this permission, the button is not displayed.
Access User Maintenance	PC		Security		With this permission, the User Maintenance button on the Security menu is displayed and enabled. Without this permission, the button is not displayed.
Assign Password	PC		Security		With this permission, the Assign Password button on the User Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Assign User Group	PC		Security		With this permission, the Assign Group button on the User Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Assign User Role	PC		Security		With this permission, the Assign Roles button on the User Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Assign User Store	PC		Security		With this permission, the Assign Stores button on the User Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create User	PC		Security		With this permission, the Create button on the User List is displayed and enabled. Without this permission, the button is not displayed.
Delete Role	PC		Security		With this permission, the Delete button on the Role List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete User	PC		Security		With this permission, the Delete button on the User List screen is displayed and enabled. Without this permission, the button is not displayed.
Edit User	PC		Security		With this permission, when the user double-clicks on an existing user in the User List screen, the User Detail screen will open in edit mode. Without this permission, the User Detail screen will open in view-only mode.
Mass Assign User Role	PC		Security		With this permission, the Mass Assign Roles button on the Security menu is displayed and enabled. Without this permission, the button is not displayed.
Mass Assign User Store	PC		Security		With this permission, the Mass Assign Stores button on the Security menu is displayed and enabled. Without this permission, the button is not displayed.
Access Sequencing	Handheld		Sequencing		With this permission the Sequencing menu option on the Inv. Management menu is displayed. Without this permission the menu option is not displayed.
Access Sequencing	PC		Sequencing		With this permission, the Sequencing button on the Inventory Management menu is displayed and enabled. Without this permission, the button is not displayed.
Add Item to Location	PC		Sequencing		With this permission, the Add Item button on the Micro Sequence Edit screen is displayed and enabled. Without this permission, the button is not displayed.
Add Locations for an Item	PC		Sequencing		With this permission, the Add Location button on the Item Locations List screen is displayed and enabled. Without this permission, the button is not displayed.
Add Sequencing Locations	PC		Sequencing		With this permission, the Add Location button on the Macro Sequence Edit screen is displayed and enabled. Without this permission, the button is not displayed.
Apply Class List to Location	PC		Sequencing		With this permission, the Apply Class List button on the Macro Sequence Edit screen is displayed and enabled. Without this permission, the button is not displayed.
Apply Item List to Location	PC		Sequencing		With this permission, the Apply Item List button on the Micro Sequence Edit screen is displayed and enabled. Without this permission, the button is not displayed.
Arrange Items Within Location	PC		Sequencing		With this permission, the Move Up and Move Down buttons on the Micro Sequence Edit screen are displayed and enabled. Without this permission, the buttons are not displayed.
Arrange Sequencing Locations	PC		Sequencing		With this permission, the Move Up and Move Down buttons on the Macro Sequence Edit screen are displayed and enabled. Without this permission, the buttons are not displayed.
Delete Items from a Location	PC		Sequencing		With this permission, the Remove Item button on the Micro Sequence Edit screen is displayed and enabled. Without this permission, this button is not displayed.
Delete Locations for an Item	PC		Sequencing		With this permission, the Remove Item button on the Item Location List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Sequencing Locations	PC		Sequencing		With this permission, the Remove Item button on the Macro Sequence Edit screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Items Within A Location	PC		Sequencing		With this permission, when the user double- clicks on an existing Sequencing Location in the Macro Sequence List screen, the Micro Sequence List screen will open in edit mode. Without this permission, the Micro Sequence List screen will open in view-only mode. With this permission, when the user double-clicks on an existing Item in the Micro Sequence List screen, the Item Location List screen will open in edit mode. Without this permission, the Micro Sequence List screen will open in view-only mode. With this permission, the Edit Items button on the Micro Sequence List screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Sequencing Locations	PC		Sequencing		With this permission, the Edit Locations button on the Macro Sequence List screen is displayed and enabled. Without this permission, the button is not displayed.
Sequence Items	Handheld		Sequencing		With this permission, the Sequence Item menu option on the Sequencing menu is displayed. Without this permission, the menu option is not displayed.
Sequence Items Within A Location	Handheld		Sequencing		With this permission, the Sequence all items in a location menu option on the Sequencing menu is displayed. Without this permission, the menu option is not displayed.
Access Shelf Adjustment	Handheld		Shelf Adjustment		With this permission, the Shelf Adjustment menu option on the Shelf Replenishment menu is displayed. Without this permission, the menu option is not displayed.
Create Shelf Adjustment	Handheld		Shelf Adjustment		With this permission, the Create menu option on the Shopfloor Adjust, Backroom Adjust, Display List and Ad Hoc Replenish menu is displayed. Without this permission, the menu option is not displayed.
Access Shelf Replenishment	Handheld		Shelf Replenishment		With this permission, the Shelf Replenishment menu option on the Inv. Management menu is displayed. Without this permission, the menu option is not displayed.
Access Shelf Replenishment	PC		Shelf Replenishment		With this permission, the Shelf Replenishment button on the Inventory Management menu is displayed and enabled. Without this permission, the button is not displayed.
Action Shelf Replenishment	Handheld		Shelf Replenishment		With this permission the Action Shelf Replen menu option on the Shelf Replenishment menu is displayed. Without this permission the menu option is not displayed.
Create Shelf Replenishment	Handheld		Shelf Replenishment		With this permission, the Within Day and the End Of Day menu options on the Shelf Replenishment menu is displayed. Without this permission, the menu options is not displayed.
Create Shelf Replenishment	PC		Shelf Replenishment		With this permission, the Create button on the Shelf Replenishment List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Shelf Replenishment	PC		Shelf Replenishment		With this permission, the Delete button on the Shelf Replenishment screen is displayed and enabled. Without this permission, the button is not displayed.
Replenishment Item Substitution	Handheld		Shelf Replenishment		With this permission, the Item Substitution option on the Pick Detail screen is enabled. Without this permission, the option is not displayed. Note: This permission only applies when the user has selected to allow item substitution when prompted.
Replenishment Item Substitution	PC		Shelf Replenishment		With this permission, the Allow Substitute Item check box on the Shelf Replenishment Create screen is displayed and enabled. Without this permission, the check box is not enabled.
Access Ad-Hoc Stock Counts	Handheld		Stock Counts		With this permission, the Ad Hoc Stock Count menu option on the Stock Counting menu is displayed. Without this permission, the menu option is not displayed.
Access Stock Count	Handheld		Stock Counts		With this permission the Stock Counts menu option on the Inv. Management menu is displayed. Without this permission, the menu option is not displayed.
Access Stock Count Attriubute	Handheld		Stock Counts		With this permission, the Add Ext Attribute menu option on the Stock Counting menu is displayed. Without this permission, the menu option is not displayed.
Access Stock Count Attribute	PC		Stock Counts		With this permission, the Ext. Attributes button on the Stock Count Detail and Stock Re-count Detail screen are displayed and enabled. Without this permission, the button is not displayed.
Access Stock Count	PC		Stock Counts		With this permission, the Stock Counts button on the Inventory Management menu is displayed and enabled. Without this permission, the button is not displayed.
Amend Stock Count	Handheld		Stock Counts		With this permission, the <amend> option (or Shift-5 function) on the Stock Counting screen is displayed and enabled. Without this permission, the option is not displayed and the Shift-5 function is not available.
Amend Stock Re-Count	Handheld		Stock Counts		With this permission, the <amend> option (or Shift-5 function) for stock re-counts is displayed and enabled. Without this permission, the option is not displayed and the Shift-5 function is not available.
Authorize Stock Count	PC		Stock Counts		With this permission, the Authorize button on the Child Stock Count List screen is displayed and enabled. Without this permission, the button is not displayed.
Complete Stock Count	Handheld		Stock Counts		With this permission, the Complete Count menu option on the Stock Counting menu is displayed. Without this permission, the menu option is not displayed.
Complete Stock Count	PC		Stock Counts		With this permission, the Complete button on the Child Stock Count List, the Stock Count Detail and the Stock Re-Count Detail Screens is displayed and enabled. Without this permission, the button is not displayed.
Confirm Authorization Stock Count	PC		Stock Counts		With this permission, the Confirm Authorization button on the Child Stock Count List screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Child Stock Count	PC		Stock Counts		With this permission, the Confirm Child button on the Stock Count Authorization screen is displayed and enabled. Without this permission, the button is not displayed.
Count Stock Count	Handheld		Stock Counts		With this permission, the Stock Count menu option on the Stock Counting menu is displayed. Without this permission, the menu option is not displayed.
Create Ad-Hoc Stock Count	Handheld		Stock Counts		With this permission, the Create New Count menu option on the Ad-Hoc Stock Count menu is displayed. Without this permission, the menu option is not displayed.
Delete Stock Count	PC		Stock Counts		With this permission, the Delete button on the Stock Count List screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Adhoc Stock Count	PC		Stock Counts		With this permission, when the user double-clicks on an existing Ad Hoc Stock Count in the Stock Count List screen, the Child Stock Count List screen will open in edit mode. Without this permission, the Child Stock Count List screen will open in view-only mode.
Edit Stock Count Attribute	PC		Stock Counts		With this permission, the Apply, Add, Remove and Cancel button on the Extended Attribute Entry screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Unit Amount Stock Count	PC		Stock Counts		With this permission, when the user double-clicks on an existing Unit and Amount Stock Count in the Stock Count List screen, the Child Stock Count List screen will open in edit mode. Without this permission, the Child Stock Count List screen will open in view-only mode.
Edit Unit Stock Count	PC		Stock Counts		With this permission, when the user double-clicks on an existing Unit Stock Count in the Stock Count List screen, the Child Stock Count List screen will open in edit mode. Without this permission, the Child Stock Count List screen will open in view-only mode.
Recount Stock Count	Handheld		Stock Counts		With this permission, the Stock Re-Count menu option on the Stock Counting menu is displayed. Without this permission, the menu option is not displayed.
Rejected Item Stock Count	PC		Stock Counts		With this permission, the Rejected Items button on the Child Stock Count List screen is displayed and enabled. Without this permission, the button is not displayed.
Save Child Stock Count	PC		Stock Counts		With this permission, the Save Child button on the Stock Count Authorization screen is displayed and enabled. Without this permission, the button is not displayed.
Snapshot Stock Count	PC		Stock Counts		With this permission, the Take Snapshot button on the Child Stock Count List screen, the Stock Count Detail and the Stock Re-Count Detail screens is displayed and enabled. Without this permission, the button is not displayed.
Update Authorization Quantity Stock Count	PC		Stock Counts		With this permission, the Update Auth Qty button on the Child Stock Count List and the Stock Count Authorization Screens is displayed and enabled. Without this permission, the button is not displayed.
Access Store Order	PC		Store Orders		With this permission, the Store Orders button on the Inventory Management screen is displayed and enabled. Without this permission, the button is not displayed.
Add Item Store Order	PC		Store Orders		With this permission and the Edit Store Orders permission, the Add Item button on the Store Order Detail screen is displayed and enabled when editing an existing Store Order. Without this permission, the button is not displayed. The Add Item button will always be available when creating a Store Order.
Approve Store Order	PC		Store Orders		With this permission, the Approve button on the Store Order Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Cancel Item Store Order	PC		Store Orders		With this permission, the Remove Item button on the Store Order Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Cancel Store Order	PC		Store Orders		With this permission, the Delete button on the Store Orders screen is displayed and enabled. Without this permission, the button is not displayed.
Create Store Order	PC		Store Orders		With this permission, the Create button on the Store Orders screen is displayed and enabled. The Add Item button the Store Order Detail screen will also be enabled. Without this permission, the button is not displayed.
Edit Store Order	PC		Store Orders		With this permission, when the user double-clicks on an existing Store Order in the Store Orders screen, the Store Detail screen will open in edit mode. Without this permission, the Store Order Detail screen will open in view-only mode.
Access Templates	PC		Templates		With this permission, the Template button on the Inventory Adjustment List screen is displayed and enabled. Without this permission, the button is not displayed.
Apply Templates	Handheld		Templates		With this permission, the Apply Template menu option on the Inventory Adj. menu is displayed. Without this permission, the menu option is not displayed.
Apply Templates	Mobile		Templates		User must have this permission for the Template option to be enabled when creating a new inventory adjustment. Without this permission, the user will only be able to create a new adjustment without a template.
Apply Templates	PC		Templates		With this permission, the Apply Template button on the Inventory Adjustment Detail screen is displayed and enabled. The template dropdown and multiplier is also enabled. Without this permission, the button is not displayed.
Delete Templates	PC		Templates		With this permission, the Delete button on the Template List screen is displayed and enabled. Without this permission, the button is not displayed.
Accept Request	Handheld		Transfers		With this permission, the Accept Request menu option on the Pick Summary screen is displayed. Without this permission, the menu option is not displayed.
Accept Transfer Request	PC		Transfers		With this permission, the Accept button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Accept Reject Request	Handheld		Transfers		With this permission, the Accept/Reject Tsf Request menu option on the Transfer menu is displayed. Without this permission, the menu option is not displayed.
Access Transfer	PC		Transfers		With this permission, the Transfers button on the Shipping/Receiving screen is displayed and enabled. Without this permission, the button is not displayed.
Access Transfer Context Field	Handheld		Transfers		With this permission, the Context Field menu option on the Request Summary screen is displayed. With this permission, the Enter Context Value is displayed when the Context Type is PROM. Without this permission, the menu option is not displayed.
Access Transfer Context Field	PC		Transfers		With this permission, the Context Type dropdown on the Transfer Detail screen is displayed and enabled. Without this permission, the dropdown is not enabled. With this permission and the Context Type selected is PROM, the Context Value field on the Transfer Detail screen is displayed and enabled. Without this permission, the field is not enabled.
Access Transfer Request	Handheld		Transfers		With this permission the Tsf Request menu option on the Shipping/Receiving menu is displayed. Without this permission the menu option is not displayed.
Add Item	PC		Transfers		With this permission, the Add Item button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Add or Edit Item	Handheld		Transfers		With this permission, the Add/Edit Item menu option on the Request Summary screen is displayed. Without this permission, the menu option is not displayed.
Approve Transfer	PC		Transfers		With this permission, the Approve button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Close Transfer	PC		Transfers		With this permission, the Close Transfer button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create Transfer	PC		Transfers		With this permission, the Create Transfer button on the Transfer List screen is displayed and enabled. The Add Item button on the Transfer Detail screen will also be enabled. Without this permission, the buttons are not displayed.
Create Transfer Request	Handheld		Transfers		With this permission the Create Tsf Request menu option on the Transfer menu is displayed. Without this permission the menu option is not displayed.
Create Transfer Request	PC		Transfers		With this permission, the Create Request button on the Transfer List screen is displayed and enabled. The Add Item button on the Transfer Detail screen will also be enabled. Without this permission, the buttons are not displayed.
Delete Transfer	PC		Transfers		With this permission, the Delete button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Transfer Request	Handheld		Transfers		With this permission, the Delete Request menu option on the Request Summary screen is displayed. Without this permission, the menu option is not displayed.
Edit Transfer	PC		Transfers		With this permission, when the user double-clicks on an existing Transfer in the Transfer List screen, the Transfer Detail screen will open in edit mode. Without this permission, the Transfer Detail screen will open in view-only mode.
Edit Transfer Request	Handheld		Transfers		With this permission, the Edit Tsf Request menu option on the Transfer menu is displayed. Without this permission, the menu option is not displayed.
Edit Transfer Requests	PC		Transfers		With this permission, when the user double-clicks on an existing Transfer Request in the Transfer List screen, the Transfer Detail screen will open in edit mode. Without this permission, the Transfer Detail screen will open in view-only mode.
Is Context Field Editable	Handheld		Transfers		With this permission, the Context Field menu options on the Request Summary menu are displayed and enabled. Without this permission, the menu is not displayed. With this permission and the Context Type selected is PROM, the user is prompted for the Context Value. Without this permission, the user is not prompted.
Reject Request	Handheld		Transfers		With this permission, the Reject Request menu option the Pick Summary screen is displayed. Without this permission, the menu option is not displayed.
Reject Transfer Request	PC		Transfers		With this permission, the Reject button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Request Transfer	Handheld		Transfers		With this permission, the Request Now menu option on the Request Summary screen is displayed. Without this permission, the menu option is not displayed.
Request Transfer	PC		Transfers		With this permission, the Request button on the Transfer Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Review Item	Handheld		Transfers		With this permission, the Review Item menu option on the Request Summary screen is displayed. Without this permission, the menu option is not displayed.
View Details	Handheld		Transfers		With this permission, the View Details menu option on the Request Summary screen is displayed. Without this permission the menu option is not displayed. Without this permission, the menu option is not displayed.
Access Additional Container Details	Handheld		Transfer Shipment		With this permission, the Additional Details menu option on the Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Additional Shipment Details	Handheld		Transfer Shipment		With this permission, the Additional Details menu option on the Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Access Container Attribute	Handheld		Transfer Shipment		With this permission, the Add Ext Attribute menu option on the Container Summary menu is displayed. Without this permission, the menu option is not displayed.
Access Container Attribute	PC		Transfer Shipment		With this permission, the Ext. Attributes button on the Transfer Shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Shipment	Handheld		Transfer Shipment		With this permission, the Transfer Shipment menu option on the Shipping/Receiving menu is displayed. Without this permission, the menu option is not displayed.
Access Shipment	PC		Transfer Shipment		With this permission, the Transfer Shipment button on the Shipping/Receiving is displayed and enabled. Without this permission, the button is not displayed.
Add Item with No Document	Handheld		Transfer Shipment		With this permission, the No Document menu option on the Document Selection menu is displayed. Without this permission, the menu option is not displayed.
Add Item with No Document	PC		Transfer Shipment		With this permission, the No Document button on the Transfer Selection screen is displayed and enabled. Without this permission, the button is not enabled.
Add Item to Container	PC		Transfer Shipment		With this permission, the Add Item and Remove Item buttons on the Transfer Shipment Container Detail screen are displayed and enabled. Without this permission, the button are not displayed.
Add or Edit Items in Container	Handheld		Transfer Shipment		With this permission, the Add/Edit Item or Remove Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Adjust Container	Handheld		Transfer Shipment		With this permission, the Adjust menu option on the Container Summary menu is displayed. Without this permission, the menu option is not displayed.
Adjust Container	PC		Transfer Shipment		With this permission, the Adjust button on the Transfer Shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Cancel Submit Shipment	Handheld		Transfer Shipment		With this permission, the Cancel Submit menu option on the Shipment Summary screen is displayed. Without this permission, the menu option is not displayed.
Cancel Submit Shipment	PC		Transfer Shipment		With this permission, the Cancel Submit button on the Transfer Shipment Detail screen are displayed and enabled. Without this permission, the buttons are not displayed.
Confirm Container	Handheld		Transfer Shipment		With this permission, the Confirm Container menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Confirm Container	PC		Transfer Shipment		With this permission, the Confirm button on the Transfer Shipment Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create Shipment	Handheld		Transfer Shipment		With this permission, the Create Shipment menu option on the Shipment Menu is displayed. Without this permission, the menu option is not displayed.
Create Shipment	PC		Transfer Shipment		With this permission, the Create button on the Transfer Shipment List screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Shipment	Handheld		Transfer Shipment		With this permission, the Delete Shipment menu option on the Shipment Summary menu, the Delete Container on the Container Summary menu on the Container Detail menu is displayed. Without this permission the menu options are not displayed.
Delete Shipment	PC		Transfer Shipment		With this permission, the Delete button on the Transfer Shipment Detail and the Delete button on the Transfer Shipment Container Detail screen are displayed and enabled. Without this permission, the buttons are not displayed.
Dispatch Shipment	Handheld		Transfer Shipment		With this permission, the Dispatch menu option on the Shipment Summary menu is displayed. Without this permission, the menu option is not displayed.
Dispatch Shipment	PC		Transfer Shipment		With this permission, the Dispatch button on the Transfer Shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Edit Container	Handheld		Transfer Shipment		With this permission, the Edit Container menu option on the Shipment Summary menu is displayed. Without this permission, the menu option is not displayed.
Edit Container	PC		Transfer Shipment		With this permission, when the user double-clicks on an existing Container in the Transfer Shipment Detail screen and the container is in an editable state, the Transfer Shipment Container Detail screen will open in edit mode. Without this permission, the Transfer Shipment Container Detail screen will open in view-only mode.
Edit Container Attribute	PC		Transfer Shipment		With this permission, the Apply, Add, Remove and Cancel buttons on the Extended Attributes Entry screen are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Container Info	PC		Transfer Shipment		With this permission, when the user clicks the Info button on the Transfer Shipment Container Detail screen, the Container Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit Shipment	Handheld		Transfer Shipment		With this permission, the Edit Shipment menu option on the Shipment menu is displayed. Without this permission the menu option is not displayed.
Edit Shipment	PC		Transfer Shipment		With this permission, when the user double-clicks on an existing Shipment in the Transfer Shipment List screen and the shipment is in an editable state, the Transfer Shipment Detail screen will open in edit mode. Without this permission, the Transfer Shipment Detail screen will open in view-only mode.
Edit Shipment BOL	PC		Transfer Shipment		With this permission, the Save button on the BOL Detail screen is displayed and enabled. Additionally, the screen opens in edit mode. Without this permission, the screen is view only.
Edit Shipment Info	PC		Transfer Shipment		With this permission, when the user clicks the Info button on the Transfer Shipment Detail screen, the Shipment Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Review Item	Handheld		Transfer Shipment		With this permission, the Review Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Select Container Document	Handheld		Transfer Shipment		With this permission, the user can toggle to access the Select Document screen from the Scan Item screen. Without this permission, the toggle option is not displayed.
Select Container Document	PC		Transfer Shipment		With this permission, when the user clicks the Document button on the Transfer Shipment Container Detail screen, the Document Selection screen is displayed and enabled. Without this permission, the button is not displayed.
Submit Shipment	Handheld		Transfer Shipment		With this permission, the Submit menu option on the Shipment Summary menu is displayed. Without this permission, the menu option is not displayed.
Submit Shipment	PC		Transfer Shipment		With this permission, the Submit button on the Transfer Shipment Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Access Additional Container Details	Handheld		Transfer Receiving		With this permission, the Additional Details menu option on the Container Summary screen is displayed. Without this permission, the menu option will not display.
Access Additional Receipt Details	Handheld		Transfer Receiving		With this permission, the Additional Details menu option on the Receipt Summary screen is displayed. Without this permission, the menu option will not display.
Access Quick Receiving	Handheld		Transfer Receiving		With this permission the Quick Receiving menu option on the Shipping/Receiving menu is displayed. Without this permission the menu option is not displayed.
Access Transfer Receiving	Handheld		Transfer Receiving		With this permission, the Transfer Receiving menu option on the Shipping/Receiving screen is displayed. Without this permission, the menu option is not displayed.
Access Transfer Receiving	PC		Transfer Receiving		With this permission, the Transfer Receiving button on the Shipping/Receiving is displayed and enabled. Without this permission, the button is not displayed.
Access Transfer Receiving Attribute	Handheld		Transfer Receiving		With this permission and the system parameter Enable Extended Attributes is set to Yes, the Add Ext Attrib menu option on the Container Summary screen is displayed. Without this permission, the menu option does not display.
Access Transfer Receiving Attribute	PC		Transfer Receiving		With this permission and the system parameter Enable Extended Attributes is set to Yes, the Ext Attributes button is displayed and enabled. Without this permission, the button is not displayed.
Add Container	Handheld		Transfer Receiving		With this permission, the Add Container menu option on the Receipt Summary Menu is displayed. Without this permission, the menu option is not displayed.
Add Unexpected Item	PC		Transfer Receiving		With this permission, the Add/Scan Item button on the Transfer Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Add Unexpected Item	Handheld		Transfer Receiving		With this permission, the user is allowed to add an unexpected item to a receipt. The system will prompt the user to confirm. Without this permission, the user is not allowed to add the item. The system will prompt the user, the item is unexpected and cannot be received.
Adjust Container	Handheld		Transfer Receiving		With this permission and the container status is ‘Received’, the Adjust menu option on the Container Summary menu is displayed. Without this permission, the menu option is not displayed.
Adjust Container	PC		Transfer Receiving		With this permission and the container status is ‘Received’, the Adjust button on the Transfer Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Container	Handheld		Transfer Receiving		With this permission, the Confirm menu option on the Container Summary screen is displayed. Without this permission the menu option is not displayed.
Confirm Container	PC		Transfer Receiving		With this permission, the Confirm button on the Transfer Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Confirm Receipt	Handheld		Transfer Receiving		With this permission, the Confirm Receipt menu option on the Receipt Summary screen is displayed. Without this permission the menu option is not displayed.
Confirm Receipt	PC		Transfer Receiving		With this permission, the Confirm button on the Transfer Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Create Container	PC		Transfer Receiving		With this permission, the Create Container button on the Transfer Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Default Qty in All Containers	Handheld		Transfer Receiving		With this permission, the Default Qty menu option on the Receipt Summary menu is displayed. Without this permission, the menu option is not displayed.
Default Qty in All Containers	PC		Transfer Receiving		With this permission, the Default Qty button on the Transfer Receiving Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Default Qty in Container	Handheld		Transfer Receiving		With this permission, the Default Qty menu option on the Container Summary menu is displayed. Without this permission, the menu option is not displayed.
Default Qty in Container	PC		Transfer Receiving		With this permission, the Default Qty button on the Transfer Receiving Container Detail screen is displayed and enabled. Without this permission, the button is not displayed.
Delete Container	Handheld		Transfer Receiving		With this permission, the Delete Container menu option on the Container Summary is displayed. Without this permission, the menu option is not displayed.
Delete Container	PC		Transfer Receiving		With this permission, the Delete Container button on the Transfer Receiving Container Detail screen is displayed and enabled. Without this permission, the menu option is not displayed.
Display Expected Qty	PC		Transfer Receiving		With this permission, the expected quantity will display on the Transfer Receiving Container Detail screen. Without this permission, the expected quantity will not be displayed.
Display Expected Qty	Handheld		Transfer Receiving		With this permission, the expected quantity will display on the Item Receive screen. Without this permission, the expected quantity will not be displayed.
Edit Container	Handheld		Transfer Receiving		With this permission, the Edit Container menu option on the Receipt Summary menu is displayed. Without this permission, the menu option is not displayed.
Edit Container	PC		Transfer Receiving		With this permission, when the user double-clicks on an existing Transfer Container on the Transfer Receiving Detail screen, the Transfer Receiving Container Detail screen will open in edit mode. Without this permission, the Transfer Receiving Container Detail screen will open in view-only mode.
Edit Receipt	PC		Transfer Receiving		With this permission, when the user double-clicks on an existing Delivery on the Transfer Receiving List screen, the Transfer Receiving Detail screen will open in edit mode. Without this permission, the Transfer Receiving Detail screen will open in view-only mode.
Edit Receiving Info	PC		Transfer Receiving		With this permission, when the user clicks the Info button on the Transfer Receiving Detail screen, the Receiving Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Edit Transfer Receiving Attribute	PC		Transfer Receiving		With this permission and the system parameter ‘Enable Extended Attributes’ is set to Yes, the Apply, Add, Remove and Cancel buttons on the Extended Attributes Entry screen are displayed and enabled. Without this permission, the buttons are not displayed.
Edit Container Info	PC		Transfer Receiving		With this permission, when the user clicks the Info button on the Transfer Receiving Detail screen, the Container Info screen will open in edit mode. Without this permission, the screen will open in view-only mode.
Misdirected Container	Handheld		Transfer Receiving		With this permission, the Misdirected Container menu option on the Receipt summary menu is displayed. Without this permission, the menu option is not displayed.
Misdirected Container	PC		Transfer Receiving		With this permission, the Misdirected Container button on the Transfer Receiving Detail screen, is displayed and enabled. Without this permission, the button is not displayed.
Receive by Item	Handheld		Transfer Receiving		With this permission, the Receive by Item menu option on the Container Summary screen is displayed. Without this permission, the menu option is not displayed.
Receive On Shop Floor	Handheld		Transfer Receiving		With this permission, the Receive on Shop floor prompt on the Confirm screen is displayed. Without this permission, the prompt is not displayed.
Receive On Shop Floor	PC		Transfer Receiving		With this permission, the Receive on Shop Floor check box on the Transfer Receiving Container Info screen is displayed and enabled. Without this permission, the check box is disabled.
Record Receipt Damages	Handheld		Transfer Receiving		With this permission, the Damage by Item and Damage Remaining menu options on the Receipt Summary screen are displayed. Without this permission, the menu options are not displayed.
Record Receipt Damages	PC		Transfer Receiving		With this permission, the damaged field on the Transfer Receiving Container Detail screen and the damaged field, the dropdown includes ‘damage’ and the Damage All button on the UIN popup is displayed and enabled. Without this permission, the fields, selections and buttons are not available.
Access UIN Attribute	PC		UIN		With this permission, the UIN Attributes button on the Setup screen is displayed and enabled. Without this permission, the button is not displayed.
Access UIN Resolution	PC		UIN		With this permission, the UIN Resolution button on the Admin screen is displayed and enabled. Without this permission, the button is not displayed.
Create UIN AGSN Ticket	Handheld		UIN		With this permission, the New AGSN menu option on the Ticketing Options menu is displayed. Without this permission, the menu option is not displayed. Note: The Re-print AGSN Ticket is controlled by the Print Auto Generated SN permission.
Create UIN AGSN Ticket	PC		UIN		With this permission, the Auto-Generate SN box on the Item Ticket Detail screen is displayed and enabled. Without this permission, the check box is disabled.
Create UIN on the Fly	Handheld		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. Without this permission, the user will not be able to create a new UIN.
Create UIN on the Fly	PC		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. Without this permission, the user will not be able to create a new UIN.
Print UIN Auto Generate Serial Number	Handheld		UIN		With this permission and the Format Type is Auto Generate SN, the Re-print AGSN menu option on the Ticketing Select Options screen is displayed. Without this permission, the menu option is not displayed. Note: The New AGSN print option is controlled by the Create UIN AGSN Ticket permission.
Print UIN Auto Generated Serial Number	PC		UIN		With this permission and the UIN type is AGSN, the Print Ticket button on the UIN Detail screen is displayed and enabled. Without this permission, the button is not displayed. With this permission and the Format type is Auto Generate SN, the Print Tickets button on the Item Ticket List and Item Ticket Detail screens and the Select UIN and Remove UIN buttons on the Item Ticket Detail screen are displayed and enabled. Without this permission, the buttons are not displayed.
Resolve UIN Exceptions	PC		UIN		With this permission, the Resolve button on the UIN Resolution List screen is displayed and enabled. Without this permission, the button is not displayed.
Update UIN Status	PC		UIN		With this permission, the Update Status dropdown on the UIN History screen is displayed and enabled. Without this permission, the dropdown is not enabled.
View UIN Detail	Handheld		UIN		With this permission, the Serial Number menu option on the Item Lookup screen is displayed. Without this permission, the menu option is not displayed.
View UIN Detail	PC		UIN		With this permission, the UIN Detail button on the Item Lookup screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, the UIN Detail tab on the Item Lookup pop-up search screen is displayed and enabled. Without this permission the tab will be disabled.
View UIN History	PC		UIN		With this permission, the View History button on the UIN Resolution List screen is displayed and enabled. Without this permission, the button is not displayed. With this permission, the View History button on the UIN Detail screen is displayed and enabled. Without this permission, the button is not displayed.

Convention	Meaning
boldface	Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic	Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace	Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Mode of Deployment	Application Control	Process Control
Internal Authentication/ Authorization	SIM control	SIM: § User § Group § Role § Store § Password § Login
External Authentication/ Authorization	LDAP control	LDAP: § User § Group § Role § Store § Password § Login
External/Internal Authentication/ Authorization	LDAP + SIM	LDAP: § Password § Login § User § Group § Role § Store SIM: § Additional Roles

Group	User for?
SIMSecureUsers	Provided by internal authentication / MUST be setup when using LDAP authentication
Admin	Accessing configuration management functionality
Security Ops	Accessing user and security management functionality
MPS	Accessing MPS (staging table) admin functionality
Batch	For triggering batch clients
Integration	Accessing external integration end points (for example, RIB, POS, third-party manifest)
Server Ops	Internal server operations

Category	Table Name	Note
Foundation	ADDRESS	Seed warehouse, partner, and supplier addresses (store addresses are seeded as part of store data).
	BRAND
	DELIVERY_SLOT
	DIFFERENTIATOR
	DIFFERENTIATOR_TYPE
	ITEM
	ITEM_COMPONENT
	ITEM_HIERARCHY
	ITEM_IMAGE
	ITEM_TICKET_TYPE	Item ticket type. This table contains SIM system control data. The external seeded data are inserted into this table only if the same item ticket types are not part of the SIM pre-installed system data.
	ITEM_UDA
	PARTNER
	PARTNER_ITEM
	RELATED_ITEM_TYPE
	RELATED_ITEM
	STORE_TRANSFER_ZONE
	SUPPLIER
	SUPPLIER_ITEM
	SUPPLIER_ITEM_COUNTRY
	SUPPLIER_ITEM_COUNTRY_DIM
	SUPPLIER_ITEM_MANUFACTURE
	SUPPLIER_ITEM_UOM
	UDA
	UDA_LOV
	UIN_LABEL	UIN Label This table contains SIM system control data. The external seeded data are inserted into this table only if the same item ticket types are not part of the SIM pre-installed system data.
	UOM_CLASS
	UOM_CONVERSION
	WAREHOUSE
	WAREHOUSE_ITEM

Category	Table Name	Note
	ADDRESS	Seed store addresses (warehouse, supplier, and partner addresses are seeded as part of foundation data).
Store	CONFIG_STORE	CONFIG_STORE records are created for each store seeded into SIM by copying the default settings from CONFIG_STORE_DEFAULT table.
	ITEM_PRICE	The RMS item location selling unit retail price is seeded into SIM as initial regular item price.
	ITEM_PRICE_HISTORY	For each ITEM_PRICE record, a price record is inserted into ITEM_PRICE_HISTORY.
	REPORT_FORMAT	REPORT_FORMAT records are created for each store seeded into SIM by copying the default settings from REPORT_FORMAT_DEFAULT table.
	STORE
	STORE_ITEM
	STORE_ITEM_STOCK
	STORE_ITEM_STOCK_NONSELL
	STORE_SEQUENCE_AREA	For each store seeded into SIM, a default record is created for the store.
	STORE_UIN_ADMIN_ITEM

Component Name	Description
setup	Creates temporary objects, it also disable foreign key constraints, and generate a file which contains the snapshot of the disabled foreign key constraints file before data seeding process starts.
Export Foundation Data	Export base foundation data (non-store specific data) from RMS database.
Export Store Data	Export store specific data from RMS database. The process creates a store_list.dat file which contains each exported store. The export data file for each store data is contained in the folder which is named by store ID. See “Defining Store List“ section for details.
Import Foundation Data	Import inventory foundation data from export data file into SIM inventory foundation table. See Inventory Base Data – Foundation Data table for target tables.
Import Store Data	Import inventory store data from export data file into SIM inventory store table. See Inventory Base Data – Foundation Data table for target tables. See ““Defining Store List“ section for details.
cleanup	Remove temporary objects, enable constraints.

Attribute Name	Mandatory	Description
roleName	Yes	Role Name. Syntax: String.
Type	No	Type of a Role – Store or Corporate. Syntax: String.
Description	No	Description of a Role. Syntax: String.

Sending Store		Receiving Store
Beginning SOH	1000 SOH	1000 SOH, 0 In Transit
Sent quantity 50	950 SOH	1000 SOH, 50 In Transit
Received quantity 30 (shortage)	970 SOH	1030 SOH, 0 In Transit

UPC-A Number	Equivalent UPC-E	Notes
0ab00000cdeX	abcde0X	Manufacturer code must have two leading digits with three trailing zeros and the item number is limited to three digits (000 to 999).
0ab10000cdeX	abcde1X	Manufacturer code must have three leading digits ending with 1 and two trailing zeros. The item number is limited to three digits.
0ab20000cdeX	abcde2X	Manufacturer code must have three leading digits ending with 2 and two trailing zeros. The item number is limited to three digits.
0abc00000deX	abcde3X	Manufacturer code must have three leading digits and two trailing zeros. The item number is limited to two digits (00 to 99).
0abcd00000eX	abcde4X	Manufacturer code must have four leading digits with one trailing zero and the item number is limited to one digit (0 to 9).
0abcde00005X 0abcde00006X 0abcde00007X 0abcde00008X 0abcde00009X	abcde5X abcde6X abcde7X abcde8X abcde9X	Manufacturer code has all five digits. The item number is limited to a single digit consisting of either 5, 6, 7, 8 or 9.

Access to Oracle Support

Enterprise Integration Guide (Located in the Oracle Retail Integration Suite Library on the Oracle Technology Network)

Technical Overview

User

UserPassword

UserRole

UserStore

Permission

PermissionGroup

PermissionSet

Role

RoleType

Group

UserGroup

Updating Reason Codes

Replenishment Calculation Summary

Future Stock Counts

Unscheduled Counts – Ad Hoc Stock Counts

Scheduled Stock Counts

Third Party Stock Counts

Unguided Stock Counts

Guided Stock Counts

Unit-Only Stock Counts

Unit and Amount Stock Counts

Stock Counts UIN Tracking

Problem Line Stock Counts

RTV UIN Tracking

Item Image URLs

Ticketing UIN Support

AGSN Auto-Ticket Printing

UIN Statuses

Unconfirmed

In Stock

In Receiving

Sold

Reserved For Shipping

Shipped To Store

Shipped To Warehouse

Shipped To Vendor

Shipped To Finisher

Removed From Inventory

Missing

Unavailable

Customer Reserved

Customer Fulfilled

Examples of Resolving Discrepancies

Example 1 – Store Mismatch: Allow Unexpected UINs parameter is Set to Yes

Example 2 – Store Mismatch: Allow Unexpected UINs Parameter is Set to No

Example 3 – Resolution List Screen: Customer Order Web Service

Example 4 – Update UIN Status Web Service Processing ACTION = SALE or VOID-RETURN