Primary Author: Kris Lange

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Value-Added Reseller (VAR) Language

Oracle Retail VAR Applications

The following restrictions and provisions only apply to the programs referred to in this section and licensed to you. You acknowledge that the programs may contain third party software (VAR applications) licensed to Oracle. Depending upon your product and its version number, the VAR applications may include:

(i) the MicroStrategy Components developed and licensed by MicroStrategy Services Corporation (MicroStrategy) of McLean, Virginia to Oracle and imbedded in the MicroStrategy for Oracle Retail Data Warehouse and MicroStrategy for Oracle Retail Planning & Optimization applications.

(ii) the Wavelink component developed and licensed by Wavelink Corporation (Wavelink) of Kirkland, Washington, to Oracle and imbedded in Oracle Retail Mobile Store Inventory Management.

(iii) the software component known as Access Via™ licensed by Access Via of Seattle, Washington, and imbedded in Oracle Retail Signs and Oracle Retail Labels and Tags.

(iv) the software component known as Adobe Flex™ licensed by Adobe Systems Incorporated of San Jose, California, and imbedded in Oracle Retail Promotion Planning & Optimization application.

You acknowledge and confirm that Oracle grants you use of only the object code of the VAR Applications. Oracle will not deliver source code to the VAR Applications to you. Notwithstanding any other term or condition of the agreement and this ordering document, you shall not cause or permit alteration of any VAR Applications. For purposes of this section, "alteration" refers to all alterations, translations, upgrades, enhancements, customizations or modifications of all or any portion of the VAR Applications including all reconfigurations, reassembly or reverse assembly, re-engineering or reverse engineering and recompilations or reverse compilations of the VAR Applications or any derivatives of the VAR Applications. You acknowledge that it shall be a breach of the agreement to utilize the relationship, and/or confidential information of the VAR Applications for purposes of competitive discovery.

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

The VAR Applications contain trade secrets of Oracle and Oracle's licensors and Customer shall not attempt, cause, or permit the alteration, decompilation, reverse engineering, disassembly or other reduction of the VAR Applications to a human perceivable form. Oracle reserves the right to replace, with functional equivalent software, any of the VAR Applications in future releases of the applicable program.

Contents

Send Us Your Comments........................................................................................ vii

Preface...................................................................................................................... 1

Related Documents............................................................................................................................... 1

Customer Support................................................................................................................................. 1

Review Patch Documentation........................................................................................................... 1

Documentation Accessibility............................................................................................................. 1

Access to Oracle Support............................................................................................................ 2

Supplemental Documentation on My Oracle Support....................................................... 2

Improved Process for Oracle Retail Documentation Corrections........................................... 2

Oracle Retail Documentation on the Oracle Technology Network........................................ 3

Conventions............................................................................................................................................ 4

1 Mobile Store Inventory Management..................................................................... 5

2 General Workflow................................................................................................. 7

Options and Permissions................................................................................................................... 7

Multiple Users in SIM.......................................................................................................................... 7

Scan-Scan Functionality..................................................................................................................... 7

Scan-Scan UIN Functionality............................................................................................................ 8

Shortcut Keys.......................................................................................................................................... 8

Error Messages....................................................................................................................................... 9

Print Functionality................................................................................................................................ 9

Select an Item from a List.................................................................................................................... 9

3 Shipping/Receiving............................................................................................ 11

Direct Delivery..................................................................................................................................... 11

Process........................................................................................................................................... 11

Warehouse Receiving........................................................................................................................ 12

Store-to-Store Transfers and Transfer Requests......................................................................... 12

Returns................................................................................................................................................... 13

Warehouse Quick Receiving........................................................................................................... 13

4 Inventory Management........................................................................................ 15

Inventory Adjustments...................................................................................................................... 15

Stock Counts......................................................................................................................................... 15

Guided Counts............................................................................................................................ 15

Unguided Counts....................................................................................................................... 16

Count Process.............................................................................................................................. 16

Item Requests....................................................................................................................................... 17

Sequencing............................................................................................................................................ 18

