You are on page 1of 270

NCR Back Office

Data Mart
Version 13.7

Data Mart Introduction i


Copyright
Copyright © 2012, NCR Corporation - All rights reserved. The information contained in this publication
is confidential and proprietary. No part of this document may be reproduced, disclosed to others,
transmitted, stored in a retrieval system, or translated into any language, in any form, by any means,
without written permission of NCR Corporation.
NCR Corporation is not responsible for any technical inaccuracies or typographical errors contained in
this publication. Changes are periodically made to the information herein; these changes will be
incorporated in new editions of this publication. Any reference to gender in this document is not meant
to be discriminatory. The software described in this document is provided under a license agreement.
The software may be used or copied only in accordance with the terms of that agreement

ii Data Mart
Table of Contents

Introduction .......................................................................................................................... 1

Is This Guide for You?............................................................................................................... 1


Audience ........................................................................................................................... 1
Summary .......................................................................................................................... 1

Entity Diagram ...................................................................................................................... 3

Public Tables ........................................................................................................................... 5


ST_Accruals ....................................................................................................................... 5
ST_AdjFoodCostByDay ........................................................................................................ 7
ST_AdjFoodCostByPartialPeriod ............................................................................................ 9
ST_AdjFoodCostByPeriod .................................................................................................... 11
ST_AdjFoodCostByWeek ..................................................................................................... 13
ST_Allocations .................................................................................................................. 15
ST_AlohaGndBreakInfo * .................................................................................................... 16
ST_AlohaSalesMixTransactions_RealTimeFeed * .................................................................... 21
ST_BOANETtoHQParameters ............................................................................................... 24
ST_Budgets ...................................................................................................................... 25
ST_Calendars.................................................................................................................... 26
ST_CalendarSubperiods * ................................................................................................... 27
ST_CostofGoods ................................................................................................................ 28
ST_CustomFPZ * ............................................................................................................... 30
ST_DataDefinitionConfiguration * ........................................................................................ 33
ST_Deposits ..................................................................................................................... 35
ST_EmpJobRates ............................................................................................................... 37
ST_EmpJobTrans ............................................................................................................... 39
ST_EmpJobTransCustom .................................................................................................... 42
ST_EmployeeClockPunchHistory_FromView * ........................................................................ 44
ST_EmployeePayrollDay ..................................................................................................... 48
ST_EmployeePayrollDayPenaltyHours * ................................................................................ 50
ST_EmployeePunches ........................................................................................................ 52
ST_EmployeePunchesRealTime * ......................................................................................... 54
ST_Employees .................................................................................................................. 57
ST_EmployeeSalesTips ....................................................................................................... 62
ST_EmployeeSalesTips_RealTimeFeed * ............................................................................... 64
ST_EmployeeStatusBySite_RealTimeFeed * .......................................................................... 68

Data Mart Table of Contents iii


ST_EmpTrans ................................................................................................................... 70
ST_EmpTransW4_I9 .......................................................................................................... 75
ST_EmpW4_I9 .................................................................................................................. 80
ST_ExcludedItemsBySite_FromView * .................................................................................. 85
ST_FoodCost .................................................................................................................... 86
ST_FoodCostByItem .......................................................................................................... 88
ST_FoodCostByItemContractDaily ....................................................................................... 91
ST_ForecastDailySalesAndGuests ........................................................................................ 93
ST_ForecastSalesGuestsByInterval_FromView * .................................................................... 94
ST_InactiveItemsBySite_FromView * ................................................................................... 96
ST_InventoryLists_RealTimeFeed * ..................................................................................... 97
ST_InventoryTransfer ........................................................................................................ 98
ST_InvoiceDetails ............................................................................................................ 100
ST_InvoiceDetailsSupplierReferenceNumber ....................................................................... 102
ST_InvoiceHeaders .......................................................................................................... 103
ST_ItemCategories * ....................................................................................................... 106
ST_ItemConversionFactors_RealTimeFeed * ....................................................................... 107
ST_ItemPropertiesBySite_FromView * ............................................................................... 108
ST_ItemRecipeIngredients_FromView * ............................................................................. 111
ST_ItemRecipeKitchenTools_FromView * ............................................................................ 114
ST_ItemRecipePlateAndStores_FromView * ........................................................................ 116
ST_ItemRecipePrepStations_FromView * ............................................................................ 118
ST_ItemRecipes_FromView * ............................................................................................ 120
ST_Items *..................................................................................................................... 126
ST_ItemUnitsOfMeasure * ................................................................................................ 129
ST_ItemUseDaily............................................................................................................. 130
ST_ItemUseVariance........................................................................................................ 133
ST_Jobs * ...................................................................................................................... 135
ST_KitchenTool_FromView * ............................................................................................. 137
ST_MIC .......................................................................................................................... 138
ST_OccasionCategoriesOccasions ...................................................................................... 140
ST_Occasions.................................................................................................................. 141
ST_PayrollStatus_FromView * ........................................................................................... 143
ST_PayrollStatusDetail_FromView * ................................................................................... 145
ST_PlateStore_FromView * ............................................................................................... 147
ST_PrepStations_FromView * ........................................................................................... 148
ST_POSSOS .................................................................................................................... 149
ST_PromosComps ........................................................................................................... 152
ST_Punches .................................................................................................................... 153
ST_PurchaseOrderItems ................................................................................................... 155
ST_PurchaseOrderItems_RealTimeFeed * ........................................................................... 157
ST_PurchaseOrders ......................................................................................................... 159

iv Table of Contents Data Mart


ST_PurchaseOrders_RealTimeFeed * ................................................................................. 162
ST_RawInfo .................................................................................................................... 165
ST_RecipeVersionBySite_FromView * ................................................................................. 168
ST_Register .................................................................................................................... 169
ST_RegisterByRevenueCenterDayPart ................................................................................ 173
ST_SafeCount * .............................................................................................................. 177
ST_SalesGuestsByInterval ................................................................................................ 181
ST_SalesMix ................................................................................................................... 183
ST_SalesMixByRawMaterial ............................................................................................... 184
ST_Schedule ................................................................................................................... 186
ST_ScheduleHours........................................................................................................... 188
ST_ScheduleIntervals ...................................................................................................... 190
ST_SchedulePayrollDay .................................................................................................... 191
ST_ScheduleRecommendedByDayLaborMatrices * ............................................................... 193
ST_ServerCheckout ......................................................................................................... 196
ST_SiteAndSiteGroupMemberships_RealTimeFeed * ............................................................ 201
ST_SiteEmployeeRateChangeAcknowledgments_FromView * ................................................ 202
ST_SiteInventoryListMembers_RealTimeFeed * ................................................................... 204
ST_SitePayroll................................................................................................................. 205
ST_Sites......................................................................................................................... 206
ST_SitesAndSiteGroups * ................................................................................................. 211
ST_SiteSubPeriod ............................................................................................................ 212
ST_TasksAndStations * .................................................................................................... 213
ST_TheoreticalCostOfGoodsByDate .................................................................................... 215
ST_TimeClockEditReason_FromView * ............................................................................... 216
ST_TipShareDistribution_RealTimeFeed * ........................................................................... 217
ST_TipShareEmployeeDistribution_RealTimeFeed * ............................................................. 220
ST_TipShareJobDistribution_RealTimeFeed * ...................................................................... 222
ST_UserGroupMemberships_RealTimeFeed * ...................................................................... 223
ST_UserGroups_RealTimeFeed * ....................................................................................... 224
ST_Users_RealTimeFeed *................................................................................................ 225
ST_VendorCustomFields ................................................................................................... 227
ST_VendorItems ............................................................................................................. 230
ST_Vendors .................................................................................................................... 232
ST_Vendors_FromView * .................................................................................................. 240
ST_Waste ....................................................................................................................... 243
ST_WasteByRawMaterial .................................................................................................. 245

Revision History ................................................................................................................ 247

Data Mart Table of Contents v


Notes:

vi Table of Contents Data Mart


Introduction

Is This Guide for You?


This guide provides you with descriptions and instructions on the NCR Back Office Data Mart.

Audience
This guide is aimed toward answering questions from different personnel within your company:
IT Personnel – This document contains an overview of the NCR Back Office Data Mart as well as best
practices during implementation.
Network Administrators − Includes questions & answers aimed toward network administrators.
Interface Developers− Includes data elements aimed toward software engineers engaged to develop
an interface with the NCR Back Office Data Mart.

Summary
The NCR Back Office Data Mart is a fully documented repository of your NCR Back Office data. The
repository contains “public tables” which are “protected”. The table/column names cannot change
from release to release (new columns/tables are added, but never dropped). The NCR Back Office
Data Mart is pre-processed information for easy data-mining. The data is transported to corporate via
SQL replication.

Data Mart Introduction 1


Notes:

2 Introduction Data Mart


Entity Diagram
Data Mart (v 13.7)

@Wastes

@SchedulePayrollDays

@EndDate @UserNumber
@Invoice
@StartDate @FoodCosts @StartDate
@strDataNumbers
@SalesMix
@Schedules @Punch @EndDate
@Deposit
@MICs

@ItemUseVariances
@strSites
@SalesMixWeekly @EmpJobTran Export_STCashierCheckout
@UserNumber

@Transfer
@RawInfos
@SalesGuestsByHalfHours
@EmployeePayrollDays
@strSites

@ItemUseDailys @CostofGood
Export_ProcessSTCashierCheckout.sql
@EmployeePunch

@ScheduleInterval

@ScheduleHour

@FoodCostByItems
Export_STSummary ST_ServerCheckout
PK SiteNumber
PK EmployeeNumber
PK Shift
PK SalesDate
PK Register

StoreID
EmployeeID
Export_ProcessSTEmployees.sql Export_ProcessSTPunches.sql Export_ProcessSTSchedule.sql Export_STItems.sql Export_STItemUnitsOfMeasure.sql Export_STItemUnitsOfMeasure.sql
Export_ProcessSTFoodCostByItem.sql Export_ProcessSTCostOfGoods.sql Export_ProcessSTTheoreticalCostOfGoodsByDate Export_ProcessSTRegister.sql Export_ProcessSTVendors.sql Export_ProcessSTVendorCustomFields.sql
Export_STEmployeePunchesRealTime.sql Export_ProcessSTEmployeePunches.sql Export_ProcessSTFoodCost.sql Export_ProcessSTFoodCostByItemContractDaily.sql SubPeriod
Sales1
Sales2
Sales3
Export_ProcessSTRevenueCenterDayPart Export_ProcessSTVendorItems.sql
Sales4
Sales5
Sales6
Sales7
Sales8
ST_Employees ST_EmpW4_I9 ST_EmployeePunchesRealTime ST_EmployeePunches ST_Punches ST_Schedule ST_Items ST_ItemCategories ST_ItemUnitsOfMeasure ST_FoodCost ST_FoodCostByItemContractDaily ST_FoodCostByItem ST_CostOfGoods ST_TheoreticalCostOfGoodsByDate ST_Register ST_RegisterByRevenueCenterDayPart ST_Vendors ST_VendorItems ST_VendorCustomFields Sales9
Sales10
PK HomeSiteNumber PK HomeSiteNumber PK BOANETEmployeeNumber PK SiteNumber PK SiteNumber PK SiteNumber PK SiteNumber PK SiteNumber PK SubPeriod PK RecordID PK SiteNumber PK SiteNumber PK SiteNumber PK SiteNumber PK SiteNumber
Sales11
PK BOANETEmployeeNumber PK BOANETEmployeeNumber PK SiteNumber PK BOANETEmployeeNumber PK BOANETEmployeeNumber PK StartSubPeriod PK BusinessDate PK StartSubPeriod PK SiteNumber PK SubPeriod PK SubPeriod PK VendorNumber PK VendorNumber PK VendorNumber
Sales12
InternalEmployeeNumber PK ClockIn PK SalesDate PK SchdDate ItemNumber ItemCategoryNumber ItemUnitOfMeasureNumber PK EndSubPeriod PK RawMaterialItemNumber PK EndSubPeriod PK RawMaterialItemNumber SiteNumber PK SalesDate PK SalesDate PK ItemNumber Sales13
HomeStoreID HomeStoreID SiteNumber PK ClockIn PK ClockIn ItemName ItemCategoryName ItemUnitOfMeasureName PK RawMaterialItemCatNum PK RawMaterialItemNumber PK RawMaterialItemUnitNumber StoreID PK RevenueCenter VendorID PK VendorItemCode VendorID
Sales14
EmployeeNumber EmployeeNumber JobNumber EmployeeNumber ItemID ItemCategoryID RawMaterialItemCategoryNumber BusinessDate StoreID PK DayPart VendorName PK OrderUnitNumber VendorName
Sales15
SSAN W4Exempt PunchTypeID StoreID StoreID StoreID StandardUnitNumber ParentItemCategoryNumber StoreID RawMaterialItemCost StoreID StoreID OccasionID TotalSales Address1 PK VendorInfoNumber Custom_Description_1
Sales16
LastName W4FedMaritalStatus BusinessDate JobNumber EmployeeNumber SubPeriod NormalizeFoodCost RawMaterialItemCatName ActualEndingInventoryCount StartingDate RawMaterialItemCatNum OccasionName CustomerCount StoreID Address2 Custom_Value_1
Sales17
FirstName W4FedExemptNbr ClockIn JobID Year EmployeeNumber ItemCategoryNumber RawMaterialItemCatID ActualQuantityUsed EndingDate RawMaterialItemCatName RawMaterialItemCatID Tax Sales1 City ItemID Custom_Description_2
Sales18
MiddleName W4FedAdditionalAmount ClockOut PunchTypeID SubPeriod JobNumber MenuItemCategoryNumber ActualUse$ TheoryQuantityUsed RawMaterialItemCatNum RawMaterialItemCatID GLAccount LaborCost Sales2 State VendorID Custom_Value_2
Sales19
Address W4StateTaxCode Shift BusinessDate JobNumber JobID PrepItemCategoryNumber TheoryUse$ RawMaterialItemCatID RawMaterialItemID TheoryUseValue OTHours Sales3 PostalCode OrderUnitPrice Custom_Description_3
Sales20
Address2 W4StateExemptNbr Hours SubPeriod JobID JobName ModifierItemCategoryNumber SumOfWklyFoodSales$ RawMaterialItemID RawMaterialItemName CashOverShort Sales4 Country ReceiveUnitNumber Custom_Value_3
Discount1
City W4StateAdditionalAmount TimeClockEditReasonNumber PayPeriodYear JobTitle ClockOut TheoryUse$FIFO RawMaterialItemUnitNumber RawMaterialItemUnitName Sales1 Sales5 PhoneNumber ReceiveUnitPrice Custom_Description_4
Discount2
State I9Citizen ManuallyAdjusted PayPeriodNumber Source Hours RawMaterialItemUnitName BeginningOnHandCount Sales2 Sales6 FaxNumber PriceLocked Custom_Value_4
Discount3
Zip AlienNumber CreatedBy ClockOut ClockOut StationNumber BegInvQty Purchases Sales3 Sales7 EmailAddress POSequence Custom_Description_5
Discount4
Country AlienAuthorizedDate CreatedTime Hours POSEmployeeNumber BegInvValue EndingOnHandCount Sales4 Sales8 ContactName PrimaryOrderItem Custom_Value_5
Discount5
Phone DocumentTitleA LastModifiedBy Source TotalHours PurchQty UsedAmount Sales5 Sales9 ContactTitle Exclude Custom_Description_6
Discount6
AltPhone IssuingAuthorityA LastModifiedTime TimeClockEditReason PurchValue EndingItemCost Sales6 Sales10 BackOrderAvailable Custom_Value_6
Discount7
Gender DocumentNumberA BusinessDateImported Export_STSiteInventoryListMembers_RealTimeFeed.sql InvoiceQuantity BeginningInventory$ Sales7 Sales11 Notes Custom_Description_7
Export_STInventoryLists_RealTimeFeed.sql Discount8
FamilyStatus ExpirationDateA MealBreakWaived InvoiceValue Purchase$ Sales8 Sales12 CreatedBy Custom_Value_7
Discount9
EthnicGroup DocumentNumberA1 RestBreakWaived TransferInQuantity EndingInventory$ Sales9 Sales13 CreatedTime Custom_Description_8
Discount10
Disability ExpirationDateA1 TransferInValue Used$ Sales10 Sales14 LastModifiedBy Custom_Value_8
Export_STItemConversionFactors_RealTimeFeed.sql Export_ProcessSTAdjFoodCostByPartialPeriodPart2.sql Export_STVendors_FromView.sql Discount11
VeteranStatus DocumentTitleB TransferOutQuantity SubPeriodStartDate Sales11 Sales15 LastModifiedTime Custom_Description_9
Discount12
ReferralSource IssuingAuthorityB ST_InventoryLists_RealTimeFeed ST_SiteInventoryListMembers_RealTimeFeed TransferOutValue SubPeriodEndDate Sales12 Sales16 ConvertedFromID Custom_Value_9
Discount13
HireDate DocumentNumberB EndInvQty EndingInventoryUnitCost Sales13 Sales17 CommissarySite Custom_Description_10
Discount14
BirthDate ExpirationDateB EndInvValue Sales14 Sales18 Exclude ST_Vendors_FromView Custom_Value_10
Discount15
MaidenName DocumentTitleC Export_ProcessSTEmployeePayrollDay.sql Export_STEmployeePayrollDayPenaltyHours.sql Export_ProcessSTSchedulePayrollDay.sql Export_ProcessSTScheduleHours.sql ST_ItemConversionFactors_RealTimeFeed ST_AdjFoodCostByPartialPeriod UnitCost Sales15 Sales19 APCode Custom_Description_11
InventoryListNumber SiteNumber Discount16
EmergencyContact IssuingAuthorityC ActualUseQty Sales16 Sales20 AccountNumber Custom_Value_11
InventoryListName InventoryListNumber PK SiteNumber Discount17
ContactRelationship DocumentNumberC ActualUseValue Sales17 VoidSales LocalVendor Custom_Description_12
InventoryListDescription ItemNumber PK Year Discount18
ContactPhone ExpirationDateC TheoryUseQty Sales18 Discount1 OrderDay1 VendorNumber Custom_Value_12
ManageListItemsInSystemManagement Exclude ItemNumber PK Period Discount19
ContactWorkPhone DocCheckedby TheoryUseValue Sales19 Discount2 DeliveryDay1 VendorID Custom_Description_13
ItemUnitNumber PK RawMaterialItemCatNum Discount20
ContactAddress DocCheckerTitle TheoryUseValueFIFO Sales20 Discount3 OrderDay2 VendorName Custom_Value_13
ST_EmployeePayrollDay ST_EmployeePayrollDayPenaltyHours ST_SchedulePayrollDay ST_ScheduleHours UnitToStandardConversionFactor Discount21
EmpStatusDate I9Complete VoidSales Discount4 DeliveryDay2 Address1 Custom_Description_14
StandardToUnitConversionFactor StartDate Discount22
EmpStatusCode LWT_ALLOWANCES Discount1 Discount5 OrderDay3 Address2 Custom_Value_14
PK SiteNumber PK SiteNumber PK SiteNumber PartialPeriodEndDate Discount23
EmpStatusReasonCode LWT_AMT Discount2 Discount6 DeliveryDay3 City Custom_Description_15
PK BOANETEmployeeNumber PK BOANETEmployeeNumber PK BOANETEmployeeNumber ActualUse$ Export_ProcessSTWaste.sql
Discount24
WorkStatus TAXLOCALITY1 Export_ProcessSTWasteByRawMaterial Export_ProcessSTRawInfo.sql Discount3 Discount7 OrderDay4 State Custom_Value_15
PK JobNumber SiteNumber PK JobNumber PK JobNumber AdjustedTheoryUse$FIFO Discount25
TerminationDate TAXLOCALITY2 Discount4 Discount8 DeliveryDay4 PostalCode Custom_Description_16
PK PayTypeID BusinessDate PK PayTypeID PK ScheduleDate Discount26
PayrollNumber TAXLOCALITY3 Discount5 Discount9 OrderDay5 Country Custom_Value_16
PK BusinessDate InternalEmployeeNumber PK BusinessDate Export_ProcessSTItemUseDaily.sql Export_ProcessSTItemUseVariance.sql Export_ProcessSTTransfers.sql Deposit1
Rehire TAXLOCALITY4 Discount6 Discount10 DeliveryDay5 PhoneNumber Custom_Description_17
JobNumber StoreID Deposit2
POSEmployeeNumber A4StateAZAdditionalAmount Discount7 Discount11 OrderDay6 FaxNumber Custom_Value_17
StoreID PenaltyType StoreID EmployeeNumber Deposit3
JobTitle StateExemptFromWithholding Discount8 Discount12 DeliveryDay6 EmailAddress Custom_Description_18
EmployeeNumber Amount EmployeeNumber JobName ST_Waste ST_WasteByRawMaterial ST_RawInfo Deposit4
County DocumentTitleA1 Discount9 Discount13 OrderDay7 ContactName Custom_Value_18
PayTypeName Hours JobID SubPeriod Deposit5
Salaried IssuingAuthorityA1 ST_ItemUseDaily ST_ItemUseVariance ST_InventoryTransfer PK SiteNumber PK SiteNumber PK SiteNumber Discount10 Discount14 DeliveryDay7 ContactTitle Custom_Description_19
Dollars Rate JobName RegularHours Deposit6
FullTime DocumentTitleA2 PK SpoilDate PK BusinessDate PK SubPeriod Discount11 Discount15 TaxID BackOrderAvailable Custom_Value_19
Hours LastModifiedTime PayTypeName OverTimeHours PK SiteNumber PK SubPeriod PK SiteNumber Deposit7
NationalInsurance IssuingAuthorityA2 PK TransactionNumber PK ItemNumber PK RawMaterialItemNum Discount12 Discount16 Notes Custom_Description_20
Rate Dollars DoubleOTHours PK SalesDate PK SiteNumber PK SubPeriod Deposit8
PrimaryJobName DocumentNumberA2 Export_ProcessSTAdjFoodCostByDayPart2.sql Export_ProcessSTAdjFoodCostByWeekPart2.sql Export_ProcessSTAdjFoodCostByPeriodPart2.sql
PK Type Discount13 Discount17 CreatedBy Custom_Value_20
JobID Hours Rate PK RawMaterialItemNum PK RawMaterialItemNumber PK InvoiceNumber Deposit9
PrimaryJobRate ExpirationDateA2 PK ItemNumber StoreID StoreID Discount14 Discount18 CreatedTime
Rate PK ItemUnitNumber PK ItemNumber Deposit10
PrimaryJobNumber AdmissionNumber StandardUnitName ExportDate Discount15 Discount19 LastModifiedBy
StoreID PK ItemUnitNumber Deposit11
PrimaryJobID ForeignPassportNumber StoreID RawMaterialItemID RawMaterialItemID Discount16 Discount20 LastModifiedTime
SubPeriod StoreID PK ToFrom Deposit12
StatusReportingDate CountryOfIssuance ST_AdjFoodCostByDay ST_AdjFoodCostByWeek ST_AdjFoodCostByPeriod ItemUnitNumber SubPeriod RawMaterialItemName Discount17 Discount21 LocalVendor
RawMaterialItemID RawMaterialItemCatNum PK Type Deposit13
PrimaryJobPayrollCode ExpirationDateNA ItemID Quantity RawMaterialItemCatNum Discount18 Discount22 UseVendorDescription
RawMaterialItemName RawMaterialItemCatName PK LastModifiedTime Deposit14
ContactAddress2 PK SiteNumber PK SiteNumber PK SiteNumber SubPeriod StandardUnitPrice RawMaterialItemCatID Discount19 Discount23 TaxID
TheoryUse RawMaterialItemID Deposit15
ContactCity PK BusinessDate PK Year PK Year Quantity RawMaterialItemCatName Discount20 Discount24
ItemUnitNumber RawMaterialItemName StoreID Deposit16
ContactState Export_ProcessSTSites.sql Export_STSitesAndSiteGroups.sql PK RawMaterialItemCatNum PK Period PK Period InventoryUnitPrice CurrentOnHandCount Discount21 Discount25
Export_ProcessSTEmpJobTransCustom.sql Export_ProcessSTScheduleIntervals.sql ItemUnitName ItemUnitName InvoiceID Deposit17
ContactZip PK Week PK RawMaterialItemCatNum TransactionTime CurrentRawMaterialItemCost Discount22 Discount26
TheoreticalOnHandCount SumOfTheoryUse ItemID Deposit18
WOTCValidationCode StoreID PK RawMaterialItemCatNum Reason DateOfCurrentCost Discount23 Deposit1
Export_ProcessSTEmployeeSalesTips.sql ActualOnHandCount EndingItemCost ItemUnitName Deposit19
CustomField1 ST_Sites RawMaterialItemCatName StoreID StandardUnitName Discount24 Deposit2
ItemCost ActualUsage Quantity Deposit20
CustomField2 RawMaterialItemCatID StoreID StartDate StandardUnitNumber Discount25 Deposit3
ST_EmpJobTransCustom PK SiteNumber ST_SitesAndSiteGroups ST_ScheduleIntervals TodaysValue ActualUse$ InventoryUnitPrice Tax
CustomField3 ActualUse$ StartDate EndDate ExportUnitToStandard Discount26 Deposit4 Export_ProcessSTAccruals.sql
YActualOnHandCount Variance BusinessDate Import_POS_SOS.sql Export_ProcessSTDeposits.sql Tax1
CustomField4 PK SiteNumber PK SiteNumber AdjustedTheoryUse$FIFO EndDate RawMaterialItemCatName ExportUnitNumber PaidOut1 Deposit5
ST_EmployeeSalesTips SiteName YItemCost IdealUse$ Accepted Tax2
CustomField5 PK Timestamp PK ScheduleDate RawMaterialItemCatName RawMaterialItemCatID ExportUnitName PaidOut2 Deposit6
StoreID YesterdayValue Variance$ LastModifiedByName Tax3
AlohaLiquorCertificationNumber PK SiteNumber PK BOANETEmployeeNumber SiteNumber PK Interval RawMaterialItemCatID ActualUse$ Inactive TIPS Deposit7
ContactName QtyBought SubPeriodStartDate TransferStatus Tax4
AlohaLiquorCertifcationExpirationDate PK BOANETEmployeeNumber PK JobNumber SiteID PK JobNumber ActualUse$ AdjustedTheoryUse$FIFO InactiveDate TableTurns Deposit8
Address1 Waste SubPeriodEndDate Tax5
EmailAddress PK JobNumber PK EffectiveDate SiteName AdjustedTheoryUse$FIFO Deposit1 Deposit9
Address2 TransferIn Tax6
TipConsent PK BusinessDate SiteType StoreID Deposit2 Deposit10 ST_Accruals ST_POSSOS ST_Deposits
City TransferOut Tax7
RehireDate StoreID SiteUniqueID JobID Deposit3 Deposit11
StateProvince InvQtyTransferred PK SiteNumber PK SiteNumber PK SiteNumber Tax8
I9ValidationCode StoreID EmployeeNumber JobName Deposit4 Deposit12
PostalCode PurchaseValue PK BusinessDate PK BusinessDate PK SalesDate Tax9
BackgroundCheckCode EmployeeNumber JobName RequiredStaff Deposit5 Deposit13
Phone ActualUse PK AccrualNumber PK ModeID PK DepositTime Tax10
DailySales Rate ScheduledStaff Deposit6 Deposit14
AltPhone ActualUseValue PK SequenceNumber Tips1
DeclaredTotalTips JobReason RecommendedStaffCount Deposit7 Deposit15
Email UnitCostExtended StoreID StoreID Tips2
ChargeTips OldEffectiveDate Deposit8 Deposit16
OpenDate Export_ProcessSTInvoices.sql StoreID TransactionCount SubPeriod Tips3
GuestCount OldJobNumber Deposit9 Deposit17
ReportingCloseDate Amount HiVolumeTransactionCount BagNumber Tips4
Export_ProcessSTEmpTrans.sql TipShare OldJobName Deposit10 Deposit18
CustomDate Export_STSiteAndSiteGroupMemberships_RealTimeFeed.sql Description LowVolumeTransactionCount Amount Tips5
Spiffs OldRate Deposit11 Deposit19
ShippingCode GLAccountNumber OrderTime UserID Tips6
Export_ProcessSTPurchaseOrders.sql Deposit12 Deposit20
LegalUnit Reversed HiVolumeOrderTime Notes Tips7
Deposit13 Change
BusinessUnit Export_ProcessSTSalesMix.sql Export_ProcessSTSalesMixByRawMaterial.sql Export_ProcessSTMIC.sql LowVolumeOrderTime CreatedByName Tips8
Deposit14 ActualDeposit
CompanyName ST_SiteAndSiteGroupMemberships_RealTimeFeed DeliveryTime PreVerifiedAmount Tips9
ST_InvoiceDetails ST_InvoiceDetailsSupplierReferenceNumber Deposit15 Labor1
Custom_Description_1 ST_InvoiceHeaders TotalTime OpenAmount Tips10
Deposit16 Labor2
Custom_Value_1 HiVolumeTotalTime VerifiedAmount Tips11
ST_EmpTrans PK SiteNumber PK SiteNumber PK SiteNumber Deposit17 Labor3
ST_EmpTransW4_I9 Custom_Description_2 LowVolumeTotalTime VerifiedTime Tips12
ST_SalesMix ST_SalesMixByRawMaterial ST_MIC PK InvoiceNumber PK InvoiceNumber PK InvoiceNumber Deposit18 Labor4
Custom_Value_2 SiteOrGroupNumber HiVolumeLineTime VerifiedByName Tips13
PK RecordNumber PK RecordNumber ST_PurchaseOrders ST_PurchaseOrderItems PK VendorNumber PK InvoiceDate PK InvoiceDate Deposit19 Labor5
Custom_Description_3 MemberOfSiteOrGroupNumber PK SiteNumber PK SiteNumber HiVolumeWindowTime ValidatedAmount Tips14
PK SiteNumber PK InvoiceDate PK PurchasedItemNumber PK PurchasedItemNumber Deposit20 Labor6
Custom_Value_3 MemberDistance PK ItemNumber PK StartingDate LowVolumeWindowTime ValidatedTime Tips15
HomeSiteNumber HomeSiteNumber PK ItemNumber PK SiteNumber PK SiteNumber PK LastModifiedDate PK InvoiceLineItem PK InvoiceLineItem Change Labor7
Custom_Description_4 PK SubPeriod PK EndingDate ValidatedByName Transaction1
HomeStoreID HomeStoreID PK SubPeriod PK PurchaseOrderNumber PK PurchaseOrderNumber ActualDeposit Labor8
Export_ProcessSTEmpJobTrans.sql Custom_Value_4 PK SalesMixDate PK RawMaterialItemNum Transaction2
Timestamp Timestamp PK PriceSoldAt PK BusinessDate PK LineItemNumber StoreID StoreID VendorItemID Labor1 Labor9
Custom_Description_5 PK SellingPrice Transaction3
BOANETEmployeeNumber BOANETEmployeeNumber InvoiceID InvoiceID SupplierReferenceNumber Labor2 Labor10
Custom_Value_5 StoreID Transaction4
EmployeeNumber W4Exempt StoreID StoreID ItemNumber VendorID PurchasedItemID Labor3 Other1
Custom_Description_6 StoreID StartSubPeriod Transaction5
SSAN W4FedMaritalStatus MenuItemID ConnectedToPurchaseOrderNumber ItemID VendorAPCode VendorItemID Labor4 Other2
Custom_Value_6 MenuItemID EndSubPeriod Transaction6
SSAN_Original W4FedExemptNbr MenuItemCatNum PurchaseOrderID ItemName EndDate QuantityReceived Labor5 Other3
Custom_Description_7 Export_ProcessSTSitePayroll.sql MenuItemName RawMaterialItemID Transaction7
LastName W4FedAdditionalAmount Export_ProcessSTSiteSubPeriod.sql MenuItemCatID VendorNumber ItemUnitNumber ReportingPeriod PurchaseUnitID Labor6 Other4
Custom_Value_7 TotalNumberSold RawMaterialItemUnitNumber Transaction8
FirstName W4StateTaxCode ST_EmpJobTrans MenuItemCatName VendorName ItemUnitName Week PurchaseUnitName Labor7 Other5
Custom_Description_8 NetSales RawMaterialItemUnitName Transaction9
MiddleName W4StateExemptNbr MenuItemName VendorID Price SubPeriod PurchaseUnitPrice Labor8 Other6
Custom_Value_8 Quantity Transaction10
Address W4StateAdditionalAmount PK TransactionNumber TotalNumberSold VendorAPCode QuantityOrdered InventoryPeriod ExtendedPrice Labor9 Other7
Custom_Description_9 QuantityUnrounded Transaction11
Address2 I9Citizen PK SiteNumber ST_SitePayroll ST_SiteSubPeriod SumOfPortionCost DueDate StandardQuantityOrdered TotalAmountPayable RawMaterialItemCatNum Labor10 Other8
Custom_Value_9 Value Transaction12
City AlienNumber PK Timestamp Contribution OrderTotal ExtendedPrice DueDate RawMaterialItemCatID Other1 Other9 Export_ProcessSTOccasions.sql Export_STALOHAGNDBREAKINFO.sql
Custom_Description_10 PK SiteNumber PK SiteNumber ValueUnrounded Transaction13
State AlienAuthorizedDate PK BOANETEmployeeNumber TotalDollarsSold OpenOrder PurchaseType FreightAmount RawMaterialItemCatName Other2 Other10
Custom_Value_10 PK SubPeriod PK SubPeriod UnitCost Transaction14
Zip DocumentTitleA PK JobNumber SubPeriodStartDate RequisitionForSiteNumber VendorItemID SalesTaxAmount SubPeriod Other3 Tax1
Custom_Description_11 UnitCostUnrounded Transaction15
Country IssuingAuthorityA PK StartDate SubPeriodEndDate CommissaryVendorNumber ConsolidatedFromSiteNumber Notes TaxAmount Other4 Tax2
Custom_Value_11 StoreID StartDate PaidOut1
Phone DocumentNumberA CommissaryVendorName GLAccountNumber PODate ItemName Other5 Tax3
Custom_Description_12 StartDate EndDate PaidOut2
AltPhone ExpirationDateA StoreID CommissaryVendorID RawMaterialItemCatNum PONumber Notes Other6 Tax4
Custom_Value_12 EndDate Year VoidSales
Gender DocumentNumberA1 EmployeeNumber Notes RawMaterialItemCatID CheckNumber Other7 Tax5
Custom_Description_13 Year Period CustomerCount
FamilyStatus ExpirationDateA1 JobName CreatedBy RawMaterialItemCatName DeliveredTime Other8 Tax6
Custom_Value_13 Period Week ST_Occasions ST_OccasionCategoriesOccasions ST_ALOHAGNDBREAKINFO CashOverShort
EthnicGroup DocumentTitleB JobID CreatedTime CreatedBy Other9 Tax7
Custom_Description_14 Week BusinessCalendarNumber Currency1
Disability IssuingAuthorityB EndDate CreatedByName CreatedByName Other10 Tax8 PK UniqueID PK OccasionCategoryUniqueID
Custom_Value_14 BusinessCalendarNumber BusinessCalendarName Currency5
VeteranStatus DocumentNumberB PayReasonNumber Export_ProcessSTSalesGuestsByInterval.sql Export_STForecastSalesGuestsByInterval_FromView.sql Export_ProcessSTForecastSalesAndGuests.sql LastModifiedBy CreatedTime Tax1 Tax9 PK OccasionUniqueID
Custom_Description_15 BusinessCalendarName Export_STCustomFPZ.sql Export_STSafeCount.sql Currency10
ReferralSource ExpirationDateB PayReasonName LastModifiedTime LastModifiedBy Tax2 Tax10 SiteNumber RecordNumber
Custom_Value_15 Currency20
HireDate DocumentTitleC PerformanceRatingNumber LastModifiedByName LastModifiedByName Tax3 TotalSales StoreID OccasionCategoryID SiteNumber
Custom_Description_16 Currency50
BirthDate IssuingAuthorityC PerformanceRatingName SentBy InvoiceFinal Tax4 CustomerCount OccasionUniqueID OccasionCategoryName BusinessDate
Custom_Value_16 Currency100
MaidenName DocumentNumberC Rate SentTime SFDate Tax5 Tax OccasionID ImportDateTime
Custom_Description_17 ST_SalesGuestsByInterval ST_ForecastSalesGuestsByInterval_FromView ST_ForecastDailySalesAndGuests Coin1
EmergencyContact ExpirationDateC PrimaryJob SentByName SFInvoiceNumber ST_CustomFPZ ST_SafeCount Tax6 LaborCost OccasionName InternalEmployeeNumber
Custom_Value_17 Export_STCalendarSubperiods.sql Coin5
ContactRelationship DocCheckedby NewEndDate Export_ProcessSTCalendars.sql
PK SiteNumber PK SiteNumber ConfirmSent InvoiceType Tax7 OTHours EventIdentifier InternalJobNumber
Custom_Description_18 Coin10
ContactPhone DocCheckerTitle NewPayReasonNumber PK SalesDate PK BusinessDate Consolidated OriginalInvoiceID Tax8 CashOverShort ParTemplateID BREAKID
Custom_Value_18 Coin25
ContactWorkPhone I9Complete NewPayReasonName PK StartTime SiteNumber InvoiceExternalID Tax9 PaidOut1 ParTemplateName EMPLOYEE
Custom_Description_19 RecordNumber SiteNumber Coin50
ContactAddress LWT_ALLOWANCES NewPerformanceRatingNumber BusinessDate StoreID Tax10 PaidOut2 StartTime AGE
Custom_Value_19 SiteNumber BusinessDate Coin100
EmpStatusDate LWT_AMT NewPerformanceRatingName ST_Calendars ST_CalendarSubperiods StoreID StartTime Sales NRT TIPS EndTime EXPORTID
Custom_Description_20 BusinessDate SafeCountNumber CoinRoll1
EmpStatusCode TAXLOCALITY1 NewRate SubPeriod EndTime Guests NetSales TableTurns CreatedTime ALOHA_JOBCODE
Custom_Value_20 ImportDateTime TotalSafeCount CoinRoll5
EmpStatusReasonCode TAXLOCALITY2 NewPrimaryJob PK SiteNumber EndTime CurrentSalesForecast LastModifiedByName NRT ModifiedTime ALOHA_BUSINESSDATE
TaxJurisdiction FPZ_DOB TotalSafeCountVariance CoinRoll10
WorkStatus TAXLOCALITY3 ModifiedByNumber PK BusinessCalendarNumber TotalSales CurrentGuestForecast LastModifiedTime NetSales SYSDATEBEG
StoreHoursSundayOpen Export_STScheduleRecommendedByDayLaborMatrices.sql Export_STPurchaseOrders_RealTimeFeed.sql Export_STPurchaseOrderItems_RealTimeFeed.sql
FPZ_DT NumberofDrawers CoinRoll25
TerminationDate TAXLOCALITY4 ModifiedByName PK CalendarType BusinessCalendarNumber TotalCustomers SYSDATEEND
StoreHoursSundayClose SystemGeneratedSalesForecast CoinRoll50
PayrollNumber A4StateAZAdditionalAmount BusinessDate BusinessCalendarSubperiodNumber FPZ_TM StandardDrawerAmount PERIOD
StoreHoursMondayOpen ToGoSales SystemGeneratedGuestForecast CoinRoll100
Rehire StateExemptFromWithholding JobPayrollCode StoreID Year FPZ_STRID CashDrops OCCASION
StoreHoursMondayClose ToGoCustomers LastYearSales TotalSales
POSEmployeeNumber DocumentTitleA1 BusinessCalendarName Period FPZ_POSNO SafeCount_1Dollar UNIT
StoreHoursTuesdayOpen EatInSales TableTurns
JobTitle IssuingAuthorityA1 Week ST_ScheduleRecommendedByDayLaborMatrices ST_PurchaseOrders_RealTimeFeed ST_PurchaseOrderItems_RealTimeFeed FPZ_ZNUM SafeCount_5Dollars SHFT_ID
StoreHoursTuesdayClose EatInCustomers Change
County DocumentTitleA2 StartDate FPZ_G1 SafeCount_10Dollars SHFT_INHR
StoreHoursWednesdayOpen FPZ_N1 SafeCount_20Dollars ActualDeposits
Salaried IssuingAuthorityA2 EndDate SHFT_INMIN
StoreHoursWednesdayClose FPZ_G2 SafeCount_50Dollars Tips
FullTime DocumentNumberA2 SHFT_OTHR
StoreHoursThursdayOpen SiteNumber CreatedTime SiteNumber FPZ_N2 SafeCount_100Dollars LaborCost
NationalInsurance ExpirationDateA2 SHFT_OTMIN
StoreHoursThursdayClose Timestamp SiteNumber PurchaseOrderNumber FPZ_G3 SafeCount_1CentRoll
Export_ProcessSTAllocations.sql Export_ProcessSTBudgets.sql Export_STDataDefinitionConfiguration.sql OTHours
StatusReportingDate AdmissionNumber SHFT_MIN
StoreHoursFridayOpen RecommendedStaffingMethod SiteID LineItemNumber FPZ_N3 SafeCount_5CentsRoll Labor1
ContactAddress2 ForeignPassportNumber SHFT_HOURS
StoreHoursFridayClose Export_STItemPropertiesBySite_FromView.sql Export_STInactiveItemBySites_FromView.sql Export_STExcludedItemsBySites_FromView.sql ScheduleDate PurchaseOrderNumber VendorItemID FPZ_G4 SafeCount_10CentsRoll Labor2
ContactCity CountryOfIssuance SHFT_EDDAT
StoreHoursSaturdayOpen ScheduleDayofWeek VendorID QuantityOrdered FPZ_N4 SafeCount_25CentsRoll Labor3
ContactState ExpirationDateNA SHFT_EDTIM
StoreHoursSaturdayClose RestConfigNumber DueDate RawMaterialItemNumber FPZ_G5 SafeCount_50CentsRoll Labor4
ContactZip SHFT_EDMGR
SiteTaxID RecommendedStaffingbyDayName SentBy StandardQuantityOrdered FPZ_N5 SafeCount_1DollarCoinRoll Labor5
WOTCValidationCode ST_Allocations ST_Budgets ST_DataDefinitionConfiguration SHFT_OPEN
MatrixNumber BusinessDate SuggestedOrderQuantity FPZ_G6 Notes Labor6
TipConsent SHFT_CKMGR
ST_ItemPropertiesBySite_FromView ST_InactiveItemsBySite_FromView ST_ExcludedItemsBySite_FromView MatrixName OrderTotal SuggestedOrderUnitNumber FPZ_N6 PostedTime PK SiteNumber PK SiteNumber Labor7
RehireDate BRK_PAID
MatrixType OpenOrder SplitCaseIndicator CreatedBy PK BusinessDate PK BusinessDate Labor8
I9ValidationCode BRK_INVALD
StartTime SentTime CreatedTime PK DataDefinitionNumber PK DataDefinitionNumber Labor9
BackgroundCheckCode DataDefinitionNumber BRK_EDIT
EndTime ConfirmSent LastModifiedBy Labor10
SiteNumber SiteNumber SiteNumber DataDefinitionName BRK_EDMGR
DailyRecommendedStaffingHours FromOrderByVendor LastModifiedTime AllocationAmount BudgetAmount Other1
ItemNumber ItemNumber ItemNumber DataDefinitionDescription BRK_EDDATE
CreatedBy Other2
RawItem InactiveDate SourceNumber BRK_EDTIME
Export_STEmployeeSalesTips_RealTimeFeed.sql Export_STAlohaSalesMixTransactions_RealTimeFeed.sql LastModifiedBy Other3
Export_STEmployeeStatusBySite_RealTimeFeed.sql
MenuItem DecimalPlaces BRK_MINMIN
LastModifiedTime Other4
PrepItem AllocationEntrySequence BRK_INHR
PurchaseOrderID Other5
ModifierItem BudgetType BRK_INMIN Other6
Purchasable BudgetEntrySequence BRK_OUTHR Other7
Waste BRK_OUTMIN Other8
ST_EmployeeStatusBySite_RealTimeFeed ST_EmployeeSalesTips_RealTimeFeed ST_AlohaSalesMixTransactions_RealTimeFeed Taxable Export_STTipShareDistribution_RealTimeFeed.sql Export_STTipShareEmployeeDistribution_RealTimeFeed.sql Export_STTipShareJobDistribution_RealTimeFeed.sql BRK_MIN
Export_STJobs.sql Export_STTasksAndStations.sql Other9
RequiredToOrder BRK_HOURS Other10
RecommendedOrderByMethod BRK_RULEID
TheoreticalCalculationMethod Export_STUsers_RealTimeFeed.sql Export_STUserGroups_RealTimeFeed.sql Export_STUserGroupMemberships_RealTimeFeed.sql BRK_RDTID
RecordNumber SiteNumber RecordNumber
POSMenuItemPrice BRK_WAVBLE
SiteFrom InternalEmployeeNumber SiteNumber
POSItemNumber ST_TipShareDistribution_RealTimeFeed ST_TipShareEmployeeDistribution_RealTimeFeed ST_TipShareJobDistribution_RealTimeFeed BRK_WAIVED
SiteTo JobNumber BusinessDate ST_Jobs ST_TasksAndStations
BRK_WINMIS
InternalEmployeeNumber BusinessDate Timesold
BRK_PENLTY
ModifiedBy DailySales AlohaSalesType ST_Users_RealTimeFeed ST_UserGroups_RealTimeFeed ST_UserGroupMemberships_RealTimeFeed BRK_COMPL
Action DeclaredTotalTips AlohaItemPOSCode SiteNumber SiteNumber SiteNumber
ActionTime ChargeTips InternalMenuLinkItemNumber JobNumber TaskOrStationNumber
BusinessDate BusinessDate BusinessDate
GuestCount AlohaParentItemPOSCode JobName TaskOrStationName
ShiftNumber InternalEmployeeNumber ShiftNumber
TipShare AlohaParentModifierPOSCode JobID TaskOrStationID UserNumber UserGroupNumber UserOrGroupNumber StartTime ShiftNumber JobNumber
OtherEarnings ItemEnteredTime DirectTips TaskOrStationType UserName UserGroupName MemberOfUserOrUserGroupNumber EndTime JobNumber DistributionPercent
AlohaTippableCreditCardSales OrderMode InDirectTips ScheduleType FirstName NotCurrentlyAssigned MemberDistance TipShare Hours DistributionAmount
AlohaDeclaredCashTips InclusiveTax DeductBreaks DataSource LastName DistributionType TipShare
AlohaTipshareContribution AlohaCheckNumber LaborGroupNumber AutoCreated Finalized
AlohaTipsforAllTenders AlohaEmployeePOSCode JobPayrollCode DatePasswordChanged LastModifiedBy
AlohaAutomaticGratuityforAllTenders InternalEmployeeNumber NonServiceJob PasswordLastClearedBy LastModifiedTime
AlohaTipsforAllCreditCardTenders AlohaSellingPrice AlternateSalesForecastJob Inactive ContributionAmountManuallyModified
AlohaAutomaticGratuityforAllCreditCardTenders AlohaDiscountedPrice ExcludeScheduleMetrics InactiveDate ImportedContributionAmount
ManualEdit QuickComboID
EditedBy QuickComboPrimary
AlohaAutomaticGratuityforAllCashTenders PrimaryItemNumber
AlohaAutomaticGratuityforAllOtherTenders QuickComboUpsell
AlohaAutomaticGratuityforAllNonCashTenders

Export_ProcessSTPromosComps.sql Export_STItemRecipes_FromView.sql Export_STItemRecipeIngredients_FromView.sql Export_STItemRecipePrepStations_FromView.sql Export_STItemRecipePlateAndStores_FromView.sql Export_STItemRecipeKitchenTools_FromView.sql Export_STRecipeVersionBySite_FromView.sql Export_STPrepStations_FromView.sql Export_STPlateStore_FromView.sql Export_STKitchenTool_FromView.sql

ST_PromosComps ST_ItemRecipes_FromView ST_ItemRecipeIngredients_FromView ST_ItemRecipePrepStations_FromView ST_ItemRecipePlateAndStores_FromView ST_ItemRecipeKitchenTools_FromView ST_RecipeVersionBySite_FromView ST_PrepStations_FromView ST_PlateStore_FromView ST_KitchenTool_FromView
Export_STPayrollStatus_FromView.sql Export_STPayrollStatusDetail_FromView.sql Export_ProcessSTEmpJobRates.sql Export_STSiteEmployeeRateChangeAcknowledgments_FromView.sql Export_STEmployeeClockPunchHistory_FromView.sql Export_STTimeClockEditReason_FromView.sql PK SiteNumber
PK BusinessDate
PK PromoCompType SiteNumber SiteNumber SiteNumber SiteNumber SiteNumber SiteNumber PrepStationNumber PlateStoreNumber KitchenToolNumber
PK ID ItemNumber ItemNumber ItemNumber ItemNumber ItemNumber ItemNumber PrepStationName PlateStoreName KitchenToolName
ST_PayrollStatus_FromView ST_PayrollStatusDetail_FromView ST_EmpJobRates ST_EmployeeClockPunchHistory_FromView ST_TimeClockEditReason_FromView RecipeNumber RecipeNumber RecipeNumber RecipeNumber RecipeNumber InheritedFromSiteNumber Plate
ST_SiteEmployeeRateChangeAcknowledgments_FromView
StoreID StartDate SequenceNumber PrepStationNumber PlateStoreNumber KitchenToolNumber
PK SiteNumber Name EndDate IngredientItemNumber
PK BOANETEmployeeNumber Amount RecipeName Amount
SiteNumber SiteNumber PK JobNumber SiteNumber SiteNumber TimeClockEditReasonNumber Quantity RecipeMakesUnitNumber RecipeUnitNumber
PayPeriodStartDate StartDate PK StartDate InternalEmployeeNumber BusinessDate TimeClockEditReasonDescription RecipeMakesAmount StandardAmount
PayPeriodEndDate EndDate InternalJobNumber PunchEditType RecipeMakesStandardAmount PrimaryIngredient
Status BusinessDate StoreID LastPayRate InternalEmployeeNumber KeyVolumeIndicator1
CreatedBy ChangedBy EmployeeNumber NewPayRate EmployeeName KeyVolumeIndicator1Quantity
CreatedTime ChangeDateTime JobName LastTipCreditAmount InternalJobNumber KeyVolumeIndicator2
LastModifiedBy RecordNumber EndDate NewTipCreditAmount JobcodeName KeyVolumeIndicator2Quantity
LastModifiedTime PayReasonNumber ExportTime ClockIn KeyVolumeIndicator3
PayReasonName AcknowledgmentStatus ClockOut KeyVolumeIndicator3Quantity
PerformanceRatingNumber AcknowledgmentTime PunchTypeNumber KeyVolumeIndicator4
PerformanceRatingName TransactionID PunchTypeName KeyVolumeIndicator4Quantity
Rate Hours KeyVolumeIndicator5
PrimaryJob TimeClockEditReasonNumber KeyVolumeIndicator5Quantity
ModifiedOn ModifiedByNumber KeyVolumeIndicator6
ModifiedBy ModifiedByName KeyVolumeIndicator6Quantity
ModifiedByName CreatedBy Sensitivity
CreatedTime SensitivityText
RecordNumber PrintedShelfLife
EmployeePOSCode PrintedShelfLifeText
POSJobcodeID PortionSizeUnitNumber
BusinessDateImport PortionSizeAmount
SourceOfEdit
POSShiftID
POSBreakID
POSAcknowledgementStatus

Data Mart Entity Diagram 3


Notes:

4 Entity Diagram Data Mart


Public Tables
ST_Accruals

Description: Accrual Information

Triggered by Export_ProcessSTAccruals.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
BusinessDate datetime No Description: Business Date of Transaction
Example: 2007-07-17
AccrualNumber Int No Description: Accrual Number (Internal)
Example: 1456
SequenceNumber Int No Description: Internal Only
You can have more than one amount for
the same accrual for the same business
day. This was added so we could set a key
for data replication.
Example: 2
Amount decimal (19, 3) Yes Description: Amount
Example: 12.34
Description nvarchar (100) Yes Description: Description
Example: Service Credit
GLAccountNumber nvarchar (100) Yes Description: General Ledger Account
Number
Example: BIO-123456
Reversed bit Yes Description: Is Accrual Reversed
0 = No
1 = Yes
Example: 0

Data Mart ST_Accruals 5


Index Name Unique Clustered Fields
PK_ST_Accruals Yes Yes SiteNumber, BusinessDate,
AccrualNumber, SequenceNumber

6 ST_Accruals Data Mart


ST_AdjFoodCostByDay

Description: FIFO Food Cost Data by SITE by DAY with Variance Cap applied.

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to True (checked).
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Only site type „2‟ (store) is supported.
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BusinessDate datetime No Description: Business Date of Transaction
Example: 2008-03-21
RawMaterialItemCatNum int No Description: Category Number (internal)
assigned to the raw material.
Note: Category Number is defined in
ST_ItemCategories.
Example: 1001283
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: Dairy (Raw)
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 10008
ActualUse$ money Yes Description: Actual usage value for the
category, calculated from beginning
inventory, purchases, transfers in and out,
and ending inventory.

For example, if the beginning inventory for


Dairy was $1000, purchases were $4000,
transfers in were $50, transfers out were
$100, and ending inventory was $1200, the
ActualUse$ would be $3750. (1000 + 4000
+ 50 – 100 – 1200 = 3750)

Example: 3750.00

Data Mart ST_AdjFoodCostByDay 7


Field Type Nulls? Comments
AdjustedTheoryUse$FIFO money Yes Description: Theoretical usage value for the
category, with the variance cap taken into
consideration. The variance cap („Allowed
Variance‟, configurable by category or by
item) ensures that restaurants don‟t get
variance credit for more than the defined
percentage. This promotes accurate
portioning and inventories, as restaurants
get no benefit from excess under-use of an
item.

For example, If theoretical usage for Dairy


was $200 and actual usage was $100, and
the variance cap set to 5%, the
AdjustedTheoryUse$FIFO would only be
$105, and the restaurant would only get a
$5 benefit.

Example: 105.00

Index Name Unique Clustered Fields


PK_ST_AdjFoodCostByDay Yes Yes SiteNumber, BusinessDate,
RawMaterialItemCatNum

8 ST_AdjFoodCostByDay Data Mart


ST_AdjFoodCostByPartialPeriod

Description: FIFO Food Cost Data by SITE by PARTIAL PERIOD with Variance Cap applied.

Time Frame: This table provides food cost values for a partial period within the selected export
timeframe. The default partial period begins with the period start date (based on the defined fiscal
calendar period) and ends on the fourteenth day of the period. The information for each day within
the partial period is summed for this export. Costing values are based on the beginning & end dates of
the partial period. These values can be compared with NCR Back Office food cost reports, only when
the report is generated for the SAME time period as the table content.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to True (checked). This setting can be changed to False
by request.
3. The default partial period is 14 days including the period start date. The number of days can be
changed by request.
4. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.
5. Data Mart exports which include the ST_AdjFoodCostByPartialPeriod table should be run with
„Period‟ selected on the „Time Frame‟ tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Only site type „2‟ (store) is supported.
Example: 1456
Year int No Description: The fiscal year of the period for
which the Data Mart export was run.
Examples: 2012
Period int No Description: The period, as defined in Back
Office Manager|Calendar|Calendar
Maintenance, for which the Data Mart export
was run.
Example: 3
StartDate datetime No Description: Start date of the period for
which the Data Mart export was run.
Example: 2012-03-01

Data Mart ST_AdjFoodCostByPartialPeriod 9


Field Type Nulls? Comments
PartialPeriodEndDate datetime No Description: End date of the partial period
for which the Data Mart export was run.

For example, if the StartDate of the Period


was March 1st, and the Partial Period is 14
days, the PartialPeriodEndDate will be March
14th.
Note: Default Partial Period is 14 days.

Example: 2012-03-14
RawMaterialItemCatNum int No Description: Category Number (internal)
assigned to the raw material.
Note: Category Number is defined in
ST_ItemCategories.

Example: 1001283
ActualUse$ money Yes Description: Actual usage value for the
category, calculated from beginning
inventory, purchases, transfers in and out,
and ending inventory.

For example, if the beginning inventory for


Dairy was $1000, purchases were $4000,
transfers in were $50, transfers out were
$100, and ending inventory was $1200, the
ActualUse$ would be $3750. (1000 + 4000
+ 50 – 100 – 1200 = 3750)

Example: 3750.00
AdjustedTheoryUse$FIFO money Yes Description: Theoretical usage value for the
category, with the variance cap taken into
consideration. The variance cap („Allowed
Variance‟, configurable by category or by
item) ensures that restaurants don‟t get
variance credit for more than the defined
percentage. This promotes accurate
portioning and inventories, as restaurants
get no benefit from excess under-use of an
item.

For example, If theoretical usage for Dairy


was $200 and actual usage was $100, and
the variance cap set to 5%, the
AdjustedTheoryUse$FIFO would only be
$105, and the restaurant would only get a
$5 benefit.

Example: 105.00

Index Name Unique Clustered Fields


PK_ST_AdjFoodCostByPartialPeriod Yes Yes SiteNumber, Year, Period,
RawMaterialItemCatNum

10 ST_AdjFoodCostByPartialPeriod Data Mart


ST_AdjFoodCostByPeriod

Description: FIFO Food Cost Data by SITE by PERIOD with Variance Cap applied.

Time Frame: This table will sum all days for the periods (based on the defined fiscal calendar period)
associated with the selected time frame for this export.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to True (checked) as the default. This setting can be
changed to False by request.
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Only site type „2‟ (store) is supported.
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
Year int No Description: The fiscal year of the period for
which the Data Mart export was run.
Examples: 2012
Period int No Description: The period, as defined in Back
Office Manager|Calendar|Calendar
Maintenance, for which the Data Mart export
was run.
Example: 3
StartDate datetime No Description: Start Date of the Period
Example: 2008-02-25
EndDate datetime No Description: End Date of the Period
Example: 2008-03-30
RawMaterialItemCatNum int No Description: Internal Category Number
(internal) assigned to the raw material.
Note: Category Number is defined in
ST_ItemCategories.
Example: 1001283

Data Mart ST_AdjFoodCostByPeriod 11


Field Type Nulls? Comments
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: Dairy (Raw)
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 10008
ActualUse$ money Yes Description: Actual usage value for the
category, calculated from beginning
inventory, purchases, transfers in and out,
and ending inventory.

For example, if the beginning inventory for


Dairy was $1000, purchases were $4000,
transfers in were $50, transfers out were
$100, and ending inventory was $1200, the
ActualUse$ would be $3750. (1000 + 4000
+ 50 – 100 – 1200 = 3750)

Example: 3750.00
AdjustedTheoryUse$FIFO money Yes Description: Theoretical usage value for the
category, with the variance cap taken into
consideration. The variance cap („Allowed
Variance‟, configurable by category or by
item) ensures that restaurants don‟t get
variance credit for more than the defined
percentage. This promotes accurate
portioning and inventories, as restaurants
get no benefit from excess under-use of an
item.

For example, If theoretical usage for Dairy


was $200 and actual usage was $100, and
the variance cap set to 5%, the
AdjustedTheoryUse$FIFO would only be
$105, and the restaurant would only get a
$5 benefit.

Example: 105.00

Index Name Unique Clustered Fields


PK_ST_AdjFoodCostByPeriod Yes Yes SiteNumber, Year, Period,
RawMaterialItemCatNum

12 ST_AdjFoodCostByPeriod Data Mart


ST_AdjFoodCostByWeek

Description: FIFO Food Cost Data by SITE by WEEK with Variance Cap applied.

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to True (checked).
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Only site type „2‟ (store) is supported.
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
Year int No Description: The fiscal year of the period for
which the Data Mart export was run.
Examples: 2012
Period int No Description: The period, as defined in Back
Office Manager|Calendar|Calendar
Maintenance, for which the Data Mart export
was run.
Example: 3
Week int No Description: Week
Example: 4
StartDate datetime No Description: Start Date of the Week
Example: 2008-03-17
EndDate datetime No Description: End Date of the Week
Example: 2008-03-23

Data Mart ST_AdjFoodCostByWeek 13


Field Type Nulls? Comments
RawMaterialItemCatNum int No Description: Category Number (internal)
assigned to the raw material.
Note: Category Number is defined in
ST_ItemCategories.
Example: 1001283
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: Dairy (Raw)
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 10008
ActualUse$ money Yes Description: Actual usage value for the
category, calculated from beginning
inventory, purchases, transfers in and out,
and ending inventory.

For example, if the beginning inventory for


Dairy was $1000, purchases were $4000,
transfers in were $50, transfers out were
$100, and ending inventory was $1200, the
ActualUse$ would be $3750. (1000 + 4000
+ 50 – 100 – 1200 = 3750)

Example: 3750.00
AdjustedTheoryUse$FIFO money Yes Description: Theoretical usage value for the
category, with the variance cap taken into
consideration. The variance cap („Allowed
Variance‟, configurable by category or by
item) ensures that restaurants don‟t get
variance credit for more than the defined
percentage. This promotes accurate
portioning and inventories, as restaurants
get no benefit from excess under-use of an
item.

For example, If theoretical usage for Dairy


was $200 and actual usage was $100, and
the variance cap set to 5%, the
AdjustedTheoryUse$FIFO would only be
$105, and the restaurant would only get a
$5 benefit.

Example: 105.00

Index Name Unique Clustered Fields


PK_ST_AdjFoodCostByWeek Yes Yes SiteNumber, Year, Period, Week,
RawMaterialItemCatNum

14 ST_AdjFoodCostByWeek Data Mart


ST_Allocations

Description: Allocation amounts by Site, by BusinessDate

Time Frame: This table will include each day‟s allocation (by day) for the selected timeframe in this
export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Also only site types of „2‟ (store) are
supported.
Example: 1456
BusinessDate datetime No Description: Business Date for the allocation
amount.
If a week or period is selected, a value for
each business day is exported.
Example: 2007-03-26
DataDefinitionNumber int No Description: Internal Number which
references the Data Definition.
Note: Data Definitions are defined in
ST_DataDefinitionConfiguration
Example: 1016924
AllocationAmount decimal (19,5) Yes Description: Amount is the value for the
daily allocation that is entered by manager
or imported.
Note: If the Allocation‟s „Time Interval‟ is
Week or Period, daily allocation records will
be created. Example: 581.1345

Index Name Unique Clustered Fields


PK_ST_Allocations Yes Yes BusinessDate, SiteNumber,
DataDefinitionNumber

Data Mart ST_Allocations 15


ST_AlohaGndBreakInfo *

16 ST_AlohaGndBreakInfo * Data Mart


Description: : This table provides employee meal & rest break information, and break rule compliance
information, imported from the Aloha POS, by site, by business date, by employee, and by shift ID.
This table is updated when the Aloha POS import is performed with „Data Mart Feed – Aloha Break
Transactions‟ import type selected. NCR Back Office punch edits may not be configured to update
Aloha and therefore may not be represented in this table.

Triggered by Export_ST ALOHAGNDBREAKINFO.sql

Time Frame: This table does not use the export time frame.

Notes:
1. The GNDBREAKINFO.DBF file is supported in Aloha POS versions 6.4 and higher.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordNumber bigint No Description: A unique record identifier.
Example: 12
SiteNumber int Yes Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime Yes Description: The business date of the imported
Aloha GNDBREAKINFO data.
Example: 2012-06-10
ImportDateTime datetime Yes Description: The date the import „Data Mart
Feed – Aloha Break Transactions‟ was
performed.
Example: 2012-06-10 14:10:32.000
Uses Site Local Time
InternalEmployeeNumber int Yes Description: Employee Number (internal).
Note: Employees are defined in ST_Employees
Example: 1002863
InternalJobNumber int Yes Description: Job Number (internal).
Note: Jobs are defined in ST_Jobs
Example: 1000626
BREAKID int Yes Description: The Break ID as imported from
Aloha POS.
Example: 10
EMPLOYEE int Yes Description: The Employee ID as imported
from Aloha. This ID is the stored in the NCR
Back Office employee profile as the POS Code.
Example: 1633566
AGE int Yes Description: The Employee‟s age on the day of
the shift, as imported from Aloha.
Example: 32
EXPORTID int Yes Description: The Employee‟s export ID
number, as imported from Aloha
Example: 0
ALOHA_JOBCODE int Yes Description: The Employee Job Code ID as
imported from Aloha POS.
Example: 100
ALOHA_BUSINESSDATE datetime Yes Description: Date of Business (DOB), as
imported from Aloha
Example: 2012-06-10
SYSDATEBEG datetime Yes Description: The calendar date associated with
the employee‟s break start time.
Note: This can differ from the business date.
Example: 2012-06-10

Data Mart ST_AlohaGndBreakInfo * 17


Field Type Nulls? Comments
SYSDATEEND datetime Yes Description: The calendar date associated with
the employee‟s break end time.
Note: This can differ from the business date.
Example: 2012-06-11
PERIOD int Yes Description: Aloha‟s Period ID, as defined in
Aloha Manager
Example: 6
OCCASION int Yes Description: The occasion associated with the
Aloha business day.
Example: 1
UNIT int Yes Description: Store number, as imported from
Aloha
Example: 150895
SHFT_ID int Yes Description: The employee shift number for
the day.
Note: First clock-in on the same day= Shift 1,
Second clock-in on the same day= Shift 2, etc
Example: 1
SHFT_INHR int Yes Description: The employee‟s shift clock-in hour
Example: 16
SHFT_INMIN int Yes Description: The employee‟s shift clock-in
minutes
Example: 59
SHFT_OTHR int Yes Description: The employee‟s shift clock-out
hour.
Example:22
SHFT_OTMIN int Yes Description: The employee‟s shift clock-out
minutes.
Example: 7
SHFT_MIN int Yes Description: The employee‟s shift total worked
time represented in minutes.
Example: 308
SHFT_HOURS decimal(5,2) Yes Description: The employee‟s shift total worked
time represented in hours
Example: 5.13
SHFT_EDDAT datetime Yes Description: The date the shift was edited in
Aloha
Example: 2012-06-18
SHFT_EDTIM nvarchar(255) Yes Description: The time the shift was edited in
Aloha
Example: 10:12:00 (hh:mm:ss)
SHFT_EDMGR nvarchar(255) Yes Description: The manager‟s lastname,
firstname that performed the shift edit in Aloha
Note: “EOD” will indicate that the shift was
ended by the EOD process.
Example: Lolita Newchurch
SHFT_OPEN nvarchar(255) Yes Description: Identifies whether the employee
was clocked out by the manager or by EOD
process.
Y= Employee was clocked out by the manager
or by EOD process.
N= Employee clocked himself out.
Example: N

18 ST_AlohaGndBreakInfo * Data Mart


Field Type Nulls? Comments
SHFT_CKMGR int Yes Description: The manager‟s ID who ended the
shift.
Note: A „NULL‟ value & the SHFT_OPEN field =
Y, indicates auto-clockout by EOD process.
Example: 0
BRK_PAID nvarchar(255) Yes Description: Is the break taken by the
employee a paid break?
Y = Break is paid according to the Aloha break
rule
N = Break is unpaid according to the Aloha
break rule
Example: Y
BRK_INVALD nvarchar(255) Yes Description: Is the break invalid?
Y = Break is invalid according to the Aloha
break rule
N = Break is valid according to the Aloha
break rule
Example: N
BRK_EDIT nvarchar(255) Yes Description: Was the break edited from the
FOH?
Y = Break was edited from FOH
N = Break was not edited from FOH
Example: N
BRK_EDMGR nvarchar(255) Yes Description: The manager‟s
lastname/firstname that edited, created, or
deleted the break shift in Aloha.
Note: Same as the MANAGER field in Aloha‟s
GNDBREAK.DBF.
EOD will indicate that the shift was ended by
the EOD process.
Example: Newchurch, Lolita
BRK_EDDATE nvarchar(255) Yes Description: The date the break was edited.
Example: 10/15/2012
BRK_EDTIME nvarchar(255) Yes Description: The time the break was edited.
Example: 11:21:00 (hh:mm:ss)
BRK_MINMIN int Yes Description: This is the earned break minutes,
also known as the minimum break minutes, in
the Break Rule setting in Aloha.
Example: 30
BRK_INHR int Yes Description: The employee‟s break start hour
Example: 10
BRK_INMIN int Yes Description: The employee‟s break start
minutes
Example: 29
BRK_OUTHR int Yes Description: The employee‟s break end hour
Example: 11
BRK_OUTMIN int Yes Description: The employee‟s break end
minutes
Example: 0
BRK_MIN int Yes Description: The employee‟s total break in
minutes
Example: 10
BRK_HOURS decimal(5,2) Yes Description: The employee‟s total break in
hours
Example: 0.45
BRK_RULEID int Yes Description: Aloha break rule ID for the break
Example: 1

Data Mart ST_AlohaGndBreakInfo * 19


Field Type Nulls? Comments
BRK_RDTID int Yes Description: The Aloha Break rule detail
information associated with BRK_RULEID.
Example: 1
BRK_WAVBLE nvarchar(255) Yes Description: Is the Break eligible to be waived?
Y/N is based on the Aloha break rule is set to
be waivable & employee worked inside the
threshold.
Example: Y
BRK_WAIVED int Yes Description: Based on the break rule settings
and the action of the employee on the Aloha
POS if the waive option is selected or not.
0 =BREAKNOTWAIVED: Break is set to “Note
waivable”, or break is mandatory & did not
prompt to waive.
1 = BREAKAUTOWAIVED
2 = BREAKWAIVED_ATCLOCKIN
3 = BREAKWAIVED_ATCLOCKOUT
4 = BREAKWAIVED_REFUSED_ATCLOCKIN
5 = BREAKWAIVED_REFUSED_ATCLOCKOUT
6 = BREAKWAIVED_NOTPROMPTED
Example: 0
BRK_WINMIS nvarchar(255) Yes Description: Did the employee start their break
outside or inside the threshold based on the
break rule defined in Aloha Manager? Y/N
Y = The employee started the break outside
the defined and enforced break start
window. Or the employee did not take the
break.
N = The employee started the break inside the
defined and enforced break start window.
Or the Break Start window is NOT
enforced.
Example: N
BRK_PENLTY nvarchar(255) Yes Description: Did employee earn a penalty pay?
Y/N based on the Aloha break rule settings.
Note: Penalty earned would be per shift per
Break Rule.
Y = Employee earned a penalty pay
N = Employee did not earn a penalty pay Or
penalty pay is not applicable
Example: N
BRK_COMPL nvarchar(255) Yes Description: Is the break compliant? Y/N
Based on certain conditions set in Aloha
Manager.
Example: Y

Index Name Unique Clustered Fields


PK_ST_ALOHAGNDBREAKINFO Yes Yes RecordNumber

* Table will not contain an index on the replicated database.

20 ST_AlohaGndBreakInfo * Data Mart


ST_AlohaSalesMixTransactions_RealTimeFeed *

Description: : This table provides sales mix transaction information, imported from the Aloha POS, by
site, by business date, by check number, by employee, including whether the item was sold as a quick
combo. This table is updated when the Aloha POS import is performed with „Sales Mix‟ import type
selected. Additional import options must be enabled to capture the transactional sales mix from Aloha.
Please contact your NCR Back Office support representative to activate. This table will only include
dates where imports occurred with this option enabled.

Triggered by Export_STAlohaSalesMixTransactions_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordNumber bigint No Description: A unique record identifier.
Example: 12
SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups. Only site types
of „2‟ (store) will be supported.
Example: 1456
BusinessDate datetime No Description: Business Date of the
transaction
Example: 2012-03-01

Data Mart ST_AlohaSalesMixTransactions_RealTimeFeed * 21


Field Type Nulls? Comments
Timesold datetime No Description: The hours & minutes of when
the transaction was completed.
Example: 2012-03-01 14:05:00.000
Uses Site Local Time
AlohaSalesType int Yes Description: Identifies the type of
transaction as imported from Aloha:
0 = Normal sale
1 = Refund
2 = Revenue Item
3 = Refunded Revenue Item
Example: 0
AlohaItemPOSCode int Yes Description: The Aloha item‟s POS code
as defined in Back Office Manager| Items|
Item Maintenance.
Example: 185005
InternalMenuLinkItemNumber int No Description: Item Number (internal).
Note: Items are defined in ST_Items.
Example: 1001865
AlohaParentItemPOSCode int Yes Description: If the item is a modifier to
another item, this value will reflect the
POS code of the parent item. Otherwise,
the value will be zero.
Example: 140101
AlohaParentModifierPOSCode int Yes Description: If the item is a modifier to
another item, this value will reflect the
POS code of the modified item.
Otherwise, the value will be zero.
Example: 1001865
ItemEnteredTime datetime No Description: The actual time in hours,
minutes, and seconds, of when the item
was entered on the POS as imported from
Aloha.
Note: Time is based on the local time of
the Aloha POS.
Example: 2012-03-01 09:08:40.000
OrderMode int Yes Description: The order mode ID number
imported from Aloha. This value is
configured in Aloha and normally
represents Take Out, Dine-in, and
Delivery.
Example: 1
InclusiveTax decimal(19, 3) Yes Description: Inclusive tax amount for the
item as calculated in Aloha.
Example:1.500
AlohaCheckNumber int Yes Description: The receipt number of the
Aloha transaction.
Example: 4001
AlohaEmployeePOSCode int Yes Description: Employee POS Code as
defined in Back Office Switchboard|
Labor| Employees|
EmployeeMaintenance.
Example: 2006
InternalEmployeeNumber int Yes Description: Employee Number (internal).
If the AlohaEmployeePOSCode does not
match an active NCR Back Office
Employee, this value will be null.
Note: Employees are defined in
ST_Employees
Example: 1002863

22 ST_AlohaSalesMixTransactions_RealTimeFeed * Data Mart


Field Type Nulls? Comments
AlohaSellingPrice decimal(19, 3) Yes Description: The actual selling price of the
item as sold in Aloha.
Example: 2.750
AlohaDiscountedPrice decimal(19, 3) Yes Description: The item‟s price after
discounts were applied.
Example: 1.750
QuickComboID int Yes Description: Quick Combo identifier, as
configured in Aloha, that indicates
whether an item was sold as a Quick
Combo in Aloha. If this item was not sold
as part of a Quick Combo, the value will
be zero.
Example: 1162
QuickComboPrimary bit No Description: Identifies whether the item
was the primary item for Quick Combo.
0 = Not a primary item
1 = Primary item
Example: 1
PrimaryItemNumber int Yes Description: If the item was sold as part
of a Quick Combo in Aloha, this number
references the NCR Back Office internal
item number of the primary item in the
Quick Combo.
Example: 1001621
QuickComboUpsell bit Yes Description: Identifies the item as an
upsell item. Example: Regular sell = a
hamburger & sm fries, Upsell =
hamburger & lg fries.
0 = regular sale
1 = upsell
Example: 0

Index Name Unique Clustered Fields


PK_ST_AlohaSalesMixTransactions_RealTimeFeed Yes Yes RecordNumber

* Table will not contain an index on the replicated database.

Data Mart ST_AlohaSalesMixTransactions_RealTimeFeed * 23


ST_BOANETtoHQParameters

Description: Used by NCR Back Office Export Application to keep track of export
functionality. INTERNAL ONLY.

Field Type Nulls?


ParameterNumber int No
ParametersXML ntext Yes

Index Name Unique Clustered Fields


PK_ParameterNumber Yes Yes ParameterNumber

24 ST_BOANETtoHQParameters Data Mart


ST_Budgets

Description: Budget amount by Site, by BusinessDate

Time Frame: This table will include each day‟s budget (by day) for the selected timeframe in this
export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: ite Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Also only site types of „2‟ (store) are
supported.
Example: 1456
BusinessDate datetime No Description: Business Date for the allocation
amount.
If a week or period is selected, a value for
each business day is exported.
If a week or period is selected, a value for
each business day is exported.
Example: 2007-03-26
DataDefinitionNumber int No Description: Internal Number associated
with the Source Data defined in Data
Definitions in Back Office Manager.
Note: Data Definitions are defined in
ST_DataDefinitionConfiguration
Example: 1016924
BudgetAmount decimal (19,5) Yes Description: Amount is the value for the
daily allocation that is entered by manager
or imported.
Note: If the Budget‟s „Time Interval‟ is
Week or Period, daily allocation budget
records will be created.
Example: 581.1345

Index Name Unique Clustered Fields


PK_ST_Budgets Yes Yes BusinessDate, SiteNumber,
DataDefinitionNumber

Data Mart ST_Budgets 25


ST_Calendars

Description: Site-related Calendar information

Triggered by Export_ProcessSTCalendars.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
BusinessCalendarNumber int No Description: Business Calendar Number
(internal)
Example: 1000609
BusinessCalendarName nvarchar (100) Yes Description: Business Calendar Name
Example: Fiscal – Radiant Systems
CalendarType bit No Description: Fiscal or Payroll Calendar
0 = Fiscal
1 = Payroll
Example: 0

Index Name Unique Clustered Fields


PK_ST_Calendars Yes Yes SiteNumber, BusinessCalendarNumber,
CalendarType

26 ST_Calendars Data Mart


ST_CalendarSubperiods *

Description: Subperiod information.

Triggered by Export_STCalendarSubperiods.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


BusinessCalendarNumber int No Description: Business Calendar Number
(internal)
Note: Calendars are defined in
ST_Calendars
Example: 1000609
BusinessCalendarSubperi int No Description: Business Calendar Subperiod
odNumber Number (internal)
Example: 1456
Year smallint No Description: Year
Example: 2011
Period smallint No Description: Period
Example: 4
Week smallint No Description: Week
Example: 3
StartDate datetime No Description: Start date of the defined
subperiod
Example 2011-12-29
EndDate datetime No Description: End date of the defined
subperiod
Example 2012-01-05

Index Name Unique Clustered Fields


PK_ST_CalendarSubperiods Yes Yes BusinessCalendarNumber,
BusinessCalendarSubperiodNumber

* Table will not contain an index on the replicated database.

Data Mart ST_CalendarSubperiods * 27


ST_CostofGoods

Description: Beginning and Ending Inventory and what was used by Item. Runs thru the Food Cost
Calculations.

Triggered by Export_ProcessSTCostOfGoods.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SubPeriod int No Description: Sub Period Number (internal)
Example: 75
SiteNumber int No Description: Site Number (internal)
Example: 1456

28 ST_CostofGoods Data Mart


Field Type Nulls? Comments
StoreID nvarchar (25) No Description: Store ID
Example: 1311
RawMaterialItemCatNum int Yes Description: Raw Material Item Category
Number (internal)
Example: 1000009
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: Nuggets
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 4110-01
RawMaterialItemNumber int No Description: Item Number (internal)
Example: 1000554
RawMaterialItemID nvarchar (40) Yes Description: Item ID
Example: 272
RawMaterialItemName nvarchar (250) Yes Description: Raw Material Item Name
Example: Dip, Buffalo Ranch
RawMaterialItemUnitNumber int No Description: Item Unit Number (internal)
Example: 6
RawMaterialItemUnitName nvarchar (50) No Description: Item Unit Name
Example: EA
BeginningOnHandCount float Yes Description: Beginning On-Hand Count
aka Beginning Inventory Quantity
Example: 145
Purchases float Yes Description: Quantity Purchased
Example: 64
EndingOnHandCount float Yes Description: Ending On-Hand Count
aka Ending Inventory Quantity
Example: 148
UsedAmount float Yes Description: Actual Quantity Usage
Example: 61
EndingItemCost money Yes Description: Ending Item Cost
Example: 1.27
BeginningInventory$ float Yes Description: Beginning On-Hand Value
Example: 184.15
Purchase$ float Yes Description: Value of Purchases
Example: 81.28
EndingInventory$ float Yes Description: Ending On-Hand Value
Example: 187.96
Used$ float Yes Description: Actual Usage Value
Example: 77.47
SubPeriodStartDate datetime Yes Description: The start date of the subperiod
Example: 2010-02-05
SubPeriodEndDate datetime Yes Description: The end date of the subperiod
Example: 2010-02-11
EndingInventoryUnitCost float Yes Description: Cost, derived from the raw
items ending inventory value unit cost. Must
have beginning inventory, must have ending
inventory, contract pricing, FIFO, will be
used to determine the values.
Example: 2.24

Index Name Unique Clustered Fields


PK_ST_CostOfGoods Yes Yes SubPeriod, SiteNumber,
RawMaterialItemNumber,
RawMaterialItemUnitNumber
IX_ST_CostOfGoods_StartDt No No SubPeriodStartDate

Data Mart ST_CostofGoods 29


ST_CustomFPZ *

Description: This table provides custom FPZ sales information from an external source, by site, by
POS terminal and by business date. The table content will be based on the data imported using the
Integration Definition: „Data Mart Feed – Custom FPZ‟ import (FPZSALES.DBF).

Triggered by Export_STCustomFPZ.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordNumber bigint No Description: Record Number
This is an Identity field type. Do not use.
Example: 141
SiteNumber int No Description: Site Number (internal).
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: The business date of the
imported Custom FPZ data.
Example: 2012-06-10

30 ST_CustomFPZ * Data Mart


Field Type Nulls? Comments
ImportDateTime datetime No Description: Date & time the Data Mart
Feed – Custom FPZ was generated in UTC.
Example: 2011-04-05 00:23:15.980
Uses UTC
FPZ_DOB smalldatetime Yes Description: Date of Business (DOB), as
imported from FPZSALES.
Example: 2012-01-05
FPZ_DT smalldatetime Yes Description: The date the file was created,
as imported from FPZSALES.
Example: 2011-06-01
FPZ_TM smalldatetime Yes Description: The time the file was created,
as imported from FPZSALES.
Example: 22:38:08
Uses UTC
FPZ_STRID float Yes Description: The STORE ID, as imported
from FPZSALES.
Example: 1234
FPZ_POSNO int Yes Description: Aloha POS Terminal ID, where
the FPZSALES occurred.
Example: 1
FPZ_ZNUM int Yes Description: Numeric identifier for the file
creation, where the FPZSALES occurred.
Example: 501
FPZ_G1 float Yes Description: The Gross Sales (G1), as
imported from FPZSALES.
Example: 985.80
FPZ_N1 float Yes Description: The Net Sales (N1), as
imported from FPZSALES.
Example: 785.80
FPZ_G2 float Yes Description: The Gross Sales (G2), as
imported from FPZSALES.
Example: 985.80
FPZ_N2 float Yes Description: The Net Sales (N2), as
imported from FPZSALES.
Example: 785.80
FPZ_G3 float Yes Description: The Gross Sales (G3), as
imported from FPZSALES.
Example: 985.80
FPZ_N3 float Yes Description: The Net Sales (N3), as
imported from FPZSALES.
Example: 785.80
FPZ_G4 float Yes Description: The Gross Sales (G4), as
imported from FPZSALES.
Example: 985.80
FPZ_N4 float Yes Description: The Net Sales (N4), as
imported from FPZSALES.
Example: 785.80
FPZ_G5 float Yes Description: The Gross Sales (G5), as
imported from FPZSALES.
Example: 985.80
FPZ_N5 float Yes Description: The Net Sales (N5), as
imported from FPZSALES.
Example: 785.80
FPZ_G6 float Yes Description: The Gross Sales (G6), as
imported from FPZSALES.
Example: 985.80

Data Mart ST_CustomFPZ * 31


Field Type Nulls? Comments
FPZ_N6 float Yes Description: The Net Sales (N6), as
imported from FPZSALES.
Example: 785.80

Index Name Unique Clustered Fields


PK_ST_CustomFPZ Yes Yes RecordNumber

* Table will not contain an index on the replicated database.

32 ST_CustomFPZ * Data Mart


ST_DataDefinitionConfiguration *

Description: Data Definitions by the DataDefinitionNumber (internal number).

Triggered by Export_STDataDefinitionConfiguration.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


DataDefinitionNumber int No Description: Data Definition Number
(Internal).
Example: 1016921
DataDefintionName nvarchar(50) Yes Description: The Data Definition Name as
defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Name field.
Example: Utilities
DataDefintionDescription nvarchar (100) Yes Description: The Data Definition Description
as defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Description field.
Example: Utilities - Allocation
SourceNumber int No Description: An internal number that
corresponds with the Source Data as
defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Source Data
0 = None
1 = Calculation
2 = CashReconciliation
3 = Deposits
4 = LaborPayroll
5 = FoodCost
6 = AllocationValue
7 = AllocationPercent
8 = DayPartSales
9 = DayPartGuests
10 = Schedule
11 = KeyVolumeIndicator
12 = RecommendedHours
13 = FoodCostItem
14 = ActualRecommendedHours

Data Mart ST_DataDefinitionConfiguration * 33


Field Type Nulls? Comments
(continued) 15 = TipShare
16 = LaborPayTypes
17 = Accruals
18 = HoursOfOperations
19 = RecommendedHoursByJob
20 = Speed of Service
21 = ForecastedSales
22 = ForecastedGuests
23 = WasteCostByRawItemCategory
Example: 6
DecimalPlaces tinyint Yes Description: The number of decimal places
as defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Decimal Places field.
Example: 2
AllocationEntrySequence smallint Yes Description:The Allocation Entry Sequence
as defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Allocation Sequence field.
Note: Will only display when the „Source
Data‟ field is „Allocation – Value‟ or
„Allocation – Percent‟
Example: 1
BudgetType smallint Yes Description: The Budget Type in an internal
number that is based on the Data Definition
setup defined in Back Office Manager|Data
Definition|Data Definition
Maintenance|Budget by field.
0 = None (This data definition is not
budgeted)
1 = Value (This data definition is budgeted
by a dollar amount)
2 = Percent(This data definition is budgeted
by a percent value)
3 = Calculation (This data definition uses
the budgeted numbers for the
calculation‟s formula)
Example: 1
BudgetEntrySequence smallint Yes Description: Budget Entry Sequence is a
number that displays the Budget Name in
sequential order, as defined in Back Office
Manager|Data Definition|Data Definition
Maintenance|Budget Sequence field.
Example: 10

Index Name Unique Clustered Fields


PK_ST_DataDefinitionConfiguration Yes Yes DataDefinitionNumber

* Table will not contain an index on the replicated database.

34 ST_DataDefinitionConfiguration * Data Mart


ST_Deposits

Description: Summary Data of Deposits.

Triggered by Export_ProcessSTDeposits.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SalesDate datetime No Description: Business Date
Example: 2007-03-26
DepositTime datetime No Description: Time of Deposit
Example: 2007-04-15 14:53:34.000
Uses Site Local Time
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
BagNumber nvarchar (100) Yes Description: Bag Number
Example: 13110573
Amount float Yes Description: Amount of Deposit
Example: 1745.75

Data Mart ST_Deposits 35


Field Type Nulls? Comments
UserID nvarchar (100) Yes Description: Person‟s name who modified the
record
Example: Cristina Andrianna
Notes nvarchar (100) Yes Description: Notes entered about the deposit
Example: Mid-day deposit
CreatedByName nvarchar (100) Yes Description: Person‟s name who entered the
deposit
Example: Francesca Caterina
PreVerifiedAmount decimal (19, 3) Yes Description: The amount before deposit was
verifed
Example: 1750.50
OpenAmount decimal (19, 3) Yes Description: The additional amount
added/subtracted from the deposit. User
entered.
Example: 10.25
VerifiedAmount decimal (19, 3) Yes Description: The amount verified. User
entered. Example: 1745.50
VerifiedTime datetime Yes Description: The date and time the deposit
was verified.
Example: 2007-04-16 14:43:34.000
Uses Site Local Time
VerifiedByName nvarchar (100) Yes Description: Person‟s name who verified the
deposit
Example: Mary McIvor
ValidatedAmount decimal (19, 3) Yes Description: The amount validated. User
entered.
Example: 1745.75
ValidatedTime datetime Yes Description: Local date and time the record
was validated.
Example: 2007-04-16 14:43:34.000
Uses Site Local Time
ValidatedByName nvarchar (100) Yes Description: Person‟s name who validated the
deposit
Example: Beth Johnson

Index Name Unique Clustered Fields


PK_ST_Deposits Yes Yes SiteNumber, SalesDate, DepositTime

36 ST_Deposits Data Mart


ST_EmpJobRates

Description: Employee Job and Rate Data

Triggered by Export_ProcessSTEmpJobRates.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) Yes Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobName nvarchar (100) Yes Description: Current Job Name
Example: Assistant General Manager
StartDate datetime No Description: Start Date
Example: 2007-06-24
EndDate datetime Yes Description: End Date
Example: 2007-07-01
PayReasonNumber int Yes Description: Pay Reason Number (internal)
Example: 6
PayReasonName nvarchar (100) Yes Description: Pay Reason Name
Example: New Hire

Data Mart ST_EmpJobRates 37


Field Type Nulls? Comments
PerformanceRatingNumber int Yes Description: Performance Rating Number
(internal)
Example: 2
PerformanceRatingName nvarchar (100) Yes Description: Performance Rating Name
Example: Meets Expectations
Rate decimal (19, 3) Yes Description: Pay Rate
Example: 7.85
PrimaryJob bit Yes Description: Primary Job
0 = Primary Job
1 = Not Primary Job
Example: 0
ModifiedOn datetime Yes Description: Date Record was Modified
Example: 2007-07-01
ModifiedBy int Yes Description: User Number of Person who
Modified Record (internal)
Example: 1002374
ModifiedByName nvarchar (100) Yes Description: Person‟s Name who Modified
Record
Example: Agrepina Smith

Index Name Unique Clustered Fields


PK_ST_EmpJobRates Yes Yes SiteNumber, BOAEmployeeNumber,
JobNumber, StartDate

38 ST_EmpJobRates Data Mart


ST_EmpJobTrans

Description: Job Transactions by JOB by EMPLOYEE. Allows you to see last and current job
information.

Triggered by Export_ProcessSTEmpJobTrans.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


TransactionNumber int No Description: Transaction Number
(internal)
Example: 14
SiteNumber int No Description: Site Number (internal)
Example: 1456

Data Mart ST_EmpJobTrans 39


Field Type Nulls? Comments
StoreID nvarchar (25) No Description: Store ID
Example: 1311
Timestamp datetime No Description: Timestamp
Example: 2007-06-25 17:08:56.000
Uses UTC
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number
(internal)
Example: 1000626
JobName nvarchar (100) No Description: Current Job Name
Example: Assistant General Manager
JobID nvarchar (100) Yes Description: Current Job ID
Example: 401
StartDate datetime No Description: Start Date
Example: 2007-06-25
EndDate datetime Yes Description: End Date
Example: 2007-07-01
PayReasonNumber int Yes Description: Pay Reason Number
(internal)
Example: 6
PayReasonName nvarchar (100) Yes Description: Pay Reason Name
Example: New Hire
PerformanceRatingNumber int Yes Description: Performance Rating Number
(internal)
Example: 2
PerformanceRatingName nvarchar (100) Yes Description: Performance Rating Name
Example: Meets Expectations
Rate decimal (19, 3) Yes Description: Pay Rate
Example: 7.85
PrimaryJob bit Yes Description: Primary Job
0 = Primary Job
1 = Not Primary Job
Example: 0
NewEndDate datetime Yes Description: End Date
Example: 2007-07-01
NewPayReasonNumber int Yes Description: Pay Reason Number
(internal)
Example: 6
NewPayReasonName nvarchar (100) Yes Description: Pay Reason Name
Example: New Hire
NewPerformanceRatingNumber int Yes Description: Performance Rating Number
(internal)
Example: 2
NewPerformanceRatingName nvarchar (100) Yes Description: Performance Rating Name
Example: Meets Expectations
NewRate decimal (19, 3) Yes Description: Pay Rate
Example: 7.85
NewPrimaryJob bit Yes Description: Defines if this is the Primary
Job for the Employee
0 = Not Primary Job
1 = Primary Job
Example:1
ModifiedByNumber int Yes Description: User Number of Person who
Modified Record (internal)
Example: 1002374

40 ST_EmpJobTrans Data Mart


Field Type Nulls? Comments
ModifiedByName nvarchar (100) Yes Description: Person‟s Name who Modified
Record
Example: Hess Chu
BusinessDate datetime Yes Description: Business Date
Example: 2007-03-26
JobPayrollCode nvarchar (25) Yes Description: Job Payroll Code
Example: BIO12345

Index Name Unique Clustered Fields


PK_ST_EmpJobTrans Yes Yes Timestamp, SiteNumber,
BOANETEmployeeNumber,
TransactionNumber, JobNumber,
StartDate
IX_ST_EmpJobTrans No No SiteNumber, BusinessDate

Data Mart ST_EmpJobTrans 41


ST_EmpJobTransCustom

Description: Custom Table containing Job Transactions by JOB by EMPLOYEE. Allows you to see last
and current job information.

Triggered by Export_ProcessSTEmpJobTransCustom.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
Timestamp datetime No Description: Timestamp
Example: 2007-06-25 17:08:56.000
Uses UTC
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (20) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobName nvarchar (100) No Description: Current Job Name
Example: Assistant General Manager
EffectiveDate datetime No Description: Effective Date
Example: 2007-05-07
Rate decimal (19, 3) Yes Description: Rate:
Example: 8.00
JobReason nvarchar (3) Yes Description: Job Reason
Example: NH

42 ST_EmpJobTransCustom Data Mart


Field Type Nulls? Comments
OldEffectiveDate datetime Yes Description: Last Effective Date
Example: 2007-03-18
OldJobNumber int Yes Description: Last Job Number (internal)
Example: 1000628
OldJobName nvarchar (100) Yes Description: Last Job Name
Example: Restaurant General Manager
OldRate decimal (19, 3) Yes Description: Last Job Rate
Example: 18.51

Index Name Unique Clustered Fields


PK_ST_EmpJobTransCustom Yes Yes SiteNumber, EffectiveDate, Timestamp,
BOANETEmployeeNumber, JobNumber

Data Mart ST_EmpJobTransCustom 43


ST_EmployeeClockPunchHistory_FromView *

Description: This table provides employee punch and punch edit information by site, by employee, by
day. These values can be used to view historical information regarding shift adjustments. In addition,
modified-by data is captured as well as the status of employee POS acknowledgments.

Shift adjustments can be made on the NCR Back Office|Labor|Payroll|Shifts|Modify Shifts|Adjust


Shifts switchboard and can be viewed on the „Shift Edit History‟ report (Back Office Labor Switchboard
(Back Office Switchboard|Labor|Reports).

Triggered by Export_STEmployeeClockPunchHistory_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab

Field Type Nulls? Comments


SiteNumber int No Description: Site number (internal)
Note: Sites are defined in
„ST_SitesAndSiteGroups.SiteNumber‟.
Example: 1456

44 ST_EmployeeClockPunchHistory_FromView * Data Mart


Field Type Nulls? Comments
BusinessDate datetime No Description: Business date of the time
punch.
Example: 2012-09-29
PunchEditType tinyint No Description: Time punch edit type
1 = Add
2 = Delete
3 = ModifyBefore – shift segment before
editing occurs
4 = ModifyAfter – shift segment after editing
occurs
5 = NoEdit
Example: 3
InternalEmployeeNumber int No Description: Employee number (internal)
Note: Employees are defined in
„ST_Employees.EmployeeNumber‟.
Example: 1001243
EmployeeName nvarchar(100) No Description: Name of Employee
Example: Jones, Bob
InternalJobNumber int No Description: Job number (internal)
Note: Job numbers are defined in
„ST_Jobs.JobNumber‟.
Example: 1001274
JobcodeName nvarchar(100) No Description: Job name for the
InternalJobNumber.
Example: Bartender
ClockIn datetime No Description: POS Clock-in time of the
employee for the specified business date.
Note: If manually entered in Back Office
Switchboard|Labor|Payroll|Adjust Shifts, the
user enters date & time.
Example: 2013-04-09 16:26:33.900
Uses Site Local Time
ClockOut datetime Yes Description: POS Clock-out time of the
employee for the specified business date.
Note: If manually entered in Back Office
Switchboard|Labor|Payroll|Adjust Shifts, the
user enters date & time.
Example: 2013-04-09 20:26:33.900
Uses Site Local Time
PunchTypeNumber tinyint No Description: Punch type number (internal)
1 = Worked
2 = Paid Break
3 = Unpaid Break
Example: 1
PunchTypeName nvarchar(100) No Description: Punch type name
Example: Worked
Hours decimal(19,3) No Description: Total hours for shift segment. A
shift segment is defined as the total span of
hours (worked, paid or unpaid break)
between a „ClockIn‟ and „ClockOut‟ punch.
Example: 3.17
TimeClockEditReasonNumber int Yes Description: Reflects the shift edit reason
number (internal) as entered in the „Reason‟
dropdown (Back Office Switchboard |Labor
|Payroll|Adjust Shifts)
Note: Time clock edit reasons are defined in
„ST_TimeClockEditReason_FromView‟.
Example: 3

Data Mart ST_EmployeeClockPunchHistory_FromView * 45


Field Type Nulls? Comments
ModifiedByNumber int Yes Description: Reflects the user number
(internal) that modified the time punch
either through an import or through manual
entry.
Note: User numbers are defined in
„ST_Users_RealTimeFeed.UserNumber‟.
Example: 1001192
CreatedBy int Yes Description: Reflects the user number
(internal) that created the record either
through an import or manually entered.
Note: User numbers are defined in
„ST_Users_RealTimeFeed.UserNumber‟.
Example: 1456432
CreatedTime datetime No Description: Date and time that the record
was created.
Example: 2013-04-09 16:26:33.900
Uses UTC
RecordNumber bigint No Description: Unique record identifier number
(internal)
Note: This is an identity field type. Do not
use.
Example: 12
EmployeePOSCode nvarchar(50) Yes Description: Employee POS code.
The value in this field is used to clock-in to
the POS system. The POS code can be
entered in the „Employee ID‟ field (NCR Back
Office| Labor Switchboard |Employees
|Employee Maintenance|Employee tab)
Example: 1024
POSJobcodeID nvarchar(50) Yes Description: POS Jobcode ID as is imported
from the POS.
Example: 1111
BusinessDateImport datetime Yes Description: Actual business date and time
when a POS import is performed.
Example: 2012-06-12 12:00:34.160
Uses Site Local Time
SourceOfEdit int Yes Description: System where punch was
edited.
0 = NCR Back Office
1 = POS
Example: 0
POSShiftID int Yes Description: Employee shift number for the
day (imported from POS).
For clock-ins on the same day:
0 = First shift clock-in for the day
1 = Second shift clock-in for day
etc.
Example: 1
POSBreakID int Yes Description: Incremental break number –
unique for valid breaks across all employees
for the day (imported from POS).
For breaks on the same day:
1 = First break taken for the day
2 = Second break taken for the day
etc.
Example: 10

46 ST_EmployeeClockPunchHistory_FromView * Data Mart


Field Type Nulls? Comments
POSAcknowledgementStatus int Yes Description: POS Acknowledgment Status
Note: A status will change when an
employee has acknowledged a time punch
edit.
0 = Pending response (employee has not
responded or has not clocked in)
1 = Yes (approved)
2 = No (not approved)
Null = Site not running Aloha version 12/1 or
higher or feature not enabled.
Example: 2

Index Name Unique Clustered Fields


ST_EmployeeClockPunchHistory_FromView Yes Yes RecordNumber

* Table will not contain an index on the replicated database.

Data Mart ST_EmployeeClockPunchHistory_FromView * 47


ST_EmployeePayrollDay

Description: Actual Daily Payroll (COST) by SITE, by DATE by EMPLOYEE

Triggered by Export_ProcessSTEmployeePayrollDay.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BOANETEmployeeNumber Int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
PayTypeID int No Description: Pay Type ID
Note: Anything other than 0, -1, -2 is a non-
worked hour.
0 = Regular
-1 = Overtime
-2 = Double Overtime
Example: 0
PayTypeName nvarchar (100) Yes Description: Pay Type Name
Note: This will only identify non-worked hour
names
Example: Shift Diff. ($)
BusinessDate datetime No Description: Business Date
Example: 2007-03-26
Dollars decimal (19, 3) Yes Description: Total Labor Dollars
Example: 47.20

48 ST_EmployeePayrollDay Data Mart


Field Type Nulls? Comments
Hours decimal (19, 3) Yes Description: Total Labor Hours
Example: 5.90
Rate decimal (19, 3) Yes Description: Rate of Pay (Hourly)
Example: 8.00
JobID nvarchar (25) Yes Description: Job ID
Example: 11

Index Name Unique Clustered Fields


PK_ST_EmployeePayrollDay Yes Yes SiteNumber, BusinessDate,
BOANETEmployeeNumber, JobNumber,
PayTypeID

Data Mart ST_EmployeePayrollDay 49


ST_EmployeePayrollDayPenaltyHours *

Description: This table provides specific information about each penalty that has been assessed for an
employee due to a violation of break or shift rules. Due to the dynamic nature of penalty hours, this
table will be updated every time the payroll is refreshed for a pay period – which can be triggered by
a POS „Labor‟ import, shift adjustment, employee profile change, or through Back Office
Manager|Time Clock Utilities.

Triggered by Export_STEmployeePayrollDayPenaltyHours.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business date where the penalty
hour occurred
Example: 2011-02-23
InternalEmployeeNumber int No Description: Employee Number (internal). An
employee may incur multiple penalties in a
single day.
Note: Employees are defined in
ST_Employees.
Example: 504931
JobNumber int No Description: Job Number (internal)
Note: Jobs are defined in ST_Jobs
Example: 1000626
PenaltyType int No Description: The break or shift rule that
caused the penalty:
-3 = Split Shift
-4 = Span Shift
-5 = Call In
-6 = Break Penalty
-7 = Paid Break Penalty
Example: -3

50 ST_EmployeePayrollDayPenaltyHours * Data Mart


Field Type Nulls? Comments
Amount decimal (19,3) Yes Description: The currency value of the
penalty earned
Example: 6.00
Hours decimal (19,3) Yes Description: The number of penalty hours
Example: 0.75
Rate decimal (19,3) Yes Description: The rate of pay for the penalty
earned
Example: 8.00
LastModifiedTime datetime No Description: The last time a refresh of the
payroll occurred (see description)
Example: 2011-02-24 14:32:15.000

Index Name Unique Clustered Fields


PK_ST_EmployeePayrollDayPenaltyHours Yes Yes SiteNumber, BusinessDate,
InternalEmployeeNumber,
JobNumber, PenaltyType

* Table will not contain an index on the replicated database.

Data Mart ST_EmployeePayrollDayPenaltyHours * 51


ST_EmployeePunches

Description: Clock-in and Clock-out by SITE by DATE by EMPLOYEE by SHIFT.

Triggered by Export_ProcessSTEmployeePunches.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobID nvarchar (25) Yes Description: Job ID
Example: 11
PunchTypeID smallint No Description: Punch Type ID
1 = Worked
2 = Paid Break
3 = Unpaid Break
Example: 1
BusinessDate datetime Yes Description: Business Date
Example: 2007-03-26

52 ST_EmployeePunches Data Mart


Field Type Nulls? Comments
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
PayPeriodYear smallint Yes Description: Pay Period Fiscal Year
Example: 2007
PayPeriodNumber float Yes Description: Pay Period Number
Example: 4
ClockIn datetime No Description: Clock-in Time
Example: 2007-03-31 14:45:00.000
If manual, user enters date & time.
If imported from POS, uses Local date & time.
ClockOut datetime Yes Description: Clock-out Time
Example: 2007-03-31 16:45:00.000
If manual, user enters date & time.
If imported from POS, uses Local date & time.
Hours decimal (19, 3) Yes Description: Total Labor Hours
Example: 4.25
Source nvarchar (50) Yes Description: Source of Information
Example: Betty Smith
TimeClockEditReason nvarchar (50) Yes Description: Time clock edit reason
Example: Forgot to clock out

Index Name Unique Clustered Fields


PK_ST_EmployeePunches Yes No BOANETEmployeeNumber,
SiteNumber, ClockIn
IX_ST_EmployeePunches_SiteBusDt Yes Yes SiteNumber, BusinessDate

Data Mart ST_EmployeePunches 53


ST_EmployeePunchesRealTime *

Description: Clock-in & Clock-out punches by employee, by day, by site, by shift, with waive break
indicators for meal & rest breaks.

Triggered by Export_STEmployeePunchesRealTime.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


InternalEmployeeNumber int No Description: Employee Number (internal)
Note: Employees are defined in
ST_Employees.
Example: 1002863
SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
JobNumber int No Description: Job number for employee‟s
punch record (internal)
Note: Jobs are defined in ST_Jobs
Example: 1012689

54 ST_EmployeePunchesRealTime * Data Mart


Field Type Nulls? Comments
PunchTypeID tinyint No Description: Punch type ID:
1 = Worked
2 = Paid Break
3 = Unpaid Break
Example: 1
BusinessDate datetime No Description: Business date associated
with the employee punch.
Example: 2011-10-27
ClockIn datetime No Description: Clock-In time of the
employee for the shift for the specified
business date.
Note: If manually entered in Back Office
Switchboard|Labor|Payroll|Adjust Shift,
user enters date & time.
If imported from POS, uses local date &
time.
Example: 2011-10-24 14:02:00.000
ClockOut datetime Yes Description: Clock-out time of the
employee for the shift for the specified
business date.
Note: If manually entered in Back Office
Switchboard|Labor|Payroll|Adjust Shift,
user enters date & time.
If imported from POS, uses local date &
time.
Example: 2011-10-24 16:02:00.000
Shift tinyint No Description: An internal number that
reflects the employee‟s clock in & clock
out which may include breaks.
Example: 1
Hours decimal (19, 3) No Description: Total hours worked.
Example: 6.5
TimeClockEditReasonNumber int Yes Description: Reflects the shift edit reason
number (internal) as entered in Back
Office Switchboard|Labor|Payroll|Adjust
Shift|
Example: 3
ManuallyAdjusted bit No Description: Reflects whether a manager
has edited an employee‟s time clock
punch.
1 = punch was modified.
0 = punch was not modified.
Example: 1
CreatedBy int Yes Description: Reflects the user number
(internal) that created the record either
through an import or manually entered.
Example: 1442
CreatedTime datetime No Description: The time this record was
initially created.
Example: 2011-10-24 18:02:00.000
Uses UTC

Data Mart ST_EmployeePunchesRealTime * 55


Field Type Nulls? Comments
LastModifiedBy int Yes Description: The internal number of the
last user that modified this record.
Example: 1022254
LastModifiedTime datetime No Description: The last time this record was
saved.
Example: 2011-02-24 15:32:15.000
Uses UTC
BusinessDateImported datetime Yes Description: The actual business date
when the import was performed.
Example: 2011-02-11
MealBreakWaived bit Yes Description: Waive Break status based on
the Aloha GNDBREAKINFO.dbf for Aloha
Break Rule Number as defined in Back
Office Manager|SiteProperties|Break &
Shift Rules|Meal Breaks| Aloha Break ID.
1=meal break was waived.
0=meal breaks was not waived.
Example: 1
RestBreakWaived bit Yes Description: Waive Break status based on
the Aloha GNDBREAKINFO.dbf for Aloha
Break Rule Number as defined in Back
Office Manager|SiteProperties|Break &
Shift Rules|Rest Breaks| Aloha Break ID.
1 = rest break was waived.
0 = rest breaks was not waived.
Example: 1

Index Name Unique Clustered Fields


PK_ST_EmployeePunchesRealTime Yes Yes InternalEmployeeNumber, ClockIn

* Table will not contain an index on the replicated database.

56 ST_EmployeePunchesRealTime * Data Mart


ST_Employees

Data Mart ST_Employees 57


Description: Employee Information.

Triggered by Export_ProcessSTEmployees.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


HomeSiteNumber int No Description: Site Number (internal)
Example: 1456
HomeStoreID nvarchar (25) Yes Description: Home Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) Yes Description: Employee ID
Example: 504931
SSAN nvarchar (50) Yes Description: Government ID Number (SSN, SIN)
Note: This can be encrypted
If the Encryption parameter is absent or if the
Encrypt Sensitive Data option is unchecked,
the current SSN processing in the Data Mart
will be unchanged (i.e. the SSN data flows
unchanged from the core tables to the Data
Mart). If the SSN data is encrypted in the core
tables (using internal NCR Back Office
encryption) it will remain encrypted in the
Data Mart but it will not be readable by third
parties.
Example: 123456789
LastName nvarchar (50) Yes Description: Employee Last Name
Example: Ahluwalia
FirstName nvarchar (50) Yes Description: Employee First Name
Example: Bob
MiddleName nvarchar (50) Yes Description: Employee Middle Name
Example: Michael
Address nvarchar (100) Yes Description: Employee Address
Example: 174 Golden Gate Road
Address2 nvarchar (100) Yes Description: Employee Address – Line 2 (Apt
Number)
Example: #2211
City nvarchar (100) Yes Description: Employee City
Example: San Francisco
State nvarchar (100) Yes Description: Employee State
Example: CA
Zip nvarchar (50) Yes Description: Employee Zip Code
Example: 45710
Country nvarchar (50) Yes Description: Employee Country
Example: United States of America
Phone nvarchar (50) Yes Description: Employee Phone Number
Example: 5555551212
AltPhone nvarchar (50) Yes Description: Employee Alternate Phone
Number (Mobile)
Example: 5555551212
Gender bit Yes Description: Gender of Employee
0 = Male
1 = Female
Example: 0

58 ST_Employees Data Mart


Field Type Nulls? Comments
FamilyStatus nvarchar (100) Yes Description: Martial Status (Customer
Definable)
Example: Single
EthnicGroup nvarchar (100) Yes Description: Ethnic Status (Customer
Definable)
Example: Italian
Disability bit Yes Description: Disability Status
0 = Not Disabled
1 = Disabled
Example: 0
VeteranStatus nvarchar (100) Yes Description: Veteran Status (Customer
Definable)
Example: Active Reserve
ReferralSource nvarchar (100) Yes Description: Referral Source (Customer
Definable)
Example: Job Fair
HireDate datetime Yes Description: Date Employee was Hired
Example: 1977-05-15
BirthDate datetime Yes Description: Employee Birth Date
Example: 1951-06-24
MaidenName nvarchar (50) Yes Description: Employee‟s Maiden Name
Example: McKenzie
EmergencyContact nvarchar (100) Yes Description: Name of Employee‟s Emergency
Contact
Example: Bob Smith
ContactRelationship nvarchar (100) Yes Description: Relationship of Emergency
Contact to Employee
Example: Father
ContactPhone nvarchar (50) Yes Description: Emergency Contact Phone
Number
Example: 5555551212
ContactWorkPhone nvarchar (50) Yes Description: Emergency Contact Work Phone
Number
Example: 5555551212
ContactAddress nvarchar (255) Yes Description: Emergency Contact Address
Example: 17 Goldenwest Road, Apt 600
EmpStatusDate datetime Yes Description: Employee Status Date
Example: 2007-06-14 14:31:02.000
Uses Site Local Time
EmpStatusCode nvarchar (100) Yes Description: Employee Status Code
(Customer Definable)
Example: Active
EmpStatusReasonCode nvarchar (100) Yes Description: Employee Status Reason Code
(Customer Definable)
Example: New Hire
WorkStatus nvarchar (100) Yes Description: Work Status Code
(Customer Definable)
Example: Active
TerminationDate datetime Yes Description: Termination Date
Example: 2006-05-31
PayrollNumber nvarchar (50) Yes Description: Payroll Code
Example: 0501627
Rehire bit Yes Description: Recommend for Rehire
0 = No
1 = Yes
Example: 1
POSEmployeeNumber nvarchar (50) Yes Description: POS Employee Number
Example: 0501627
JobTitle nvarchar (100) Yes Description: Employee Job Title
Example: Customer Service Team Member

Data Mart ST_Employees 59


Field Type Nulls? Comments
County nvarchar (100) Yes Description: Employee County of Residence
Example: Athens
Salaried bit Yes Description: Salaried
0 = No
1 = Yes
Example: 0
FullTime bit Yes Description: Full Time Status
0 = No
1 = Yes
Example: 0
NationalInsurance nvarchar (100) Yes Description: National Insurance
Example: ABC Insurance
PrimaryJobName nvarchar (100) Yes Description: Job Name
Example: Food Service Team Member
PrimaryJobRate decimal (19, 3) Yes Description: Pay Rate
Example: 7.85
PrimaryJobNumber int Yes Description: Current Job Number (internal)
Example: 1000626
PrimaryJobID nvarchar (25) Yes Description: Job ID
Example: 11
StatusReportingDate datetime Yes Description: Date of Status Change
Example: 2007-07-14
PrimaryJobPayrollCode nvarchar (25) Yes Description: Primary Job Payroll Code
Example: BIO12345
ContactAddress2 nvarchar (100) Yes Description: Emergency Contact Address2
Example: Apt 600
ContactCity nvarchar (100) Yes Description: Emergency Contact City
Example: San Francisco
ContactState nvarchar (100) Yes Description: Emergency Contact State
Example: California
ContactZip nvarchar (50) Yes Description: Emergency Contact Postal Code
Example: 45710
WOTCValidationCode nvarchar (6) Yes Description: WOTC is the Work Opportunity
Tax Credit and the code is the validation code
for this credit. The WOTC credit is assigned
using the following algorithm:
o The first 3 digits are the operator ID
o The 4th digit is the first and last
numbers of the SSN added together,
then divided by 2 and rounded up to
the next whole number
o The 5th digit is the 4th number of the
Social Security Number of the new
hire.
o The last digit is a 0 if eligible and 1 if
not eligible for the credit.
Example: 324450
CustomField1 nvarchar(50) Yes Description: Custom Field 1 from Employee
Maintenance Custom Fields tab
Example: Uniform Deposit $20
CustomField2 nvarchar(50) Yes Description: Custom Field 2 from Employee
Maintenance Custom Fields tab
Example: Uniform Deposit $20
CustomField3 nvarchar(50) Yes Description: Custom Field 3 from Employee
Maintenance Custom Fields tab
Example: Uniform Deposit $20
CustomField4 nvarchar(50) Yes Description: Custom Field 4 from Employee
Maintenance Custom Fields tab
Example: Uniform Deposit $20

60 ST_Employees Data Mart


Field Type Nulls? Comments
CustomField5 nvarchar(50) Yes Description: Custom Field 5 from Employee
Maintenance Custom Fields tab
Example: Uniform Deposit $20
AlohaLiquorCertification nvarchar(100) Yes Description: Aloha Liquor Certification Number
Number from Employee Maintenance Point of Sale Tab.
Example: ABCDE12345FGHIJ67890
AlohaLiquorCertifcation datetime Yes Description: Date entered for Aloha Liquor
ExpirationDate Expiration on Employee Maintenance Point of
Sale Tab.
Example: 2011-12-31
EmailAddress nvarchar(100) Yes Description: An employee‟s email address that
is entered in Back Office Switchboard|Labor|
Employees| Employee Maintenance. This can
be used as another form communication to the
employee.
Example: myemail@myemail.com
TipConsent bit No Description: Tip consent status as selected in
the Employee Profile|Status tab‟s „Tip Consent‟
checkbox.
0 = Not Completed
1 = Completed
Example: 0
RehireDate datetime Yes Description: The „Rehire Date‟ on the „Status‟
Tab that is entered by the manager (Labor
Switchboard|Employees|Employees
Maintenance|Employee Profile) when an
employee is rehired.

If the Rehire Date field is not displayed on the


Employee Profile, or is not manually entered
by the manager, the date defaults to the
current date.

Note: The „Rehire Date‟ field can be added to


the „Employee Profile‟ using Labor|Employee
Maintenance|Employee Fields in Back Office
Manager.

Example: 2010-03-01
I9ValidationCode nvarchar (20) Yes Description: The „I-9 Validation Code‟ on the
„Status‟ tab that is entered by the manager
when an employee is hired (Labor Switchboard
|Employees|Employee Maintenance| Employee
Profile). This setting can be activated by
request.

Example: KMQFIKPF#
BackgroundCheckCode nvarchar (20) Yes Description: The „Background Check Code‟ on
the „Jobcode‟ Tab that is entered by the
manager (Labor Switchboard
|Employees|Employees Maintenance|
Employee Profile) when an employee is
assigned a job requiring a background check.
This setting can be activated by request.

Example: NPXSNXRR#JJ

Index Name Unique Clustered Fields


PK_ST_Employees Yes Yes HomeSiteNumber, BOANETEmployeeNumber

Data Mart ST_Employees 61


ST_EmployeeSalesTips

Description: Sales and Tip Information by EMPLOYEE, by JOB, by DATE

Triggered by Export_ProcessSTEmployeeSalesTips.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
BusinessDate datetime No Description: Business Date
Example: 200703-26
DailySales decimal (19, 3) Yes Description: Daily Sales
Example: 998.74
DeclaredTotalTips decimal (19, 3) Yes Description: Declared Total Tips
Note: When using the Tip Share Distribution,
if a record already exists, „TipShare‟ is
updated. If a record does not exist, a row will
be inserted and „TipShare‟ will be populated.
„DeclaredTotalTips‟ and „ChargeTips‟ would
both be set to NULL when the record is
inserted.
Example: 119.87

62 ST_EmployeeSalesTips Data Mart


Field Type Nulls? Comments
ChargeTips decimal (19, 3) Yes Description: Charged Tips
Note: When using the Tip Share Distribution,
if a record already exists, „TipShare‟ is
updated. If a record does not exist, a row will
be inserted and „TipShare‟ will be populated.
„DeclaredTotalTips‟ and „ChargeTips‟ would
both be set to NULL when the record is
inserted.
Example: 87.54
GuestCount int Yes Description: Guest Count
Example 21
TipShare decimal (19, 3) Yes Description: Tip Share
Note: When using the Tip Share Distribution,
if a record already exists, „TipShare‟ is
updated. If a record does not exist, a row will
be inserted and „TipShare‟ will be populated.
„DeclaredTotalTips‟ and „ChargeTips‟ would
both be set to NULL when the record is
inserted.
Example: 119.87
Spiffs decimal (19, 3) Yes Description: Spiffs
Example: 0

Index Name Unique Clustered Fields


PK_ST_EmployeeSalesTips Yes Yes BusinessDate, SiteNumber,
BOANETEmployeeNumber, JobNumber

Data Mart 63
ST_EmployeeSalesTips_RealTimeFeed *

Description: This table provides sales and tip Information by site, employee, job and business date. If
an employee has two shifts using the same jobcode, the sales & tips are summed and stored with the
first shift. Values in this table can be created, modified and removed by a POS import, manual
adjustment to an employee‟s shift or „Tip Share Distribution‟.

When using the „Tip Share Distribution‟, if a record already exists, „TipShare‟ is updated. If a record
does not exist, a row will be inserted and „TipShare‟ will be populated. „DeclaredTotalTips‟ and
„ChargeTips‟ would both be set to NULL when the record is inserted.

Triggered by Export_STEmployeeSalesTips_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456

64 ST_EmployeeSalesTips_RealTimeFeed * Data Mart


Field Type Nulls? Comments
InternalEmployeeNumber int No Description: Employee Number (internal).
An employee number will ONLY occur once
for each jobcode worked in a business day.
An employee number may occur multiple
times for different jobcodes in a day.
Example: 10022155
JobNumber int No Description: Jobcode Number (internal).
This number identifies each jobcode an
employee used for the day of business.
Note: Jobs are defined in ST_Jobs
Example: 100026
BusinessDate datetime No Description: Date of business that the sales
and tips occurred on.
Example: 2012-03-26
DailySales decimal(19, 3) No Description: Amount of sales for the
business day for a jobcode. This amount
can be imported or entered or modified
from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Sales‟ box.
Example: 998.74
DeclaredTotalTips decimal(19, 3) No Description: Amount cash, credit and any
other source of tips declared by an
employee for a day of business for a
jobcode. This amount can be imported or
entered or modified from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Declared Tips‟ box.
Example: 119.87
ChargeTips decimal(19, 3) No Description: Amount credit tips for an
employee for a day of business for a
jobcode. This amount can be imported or
entered or modified from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Charge Tips‟ box.
Example: 87.54
GuestCount int No Description: Total guest count for an
employee for a day of business for a
jobcode. This amount can be imported or
entered or modified from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Charge Tips‟ box.
Example: 21
TipShare decimal(19, 3) No Description: Amount tip share allocated
employee for a day of business and job.
This amount can be entered or modified
from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Tipshare Earned‟ box or distributed by
„Tip Share Distribution‟.
Note: The text label „Tipshare Earned‟ in the
Labor Switchboard can be changed in Site
Properites|General 2 through the „Auto
Balance Grid Distribution‟ ellipses „...‟
button.
Example: 119.87

Data Mart ST_EmployeeSalesTips_RealTimeFeed * 65


Field Type Nulls? Comments
OtherEarnings decimal(19, 3) No Description: Amount of other earnings for
an employee for a day of business and
jobcode. This amount can be entered or
modified from the Labor
Switchboard|Payroll|Shifts|Sales and Tips in
the „Other Earnings‟ box or distributed by
„Tip Share Distribution‟.
Note: The text label „Other Earnings‟ in the
Labor Switchboard can be changed in Site
Properites|General 2 through the „Auto
Balance Grid Distribution‟ ellipses „...‟
button.
Example: 123.45
AlohaTippableCreditCardS decimal(19, 3) No Description: Amount of tippable credit card
ales sales for a business day for a jobcode. This
amount can only be imported with the
Aloha POS import type „Labor‟. This amount
is NOT visible from within the Switchboard.
Note: Amount includes credit tips and cash
auto gratuities.
Example: 103.72
AlohaDeclaredCashTips decimal(19, 3) No Description: Amount cash tips declared for
a business day for a jobcode. This amount
can only be imported with the Aloha POS
import type „Labor‟. This amount is NOT
visible from within the Switchboard.
Note: Aloha has various configuration
options for how to declare tips at the end of
a shift. This total will always be the total
cash tips regardless of how the Aloha
settings are defined.
Example: 245.33
AlohaTipshareContribution decimal(19, 3) No Description: Amount of employee tips
contributed towards the tip share for a
business day for a jobcode. This amount
can only be imported with the Aloha POS
import type „Labor‟. This amount is NOT
visible from within the Switchboard.
Note: Amount is based on the percentage
(%) set in Aloha for required tip
contribution plus any additional tip share an
employee contributes.
Example: 23.44
AlohaTipsforAllTenders decimal(19, 3) No Description: Amount of tips collected for a
business day for a jobcode. This amount
can only be imported with the Aloha POS
import type „Labor‟. This amount is NOT
visible from within the Switchboard.
Example: 33.33
AlohaAutomaticGratuityfor decimal(19, 3) No Description: Amount automatic gratuity for
AllTenders a business day for a jobcode. This amount
can only be imported with the Aloha POS
import type „Labor‟. This amount is NOT
visible from within the Switchboard.
Example: 34.55

66 ST_EmployeeSalesTips_RealTimeFeed * Data Mart


Field Type Nulls? Comments
AlohaTipsforAllCreditCard decimal(19, 3) No Description: Amount of tips for all credit
Tenders card tenders for a business day for a
jobcode. This amount can only be imported
with the Aloha POS import type „Labor‟. This
amount is NOT visible from within the
Switchboard.
Example: 122.55
AlohaAutomaticGratuityfor decimal(19, 3) No Description: Amount of automatic gratuity
AllCreditCardTenders collected for all credit card tenders for a
business day for a jobcode. This amount
can only be imported with the Aloha POS
import type „Labor‟. This amount is NOT
visible from within the Switchboard.
Example: 134.55
ManualEdit bit Yes Description: Identifies if the record was
manually edited.
0 or Null = Not Manually Edited
1 = Record was Manually Edited
Example: 0
EditedBy int Yes Description: User Number (internal).
Example: 10022155
AlohaAutomaticGratuityfor decimal(19, 3) No Description: Amount of automatic gratuity
AllCashTenders collected for all cash tenders for a business
day for a jobcode. This amount can only be
imported with the Aloha POS import type
„Labor‟. This amount is NOT visible from
within the Switchboard.
Example: 134.55
AlohaAutomaticGratuityfor decimal(19, 3) No Description: Amount of automatic gratuity
AllOtherTenders collected for all tenders that are neither
cash nor credit card (e.g. gift card, check,
house account) for a business day for a
jobcode. This amount can only be imported
with the Aloha POS import type „Labor‟. This
amount is NOT visible from within the
Switchboard.
Example: 134.55
AlohaAutomaticGratuityfor decimal(19, 3) No Description: Amount of automatic gratuity
AllNonCashTenders collected for all non-cash tenders (e.g.
credit card, gift card, check, house account)
for a business day for a jobcode. This
amount can only be imported with the
Aloha POS import type „Labor‟. This amount
is NOT visible from within the Switchboard.
Example: 134.55

Index Name Unique Clustered Fields


PK_ST_EmployeeSalesTips Yes Yes BusinessDate, SiteNumber,
_RealTimeFeed InternalEmployeeNumber, JobNumber

* Table will not contain an index on the replicated database.

Data Mart ST_EmployeeSalesTips_RealTimeFeed * 67


ST_EmployeeStatusBySite_RealTimeFeed *

Description: This table provides borrowed employee information such as current home site (SiteFrom)
and borrowed site (SiteTo), who initiated and/or modified the record with the date and time of each
action.

Triggered by Export_STEmployeeStatusBySite_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include employee history for all sites. The site property, „Exclude from
Data Mart‟ setting is not supported in this Data Mart table. Sites that have this setting checked in
Back Office Manager will be included in this table.

Field Type Nulls? Comments


RecordNumber bigint No Description: A unique record identifier.
This is an Identity field type. Do not use.
Example: 12
SiteFrom int No Description: Current Site of the employee
(internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
SiteTo int Yes Description: The site in which the employee is
either borrowed or transferred to. (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1001865
InternalEmployeeNumber int No Description: Employee Number (internal)
Note: Employees are defined in ST_Employees.
Example: 122000186
ModifiedBy int No Description: User internal number of the person
who modified the record.
Example: 122000145
Action tinyint No Description: A value that represents the action
that occurred for the specified employee:
1 = Borrowed
2 = Transferred
3 = Adding a new employee to the site
4 = Modify the employee‟s profile
5 = Delete (unborrowed)
Example: 5
ActionTime datetime No Description: Date and time of when the action
occurred.
Example: 2012-03-01 14:05:00.000
Uses Site Local Time

68 ST_EmployeeStatusBySite_RealTimeFeed * Data Mart


Index Name Unique Clustered Fields
PK_ST_EmployeeStatusBySite_RealTimeFeed Yes Yes RecordNumber

* Table will not contain an index on the replicated database.

Data Mart ST_EmployeeStatusBySite_RealTimeFeed * 69


ST_EmpTrans

70 ST_EmpTrans Data Mart


Description: Employee Changes and Transactions. Also has original Government ID Number (SSN,
SIN)

Triggered by Export_ProcessSTEmpTrans.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordNumber bigint No Description: Record Number
This is an Identity field type. Do not use.
Example: 141
HomeSiteNumber int No Description: Site Number (internal)
Example: 1456
HomeStoreID nvarchar (25) Yes Description: Home Store ID
Example: 1311
Timestamp datetime No Description: Timestamp
Example: 2007-06-14 14:31:02.000
Uses UTC
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) Yes Description: Employee ID
Example: 504931
SSAN nvarchar (50) Yes Description: New Gov‟t ID Number (SSN, SIN)
Note: This can be encrypted
If the Encryption parameter is absent or if the
Encrypt Sensitive Data option is unchecked, the
current SSN processing in the Data Mart will be
unchanged (i.e. the SSN data flows unchanged
from the core tables to the Data Mart). If the SSN
data is encrypted in the core tables (using internal
NCR Back Office encryption) it will remain
encrypted in the Data Mart but it will not be
readable by third parties.
Example: 123456789
SSAN_Original nvarchar (50) Yes Description: Original Gov‟t ID Number (SSN, SIN)
Note: This can be encrypted
If the Encryption parameter is absent or if the
Encrypt Sensitive Data option is unchecked, the
current SSN processing in the Data Mart will be
unchanged (i.e. the SSN data flows unchanged
from the core tables to the Data Mart). If the SSN
data is encrypted in the core tables (using internal
NCR Back Office encryption) it will remain
encrypted in the Data Mart but it will not be
readable by third parties.
Example: 123456789
LastName nvarchar (50) Yes Description: Employee Last Name
Example: Ahluwalia
FirstName nvarchar (50) Yes Description: Employee First Name
Example: Bob
MiddleName nvarchar (50) Yes Description: Employee Middle Name
Example: Michael

Data Mart ST_EmpTrans 71


Field Type Nulls? Comments
Address nvarchar (100) Yes Description: Employee Address
Example: 174 Golden Gate Road
Address2 nvarchar (100) Yes Description: Employee Address – Line 2 (Apt
Number)
Example: #2211
City nvarchar (100) Yes Description: Employee City
Example: San Francisco
State nvarchar (100) Yes Description: Employee State
Example: CA
Zip nvarchar (50) Yes Description: Employee Zip Code
Example: 45710
Country nvarchar (50) Yes Description: Employee Country
Example: United States of America
Phone nvarchar (50) Yes Description: Employee Phone Number
Example: 5555551212
AltPhone nvarchar (50) Yes Description: Employee Alternate Phone Number
(Mobile)
Example: 5555551212
Gender bit Yes Description: Gender of Employee
0 = Male
1 = Female
Example: 0
FamilyStatus nvarchar (100) Yes Description: Martial Status (Customer Definable)
Example: Single
EthnicGroup nvarchar (100) Yes Description: Ethnic Status (Customer Definable)
Example: Italian
Disability bit Yes Description: Disability Status
0 = Not Disabled
1 = Disabled
Example: 0
VeteranStatus nvarchar (100) Yes Description: Veteran Status (Customer Definable)
Example: No Beteran Status
ReferralSource nvarchar (100) Yes Description: Referral Source (Customer Definable)
Example: Employee Referral
HireDate datetime Yes Description: Date Employee was Hired
Example: 1977-05-17
BirthDate datetime Yes Description: Employee Birth Date
Example: 1951-06-25
MaidenName nvarchar (50) Yes Description: Employee‟s Maiden Name
Example: McKenzie
EmergencyContact nvarchar (100) Yes Description: Name of Employee‟s Emergency
Contact
Example: Bob Smith
ContactRelationship nvarchar (100) Yes Description: Relationship of Emergency Contact to
Employee
Example: Father
ContactPhone nvarchar (50) Yes Description: Emergency Contact Phone Number
Example: 5555551212
ContactWorkPhone nvarchar (50) Yes Description: Emergency Contact Work Phone
Number
Example: 5555551212
ContactAddress nvarchar (255) Yes Description: Emergency Contact Address
Example: 17 Goldenwest Road, Apt 600
EmpStatusDate datetime Yes Description: Employee Status Date
Example: 2007-06-14 14:31:02.000
Uses Site Local Time
EmpStatusCode nvarchar (100) Yes Description: Employee Status Code
(Customer Definable)
Example: Active

72 ST_EmpTrans Data Mart


Field Type Nulls? Comments
EmpStatusReasonCode nvarchar (100) Yes Description: Employee Status Reason Code
(Customer Definable)
Example: New Hire
WorkStatus nvarchar (100) Yes Description: Work Status Code
(Customer Definable)
Example: Active
TerminationDate datetime Yes Description: Termination Date
Example: 2006-05-25
PayrollNumber nvarchar (50) Yes Description: Payroll Number
Example: 0501627
Rehire bit Yes Description: Recommend for Rehire
0 = No
1 = Yes
Example: 1
POSEmployeeNumber nvarchar (50) Yes Description: POS Employee Number
Example: 0501627
JobTitle nvarchar (100) Yes Description: Employee Job Title
Example: Customer Service Team Member
County nvarchar (100) Yes Description: Employee County of Residence
Example: Athens
Salaried bit Yes Description: Salaried
0 = No
1 = Yes
Example: 0
FullTime bit Yes Description: Full Time Status
0 = No
1 = Yes
Example: 0
NationalInsurance nvarchar (100) Yes Description: National Insurance
Example: ABC Insurance
StatusReportingDate datetime Yes Description: Date of Status Change
Example: 2007-07-14
ContactAddress2 nvarchar (100) Yes Description: Emergency Contact Address2
Example: Apt 600
ContactCity nvarchar (100) Yes Description: Emergency Contact City
Example: San Francisco
ContactState nvarchar (100) Yes Description: Emergency Contact State
Example: California
ContactZip nvarchar (50) Yes Description: Emergency Contact Postal Code
Example: 45710
WOTCValidationCode nvarchar (6) Yes Description: WOTC is the Work Opportunity Tax
Credit and the code is the validation code for this
credit. The WOTC credit is assigned using the
following algorithm:
o The first 3 digits are the operator ID
o The 4th digit is the first and last numbers
of the SSN added together, then divided by
2 and rounded up to the next whole
number
o The 5th digit is the 4th number of the
Social Security Number of the new hire.
o The last digit is a 0 if eligible and 1 if not
eligible for the credit.
Example: 324450
TipConsent bit Yes Description: Tip consent status as selected in the
Employee Profile|Status tab‟s „Tip Consent‟
checkbox.
0 = Not Completed
1 = Completed
Example: 0

Data Mart ST_EmpTrans 73


Field Type Nulls? Comments
RehireDate datetime Yes Description: The „Rehire Date‟ on the „Status‟ Tab
that is entered by the manager (Labor
Switchboard|Employees|Employees
Maintenance|Employee Profile) when an employee
is rehired.

If the Rehire Date field is not displayed on the


Employee Profile, or is not manually entered by the
manager, the date defaults to the current date.

Note: The „Rehire Date‟ field can be added to the


„Employee Profile‟ using Labor|Employee
Maintenance|Employee Fields in Back Office
Manager.

Example: 2010-03-01
I9ValidationCode nvarchar (20) Yes Description: The „I-9 Validation Code‟ on the
„Status‟ tab that is entered by the manager when
an employee is hired (Labor Switchboard
|Employees|Employee Maintenance| Employee
Profile). This setting can be activated by request.

Example: KMQFIKPF#
BackgroundCheckCode nvarchar (20) Yes Description: The „Background Check Code‟ on the
„Jobcode‟ Tab that is entered by the manager
(Labor Switchboard|Employees|Employees
Maintenance| Employee Profile) when an employee
is assigned a job requiring a background check.
This setting can be activated by request.

Example: NPXSNXRR#JJ

Index Name Unique Clustered Fields


PK_ST_EmpTrans Yes No RecordNumber
IX_ST_EmpTrans No Yes HomeSiteNumber, Timestamp,
BOANETEmployeeNumber

74 ST_EmpTrans Data Mart


ST_EmpTransW4_I9

Data Mart ST_EmpTransW4_I9 75


Description: Employee W4 and I9 Transaction Information

Triggered by Export_ProcessSTEmpTrans.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordNumber bigint No Description: Record Number
Example: 141
HomeSiteNumber int No Description: Site Number (internal)
Example: 1456
HomeStoreID nvarchar (25) Yes Description: Home Store ID
Example: 1311
Timestamp datetime No Description: Timestamp
Example: 2007-06-14 14:31:02.000
Uses UTC
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
W4Exempt bit Yes Description: W4 Exemption Status
0 = Not Exempt
1 = Exempt
Example: 1
W4FedMaritalStatus nvarchar (100) Yes Description: Marital Status as declared on
W4
Example: Single
W4FedExemptNbr decimal (19, 3) Yes Description: W4 Federal Exemption
Number
Example: 1
W4FedAdditionalAmount float Yes Description: W4 Federal Additional Amount
to be Deducted
Example: 100
W4StateTaxCode nvarchar (100) Yes Description: State Filing Status used by
W4 & K4.
A4: Arizona does not use this field.
K4: Kansas uses this field to hold the
Allowance Rate type: Single, Joint.
W4: All other states uses this field to hold
the State Filing Status.
Example: Single
ie: Married, Single, Head of Household,
NULL
W4StateExemptNbr smallint Yes Description: This field is used for W4, K4
and A4.
A4: Arizona is using this field to hold the
A4 tab selection: 3 = Exempt; 4 =
Withholding (If you see 1 or 2 that was
used for 2010 (1= $15,000 or More; 2=
Less Than $15,000; 3 = Exempt).
W4 & K4: All other states, including
Kansas, uses this field to hold the State
Number of Allowances.
Example: 1

76 ST_EmpTransW4_I9 Data Mart


Field Type Nulls? Comments
W4StateAdditionalAmount decimal (19, 3) Yes Description: This field is used for W4, K4
and A4.
A4: Arizona is using this field to hold the
withholding percentage Rate (ie: 1.8%,
etc).
W4 & K4: All other states, including
Kansas, uses this field to hold the States
Additional Withholding Amount.
Example: 0
I9Citizen smallint Yes Description: I9 Citizen
Example: 1
AlienNumber nvarchar (50) Yes Description: Alien Number
Example: A123456
AlienAuthorizedDate datetime Yes Description: Alien Authorization Date
Example: 2010-03-27
DocumentTitleA nvarchar (50) Yes Description: Document Title A
Example: U. S. Passport
IssuingAuthorityA nvarchar (50) Yes Description: Issuing Authority for
Document A
Example: United States Government
DocumentNumberA nvarchar (50) Yes Description: Document Number for
Document A
Example: P1234567
ExpirationDateA datetime Yes Description: Expiration Date for Document
A
Example: 2010-03-27
DocumentNumberA1 nvarchar (50) Yes Description: Document Number for
Document A1
Example: <TBD>
ExpirationDateA1 datetime Yes Description: Expiration Date for Document
A1
Example: <TBD>
DocumentTitleB nvarchar (50) Yes Description: Document Title B
Example: Driver‟s License
IssuingAuthorityB nvarchar (50) Yes Description: Issuing Authority for
Document B
Example: State of California
DocumentNumberB nvarchar (50) Yes Description: Document Number for
Document B
Example: D11010101
ExpirationDateB datetime Yes Description: Expiration Date for Document
B
Example: 2018-07-18
DocumentTitleC nvarchar (50) Yes Description: Document Title C
Example: Social Security Card
IssuingAuthorityC nvarchar (50) Yes Description: Issuing Authority for
Document C
Example: United States Government
DocumentNumberC nvarchar (50) Yes Description: Document Number for
Document C
Note: This can be encrypted, but only when
DocumentTitleC = „Social Security Card‟.
Note: Technically, the value in DocumentTitleC
column will be driven by the value in the
ListItemName column in
SiteEmployeeFieldListItems where
EmployeeFieldNumber = -47 and
ListItemNumber = 0 which is currently „Social
Security Card‟
Example: 123456789

Data Mart ST_EmpTransW4_I9 77


Field Type Nulls? Comments
ExpirationDateC datetime Yes Description: Expiration Date for Document
C
Example: 2025-06-10
DocCheckedby nvarchar (50) Yes Description: Documents Checked By
Example: Bob Smith
DocCheckerTitle nvarchar (50) Yes Description: Title of Person who Cecked
Documents
Example: Assistant Manager
I9Complete tinyint Yes Description: I9 Completion Status
0 = No
1 = Yes
Example: 1
LWT_ALLOWANCES smallint Yes Description: Local tax allowance for
employee
Example: 1
LWT_AMT decimal (19, 3) Yes Description: Local tax additional amount
for employee
Example: 500.00
TAXLOCALITY1 nvarchar (50) Yes Description: First local tax option for
employee
Example: Orange County Tax
TAXLOCALITY2 nvarchar (50) Yes Description: Second local tax option for
employee
Example: LA County Tax
TAXLOCALITY3 nvarchar (50) Yes Description: Third local tax option for
employee
Example: Riverside County Tax
TAXLOCALITY4 nvarchar (50) Yes Description: Fourth local tax option for
employee
Example: San Diego County Tax
A4StateAZAdditionalAmount decimal(19, 3) Yes Description: Arizona‟s State Additional
Withholding Amount. Created for Arizona‟s
A4 tab and not used by any other state.
Example: 15.00
StateExemptFromWithholding bit Yes Description: State Exempt from
Withholding flag. Created for Kansas K4
tab and not used by any other states at
this time.
0 = Not Exempt
1 = Exempt
Example: 1
DocumentTitleA1 nvarchar(50) Yes Description: Document title selected as
evidence of identity and employment
authorization (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: U.S. Passport
IssuingAuthorityA1 nvarchar(50) Yes Description: Free form text field. Issuing
authority associated with document title
selected for “DocumentTitleA1” (Employee
Maintenance|Employee – Profile|I-9 Form
tab).
Example: USA
DocumentTitleA2 nvarchar(50) Yes Description: Document title selected as
evidence of identity and employment
authorization (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: Foreign Passport w/I-94

78 ST_EmpTransW4_I9 Data Mart


Field Type Nulls? Comments
IssuingAuthorityA2 nvarchar(50) Yes Description: Free form text field. Issuing
authority associated with document title
selected for “DocumentTitleA2” (Employee
Maintenance|Employee – Profile|I-9 Form
tab).
Example: USA
DocumentNumberA2 nvarchar(50) Yes Description: Free form text field.
Document number associated with
document title selected for
“DocumentTitleA2” (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: DO987654
ExpirationDateA2 datetime Yes Description: Expiration date associated
with document title selected for
“DocumentTitleA2” (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: 2016-11-10
AdmissionNumber nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: 12345678901
ForeignPassportNumber nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: UK1234567
CountryofIssuance nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: United Kingdom
ExpirationDateNA bit Yes Description: When “An alien authorized to
work” is selected (Employee Maintenance
|Employee – Profile|I-9 Form tab),
indicates no expiration date will be
assigned and will display “N/A” when Form
I-9 is printed).
0 = The expiration date is applicable for
the Alien Number and will print the
selected date on the I9 form.
1 = The expiration date is not applicable
for the Alien Number and will print
„N/A‟ on the I9 form.
Example: 1

Index Name Unique Clustered Fields


PK_ST_EmpTransW4_I9 Yes No RecordNumber

IX_ST_EmpTransW4_I9_HomeSite No Yes HomeSiteNumber, Timestamp,


NumTimeStaBOAEmpNum BOANETEmployeeNumber

Data Mart ST_EmpTransW4_I9 79


ST_EmpW4_I9

80 ST_EmpW4_I9 Data Mart


Description: Employee W4 and I9 Information

Triggered by Export_ProcessSTEmployees.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


HomeSiteNumber int No Description: Site Number (internal)
Example: 1456
HomeStoreID nvarchar (25) Yes Description: Home Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) Yes Description: Employee ID
Example: 504931
W4Exempt bit Yes Description: W4 Exemption Status
0 = Not Exempt
1 = Exempt
Example: 1
W4FedMaritalStatus nvarchar (100) Yes Description: Marital Status as declared on
W4
Example: Single
W4FedExemptNbr decimal (19, 3) Yes Description: W4 Federal Exemption
Number
Example: 1
W4FedAdditionalAmount float Yes Description: W4 Federal Additional
Amount to be Deducted
Example: 100
W4StateTaxCode nvarchar (100) Yes Description: State Filing Status used by
W4 & K4.
A4: Arizona does not use this field.
K4: Kansas uses this field to hold the
Allowance Rate type: Single, Joint.
W4: All other states uses this field to hold
the State Filing Status.
Example: Single
ie: Married, Single, Head of Household,
NULL
W4StateExemptNbr smallint Yes Description: This field is used for W4, K4
and A4.
A4: Arizona is using this field to hold the
A4 tab selection: 3 = Exempt; 4 =
Withholding (If you see 1 or 2 that was
used for 2010 (1= $15,000 or More; 2=
Less Than $15,000; 3 = Exempt).
W4 & K4: All other states, including
Kansas, uses this field to hold the State
Number of Allowances.
Example: 3
W4StateAdditionalAmount decimal (19, 3) Yes Description: This field is used for W4, K4
and A4.
A4: Arizona is using this field to hold the
withholding percentage Rate (ie: 1.8%,
etc).
W4 & K4: All other states, including
Kansas, uses this field to hold the States
Additional Withholding Amount.
Example: 0

Data Mart ST_EmpW4_I9 81


Field Type Nulls? Comments
I9Citizen smallint Yes Description: I9 Citizen
0 = A citizen or national of the United
States
1 = A lawful permanent resident
2 = An alien authorized to work
3 = A citizen of the United States
4 = A noncitizen national of the United
States
Example: 1
AlienNumber nvarchar (50) Yes Description: Alien Number
Example: A123456
AlienAuthorizedDate datetime Yes Description: Alien Authorization Date
Example: 2010-03-27
DocumentTitleA nvarchar (50) Yes Description: Document Title A
Example: Passport
IssuingAuthorityA nvarchar (50) Yes Description: Issuing Authority for
Document A
Example: United States Government
DocumentNumberA nvarchar (50) Yes Description: Document Number for
Document A
Example: P1234567
ExpirationDateA datetime Yes Description: Expiration Date for
Document A
Example: 2010-03-27
DocumentNumberA1 nvarchar (50) Yes Description: Document Number for
Document A1
Example: <TBD>
ExpirationDateA1 datetime Yes Description: Expiration Date for
Document A1
Example: <TBD>
DocumentTitleB nvarchar (50) Yes Description: Document Title B
Example: Driver‟s License
IssuingAuthorityB nvarchar (50) Yes Description: Issuing Authority for
Document B
Example: State of California
DocumentNumberB nvarchar (50) Yes Description: Document Number for
Document B
Example: D11010101
ExpirationDateB datetime Yes Description: Expiration Date for
Document B
Example: 2018-07-16
DocumentTitleC nvarchar (50) Yes Description: Document Title C
Example: Social Security Card
IssuingAuthorityC nvarchar (50) Yes Description: Issuing Authority for
Document C
Example: United States Government
DocumentNumberC nvarchar (50) Yes Description: Document Number for
Document C
Note: This can be encrypted, but only
when DocumentTitleC = „Social Security
Card‟.
Note: Technically, the value in
DocumentTitleC column will be driven by
the value in the ListItemName column in
SiteEmployeeFieldListItems where
EmployeeFieldNumber = -47 and
ListItemNumber = 0 which is currently
„Social Security Card‟
Example: 123456789

82 ST_EmpW4_I9 Data Mart


Field Type Nulls? Comments
ExpirationDateC datetime Yes Description: Expiration Date for
Document C
Example: 2025-12-21
DocCheckedby nvarchar (50) Yes Description: Documents Checked By
Example: Bob Smith
DocCheckerTitle nvarchar (50) Yes Description: Title of Person who Checked
Documents
Example: Assistant Manager
I9Complete tinyint Yes Description: I9 Completion Status
0 = No
1 = Yes
Example: 1
LWT_ALLOWANCES smallint Yes Description: Local tax allowance for
employee
Example: 1
LWT_AMT decimal (19, 3) Yes Description: Local tax additional amount
for employee
Example: 500.00
TAXLOCALITY1 nvarchar (50) Yes Description: First local tax option for
employee
Example: Orange County Tax
TAXLOCALITY2 nvarchar (50) Yes Description: Second local tax option for
employee
Example: LA County Tax
TAXLOCALITY3 nvarchar (50) Yes Description: Third local tax option for
employee
Example: Riverside County Tax
TAXLOCALITY4 nvarchar (50) Yes Description: Fourth local tax option for
employee
Example: San Diego County Tax
A4StateAZAdditionalAmount decimal(19, 3) Yes Description: Arizona‟s State Additional
Withholding Amount. Created for
Arizona‟s A4 tab and not used by any
other state.
Example: 15.00
StateExemptFromWithholding bit Yes Description: State Exempt from
Withholding flag. Created for Kansas K4
tab and not used by any other states at
this time.
0 = Not Exempt
1 = Exempt
Example: 1
DocumentTitleA1 nvarchar(50) Yes Description: Document title selected as
evidence of identity and employment
authorization (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: U.S. Passport
IssuingAuthorityA1 nvarchar(50) Yes Description: Free form text field. Issuing
authority associated with document title
selected for “DocumentTitleA1”
(Employee Maintenance|Employee –
Profile|I-9 Form tab).
Example: USA
DocumentTitleA2 nvarchar(50) Yes Description: Document title selected as
evidence of identity and employment
authorization (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: Foreign Passport w/I-94

Data Mart ST_EmpW4_I9 83


Field Type Nulls? Comments
IssuingAuthorityA2 nvarchar(50) Yes Description: Free form text field. Issuing
authority associated with document title
selected for “DocumentTitleA2”
(Employee Maintenance|Employee –
Profile|I-9 Form tab).
Example: USA
DocumentNumberA2 nvarchar(50) Yes Description: Free form text field.
Document number associated with
document title selected for
“DocumentTitleA2” (Employee
Maintenance |Employee – Profile|I-9 Form
tab).
Example: DO987654
ExpirationDateA2 datetime Yes Description: Expiration date associated
with document title selected for
“DocumentTitleA2” (Employee
Maintenance |Employee – Profile|I-9 Form
tab).
Example: 2016-11-10
AdmissionNumber nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: 12345678901
ForeignPassportNumber nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: UK1234567
CountryofIssuance nvarchar(50) Yes Description: Free form text field. Displays
when “An alien authorized to work” is
selected (Employee Maintenance
|Employee – Profile|I-9 Form tab).
Example: United Kingdom
ExpirationDateNA bit Yes Description: When “An alien authorized to
work” is selected (Employee Maintenance
|Employee – Profile|I-9 Form tab),
indicates no expiration date will be
assigned and will display “N/A” when
Form I-9 is printed).
0 = The expiration date is applicable for
the Alien Number and will print the
selected date on the I9 form.
1 = The expiration date is not applicable
for the Alien Number and will print
„N/A‟ on the I9 form.
Example: 1

Index Name Unique Clustered Fields


PK_ST_EmpW4_I9 Yes Yes HomeSiteNumber,
BOANETEmployeeNumber

84 ST_EmpW4_I9 Data Mart


ST_ExcludedItemsBySite_FromView *

Description: This table provides information on items (raw, prep, menu, and modifiers) that are set as
„excluded‟ in NCR Back Office Manager|Items|Item Maintenance. Items that are excluded are not
displayed in the Back Office Switchboard UIs and are not available for purchasing or used recipes.

Triggered by Export_STExcludedItemsBySite_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number of where
the item is excluded.
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
ItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items.
Example: 1001865

Index Name Unique Clustered Fields


PK_ST_ExcludedItemsBySite Yes Yes SiteNumber, ItemNumber
_FromView

* Table will not contain an index on the replicated database.

Data Mart ST_ExcludedItemsBySite_FromView * 85


ST_FoodCost

Description: Actual and Theoretical Food Cost Data by SITE by SUBPERIOD.


Goes through the configurable Data and gets food cost.

Triggered by Export_ProcessSTFoodCost.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
StartSubPeriod int No Description: Starting Sub Period (internal)
Example: 69
EndSubPeriod int No Description: Ending Sub Period (internal)
Example: 69
RawMaterialItemCatNum int No Description: Raw Material Item Category
Number (internal)
Example: 1000020
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: SHORTENING
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 1401
ActualUse$ money Yes Description: Actual Usage Value
Example: 223.92

86 ST_FoodCost Data Mart


Field Type Nulls? Comments
TheoryUse$ money Yes Description: Theoretical Usage Value
Example: 331.57
SumOfWklyFoodSales$ money Yes Description: Week to Date Food Sales in
Dollars
Example: 23346.84
TheoryUse$FIFO money Yes Description: Theoretical Use dollars using
FIFO for the cost evaluation.
Example: $123

Index Name Unique Clustered Fields


PK_ST_FoodCost Yes Yes SiteNumber, StartSubPeriod, EndSubPeriod,
RawMaterialItemCatNum

Data Mart ST_FoodCost 87


ST_FoodCostByItem

Description: Actual and Theoretical Food Cost Data by SITE by SUBPERIOD by ITEM.

Triggered by Export_ProcessSTFoodCostByItem.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. The following settings (based on the report parameter „Actual Use‟) are applied every time the
export is performed:
a. “Must have a Beginning Inventory” - Unchecked (set to False)
b. “Must have an Ending Inventory” - Unchecked (set to False)

88 ST_FoodCostByItem Data Mart


c.“Use theoretical amount for ending inventory for an item that does not have a current
inventory” - Unchecked (set to False)
o This setting (c) can be changed to „checked‟, which will provide a theoretical value for
the following columns:
 BegInvQty
 BegInvValue
 EndInvQty
 EndInvValue
 UnitCost
 TheoryUseValueFIFO
o To change this setting, please contact your NCR Back Office representative.
If you are attempting to reconcile the Data Mart values to a NCR Back Office report, please ensure
that the „Actual Use‟ parameter in the report has the same settings applied.

2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
StartSubPeriod int No Description: Starting Sub Period (internal)
Example: 69
EndSubPeriod int No Description: Ending Sub Period (internal)
Example: 69
StartingDate datetime Yes Description: Starting Date
Example: 2007-04-28
EndingDate datetime Yes Description: Ending Date
Example: 2007-05-14
RawMaterialItemCatNum int Yes Description: Item Category Number (internal)
Example: 1000027
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 1401
RawMaterialItemNumber int No Description: Item Number (internal)
Example: 1000554
RawMaterialItemID nvarchar(40) Yes Description: Raw Material Item ID
Example: 1404
RawMaterialItemUnitNum int No Description: Item Unit Number (internal)
ber Example: 6
RawMaterialItemUnitName nvarchar (50) Yes Description: Item Unit Name
Example: EA
BegInvQty decimal (28, 3) No Description: Beginning Inventory Quantity
Example: 12000
BegInvValue decimal (28, 3) No Description: Beginning Inventory Value
Example: 67.76
PurchQty decimal (28, 3) No Description: Quantity Purchased
Example: 5400
PurchValue decimal (28, 3) No Description: Purchased Value
Example: 30.49
InvoiceQuantity decimal (28, 3) No Description: Invoice Quantity
Example: 5400
InvoiceValue decimal (28, 3) No Description: Invoice Value
Example: 30.49

Data Mart ST_FoodCostByItem 89


Field Type Nulls? Comments
TransferInQuantity decimal (28, 3) No Description: Transfered In Quantity
Example: 0
TransferInValue decimal (28, 3) No Description: Transfered In Value
Example: 0
TransferOutQuantity decimal (28, 3) No Description: Transfered Out Quantity
Example: 0
TransferOutValue decimal (28, 3) No Description: Transfered Out Value
Example: 0
EndInvQty decimal (28, 3) No Description: Ending Inventory Quantity
Example: 9600
EndInvValue decimal (28, 3) No Description: Ending Inventory Value
Example: 54.2
UnitCost decimal (19, 3) No Description: Unit Cost
Example: 0.01
ActualUseQty decimal (28, 3) No Description: Actual Use Quantity
Example: 7800
ActualUseValue decimal (28, 3) No Description: Actual Use Value
Value: 44.05
TheoryUseQty decimal (28, 3) No Description: Theoretical Use Quantity
Example: 1248
TheoryUseValue decimal (28, 3) No Description: Theoretical Use Value
Example: 7.05
TheoryUseValueFIFO decimal (28, 3) Yes Description: Theoretical Use dollars using
FIFO for the cost evaluation.
Example: $123

Index Name Unique Clustered Fields


PK_ST_FoodCostByItem Yes Yes SiteNumber, StartSubPeriod, EndSubPeriod,
RawMaterialItemNumber

90 ST_FoodCostByItem Data Mart


ST_FoodCostByItemContractDaily

Description: Actual and Theoretical Food Cost Data by SITE by BUSINESS DATE by ITEM NUMBER.
Runs thru the Food Cost Calculations.

Triggered by Export_ProcessSTFoodCostByItemContractDaily.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. Use Theory is set to False (unchecked) and Use Contract Pricing is set to True (checked).
4. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business Date of activity.
Business date start time is defined in
Site Properties/Main/Day Time End.
Example: 2010-03-21
RawMaterialItemCategoryNumber int No Description: Category Number
(internal) assigned to the raw
material.
Note: Categories are defined in
ST_ItemCategories.
Example: 1001283
RawMaterialItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items
Example: 1000554
RawMaterialItemCost float No Description: Cost, expressed in item‟s
standard unit, based on last received
invoice date for the item. Can reflect
actual invoice price or contract price,
if exists.
Example: 2.333

Data Mart ST_FoodCostByItemContractDaily 91


Field Type Nulls? Comments
ActualEndingInventoryCount float Yes Description: Amount, expressed in
item‟s standard unit, of the last
inventory count for the day. If no
count is performed or if zero was
entered as the count, this value will
be represented as “0”.
Example: 156.546
ActualQuantityUsed decimal (28,3) No Description: Actual usage expressed
in the item‟s standard unit. The
calculation for actual usage is:
Beginning Inventory
+ Purchases/Transfers In
- Credits/Transfers Out
- Ending Inventory
= Actual Usage
Example: 30.667
TheoryQuantityUsed decimal (28,3) Yes Description: Theoretical usage
expressed in the item‟s standard unit.
The theoretical usage is based on the
item‟s “Theoretical Calculation”
setting.
 “Recipes” - Determined by the
sales mix (in raw materials) for
the site for the day.
 “Usage Per Factor” – Determined
by the item‟s calculated Usage Per
Factor applied against the sales
for the day.
Example: 1248.345

Index Name Unique Clustered Fields


PK_ST_FoodCostByItemContractDaily Yes Yes BusinessDate, SiteNumber,
RawMaterialItemNumber

92 ST_FoodCostByItemContractDaily Data Mart


ST_ForecastDailySalesAndGuests

Description: Forecast Daily for Sales and Guests Data by SITE by DATE.

Triggered by Export_ProcessSTForecastDailySalesAndGuests.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1002155
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BusinessDate datetime No Description: Business Date of Sales
Example: 2008-01-15
Sales decimal (19, 3) No Description: Total Daily Sales
Example: 7073.000
Guests decimal (19, 3) No Description: Total Daily Guests
Example: 177.000
LastModifiedByName nvarchar (100) Yes Description: Name of Last Modified By
Example: Cristina Adrianna
LastModifiedTime datetime No Description: Date of Last Modification
Example: 2007-12-21

Index Name Unique Clustered Fields


PK_ST_ForecastDailySalesAndGuests Yes Yes BusinessDate, SiteNumber

Data Mart ST_ForecastDailySalesAndGuests 93


ST_ForecastSalesGuestsByInterval_FromView *

Description: This table provides forecasted sales and guest counts by interval. These values can be
used to drive ordering, prep production, and labor scheduling and can be viewed directly from the
Back Office Switchboard „Forecasting‟ UI. In addition, this table includes actual sales by interval on
the same day of week for the previous year. Intervals are defined in „Sales Intervals‟ in Site
Properties (Back Office Manager|Site Properties|Main tab).

Triggered by Export_STForecastSalesGuestsByInterval_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business date of the forecast
Example: 2012-09-29
StartTime datetime No Description: The business date and start
time of the sales interval forecast as
defined in „Sales Interval‟
(Back Office Manager|Site Properties|Main
tab).
Example: 2012-09-29 04:00:00.000
Uses Site Local Time
EndTime decimal (19,3) No Description: The business date and end
time of the sales interval forecast as
defined in „Sales Interval‟
(Back Office Manager|Site Properties|Main
tab).
Example: 2012-09-29 04:30:00.000
Uses Site Local Time
CurrentSalesForecast decimal (19,3) No Description: Forecasted sales for the
defined interval after adjustments have
been made.
Example: 7073.00
CurrentGuestForecast decimal (19,3) No Description: Forecasted guest count for
the defined interval after adjustments
have been made.
Example: 177.000

94 ST_ForecastSalesGuestsByInterval_FromView * Data Mart


Field Type Nulls? Comments
SystemGeneratedSalesForec decimal (19,3) No Description: Total forecasted sales
ast (System Forecast) for defined interval.
Example: 7073.00
SystemGeneratedGuestForec decimal (19,3) No Description: Total forecasted guests
ast (System Forecast) for defined interval.
Example: 177.000
LastYearSales decimal (19,3) Yes Description: Actual sales for defined
interval (last year, same period, same
week, same day of week) .
Example: 773.000

Index Name Unique Clustered Fields


PK_ST_ForecastSalesGuests Yes Yes SiteNumber, BusinessDate, StartTime
ByInterval_FromView

* Table will not contain an index on the replicated database.

Data Mart ST_ForecastSalesGuestsByInterval_FromView * 95


ST_InactiveItemsBySite_FromView *

Description: This table provides information on items (raw, prep, menu, and modifiers) that are set as
“inactive” by site and the date the item became inactive. Items can be set as “inactive‟ in Back Office
Manager |Items|Item Maintenance. Inactive items are not available for purchasing and recipes based
on a specified date.

Triggered by Export_STInactiveItemsBySite_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number of where
the item is excluded.
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
ItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items.
Example: 1001865
InactiveDate datetime No Description: This field represents the date
of when the item became inactive. The
inactive date is entered in Back Office
Manager|Items|Item Maintenance.
Example: 2013-01-10

Index Name Unique Clustered Fields


PK_ST_InactiveItemsBySite_ Yes Yes SiteNumber, ItemNumber
FromView

* Table will not contain an index on the replicated database.

96 ST_InactiveItemsBySite_FromView * Data Mart


ST_InventoryLists_RealTimeFeed *

Description: This table provides all configured Inventory Lists with name and description. This table
can be used as a reference to match „InventoryListNumber‟ from
„ST_SiteInventoryListMembers_RealTimeFeed‟ and return the actual name and description.

Triggered by Export_STInventoryLists_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


InventoryListNumber int No Description: Inventory List Number (Internal)
Example: 1016921
InventoryListName nvarchar(50) No Description: Inventory List Name as
configured in Back Office
Manager|Inventory|Inventory List
Maintenance
Example: Daily
InventoryListDescription nvarchar(100) Yes Description: Inventory List Description as
configured in Back Office
Manager|Inventory|Inventory List
Maintenance
Example: Daily Inventory of Hot Items
ManageListItemsInSyste bit No Description: „Manage inventory list items &
mManagement activate „Unassigned Items‟ location‟ as
configured in Back Office
Manager|Inventory|Inventory List
Maintenance
0 = No
1 = Yes
Example: 0

Index Name Unique Clustered Fields


PK_ST_InventoryLists_RealTimeFeed Yes Yes InventoryListNumber

* Table will not contain an index on the replicated database.

Data Mart ST_InventoryLists_RealTimeFeed * 97


ST_InventoryTransfer

Description: Inventory Transfer Data by SITE by BUSINESS DATE by INVENTORY ITEM.

Triggered by Export_ProcessSTTransfers.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on LastModifiedTime.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
InvoiceNumber int No Description: Invoice Number (internal)
Example: 9
InvoiceID nvarchar (100) No Description: Invoice ID (Transfer ID)
Example: 1317 to 1311
ItemNumber int No Description: Item Number (internal)
Example: 1000554
ItemID nvarchar (40) No Description: Inventory Item ID
Example: 1450

98 ST_InventoryTransfer Data Mart


Field Type Nulls? Comments
ItemUnitNumber int No Description: Item Unit Number (internal)
Example: 6
ItemUnitName nvarchar (50) Yes Description: Item Unit Name
Example: EA=250ml
Quantity float Yes Description: Transfered Quantity
Example: 360
InventoryUnitPrice float Yes Description: Inventory Unit Price
Example; 12.713
ToFrom nvarchar (15) No Description: Transfer To or From
Example: To
Example: From
Type nvarchar (15) No Description: Transfer Type
Example: Raw
Example: Prep
BusinessDate datetime Yes Description: BusinessDate of Transfer
Example: 2008-12-21
Accepted bit Yes Description: Indicates if the transfer was
accepted
Example: 1
0 = No
1 = Yes
LastModifiedTime datetime No Description: Date & Time of Last Modification
Example: 2008-10-01 23:53:00.000
Uses UTC
LastModifiedByName nvarchar(100) Yes Description: Name of Last Modified By
Example: Francesca Caterina
TransferStatus nvarchar(1) Yes Description: Contains the status of the
transfer.
Possible values are:
P = Pending
A = Accepted
R = Rejected
Example: R

Index Name Unique Clustered Fields


PK_ST_InventoryTransfer Yes Yes SiteNumber, InvoiceNumber,
LastModifiedTime, ItemNumber,
ItemUnitNumber, ToFrom, Type,
SubPeriod

Data Mart ST_InventoryTransfer 99


ST_InvoiceDetails

Description: Invoice Detail Data by SITE by INVOICE DATE by INVOICE NUMBER

Triggered by Export_ProcessSTInvoices.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on Invoice Header LastModifiedDate. If an invoice is deleted in the Back Office
Switchboard|Purchasing Switchboard, a Data Mart export can be performed for the timeframe when
the invoice was previously modified to remove the invoice from the table.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
InvoiceNumber int No Description: Invoice Number (internal)
Example: 9
InvoiceID nvarchar (100) No Description: Invoice ID
Example 5008127
InvoiceDate datetime No Description: Invoice Date
Example: 2007-05-14

100 ST_InvoiceDetails Data Mart


Field Type Nulls? Comments
PurchasedItemNumber int No Description: Purchased Inventory Item Number
(internal)
Example: 1000107
PurchasedItemID nvarchar (50) No Description: Purchased Inventory Item ID
Example: 147
VendorItemID nvarchar (50) Yes Description: Vendor Item ID
Example: 66468
InvoiceLineItem smallint No Description: Invoice Line Item Number
Example: 45
QuantityReceived float Yes Description: Quantity Received
Example: 2
PurchaseUnitID int Yes Description: Purchased Conversion Unit ID
Example: 1322
PurchaseUnitName nvarchar (50) Yes Description: Purchase Unit Name
Example: CS=12 EA
PurchaseUnitPrice float Yes Description: Purcahsed Conversion Unit Price
Example: 12.76
ExtendedPrice float Yes Description: Extended Price (Conversion Unit
Quantity * Unit Price)
Example: 25.52
RawMaterialItemCatNum int Yes Description: Raw Material Item Category
Number (internal)
Example: 1000020
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 1401
RawMaterialItemCatNam nvarchar (100) Yes Description: Raw Material Item Category Name
e Example: SHORTENING
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
TaxAmount float Yes Description: Tax associated with a particular
line item.
Example: .70
ItemName nvarchar(250) Yes Description: The Item name
Example: Orange Juice
Notes nvarchar(255) Yes Description: Invoice item note
Example: Case damaged during shipment

Index Name Unique Clustered Fields


PK_ST_InvoiceDetails Yes Yes SiteNumber, InvoiceNumber, InvoiceDate,
PurchasedItemNumber, InvoiceLineItem

Data Mart ST_InvoiceDetails 101


ST_InvoiceDetailsSupplierReferenceNumber

Description: Invoice Supplier Reference Number by SITE by INVOICE DATE by INVOICE NUMBER.
Supplier Reference Number is not entered nor shown within NCR Back Office; this field is populated
via Invoice XML Import. A row will only exists in this table if there is a value in the
SupplierReferenceNumber field.

Triggered by Export_ProcessSTInvoices.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on Invoice Header LastModifiedDate. If an invoice is deleted in the Back Office
Switchboard|Purchasing Switchboard, a Data Mart export can be performed for the timeframe when
the invoice was previously modified to remove the invoice from the table.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 122000261
InvoiceNumber int No Description: Invoice Number (internal)
Example: 46
InvoiceDate datetime No Description: Invoice Date
Example: 2010-10-14
PurchasedItemNumber int No Description: Purchased Inventory Item
Number (internal)
Example: 1000107
InvoiceLineItem smallint No Description: Invoice Line Item Number
Example: 1
VendorItemID nvarchar (50) Yes Description: Vendor Item ID
Example: 15
SupplierReferenceNumber nvarchar (50) Yes Description: Supplier Reference Number.
Populated via Invoice XML Import. Not shown
on ML.
Example: 001235

Index Name Unique Clustered Fields


PK_ST_InvoiceDetailsSupplier Yes Yes InvoiceDate, SiteNumber, InvoiceNumber,
ReferenceNumber PurchasedItemNumber, InvoiceLineItem

102 ST_InvoiceDetailsSupplierReferenceNumber Data Mart


ST_InvoiceHeaders

Description: Invoice Header Data by SITE by INVOICE DATE by INVOICE NUMBER.

Triggered by Export_ProcessSTInvoices.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on the invoice‟s LastModifiedDate. If an invoice is deleted in the Back Office
Switchboard|Purchasing Switchboard, a Data Mart export can be performed for the timeframe when
the invoice was previously modified to remove the invoice from the table.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Data Mart ST_InvoiceHeaders 103


Field Type Nulls? Comments
SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
InvoiceNumber int No Description: Invoice Number (internal)
Example: 9
InvoiceID nvarchar (100) No Description: Invoice ID
Example 5008127
VendorNumber int No Description: Vendor Number (internal)
Example: 1000005
VendorID nvarchar (50) No Description: Vendor ID
Example: 349
VendorAPCode nvarchar (255) Yes Description: Vendor Accounts Payable Code
Example: 449
EndDate datetime Yes Description: End Date
Example: 2007-03-27
ReportingPeriod int Yes Description: Reporting Period Number
(internal)
Example: 3
Week int Yes Description: Week Number
Example: 1
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
InventoryPeriod int Yes Description: Inventory Period Number
(internal)
Example: 1
TotalAmountPayable money Yes Description: Total Amount Payable
Example: 1184.12
InvoiceDate datetime No Description: Invoice Date
Example: 2007-05-15
DueDate datetime Yes Description: Invoice Due Date
Example: 2007-04-20
FreightAmount money Yes Description: Freight Amount
Example: 6.58
SalesTaxAmount money Yes Description: Sales Tax Amount
Example: 13.98
Notes nvarchar (1000) Yes Description: Notes
Example: Case size on bottle ice tea and
bottle water
PODate datetime Yes Description: Purchase Order Date
Example: 2007-03-27
PONumber int Yes Description: Purchase Order Number
Example: 1234
CheckNumber nvarchar (255) Yes Description: Check Number
Example: ABC12345
DeliveredTime datetime Yes Description: Delivered Time
Example: 2007-03-27 14:30:00.000
User enters date & time of delivery.
CreatedBy int Yes Description: Creator of Invoice (internal)
Example: 1001471
CreatedByName nvarchar (100) Yes Description: Name of the Invoice Creator
Example: Hess Chu

104 ST_InvoiceHeaders Data Mart


Field Type Nulls? Comments
CreatedTime datetime Yes Description: Created Time
Example: 2007-03-27 14:25:46.000
Uses UTC
LastModifiedBy int Yes Description: Last Modified by Person
(internal)
Example: 1001471
LastModifiedByName nvarchar (100) Yes Description: Name of Last Modified By
Example: Hess Chu
LastModifiedDate datetime No Description: Date and Time of Last
Modification
Example: 2007-03-27 14:24:25.000
Uses UTC
InvoiceFinal bit No Description:Has the Invoice Been Finalized
0 = No
1 = Yes
Example:0 (default is 0 – not final)
SFDate datetime Yes Description: Export Date – user entered
No checking is done to constrain the date to
any particular range.
Example: 2005-12-21
SFInvoiceNumber nvarchar (100) Yes Description: Export Invoice Number – user
entered
If there is a value, this field must be unique
by vendor.
Example: 1000626
InvoiceType nvarchar(10) Yes Description: This indicates the type of invoice.
Example: Standard / Transfer / Paid Out /
Paid In
OriginalInvoiceID nvarchar(100) Yes Description: This is used for Adjustment
invoices and it contains the orginal Invoice ID
that the adjustment is for. Only Adjustment
invoices will have a value, all other invoices
will have a null value.
Example: 641001
InvoiceExternalID uniqueidentifier No Description: Global Unique ID for Invoices –
Used with external systems.
Example: 5294ea30-46e2-4874-93cc-
baced0cea1b8

Index Name Unique Clustered Fields


PK_ST_InvoiceHeaders Yes Yes SiteNumber, InvoiceNumber, VendorNumber,
InvoiceDate, LastModifiedDate

Data Mart ST_InvoiceHeaders 105


ST_ItemCategories *

Description: Item category information

Triggered by Export_STItemCategories.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


ItemCategoryNumber int No Description: Category Number (internal)
Example: 1456
ItemCategoryName nvarchar (100) No Description: Name assigned to specific
category
Example: Produce
ItemCategoryID nvarchar (25) No Description: Item Category ID assigned to
specific category
Example: RM – 8011-9876
ParentItemCategoryNumber int Yes Description: Category Number (internal) for
parent category assigned to specific
category
Example: 145600

Index Name Unique Clustered Fields


PK_ST_ItemCategories Yes Yes ItemCategoryNumber

* Table will not contain an index on the replicated database.

106 ST_ItemCategories * Data Mart


ST_ItemConversionFactors_RealTimeFeed *

Description: This table provides conversion factors for Raw, Prep, Menu and Modifier items.
Conversion factors describe the mathematical relationship between the Standard Unit and other
configured Units of Measure for the item.

Triggered by Export_STItemConversionFactors_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


ItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items.
Example: 1001865
ItemUnitNumber int No Description: Item Unit Number
(internal) assigned to the item in „Units
of Measure‟ in the Back Office
Manager|Items|General tab.
Note: Units of measure are defined in
ST_ItemUnitsOfMeasure
Example: 1234
UnitToStandardConversionFactor float No Description: Conversion factor to the
Standard Unit. The conversion factor is
configured in Back Office
Manager|Items|General tab.
Examples: 36; 0.16666666666666666
StandardToUnitConversionFactor decimal(19,3) Yes Description: Conversion factor from the
Standard Unit. The conversion factor is
configured in Back Office
Manager|Items|General tab when
„{Standard Unit} to Unit‟ is selected
from the dropdown in the „Units of
Measure groupbox.
Example: 1984.000

Index Name Unique Clustered Fields


PK_ST_ItemConversionFactors_RealTime Yes Yes ItemNumber, ItemUnitNumber
Feed

* Table will not contain an index on the replicated database.

Data Mart ST_ItemConversionFactors_RealTimeFeed * 107


ST_ItemPropertiesBySite_FromView *

Description: This table provides information on the item, such as purchaseable, taxable,
POSMenuItemPrice, POSItemNumber, and ordering information. In addition, this table identifies the
item type - Raw, Prep, Menu or a Modifier, as configured in Back Office Manager|Items|Item
Maintenance by site.

Triggered by Export_STItemPropertiesBySite_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
ItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items.
Example: 1001865
RawItem bit No Description: This bit value identifies the
item number as item type „Raw‟. This field
can be selected in Back Office
Manager|Items|Item Maintenance.
0 = Not checked
1 = checked
Example: 1
MenuItem bit No Description: This bit value identifies the
item number as item type „Menu‟. This
field can be selected in Back Office
Manager |Items|Item Maintenance.
0 = Not checked
1 = checked
Example: 0
PrepItem bit No Description: This bit value identifies the
item number as item type „Prep‟. This field
can be selected in Back Office Manager

108 ST_ItemPropertiesBySite_FromView * Data Mart


Field Type Nulls? Comments
|Items|Item Maintenance.
0 = Not checked
1 = checked
Example: 0
ModifierItem bit No Description: This bit value identifies the
item number as item type „Modifier‟. This
field can be selected in Back Office
Manager |Items|Item Maintenance.
0 = Not checked
1 = checked
Example: 0
Purchaseable bit No Description: This bit value represents if the
item is orderable.
Note: Only Raw items can be checked as
„Purchaseable‟.
0 = Not checked
1 = checked
Example: 0
Waste bit No Description: This bit value represents if the
item is a waste item that can be entered in
the „Spoil & Loss‟ UI from the Inventory
Switchboard.
Note: Modifiers cannot be checked as a
waste item Back Office
Manager|Items|Item Maintenance.
0 = Not checked
1 = Checked
Example: 0
Taxable bit No Description: This bit value represents if the
item is taxable.
Note: Only Raw items can be checked as
„Taxable‟ in Back Office
Manager|Items|Item Maintenance.
0 = Not checked
1 =Checked
Example: 0
RequireToOrder bit No Description: This bit value represents if the
item has a minimum & maximum quantity
amount that is required for ordering.
Note: Only „Raw‟ & „Prep‟ items can be
checked as „Require to Order‟ in Back
Office Manager|Items|Item Maintenance.
0 = Not checked
1 = Checked
Example:
RecommendedOrderByMethod int No Description: The recommended order by
method is selected in Back Office
Manager|Items|Item Maintenance for
„Raw‟ & „Prep‟ items only. This value is
used to determine the order amount of the
item based on the following methods:
0 = Par
1 = Forecasting
2 = Usage Per
Example: 2
TheoreticalCalculationMethod int No Description: The value in this field
represents the following theoretical
calculation method:
0 = “Recipes” - Determined by the sales
mix (in raw materials) for the site for the
day.

Data Mart ST_ItemPropertiesBySite_FromView * 109


Field Type Nulls? Comments
1 = “Usage Per Factor” – Determined by
the item‟s calculated Usage Per Factor
applied against the sales for the day.
Example:1
POSMenuItemPrice decimal(19,3) No Description: This value represents the
selling price of the Menu item only
configured in Back Office
Manager|Items|Item Maintenance.
Example: 2.590
POSItemNumber nvachar(255) No Description: This code identifies the item
being entered on the point of sale.
Example: 123

Index Name Unique Clustered Fields


PK_ST_ItemPropertiesBySite_ Yes Yes SiteNumber, ItemNumber
FromView

* Table will not contain an index on the replicated database.

110 ST_ItemPropertiesBySite_FromView * Data Mart


ST_ItemRecipeIngredients_FromView *

Description: This table contains the ingredients and ingredient amounts for the recipe.

Other recipe tables include:


 ST_ItemRecipes_FromView – Recipe Cost, “Recipe Makes” amount, recipe effective dates
 ST_ItemRecipeKitchenTools_FromView –Kitchen tools used within the recipe
 ST_ItemRecipePlateAndStores_FromView – Plates & stores to which the recipe is assigned
 ST_ItemRecipePrepStations_FromView – Prep stations to which the recipe is assigned

Triggered by Export_STItemRecipeIngredients_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number where the
recipe is managed.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1456
ItemNumber int No Description: Item Number (internal) for
the recipe.

Note: To determine where this recipe is


used, cross-reference this table‟s

Data Mart ST_ItemRecipeIngredients_FromView * 111


Field Type Nulls? Comments
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

Note: Items are defined in ST_Items.

Example: 1001865
RecipeNumber smallint No Description: Since multiple recipes can be
assigned to a single menu/prep item, this
field provides the sequence in which the
recipes were added. The first recipe
created for an item is „1‟.

Note: A „Menu Item‟ or „Prep Item‟ can


have multiple recipes defined but only one
can be “active” for any business day.

Note: Cross-reference this with


ST_ItemRecipes_FromView.

Example: 1
SequenceNumber smallint No Description: A sequential order of the
recipe ingredient entered in Back Office
Manager|Items|Item Maintenance|Modify
Recipe.

Example: 4
IngredientItemNumber int No Description: The internal number of the
raw or prep item listed in „Modify Recipe‟ in
the „Ingredient‟ tab in Back Office
Manager|Items|Item Maintenance|Modify
Recipe.

Note: Items are defined in ST_Items.

Example: 1045815
Amount decimal(19,3) No Description: This represents the amount
used for the corresponding
„IngredientItemNumber‟. The Amount is
entered on the Ingredients tab in the Units
column in „Modify Recipe‟ (Back Office
Manager |Items|Item Maintenance).

Example: 1.000
RecipeUnitNumber int No Description: The internal number of the
unit of measure (UOM) for recipe for the
corresponding „IngredientItemNumber‟.
The UOM is selected on the Ingredients tab
in the Units column in „Modify Recipe‟
(Back Office Manager |Items|Item
Maintenance).

Note: Unit of measure are defined in


ST_ItemUnitsOfMeasure.

112 ST_ItemRecipeIngredients_FromView * Data Mart


Field Type Nulls? Comments
Example: 1234
StandardAmount float No Description: This field provides the amount
converted to the item‟s standard unit of
measure.

Note: The item‟s standard unit of measure


is defined in ST_Items.

Example: 6.00
PrimaryIngredient bit No Description: This field is used to determine
the primary raw item in the recipe.
Note: Only one ingredient can be the
prime. Example: Avocado is the primary
ingredient of the guacamole.

Example: 1

Index Name Unique Clustered Fields


PK_ST_ItemRecipeIngredients Yes Yes SiteNumber, ItemNumber, RecipeNumber,
_FromView SequenceNumber

* Table will not contain an index on the replicated database.

Data Mart ST_ItemRecipeIngredients_FromView * 113


ST_ItemRecipeKitchenTools_FromView *

Description: This table provides information on the kitchen tool used in the recipe.

Other recipe tables include:


 ST_ItemRecipes_FromView – Recipe Cost, “Recipe Makes” amount, recipe effective dates
 ST_ItemRecipeIngredients_FromView – Quantities for each ingredient within the recipe
 ST_ItemRecipePlateAndStores_FromView – Plates & stores to which the recipe is assigned
 ST_ItemRecipePrepStations_FromView – Prep stations to which the recipe is assigned

Triggered by Export_STItemRecipeKitchenTools_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number where the
recipe is managed.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1456
ItemNumber int No Description: Item Number (internal) for
the recipe.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit

114 ST_ItemRecipeKitchenTools_FromView * Data Mart


Field Type Nulls? Comments
this recipe.

Note: Items are defined in ST_Items.

Example: 1001865
RecipeNumber smallint No Description: Since multiple recipes can be
assigned to a single menu/prep item, this
field provides the sequence in which the
recipes were added. The first recipe
created for an item is „1‟.

Note: A „Menu Item‟ or „Prep Item‟ can


have multiple recipes defined but only one
can be “active” for any business day.

Note: Cross-reference this field with


ST_ItemRecipeIngredients_FromView.Reci
peNumber.

Example: 1
KitchenToolNumber int No Description: Internal number of the
kitchen tool assigned to a recipe
ingredient.

Note: Kitchen tools are defined in


ST_KitchenTool_FromView.

Example: 1045820

Index Name Unique Clustered Fields


PK_ST_ItemRecipeKitchenTools Yes Yes SiteNumber, ItemNumber, RecipeNumber,
_FromView KitchenToolNumber

* Table will not contain an index on the replicated database.

Data Mart 115


ST_ItemRecipePlateAndStores_FromView *

Description: : This table provides information on the types of plates used in a Menu Item Recipe and
stores assigned to a prep item recipe.

Other recipe tables include:


 ST_ItemRecipes_FromView – Recipe Cost, “Recipe Makes” amount, recipe effective dates
 ST_ItemRecipeIngredients_FromView – Quantities for each ingredient within the recipe
 ST_ItemRecipeKitchenTools_FromView – Kitchen tools used within the recipe
 ST_ItemRecipePrepStations_FromView – Prep stations to which the recipe is assigned

Triggered by Export_STItemRecipePlateAndStores_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number where the
recipe is managed.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1456
ItemNumber int No Description: Item Number (internal) for
the recipe.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit

116 ST_ItemRecipePlateAndStores_FromView * Data Mart


Field Type Nulls? Comments
this recipe.

Note: Items are defined in ST_Items.

Example: 1001865
RecipeNumber smallint No Description: Since multiple recipes can be
assigned to a single menu/prep item, this
field provides the sequence in which the
recipes were added. The first recipe
created for an item is „1‟.

Note: A „Menu Item‟ or „Prep Item‟ can


have multiple recipes defined but only one
can be “active” for any business day.

Note: Cross-reference this field with


ST_ItemRecipeIngredients_FromView.Reci
peNumber.

Example: 1
PlateStoreNumber int No Description: Internal number of the types
of plate used in a Menu Item recipe and/or
store assigned to a Prep Item recipe.

Note: Plate and Store are defined in


ST_PlateStore_FromView.

Example: 1045821

Index Name Unique Clustered Fields


PK_ST_ItemRecipePlateAndStores Yes Yes SiteNumber, ItemNumber,
_FromView RecipeNumber, PlateStoreNumber

* Table will not contain an index on the replicated database.

Data Mart ST_ItemRecipePlateAndStores_FromView * 117


ST_ItemRecipePrepStations_FromView *

Description: This table provides information on the Prep Station assigned to the recipe.

Other recipe tables include:


 ST_ItemRecipes_FromView – Recipe Cost, “Recipe Makes” amount, recipe effective dates
 ST_ItemRecipeIngredients_FromView – Quantities for each ingredient within the recipe
 ST_ItemRecipePlateAndStores_FromView – Plates & stores to which the recipe is assigned
 ST_ItemRecipeKitchenTools_FromView – Kitchen tools used within the recipe

Triggered by Export_STItemRecipePrepStations_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
This is the internal site number where the
recipe is managed.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1456
ItemNumber int No Description: Item Number (internal) for
the recipe.

Note: To determine where this recipe is


used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.

118 ST_ItemRecipePrepStations_FromView * Data Mart


Field Type Nulls? Comments

Note: Items are defined in ST_Items.

Example: 1001865
RecipeNumber smallint No Description: Since multiple recipes can be
assigned to a single menu/prep item, this
field provides the sequence in which the
recipes were added. The first recipe
created for an item is „1‟.

Note: A „Menu Item‟ or „Prep Item‟ can


have multiple recipes defined but only one
can be “active” for any business day.

Note: Cross-reference this field with


ST_ItemRecipeIngredients_FromView.Reci
peNumber.

Example: 1
PrepStationNumber int No Description: Internal number of the Prep
Station assigned to the recipe.

Note: Prep Station are defined in


ST_PlateStore_FromView.

Example: 1045822

Index Name Unique Clustered Fields


PK_ST_ItemRecipePrepStations Yes Yes SiteNumber, ItemNumber, RecipeNumber,
_FromView PrepStationNumber

* Table will not contain an index on the replicated database.

Data Mart ST_ItemRecipePrepStations_FromView * 119


ST_ItemRecipes_FromView *

Description: This table provides „header‟ type information for a recipe such as – Recipe Name, Start &
End date of a recipe, „Recipe Makes‟ amount, Portion Size, KVI‟s, Procedures & Sensitivity
Information.

Other recipe tables include:


 ST_ItemRecipeIngredients_FromView – Quantities for each ingredient within the recipe
 ST_ItemRecipeKitchenTools_FromView – Kitchen tools used within the recipe
 ST_ItemRecipePlateAndStores_FromView – Plates & stores to which the recipe is assigned
 ST_ItemRecipePrepStations_FromView – Prep stations to which the recipe is assigned

Triggered by Export_STItemRecipes_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

120 ST_ItemRecipes_FromView * Data Mart


Field Type Nulls? Comments
SiteNumber int No Description: Site Number (internal)
This is the internal site number where the
recipe is managed.
Note: To determine where this recipe is
used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
ItemNumber int No Description: Item Number (internal) for
the recipe.
Note: To determine where this recipe is
used, cross-reference this table‟s
SiteNumber with
ST_RecipeVersionBySite_FromView.Inherit
edFromSiteNumber and this table‟s
ItemNumber with
ST_RecipeVersionBySite_FromView.ItemN
umber. The
ST_RecipeVersionBySite_FromView.SiteNu
mber will contain all the sites that inherit
this recipe.
Note: Items are defined in ST_Items.
Example: 1001865
RecipeNumber smallint No Description: Since multiple recipes can be
assigned to a single menu/prep item, this
field provides the sequence in which the
recipes were added. The first recipe
created for an item is „1‟.
Note: A „Menu Item‟ or „Prep Item‟ can
have multiple recipes defined but only one
can be “active” for any business day.
Note: Cross-reference this field with
ST_ItemRecipeIngredients_FromView.Reci
peNumber.
Example: 1
StartDate datetime No Description: The start date represents the
beginning date of the recipe.
Note: No overlapping recipes are allowed.
Example: 2013-01-01
EndDate datetime Yes Description: The end date represents when
the recipe is no longer active.
Note: No overlapping recipes are allowed.
If there is no date in this field, this recipe
would continue to be used until the „End
Date‟ is populated.
Example: 2013-12-31
RecipeName nvarchar(100) No Description: The name of the recipe for the
Menu Item or Prep Item defined in „Modify
Recipe‟ (Back Office Manager|Items|Item
Maintenance|Recipes).
Example: Petit Sirloin Dinner

Data Mart ST_ItemRecipes_FromView * 121


Field Type Nulls? Comments
RecipeMakesUnitNumber int No Description: The internal number of the
unit of measure (UOM) for the recipe. The
UOM is selected in the „Recipe Makes:‟ field
in „Modify Recipe‟ (Back Office Manager
|Items|Item Maintenance|Recipes).
Note: Unit of measure is defined in
ST_ItemUnitsOfMeasure
Example: 1016346
RecipeMakesAmount decimal(19,3) No Description: This field is the quantity for
the „Recipe Makes‟ unit of measure.
Example: 18.00
RecipeMakesStandardAmount float No Description: This field provides the „Recipe
Makes‟ amount converted to the item‟s
standard unit of measure.
Note: The item‟s standard unit of measure
is defined in ST_Items.
Example: 9.00
KeyVolumeIndicator1 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager|Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1019742
KeyVolumeIndicator1Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 3.00
KeyVolumeIndicator2 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager |Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1045817

122 ST_ItemRecipes_FromView * Data Mart


Field Type Nulls? Comments
KeyVolumeIndicator2Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 1
KeyVolumeIndicator3 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager |Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1045818
KeyVolumeIndicator3Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 2
KeyVolumeIndicator4 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager |Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1045819
KeyVolumeIndicator4Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume

Data Mart ST_ItemRecipes_FromView * 123


Field Type Nulls? Comments
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 1
KeyVolumeIndicator5 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager |Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1045820
KeyVolumeIndicator5Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 1
KeyVolumeIndicator6 int Yes Description: This is the internal number of
the KVI (Key Volume Indicator) data
definition assigned to the item recipe
(Back Office Manager |Configurable
Reporting & Data Mapping|Data
Definition).
Note: Site Property, „Display KVI Setup
Controls‟, must be checked in Back Office
Manager to use this field.
Note: Cross Reference this field with
ST_DataDefinitionConfiguration.DataDefinit
ionNumber
Example: 1045821
KeyVolumeIndicator6Quantity decimal(19,3) Yes Description: Represents the value entered
in the „Quantity‟ field for the corresponding
„Key Volume Indicator‟ in the „Key Volume
Indicator‟ tab (Back Office Manager
|Items|Item Maintenance|Modify Recipe
UI).

124 ST_ItemRecipes_FromView * Data Mart


Field Type Nulls? Comments
Note: Key Volume Indicators can be used
to apply specific weightings to like menu
items for reporting purposes. For example,
a 3-piece chicken strip dinner can have a
KVI quantity of „3‟ and a 6-piece chicken
strip dinner can have a KVI quantity of „6‟.
These KVI‟s can be used on configurable
reports to provide a sum total of the
number chicken strip sold.
Example: 2
Sensitivity bit No Description: This checkbox is used to
enable the SensitivityText field (Back
Office Manager |Items|Item
Maintenance|Modify Recipe|Component
tab):
0 = Checked
1 = Unchecked
Example: 0
SensitivityText nvarchar(1000) Yes Description: This field is an open text field
used to enter special cooking instructions
that can be printed on a recipe card.
Example: Steak must be seasoned well
before cooking
PrintedShelfLife bit No Description: This checkbox is used to
enable the PrintedShelfLifeText field(Back
Office Manager |Items|Item
Maintenance|Modify Recipe|Component
tab)
0 = Checked
1 = Unchecked
Example: 1
PrintedShelfLifeText nvarchar(20) Yes Description: This field is used to enter
shelf life information for the recipe.
Example: Discard after 2 days
PortionSizeUnitNumber int Yes Description: The internal number of the
unit of measure (UOM) for the Prep item
recipe. The UOM is selected in the „Portion
Size:‟ field in „Modify Recipe‟ (Back Office
Manager|Items|Item Maintenance) for the
Prep item recipe.
Note: UOM is defined in
ST_ItemUnitsOfMeasure.ItemUnitofMeasur
eNumber
Example: The recipe for aujus sauce
makes 10 gallons but the portion size 1
cup.
Example: 1016346
PortionSizeAmount decimal(19,3) Yes Description: This field is defined in Prep
Item recipes to show the portion amount
used, based on the unit of measure.
Example: 18.00

Index Name Unique Clustered Fields


PK_ST_ItemRecipes_FromView Yes Yes SiteNumber, ItemNumber, RecipeNumber

* Table will not contain an index on the replicated database.

Data Mart ST_ItemRecipes_FromView * 125


ST_Items *

Description: This table provides item information for Raw, Prep, Menu, and Modifiers, such as the item
categories the item is assigned and standard of unit

Triggered by Export_STItems.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


ItemNumber int No Description: Item Number (internal)
Example: 1000554
ItemName nvarchar (250) No Description: Name assigned to specific item
Example: Hamburger Patty
ItemID nvarchar (40) No Description: Item ID assigned to specific item
Example: RM – 1234
StandardUnitNumber int No Description: Standard Unit of Measure assigned to
Item; references ST_ItemUnitofMeasure (internal
number)
Example: 1001283
NormalizeFoodCost bit No Description: Set item to report as normalized -
where theoretical is set to actual
0 = Not normalized
1 = Normalized
Example: 0
ItemCategoryNumber int No Description: Category Number (internal) for raw
items.

Note: Since this field cannot be NULL, the internal


number populated in this field may not represent
the ItemCategory but may represent the internal
number for the category the Item is actually
assigned to.

For example: Item, „Cherry Pie‟, is assigned a


Menu Item Category (Internal number = 1456).
The fields will be populated as:
ItemCategoryNumber = 1456
PrepItemCategoryNumber = 1456
MenuItemCategoryNumber = 1456
ModifierItemCategoryNumber = 1456

Note: ItemCategory is defined in

126 ST_Items * Data Mart


Field Type Nulls? Comments
ST_ItemCategories

Example: 12030564
MenuItemCategoryNu int No Description: Category Number (internal) for Menu
mber items.

Note: Since this field cannot be NULL, the internal


number populated in this field may not represent
the MenuItemCategory but may represent the
internal number for the category the Item is
actually assigned to.

For example: Item, „Cherry Pie‟, is assigned a


Raw Item Category (Internal number = 1515).
The fields will be populated as:
ItemCategoryNumber = 1515
PrepItemCategoryNumber = 1515
MenuItemCategoryNumber = 1515
ModifierItemCategoryNumber = 1515

Note: ItemCategory is defined in


ST_ItemCategories

Example: 12030564
PrepItemCategoryNu int No Description: Category Number (internal) for prep
mber items.

Note: Since this field cannot be NULL, the internal


number populated in this field may not represent
the PrepItemCategory but may represent the
internal number for the category the Item is
actually assigned to.

For example: Item, „Cherry Pie‟, is assigned a


Menu Item Category (Internal number = 1456).
The fields will be populated as:
ItemCategoryNumber = 1456
PrepItemCategoryNumber =1456
MenuItemCategoryNumber = 1456
ModifierItemCategoryNumber = 1456

Note: ItemCategory is defined in


ST_ItemCategories

Example: 12030564
ModifierItemCategory int No Description: Category Number (internal) for
Number modifier items.

Note: Since this field cannot be NULL, the internal


number populated in this field may not represent
the ModifierItemCategory but may represent the
internal number for the category the Item is
actually assigned to.

For example: Item, „Cherry Pie‟, is assigned a


Menu Item Category (Internal number = 1456).
The fields will be populated as:
ItemCategoryNumber = 1456
PrepItemCategoryNumber =1456
MenuItemCategoryNumber = 1456
ModifierItemCategoryNumber = 1456

Data Mart ST_Items * 127


Field Type Nulls? Comments

Note: ItemCategory is defined in


ST_ItemCategories

Example: 12030564

Index Name Unique Clustered Fields


PK_ST_Items Yes Yes ItemNumber

* Table will not contain an index on the replicated database.

128 ST_Items * Data Mart


ST_ItemUnitsOfMeasure *

Description: Item units of measure information.

Triggered by Export_STItemUnitsOfMeasure.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


ItemUnitofMeasureNumber int (4) No Description: Item Unit of Measure Number
(internal)
Example: 1456
ItemUnitofMeasureName nvarchar (50) No Description: Name assigned to Unit of Measure
Example: Pound

Index Name Unique Clustered Fields


PK_ST_ItemUnitsOfMeasure Yes Yes ItemUnitOfMeasureNumber

* Table will not contain an index on the replicated database.

Data Mart ST_ItemUnitsOfMeasure * 129


ST_ItemUseDaily

Description: Item Usage by SITE, by DATE by RAW MATERIAL.


Food Cost Calculations with Waste Added.

Triggered by Export_ProcessSTItemUseDaily.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. SubPeriod field shows which subperiod the day belongs to.
4. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311

130 ST_ItemUseDaily Data Mart


Field Type Nulls? Comments
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
SalesDate datetime No Description: Business Date
Example: 2007-03-27
RawMaterialItemNum int No Description: Item Number (internal)
Example: 1000554
RawMaterialItemID nvarchar (40) Yes Description: Item ID
Example: 272
RawMaterialItemName nvarchar (250) Yes Description: Raw Material Item Name
Example: Dip, Buffalo Ranch
TheoryUse float Yes Description: Theoretical Usage
Example: 4.67
ItemUnitNumber int No Description: Item Unit Number (internal)
Example: 6
ItemUnitName nvarchar (50) Yes Description: Item Unit Name
Example: EA=250ml
TheoreticalOnHandCount float Yes Description: Theoretical On Hand Count
Example: 300
ActualOnHandCount float Yes Description: Actual On Hand Count
Example: 184
ItemCost float Yes Description: Item Cost by Conversion Unit.

ItemCost = Ending Inventory Value / Ending


Inventory Quantity. If Ending Inventory Quantity
is zero then ItemCost = 0.

Ending Inventory Value = TodaysValue


Ending Inventory Quantity = ActualOnHandCount

Example: 1.33
TodaysValue float Yes Description: Current On Hand Count
Example: 244.72
YActualOnHandCount float Yes Description: Previous Actual On Hand Count
Example: 192
YItemCost float Yes Description: Previous Item Cost
Example: 1.33
YesterdayValue float Yes Description: Previous Days Item Cost by
Conversion Unit
Example: 256.17
QtyBought float Yes Description: Quantity Bought
Example: 12
Waste float Yes Description: Waste
Example: 0
TransferIn float Yes Description: Quantity Transferred In
Example: 0
TransferOut float Yes Description: Quantity Transferred Out
Example: 0
InvQtyTransferred float Yes Description: Inventory Quantity Transferred
Transferred In minus Transferred Out
Example: 8.2
PurchaseValue float Yes Description: Purchased Value
Example: 0

Data Mart ST_ItemUseDaily 131


Field Type Nulls? Comments
ActualUse float Yes Description: Actual Usage
Example: 0
ActualUseValue float Yes Description: Actual Usage Value
Example: 0
UnitCostExtended decimal (19,5) No Description: Extended cost based on the
Inventory Extension Report to five decimal
places.
Example: 0.53072

Index Name Unique Clustered Fields


PK_ST_ItemUseDaily Yes Yes SiteNumber, SalesDate, RawMaterialItemNum

132 ST_ItemUseDaily Data Mart


ST_ItemUseVariance

Description: Difference between Actual and Theoretical Inventory.


Goes thru Food Cost daily by site calculations.

Triggered by Export_ProcessSTItemUseVariance.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SubPeriod int No Description: Sub Period Number (internal)
Example: 65
SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
RawMaterialItemCatNum int Yes Description: Raw Material Item Category
Number (internal)
Example: 1000009

Data Mart ST_ItemUseVariance 133


Field Type Nulls? Comments
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category Name
Example: Nuggets
RawMaterialItemNumber int No Description: Item Number (internal)
Example: 1000554
RawMaterialItemID nvarchar (40) Yes Description: Raw Material Item ID
Example: 13
RawMaterialItemName nvarchar (250) Yes Description: Raw Material Item Name
Example: Dip, Buffalo Ranch
ItemUnitNumber int No Description: Item Unit Number (internal)
Example: 6
ItemUnitName nvarchar (50) No Description: Item Unit Name
Example: EA=250ml
SumOfTheoryUse float Yes Description: Theoretical Usage Quantity
Example: 171.64
EndingItemCost money Yes Description: Ending Item Cost
Example: 1.40
ActualUsage float Yes Description: Actual Quantity Usage
Example: 40
ActualUse$ float Yes Description: Actual Usage Value
Example: 21.66
Variance float Yes Description: Actual to Theoretical Quantity
Variance
Example: -4.27
IdealUse$ float Yes Description: Theoretical Usage Value
Example: 12.19
Variance$ float Yes Description: Actual to Theoretical Variance
Value
Example: -9.43
SubPeriodStartDate datetime Yes Description: The start date of the subperiod
Example: 2007-02-01
SubPeriodEndDate datetime Yes Description: The end date of the subperiod
Example: 2007-02-14

Index Name Unique Clustered Fields


PK_ST_ItemUseVariance Yes Yes SubPeriod, SiteNumber,
RawMaterialItemNumber,
ItemUnitNumber
IX_ST_ItemUseVariance_StartDt No No SubPeriodStartDate

134 ST_ItemUseVariance Data Mart


ST_Jobs *

Description: This table provides the job properties that are „global‟ settings. Global settings affect all
sites and site versions of these properties are not supported. This table is updated when a „Job‟ is
created or updated in Back Office Manager.

Triggered by Export_STJobs.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


JobNumber int No Description: Job Number (internal)
Example: 1000626
JobName nvarchar(100) No Description: Name assigned to job
Example: Assistant General Manager
JobID nvarchar(25) No Description: The Jobcode ID identifier as
defined in Back Office Manager|Labor|Jobcode
Maintenance.
Example: 1001
DirectTips bit No Description: The setting for Exported Tip
Values|Export Declared Tips to „Tips Amount‟
for this job
0 = Do not export Declared Tips to „Tips
Amount‟
1 = Export Declared Tips to „Tips Amount‟
Example: 1
InDirectTips bit No Description: The setting for Exported Tip
Values|Export Declared Tips to „Indirect Tips
Amount‟ for this job
0 = Do not export Declared Tips to „Indirect
Tips Amount‟
1 = Export Declared Tips to „Indirect Tips
Amount‟
Example: 0

Data Mart ST_Jobs * 135


Field Type Nulls? Comments
DeductBreaks bit No Description : The schedule will automatically
deduct breaks for all qualified scheduled shifts
for this job
0 = Do not automatically deduct breaks for
qualified scheduled shifts
1 = Automatically deduct breaks for qualified
schedule shifts
Example : 1
LaborGroupNumber int Yes Description : Labor Group Number (Internal)
Example : 1
JobPayrollCode nvarchar (25) Yes Description : The Job Payroll Export Code
assigned to the job
Example: 10
NonServiceJob bit No Description: The setting for „Schedule displays
a single recommended hours amount‟ for the
day for this job
0 = False
1 = True
Example: 0
AlternateSalesForecastJob bit No Description : The setting for „Schedule Uses
Forecasted Alternate Sales for Labor %‟
0 = False
1 = True
Example : 1
ExcludeScheduleMetrics bit No Description : The setting for „Exclude Hours
and Dollars from Metrics on Schedule‟ for this
job
0 = False
1 = True
Example = 1

Index Name Unique Clustered Fields


PK_ST_Jobs Yes Yes JobNumber

* Table will not contain an index on the replicated database.

136 ST_Jobs * Data Mart


ST_KitchenTool_FromView *

Description: This table provides information on kitchen tools defined in Back Office
Manager|Inventory|Kitchen Tool Maintenance.

Triggered by Export_STKitchenTool_FromView.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


KitchenToolNumber int No Description: Internal Number of the kitchen
tool defined in Back Office Manager.
Example: 1045821
KitchenToolName nvarchar(50) No Description: Name of the kitchen tool as
defined in Back Office Manager.
Example: Chef Knife

Index Name Unique Clustered Fields


PK_ST_KitchenTool_FromView Yes Yes KitchenToolNumber

* Table will not contain an index on the replicated database.

Data Mart ST_KitchenTool_FromView * 137


ST_MIC

Description: Sales Mix broken down into site items as raw materials to get cost of goods and summed
for total price.

Triggered by Export_ProcessSTMIC.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
ItemNumber int No Description: Item Number (internal)
Example: 1000554
MenuItemID nvarchar (40) No Description: Menu Item ID
Example: 627
MenuItemCatNum int Yes Description: Menu Item Category Number
(internal)
Example: 1000413
MenuItemCatID nvarchar (25) Yes Description: Menu Item Category ID
Example: 4563
MenuItemCatName nvarchar (100) Yes Description: Menu Item Category Name
Example: * SANDWICHES

138 ST_MIC Data Mart


Field Type Nulls? Comments
MenuItemName nvarchar (250) Yes Description: Menu Item Name
Example: GRILLED RGC TWST
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
TotalNumberSold float Yes Description: Total Number Sold
Example: 1
PriceSoldAt money No Description: Price Sold At
Example: 4.29
SumOfPortionCost float Yes Description: Sum of Portion Cost
Example: 1.482
Contribution float Yes Description: Contribution
Example: 2.808
TotalDollarsSold float Yes Description: Total Dollars Sold
Example: 4.29
SubPeriodStartDate datetime Yes Description: The start date of the subperiod
Example: 2010-02-05
SubPeriodEndDate datetime Yes Description: The end date of the subperiod
Example: 2010-02-14

Index Name Unique Clustered Fields


PK_ST_MIC Yes Yes SiteNumber, SubPeriod, ItemNumber,
PriceSoldAt
IX_ST_MIC_StartDt No No SubPeriodStartDate

Data Mart ST_MIC 139


ST_OccasionCategoriesOccasions

Description: This table contains information about the Occasions feature maintained within
Configuration Center (CFC). It contains OccasionCategoriesOccasions combined with
OccasionCategories information.

Triggered by Export_ProcessSTOccasions.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


OccasionCategoryUniqueID uniqueidentifier No Description: Occasion Category Unique ID
but not unique within this table.
Example: F8797CBD-64A2-48E9-0C0C-
5A1028760C01
OccasionUniqueID uniqueidentifier No Description: Occasion Unique ID but not
unique within this table.
Example: 0CF49A96-4CCD-446F-AD21-
B8A9AB7DF7AC
OccasionCategoryID int No Description: Occasion Category ID
Example: 1
OccasionCategoryName nvarchar(50) No Description: Occasion Cateogory Name
Example: Cultural Events

Index Name Unique Clustered Fields


PK_ST_OccasionCategoriesOccasions Yes No OccasionCategoryUniqueID,
OccasionUniqueID

140 ST_OccasionCategoriesOccasions Data Mart


ST_Occasions

Description: This table contains information about the Occasions feature maintained within Aloha
Configuration Center (CFC).
It contains Occasions combined with SiteOccasions information.

Triggered by Export_ProcessSTOccasions.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


UniqueID nvarchar (100) No Description: Unique ID (internal) – needed to create
primary key. It is a combination of
OccasionUniqueID plus SiteNumber. Note: There
can be occasions without siteoccasions.
Example: 0CF49A96-4CCD-446F-AD21-
B8A9AB7DF7AC:1000204
Example: F8797CBD-64A2-48E9-0C0C-
5A1028760C02:
SiteNumber int Yes Description: Site Number (internal)
Example: 145612
StoreID nvarchar (50) Yes Description: Store ID
Example: 2121
OccasionUniqueID uniqueidentifier No Description: Occasion Unique ID (internal) but not
unique within this table.
Example: 0CF49A96-4CCD-446F-AD21-
B8A9AB7DF7AC
OccasionID int No Description: Occasion ID
Example: 890
OccasionName nvarchar(50) No Description: Occasion Name
Example: Indian Cultural Festival
EventIdentifier nvarchar(50) Yes Description: Event Identifier
Example: NonFootball10082008

Data Mart ST_Occasions 141


Field Type Nulls? Comments
ParTemplateID int Yes Description: Par template ID
Example: 123
ParTemplateName nvarchar(50) Yes Description: Par template name
Example: Healthy Food Carts
StartTime datetime Yes Description: Start Time
Example:
EndTime datetime Yes Description: End Time
Example:
CreatedTime datetime No Description: Date this occasion was created
Example:
ModifiedTime datetime No Description: Date of Last Modification
Example:

Index Name Unique Clustered Fields


PK_ST_Occasions Yes No UniqueID

IX_ST_Occasions No Yes OccasionUniqueID, SiteNumber

142 ST_Occasions Data Mart


ST_PayrollStatus_FromView *

Description: This table provides payroll status information by site. Records in this table will be created
when a site completes the „Payroll-Finalize‟ workflow action (Back Office
Switchboard|Workflow|Workflow Selection). Records will be updated if changes are made to a
„Finalized‟ payroll period.

Triggered by Export_STPayrollStatus_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site number (internal)

Note: Sites are defined in


„ST_SitesAndSiteGroups.SiteNumber‟

Example:1456
PayPeriodStartDate datetime No Description: Start date of the specified payroll
period, which is defined by the value set in
the „Param 1‟ field of the „SetDaysBack‟ action
in the „Payroll-Finalize‟ workflow.

Example: 2013-4-23
PayPeriodEndDate datetime No Description: End date of the specified payroll
period, which is defined by the value set in
the „Param 1‟ field of the „SetDaysBack‟ action
in the „Payroll-Finalize‟ workflow.

Example: 2013-4-23
Status smallint No Description: Payroll status – populated based
on the following conditions:
„1‟ = Finalized – A payroll period is „finalized‟
through the „Payroll-Finalize‟ workflow action
„2‟ = Unfinalized – A payroll period is
unfinalized by selecting the „Unfinalize‟ button
on the „Modify Shifts‟ UI. (Labor
Switchboard|Payroll|Shifts|Modify Shifts)
„3‟ = Re-finalized – A payroll period is re-
finalized by selecting the „Re-finalize‟ button
on the „Modify Shifts‟ UI or by reprocessing
the „Payroll-Finalized‟ workflow.

Example: 1

Data Mart ST_PayrollStatus_FromView * 143


Field Type Nulls? Comments
CreatedBy int No Description: User number (internal) –
represents the user that initially executed the
„Payroll-Finalize‟ workflow

Note: Users are defined in


„ST_Users_RealTimeFeed.UserName‟

Example: 1232
CreatedTime datetime No Description: Date and time that the „Payroll-
Finalize‟ workflow was initially executed

Example: 2013-4-23 14:37:38.000


Uses UTC
LastModifiedBy int No Description: User number (internal) –
populates when a user re-initiates the
„Payroll-Finalize‟ workflow or when a payroll
period is unfinalized or re-finalized from the
„Modify Shifts‟ UI (whichever occurred last).

Note: Users are defined in


„ST_Users_RealTimeFeed.UserName‟

Example: 1234
LastModifiedTime datetime No Description: Date and time that user re-
initiated the „Payroll-Finalize‟ workflow or
unfinalized/re-finalized the payroll period
from the „Modify Shifts‟ UI (whichever
occurred last).

Example: 2013-4-23 14:37:38.000


Uses UTC

Index Name Unique Clustered Fields


PK_ST_PayrollStatus_FromView Yes Yes SiteNumber, PayPeriodStartDate

* Table will not contain an index on the replicated database.

144 ST_PayrollStatus_FromView * Data Mart


ST_PayrollStatusDetail_FromView *

Description: This table provides payroll modification information by site, by payroll period. Payroll
period change information will not populate this table until the „Payroll-Finalization‟ workflow is initially
run for a payroll period (Back Office Switchboard|Workflow).

Triggered by Export_STPayrollStatusDetail_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site number (internal)

Note: Sites are defined in


„ST_SitesAndSiteGroups.SiteNumber‟

Example:1456
StartDate datetime No Description: Start date of the specified payroll
period, which is defined by the value set in
the „Param 1‟ field of the „SetDaysBack‟ action
in the „Payroll-Finalize‟ workflow.

Example: 2013-4-23
EndDate datetime No Description: End date of the specified payroll
period, which is defined by the value set in
the „Param 1‟ field of the „SetDaysBack‟ action
in the „Payroll-Finalize‟ workflow.

Example: 2013-4-30
BusinessDate datetime Yes Description: Business date that a change was
applied to.

Example: 2013-4-23
ActionType smallint No Description: Type of change made to a
„Finalized‟, „Unfinalized‟, or „Re-finalized‟
payroll period.

„1‟ = ‘Labor’ POS Import After


Finalization - applied if POS time punch
information is imported after the „Payroll-
Finalize‟ workflow action is run (Labor
Switchboard|Manager Tools|Import).

„2‟ = Punch Errors After Finalization –


applied if time punch errors are corrected
after the „Payroll-Finalize‟ workflow action is

Data Mart ST_PayrollStatusDetail_FromView * 145


Field Type Nulls? Comments
run. The „Employee Punches Errors‟ report
(#87) can be run at Labor
Switchboard|Reports.

„3‟ = Shift Adjustments After Finalization


– applied if shift adjustments are made after
the „Payroll-Finalize‟ workflow action is run.
Shift adjustments include:
Add/edit/delete worked hours
Add/edit/delete paid or unpaid breaks
Add/edit/delete non-worked hours

„4‟ = Clear POS Data After Finalization –


applied if existing POS import data is cleared
and re-imported for a specified business date.

„5‟ = Finalized- applied when the „Payroll-


Finalized‟ workflow action is successfully run.

„6‟ = Unfinalized – applied when the


„Unfinalize Payroll‟ button is selected on the
„Modify Shifts‟ UI (Labor
Switchboard|Payroll|Shifts)

„7‟ = Re-finalized – applied when


„Re-finalize Payroll‟ button is selected on the
„Modify Shifts‟ UI (Labor
Switchboard|Payroll|Shifts|Modify Shifts)

„8‟ = Recalculate payroll – applied when the


„Recalculate‟ button is selected on the „Time
Clock Utilities‟ screen (Back Office
Manager|Configuration Settings|Labor|Payroll
Maintenance|Time Clock Utilities)

Example: 1
ChangedBy int No Description: User number (internal) –
represents the user that made a change to a
payroll period (edited, imported, or cleared).

Note: Users are defined in


„ST_Users_RealTimeFeed.UserName‟

Example: 1232
ChangeDateTime datetime No Description: Date and time that a change was
made to a payroll period.

Example: 2013-4-23 14:37:38.000


Uses UTC
RecordNumber bigint No Description: A unique record identifier
(internal). Note: This is an Identity field
type. Do not use.

Example: 12

Index Name Unique Clustered Fields


PK_ST_PayrollStatusDetail Yes Yes RecordNumber
_FromView

* Table will not contain an index on the replicated database.

146 ST_PayrollStatusDetail_FromView * Data Mart


ST_PlateStore_FromView *

Description: This table provides information on Plate Store defined in Back Office Manager
|Inventory|PlateStore Maintenance and Plate Store internal number.

Triggered by Export_STPlateStore_FromView.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


PlateStoreNumber int No Description: Internal Number of the
plate/store defined in Back Office Manager.
Example: 1045822
PlateStoreName nvarchar(50) No Description: Name of the kitchen tool as
defined in Back Office Manager.
Example: 12” Large Plate
Plate bit No Description: This field is used to denote if the
„PlateStoreName‟ is defined as either a Plate
or Store in a bit value:

0 = Store
1 = Plate

Note: In Back Office Manager |Inventory


|PlateStore Maintenance|Plate/Store lookup,
displays the option to select Plate or Store.

Example: 1

Index Name Unique Clustered Fields


PK_ST_PlateStore_FromView Yes Yes PlateStoreNumber

* Table will not contain an index on the replicated database.

Data Mart ST_PlateStore_FromView * 147


ST_PrepStations_FromView *

Description: This table provides information on Prep Stations defined in Back Office Manager
|Inventory|Prep Station Maintenance and the internal number.

Triggered by Export_STPrepStations_FromView.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


PrepStationNumber int No Description: Internal Number of the Prep
Station defined in Back Office Manager.
Example: 1045820
PrepStationName nvarchar(50) No Description: Name of the Prep Station as
defined in Back Office Manager.
Example: Dessert Prep Counter

Index Name Unique Clustered Fields


PK_ST_PrepStations_FromView Yes Yes PrepStationNumber

* Table will not contain an index on the replicated database.

148 ST_PrepStations_FromView * Data Mart


ST_POSSOS

Description: Summary Table Point of Sale Speed of Service. The table contains Speed or Service
information generated by the POS and grouped by SiteNumber, BusinessDate and ModeID.

Triggered by Import_POS_SOS.sql

Notes:
1. This table is not populated via Data Mart Export. This table is populated when importing Aloha
POS – Speed of Service.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (50) Yes Description: Store ID
Example: 2121
BusinessDate datetime No Description: Business Date
Example: 2007-03-14
ModeID nvarchar (50) No Description: Mode ID
Example: 3
TransactionCount decimal (19, 3) Yes Description: Transaction count is a count of
all checks by MODEID. The user can, if
required, total all transaction counts by
MODEID to receive a daily count.
Example: 183
HiVolumeTransactionCount decimal (19, 3) Yes Description: High Volume specifies that a
transaction is opened prior to the previous
transaction being bumped in the same
MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter

Data Mart ST_POSSOS 149


Field Type Nulls? Comments
how many orders are in queue at that time.
Example: 73
LowVolumeTransactionCo decimal (19, 3) Yes Description: Low Volume specifies that a
unt transaction is opened and all previous orders
have been bumped in the same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 110
OrderTime decimal (19, 3) Yes Description: Order time is the sum of
seconds between the open time and the last
payment applied which will provide a
number for how long it took the cashier to
place the order.
Each order mode should have total seconds
for all checks within the order mode.
Example: 18608
HiVolumeOrderTime decimal (19, 3) Yes Description: High Volume specifies that a
transaction is opened prior to the previous
transaction being bumped in the same
MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 2008
LowVolumeOrderTime decimal (19, 3) Yes Description: Low Volume specifies that a
transaction is opened and all previous orders
have been bumped in the same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 3591
DeliveryTime decimal (19, 3) Yes Description: Delivery time is the sum of
seconds between the last payment applied
and the last item bumped which will provide
a number for how long it took to fill the
order once sent to the video.
Example: 7984
TotalTime decimal (19, 3) Yes Description: Total time is the sum of seconds
between the last item bumped and the check
open time which will provide a number for
the total time from the start of the order to
the completion of the order.
Example: 26592
HiVolumeTotalTime decimal (19, 3) Yes Description: High Volume specifies that a
transaction is opened prior to the previous
transaction being bumped in the same
MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 13721

150 ST_POSSOS Data Mart


Field Type Nulls? Comments
LowVolumeTotalTime decimal (19, 3) Yes Description: Low Volume specifies that a
transaction is opened and all previous orders
have been bumped in the same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 12871
HiVolumeLineTime decimal (19, 3) Yes Description: Line time is the sum of seconds
between the previous check‟s last item
bumped and current check‟s last item
ordered. This will provide a number for the
time for how long the order waited in queue
until it could begin to be worked. High
Volume specifies that a transaction is opened
prior to the previous transaction being
bumped in the same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 6106
HiVolumeWindowTime decimal (19, 3) Yes Description: High Volume Window time is the
sum of seconds between the previous order‟s
last item bumped and current order‟s last
item bumped. This will provide a number for
the time for how long the order took once it
became first in queue. High Volume specifies
that a transaction is opened prior to the
previous transaction being bumped in the
same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time
Example: 5933
LowVolumeWindowTime decimal (19, 3) Yes Description: Low Volume Window time is the
sum of seconds between the last item
ordered and last item bumped. This will
provide a number for the time for how long
the order took after it was sent to the
kitchen. Low Volume specifies that a
transaction is opened and all previous orders
have been bumped in the same MODEID.
Note – If a check is opened and a single
previous order has not been bumped, it is
considered high volume. It does not matter
how many orders are in queue at that time.
Example: 9280

Index Name Unique Clustered Fields


PK_POSSOS Yes Yes SiteNumber, BusinessDate, ModeID

Data Mart 151


ST_PromosComps

Description: Promotions and Comps that were imported from the POS System.

Triggered by Export_ProcessSTPromosComps.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (50) Yes Description: Store ID
Example: 2121
BusinessDate datetime No Description: Business Date
Example: 2009/04/14
PromoCompType tinyint No Description: Indicator if Item is a Promo or
Comp.
1 = Comp
2 = Promo
Example: 1
ID float No Description: Internal identifier from the POS
System.
Example: 4
Name nvarchar(20) Yes Description: Name of the Comp or Promo.
Example: Employee Meal
Amount decimal (19, 3) No Description: Dollar amount
Example: 11.68
Quantity decimal (19, 3) No Description: Count
Example: 1

Index Name Unique Clustered Fields


PK_ST_PromosComps Yes Yes SiteNumber, BusinessDate, PromoCompType, ID

152 ST_PromosComps Data Mart


ST_Punches

Description: Clock-in/Clock-out by SITE, by DATE, by EMPLOYEE

Triggered by Export_ProcessSTPunches.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
Year nvarchar (4) Yes Description: Year
Example: 2007
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
SalesDate datetime No Description: Sales Date
Example: 2007-03-29
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobID nvarchar (25) Yes Description: Job ID
Example: 2009
JobTitle nvarchar (50) Yes Description: Job Title
Example: Food Service Team Member

Data Mart ST_Punches 153


Field Type Nulls? Comments
Source nvarchar (100) Yes Description: Source of Information
 The source in the ST_Punches is blank
if the POS Imports the punch
 If a user edits the punch or enters a
punch manually then the source
becomes that user
Example: Hess Chu
ClockIn datetime No Description: Clock-in
Example: 2007-03-29 15:00:00.000
If manual, user enters date & time.
If imported from POS, uses Local date & time.
ClockOut datetime Yes Description: Clock-out
Example: 2007-03-29 20:15:00.000
If manual, user enters date & time.
If imported from POS, uses Local date & time.
POSEmployeeNumber nvarchar (20) Yes Description: POS Employee Number
Example: 549388
TotalHours decimal (19, 3) Yes Description: Total Hours
Example: 32.34

Index Name Unique Clustered Fields


PK_ST_Punches Yes Yes SiteNumber, SalesDate,
BOANETEmployeeNumber, ClockIn

154 ST_Punches Data Mart


ST_PurchaseOrderItems

Description: Purchase Order Information

Triggered by Export_ProcessSTPurchaseOrders.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on Purchase Orders LastModifiedTime.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
PurchaseOrderNumber int No Description: Purchase Order Number
(internal)
Example: 234
LineItemNumber int No Description: Line item Number (internal)
Example: 1
ItemNumber int No Description: Item Number (internal)
Example: 1000885
ItemID nvarchar (40) Yes Description: Item ID
Example: 456
ItemName nvarchar (250) Yes Description: Item Name
Example: Chicken
ItemUnitNumber int Yes Description: Item Unit Number (internal)
Example: 1000883

Data Mart ST_PurchaseOrderItems 155


Field Type Nulls? Comments
ItemUnitName nvarchar (100) Yes Description: Item Unit Name
Example: EA=250ml
Price decimal (19, 3) Yes Description: Price
Example: 2.34
QuantityOrdered decimal (19, 3) Yes Description: Quantity Ordered
Example: 2
StandardQuantityOrdered float Yes Description: Standard Quantity Ordered
Example: 2
ExtendedPrice decimal (19, 3) Yes Description: Extended Price
Example: 2.34
PurchaseType smallint Yes Description: Purchase Type
Example: 0
VendorItemID nvarchar (50) Yes Description: Vendor Item ID
Example:66468
ConsolidatedFromSiteNumber int Yes Description: ConsolidatedFromSiteNumber
Example: 2
GLAccountNumber nvarchar (100) Yes Description: GL Account Number
Example: BIO-32654
RawMaterialItemCatNum int Yes Description: RawMaterial Item Category
Number (internal)
Example: 1000020
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category
ID
Example: 1401
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: SHORTENING

Index Name Unique Clustered Fields


PK_ST_PurchaseOrderItems Yes Yes SiteNumber, PurchaseOrderNumber,
LineItemNumber

156 ST_PurchaseOrderItems Data Mart


ST_PurchaseOrderItems_RealTimeFeed *

Description: Purchase Order Items limited Information

Triggered by Export_STPurchaseOrderItems_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
PurchaseOrderNumber int No Description: Purchase Order Number
(internal)
Example: 234
LineItemNumber int No Description: Line item Number (internal)
Example: 1
VendorItemID nvarchar (50) Yes Description: Vendor Item ID
Example: 66468
QuantityOrdered decimal (19, 3) No Description: Quantity ordered expressed in
the item's purchase unit.
Example: 2
RawMaterialItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items
Example: 1000554
StandardQuantityOrdered float No Description: Quantity ordered expressed in
the item's standard unit.
Note: Items are defined in ST_Items
Example: 100.255
SuggestedOrderQuantity decimal (19, 3) Yes Description: Quantity suggested to order.
Example: 10
SuggestedOrderUnitNumber int Yes Description: NCR Back Office internal
number of the unit of measure reflected by
the suggested order quantity (internal).
Note: SuggestedOrderUnitNumber are
defined in ST_ItemUnitsOfMeasure.
Example: 123456

Data Mart ST_PurchaseOrderItems_RealTimeFeed * 157


Field Type Nulls? Comments
SplitCaseIndicator bit Yes Description: Identifies whether the order &
receive unit combination is designated as a
„Split Case‟ (Back Office Manager |Item
Maintenance| Order/Inventory|Purchase
Units)
1 = Order unit is a split case
0 = Order unit is not a split case
Example: 1

Index Name Unique Clustered Fields


PK_ST_PurchaseOrderItems_RealTimeFeed Yes Yes SiteNumber,
PurchaseOrderNumber,
LineItemNumber

* Table will not contain an index on the replicated database.

158 ST_PurchaseOrderItems_RealTimeFeed * Data Mart


ST_PurchaseOrders

Description: Purchase Order Information

Triggered by Export_ProcessSTPurchaseOrders.sql

Time Frame: This table will include each day individually for the selected time frame for this export
based on LastModifiedTime.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
PurchaseOrderNumber int No Description: Purchase Order
Number (internal)
Example: 234

Data Mart ST_PurchaseOrders 159


Field Type Nulls? Comments
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
ConnectedToPurchaseOrderNumber int Yes Description: Connected to
Purchase Prder Number
Example: 234
PurchaseOrderID nvarchar (100) Yes Description: Purchase Order ID
Example: 234
VendorNumber int Yes Description: Vendor Number
(internal)
Example:1000005
VendorName nvarchar (100) Yes Description: Vendor Name
Example: Mark‟s Bakery
VendorID nvarchar (50) Yes Description:Vendor ID
Example: 561
VendorAPCode nvarchar (255) Yes Description: Vendor AP Code
Example: 449
BusinessDate datetime No Description:Business Date
Example: 2007-07-17
DueDate datetime Yes Description: Due Date
Example: 2007-07-18
OrderTotal decimal (19, 3) Yes Description: Order Total
Example: 234.17
OpenOrder bit Yes Description:Open Order
0 = No
1 = Yes
Example: 0
RequisitionForSiteNumber int Yes Description: Requisition For Site
Number
Example: NULL
CommissaryVendorNumber int Yes Description: Commissary Vendor
Number (internal)
Example: 12
CommissaryVendorName nvarchar (100) Yes Description: Commissary Vendor
Name
Example: Mike‟s Depot
CommissaryVendorID nvarchar (50) Yes Description: Commissary Vendor
ID
Example: 517
Notes nvarchar (1000) Yes Description: Notes
Example: Closed Sunday
CreatedBy int Yes Description: Created By (internal)
Example: 4
CreatedTime datetime Yes Description: Created Date and
Time
Example: 2007-06-14 14:37:38.000
Uses UTC
CreatedByName nvarchar (100) Yes Description:Created by Name
Example: Mark Smith
LastModifiedBy int Yes Description: Last Modified By
(internal)
Example: 4

160 ST_PurchaseOrders Data Mart


Field Type Nulls? Comments
LastModifiedTime datetime Yes Description: Last Modified By Date
and Time
Example: 2007-06-20 14:37:38.000
Uses UTC
LastModifiedByName nvarchar (100) Yes Description: Last Modified By
Name
Example: Mark Smith
SentBy int Yes Description: Sent By (internal)
Example:4
SentTime datetime Yes Description: Sent Date and Time
Example: 2007-06-14 14:37:38.000
On client app, when Sent checkbox
gets updated manually (not
electronically), uses Locate date &
time.
Otherwise, uses UTC.
SentByName nvarchar (100) Yes Description: Sent By Name
Example: Mark Smith
ConfirmSent bit Yes Description: Order
Confirmation/Sent
0 = No
1 = Yes
Example: 1
Consolidated bit Yes Description: Consolidated Order
0 = No
1 = Yes
Example: 0

Index Name Unique Clustered Fields


PK_ST_PurchaseOrders Yes Yes BusinessDate, SiteNumber,
PurchaseOrderNumber

Data Mart ST_PurchaseOrders 161


ST_PurchaseOrders_RealTimeFeed *

Description: Purchase Order limited Information

Triggered by Export_STPurchaseOrders_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


CreatedTime datetime No Description: Created Date and Time
Example: 2007-06-14 14:37:38.000
Uses UTC
SiteNumber int No Description: Site Number (internal)
Example: 1456
SiteID nvarchar(25) No Description: Site ID aka Store ID
Example: 1311
PurchaseOrderNumber int No Description: Purchase Order Number
(internal)
Example: 234
VendorID nvarchar(50) No Description:Vendor ID
Example: 561
DueDate datetime Yes Description: Due Date
Example: 2012-07-18
SentBy Int Yes Description: Sent By User Number
(internal)
Example:4
BusinessDate datetime No Description: Business date of when the
purchase order was created.
Example: 2012-06-14
OrderTotal decimal(19, 3) No Description: Total amount of the entire
purchase order
Example: 84.000
162 ST_PurchaseOrders_RealTimeFeed * Data Mart
Field Type Nulls? Comments
OpenOrder bit No Description: A value that represents if the
order is open or has been close/converted
into an invoice:
0 = Not open (close/converted to an
invoice)
1 = Open
Example: 1
SentTime datetime Yes Description: The sent time (uses local date
& date) represents the time when the
„Send Order Now‟ button is manually
selected in Back Office
Switchboard|Inventory|Purchasing|
Orders| Purchase Orders which calls a
batch file (setup in Back Office
Switchboard|Inventory|Purchasing|
Vendors|Electronic Ordering tab), to
electronically send the order and a
confirmation message is displayed in the
UI confirming the order has been sent to
the vendor.
Example: 2007-06-14 14:37:38.000
Uses Site Local Time
ConfirmSent bit No Description: A value that represents a
confirmation message has been sent back
to the sender. Note: A confirmation
message is displayed in Back Office
Switchboard|Inventory|
Purchasing|Orders|Purchase
Orders|Purchasing – Purchase Orders UI.
0 = Confirmation of the purchase order
has NOT been sent electronically to the
vendor
1 = Confirmation of the purchase order
has been sent electronically to the
vendor
Example: 1
FromOrderByVendor bit Yes Description: A value that represents if the
purchase order was created from the Order
By Vendor UI or from Purchase Orders UI
in Back Office
Switchboard|Inventory|Purchasing|Orders
0 = Purchase Order created from Purchase
Orders
1 = Purchase Order created from
OrderByVendor
Example: 0
CreatedBy int Yes Description: User Number (internal) that
represents the user that created the
purchase order.
Example:1000780
LastModifiedBy int Yes Description: User Number (internal) that
represents last user that modified the
purchase order.
Example: 1022254
LastModifiedTime datetime No Description: The last date & time the
purchase order was modified.
Example: 2007-06-14 14:37:38.000
Uses UTC

Data Mart ST_PurchaseOrders_RealTimeFeed * 163


Field Type Nulls? Comments
PurchaseOrderID nvarchar(100) Yes Description: The value entered in the
Order ID field in NCR Back Office
Switchboard|Inventory |Purchasing
|Orders that identifies the purchase order.
Example: A99980

Index Name Unique Clustered Fields


PK_ST_PurchaseOrders_RealTimeFeed Yes Yes CreatedTime, SiteNumber,
PurchaseOrderNumber

* Table will not contain an index on the replicated database.

164 ST_PurchaseOrders_RealTimeFeed * Data Mart


ST_RawInfo

Description: Actual and Theoretical Raw Material data by SITE, by SUBPERIOD, by RAW MATERIAL
ITEM
Information about what‟s on hand with current cost

Triggered by Export_ProcessSTRawInfo.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Notes:
1. The following settings (based on the report parameter „Actual Use‟) are applied every time the
export is performed:
a. “Must have a Beginning Inventory” - Unchecked (set to False)
b. “Must have an Ending Inventory” - Unchecked (set to False)
c. “Use theoretical amount for ending inventory for an item that does not have a current
inventory” - Unchecked (set to False)
o This setting (c) can be changed to „checked‟, which will provide a theoretical value for
the following columns:
 CurrentOnHandCount
 CurrentRawMaterialItemCost
o To change this setting, please contact your NCR Back Office representative.

If you are attempting to reconcile the Data Mart values to a NCR Back Office report, please ensure
that the „Actual Use‟ parameter in the report has the same settings applied.

Data Mart ST_RawInfo 165


2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
ExportDate datetime Yes Description: Export Date
Example: 2007-04-23 14:37:38.000
Uses UTC
RawMaterialItemNum int No Description: Item Number (internal)
Example: 1000554
RawMaterialItemID nvarchar (40) Yes Description: Item ID
Example: 272
RawMaterialItemName nvarchar (250) Yes Description: Raw Material Item Name
Example: Dip, Buffalo Ranch
RawMaterialItemCatNum int Yes Description: Raw Material Item Category
Number (internal)
Example: 1000009
RawMaterialItemCatID nvarchar (25) Yes Description: Raw Material Item Category ID
Example: 4110
RawMaterialItemCatName nvarchar (100) Yes Description: Raw Material Item Category
Name
Example: Nuggets
CurrentOnHandCount float Yes Description: Current Theoretical On Hand
Count
Example: 422.4
CurrentRawMaterialItemCo money Yes Description: Current Raw Material Item Cost
st Example: 0.317
DateOfCurrentCost datetime Yes Description: Date of Current Cost
Example: 2007-03-15
StandardUnitName nvarchar (50) Yes Description: Standard Unit Name
Example: EA=250ml
StandardUnitNumber int Yes Description: Standard Unit Number
(internal)
Example: 1000058
ExportUnitToStandard float Yes Description: Export Unit to Standard Unit
Example:12.34
ExportUnitNumber int Yes Description: Export Unit Number (internal)
Example:1000136
ExportUnitName nvarchar (50) Yes Description: Export Unit Name
Example: CS=150 SL
Inactive bit Yes Description: If Raw Material Item is Inactive
0 = No (Active)
1 = Yes (Inactive)
Example: 1
InactiveDate datetime Yes Description: Date Raw Material Item
Became Inactive
Example: 2007-03-24

166 ST_RawInfo Data Mart


Index Name Unique Clustered Fields
PK_ST_RawInfo Yes Yes SiteNumber, SubPeriod, RawMaterialItemNum

Data Mart 167


ST_RecipeVersionBySite_FromView *

Description: This table provides a method to lookup which recipe version is used by a site, or site
group, for a specified menu or prep item.

Triggered by Export_STRecipeVersionBySite_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include all sites & groups. The site property, „Exclude from Data Mart‟
setting is not supported in this Data Mart table. Sites that have this setting checked in Back Office
Manager will be included in this table.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1456
ItemNumber int No Description: Item Number (internal) for the
recipe.

Note: Items are defined in ST_Items.

Example: 1001865
InheritedFromSiteNumber int No Description: This is the internal site number
for the site/site group that manages the
recipe version inherited by the site. This field
is used to determine the source of where the
recipe originates.

Note: When a recipe is created at a higher


level, all sites within the hierarchy group
inherit the recipe - unless a change is made
at a lower level.

Note: Sites are defined in


ST_SitesAndSiteGroups.

Example: 1045816

Index Name Unique Clustered Fields


PK_ST_RecipeVersionBySite Yes Yes SiteNumber, ItemNumber
_FromView

* Table will not contain an index on the replicated database.

168 ST_RecipeVersionBySite_FromView * Data Mart


ST_Register

Data Mart ST_Register 169


Description: Sales-related data based on mappings in data definitions by SITE by DATE.
This table holds the summary of the configuration data. This eliminates the need to go to the
configurable data tables.

Triggered by Export_ProcessSTRegister.sql

Time Frame: Sum by day. This table will include each day individually for the selected time frame for
this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
SalesDate datetime No Description: Sales Date
Example: 2007-03-15
TotalSales money Yes Description: Total Sales
Example: 5360.64
CustomerCount float Yes Description: Customer Count
Example: 619
Tax money Yes Description: Tax
Example: 695.14
LaborCost money Yes Description: Labor Cost
Example: 335.80
OTHours float Yes Description: Overtime Hours
Example: 0
CashOverShort money Yes Description: Cash Over Short
Example: 6.36
Sales1 money Yes BASED ON DATA DEFINITIONS
Sales2 money Yes BASED ON DATA DEFINITIONS
Sales3 money Yes BASED ON DATA DEFINITIONS
Sales4 money Yes BASED ON DATA DEFINITIONS
Sales5 money Yes BASED ON DATA DEFINITIONS
Sales6 money Yes BASED ON DATA DEFINITIONS
Sales7 money Yes BASED ON DATA DEFINITIONS
Sales8 money Yes BASED ON DATA DEFINITIONS
Sales9 money Yes BASED ON DATA DEFINITIONS
Sales10 money Yes BASED ON DATA DEFINITIONS
Sales11 money Yes BASED ON DATA DEFINITIONS
Sales12 money Yes BASED ON DATA DEFINITIONS
Sales13 money Yes BASED ON DATA DEFINITIONS
Sales14 money Yes BASED ON DATA DEFINITIONS
Sales15 money Yes BASED ON DATA DEFINITIONS
Sales16 money Yes BASED ON DATA DEFINITIONS
Sales17 money Yes BASED ON DATA DEFINITIONS
Sales18 money Yes BASED ON DATA DEFINITIONS
Sales19 money Yes BASED ON DATA DEFINITIONS

170 ST_Register Data Mart


Field Type Nulls? Comments
Sales20 money Yes BASED ON DATA DEFINITIONS
VoidSales money Yes Description: Dollar Amount of Voids
Example: 18.16
Discount1 money Yes BASED ON DATA DEFINITIONS
Discount2 money Yes BASED ON DATA DEFINITIONS
Discount3 money Yes BASED ON DATA DEFINITIONS
Discount4 money Yes BASED ON DATA DEFINITIONS
Discount5 money Yes BASED ON DATA DEFINITIONS
Discount6 money Yes BASED ON DATA DEFINITIONS
Discount7 money Yes BASED ON DATA DEFINITIONS
Discount8 money Yes BASED ON DATA DEFINITIONS
Discount9 money Yes BASED ON DATA DEFINITIONS
Discount10 money Yes BASED ON DATA DEFINITIONS
Discount11 money Yes BASED ON DATA DEFINITIONS
Discount12 money Yes BASED ON DATA DEFINITIONS
Discount13 money Yes BASED ON DATA DEFINITIONS
Discount14 money Yes BASED ON DATA DEFINITIONS
Discount15 money Yes BASED ON DATA DEFINITIONS
Discount16 money Yes BASED ON DATA DEFINITIONS
Discount17 money Yes BASED ON DATA DEFINITIONS
Discount18 money Yes BASED ON DATA DEFINITIONS
Discount19 money Yes BASED ON DATA DEFINITIONS
Discount20 money Yes BASED ON DATA DEFINITIONS
Discount21 money Yes BASED ON DATA DEFINITIONS
Discount22 money Yes BASED ON DATA DEFINITIONS
Discount23 money Yes BASED ON DATA DEFINITIONS
Discount24 money Yes BASED ON DATA DEFINITIONS
Discount25 money Yes BASED ON DATA DEFINITIONS
Discount26 money Yes BASED ON DATA DEFINITIONS
PaidOut1 float Yes BASED ON DATA DEFINITIONS
PaidOut2 float Yes BASED ON DATA DEFINITIONS
TIPS float Yes Description: Amount of Tips
Collected/Reported
Example: 118.64
TableTurns float Yes Description: Number of Tables
Example: 11
Deposit1 money Yes BASED ON DATA DEFINITIONS
Deposit2 money Yes BASED ON DATA DEFINITIONS
Deposit3 money Yes BASED ON DATA DEFINITIONS
Deposit4 money Yes BASED ON DATA DEFINITIONS
Deposit5 money Yes BASED ON DATA DEFINITIONS
Deposit6 money Yes BASED ON DATA DEFINITIONS
Deposit7 money Yes BASED ON DATA DEFINITIONS
Deposit8 money Yes BASED ON DATA DEFINITIONS
Deposit9 money Yes BASED ON DATA DEFINITIONS
Deposit10 money Yes BASED ON DATA DEFINITIONS
Deposit11 money Yes BASED ON DATA DEFINITIONS
Deposit12 money Yes BASED ON DATA DEFINITIONS
Deposit13 money Yes BASED ON DATA DEFINITIONS
Deposit14 money Yes BASED ON DATA DEFINITIONS
Deposit15 money Yes BASED ON DATA DEFINITIONS

Data Mart ST_Register 171


Field Type Nulls? Comments
Deposit16 money Yes BASED ON DATA DEFINITIONS
Deposit17 money Yes BASED ON DATA DEFINITIONS
Deposit18 money Yes BASED ON DATA DEFINITIONS
Deposit19 money Yes BASED ON DATA DEFINITIONS
Deposit20 money Yes BASED ON DATA DEFINITIONS
Change money Yes Description: Amount of Change Provided
Example: 0
ActualDeposit money Yes Description: Actual Deposit
Example: 4800.00
Labor1 float Yes BASED ON DATA DEFINITIONS
Labor2 float Yes BASED ON DATA DEFINITIONS
Labor3 float Yes BASED ON DATA DEFINITIONS
Labor4 float Yes BASED ON DATA DEFINITIONS
Labor5 float Yes BASED ON DATA DEFINITIONS
Labor6 float Yes BASED ON DATA DEFINITIONS
Labor7 float Yes BASED ON DATA DEFINITIONS
Labor8 float Yes BASED ON DATA DEFINITIONS
Labor9 float Yes BASED ON DATA DEFINITIONS
Labor10 float Yes BASED ON DATA DEFINITIONS
Other1 float Yes BASED ON DATA DEFINITIONS
Other2 float Yes BASED ON DATA DEFINITIONS
Other3 float Yes BASED ON DATA DEFINITIONS
Other4 float Yes BASED ON DATA DEFINITIONS
Other5 float Yes BASED ON DATA DEFINITIONS
Other6 float Yes BASED ON DATA DEFINITIONS
Other7 float Yes BASED ON DATA DEFINITIONS
Other8 float Yes BASED ON DATA DEFINITIONS
Other9 float Yes BASED ON DATA DEFINITIONS
Other10 float Yes BASED ON DATA DEFINITIONS
Tax1 float Yes BASED ON DATA DEFINITIONS
Tax2 float Yes BASED ON DATA DEFINITIONS
Tax3 float Yes BASED ON DATA DEFINITIONS
Tax4 float Yes BASED ON DATA DEFINITIONS
Tax5 float Yes BASED ON DATA DEFINITIONS
Tax6 float Yes BASED ON DATA DEFINITIONS
Tax7 float Yes BASED ON DATA DEFINITIONS
Tax8 float Yes BASED ON DATA DEFINITIONS
Tax9 float Yes BASED ON DATA DEFINITIONS
Tax10 float Yes BASED ON DATA DEFINITIONS
NRT float Yes Description: Non-Resetable Total
(Configurable)
Example: 100.00
NetSales decimal (19, 3) Yes Description: Net Sales Amount
Example: 3289.51

Index Name Unique Clustered Fields


PK_ST_Register Yes Yes SiteNumber, SalesDate, SubPeriod

172 ST_Register Data Mart


ST_RegisterByRevenueCenterDayPart

Data Mart ST_RegisterByRevenueCenterDayPart 173


Description: Sales-related data based on mappings in data definitions by SITE by DATE by REVENUE
CENTER by DAY PART.
This table holds the summary of the configuration data.

Triggered by Export_ProcessSTRevenueCenterDayPart.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls Comments


?
SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
SalesDate datetime No Description: Sales Date
Example: 2007-03-15
RevenueCenter nvarchar(100) No Description: Renvenue Center
Example: Bar
DayPart nvarchar(100) No Description: Day Part
Example: Lunch
Sales1 money Yes BASED ON DATA DEFINITIONS
Sales2 money Yes BASED ON DATA DEFINITIONS
Sales3 money Yes BASED ON DATA DEFINITIONS
Sales4 money Yes BASED ON DATA DEFINITIONS
Sales5 money Yes BASED ON DATA DEFINITIONS
Sales6 money Yes BASED ON DATA DEFINITIONS
Sales7 money Yes BASED ON DATA DEFINITIONS
Sales8 money Yes BASED ON DATA DEFINITIONS
Sales9 money Yes BASED ON DATA DEFINITIONS
Sales10 money Yes BASED ON DATA DEFINITIONS
Sales11 money Yes BASED ON DATA DEFINITIONS
Sales12 money Yes BASED ON DATA DEFINITIONS
Sales13 money Yes BASED ON DATA DEFINITIONS
Sales14 money Yes BASED ON DATA DEFINITIONS
Sales15 money Yes BASED ON DATA DEFINITIONS
Sales16 money Yes BASED ON DATA DEFINITIONS
Sales17 money Yes BASED ON DATA DEFINITIONS
Sales18 money Yes BASED ON DATA DEFINITIONS
Sales19 money Yes BASED ON DATA DEFINITIONS
Sales20 money Yes BASED ON DATA DEFINITIONS
VoidSales money Yes BASED ON DATA DEFINITIONS
Discount1 money Yes BASED ON DATA DEFINITIONS
Discount2 money Yes BASED ON DATA DEFINITIONS
Discount3 money Yes BASED ON DATA DEFINITIONS
Discount4 money Yes BASED ON DATA DEFINITIONS
Discount5 money Yes BASED ON DATA DEFINITIONS

174 ST_RegisterByRevenueCenterDayPart Data Mart


Field Type Nulls Comments
?
Discount6 money Yes BASED ON DATA DEFINITIONS
Discount7 money Yes BASED ON DATA DEFINITIONS
Discount8 money Yes BASED ON DATA DEFINITIONS
Discount9 money Yes BASED ON DATA DEFINITIONS
Discount10 money Yes BASED ON DATA DEFINITIONS
Discount11 money Yes BASED ON DATA DEFINITIONS
Discount12 money Yes BASED ON DATA DEFINITIONS
Discount13 money Yes BASED ON DATA DEFINITIONS
Discount14 money Yes BASED ON DATA DEFINITIONS
Discount15 money Yes BASED ON DATA DEFINITIONS
Discount16 money Yes BASED ON DATA DEFINITIONS
Discount17 money Yes BASED ON DATA DEFINITIONS
Discount18 money Yes BASED ON DATA DEFINITIONS
Discount19 money Yes BASED ON DATA DEFINITIONS
Discount20 money Yes BASED ON DATA DEFINITIONS
Discount21 money Yes BASED ON DATA DEFINITIONS
Discount22 money Yes BASED ON DATA DEFINITIONS
Discount23 money Yes BASED ON DATA DEFINITIONS
Discount24 money Yes BASED ON DATA DEFINITIONS
Discount25 money Yes BASED ON DATA DEFINITIONS
Discount26 money Yes BASED ON DATA DEFINITIONS
Deposit1 money Yes BASED ON DATA DEFINITIONS
Deposit2 money Yes BASED ON DATA DEFINITIONS
Deposit3 money Yes BASED ON DATA DEFINITIONS
Deposit4 money Yes BASED ON DATA DEFINITIONS
Deposit5 money Yes BASED ON DATA DEFINITIONS
Deposit6 money Yes BASED ON DATA DEFINITIONS
Deposit7 money Yes BASED ON DATA DEFINITIONS
Deposit8 money Yes BASED ON DATA DEFINITIONS
Deposit9 money Yes BASED ON DATA DEFINITIONS
Deposit10 money Yes BASED ON DATA DEFINITIONS
Deposit11 money Yes BASED ON DATA DEFINITIONS
Deposit12 money Yes BASED ON DATA DEFINITIONS
Deposit13 money Yes BASED ON DATA DEFINITIONS
Deposit14 money Yes BASED ON DATA DEFINITIONS
Deposit15 money Yes BASED ON DATA DEFINITIONS
Deposit16 money Yes BASED ON DATA DEFINITIONS
Deposit17 money Yes BASED ON DATA DEFINITIONS
Deposit18 money Yes BASED ON DATA DEFINITIONS
Deposit19 money Yes BASED ON DATA DEFINITIONS
Deposit20 money Yes BASED ON DATA DEFINITIONS
Change money Yes BASED ON DATA DEFINITIONS
ActualDeposit money Yes BASED ON DATA DEFINITIONS
Labor1 float Yes BASED ON DATA DEFINITIONS
Labor2 float Yes BASED ON DATA DEFINITIONS
Labor3 float Yes BASED ON DATA DEFINITIONS
Labor4 float Yes BASED ON DATA DEFINITIONS
Labor5 float Yes BASED ON DATA DEFINITIONS
Labor6 float Yes BASED ON DATA DEFINITIONS
Labor7 float Yes BASED ON DATA DEFINITIONS
Labor8 float Yes BASED ON DATA DEFINITIONS

Data Mart ST_RegisterByRevenueCenterDayPart 175


Field Type Nulls Comments
?
Labor9 float Yes BASED ON DATA DEFINITIONS
Labor10 float Yes BASED ON DATA DEFINITIONS
Other1 float Yes BASED ON DATA DEFINITIONS
Other2 float Yes BASED ON DATA DEFINITIONS
Other3 float Yes BASED ON DATA DEFINITIONS
Other4 float Yes BASED ON DATA DEFINITIONS
Other5 float Yes BASED ON DATA DEFINITIONS
Other6 float Yes BASED ON DATA DEFINITIONS
Other7 float Yes BASED ON DATA DEFINITIONS
Other8 float Yes BASED ON DATA DEFINITIONS
Other9 float Yes BASED ON DATA DEFINITIONS
Other10 float Yes BASED ON DATA DEFINITIONS
Tax1 float Yes BASED ON DATA DEFINITIONS
Tax2 float Yes BASED ON DATA DEFINITIONS
Tax3 float Yes BASED ON DATA DEFINITIONS
Tax4 float Yes BASED ON DATA DEFINITIONS
Tax5 float Yes BASED ON DATA DEFINITIONS
Tax6 float Yes BASED ON DATA DEFINITIONS
Tax7 float Yes BASED ON DATA DEFINITIONS
Tax8 float Yes BASED ON DATA DEFINITIONS
Tax9 float Yes BASED ON DATA DEFINITIONS
Tax10 float Yes BASED ON DATA DEFINITIONS
TotalSales money Yes BASED ON DATA DEFINITIONS
CustomerCount float Yes BASED ON DATA DEFINITIONS
Tax money Yes BASED ON DATA DEFINITIONS
LaborCost money Yes BASED ON DATA DEFINITIONS
OTHours float Yes BASED ON DATA DEFINITIONS
CashOverShort money Yes BASED ON DATA DEFINITIONS
PaidOut1 float Yes BASED ON DATA DEFINITIONS
PaidOut2 float Yes BASED ON DATA DEFINITIONS
TIPS float Yes BASED ON DATA DEFINITIONS
TableTurns float Yes BASED ON DATA DEFINITIONS
NRT float Yes BASED ON DATA DEFINITIONS
NetSales decimal (19, 3) Yes BASED ON DATA DEFINITIONS

Index Name Unique Clustered Fields


PK_ST_RegisterByRevenueCenterDayPart Yes Yes SiteNumber, SalesDate,
SubPeriod, RevenueCenter,
DayPart

Note: ST_RegisterByRevenueCenterDayPart is not supported by all POS


Systems. Please check with your account manager.

176 ST_RegisterByRevenueCenterDayPart Data Mart


ST_SafeCount *

Description: Safe Count detail and summary information which includes Safe Count Variances and
Cash Drops by business day by site by safe count number.

Triggered by Export_ProcessSTSafeCount.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business date associated with this
safe count.
Example: 2011-02-23

Data Mart ST_SafeCount * 177


Field Type Nulls? Comments
SafeCountNumber smallint No Description: Number associated with the Safe
Count for the business day. Each safe count
performed for the business day will increment
the number by one.
Example: 1000213
TotalSafeCount decimal (19,3) No Description: Total amount entered in Safe
Count including all currency and drawers.
Example: 5000.250
TotalSafeCountVariance decimal (19,3) No Description: Variance of Safe Count Amount –
dependent on Site Properties|General 2|Safe
Count|‟Use Perpetual Safe Count Balance‟
setting
Example: -10.25
NumberofDrawers int Yes Description: The number of drawers entered
by the manager.
Example: 3
StandardDrawerAmount decimal (19,3) No Description: The amount entered by the
manager for the standard drawer amount. This
amount is multiplied by the number of drawers
and included in the TotalSafeCount.
Example: 250.000
CashDrops decimal (19,3) No Description: Total amount of „Cash Drops‟
based on the data definition assigned in Back
Office Manager|General 2|Safe Count|Cash
Drops.
Example: 5000.250
SafeCount_1Dollar int Yes Description: The count of $1 bills entered by
the manager. This count is multiplied by „1.00‟
and included in the TotalSafeCount.
Example: 27
SafeCount_5Dollars int Yes Description: The count of $5 bills entered by
the manager. This count is multiplied by „5.00‟
and included in the TotalSafeCount.
Example: 15
SafeCount_10Dollars int Yes Description: The count of $10 bills entered by
the manager. This count is multiplied by
„10.00‟ and included in the TotalSafeCount.
Example: 34
SafeCount_20Dollars int Yes Description: The count of $20 bills entered by
the manager. This count is multiplied by
„20.00‟ and included in the TotalSafeCount.
Example: 43
SafeCount_50Dollars int Yes Description: The count of $50 bills entered by
the manager. This count is multiplied by
„50.00‟ and included in the TotalSafeCount.
Example: 4
SafeCount_100Dollars int Yes Description: The count of $100 bills entered by
the manager. This count is multiplied by
„100.00‟ and included in the TotalSafeCount.
Example: 7

178 ST_SafeCount * Data Mart


Field Type Nulls? Comments
SafeCount_1CentRoll int Yes Description: The count of rolls of pennies
entered by the manager. This count is
multiplied by „0.50‟ and included in the
TotalSafeCount.
Example: 3
SafeCount_5CentsRoll int Yes Description: The count of rolls of nickels
entered by the manager. This count is
multiplied by „2.00‟ and included in the
TotalSafeCount.
Example: 2
SafeCount_10CentsRoll int Yes Description: The count of rolls of dimes
entered by the manager. This count is
multiplied by „5.00‟ and included in the
TotalSafeCount.
Example: 4
SafeCount_25CentsRoll int Yes Description: The count of rolls of quarters
entered by the manager. This count is
multiplied by „10.00‟ and included in the
TotalSafeCount.
Example: 5
SafeCount_50CentsRoll int Yes Description: The count of rolls of half-dollars
entered by the manager. This count is
multiplied by „10.00‟ and included in the
TotalSafeCount.
Example: 4
SafeCount_1DollarCoinRoll int Yes Description: The count of rolls of dollar coins
entered by the manager. This count is
multiplied by „25.00‟ and included in the
TotalSafeCount.
Example: 1
Notes nvarchar(100) Yes Description: Notes entered by the manager
during the safe count.
Example: Safe count is $20 short due to
pending paid out.
PostedTime datetime No Description: Date & time that the safe count is
associated (business date)
Example: 2011-02-24 14:00:00.000
Uses UTC
CreatedBy int Yes Description: Internal number of user
associated with initial creation of the safe
count.
Example: 1022254
CreatedTime datetime No Description: The time this safe count was
initially created.
Example: 2011-02-24 14:32:15.000
Uses UTC
LastModifiedBy Int Yes Description: The internal number of the last
user that modified this safe count.
Example: 1022254
LastModifiedTime datetime No Description: The last time this safe count was
saved.
Example: 2011-02-24 14:32:15.000
Uses UTC

Data Mart ST_SafeCount * 179


Index Name Unique Clustered Fields
PK_ST_SafeCount Yes Yes BusinessDate, SiteNumber, SafeCountNumber

* Table will not contain an index on the replicated database.

180 ST_SafeCount * Data Mart


ST_SalesGuestsByInterval

Description: Sales Information and Guest Information by INTERVAL

Triggered by Export_ProcessSTSalesGuestsByInterval.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
SalesDate datetime No Description: Sales Date
Example: 2007-03-18
StartTime datetime No Description: Start Time
Example: 2007-03-18 14:30:00.000
Imported from POS which uses Local date & time.
EndTime datetime Yes Description: End Time
Example: 2007-03-18 14:45:00.000
Imported from POS which uses Local date & time.
TotalSales float Yes Description: Total Sales
Example: 140.51
TotalCustomers float Yes Description: Total Customers
Example: 22
ToGoSales float Yes Description: To Go Sales (dependent on POS)
Example: 62.37
ToGoCustomers float Yes Description: Total To Go Customers (dependent on
POS)
Example: 9
EatInSales float Yes Description: Eat In Sales (dependent on POS)
Example: 78.14

Data Mart ST_SalesGuestsByInterval 181


Field Type Nulls? Comments
EatInCustomers float Yes Description: Total Eat In Customers (dependent on
POS)
Example: 13

Index Name Unique Clustered Fields


PK_ST_SalesGuestsByInterval Yes Yes SiteNumber, SalesDate, StartTime

182 ST_SalesGuestsByInterval Data Mart


ST_SalesMix

Description: Contains daily sales mix data. Sales Mix by SITE, by DATE, by ITEM.

Triggered by Export_ProcessSTSalesMix.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
ItemNumber int No Description: Item Number (internal)
Example: 1000554
MenuItemID nvarchar (40) No Description: MenuItem ID
Example: 639
MenuItemName nvarchar (250) Yes Description: Menu Item Name
Example: GRILLED RGC TWST
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
SalesMixDate datetime No Description: Sales Mix Date
Example: 2007-04-26
TotalNumberSold float Yes Description: Sum of Total Number Sold
Example: 1
SellingPrice money No Description: Selling Price
Example: 5.99
NetSales float Yes Description: Net Sales
Example: 5.99

Index Name Unique Clustered Fields


PK_ST_SalesMix Yes Yes SiteNumber, SalesMixDate, ItemNumber,
SubPeriod, SellingPrice

Data Mart ST_SalesMix 183


ST_SalesMixByRawMaterial

Description: Sales Mix Broken into Raw Materials

Triggered by Export_ProcessSTSalesMixByRawMaterial.sql

Time Frame: This table provides food cost values for each sub-period (based on the defined fiscal
calendar week) within the selected export timeframe. The information for each day within a sub-
period is summed for this export. Costing values are based on the beginning & end dates of the sub-
period. These values can be compared with NCR Back Office food cost reports, only when the report is
generated for the SAME sub-period as the table content.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
StartSubPeriod int No Description: Starting Sub Period Number
(internal)
Example: 65
EndSubPeriod int No Description: Ending Sub Period Number
(internal)
Example: 65
StartingDate datetime No Description: Starting Date
Example: 2007-06-10
EndingDate datetime No Description: Ending Date
Example: 2007-06-17
RawMaterialItemNum int No Description: Raw Material Item Number
(internal)
Example: 1000043

184 ST_SalesMixByRawMaterial Data Mart


Field Type Nulls? Comments
RawMaterialItemID nvarchar (40) Yes Description: Item ID
Example: 272
RawMaterialItemUnitNumber int Yes Description: Item Unit Number (internal)
Example: 6
RawMaterialItemUnitName nvarchar (50) Yes Description: Itme Unit Name
Example: EA
Quantity decimal (28, 3) Yes Description: Theoretical Quantity
Example: 82.29
QuantityUnrounded float Yes Description: Theoretical Quantity Unrounded
Example: 82.29349
Value decimal (28, 3) Yes Description: Theoretical Value
Example: 99.58
ValueUnrounded float Yes Description: Theoretical Value Unrounded
Example: 99.57513
UnitCost decimal (19, 3) Yes Description: Standard Unit Cost
Example: 0.35
UnitCostUnrounded float Yes Description: Standard Unit Cost Unrounded
Example: 0.354166657

Index Name Unique Clustered Fields


PK_ST_SalesMixByRawMaterial Yes Yes SiteNumber, StartingDate, EndingDate,
RawMaterialItemNum

Data Mart ST_SalesMixByRawMaterial 185


ST_Schedule

Description: Summary Data of Employee Schedule Information


Scheduled Clock-in/Clock-out by SITE by DATE by EMPLOYEE by SHIFT

Triggered by Export_ProcessSTSchedule.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobID nvarchar (25) Yes Description: Job ID
Example: 2009
JobName nvarchar (100) No Description: Job Name
Example: Food Service Team Member
SchdDate datetime No Description: Schedule Date
Example: 2007-03-26

186 ST_Schedule Data Mart


Field Type Nulls? Comments
ClockIn int No Description: Clock-In – stored in minutes.
Example: 600
Which means 600/60min = 10.00 in military
time; which is 10:00 am.
ClockOut int Yes Description: Clock-Out – stored in minutes.
Example: 900
Which means 900/60min = 15.00 in military
time; which is 3:00 pm.
Hours decimal (19, 3) Yes Description: Total Labor Hours
Example: 4.25
StationNumber int Yes Description: The StationNumber is the NCR
Back Office internal ID for the employee's
station assignment. The StationNumber can be
cross-referenced to the corresponding
TaskOrStationNumber defined in
ST_TasksAndStations to identify the related
TaskOrStationID and TaskOrStationName. If a
station is not assigned to an employee shift,
the corresponding StationNumber field in the
Data Mart table ST_Schedule will be null or
zero.
Example: 122000718

Index Name Unique Clustered Fields


PK_ST_Schedule Yes Yes SiteNumber, SchdDate,
BOANETEmployeeNumber, ClockIn

Data Mart ST_Schedule 187


ST_ScheduleHours

Description: Summarized Schedule Data - Scheduled Payroll by SITE, by DATE, by EMPLOYEE

Triggered by Export_ProcessSTScheduleHours.sql

Time Frame: Sum by Day. This table will include each day individually for the selected time frame for
this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked
from Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobName nvarchar (100) No Description: Job Name
Example: Restaurant General Manager
ScheduleDate datetime No Description: Schedule Date
Example: 2007-05-14
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
RegularHours decimal (19, 3) Yes Description: Regular Hours
Example: 6
OverTimeHours decimal (19, 3) Yes Description: Overtime Hours
Example: 0
DoubleOTHours decimal (19, 3) Yes Description: Double Overtime Hours
Example: 0
Rate decimal (19, 3) Yes Description: Rate
Example: 8.35

188 ST_ScheduleHours Data Mart


Index Name Unique Clustered Fields
PK_ST_ScheduleHours Yes Yes SiteNumber, ScheduleDate,
BOANETEmployeeNumber, JobNumber

Data Mart ST_ScheduleHours 189


ST_ScheduleIntervals

Description: Summarized Schedule Data; Forecast Intervals


Uses Forecasted Labor by Intervals to get Required Staffing

Triggered by Export_ProcessSTScheduleIntervals.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
ScheduleDate datetime No Description: Schedule Date
Example: 2007-03-26
Interval smallint No Description: Interval
Example: 4
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobID nvarchar (25) Yes Description: Job ID
Example: 2009
JobName nvarchar (100) Yes Description: Job Name
Example: Restaurant General Manager
RequiredStaff float Yes Description: Required Staff
Example: 0
ScheduledStaff float Yes Description: Scheduled Staff
Example: 1
RecommendedStaffCount float Yes Description: Recommended Staff Amount
Example: 1

Index Name Unique Clustered Fields


PK_ST_ScheduleIntervals Yes Yes SiteNumber, ScheduleDate, Interval,
JobNumber

190 ST_ScheduleIntervals Data Mart


ST_SchedulePayrollDay

Description: Scheduled Payroll by SITE, by DAY by EMPLOYEE

Triggered by Export_ProcessSTSchedulePayrollDay.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
JobNumber int No Description: Current Job Number (internal)
Example: 1000626
JobID nvarchar (25) Yes Description: Job ID
Example: 2009
JobName nvarchar (100) Yes Description: Job Name
Example: Restaurant General Manager
PayTypeID int No Description: Pay Type ID
Note: Anything other than 0, -1, -2 is a non-
worked hour.
0 = Regular
-1 = Overtime
-2 = Double Overtime
Example: 0

Data Mart ST_SchedulePayrollDay 191


Field Type Nulls? Comments
PayTypeName nvarchar (100) Yes Description: Pay Type Name
Note: This will only identify non-worked hour
names
Example: Shift Diff. ($)
BusinessDate datetime No Description: Business Date
Example: 2007-03-27
Dollars decimal (19, 3) Yes Description: Dollars
Example: 68.25
Hours decimal (19, 3) Yes Description: Total Labor Hours
Example: 7
Rate decimal (19, 3) Yes Description: Rate
Example: 9.75

Index Name Unique Clustered Fields


PK_ST_SchedulePayrollDay Yes Yes SiteNumber, BusinessDate,
BOANETEmployeeNumber, JobNumber,
PayTypeID

192 ST_SchedulePayrollDay Data Mart


ST_ScheduleRecommendedByDayLaborMatrices *

Description: Daily Matrices used to determine the recommended staffing hours for a schedule. If the
recommended labor is updated multiple times, matrix information will be written each time the
recommended labor is updated with date & time of update. Records will not be over-written; new
records are appended.

Triggered by Export_STScheduleRecommendedByDayLaborMatrices.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal).
Example: 1456
Timestamp datetime No Description: Date & time that the
recommended staffing was generated
in UTC.
Example: 2011-04-05 00:23:15.980
Uses UTC
RecommendedStaffingMethod int No Description: Recommended labor can
be initiated through a forecast or Back
Office Manager\Time Clock Utilites.
This indicated which method was used.
1 = Forecast
2 = Time Clock Utilities
3 = Automated Labor Refresh
Example: 2
ScheduleDate datetime No Description: Date on the Employee
Schedule.
Example: 2011-03-29

Data Mart ST_ScheduleRecommendedByDayLaborMatrices * 193


Field Type Nulls? Comments
ScheduleDayofWeek tinyint No Description: The day of week for the
schedule date.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 3
RestConfigNumber int No Description: Recommended Staffing by
Day Number (internal). Internal
number: this is one of the fields used
to provide uniqueness to matrices
(required for view replication).
Example: 1000327
RecommendedStaffingByDayNa nvarchar(100) No Description: The Recommended
me Staffing by Day Name as defined in
Back Office Manager\Labor
\Recommended Staffing
\Recommended by Day.
Example: Monday Drive Thru
MatrixNumber int No Description: Matrix Number (internal).
Example: 1095112
MatrixName nvarchar(100) No Description: The name of the daily
staffing matrix as defined in Back
Office Manager\ Labor\Matrix
Maintenance.
Example: Monday Lunch
MatrixType int No Description: The type of daily staffing
matrix as defined in Back Office
Manager\ Labor\Matrix Maintenance.
1 = Non Service Staffing
4 = Daily Base Staffing
5 = Daily Added Staffing
7 = Peak Shift Staffing
Note: Only matrices assigned to
“Recommended by Day” staffing will be
included.
Example: 7
StartTime datetime No Description: For Peak Shift matrix
type, this will be the Schedule Date
Start Time as defined in Back Office
Manager\ Labor\ Recommended
Staffing\Recommended by Day.
For all other matrix types, this will be
the Schedule Date and start of
business time.
Example: 2011-03-29 04:00:00.000
Example: 2011-03-29 11:30:00.000
(peak)

194 ST_ScheduleRecommendedByDayLaborMatrices * Data Mart


Field Type Nulls? Comments
EndTime datetime No Description: For Peak Shift matrix
type, this will be the Schedule Date
End Time as defined in Back Office
Manager\ Labor\ Recommended
Staffing\Recommended by Day.
For all other matrix types, this will be
the Schedule Date and end of business
time.
Example: 2011-03-30 04:00:00.000
Example: 2011-03-29 12:30:00.000
(peak)
DailyRecommendedStaffingHours decimal (19, 3) Yes Description: The number of
recommended staffing hours for the
day based on the matrix. For Peak
Shift matrix type, this value will be the
hours used in the interval.
Example: 85.5
Example: 7 (for Peak Shift matrix type)

Index Name Unique Clustered Fields


PK_ST_ScheduleRecommendedBy Yes Yes Timestamp, SiteNumber, ScheduleDate,
DayLaborMatrices RestConfigNumber, MatrixType,
MatrixNumber, StartTime

* Table will not contain an index on the replicated database.

Data Mart ST_ScheduleRecommendedByDayLaborMatrices * 195


ST_ServerCheckout

196 ST_ServerCheckout Data Mart


Description: All Configurable Data
Looks at Configurable Cashier Checkout Data Decimal Tables
FIFO comes from all stores level for Food Cost, Cost of Goods and Item Use Variance

Triggered by Export_ProcessSTCashierCheckout.sql
Data gathered by: Export_STCashierCheckout.sql

Time Frame: Sum by day. This table will include each day individually for the selected time frame for
this export.

Notes:
1. SubPeriod field shows which subperiod the day belongs to.
2. A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BOANETEmployeeNumber int No Description: Employee Number (internal)
Example: 1002115
EmployeeNumber nvarchar (25) No Description: Employee ID
Example: 504931
Shift smallint No Description: Shift
Example: 1
SalesDate datetime No Description: Sales Date
Example: 2007-03-27
Register smallint No Description: Register Used
Example: 2
SubPeriod int Yes Description: Sub Period Number (internal)
Example: 65
Sales1 money Yes CONFIGURABLE DATA
Sales2 money Yes CONFIGURABLE DATA
Sales3 money Yes CONFIGURABLE DATA
Sales4 money Yes CONFIGURABLE DATA
Sales5 money Yes CONFIGURABLE DATA
Sales6 money Yes CONFIGURABLE DATA
Sales7 money Yes CONFIGURABLE DATA
Sales8 money Yes CONFIGURABLE DATA
Sales9 money Yes CONFIGURABLE DATA
Sales10 money Yes CONFIGURABLE DATA
Sales11 money Yes CONFIGURABLE DATA
Sales12 money Yes CONFIGURABLE DATA
Sales13 money Yes CONFIGURABLE DATA
Sales14 money Yes CONFIGURABLE DATA
Sales15 money Yes CONFIGURABLE DATA
Sales16 money Yes CONFIGURABLE DATA
Sales17 money Yes CONFIGURABLE DATA
Sales18 money Yes CONFIGURABLE DATA
Sales19 money Yes CONFIGURABLE DATA
Sales20 money Yes CONFIGURABLE DATA
Discount1 money Yes CONFIGURABLE DATA
Discount2 money Yes CONFIGURABLE DATA

Data Mart ST_ServerCheckout 197


Field Type Nulls? Comments
Discount3 money Yes CONFIGURABLE DATA
Discount4 money Yes CONFIGURABLE DATA
Discount5 money Yes CONFIGURABLE DATA
Discount6 money Yes CONFIGURABLE DATA
Discount7 money Yes CONFIGURABLE DATA
Discount8 money Yes CONFIGURABLE DATA
Discount9 money Yes CONFIGURABLE DATA
Discount10 money Yes CONFIGURABLE DATA
Discount11 money Yes CONFIGURABLE DATA
Discount12 money Yes CONFIGURABLE DATA
Discount13 money Yes CONFIGURABLE DATA
Discount14 money Yes CONFIGURABLE DATA
Discount15 money Yes CONFIGURABLE DATA
Discount16 money Yes CONFIGURABLE DATA
Discount17 money Yes CONFIGURABLE DATA
Discount18 money Yes CONFIGURABLE DATA
Discount19 money Yes CONFIGURABLE DATA
Discount20 money Yes CONFIGURABLE DATA
Discount21 money Yes CONFIGURABLE DATA
Discount22 money Yes CONFIGURABLE DATA
Discount23 money Yes CONFIGURABLE DATA
Discount24 money Yes CONFIGURABLE DATA
Discount25 money Yes CONFIGURABLE DATA
Discount26 money Yes CONFIGURABLE DATA
Deposit1 money Yes CONFIGURABLE DATA
Deposit2 money Yes CONFIGURABLE DATA
Deposit3 money Yes CONFIGURABLE DATA
Deposit4 money Yes CONFIGURABLE DATA
Deposit5 money Yes CONFIGURABLE DATA
Deposit6 money Yes CONFIGURABLE DATA
Deposit7 money Yes CONFIGURABLE DATA
Deposit8 money Yes CONFIGURABLE DATA
Deposit9 money Yes CONFIGURABLE DATA
Deposit10 money Yes CONFIGURABLE DATA
Deposit11 money Yes CONFIGURABLE DATA
Deposit12 money Yes CONFIGURABLE DATA
Deposit13 money Yes CONFIGURABLE DATA
Deposit14 money Yes CONFIGURABLE DATA
Deposit15 money Yes CONFIGURABLE DATA
Deposit16 money Yes CONFIGURABLE DATA
Deposit17 money Yes CONFIGURABLE DATA
Deposit18 money Yes CONFIGURABLE DATA
Deposit19 money Yes CONFIGURABLE DATA
Deposit20 money Yes CONFIGURABLE DATA
Tax money Yes CONFIGURABLE DATA
Tax1 money Yes CONFIGURABLE DATA
Tax2 money Yes CONFIGURABLE DATA
Tax3 money Yes CONFIGURABLE DATA
Tax4 money Yes CONFIGURABLE DATA
Tax5 money Yes CONFIGURABLE DATA
Tax6 money Yes CONFIGURABLE DATA

198 ST_ServerCheckout Data Mart


Field Type Nulls? Comments
Tax7 money Yes CONFIGURABLE DATA
Tax8 money Yes CONFIGURABLE DATA
Tax9 money Yes CONFIGURABLE DATA
Tax10 money Yes CONFIGURABLE DATA
Tips1 money Yes CONFIGURABLE DATA
Tips2 money Yes CONFIGURABLE DATA
Tips3 money Yes CONFIGURABLE DATA
Tips4 money Yes CONFIGURABLE DATA
Tips5 money Yes CONFIGURABLE DATA
Tips6 money Yes CONFIGURABLE DATA
Tips7 money Yes CONFIGURABLE DATA
Tips8 money Yes CONFIGURABLE DATA
Tips9 money Yes CONFIGURABLE DATA
Tips10 money Yes CONFIGURABLE DATA
Tips11 money Yes CONFIGURABLE DATA
Tips12 money Yes CONFIGURABLE DATA
Tips13 money Yes CONFIGURABLE DATA
Tips14 money Yes CONFIGURABLE DATA
Tips15 money Yes CONFIGURABLE DATA
Transaction1 float Yes CONFIGURABLE DATA
Transaction2 float Yes CONFIGURABLE DATA
Transaction3 float Yes CONFIGURABLE DATA
Transaction4 float Yes CONFIGURABLE DATA
Transaction5 float Yes CONFIGURABLE DATA
Transaction6 float Yes CONFIGURABLE DATA
Transaction7 float Yes CONFIGURABLE DATA
Transaction8 float Yes CONFIGURABLE DATA
Transaction9 float Yes CONFIGURABLE DATA
Transaction10 float Yes CONFIGURABLE DATA
Transaction11 float Yes CONFIGURABLE DATA
Transaction12 float Yes CONFIGURABLE DATA
Transaction13 float Yes CONFIGURABLE DATA
Transaction14 float Yes CONFIGURABLE DATA
Transaction15 float Yes CONFIGURABLE DATA
PaidOut1 money Yes CONFIGURABLE DATA
PaidOut2 money Yes CONFIGURABLE DATA
VoidSales money Yes CONFIGURABLE DATA
CustomerCount float Yes CONFIGURABLE DATA
CashOverShort money Yes CONFIGURABLE DATA
Currency1 float Yes CONFIGURABLE DATA
Currency5 float Yes CONFIGURABLE DATA
Currency10 float Yes CONFIGURABLE DATA
Currency20 float Yes CONFIGURABLE DATA
Currency50 float Yes CONFIGURABLE DATA
Currency100 float Yes CONFIGURABLE DATA
Coin1 float Yes CONFIGURABLE DATA
Coin5 float Yes CONFIGURABLE DATA
Coin10 float Yes CONFIGURABLE DATA
Coin25 float Yes CONFIGURABLE DATA
Coin50 float Yes CONFIGURABLE DATA
Coin100 float Yes CONFIGURABLE DATA

Data Mart ST_ServerCheckout 199


Field Type Nulls? Comments
CoinRoll1 float Yes CONFIGURABLE DATA
CoinRoll5 float Yes CONFIGURABLE DATA
CoinRoll10 float Yes CONFIGURABLE DATA
CoinRoll25 float Yes CONFIGURABLE DATA
CoinRoll50 float Yes CONFIGURABLE DATA
CoinRoll100 float Yes CONFIGURABLE DATA
TotalSales money Yes CONFIGURABLE DATA
TableTurns float Yes CONFIGURABLE DATA
Change money Yes CONFIGURABLE DATA
ActualDeposits money Yes CONFIGURABLE DATA
Tips money Yes CONFIGURABLE DATA
LaborCost money Yes CONFIGURABLE DATA
OTHours float Yes CONFIGURABLE DATA
Labor1 float Yes CONFIGURABLE DATA
Labor2 float Yes CONFIGURABLE DATA
Labor3 float Yes CONFIGURABLE DATA
Labor4 float Yes CONFIGURABLE DATA
Labor5 float Yes CONFIGURABLE DATA
Labor6 float Yes CONFIGURABLE DATA
Labor7 float Yes CONFIGURABLE DATA
Labor8 float Yes CONFIGURABLE DATA
Labor9 float Yes CONFIGURABLE DATA
Labor10 float Yes CONFIGURABLE DATA
Other1 float Yes CONFIGURABLE DATA
Other2 float Yes CONFIGURABLE DATA
Other3 float Yes CONFIGURABLE DATA
Other4 float Yes CONFIGURABLE DATA
Other5 float Yes CONFIGURABLE DATA
Other6 float Yes CONFIGURABLE DATA
Other7 float Yes CONFIGURABLE DATA
Other8 float Yes CONFIGURABLE DATA
Other9 float Yes CONFIGURABLE DATA
Other10 float Yes CONFIGURABLE DATA

Index Name Unique Clustered Fields


PK_ST_ServerCheckout Yes Yes SiteNumber, SalesDate,
BOANETEmployeeNumber, Shift, Register

200 ST_ServerCheckout Data Mart


ST_SiteAndSiteGroupMemberships_RealTimeFeed *

Description: This table contains all site & site group memberships. Each site or group will display all
sites & groups that it is a member of and the distance in the hierarchy from the site or group. This
includes all site and group types as defined in the SiteType field in the ST_SitesAndSiteGroups table.

Triggered by Export_STSiteAndSiteGroupMemberships_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: This table will include all sites & groups. The site property, „Exclude from Data Mart‟ setting in
Back Office Manager|Site Properties|General 1 tab, is not supported in this Data Mart export. Sites
that have this setting checked in Back Office Manager will be included in this table.

Field Type Nulls? Comments


SiteOrGroupNumber int Yes Description: Site Number (internal) of each
site or group.
Note: Sites & Groups are defined in
ST_SitesAndSiteGroups.
Example: 122000029
MemberOfSiteOrGroupNumber int Yes Description: Site or Site Group Number
(internal) that the SiteOrGroupNumber is a
member of. This can include all site types
such as sites, settings groups & report
groups.
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 5 or 122000029
MemberDistance int No Description: The distance from the
„SiteOrGroupNumber‟ to the
„MemberOfSiteOrGroupNumber‟ within the
Back Office Manager hierarchy. All sites are
linked to themselves with a distance of 0.
ie: If the hierarchical path to „Site #1‟ is: All
Stores\Burger Joint\Dallas\Site #1
Distance from „Site #1‟ is:
To „All Stores‟ = 3
To „Burger Joint‟ = 2
To „Dallas‟ = 1
To „Site #1‟ = 0
Example: 0

Index Name Unique Clustered Fields


PK_ST_SiteAndSiteGroupMemb Yes Yes SiteOrGroupNumber,
erships_RealTimeFeed MemberOfSiteOrGroupNumber

* Table will not contain an index on the replicated database.

Data Mart ST_SiteAndSiteGroupMemberships_RealTimeFeed * 201


ST_SiteEmployeeRateChangeAcknowledgments_FromView *

Description: This table provides employee rate change and tip credit change information by employee
by site by job. These values can be used to determine when employee rates and tip credit amounts
have changed. In addition, this table includes employee acknowledgement timestamp and status
information.

This information can also be viewed on the „Employee Rate & Tip Credit Acknowledgments‟ report
from the Back Office Labor Switchboard (Back Office Switchboard|Labor|Reports).

Triggered by Export_STSiteEmployeeRateChangeAcknowledgemenets_FromView.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site number (internal)
Note: Sites are defined in
„ST_SitesAndSiteGroups.SiteNumber‟
Example: 122000031
InternalEmployeeNumber int No Description: Employee number (internal)
Note: Employees are defined in
„ST_Employees. EmployeeNumber‟.
Example: 1018
InternalJobNumber int No Description: Job number (internal)
Note: Job numbers are defined in
„ST_Jobs.JobNumber‟.
Example: 1000626
LastPayRate decimal(19,3) Yes Description: Last pay rate
Note: „LastPayRate‟ will be captured when a
rate change has been applied to a job code
(Back Office Manager|Labor|Employee
Maintenance|Jobcodes).
Example: 7.50
NewPayRate decimal(19,3) Yes Description: New pay rate
Note: „NewPayRate‟ will be captured when a
rate change has been applied to a job code
(Back Office Manager|Labor|Employee
Maintenance|Jobcodes).
Example: 7.75
LastTipCreditAmount decimal(19,3) Yes Description: Last tip credit amount

202 ST_SiteEmployeeRateChangeAcknowledgments_FromView * Data Mart


Field Type Nulls? Comments
Note: Tip credits will adjust when a „Job
Rate‟ change or minimum wage change is
applied.
Example: 2.25
NewTipCreditAmount decimal(19,3) Yes Description: New tip credit amount
Note: Tip credits will adjust when a „Job
Rate‟ change or minimum wage change is
applied.
Example: 3.50
ExportTime datetime No Description: Date and Time of when the
„Aloha POS‟ export „Employees – POS‟ was
performed.
Example: 2013-04-02 14:37:38.000
Uses Site Local Time
AcknowledgmentStatus tinyint No Description: Status of employee
acknowledgment
0 = Pending Acknowledgment
1 = Acknowledged
2 = Replaced - A „Replaced‟ status is applied
when a new transaction record overrides
the existing transaction record in the
export file to the Aloha POS.
3 = Removed – A „Removed‟ transaction
status is applied when a transaction
record has been removed from the
existing transaction record in the export
file to the Aloha POS. This may occur
when:
A jobcode is made inactive or is deleted
When an employee has been:
Terminated
Transferred
Borrowed/Un-borrowed
Example: 1
AcknowledgmentTime datetime Yes Description: Date and time that employee
acknowledged a job rate change or tip credit
change at the Aloha POS.
Example: 2013-04-02 14:37:38.000
Uses Site Local Time
TransactionID int No Description: Transaction ID (unique).
This is an Identity field type.
Example: 12344

Index Name Unique Clustered Fields


PK_ST_SiteEmployeeRateChange Yes Yes TransactionID
Acknowledgments_FromView

* Table will not contain an index on the replicated database.

Data Mart ST_SiteEmployeeRateChangeAcknowledgments_FromView * 203


ST_SiteInventoryListMembers_RealTimeFeed *

Description: This table provides Inventory Lists showing each Raw or Prep item assigned to the list.
Note: There will not be a complete inventory list for each site. A record is only created with the
associated SiteNumber where an item was added to the list, or if Exclude = 1, where the item was
removed from an existing list.

Triggered by Export_STSiteInventoryListMembers_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
InventoryListNumber int No Description: Inventory List number (internal)
Note: Inventory Lists are defined in
ST_InventoryLists_RealTimeFeed.
Example: 124123
ItemNumber int No Description: Item Number (internal)
Note: Items are defined in ST_Items.
Example: 1001865
Exclude bit No Description: Item Excluded – 0 = item was
added to list at this site; 1=item was
removed from list at this site
0 = No
1 = Yes
Example: 0

Index Name Unique Clustered Fields


PK_ST_SiteInventoryList Yes Yes SiteNumber, InventoryListNumber,
Members_RealTimeFeed ItemNumber

* Table will not contain an index on the replicated database.

204 ST_SiteInventoryListMembers_RealTimeFeed * Data Mart


ST_SitePayroll

Description: Payroll Calendar Information

Triggered by Export_ProcessSTSitePayroll.sql

Time Frame: This table will export each subperiod (based on the defined fiscal calendar week)
associated with the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
StartDate datetime Yes Description: Start Date
Example: 2007-06-25
EndDate datetime Yes Description: End Date
Example: 2007-07-01
Year smallint Yes Description: Year
Example: 2007
Period smallint Yes Description: Period
Example: 65
Week smallint Yes Description: Week
Example: 1
BusinessCalendarNumber int Yes Description: Business Calendar Number
(internal)
Example: 1000609
BusinessCalendarName nvarchar (100) Yes Description: Business Calendar Name
Example: Payroll – Radiant Systems

Index Name Unique Clustered Fields


PK_ST_SitePayroll Yes Yes SiteNumber, SubPeriod

Data Mart ST_SitePayroll 205


ST_Sites

Description: Site Information

Triggered by Export_ProcessSTSites.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

206 ST_Sites Data Mart


Field Type Nulls? Comments
SiteNumber int No Description: Site Number (internal)
Example: 1456
SiteName nvarchar (100) Yes Description: Site Name
Example: KFC California – 1311
StoreID nvarchar (25) Yes Description: Store ID
Example: 1311
ContactName nvarchar (100) Yes Description: Contact Name
Example: Bob Smith
Address1 nvarchar (100) Yes Description: Address 1
Example: 123 Main Street
Address2 nvarchar (100) Yes Description: Address 2
Example: Suite 600
City nvarchar (100) Yes Description: City
Example: San Francisco
StateProvince nvarchar (100) Yes Description: State
Example: California
PostalCode nvarchar (100) Yes Description: Postal Code
Example: 45710
Phone nvarchar (100) Yes Description: Phone
Example: 5555551212
AltPhone nvarchar (100) Yes Description: Alternative Phone
(Mobile/Fax)
Example: 5555551212
Email nvarchar (100) Yes Description: Email Address
Example: MySiteEmail@NCR.com
OpenDate datetime Yes Description: Store Open Date
Example: 2005-07-01
ReportingCloseDate datetime Yes Description: Store Close Date
Example: 2007-07-01
CustomDate datetime Yes Description: Custom Date
Example: 2007-07-01
ShippingCode nvarchar (100) Yes Description: Shipping Code
Example: 123 Main Street, Marysville, OH
LegalUnit nvarchar (100) Yes Description: Legal Unit
Example: Meat Packers
BusinessUnit nvarchar (100) Yes Description: Business Unit
Example: Purchasing
CompanyName nvarchar (100) Yes Description: Company Name
Example: Corporate Store
Custom_Description_1 nvarchar(25) Yes Description: User Defined Description.
Example: Store Colors
Custom_Value_1 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_2 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_2 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_3 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_3 nvarchar(50) Yes Description: User Defined Value
Example: Red and White

Data Mart ST_Sites 207


Field Type Nulls? Comments
Custom_Description_4 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_4 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_5 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_5 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_6 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_6 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_7 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_7 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_8 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_8 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_9 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_9 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_10 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_10 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_11 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_11 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_12 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_12 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_13 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_13 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_14 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_14 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_15 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_15 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_16 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_16 nvarchar(50) Yes Description: User Defined Value
Example: Red and White

208 ST_Sites Data Mart


Field Type Nulls? Comments
Custom_Description_17 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_17 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_18 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_18 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_19 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_19 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_20 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_20 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
TaxJurisdiction nvarchar(100) Yes Description: The Tax Jurisdiction option will
allow the user the select which State/Country
this site belongs too.
Example: California
StoreHoursSundayOpen nvarchar(12) Yes Description: The time the store Opens on
Sunday.
Example: 7:00AM
StoreHoursSundayClose nvarchar(12) Yes Description: The time the Store Closes on
Sunday.
Example: 8:00PM
StoreHoursMondayOpen nvarchar(12) Yes Description: The time the store Opens on
Monday.
Example: 7:00AM
StoreHoursMondayClose nvarchar(12) Yes Description: The time the Store Closes on
Monday.
Example: 11:00PM
StoreHoursTuesdayOpen nvarchar(12) Yes Description: The time the store Opens on
Tuesday.
Example: 7:00AM
StoreHoursTuesdayClose nvarchar(12) Yes Description: The time the Store Closes on
Tuesday.
Example: 11:00PM
StoreHoursWednesdayOpen nvarchar(12) Yes Description: The time the store Opens on
Wednesday.
Example: 7:00AM
StoreHoursWednesdayClose nvarchar(12) Yes Description: The time the Store Closes on
Wednesday.
Example: 11:00PM
StoreHoursThursdayOpen nvarchar(12) Yes Description: The time the store Opens on
Thursday.
Example: 7:00AM
StoreHoursThursdayClose nvarchar(12) Yes Description: The time the Store Closes on
Thursday.
Example: 11:00PM
StoreHoursFridayOpen nvarchar(12) Yes Description: The time the store Opens on
Friday.
Example: 7:00AM

Data Mart ST_Sites 209


Field Type Nulls? Comments
StoreHoursFridayClose nvarchar(12) Yes Description: The time the Store Closes on
Friday.
Example: 1:00AM
StoreHoursSaturdayOpen nvarchar(12) Yes Description: The time the store Opens on
Saturday.
Example: 7:00AM
StoreHoursSaturdayClose nvarchar(12) Yes Description: The time the Store Closes on
Saturday.
Example: 2:00AM
SiteTaxID nvarchar(25) Yes Description: A unique site tax identifier as
configured in Back Office Manager| Site
Properties|Main tab.
Example: 12.345.678/0123-12

Index Name Unique Clustered Fields


PK_ST_Sites Yes Yes SiteNumber

210 ST_Sites Data Mart


ST_SitesAndSiteGroups *

Description: Sites and Site Group information.

Triggered by Export_STSitesAndSiteGroups.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber Int No Description: Site Number (internal)
Example: 1456
SiteID nvarchar (25) No Description: Site ID assigned to site
Example: 1234
SiteName nvarchar (100) No Description: Name assigned to site
Example: Texas BBQ - Irvine
SiteType tinyint No Description: Type of site
1= Settings Group
2=Site
3=Commissary
4=Revenue Center
5=Cost Center
6=Profit Center
7= Reporting Group
Example: 2
SiteUniqueID uniqueidentifier No Description: Global Unique ID for Site –
Used with Configuration Center
Example: 5294ea30-46e2-4874-93cc-
baced0cea1b8

Index Name Unique Clustered Fields


PK_ST_SitesAndSiteGroups Yes Yes SiteNumber

* Table will not contain an index on the replicated database.

Data Mart ST_SitesAndSiteGroups * 211


ST_SiteSubPeriod

Description: Fiscal Calendar Information

Triggered by Export_ProcessSTSiteSubPeriod.sql

Time Frame: This table will export each subperiod (based on the defined fiscal calendar week)
associated with the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
StartDate datetime Yes Description: Start Date
Example: 2007-06-25
EndDate datetime Yes Description: End Date
Example: 2007-07-01
Year smallint Yes Description: Year
Example: 2007
Period smallint Yes Description: Period
Example: 65
Week smallint Yes Description: Week
Example: 1
BusinessCalendarNumber int Yes Description: Business Calendar Number
(internal)
Example: 1000609
BusinessCalendarName nvarchar (100) Yes Description: Business Calendar Name
Example: Fiscal – Radiant Systems

Index Name Unique Clustered Fields


PK_ST_SiteSubPeriod Yes Yes SiteNumber, SubPeriod

212 ST_SiteSubPeriod Data Mart


ST_TasksAndStations *

Description: Contains Employee Scheduling Task and Station configuration information. Triggered by

Export_STTasksAndStations.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls? Comments


TaskOrStationNumber int No Description: Task/Station Number (internal).
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: 122000708
TaskOrStationName nvarchar (100) No Description: Name of the Task or Station.
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: Drive Thru #1
TaskOrStationID nvarchar (25) No Description: Alphanumeric identification
Number of the Task or Station.
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: 4S
TaskOrStationType bit No Description: Identifies the type as a station
or task.
1 = Task
0 = Station
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: 1
ScheduleType bit No Description: Identifies the task as Manager
Entered Hours or Calculated Based on
Weekly Matrix.
1 = Calculated Based on Weekly Matrix
0 = Manager Entered Hours
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: 1

Data Mart ST_TasksAndStations * 213


Field Type Nulls? Comments
DataSource bit No Description: Identifies the data source type
used for the Calculated Based on Weekly
Matrix.
1 = * Sales Total
0 = * Guests Total
Note: Tasks and Stations are defined in Back
Office Manager|Labor|Shift Detail
Maintenance
Example: 1

Index Name Unique Clustered Fields


PK_ST_TasksAndStations Yes Yes TaskOrStationNumber

* Table will not contain an index on the replicated database.

214 ST_TasksAndStations * Data Mart


ST_TheoreticalCostOfGoodsByDate

Description: Cost of Goods by Occasions.

Triggered by Export_ProcessSTTheoreticalCostOfGoodsByDate.sql

Time Frame: This table will include each day individually for the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


RecordID bigint No Description: Internal sql number – do not
use.
Example: 123
SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BusinessDate datetime No Description: Business Date
Example: 2007-03-21
OccasionID int Yes Description: Occasion ID
Example: 890
OccasionName nvarchar(50) Yes Description: Occasion Name
Example: Indian Cultural Festival
RawMaterialItemCatID nvarchar(25) No Description: Raw Material Item Category ID
Example: 4110
GLAccount nvarchar (100) Yes Description: General Ledger Account Number
Example: BIO-123456
TheoryUseValue money No Description: Theoretical Use Value
Example: 7.05

Index Name Unique Clustered Fields


PK_ST_TheoreticalCostOfGoodsByDate Yes No RecordID
IX_ST_TheoreticalCostOfGoodsByDate No Yes SiteNumber, BusinessDate

Data Mart ST_TheoreticalCostOfGoodsByDate 215


ST_TimeClockEditReason_FromView *

Description: This table provides time clock edit reason descriptions. Time clock edit reasons are
defined in Back Office Manager|Labor|Payroll Maintenance|Punch Edit Reasons and are displayed in
the „Reason‟ dropdown (Back Office Switchboard|Payroll|Shifts|Adjust Shifts).

Triggered by Export_STTimeClockEditReason_FromView.sql

Time Frame: This table does not use the export time frame.

Field Type Nulls Comments


?
TimeClockEditReasonNumber int No Description: Time punch edit reason
number (internal).

Example: 1
TimeClockEditReasonDescription nvarchar(50) No Description: Time punch edit reason
description.

Note: A shift edit reason can be selected


from the „Reason‟ dropdown (Back Office
Switchboard|Labor|Payroll|Adjust Shifts).

Example: Early Clock In

Index Name Unique Clustered Fields


PK_ST_TimeClockEditReason_FromView Yes Yes TimeClockEditReasonNumber

* Table will not contain an index on the replicated database.

216 ST_TimeClockEditReason_FromView * Data Mart


ST_TipShareDistribution_RealTimeFeed *

Description: Tip Share allocations by site, by business date, by shift

Triggered by Export_STTipShareDistribution_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls Comments


?
SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business Date associated with
the tip share amount.
Example: 2012-06-21
ShiftNumber int No Description: An internal number that reflects
the Labor „Day Parts‟ as defined in Back
Office Manager|Site Properties|Day Parts tab
at the time the distribution was saved.
Example: 122000567
StartTime datetime No Description: The beginning time of the shift
as defined in Back Office Manager|Site
Properties|Day Parts tab.
Note: If the Breakfast shift = 4:00am –
10:30 am, the start time is 4:00am.
Example: 2012-06-21 04:00:00.000
Uses UTC
EndTime datetime No Description: The ending time of the shift as
defined in Back Office Manager|Site
Properties|Day Parts tab.
Note: If the Breakfast shift = 4:00am –
10:30 am, the end time is 10:30am.
Example: 2012-06-21 10:30:00.000
Uses UTC

Data Mart ST_TipShareDistribution_RealTimeFeed * 217


Field Type Nulls Comments
?
TipShare decimal(19,3) No Description: Total tip share amount entered
for the shift in Back Office Switchboard.
Example: 500.000
DistributionType tinyint Yes Description: Represents the distribution
method selected in Back Office Switchboard|
Inventory| Sales| Reconcile|Tip Share
Distribution UI for the specified shift.
Note: Distribution Methods are:
0 = Distribute tip share amount evenly
based on jobcodes
1 = Distribute tip share amount evenly
based on hours worked
Example: 1
Finalized bit No Description: Indicates whether the tip share
for the day part has been finalized. When a
tip share for a day part is finalized, no
additional changes can be made unless the
day part is „Unfinalized‟.
0 = Not finalized
1 = Finalized
Example: 0
LastModifiedBy int Yes Description: Reflects the user number
(internal) who last saved the tip share for
the day part. If the tip share is „Finalized‟,
this will represent the user who finalized the
day part.
Example: 1442
LastModifiedTime datetime Yes Description: The last time this record was
saved.
Example: 2011-02-24 14:32:15.000
Uses UTC
ContributionAmountManually bit No Description: Indicates whether the tip share
Modified contribution amount for the day part was
manually entered or imported. When a tip
share contribution amount is manually
edited, subsequent Aloha POS imports will
not update the amount for the day part.
Note: The import of the contribution amount
can be performed with Aloha POS. Please
see your NCR Back Office representative for
more information. Otherwise, the tip share is
always manually entered.
0 = Not manually modified
1 = Manually modified
Example: 0
ImportedContributionAmount decimal(19,3) Yes Description: Reflects the tip share
contribution amount, based on the last Aloha
POS import for the business day. If the tip
share contribution amount was manually
modified OR the day part was finalized prior
to changes in the import, this amount may
vary from the value in
ST_TipShareDistribution_RealTimeFeed.Tipshare.
Example: 434.25

218 ST_TipShareDistribution_RealTimeFeed * Data Mart


Index Name Unique Clustered Fields
PK_ST_TipShareDistribution_RealTimeFeed Yes Yes BusinessDate, SiteNumber,
ShiftNumber

* Table will not contain an index on the replicated database.

Data Mart ST_TipShareDistribution_RealTimeFeed * 219


ST_TipShareEmployeeDistribution_RealTimeFeed *

Description: Tip Share allocations by site, by businessdate, by employee, by shift, by job

Triggered by Export_STTipShareEmployeeDistribution_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business Date associated with
the tip share amount.
Example: 2012-06-21
InternalEmployeeNumber int No Description: Employee Number (internal)
Note: Employees are defined in
ST_Employees
Example: 1002863
ShiftNumber int Description: Represents the NCR Back
Office internal number for each Day Part.
Day Parts are defined in Back Office
Manager|Site Properties|Day Parts tab.
Note:
Breakfast - 4:00am – 10:30am
Lunch – 10:30am – 2:00pm
Dinner – 2:00pm – 6:00pm
Late Night – 6:00pm – 4:00am
Example: 1
JobNumber int No Description: Job Number (internal).
Note: Job Names are defined in ST_Jobs
Example: 1000226
Hours decimal(19, 3) Yes Description: Hours worked for the shift.
Note: Tip Share Distribution is Day Part
driven. Hours shown are based on the Day
Parts defined in Back Office Manager|Site
Properties|Day Parts tab.
Example: 1.90
TipShare decimal(19, 3) No Description: Employee‟s allocated gratuity
tip amount.
Example: 120.870

220 ST_TipShareEmployeeDistribution_RealTimeFeed * Data Mart


Index Name Unique Clustered Fields
PK_ST_TipShareEmployeeDistribu Yes Yes BusinessDate, SiteNumber,
tion_RealTimeFeed InternalEmployeeNumber, ShiftNumber,
JobNumber

* Table will not contain an index on the replicated database.

Data Mart ST_TipShareEmployeeDistribution_RealTimeFeed * 221


ST_TipShareJobDistribution_RealTimeFeed *

Description: Tip Share allocations by site, by businessdate, by shift, by jobnumber

Triggered by Export_STTipShareJobDistribution_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Note: Sites are defined in
ST_SitesAndSiteGroups.
Example: 1456
BusinessDate datetime No Description: Business Date associated with
the tip share amount.
Example: 2012-06-21
ShiftNumber int No Description: An internal number that
reflects the Labor „Day Parts‟ as defined in
Back Office Manager|Site Properties|Day
Parts tab at the time the distribution was
saved.
Example: 122000567
JobNumber int No Description: Job number (internal).
Note: Job Names are defined in ST_Jobs
Example: 1000226
DistributionPercent decimal(19, 3) No Description: A percentage of the total tip
share amount to be distributed by site, by
business date, by shift, by job.
Note: The distribution percent by jobcode
must equal a 100%.
Example: 33.330
DistributionAmount decimal(19, 3) No Description: The distribution dollar amount
by site, by business date, by shift, by job.
Example: 500.000

Index Name Unique Clustered Fields


PK_ST_TipShareDistributio Yes Yes BusinessDate, SiteNumber, ShiftNumber,
n_RealTimeFeed JobNumber

* Table will not contain an index on the replicated database.

222 ST_TipShareJobDistribution_RealTimeFeed * Data Mart


ST_UserGroupMemberships_RealTimeFeed *

Description: This table contains all user & user group memberships. Each user or user group will
display all user groups that it is a member of and the distance in the hierarchy from the user group.
This table includes both active and inactive users. Inactive users are only connected to themselves
with a „MemberDistance‟ of 0.

Triggered by Export_STUserGroupMemberships_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: This table will include users for all sites. The site property, „Exclude from Data Mart‟ setting in
Back Office Manager|Site Properties|General 1 tab, is not supported in this Data Mart export. Sites
that have this setting checked in Back Office Manager will be included in this table.

Field Type Nulls? Comments


UserOrGroupNumber int No Description: User or User Group Number
(internal) of each user or group.

Example: 122000503
MemberOfUserOrUserGroup int No Description: User or User Group Number
Number (internal) that the UserOrGroupNumber is a
member of.

Note: Users are defined in


ST_Users_RealTimeFeed
User Groups are defined in
ST_UserGroups_RealTimeFeed

Example: 122000503
MemberDistance int No Description: The distance from the
„UserOrGroupNumber‟ to the
„MemberOfUserOrUserGroupNumber‟ within
the Back Office Manager hierarchy. All users
& groups are linked to themselves with a
distance of 0.

ie: If the hierarchical path to user „Lee


Wharton‟ is: All Users\ Management\ GM\
Lee Wharton
Distance from „Lee Wharton‟ is:
To „All Users‟ = 3
To „Management‟ = 2
To „GM‟ = 1
To „Lee Wharton‟ = 0

Example: 0

Index Name Unique Clustered Fields


PK_ST_UserGroupMemberships Yes Yes UserOrGroupNumber,
_RealTimeFeed MemberOfUserOrUserGroupNumber

* Table will not contain an index on the replicated database.

Data Mart ST_UserGroupMemberships_RealTimeFeed * 223


ST_UserGroups_RealTimeFeed *

Description: This table provides the current list of User Groups in Back Office Manager. If a user
group is not currently assigned to any user groups or does not has any user groups assigned within
Back Office Manager, the group will still be included & indicated as not in use.

Triggered by Export_STUserGroups_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: This table will include users for all sites. The site property, „Exclude from Data Mart‟ setting in
Back Office Manager|Site Properties|General 1 tab, is not supported in this Data Mart export. Sites
that have this setting checked in Back Office Manager will be included in this table.

Field Type Nulls? Comments


UserGroupNumber int No Description: The User Group internal number.

Example: 1000587
UserGroupName nvarchar(100) No Description: The User Group name as defined
in the Back Office Manager| Manage User
Groups|User Group Name.

Example: All Users


NotCurrentlyAssigned bit No Description: Defines if the user group is
currently assigned to any user groups. If a
user group is not assigned to other user
groups, or has no user groups assigned it is
considered not used.

0 = In Use
1 = Not In Use

Example: 1

Index Name Unique Clustered Fields


PK_ST_UserGroups_RealTimeFeed Yes Yes UserGroupNumber

* Table will not contain an index on the replicated database.

224 ST_UserGroups_RealTimeFeed * Data Mart


ST_Users_RealTimeFeed *

Description: This table provides current user information for all active and inactive NCR Back Office
users. Any NCR Back Office users with the access to login to Back Office Manager or the Switchboard
are considered users. A user can be added through the user profile in Back Office Manager or when
the employee profile is created from the Labor Switchboard.

Triggered by Export_STUsers_RealTimeFeed.sql

Time Frame: This table does not use the export time frame.

Note: This table will include users for all sites. The site property, „Exclude from Data Mart‟ setting in
Back Office Manager|Site Properties|General 1 tab, is not supported in this Data Mart export. Sites
that have this setting checked in Back Office Manager will be included in this table.

Field Type Nulls? Comments


UserNumber int No Description: The User Number (internal). This
number is assigned when the employee profile
is created from the Labor Switchboard or when
a new user is added through the user profile in
Back Office Manager. Only users with NCR Back
Office login capabilities will have a number.
Example: 122000503
UserName nvarchar(100) Yes Description: The username as defined in the
Back Office Manager|Manage Users|Username.
Example: jsmith
FirstName nvarchar(50) Yes Description: The user‟s first name as defined in
Back Office Manager|Manage User|First Name.
If a name is not configured, this field will be
blank.
Example: Robert
LastName nvarchar(50) Yes Description: The user‟s last name as defined in
Back Office Manager|Manage User|Last Name.
If a name is not configured, this field will be
blank.
Example: Palmer
AutoCreated bit No Description: Defines if user was auto created
from the Labor Switchboard or manually
created. Auto created users can be activated by
the Site Properties|Employees|Use User Levels
to automatically create & remove users logins
for employees.
0 = Manually Created
1 = Auto Created
Example: 1

Data Mart ST_Users_RealTimeFeed * 225


Field Type Nulls? Comments
DatePasswordChanged datetime Yes Description: The date & time the user‟s
password was last changed.
Example: 2012-09-14 19:51:54.560
Uses Site Local Time
PasswordLastClearedBy int Yes Description: The User Number (internal) who
last cleared the user‟s password.
Example: 100022
Inactive bit No Description: The user‟s active status. If a user‟s
account is „Locked‟ they will still be in an active
status. A user will be set to inactive when
terminated from the Labor Switchboard or
selected as „Inactive‟ from Back Office
Manager|Manage Users|Inactive.
0 = Active
1 = Inactive
Example: 1
InactiveDate datetime Yes Description: If the user is inactive, this is the
date the user was set to be inactive on. The
inactive date can be set for a future date.
ie: If the user was set to be inactive beginning
10/31/2012 on 10/01/2012 then the
InactiveDate would be 2012-10-31.
Example: 2012-10-31

Index Name Unique Clustered Fields


PK_ST_Users_RealTimeFeed Yes Yes UserNumber

* Table will not contain an index on the replicated database.

226 ST_Users_RealTimeFeed * Data Mart


ST_VendorCustomFields

Data Mart ST_VendorCustomFields 227


Description: Data of Vendor‟s Custom Fields

Triggered by Export_ProcessSTVendorCustomFields.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
VendorNumber int No Description: Vendor Number (internal)
Example: 1000005
VendorID nvarchar (50) No Description: Vendor ID
Example: 349
VendorName nvarchar (256) No Description: Vendor Name
Example: Westons Bakery
Custom_Description_1 nvarchar(25) Yes Description: User Defined Description.
Example: Store Colors
Custom_Value_1 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_2 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_2 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_3 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_3 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_4 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_4 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_5 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_5 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_6 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_6 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_7 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_7 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_8 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_8 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_9 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors

228 ST_VendorCustomFields Data Mart


Field Type Nulls? Comments
Custom_Value_9 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_10 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_10 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_11 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_11 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_12 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_12 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_13 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_13 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_14 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_14 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_15 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_15 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_16 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_16 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_17 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_17 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_18 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_18 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_19 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_19 nvarchar(50) Yes Description: User Defined Value
Example: Red and White
Custom_Description_20 nvarchar(25) Yes Description: User Defined Description
Example: Store Colors
Custom_Value_20 nvarchar(50) Yes Description: User Defined Value
Example: Red and White

Index Name Unique Clustered Fields


PK_ST_VendorCustomFields Yes Yes SiteNumber, VendorNumber

Data Mart ST_VendorCustomFields 229


ST_VendorItems

Description: Summary Data of Vendor Items

Triggered by Export_ProcessSTVendorItems.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
VendorNumber int No Description: Vendor Number
Example: 100002
ItemNumber int No Description: Item Number
Example: 1000040
ItemID nvarchar (25) Yes Description: Inventory Item ID
Example: 1450
VendorItemCode nvarchar (50) No Description: Vendor Item Code
Example: 2066
VendorID nvarchar (50) Yes Description: Vendor ID
Example: 26
OrderUnitNumber int No Description: Order Unit Number
Example: 100039
OrderUnitPrice decimal (19, 3) Yes Description: Order Unit Price
Example: 1.33
ReceiveUnitNumber int No Description: Receive Unit Number
Example: 100039
ReceiveUnitPrice decimal (19, 3) Yes Description: Receive Unit Price
Example: 1.33

230 ST_VendorItems Data Mart


Field Type Nulls? Comments
PriceLocked bit No Description: Price Locked
0 = No
1 = Yes
Example: 0
POSequence smallint Yes Description: Purchase Order Sequence
Example: NULL
PrimaryOrderItem bit No Description: Primary Order Item
0 = No
1 = Yes
Example: 1
Exclude bit No Description: Exclude Item
0 = No
1 = Yes
Example: 0
VendorInfoNumber int No Description: Vendor Info Number (internal)
Note: At conversion value will = 0 until a
new export has been completed.
Example: 123456

Index Name Unique Clustered Fields


PK_ST_VendorItems Yes Yes SiteNumber, VendorNumber, ItemNumber,
VendorItemCode, OrderUnitNumber,
VendorInfoNumber

Data Mart ST_VendorItems 231


ST_Vendors

232 ST_Vendors Data Mart


Description: Site Specific Vendor Data

Triggered by Export_ProcessSTVendors.sql

Time Frame: This table does not use the export time frame.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
VendorNumber int No Description: Vendor number (internal)
Example: 123456
VendorID nvarchar (50) No Description: Vendor ID entered by user
Example: 4D56789DD
VendorName nvarchar (256) No Description: Vendor name
Example: Acme Foods
Address1 nvarchar (255) Yes Description: Vendor address – line 1
Example: 123 Main Street
Address2 nvarchar (255) Yes Description: Vendor address – line 2 (Suite
number)
Example: Suite 100
City nvarchar (100) Yes Description: Vendor city
Example: Huntington Beach
State nvarchar (100) Yes Description: Vendor state or province
Example: CA
PostalCode nvarchar (50) Yes Description: Vendor zip code or postal code
Example: 92647
Country nvarchar (50) Yes Description: Vendor country
Example: United States of America
PhoneNumber nvarchar (50) Yes Description: Vendor phone number
Example: 888-555-1212
FaxNumber nvarchar (50) Yes Description: Vendor fax number
Example: 888-555-2323
EmailAddress nvarchar (100) Yes Description: Vendor email address
Example: vendor123@vendor.com
ContactName nvarchar (55) Yes Description: Vendor contact name
Example: Bob Smith
ContactTitle nvarchar (50) Yes Description: Vendor contact title
Example: Purchasing Manager
BackOrderAvailable bit Yes Description: Defines if vendor allows the
creation of back orders
0= No
1= Yes
Example: 0
Notes nvarchar (1000) Yes Description: Free form text field. Comes
from the vendor comments field (Vendor
Maintenance)
Example: Acme Foods will only accept orders
on Wednesdays
CreatedBy int Yes Description: Reflects the user number
(internal) that created the record.

Note: To view the user name associated with


this field, refer to the „UserName‟ field in
table „ST_Users_RealTimeFeed‟

Example: 4

Data Mart ST_Vendors 233


Field Type Nulls? Comments
CreatedTime datetime Yes Description: Creation date and time for
vendor record
Example: 2013-03-11 17:58:24.483
Uses UTC
LastModifiedBy int Yes Description: Last user to modify vendor
record.

Note: To view the user name associated with


this field, refer to the „UserName‟ field in
table „ST_Users_RealTimeFeed‟

Example: 1442
LastModifiedTime datetime Yes Description: Last modified date and time for
vendor record
Example: 2013-03-11 17:58:24.483
Uses UTC
ConvertedFromID nvarchar (25) Yes Description: Converted From ID
Example: 4000-12
CommissarySite int Yes Description: Commissary Site
Example: 14
Exclude bit Yes Description: Exclude
0 = No
1 = Yes
Example: 0
APCode nvarchar (100) Yes Description: Vendor Accounts Payable Code
Example: 449
AccountNumber nvarchar (100) Yes Description: Account Number
Example: 123456
LocalVendor bit No Description: Defines if vendor is a local
vendor. If „Local Vendor‟ = 1, users can add
vendor items at the site level through the
„Item Lookup‟ function.
0= No (not a local vendor)
1= Yes (local vendor)
Example: 1
OrderDay1 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 3

234 ST_Vendors Data Mart


Field Type Nulls? Comments
DeliveryDay1 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 3
OrderDay2 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 4
DeliveryDay2 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 4

Data Mart ST_Vendors 235


Field Type Nulls? Comments
OrderDay3 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 5
DeliveryDay3 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 5
OrderDay4 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 6

236 ST_Vendors Data Mart


Field Type Nulls? Comments
DeliveryDay4 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 6
OrderDay5 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 7
DeliveryDay5 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 7

Data Mart ST_Vendors 237


Field Type Nulls? Comments
OrderDay6 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 1
DeliveryDay6 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 1
OrderDay7 tinyint Yes Description: The 'Order' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Order Day.
These days are sequenced 1-7 to match the
order set in the NCR Back Office UI. If an
Order Day is not selected in NCR Back Office,
the corresponding field in the Data Mart will
be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 2

238 ST_Vendors Data Mart


Field Type Nulls? Comments
DeliveryDay7 tinyint Yes Description: The 'Delivery' day of week as
configured in Vendors|Order/Invoice
Options |Order & Delivery Days|Delivery
Day. These days are sequenced 1-7 to match
the order set in the NCR Back Office UI. If a
Delivery Day is not selected in NCR Back
Office, the corresponding field in the Data
Mart will be blank.
1 = Sunday
2 = Monday
3 = Tuesday
4 = Wednesday
5 = Thursday
6 = Friday
7 = Saturday
Example: 2
TaxID nvarchar(50) Yes Description: Tax ID entered by user
Example: (EIN) AB123456

Index Name Unique Clustered Fields


PK_ST_Vendors Yes Yes SiteNumber, VendorNumber

Data Mart ST_Vendors 239


ST_Vendors_FromView *

Description: This table provides general vendor information. Values in this table are populated when
a new vendor record is created and when an existing vendor record is modified. For example, the
„ST_Vendors_FromView‟ table would capture data if a change were made at the site level in „Vendors‟
(Inventory Switchboard|Purchasing|Vendors).

Triggered by Export_STVendors_FromView.sql

Time Frame: This table does not use the export time frame.

Note: This Data Mart table will include vendors for all sites. The site property „Exclude from Data
Mart‟ setting is not supported in this Data Mart table (Back Office Manager|Site Properties|General 1
tab). Sites that have this setting checked in Back Office Manager will be included in this table.

Field Type Nulls? Comments


VendorNumber int No Description: Vendor number (internal)
Example: 123456
VendorID nvarchar(50) No Description: Vendor ID entered by user
Example: 4D56789DD
VendorName nvarchar(256) No Description: Vendor name
Example: Acme Foods
Address1 nvarchar(255) Yes Description: Vendor address – line 1
Example: 123 Main Street

240 ST_Vendors_FromView * Data Mart


Field Type Nulls? Comments
Address2 nvarchar(255) Yes Description: Vendor address – line 2 (Suite
number)
Example: Suite 100
City nvarchar(100) Yes Description: Vendor city
Example: Huntington Beach
State nvarchar(100) Yes Description: Vendor state or province
Example: CA
PostalCode nvarchar(50) Yes Description: Vendor zip code or postal code
Example: 92647
Country nvarchar(50) Yes Description: Vendor country
Example: United States of America
PhoneNumber nvarchar(50) Yes Description: Vendor phone number
Example: 888-555-1212
FaxNumber nvarchar(50) Yes Description: Vendor fax number
Example: 888-555-2323
EmailAddress nvarchar(100) Yes Description: Vendor email address
Example: vendor123@vendor.com
ContactName nvarchar(55) Yes Description: Vendor contact name
Example: Bob Smith
ContactTitle nvarchar(50) Yes Description: Vendor contact title
Example: Purchasing Manager
BackOrderAvailable bit No Description: Defines if vendor allows the
creation of back orders.
0= No
1= Yes
Example: 0
Notes nvarchar(1000) Yes Description: Free form text field. Comes from
the vendor comments field (Vendor
Maintenance).
Example: Acme Foods will only accept orders on
Wednesdays
CreatedBy int No Description: Reflects the user number (internal)
that created the record.

Note: To view the user name associated with


this field, refer to the „UserName‟ field in table
„ST_Users_RealTimeFeed‟

Example: 4
CreatedTime datetime No Description: Creation date and time for vendor
record.
Example: 2013-03-11 17:58:24.483
Uses Site Local Time
LastModifiedBy int No Description: Last user to modify vendor record.

Note: To view the user name associated with


this field, refer to the „UserName‟ field in table
„ST_Users_RealTimeFeed‟

Example: 1442
LastModifiedTime datetime No Description: Last modified date and time for
vendor record.
Example: 2013-03-11 17:58:24.483
Uses Site Local Time
LocalVendor bit No Description: Defines if vendor is a local vendor.
If „Local Vendor‟ = 1, users can add vendor
items at the site level through the „Item
Lookup‟ function.
0= No (not a local vendor)
1= Yes (local vendor)
Example: 1

Data Mart ST_Vendors_FromView * 241


Field Type Nulls? Comments
UseVendorDescription bit No Description: Defines if Vendor Item Descriptions
will display.
0= No
1= Yes
Example: 0
TaxID nvarchar(50) Yes Description: Tax ID entered by user
Example: (EIN) AB123456

Index Name Unique Clustered Fields


PK_ST_Vendors_FromView Yes Yes VendorNumber

* Table will not contain an index on the replicated database.

242 ST_Vendors_FromView * Data Mart


ST_Waste

Description: Summary Data of Inventory Waste

Triggered by Export_ProcessSTWaste.sql

Time Frame: This table will include each day individually for each subperiod (based on the defined
fiscal calendar week) associated with the selected time frame for this export.

Note: A site may be excluded from the Data Mart export if „Excluded from Data Mart‟ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
SpoilDate datetime No Description: Date Spoilage Occurred
Example: 2007-04-14
TransactionNumber int No Description: Transaction Number (internal)
Example: 2
Type nvarchar (15) No Description: Transaction Type
Example: RAW/MENU/PREP
ItemNumber int No Description: Item Number (internal)
Example: 1000554
ItemUnitNumber int No Description: Item Unit Number (internal)
Example: 6
ItemID nvarchar (40) No Description: Inventory Item ID
Example: 1450
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
Quantity float Yes Description: Quantity Wasted
Example: 3
InventoryUnitPrice float Yes Description: Inventory Unit Price
Example: 36.95
TransactionTime datetime Yes Description: Date and Time of Waste
Example: 2007-07-17 17:23:00.000
Reason nvarchar (255) Yes Description: Reason for the Waste
Example: Expired

Data Mart ST_Waste 243


Index Name Unique Clustered Fields
PK_ST_Waste Yes Yes SiteNumber, SpoilDate, TransactionNumber,
Type, ItemNumber

244 Data Mart


ST_WasteByRawMaterial

Description: This will contain all the waste at the raw material level (not at the menu or prep level). It
is summed up by Site by BusinessDate by ItemNumber.

Time Frame: This table will include each day individually for the selected time frame for this export.

Notes:
1. “Must have a Beginning Inventory” is set to False (unchecked).
2. “Must have an Ending Inventory” is set to False (unchecked).
3. SubPeriod field shows which subperiod the day belongs to.
4. A site may be excluded from the Data Mart export if ‘Excluded from Data Mart’ is checked from
Back Office Manager|Site Properties|General 1 tab.

Field Type Nulls? Comments


SiteNumber int No Description: Site Number (internal)
Example: 1456
StoreID nvarchar (25) No Description: Store ID
Example: 1311
BusinessDate datetime No Description: Business Date of Transaction
Example: 2010-02-15
ItemNumber int No Description: Item Number (internal)
Example: 1000221
StandardUnitName nvarchar (50) No Description: Standard Unit Name
Example: CS=4/5 LB
RawMaterialItemID nvarchar (40) No Description: Raw Material Item ID
Example: 1055
SubPeriod int No Description: Sub Period Number (internal)
Example: 65
Quantity float Yes Description: Quantity wasted
Example: 12
StandardUnitPrice float Yes Description: Standard Unit Price
Example: 22.25

Index Name Unique Clustered Fields


PK_ST_WasteByRawMaterial Yes Yes BusinessDate, SiteNumber, ItemNumber

Data Mart ST_WasteByRawMaterial 245


Notes:

246 Data Mart


Revision History

Version Date Author Description

4.1.0.0 9/14/07 MJF Original Version

4.1.1.0 9/24/07 MJF – Added columns to ST_SiteSubPeriod


– Added the ST_EmpJobRates Table
– Added PrimaryJobName, PrimaryJobRate, PrimaryJobNumber
and Primary JobID to ST_Employees
– Previous ST_EmpJobTrans Table was renamed
ST_EmpJobTransCustom
– New ST_EmpJobTrans Table created to hold real transation
data for Employee Jobs
o The saving of jobs for employee Updates/Borrows
and Transfers has been modified. Originally, all
employee jobs were deleted and then re-instered into
the Public Table. Now, only the changes are applied.

4.1.2.0 10/1/07 MJF – Added the ST_Site Payroll Table


– Added the ST_Calendars Table

4.2 10/24/07 MJF – Modifications to ST_EmpJobTrans Table


o NewPrimaryJob changed to a bit(1)
o NewPayReasonName length changed to nvarchar
(100)
o NewPerformanceRatingName length changed to
nvarchar (100)
– Added notes to ST_EmployeeSalesTips indicating how new
Tip Share Distribution functionality will affect „TipShare‟,
„DeclaredTotalTips‟ and „ChargeTips‟ columns.
– Added the ST_Vendors Table
– Added the ST_PurchaseOrders Table
– Added the ST_PurchaseOrderItems Table
– Changed Data Type of ST_Employees.Zip and
ST_EmpTrans.Zip from varchar(50) to nvarchar (50)
– Added the ST_Sites Table
– Added BusinessCalendarName to ST_SiteSubPeriod
– Added StatusReportingDate to ST_Employees and
ST_EmpTrans
– Added CompanyName to ST_Sites
– ERD Updated
– Images Updated for ST_Employees, ST_EmpTrans,
ST_EmpJobTrans, ST_SiteSubPeriod

Data Mart Revision History 247


Version Date Author Description

4.2 10/29/07 MJF – Corrected the NULL values on columns in the


ST_PurchaseOrders table

4.2 10/31/07 MJF – Corrected ST_PurchaseOrders.CreatedName to be


ST_PurchaseOrders.CreatedByName
– Updated ST_Sites table to correct ReportingCloseDate
– Corrected Length on fields in ST_Sites

4.2 11/2/07 MJF – Corrected ST_ItemUseDaily.RawMaterialItemNum


– Corrected ST_Sites.StateProvince
– Corrected several table index listings

4.3 11/27/07 MJF – Added PrimaryJobPayrollCode to ST_Employees


– Added JobPayrollCode to ST_EmpJobTrans
– Added ContactAddress2 to ST_Employees
– Added ContactCity to ST_Employees
– Added ContactState to ST_Employees
– Added ContactZip to ST_Employees
– Added ContactAddress2 to ST_EmpTrans
– Added ContactCity to ST_EmpTrans
– Added ContactState to ST_EmpTrans
– Added ContactZip to ST_EmpTrans
– Added a new table – ST_EmpTransW4_I9
– Added a new table – ST_EmpW4_I9
– Added a new table – ST_VendorItems
– Added Inactive to ST_RawInfo
– Added InactiveDate to ST_RawInfo
– Added JobID to ST_EmployeePayrollDay
– Added BusinessCalendarName to ST_SitePayroll

4.3 12/3/07 MJF – Changed the Examples for W4StateTaxCode in


ST_EmpW4_I9 and ST_EmpTransW4_I9

5.2 1/18/08 MJF – Added the ST_Accruals table


– Changed ST_InvoiceHeaders.CheckNumber to a length of
255
– ST_Vendors.VendorName lengthened to 256 characters
– ST_Vendors.Address1 lengthened to 255 characters
– ST_Vendors.Address2 lengthened to 255 characters
– ST_Vendors.ContactName lengthened to 55 characters
– Added a LocalVendor bit to the ST_Vendors table
– Changed ST_CostOfGoods.RawMaterialItemID length to 40
– Changed ST_CostOfGoods.RawMaterialItemName length to
250
– Changed ST_FoodCostByItem.RawMaterialItemID length to
40
– Changed ST_InventoryTransfer.ItemID length to 40
– Changed ST_ItemUseDaily.RawMaterialItemID length to 40
– Changed ST_ItemUseDaily.RawMaterialItemName length to
250
– Changed ST_ItemUseVariance.RawMaterialItemID length to
40
– Changed ST_ItemUseVariance.RawMaterialItemName length
to 250
– Changed ST_MIC.MenuItemID length to 40
– Changed ST_MIC.MenuItemName length to 250
– Changed ST_PurchaseOrderItems.ItemID length to 40

248 Revision History Data Mart


Version Date Author Description

– Changed ST_PurchaseOrderItems.ItemName length to 250


– Changed ST_RawInfo.RawMaterialItemID length to 40
– Changed ST_RawInfo.RawMaterialItemName length to 250
– Corrected some inconsistencies with ST_RawInfo
– Changed ST_SalesMix.MenuItemID length to 40
– Changed ST_SalesMix.MenuItemName length to 250
– Changed ST_SalesMixByRawMaterial.RawMaterialItemID
length to 40
– Changed ST_Waste.ItemID length to 40
– Added comments about encryption in the following locations:
o ST_Employees.SSAN
o ST_EmpTrans.SSAN
o ST_Emloyees.SSAN_Original
o ST_EmpW4_I9.DocumentNumberC
o ST_EmpTransW4_I9.DocumentNumberC
– Updated ERD

5.3 2/13/08 MJF – Added InvoiceFinalize field to the ST_InvoiceHeaders table.

5.3 2/20/08 BPG – Added the new table:


o ST_RegisterByRevenueCenterDayPart
– Added 40 fields to ST_Sites:
o Custom_Description_1
o Custom_Description_...
o Custom_Description_20
o Custom_Value_1
o Custom_Value_...
o Custom_Value_20
– Added the following fields to ST_EmpW4_I9
o Lwt_Allowances
o Lwt_Amt
o TaxLocality
– Added the following fields to ST_EmpTransW4_I9
o Lwt_Allowances
o Lwt_Amt
o TaxLocality
– Updated ERD

5.4 3/18/08 BPG – Added TaxJurisdiction to ST_Sites


– Changed name from TaxLocality to TaxLocality1 on
ST_EmpW4I9 & ST_EmpTransW4_I9
– Added the following fields to ST_EmpW4_I9
o TaxLocality2
o TaxLocality3
o TaxLocality4
– Added the following fields to ST_ EmpTransW4_I9
o TaxLocality2
o TaxLocality3
o TaxLocality4
– Added new index to ST_EmpJobTrans & ST_EmpTransW4_I9
and updated indexes with correct field names.
– Updated ERD
– Updated Copyright text per Laura‟s email.
– Update screen shots to show entire table.

Data Mart Revision History 249


Version Date Author Description

5.5 4/23/08 BPG – Added TheoryUse$FIFO to ST_FoodCost


– Added TheoryUseValueFIFO to ST_FoodCostByItem
– Added TaxAmount to ST_InvoiceDetails
– Added table ST_POSSOS
– Added table ST_VendorCustomFields
– Updated ERD
– Change front and last page per Laura‟s email dated
4/7/2008

5.6 5/27/08 BPG – Changed version number from 5.5 to 5.6.


– There were no data changes from 5.5 to 5.6.

5.6 6/25/08 BPG – For DateTime data types, if storing time, indicate where it is
coming from: GMT or Local
Note: The current GMT time (Greenwich Mean Time or
Coordinated Universal Time) is derived from the current local
time and the time zone setting in the operating system of
the computer on which the instance of Microsoft SQL Server
is running.

5.7 6/26/08 BPG – Added the following to ST_InvoiceHeaders


o SFDate
o SFInvoiceNumber
– Updated ERD

5.8 7/28/08 BPG – Added the following to ST_Sites


o StoreHoursSundayOpen
o StoreHoursSundayClose
o StoreHoursMondayOpen
o StoreHoursMondayClose
o StoreHoursTuesdayOpen
o StoreHoursTuesdayClose
o StoreHoursWednesdayOpen
o StoreHoursWednesdayClose
o StoreHoursThursdayOpen
o StoreHoursThursdayClose
o StoreHoursFridayOpen
o StoreHoursFridayClose
o StoreHoursSaturdayOpen
o StoreHoursSaturdayClose
– Added WOTCValidationCode to ST_Employees
– Added WOTCValidationCode to ST_EmpTrans
– Updated ERD
– Updated version number

5.9 9/8/08 BPG – ST_InvoiceHeaders


o Modified LastModifiedDate to Not Nullable
o Added LastModifiedTime to PrimaryKey
o Note: Originated on 5.9. Changes repinned to
version 5.8.29.1 & 5.7.36.10 & 5.6.35.25
– ST_Deposit
o Notes – changed from nvarchar(50) to
nvarchar(100)

250 Revision History Data Mart


Version Date Author Description

– Updated ERD
– Updated version number

5.10 9/15/08 BPG – Updated version number


– Updated ERD
– Updated ST_SitePayroll. Use DateTime instead of
SmallDateTime on the following fields:
o StartDate
o EndDate

5.11 10/08/08 BPG – ST_Deposits


o UserID – changed Description - content now contains
the user name (not Id).
– ST_Employee
o PayrollNumber – corrected description – it contains
Payroll Code.
– Updated version number
– Updated ERD

5.12 11/14/08 BPG – Updated version number


– There were no other changes.

6.1 12/31/08 BPG – Added the following fields to ST_InventoryTransfer:


o BusinessDate
o Accepted
– Added the following fields to ST_Deposits:
o CreatedByName
o PreVerifiedAmount
o OpenAmount
o VerifiedAmount
o VerifiedTime
o VerifiedByName
o ValidatedAmount
o ValidatedTime
o ValidatedByName
– Modified the following fields on ST_Deposits:
o UserId is now of max length 100.
– Added the following fields to ST_EmployeePunches:
o TimeClockEditReason
– Updated ERD
– Updated version number

6.2 2/19/09 BPG – Added new table: ST_ForecastDailySalesAndGuests


– ST_Employees: Changed primary key to be clustered.
– ST_EmpW4_I9: Changed primary key to be clustered.
– ST_Vendors: Changed primary key to be clustered.
– ST_Deposits: Changed primary key to be clustered.
– ST_EmployeePunches: Add clustered index.
– Updated ERD
– Updated version number
– Note: All changes in 6.2, except new table added, were
repinned to version 5.11.40.38.

Data Mart Revision History 251


Version Date Author Description

6.3 3/3/09 BPG – ST_Calendars:


o Added CalendarType to the primary key
o Changed primary key to be clustered.
– ST_CostOfGoods:
o Changed primary key to be clustered.
– ST_SalesMix:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_ScheduleIntervals:
o Changed primary key to be clustered.
– ST_MIC:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_ItemUseDaily:
o Changed primary key to be clustered
– ST_SalesGuestsByInterval:
o Changed primary key to be clustered
– ST_ItemUseVariance:
o Changed primary key to be clustered
– ST_FoodCostByItem:
o Changed primary key to be clustered
– ST_RawInfo:
o Changed primary key to be clustered
– ST_SalesMixByRawMaterial:
o Changed primary key to be clustered
– ST_InvoiceDetails:
o Changed primary key to be clustered
– ST_InvoiceHeaders:
o Changed primary key to be clustered
– ST_Punches:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_EmployeePayrollDay:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_InventoryTransfer:
o Changed primary key to be clustered
– ST_Schedule:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_SchedulePayrollDay:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_ScheduleHours:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_FoodCost:
o Changed primary key to be clustered
– ST_Waste:
o Changed primary key to be clustered
– ST_Register:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_EmpJobRates:
o Changed primary key to be clustered
– ST_EmpJobTransCustom:
o Changed primary key to be clustered
o Changed order of fields in pk

252 Revision History Data Mart


Version Date Author Description

– ST_EmployeeSalesTips:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_EmpTrans:
o Changed primary key to be clustered
– ST_EmpTransW4_I9:
o Changed Index to be clustered
– ST_ForecastDailySalesAndGuests:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_PurchaseOrders:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_PurchaseOrderItems:
o Changed primary key to be clustered
– ST_RegisterByRevenueCenterDayPart:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_ServerCheckout:
o Changed primary key to be clustered
o Changed order of fields in pk
– ST_SitePayroll:
o Changed primary key to be clustered
– ST_Sites:
o Changed primary key to be clustered
– ST_VendorCustomFields:
o Changed primary key to be clustered
– ST_EmpJobTrans:
o Changed primary key to be clustered
o Changed order of fields in pk
o Removed index not used within app
o Changed index to be based on export sp
– Updated ERD
– Updated version number
Note: All changes in 6.3 were repinned to version 5.11.40.38.

6.4 4/21/2009 BPG – ST_InventoryTransfer: Changed InvoiceID length to 100.


Note: This was applied back to version 6.3.1.34.
– Added new table: ST_Occasions
– Added new table: ST_OccasionCategoriesOccasions
– Updated ERD
– Updated version number

6.5 5/21/2009 BPG – Added the following to ST_ InventoryTransfer:


o LastModifiedTime
o LastModifiedByName
– Added new table: ST_PromosComps
– Updated ERD
– Updated version number

6.6 5/26/2009 BPG – ST_InventoryTransfer: Added new field – TransferStatus


– Added new table: ST_TheoreticalCostOfGoodsByDate
– Updated ERD
– Updated version number.

6.7 5/15/2009 BPG – Updated version number.


– There were no other changes.

Data Mart Revision History 253


Version Date Author Description

6.8 9/02/2009 BPG – Updated version number.


– There were no other changes.

6.9 9/28/2009 BPG – Added new field to ST_ItemUseDaily: UnitCostExtended


– Added new table: ST_AdjFoodCostByDay
– Added new table: ST_AdjFoodCostByPeriod
– Added new table: ST_AdjFoodCostByWeek
– Updated ERD
– Updated version number.

6.10 10/27/2009 BPG – Updated version number.


– There were no other changes.

6.11 12/07/2009 BPG – Updated version number.


– There were no other changes.

6.12 01/04/2010 BPG – Updated version number.


– There were no other changes.

7.1 02/05/2010 BPG – Updated version number.


– There were no other changes.

7.2 02/10/2010 BPG – ST_MIC:


o added a new index
o added the following fields:
 SubPeriodStartDate
 SubPeriodEndDate
– ST_ItemUseVariance:
o added a new index
o added the following fields:
 SubPeriodStartDate
 SubPeriodEndDate
– ST_CostOfGoods:
o added a new index
o added the following fields:
 SubPeriodStartDate
 SubPeriodEndDate
– ST_ InvoiceHeaders:
o added the following field:
 InvoiceType
– Added a note to ST_AdjFoodCostByDay,
ST_AdjFoodCostByWeek, and ST_AdjFoodCostByPeriod.
– Updated ERD
– Updated version number

7.3 04/14/2010 BPG – Added new table: ST_WasteByRawMaterial


– Updated ERD
– Updated version number

7.4 07/06/2010 BPG – Modified all screen shots to show the table design from SQL.
– Updated all Type column to match the table design from SQL
for the following types: int, smallint, tinyint, bigint,
datetime, bit, money, float
– Updated version number

254 Revision History Data Mart


Version Date Author Description

7.5 07/12/2010 BPG – Updated version number


– There were no other changes at this time.

7.5.1.24 07/15/2010 BPG – ST_EmpW4_I9


& o added field: A4StateAZAdditionalAmount
7.3.1.56 o Note: added in 7.7 and applied back to this version
– ST_EmpTransW4_I9
o added field: A4StateAZAdditionalAmount
o Note: added in 7.7 and applied back to this version
– Updated ERD

7.6 07/19/2010 BPG – All data types with decimal (10, 3) or (10, 2) are now
decimal (19, 3). Here is a list of tables that have been
modified:
o ST_Accruals
o ST_Deposits
o ST_EmpJobRates
o ST_EmpJobTrans
o ST_EmpJobTransCustom
o ST_EmployeePayrollDay
o ST_EmployeePunches
o ST_Employees
o ST_EmployeeSalesTips
o ST_EmpTransW4_I9
o ST_EmpW4_I9
o ST_FoodCostByItem
o ST_ForecastDailySalesAndGuests
o ST_POSSOS
o ST_PromosComps
o ST_Punches
o ST_PurchaseOrderItems
o ST_PurchaseOrders
o ST_Register
o ST_RegisterByRevenueCenterDayPart
o ST_SalesMixByRawMaterial
o ST_Schedule
o ST_ScheduleHours
o ST_SchedulePayrollDay
o ST_VendorItems
– Updated all screen shots to show new decimal format
– Updated all Type column description to show new decimal
format.
– Updated version number

7.5.1.26 9/28/2010 BPG – ST_InvoiceDetails


& o added field: ItemName
7.3.1.58 o Note: added in 7.7 and applied back to this version

Data Mart Revision History 255


Version Date Author Description

7.7 9/28/2010 BPG – ST_EmpW4_I9


o added field: A4StateAZAdditionalAmount
o Note: This was applied back to 7.5.1.24 & 7.3.1.56
– ST_EmpTransW4_I9
o added field: A4StateAZAdditionalAmount
o Note: This was applied back to 7.5.1.24 & 7.3.1.56
– ST_InvoiceHeaders
o added field: OriginalInvoiceID
– ST_InvoiceDetails
o added field: ItemName
o Note: This was applied back to 7.5.1.26 & 7.3.1.58
– Updated ERD
– Updated version number

7.8 9/28/2010 BPG – Updated version number.


– There were no other changes at this time.

7.9 9/29/2010 BPG – ST_EmpW4_I9


o added field: StateExemptFromWithholding
– ST_EmpTransW4_I9
o added field: StateExemptFromWithholding
– Updated ERD
– Updated version number

7.10 11/03/2010 BPG – Added new table:


ST_InvoiceDetailsSupplierReferenceNumber
– Added new table: ST_FoodCostByItemContractDaily
– Added new table: ST_SitesAndSiteGroups *
– Added new table: ST_CalendarSubperiods *
– Added new table: ST_Items *
– Added new table: ST_ItemCategories *
– Added new table: ST_ItemUnitsOfMeasure *
– Added new table: ST_PurchaseOrderItems_RealTimeFeed *
– Added new table: ST_PurchaseOrders_RealTimeFeed *
– Updated ERD
– Updated version number

7.11 12/15/2010 BPG – ST_PurchaseOrderItems_RealTimeFeed


o added field: RawMaterialItemNumber
o added field: StandardQuantityOrdered
– Updated ERD
– Updated version number

7.12 01/10/2011 BPG – Updated version number


– There were no other changes at this time.

8.1 01/14/2011 BPG – Within each table description, identify the time frame
method used when exporting.
– Updated version number

8.1.1.4 03/02/2011 BPG – W4StateExemptNbr definition for A4 has changed for 2011.
Note: added in 8.2 and applied back to this version

256 Revision History Data Mart


Version Date Author Description

8.2 03/02/2011 BPG – ST_EmpW4_I9


o W4StateExemptNbr: A4 definition changed for 2011
– ST_EmpTransW4_I9
o W4StateExemptNbr: A4 definition changed for 2011
Note: A4 definition change was applied back to 8.1.1.4

– Updated version number

8.4 04/12/2011 BPG – Added new table:


o ST_ScheduleRecommendedByDayLaborMatrices*
– Updated ERD
– Updated version number

8.5 05/12/2011 BPG – ST_PurchaseOrderItems_RealTimeFeed*


o added field: SuggestedOrderQuantity
o added field: SuggestedOrderUnitNumber
– Updated ERD
– Updated version number

7.8.1.78 07/06/2011 BPG – ST_VendorItems


& o added field: VendorInfoNumber
8.5.1.10 o and added it to the primary key
o Note: added in 8.6 and applied back to this version

8.6 07/09/2011 BPG – ST_Vendors


o added field: OrderDay1
o added field: DeliveryDay1
o added field: OrderDay2
o added field: DeliveryDay3
o added field: OrderDay3
o added field: DeliveryDay3
o added field: OrderDay4
o added field: DeliveryDay4
o added field: OrderDay5
o added field: DeliveryDay5
o added field: OrderDay6
o added field: DeliveryDay6
o added field: OrderDay7
o added field: DeliveryDay7
– Added new table:
o ST_SafeCount*
– ST_VendorItems
o added field: VendorInfoNumber
o and added it to the primary key
o Note: This was applied back to 7.8.1.78 & 8.5.1.10
– Updated ERD
– Updated version number

8.7 07/11/2011 BPG – ST_CostOfGoods


o added field: EndingInventoryUnitCost
– Updated ERD
– Updated version number

8.7 07/22/2011 BPG – Updated table image for ST_Vendors

Data Mart Revision History 257


Version Date Author Description

8.8 08/31/2011 BPG – ST_Schedule


o added field: StationNumber
– Added new table:
o ST_TasksAndStations*
– ST_Employees
o added field: CustomField1
o added field: CustomField2
o added field: CustomField3
o added field: CustomField4
o added field: CustomField5
o added field: AlohaLiquorCertificationNumber
o added field: AlohaLiquorCertifcationExpirationDate
– ST_PurchaseOrderItems_RealTimeFeed*
o added field: SplitCaseIndicator
– Updated ERD
– Updated version number

8.9 09/07/2011 BPG – Added new table: ST_Jobs*


– Added new table: ST_EmployeePayrollDayPenaltyHours*
– Updated ERD
– Updated version number

8.9 10/07/2011 BPG – Fixed typo

8.10 10/19/2011 BPG – Updated version number


– There were no other changes at this time.

8.10.1.67 01/19/2012 BPG – ST_EmployeePayrollDayPenaltyHours*


o fixed employee field name
o Note: changed in 12.1 and applied back to this
version

8.11 12/12/2011 BPG – Added new table: ST_Allocations


– Added new table: ST_Budgets
– Added new table: ST_DataDefinitionConfiguration *
– Updated ERD
– Updated version number

8.12 01/18/2012 BPG – ST_ScheduleRecommendedByDayLaborMatrices


o RecommendedStaffingMethod: update description
– Updated version number

12.1 01/19/2012 BPG – ST_InvoiceDetails


o added field: Notes
– ST_EmployeePayrollDayPenaltyHours*
o fixed employee field name
o Note: This was applied back to 8.10.1.67
– Added new table: ST_EmployeePunchesRealTime *
– Updated ERD
– Updated version number

258 Revision History Data Mart


Version Date Author Description

12.1 02/02/2012 BPG – ST_Allocations


o fixed field name for: data definition number
– ST_Budgets
o fixed field name for: data definition number
– Updated ERD with new field name

12.2 03/09/2012 BPG – Updated Time Frame description for tables that will sum all
days for the subperiods.
– Updated version number

8.10.1.87 03/21/2012 MRH – ST_ScheduleRecommendedByDayLaborMatrices


o RecommendedStaffingMethod: update description
o Note: changed in 8.12 and applied back to this
version

12.3 03/21/2012 MRH – Updated version number


– There were no other changes at this time.

12.3.1.35 06/18/2012 BPG – ST_PurchaseOrders_RealTimeFeed *


o added field: BusinessDate
o added field: OrderTotal
o added field: OpenOrder
o added field: SentTime
o added field: ConfirmSent
o added field: FromOrderByVendor
o added field: CreatedBy
o added field: LastModifiedBy
o added field: LastModifiedTime
o Note: changed in 12.5 and applied back to this
version

12.3.249.0 6/18/2012 BPG – ST_PurchaseOrders_RealTimeFeed *


o added field: PurchaseOrderID
o Note: changed in 12.7 and applied back to this
version

12.4 6/18/2012 BPG – Added new table: ST_ALOHAGNDBREAKINFO*


– ST_AdjFoodCostByPeriod
o Update description for “Must have an Ending
Inventory”
– Updated ERD
– Update version number

12.5 6/19/2012 BPG – Added new tables:


o ST_TipShareDistribution_RealTimeFeed *
o ST_TipShareEmployeeDistribution_RealTimeFeed *
o ST_TipShareJobDistribution_RealTimeFeed *
– ST_PurchaseOrders_RealTimeFeed *
o added field: BusinessDate
o added field: OrderTotal
o added field: OpenOrder
o added field: SentTime
o added field: ConfirmSent
o added field: FromOrderByVendor

Data Mart Revision History 259


Version Date Author Description

o added field: CreatedBy


o added field: LastModifiedBy
o added field: LastModifiedTime
o Note: This was applied back to 12.3.1.35
– ST_Vendors
o added field: TaxID
– ST_InvoiceHeader
o updated the Time Frame description
– ST_InvoiceDetails
o updated the Time Frame description
– ST_ InvoiceDetailsSupplierReferenceNumber
o updated the Time Frame description
– Updated ERD
– Updated version number

12.6 6/22/2012 BPG – ST_TipShareDistribution_RealTimeFeed *


o added field: Finalized
o added field: LastModifiedBy
o added field: LastModifiedTime
o added field: ContributionAmountManuallyModified
o added field: ImportedContributionAmount
– Added new tables:
o ST_AlohaSalesMixTransactions_RealTimeFeed *
o ST_EmployeeSalesTips_RealTimeFeed *
– Updated ERD
– Updated version number

12.6.203.0 7/25/2012 BPG – ST_PurchaseOrders_RealTimeFeed *


o added field: PurchaseOrderID
o Note: changed in 12.7 and applied back to this
version

12.7 7/25/2012 BPG – ST_InventoryTransfer


o updated the LastModifiedTime description
– ST_PurchaseOrders_RealTimeFeed *
o added field: PurchaseOrderID
o Note: This was applied back to 12.6.203.0 &
12.3.249.0
– Updated version number

12.8 8/29/2012 BPG – Updated cover and ending page.


– Updated version number
– There were no other changes at this time.

12.9 09/07/2012 BPG – Added a note to all exports that has a site number: a site
may be excluded from the Data Mart export if the „Excluded
from Data Mart‟ is checked in the System Mgmt application.
Most data mart exports that have a site number has been
modifed to use this new table to exclude sites from being
exported.
– Added new table:
o ST_CustomFPZ *
– Updated ERD
– Updated version number

260 Revision History Data Mart


Version Date Author Description

12.10 10/17/2012 BPG – ST_Employees


o added field: EmailAddress
o added field: TipConsent
o Note: TipConsent was applied back to 12.3.364.0 &
12.9.278.0
– ST_Jobs *
o added field: JobID
o Note: This was applied back to 12.9.276.0.
– ST_Items *
o added field: ItemCategoryNumber
o added field: MenuItemCategoryNumber
o added field: PrepItemCategoryNumber
o added field: ModifierItemCategoryNumber
– Added new tables:
o ST_EmployeeStatusBySite_RealTimeFeed *
– Added new tables:
o ST_InventoryLists_RealTimeFeed *
o ST_ItemConversionFactors_RealTimeFeed *
o ST_SiteInventoryListMembers_RealTimeFeed *
o Note: These were applied back to 12.9.222.0.
– Updated ERD
– Updated version number
– Updated document for branding changes (cover, header,
footer, etc).

12.3.301.0 01/07/2013 BPG – ST_FoodCostByItem


o Export changed to use theoretical amount for ending
inventory for an item that does not have a current
inventory, if property is set to checked.
o Update the table description note #1 to indicate
theoretical values can be exported, if property is set.
o Note: Changed in 12.11 and applied back to this
version.

12.9.222.0 01/07/2013 BPG – Added new tables:


o ST_InventoryLists_RealTimeFeed *
o ST_ItemConversionFactors_RealTimeFeed *
o ST_SiteInventoryListMembers_RealTimeFeed *
o Note: Added in 12.10 and applied back to this
version.
12.11 01/08/2013 BPG – ST_FoodCostByItem
o Export changed to use theoretical amount for ending
inventory for an item that does not have a current
inventory, if property is set to checked.
o Update the table description note #1 to indicate
theoretical values can be exported, if property is set.
o Note: This was applied back to 12.3.301.0
– ST_EmpTrans
o added field: TipConsent
– Added new tables:
o ST_SiteAndSiteGroupMemberships_RealTimeFeed *
o ST_Users_RealTimeFeed *
o ST_UserGroups_RealTimeFeed *
o ST_UserGroupMemberships_RealTimeFeed *

Data Mart Revision History 261


Version Date Author Description

– Updated description for ST_ItemUseDaily.ItemCost field.


– Updated description for Beginning & Ending Inventory to
include the word “checked” and “unchecked”.
– Updated datetime example to be consistent.
– Updated ERD
– Updated version number

12.12 01/10/2013 BPG – Added new tables:


o ST_AdjFoodCostByPartialPeriod
– Updated some descriptions to the following tables to match
ST_AdjFoodCostByPartialPeriod:
o ST_AdjFoodCostByDay
o ST_AdjFoodCostByPeriod
o ST_AdjFoodCostByWeek
– Updated ERD
– Updated version number

13.1 01/11/2013 BPG – Updated version number


– There were no other changes at this time.

13.2 02/05/2013 BPG – Updated version number


– There were no other changes at this time.

12.9.276.0 03/28/2013 BPG – ST_Jobs *


o added field: JobID
o Note: Added in 12.10 and applied back to this
version.

13.3 03/28/2013 BPG – Updated document for branding changes


– Updated ERD for branding changes
– Updated version number

12.3.363.0 04/18/2013 BPG – ST_Employees


& o added field: RehireDate
12.9.277.0 o Note: Added in 13.4 and applied back to this version.
– ST_EmpTrans
o added field: RehireDate
o Note: Added in 13.4 and applied back to this version.

12.3.364.0 04/18/2013 BPG – ST_Employees


& o added field: TipConsent
12.9.278.0 o Note: Added in 12.10 and applied back to this
version.

13.4 04/18/2013 BPG – ST_Employees


o added field: RehireDate
o Note: This was applied back to 12.3.363.0 &
12.9.277.0
– ST_EmpTrans
o added field: RehireDate
o Note: This was applied back to 12.3.363.0 &
12.9.277.0
– ST_ EmployeeSalesTips_RealTimeFeed *
o added field: AlohaAutomaticGratuityforAllCashTenders

262 Revision History Data Mart


Version Date Author Description

o added field: AlohaAutomaticGratuityforAllOtherTenders


o added field: AlohaAutomaticGratuityforAllNonCashTenders
– Added new tables:
o ST_ItemRecipeIngredients_FromView *
o ST_ItemRecipeKitchenTools_FromView *
o ST_ItemRecipePlateAndStores_FromView *
o ST_ItemRecipePrepStations_FromView *
o ST_ItemRecipes_FromView *
o ST_KitchenTool_FromView *
o ST_PlateStore_FromView *
o ST_PrepStations_FromView *
o ST_RecipeVersionBySite_FromView *
o ST_ForecastSalesGuestsByInterval_FromView *
o ST_ExcludedItemsBySite_FromView *
o ST_InactiveItemsBySite_FromView *
o ST_ItemPropertiesBySite_FromView *
o ST_Vendors_FromView * Note: This was applied
back to 12.9.307.0
– Updated ERD
– Updated version number

12.3.375.0 4/29/2013 BPG – ST_EmpW4_I9


& o added field: DocumentTitleA1
12.9.288.0 o added field: IssuingAuthorityA1
o added field: DocumentTitleA2
o added field: IssuingAuthorityA2
o added field: DocumentNumberA2
o added field: ExpirationDateA2
o added field: AdmissionNumber
o added field: ForeignPassportNumber
o added field: CountryOfIssuance
o added field: ExpirationDateNA
o Note: Added in 13.5 and applied back to this version.
– ST_EmpTransW4_I9
o added field: DocumentTitleA1
o added field: IssuingAuthorityA1
o added field: DocumentTitleA2
o added field: IssuingAuthorityA2
o added field: DocumentNumberA2
o added field: ExpirationDateA2
o added field: AdmissionNumber
o added field: ForeignPassportNumber
o added field: CountryOfIssuance
o added field: ExpirationDateNA
o Note: Added in 13.5 and applied back to this version.

13.5 4/29/2013 BPG – ST_Employees


o added field: I9ValidationCode
o added field: BackgroundCheckCode
– ST_EmpTrans
o added field: I9ValidationCode
o added field: BackgroundCheckCode
– ST_EmpW4_I9
o added field: DocumentTitleA1
o added field: IssuingAuthorityA1
o added field: DocumentTitleA2
o added field: IssuingAuthorityA2
o added field: DocumentNumberA2

Data Mart Revision History 263


Version Date Author Description

o added field: ExpirationDateA2


o added field: AdmissionNumber
o added field: ForeignPassportNumber
o added field: CountryOfIssuance
o added field: ExpirationDateNA
o Note: These were applied back to 12.3.375.0 &
12.9.288.0
– ST_EmpTransW4_I9
o added field: DocumentTitleA1
o added field: IssuingAuthorityA1
o added field: DocumentTitleA2
o added field: IssuingAuthorityA2
o added field: DocumentNumberA2
o added field: ExpirationDateA2
o added field: AdmissionNumber
o added field: ForeignPassportNumber
o added field: CountryOfIssuance
o added field: ExpirationDateNA
o Note: These were applied back to 12.3. 375.0 &
12.9.288.0
– Added new tables:
o ST_SiteEmployeeRateChangeAcknowledgments_FromView*
– Updated ERD
– Updated version number

12.9.307.0 6/12/2013 BPG – Added new table:


o ST_Vendors_FromView *
o Note: Added in 13.4 and applied back to this version.

13.6 6/12/2013 BPG – ST_RawInfo


o Export changed to use theoretical amount for ending
inventory for an item that does not have a current
inventory, if property is set to checked.
o Update the table description and notes to indicate
theoretical values can be exported, if property is set.
– Added new tables:
o ST_EmployeeClockPunchHistory_FromView *
o ST_TimeClockEditReason_FromView *
o ST_PayrollStatus_FromView * PDR 18605
o ST_PayrollStatusDetail_FromView * PDR 18605
– Change wording from „GMT‟ (Greenwich Mean Time) to „UTC‟
(Universal Time Coordinated).
– Updated ERD
– Updated version number

13.7 7/15/2013 BPG – ST_InvoiceHeaders


o added field: InvoiceExternalID
– ST_Sites
o added field: SiteTaxID
– Updated ERD
– Updated version number

264 Revision History Data Mart

You might also like