This page applies to the legacy version of Stand Sheets released prior to Volante 7: build 1766.

See Stand Sheets for details on Stand Sheets available in build 1766+.

Overview

Concession stands cashiers traditionally fill in an inventory sheet to

Use Cases

Cashier

Stand sheet setup for 200 terminal stadium

Restaurant Scenerio

Specifications

Setup

See setup and configuration options here

Usage

See how to use the inventory system here.

Design

Overview

Each terminal group shares same inventory
Inventory data is pulled from the server DB. Before server information is pulled, each terminal use a RMI cache for up-to-date information

DB Tables

SSINV_TERMINAL_GROUP (Table)

Terminal groups are a set of terminals grouped together. Each terminal group will share same inventory, and that means they shares same stand sheet item count.

SSINV_ENTRY (Table)

Inventory entry includes all inventory operations, which includes following transaction types

Purchase Received, External Purchase, Transfer In, Transfer Out, Wastage, Manual Adjust, Sale, Return, Physical Count Start, Physical Count Finish

Each operation will create an inventory entry into the database. If an operation is for more than 1 item, entries will be created for each item.

SSINV_COUNT (Table)

Inventory count contains current item count for each item. This table is not historical, which means it only holds current count. To look for historical information, SSINV_ENTRY table need to be referenced. Each new row in SSINV_ENTRY table will trigger this table to update (from db trigger level)

SSINV_SYNC_STATUS (Table)

This table contains information about last sync time for each terminal. This table is used to see if terminal needs to update information from the server database

SSINV_SHEET (Table)

Inventory sheet is stored in this table. Each inventory sheet is final and once it is closed, any number in the sheet will not changed. Counts on sheet is independent from SSINV_COUNT and SSINV_ENTRY once it is closed. This is to simulate physical stand sheet sheet, once it's filled out, it cannot be modified.

Core Operations

Open Stand Sheet

Assumptions:

Server connection is available
There is no currently open sheet

Starting class: chezTesoro.posMain.posGUI2.ssInv.button.OpenSheetB

What happens:

User enters starting count - expected starting count is based on current item count from SSINV_COUNT table
If there is a discrepancy, create adjusting entry with discrepancy. Otherwise, adjusting entry has quantity of 0
Put inventory entry into Local DB, Server DB, and send RMI message to same terminal group
Insert new SSINV_SHEET rows to Server DB
Update EMPLOYEE_SHIFT table and associate new sheet with the shift
Refresh GUI information

Close Stand Sheet

Assumptions:

Server connection is available
There is a open sheet

Starting class: chezTesoro.posMain.posGUI2.ssInv.button.CloseSheetB

What happens:

User enters finish count - expected finish count is calculated based on start count + all other recorded inventory entries
If there is a discrepancy, create adjusting entry with discrepancy. Otherwise, adjusting entry has quantity of 0
Put inventory entry into Local DB, Server DB, and send RMI message to same terminal group
Update SSINV_SHEET rows to Server DB
Update all SSINV_ENTRY entries from enteredTime to closedTime with closed sheet id - This is because for sale entries doesn't have sheet id since acquiring sheet id requires server database
Refresh GUI information

Sale/Return Inventory Item

Assumptions:

Inventory counter only works for inventory items

Starting class: chezTesoro.standSheetInv.SSInvCountUpdateManager

What happens:

Inventory entry will be created based on this item is sale or return.
Created inventory entry will be inserted to local db only
Send RMI message to terminals in same terminal group
KioskQuickMenuTableRenderer.setValue() has logic to show menu item counts on the screen

Create New Inventory Entry

Assumptions:

Server connection is available
There is an open sheet (Exception: if they don't use stand sheet module, they can create entry without an open sheet)

Starting class: chezTesoro.posMain.posGUI2.ssInv.button.InvNewEntryB

What happens:

User enters transaction type and quantity
For quantity, only positive values are accepted except for manual adjust which can take negative numbers as well
Put inventory entry into Local DB, Server DB, and send RMI message to same terminal group
For new entries, sheet id is recorded as currently open sheet id. This is recorded as -1 if there is no open sheet id (only happens with stand sheet module disabled)

Send Transfer

Assumptions:

Server connection is available
There is a open sheet

Starting class: chezTesoro.posMain.posGUI2.ssInv.button.TransferOutB

What happens:

User selects a destination terminal group
User selects item to send, with quantities - only items that exists on both terminal groups are showing on the list
New Inventory entries are created. Destination terminal group id is recorded as note. (ex. "TO:123123")
All entries will have referenceId, which is an id of first inventory entry. This is to mark different sets of transfers
Entries are saved on local DB, server DB and sent as RMI message

Receive Transfer

Assumptions:

Server connection is available
There is a open sheet

Starting class: chezTesoro.posMain.posGUI2.ssInv.button.TransferInB

What happens:

All transfers with current term group as destination is searched through server database.
User selects a transfer from available list
User confirms quantities from transfer out. If there was a discrepancy, it will automatically create manual adjust entries, with referenceId points to entry id of transfer in entry.
Transfer out entries are marked as "RCVD", on the notes field

Update Count Thread

Assumptions:

Starting class: chezTesoro.standSheetInv.SSInvCountUpdateThread

What happens:

Thread repeats every 60 seconds
Thread will see if there is any change on current terminal group. To see this. we query the most recent lastSyncTime from SSINV_SYNC_STATUS table. If this timestamp is later than marked time, then pull the information from local DB
Go through RMI cache list, and if it is created before last sync time, then remove the cache
Refresh inventory count cache

Limitations

No recipe support

Inventory count per menu item basis only

No decimal point count

Replenish on void is store-wide. No per-item config

Other Notes

New Packages

Package Name	Description
chezTesoro.generalSetup.standSheetInvTermGroup	Terminal group handling classes for stand sheet
chezTesoro.menuSetup.ssinv	Classes for Back office menu setup stand sheet tab
chezTesoro.posMain.posGUI2.ssInv	Base package for ssInvStyleDialog. Contains code for POS stand sheet dialog
chezTesoro.posMain.posGUI2.ssInv.button	Implementation for buttons for POS stand sheet dialog
chezTesoro.posMain.posGUI2.ssInv.panel	Implementation for additional panels for POS stand sheet dialog
chezTesoro.posMain.posGUI2.ssInv.tableModel	Implementation for table models for POS stand sheet dialog
chezTesoro.reports2.reports.base.standSheetInv	Reports for stand sheet inventory
chezTesoro.standSheetInv	Database handlers and db table managers for SSINV_ENTRY, SSINV_COUNT, SSINV_SHEET, SSINV_SYNC_STATUS tables

Database Tables

Related Jira Issues

Contacts

Filter by label

There are no items with the selected labels at this time.

Third Party Docs and Relevant Files

Description	Dropbox Location	Dropbox Link

Overview

Use Cases

Cashier

Stand sheet setup for 200 terminal stadium

Restaurant Scenerio

Specifications

Setup

Usage

Design

Overview

DB Tables

Core Operations

Open Stand Sheet

Close Stand Sheet

Sale/Return Inventory Item

Create New Inventory Entry

Send Transfer

Receive Transfer

Update Count Thread

Limitations

Other Notes

New Packages

Related Articles

Filter by label

Third Party Docs and Relevant Files

Browser not supported