Shelf Replenishment.......................................................................................................................... 18

Create Pick List............................................................................................................................ 18

Action Pick List........................................................................................................................... 18

Shelf Adjustment......................................................................................................................... 19

Item Basket............................................................................................................................................ 19

5 Customer Order Management............................................................................. 21

Customer Orders................................................................................................................................. 21

Customer Order Picking................................................................................................................... 21

Customer Order Deliveries............................................................................................................... 21

6 Lookups............................................................................................................. 23

Item Lookup.......................................................................................................................................... 23

Supplier Lookup................................................................................................................................. 24

Container Lookups............................................................................................................................. 24

7 Ticketing............................................................................................................. 25

Auto Print.............................................................................................................................................. 25

Manual Print........................................................................................................................................ 25

8 Session Printer................................................................................................... 27

Session Printer..................................................................................................................................... 27

Preface

The Oracle Retail Store Inventory Management Implementation Guide, Volume 3 – Mobile Store Inventory Management provides detailed information about using the Store Inventory Management handheld utility to perform SIM functions.

Customer Support

To contact Oracle Customer Support, access My Oracle Support at the following URL:

https://support.oracle.com

When contacting Customer Support, please provide the following:

§ Product version and program/module name

§ Functional and technical description of the problem (include business impact)

§ Detailed step-by-step instructions to re-create

§ Exact error message received

§ Screen shots of each step you take

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

The following documents are available through My Oracle Support. Access My Oracle Support at the following URL:

http://support.oracle.com/

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

The Enterprise Integration Guide is an HTML document that summarizes Oracle Retail integration. This version of the Integration Guide is concerned with the two integration styles that implement messaging patterns: Asynchronous JMS Pub/Sub Fire-and-Forget and Web Service Request Response. The Enterprise Integration Guide addresses the Oracle Retail Integration Bus (RIB), a fully distributed integration infrastructure that uses Message Oriented Middleware (MOM) to integrate applications, and the Oracle Retail Service Backbone (RSB), a productization of a set of Web Services, ESBs and Security tools that standardize the deployment.

Supplemental Documentation on My Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Improved Process for Oracle Retail Documentation Corrections

To more quickly address critical corrections to Oracle Retail documentation content, Oracle Retail documentation may be republished whenever a critical correction is needed. For critical corrections, the republication of an Oracle Retail document may at times not be attached to a numbered software release; instead, the Oracle Retail document will simply be replaced on the Oracle Technology Network Web site, or, in the case of Data Models, to the applicable My Oracle Support Documentation container where they reside.

This process will prevent delays in making critical corrections available to customers. For the customer, it means that before you begin installation, you must verify that you have the most recent version of the Oracle Retail documentation set. Oracle Retail documentation is available on the Oracle Technology Network at the following URL:

http://www.oracle.com/technetwork/documentation/oracle-retail-100266.html

An updated version of the applicable Oracle Retail document is indicated by Oracle part number, as well as print date (month and year). An updated version uses the same part number, with a higher-numbered suffix. For example, part number E123456-02 is an updated version of a document with part number E123456-01.

If a more recent version of a document is available, that version supersedes all previous versions.

Oracle Retail Documentation on the Oracle Technology Network

Documentation is packaged with each Oracle Retail product release. Oracle Retail product documentation is also available on the following Web site:

http://www.oracle.com/technetwork/documentation/oracle-retail-100266.html

(Data Model documents are not available through Oracle Technology Network. These documents are packaged with released code, or you can obtain them through My Oracle Support.)

Documentation should be available on this Web site within a month after a product release.

Conventions

The following text conventions are used in this document:

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.

General Workflow

This chapter describes the general workflow.

Options and Permissions

Not all functions described in this document might be available to you. Whether a function is available might depend on your security permissions or the system and store options used.

Multiple Users in SIM

SIM contains activity-locking functionality. This allows one user to update a transaction at a time. Depending on the functional area, if another user is processing a transaction that you want to initiate, you might receive a prompt to take over the transaction. If you take over the transaction, the original user receives a message when they try to save the transaction that they no longer have the lock. This is to ensure that only the user who currently owns the lock on the transaction can update the transaction.

