|Foreign Key Table
|A universally unique identifier (UUID) for the Transaction. This may be assembled from alternate key members.
|The unique identifier for the WORKSTATION, typically the serial number.
|A unique retailer assigned identifier for an RetailStore, DistributionCenter or AdministrationCenter
|The calendar date of the BusinessDay.
|SequenceNumber is a counter used to uniquely identify individual transaction within a transaction set identified by: BusinessUnit (store or channel location), BusinessDayDate (day this sale/return is attributed to for accounting purposes), WorkstationID (terminal, register where transaction was entered), OperatorID (the cashier or sales associate entering the transaction) and sequence number which exists only to distinguish each transaction. With this in mind, the sequence number is a counter and IS RESET to 1 when a BusinessUnit, BusinessDayDate, WorkstationID, OperatorID control break is encountered.
|A code to denote the type of Transtion. e.g. RetailTransaction, ControlTransaction, TenderControlTrnsaction, etc...
|The time and date a transaction is initiated.
|The time and date stamp a transaction is completed.
|A flag denoting that this entire transaction has been cancelled before it was completed at the POS.
|A flag denoting that this entire transaction has been voided (and reversed) after it was completed at the POS via a PostVoidTransaction.
|A flag denoting that this entire transaction has been suspended before it was completed at the POS.
|A flag to signify whether the workstation is in training mode.
|A code that indiates the online/offline state of how a transaction and its components was entered at a work station. Valid values include 'OL' online, 'SA' Standalone (offline), and 'BO' both online and offline. BO means that some line items (e.g. payment authorizations) were processed online while some (e.g. item scanning/key entry) were done offline.
|A unique retailer assigned identifier for an accounting budget, that owns merchandise and is used to track the financial performance of the retail enterprise.
|Token ID for each METAR Weather condition row. Typically METAR reports are made once per hour per ICAO location. Only locations tied to retailer Sites will have weather conditions reported. Also, retailers may choose to limit the forecasts to once or twice a day. The granularity of weather tracking for retail sales analysis and reporting is less rigorous thant for flight safety and control.
|Token identifier for each instance of a METAR weather forecast entity. Forecast periods, unlike METARWeatherCondition (which are done on an hourly basis or more in volatile weather situations) these cover peirods of multiple days.
|A boolean indicator that if set to YES tells the retailer that this ControlTransaction was used to override a standard operating procedure and set a state/status to a desired value. Examples of forced control transactions include: FORCED_SIGNOFF FORCED_SIGNON FORCED_ENDOFDAY_CLOSE etc. The ForceFlag, when set to YES indicates an exception condition that should be reviewed by store operations and internal auditing.
|A unique, token identifier for a Logo instance.
|A retailer defined and managed reference to a BATCH used to group transactions for processing purposes. This is an analog for POSLOG6 Batch ID. It is an owned attribute and does not reference another entity.
|A unique token ID for a Session instance.