Only two dialogues support multi-user processing:

§ Stock Counts can be configured to allow multiple users to scan for the same transaction on the handheld. The PC and the handheld are mutually exclusive, so the PC can lock out multiple users in this dialogue.

§ Warehouse Quick Receiving allows multiple users to scan containers for the same Advanced Shipment Notice (ASN). However, the detailed Warehouse Receiving dialogue allows only a single user to use the transaction.

Scan-Scan Functionality

Scan-Scan functionality in SIM is a term that describes the ability to scan the same item multiple times and incrementally increase the quantity of the item for each scan.

The following dialogues allow scan-scan functionality in certain modes:

§ Receive a direct delivery

§ Receive shipments at the case level (by item) from a warehouse

§ Create a transfer

§ Receive a transfer

§ Create a return

§ Transfer requests

§ Enter stock count details (unguided)

§ Item requests

§ Inventory adjustments

§ Customer Order Deliveries

Scan-Scan UIN Functionality

The user can scan a Unique Identification Number (UIN) that is associated with a different item without being forced to exit the Scan <UIN Label> screen.

The user will not need to select Done to exit the UIN screen before being able to add a UIN of another item.

For example:

A stock count is created for the following items:

§ Item A -- UIN 123

§ Item B -- UIN 124

The user scans UIN 123.

The Scan <UIN Label> screen is displayed showing that one quantity was assigned to item A.

The user scans UIN 124.

A screen is displayed showing that one quantity was added to item B.

Note: It will work similar to non-UIN items for unguided counts where the users can scan-scan without being interrupted.

Shortcut Keys

The following table describes shortcut keys for the SIM handheld:

Key	Description
Esc or Clear	Returns you to the previous window without saving any information. SIM allows you to use Esc or Clear only where appropriate. If the handheld has a Clear key, use Clear. If the handheld does not have a Clear key, use Esc.
Enter	Submits the information to SIM.
@ (Shift-2)	Toggles the unit of measure between cases and the standard unit of measure. Toggles in DSD between item and PO. Toggles in Customer Order Picking between Bin and Customer Order.
( (Shift-9)	There is additional information that you can view. You can also press the <next> key.
& (Shift-7)	Returns you to the previous window if you used <next> to view additional information. You can also press the <prev> key.
* (Shift-8)	Brings you to a Summary window. You can also press the <total> key.
! (Shift-1)	Search for information.

Note: Handheld devices might have different buttons used to send these characters.

Depending on the dialogue, only certain shortcut keys are available.

Error Messages

If you scan information with the handheld that SIM does not recognize, you receive an Invalid message. To continue, press Enter and scan the next item.

If you enter an alphanumeric or negative quantity or value on the handheld, you receive an Invalid message. To continue, press Enter and enter the correct quantity.

Note: The handheld emits a double-beep in case of errors, notifying the user something is wrong.

Print Functionality

It is possible to set up default reports on the PC client, which are printed on the handheld. Many transactions are enabled to print these default reports to their respective default printers when the transaction is completed.

It is not possible to re-print default reports from the handheld.

Select an Item from a List

All list objects are given a corresponding number that you must enter to select that object. For example:

1–1000 Minneapolis

2–1012 St Paul

3–1007 Eden Prairie

To select Eden Prairie from the list, press 3.

Shipping/Receiving

This chapter describes shipping and receiving.

Direct Delivery

The handheld allows for the receiving of merchandise from a supplier with a purchase order written for shipment directly to the store, or without an existing purchase order. SIM also allows receiving against purchase orders with Advanced Shipment Notices (ASN) and created through DEX/NEX.

The direct store delivery option enables a store user to identify a purchase order (PO) by scanning an item to be delivered or using the PO number. The system will verify the item is valid and display a list of valid suppliers of the item. Once the supplier is identified, the store user will select the PO that is associated to the selected supplier (or a new PO can be created for some suppliers). The store user will be prompted to enter any appropriate invoice information, including the invoice date.

Process

The process begins as the user scans all items to indicate they have been received, which can be done at item or case level. Unexpected items can be added to the order,this feature is configurable at a system administration level. Unit cost can be displayed for those items on the purchase order (configurable to display or not display). Once the delivery is complete, SIM will print a delivery notice, with all delivery details, for both the user and the driver. Simultaneously, SIM updates the store's on-hand inventory for the received items. The necessary information will be sent to the central merchandising and financial systems to create and close the purchase order and match against the upcoming invoice.

During the receiving process, the store user has the opportunity to record any damaged or missing items on the receipt. Substantial size delivery can saved with In Progress status to be completed later.

When the user confirms the delivery, the system performs the supplier attribute-based discrepancy checks. The supplier attribute values for the delivery exception are:

§ Allow any discrepancy

§ Allow overages but not short receipts

§ Do not allow any discrepancies

This value is a supplier attribute. It can be set up manually in SIM for a standalone environment. The user has an option to override the check based on the permissions. User also has a facility to directly receive goods on shop-floor.

Once the user has completed receipt of the entire direct delivery it will be moved to a Received status. At this point, changes to the delivery can no longer be made on the handheld.

As in most dialogues, it is possible to start the transaction on the handheld, save it and complete it on the PC. It is only possible to have a single user work on a given delivery.

UINs can be captured on the handheld if the item is set up to order.

For PO’s with an ASN applied, the user has an option to select Reject Delivery from the Direct Delivery summary screen to reject the entire delivery. This option is enabled if the user has enabled the permission for this option (see Appendix: SIM Permissions in Oracle Retail Store Inventory Management Implementation Guide, Volume 1 – Overview).

If the user chooses to reject the delivery, all the received quantity will be set to zero and the delivery will be confirmed. If the delivery is rejected, the user can view the information on the DSD, but cannot edit nor make any Receiver Unit Adjustment.

Warehouse Receiving

Two different dialogues are supported on the handheld to support warehouse deliveries. In either dialogue, the process starts by scanning a valid container ID.

The Warehouse Quick Receiving dialogue is used in SIM to enable a user to receive containers in a single-step process for a single ASN or across multiple ASNs. This method is especially effective when working with consolidators or large deliveries. This dialogue allows multiple users to receive containers, and SIM can be configured to allow auto-completion of the ASN when every container is received.

When scanning a container that is listed as missing from a confirmed ASN in Quick Warehouse Receiving on the handheld, SIM will receive the container instead of prompting the user with an error message. The receiving process follows the same logic as on the PC. The result of this operation is that the receipt is amended with the missing container now received and a message is sent on to RMS to bring both systems in sync. User can now receive the delivery directly at shop-floor.

The second dialogue is used in SIM to receive at three different levels, but in a more methodical fashion by first identifying a single ASN:

§ An entire ASN can be received without any detailed confirmation.

§ The user can identify each container individually and receive it.

§ The items in each container individually can be received.

Only a single user can work on the same ASN to prevent item entry discrepancies. After confirming the ASN receipt, it is not possible to make any adjustments through this dialogue. Adjustments will need to be made on the SIM PC client.

A system option exists to not allow additional items to be added to the delivery.

This dialogue allows a combination of container-level or item-level receiving. For example, a user could receive all undamaged containers, but can decide to detail receive any damaged containers at the item level.

Store-to-Store Transfers and Transfer Requests

Store-to-store transfers can be initiated and dispatched from the handheld. It is also possible to dispatch or edit transfers created on the PC or through external systems.

Transfer requests can be created, modified and deleted from the handheld, but it is not possible to approve them on the handheld. Approving a transfer request is considered an administrative function a manager performs on the PC.

Only a single user is able to work on a single transfer at one time. The intent is to keep transactions small so the user is assumed to work on a single shipment or delivery at one time.

Unlike warehouse deliveries or DSD delivery, for store-to-store transfers, the user is required to scan the serial number. This is regardless of the item being set up as an AGSN or serial number.

Returns

The Returns functionality enables the store user in SIM to create, edit, dispatch, and return from the store to a warehouse, finisher, or directly to the vendor.

The handheld does not allow the approval of return requests. Approving a return request is considered an administrative function a manager performs on the PC.

For Return to warehouse or finisher, the context type and value can be entered for the return, indicating the purpose of the return.

When creating or adding items to a return, SIM allows scan-scan functionality (see Scan-Scan Functionality). Similar to most transactions, to guarantee data integrity, only a single user is allowed in a single unique transaction at the time.

If the item is set up to handle UINs, the user must identify which specific serial number is returned to the warehouse, finisher, or vendor. UIN’s must be in the proper status to create the return.

Warehouse Quick Receiving

Quick Warehouse receiving functionality only exists on the handheld, and the system can be configured to turn this function off. Quick Warehouse receiving allows the user to just scan container after container in which they want to receive. The containers may or may not belong to the same ASN. This allows the user to scan each container as it comes off of the truck and then confirm and reconcile after all of the containers have been received.

After all containers associated with an ASN have been received, the ASN may automatically be marked as ‘Received’, this is based on a system setting. Once an ASN is marked to ‘received’, the stock on hand for all of the items on the received containers will be incremented and the receipt message will be published to the merchandising system. Note that if UIN items exist on the container, then the container will not be received and the normal detailed level warehouse receiving must be used (this is assuming that the UINs were not sent on the ASN).

This process allows for receipt of containers which are ‘New’, ‘In Progress’ or ‘Missing’ status. Containers can only go ‘missing’ when receiving via the regular warehouse receiving method on either PC or the handheld, when a delivery gets received and a container is not received, it is missing. Quick Warehouse Receiving allows for receipt of the ‘missing’ container, if the system is configured to allow for missing container receiving. Because ‘missing’ containers belong to already received deliveries, the system must also be configured to allow for receiver unit adjustments. This means the receipt of the ‘missing’ container must be within the system defined number of days in which adjusted deliveries are allowed.

Inventory Management

This chapter describes inventory management.

Inventory Adjustments

Inventory Adjustments allow users to move inventory out of the system, mark inventory as unavailable to sell, add inventory, or move inventory back from an unavailable state.

The handheld allows the user to identify the item and a reason code that will determine the disposition of the item.

If the item is set up to handle Unique Identification Numbers (UINs), the user must identify which specific serial number is adjusted. If the item is set up as an auto-generated serial number (AGSN) and the user tries to increase the SOH, then UINs are created when the user confirms the inventory adjustment.

Stock Counts

SIM provides the ability to schedule, perform, and authorize stock counts. 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 handheld.

The following types of stock counts can be counted on the handheld:

§ Ad hoc

§ Unit

§ Unit and Amount

§ Problem Line

There are three different stages a Stock Count goes through:

§ Stock Count

§ Stock Re-count (optional)

§ Authorize

Only the Stock Count and Stock Re-count stages apply to the handheld.

The handheld allows the user to count items through a guided or unguided count method that is determined during the product group setup on the PC.

Note: The final authorization of the stock count needs to be performed on the PC.

Guided Counts

Guided Stock counts (Unit, Unit and Amount, Problem Line) are divided so that each user of a handheld device performs a stock count according to a macro location (for example, vegetables, cereals). Guided stock counts will prompt the user to scan the next item in sequence. If sequencing is not set up for the items, the user will be prompted in item number order.

Unguided Counts

Unguided Stock Counts (Ad hoc, Unit, Problem Line, Unit and Amount) allow the user to scan items on the handheld without being prompted which item to scan. There is still an option to count an unguided count by macro location. The user might also choose to break down an unguided master count by hierarchy (dept/class/sub-class).

Unguided stock counts decrease the time it takes to completely scan a count and provides more flexibility. Multiple users are able to scan items for the same child stock count. This is controlled through a system option. The user will be alerted if they attempt to complete the count while other users are still in the count.

For unguided counts, the following menu options and functions exist:

§ Return to Count – takes the user back to the count and saves all changes but does not commit the changes.

§ Quick Save – changes are committed to the database and the user is returned to the count.

§ Save and Exit – changes are committed and the user is returned to the list of master stock counts.

§ Discard Changes – the user is prompted if they want to discard their changes.

§ Complete Count – changes are committed and the stock count is completed and moved to the next stage.

§ Items Left to Count – allows the user to scan through items that have not yet been counted and enter a count quantity for the item. This feature is not available for ad hoc counts.

The unguided process also allows for a review process that is typically performed by a manager as a final check before moving to the next stock count stage. The user will be prompted with the old count quantity and can manually enter a new count quantity to override the old quantity.

Count Process

In order to begin the initial count, the user selects the Stock Count option and accesses the master count from a list of stock counts. Once the master count is selected, the user will need to select a child count to begin the count process. The s option on the bottom of the screen enables the user to search for a specific child count. The user can search by the child barcode, child ID or child description. Only uncounted child counts are returned.

Note: If no master counts exist, the user will be alerted that no stock counts currently require any action.

When the user scans the item, SIM performs an item validation to ensure the item is valid and that it is on the count. Since ad hoc counts do not have a pre-defined list of items, any item can be scanned on an ad hoc count.

During the count stage, the user will scan the item and can enter the count quantity for each item on the count. Scanning the first item triggers the snapshot to be taken for Unit, Problem Line, and Ad hoc counts. For Unit and Amount counts, the user must trigger the snapshot from the PC; however, the count can still be started on the handheld. The count will not move to the next stage of the re-count until the snapshot has been taken. Once the last item is counted and the snapshot has been taken, the count will move to the next stage.

The re-count stage is optional and is determined during the Product Group setup on the PC. If the re-count discrepant items option is selected and discrepant items exist, a re-count will be required. The user will be able to enter a re-count quantity for each item on the count. Once the last item is counted, the stock count will move to the Authorize stage and will no longer be accessible on the handheld.

The user can amend the count or re-count at any time. If the user does not wish to complete the count in the current session, the count can be saved and completed at a different time on the handheld or the PC. Before completing the count, the user will be prompted if there are any uncounted items.

The user will be able to register any UINs that are required to be counted. Only those UINs that are associated and supposed to be in inventory can be added during the counting or re-counting phase.

Item Requests

The Item Request functionality gives the user the ability to request inventory for individual items using the replenishment and sourcing parameters of RMS from within SIM.

The Item Request functionality enables the user to request items regardless of the replenishment type normally used by the merchandising system to replenish the item.

From the handheld, the user can do the following:

1. The user can create, edit, delete or request an item request. Item request can be accessed either from PC or handheld.

Requests that were created automatically by the Product Group Scheduler can also be edited on the handheld.

2. When creating an item request, the user can specify a request delivery date or accept the default date of tomorrow.

Note: When entering a request delivery date, SIM allows the user to enter today's date or future date

3. After specifying the request delivery date, the user can select a default timeslot to specify what time of day the delivery occurs.

The timeslot option is only available if the Display Item Request Delivery Timeslot store parameter is set to allow it, and only applies to store order replenishment items. The timeslot option allows the retailer to have multiple deliveries per day for the same item.

4. The next step is to scan the barcode of the item being requested.
As each item is scanned, the user can view the stock on hand for the item and the number of items in transit. On this screen, the user has the option of changing the timeslot for the current item.

5. After all of the desired items have been added and quantities entered, the user has the ability to submit the request immediately or to save the request for later approval.

6. When the user finally submits the request, all items will be sourced from either a Warehouse or through Supplier Purchase Orders, depending on the sourcing parameters for the item specified in the merchandising system.

7. Once the user submits the item request, the request moves to Completed status and will no longer appear on the handheld but can be viewed on the PC.

Sequencing

Sequencing gives stores the ability to know the exact location of an item in a store. Sequencing a store will improve store processes and reduce massive amounts of time spent looking for items.

Sequencing is broken down into two parts: macro and micro. Macro sequencing sequences all locations that are set up in the store. The micro sequence is found within the macro sequence. Micro sequencing sequences all the items that are attached to the macro sequence location.

The handheld enables users to do the following:

§ Add items to a sequence

§ Remove items from a sequence

§ Re-organize the order of the sequence

For more information about using the handheld to perform a function, see the Scan-Scan Functionality.

Shelf Replenishment

Shelf Replenishment lists are created to move inventory from the backroom into the shop floor for in-store replenishment. This feature may or may not require sequencing to be turned on, depending upon the type of shelf replenishment selected. SIM needs to understand how much inventory is on the shop floor for a specific item as opposed to the back room, and how much capacity that item has on the shop floor if capacity is defined.

There are 4 type of shelf replenishment lists can be created and actioned from the handheld:

§ Capacity

§ Sales

§ Ad Hoc Replenish

§ Display List

Create Pick List

The handheld can be used to generate a list of items to pick for replenishment and the create pick list. The pick list may be created within the day and at end of day from shelf replenishment lists created on the PC. This flow resembles the customer order picking flow. The main exception is that bins are not available for shelf replenishment. The list will be sorted by item sequence if sequencing is setup. The list may also be configured to generate by case or standard unit of measure.

Action Pick List

When the user is ready to pull the inventory, they are able to action the previously created pick list from the shelf replenishment or shelf adjustment list.

The handheld provides the following functionality:

§ Action within the day and at end of day shelf replenishment lists created on the PC

§ Amend suggested quantities

§ Validate replenished items

§ Complete the shelf replenishment list

§ Substitute items when necessary

Shelf Adjustment

Shelf adjustment lists are created to move inventory from backroom to the shop-floor and from shop-floor to backroom; it also updates the current status stock of the shop-floor without physical movement of goods. Using of sequencing is not a mandate for this functionality. The user will also have the ability to reverse pick a shelf replenishment list within the shelf adjustment feature. There are 4 types of shelf adjustment list which are mentioned below:

§ Shop-floor Adjust

§ Backroom Adjust

§ Display List

§ Ad Hoc Replenish

Shop-floor Adjust: The purpose of this list is to allow the user to scan the items in the shopfloor and update the shopfloor quantity with the scanned item quantities. The shelf adjustment list can only be created on the handheld. After the creation of the list user clicks confirm to update the stock on shop-floor. Adjust the shopfloor will also adjust the backroom to ensure that the shopfloor+backroom is equal to the SOH.

Backroom Adjust: This is very similar to the shop-floor adjusted, except here the user scans the backroom and updates the backroom quantities. Adjusting the backroom will also automatically adjust the shop floor to ensure the SOH is always equal to shopfloor+backroom.

Display List: This list has as intent that the user scans the shopfloor display items. The list of scanned items will be compared on the PC or HH when generating a pick list . This list can only be created on the HH.

Ad Hoc Replenish: For ad Hoc replenishment, the user will scan gaps on the shelf. When the list is complete, the user can save it and have it execute don the PC or HH. This list can only be created on the HH.

Item Basket

SIM often has the only wireless network in the store. It is very expensive to run two applications with different protocols in the same store, especially with smaller retailers. Therefore, the SIM wireless device is very well suited to aid the retailer with line busting, investigative item lists or creating gift registries.

The handheld provides a new menu option that can capture items and their quantities by scanning the UPC.

When all items are captured, the handheld will present an option to print a ticket with a barcode for the customer or allow the customer to enter in their own ID. This barcode can be scanned or entered by a third-party system to retrieve the basket from SIM.

A purging process will delete all baskets after a 24-hour period.

After the user scans the barcode or enters the ID, a web service call can be made to SIM to retrieve the basket information.

Note: Item Basket supports only sellable items.

For more information about using the handheld to perform a function, see the Scan-Scan Functionality.

Lookups

This chapter describes lookups.

Item Lookup

The Item Lookup functionality provides the business user with the ability to view information related to an item:

§ Price information – The user can view current price, effective date, price type and, if applicable, multi-unit price information.

§ Internal Deliveries - View internal deliveries which are warehouse deliveries the store is expecting to receive from the warehouse or saved transfers to the user's store.

§ Inventory details – The user can view inventory details for current items such as stock on hand, on order, in transit, reserved inventory, inventory received in the store today, customer orders, and backroom/shop floor/delivery bay inventory.

§ Related items – Store users can quickly and easily determine what related items exist in the store by accessing the Related Items option. The user can lookup related items for the current item and view stock on hand information, differentiators, and so forth.

§ Item attributes – The user can view attributes for the current item such as standard unit of measure, pack size, whether or not the item is a pack item, a concession or consignment item, sellable, or non-sellable, and whether or not it is orderable.

§ Print item report – The user can print a report to view information about the item such as SKU, description, price, differentiators, and inventory position.

§ Price history – Provides the user with a list of price changes for the item, excluding promotional price changes.

§ Stock locator – The user can look up inventory for the current item at other stores and will also be able to determine if any of the store’s buddy stores have any inventory for the item.

§ Customer orders – The user can view any customer orders that exist for the current item.

§ Non-sell Sub-buckets - The user can view the sub-buckets that are associated to the nonsellable stock on hand. Non-sell Sub-buckets are only displayed if the system is configured to use sub-buckets

§ User-defined attributes –The user can view any UDAs that exist for an item.

Su pplier Lookup

The Supplier Lookup functionality provides users with the ability to view information about the supplier such as:

§ Supplier ID

§ Supplier name

§ Headquarters address, phone, contact, contact e-mail

§ Return address, phone, fax, contact e-mail

§ Other addresses for the supplier

§ Status

§ Return allowed

§ Return authorization required

§ Primary Supplier – The primary supplier details of the item are displayed. Any additional suppliers are displayed.

Container Lookups

The Container Lookup functionality provides users with the ability to view information about the container such as:

§ Container ID

§ Advanced Shipment Notice (ASN) number

§ Status (for example, received, in transit)

§ Receipt date and time

§ ETA

§ From location

§ Total number of cases

Ticketing

This chapter describes ticketing.

Auto Print

Ticket printing on the handheld is accessible from the Main Menu. There are two modes of printing tickets, auto print and manual print. The user is unable to generate tickets from various transactions or print ticket batches on the handheld. These functions can only be done on the PC.

In auto print mode, the user is able to print tickets quickly by defining format, printer, quantity and event before scanning the item. When the item is scanned SIM will determine if a ticket needs to be printed allowing the user to scan uninterrupted.

The auto print mode can be used for printing tickets for a price event in the past, future or current date. This allows the user to scan all items on a shelf, rack or other area and automatically print tickets only for the items going on sale, coming off a sale, etc. The user also has the option print a ticket for every item scanned with the price relevant for the day selected. The user may swap formats and/or printers by toggling to another screen at the point of any item scan.

§ Pre-defined Options:

– Define number of tickets

– Select price event or always print

– Effective date range

– Selecting Printer

– Selecting format type/name

§ Use Case – Reticketing items expiring at the end of the day

– A format ticket is created that takes the current price and divides it by 2. The ticket printed states: 50% off and generates a type 2 with embedded price.

– User scans items that are expiring with a fixed weight (e.g. Yogurt and milk),

– SIM prints a ticket barcode and puts it over the ticket on the package.

Manual Print

In manual print mode, the user is able set an override price, quantity, country of origin, format and printer for each scanned item depending on the need. This mode can be used to print a set quantity of tickets for each item scanned and to override a price currently on the item. This is typically used for quickly printing missing tickets for items. This process is also used when generating or reprinting UINs for AGSN tickets. The user may swap formats and/or printer by toggling to another screen at the point of any item scan.

§ Options:

– Price Override (controlled by security permissions)

– Define number of tickets

– Select printer

– Select format type/name

– Select country of manufacture

– Print new or re-print AGSNs (controlled by security permissions)

§ Use Case – Items are delivered on a DSD without a price

– User scans the item’s UPC

– User types in the number of units received

– SIM prints a specific number of tickets

– User quickly tags the received items and scans the next group of items.