Brewer Information Specifications

advertisement
POLICIES & PROCEDURES
Brewer Information Specification
TBS
Effective Date: December 8, 2015
Table of Contents
Revision History........................................................................................................................................ 3
Introduction ............................................................................................................................................... 4
Purpose ...................................................................................................................................................... 4
Background ............................................................................................................................................... 4
Conventions............................................................................................................................................... 4
Number Representation............................................................................................................... 4
Syntactical Notation .................................................................................................................... 4
File Naming Conventions............................................................................................................ 5
Definitions, Acronyms, and Abbreviations ............................................................................................... 6
Data File Descriptions and Data Formats.................................................................................................. 7
General Information .................................................................................................................... 7
Header and Footer Layouts........................................................................................... 7
Reference Files............................................................................................................................ 8
Store Data File (STORyyyymmdd.DAT) ..................................................................... 8
Package Data File (PAKGyyyymmdd.DAT)................................................................ 9
Brand Data File (BRNDyyyymmdd.DAT ) .................................................................. 10
Brand Pack Data File (BRPKyyyymmdd.DAT ) .......................................................... 11
Reason Code Data File (RESNyyyymmdd.DAT)......................................................... 12
Transaction Code Data File (TRNSyyyymmdd.DAT) ................................................. 14
Customer Data File (CUSTyyyymmdd.DAT) .............................................................. 15
Price Data File (PRICyyyymmdd.DAT)....................................................................... 17
Charge Type Data File (CTYPyyyymmdd.DAT) ......................................................... 18
Transaction Files........................................................................................................... 19
General Information...................................................................................................... 19
Customer Sales/Returns (CSHDyyyymmdd.DAT)....................................................... 20
Brewer Shipment (BSHDyyyymmdd.DAT) ................................................................. 21
Full Goods Return to Brewer Header (FRHDyyyymmdd.DAT) .................................. 22
Transfer Header (TRHDyyyymmdd.DAT)................................................................... 23
Full Goods Detail (FGDTyyyymmdd.DAT)................................................................. 24
Empties shipment Header File (MTHDyyyymmdd.DAT)............................................ 25
Empties shipment Detail File (MTDTyyyymmdd.DAT).............................................. 26
Industry Files ................................................................................................................ 27
Store Industry Summary (STINyyyymmdd.DAT)........................................................ 28
Customer Sales Industry Summary (CSINyyyymmdd.DAT) ....................................... 29
Frequency of Delivery............................................................................................................................... 30
Special Notes ............................................................................................................................................. 30
Distribution Media and Transfer ............................................................................................................... 30
Appendix I - Transaction Codes................................................................................................................ 31
Appendix II - Size Code ............................................................................................................................ 32
Appendix III - Type of Beer...................................................................................................................... 33
Appendix IV - Transfer Charge Type ....................................................................................................... 34
Appendix V - Customer Type ................................................................................................................... 35
Appendix VI - Store Types........................................................................................................................ 36
Appendix VII - POS Transaction Types.................................................................................................... 37
Appendix VIII - Electronic Receipt of Data.............................................................................................. 38
PASSWORD ............................................................................................................................................. 38
Data Recovery Requests............................................................................................................................ 38
2
Revision History
REVISION DESCRIPTION
---------------------------------------------------------------------1.0
Initial Version, 28-Nov-93
1.2
Changes to store hours codes March 26, 1996
affects store data file:
- elements
tour-hr-code
summ-hr-code
basic-hr-code
store hours data file:
- elements
hr-code
* char (5)
“
“
char (5)
Update Distribution Media & Transfer section to include references to BBS procedures
New appendix VIII - Electronic Receipt of Data
1.3
Fixed page numbering;
Removed the following from Transaction Files, General Information:
Any record received with the same transaction date should be considered as an adjustment to
previously received records with the same date. Use key fields to adjust accordingly. (Key
fields are identified in the file layout description)
1.4
Change all dates to yyyymmdd format. July 26, 1999
1.5
1.6
Add Brand Pack Data file;
Change qty data type from N to S. September 12, 2001
Removed Store Hours Master File
FGDT reason code incorrectly referenced Appendix V. Entry removed April 24 2002.
1.7
Reason codes – page 13 updated to reflect new codes – lgs June 26, 2006
3
Introduction
Purpose
The purpose of this document is to provide a description of information available to all brewers who supply product
to TBS. The data is to be provided electronically and this document will cover file descriptions, data formats
frequency of delivery, delivery means and media.
Background
The reader should be familiar with:
x
Distribution terminology of the Ontario beer industry.
Conventions
The following is a summary of conventions observed throughout this document:
Number Representation
Each ASCII record within each file is separated by a “carriage-return” (0x0d) followed by a line-feed (0x0a). This
description uses a notation to describe each field contained within the file. Below is a brief description of the
notation. Note that a number within parenthesis denotes the total number of character positions that will be occupied
by the field data.
N(n)
S(n)
C(n)
D(8)
DT(12)
T(4)
M(n)
F(n)
Unsigned numeric (0-9,<sp>), of length n
Signed numeric (0-9,-,+,<sp>), of length n
Alphanumeric (mix of letters and/or numbers); length n
Represents a date of the form YYYYMMDD
Represents a date and time of the form YYYYMMDDHHMM
Represents time of the form HHMM
Signed money value represented in cents, length n
Signed float value of length n, with two implied decimal places
Any number in this document not preceded by a special symbol is a decimal number.
Syntactical Notation
Syntactical notations are used to describe the format of command statements and other user-specifiable items such
as system resource names. The following conventions apply to these syntax definitions:
<> Angle brackets enclose a description of information, which must be provided, as opposed to a literal character
string. For example, "<file__name>" indicates that the user must enter the name of a file, not the string
"file__name".
.... An ellipsis appearing inside a pair of square brackets indicates that the element(s) enclosed within the brackets
may optionally be repeated. Any blanks or other separators inside the square brackets must also be repeated. For
example, "[,<modifier>...]" represents optional modifiers which may be repeated; each must be preceded by a
comma.
In character strings, upper case is used for letters which are significant (required), while lower case is used for
optional letters. For example, "DEFault" specifies a string that the user may enter as "default", "defaul", "defau",
"defa", or "def". Note that this convention indicates the characters that are required, not the case in which the
characters must appear.
4
File Naming Conventions
The data files are comprised of three types: reference files, transaction files and industry files. The reference files
contain information required to decode the information found in the transaction files and the industry files. Each
file is named using the following convention:
AAAAyyyymmdd.xxx
A
yyyy
mm
dd
xxx
- Alphabetic character in the range [A .. Z]
-numeric 4 digit year
- Numeric characters in the range [01 .. 12 ] denoting the calendar month
ie. 01 = January, 02 = February, 03 = March etc...
- Numeric characters in the range [0 .. 9] denoting the period end day
- Denotes the 3 character DOS file extension. Current file extensions used are:
DAT - Indicates a data file
ERR - Indicates an errata file
DOC - Indicates a Microsoft Word document
HLP - Indicates a help file
ZIP - Indicates a PKZIP compressed file
NOTE: The date extension on all files will be the period ending date for this set of data.
ie. STOR19971124.DAT would be the store reference file for November 1997 for period ending the 24th.
5
Definitions, Acronyms, and Abbreviations
BRI
ASCII
GST
PST
POS
Brand Code
Customer #
Reference Customer Type Code
Reference Customer #
Trans Id
Reason Code
Store
Size Code
TBS
Qty
Content Amount
Total Deposit Value
Brewers Retail Inc.
American Standard Code for Information Interchange
Goods and Services Tax
Provincial Sales Tax
Point-of-Sale
This code identifies a unique brewer/brand combination
Identifies a TBS customer. ‘custype_code’+’customer_no’ form a unique
external TBS client
Legal values are the same as those for ‘custype_code’, but are usually
confined to just ‘G’. A reference customer is an intermediate client who
may supervise or invoice the “real” customer. Such is often the case with
the LCBO and Northern Agencies. Here, the LCBO is the “reference”
customer.
This number identifies a reference customer. ‘ref_custype_code’ +
‘ref_customer_no’ form a unique external “reference” customer.
An artifical number used for joining to detail information in the detail file.
This is a one-to-many relationship. Note that it is not the case that
there exists a record in the detail file for every record in the header or viceversa.
Describes an associated reason for the transaction.
The Beer Store store/depot identification number
Identifies a package size.
The Beer Store
Transaction quantity in units. (Note that this quantity can be a negative number.
Dollar value of the product less the value of the container
Dollar value of the container
6
Data File Descriptions and Data Formats
The information to be delivered consists of a series of ASCII files containing transaction, reference and industry
information. Transaction and industry data files differ from reference files in the sense that their contents will vary
greatly between one period end and the next. Reference files are fairly static in nature and as such will remain
basically the same from one period end to the next.
General Information
x
x
x
All brewer data files are available on a period end basis.
All transaction and industry data files produced by TBS are in ASCII format with fixed length records.
If a field is not applicable or not available, a null value is entered for that field.
Header and Footer Layouts
File headers and footers are found only in transaction and industry files. Header and footer fields will be
separated by a pipe (|). The header and footer records consist of the following layouts.
File Header Layout
FIELD
SIZE
Header sentinel
Number of lines *
Number of words *
Number of characters *
Footer sentinel
Date of last balance
Filename
5 bytes
9 bytes
9 bytes
9 bytes
5 bytes
8 bytes
30 bytes
FORMAT/
VALUE
#####
Numeric
Numeric
Numeric
#!#!#
yyyymmdd
Alphanumeric
File Footer Layout
FIELD
Footer sentinel
SIZE
5 bytes
* Excluding header and footer information
7
VALUE
#!#!#
Reference Files
Store Data File (STORyyyymmdd.DAT)
This file contains the description of all stores/depots.
Field Name
store
store_typ
Field Type
N(4)
C(3)
Field Description
The Beer Store store/depot identification number
Describes the type of store/depot
BRW Brewery Retail
WHR Wholesale / retail
RWD Retail with deliveries
RET
Retail
DEP
Depot
open_dt
close_dt
loc_name
unit_no
street_no
street_name
box
plaza
city
postal_code
prov
stat
network_office
grp_office
self_serve
drive_thru
mini
handi
pall_ss
tour_hr_code
summ_hr_code
basic_hr_code
area_code
exchange
suffix
ext
mgr_name
D(8)
D(8)
C(30)
C(5)
N(6)
C(30)
C(30)
C(30)
C(30)
C(10)
C(2)
C(1)
N(4)
N(4)
C(1)
C(1)
C(1)
C(1)
C(1)
C(5)
C(5)
C(5)
C(3)
C(3)
C(4)
C(4)
C(30)
Opening date - yyyymmdd
Closing date - yyyymmdd
Name of the store location
Unit number
Street address number
Street name
Post Office box
Name of the plaza/mall
Name of city
Canadian postal code
Provincial abbreviation
Store status - Active (A), Inactive (I)
Operations office
Group office number (TBS internal use only)
Self serve (Y/N)
Drive through service (Y/N)
Mini store (limited access, stock selection and capacity) (Y/N)
Access facilities for handicap persons
Palletized self serve (Y/N)
Tourist hours code
Summer hours code
Basic hours code
Telephone area code
First three digits of the local number
Last four digits of the local number
PBX Extension
Name of store manager
8
Package Data File (PAKGyyyymmdd.DAT)
Describes all industry packages.
size_code
s_name
l_name
no_contr
volume
intro_dt
remove_dt
contr_typ
N(3)
C(8)
C(30)
N(3)
F(10)
D(8)
D(8)
C(1)
sub_contr_typ
C(2)
non_rtl_sz
stat
ind_pool_sz
mt_brewer_ret
C(1)
C(1)
C(1)
C(1)
Unique package size code
Abbreviated name for the package size
Full name for the package size
Number of containers within a package / size
Total product volume of package in millilitres
Date introduced to market – yyyymmdd
Date removed from market - yyyymmdd
Container type:
B
Bottle
K
Keg
S
Sphere
P
Pump
C
Can
O
Other
X
Carton request
Further description of the container type
NA
Not applicable
QB
Quart bottle
SB
Standard bottle
SC
Standard can
TC
Tall can
UB
Universal bottle
UC
Universal can
SK
Standard Keg
PK
Private Keg
NK
Northern Keg (Golden Gate)
Non retail size (Y/N)
Status (Active=A, Inactive=I)
Industry pool size (Y/N)
Valid for empty returns (Y/N)
9
Brand Data File (BRNDyyyymmdd.DAT )
Describes all industry brands.
brand_code
s_name
l_name
brewer_code
producer
stat
beer_type
N(4)
C(8)
C(30)
C(3)
C(3)
C(1)
C(3)
alc_prct
cal_cnt
seas_bd
intro_dt
remove_dt
mix_repack
F(10)
N(10)
C(1)
D(8)
D(8)
C(1)
Unique industry brand code specifying both brewer and brand
Abbreviated brand name
Full brand name
Identifies the brewer
Producer of product
Status (Active=A, Inactive=I)
Beer type
ALE
Ale
MIX
Mixed case
STT
Stout
LIT
Light
LAG
Lager
MLT Malt
Percentage of alcohol
Number of calories per 100ml
Seasonal brand (Y/N)
Date introduced to the market – yyyymmdd
Date removed from the market - yyyymmdd
Mixed repacks allowed (Y/N)
10
Brand Pack Data File (BRPKyyyymmdd.DAT )
Describes all industry brand packs.
brand_code
size_code
stat
ship_stat
cspc_no
upc_code
C(4)
C(3)
C(1)
C(1)
C(6)
C(20)
Unique industry brand code specifying both brewer and brand
Size Code
Status(Active=A, Inactive=I)
Ship Status(Shipable=S, Nonshipable=N)
CSPC number
UPC code
11
Reason Code Data File (RESNyyyymmdd.DAT)
Provides a unique list of codes associated with specific transactions.
trans_code
reason_code
s_reason
l_reason
Stat
N(3)
N(3)
C(20)
C(60)
C(1)
Transaction code
Reason code
Abbreviated descriptive text of the reason
Full descriptive text of the reason
Status (Active=A, Inactive=I)
**The following table shows the current list of transaction / reason combinations
trans_code
reason_code
Description
14
1
2
3
4
5
6
12
19
0
1
2
3
4
5
6
12
19
0
9
0
9
8
9
0
1
2
3
4
5
6
7
8
9
10
1
2
3
4
5
6
7
Old code
Stock Leaker
Taste
Foreign material
Return to stock
Chipped neck
Leaker Package
Overstock
No reason given
Old code
Stock Leaker
Taste
Foreign material
Return to stock
Chipped neck
Leaker Package
Overstock
No reason given
Short Shipment
No reason given
Short Shipment
Other
Short Shipment
No charge transfer
Fluctuation in sale
Brewer shipment error
Repack cartons unavailable
Excess stock
Scheduled transfers
Brewer request
Unable to unload truck
Damage replacement
Order change-unproc.
Old code
Old Code
Brewer Damages
Customer complaint
Brewer recall – Quality
Fresh Code for Redistribution
SOP Return
Unsaleable Damaged Packaging
17
50
55
60
70
71
12
97
171
171
173
8
9
11
1
2
3
4
6
8
12
19
0
1
1
2
3
4
5
7
Customer Return
Licensee old codes
LCBO Old Code
Old Code
Stock Leaker
Taste
Foreign Material
Chipped Neck
Other
Leaker Package
Overstock
RP Return
RP Return to Vendor
Stolen
Damaged in Store
Damaged in Transit
Customer Return
Other
Insurable Loss (Mf & Store Only) Sbs Transcode 175
13
Transaction Code Data File (TRNSyyyymmdd.DAT)
Provides a list of all possible TBS transactions.
Trans_code
Trans_name
Stat
N(3)
C(16)
C(1)
Uniquely identifies a type of transaction
Descriptive text
Status (Active=A, Inactive=I)
14
Customer Data File (CUSTyyyymmdd.DAT)
A List of TBS customers.
Custype_code
C(1)
Customer type code (see fgcust.dat)
0
Undefined
A
Agency (not southern)
E
Embassy
G
Government (LCBO)
L
Licensee
P
Public
S
Southern agency
Customer_no
C(10)
Cust_name1
Cust_name2
est_typ
C(78)
C(78)
C(3)
lic_typ
C(2)
Customer number identifies a TBS customer.
‘custype_code’+’customer_no’ form a unique external TBS client
Customer name
Customer name (more text)
Establishment type
AFA
Armed forces - active
AFR
Armed forces - reserve
AIR
Aircraft
BPB
brew pub
CAN Canteen
CLF
Club (fraternal)
CLS
Club (social)
CLV
Club (veteran)
CNV Convention centre
EL
Entertainment lounge
HTL
Hotel
PAT
Patio
REC
Recreational
RES
Restaurant
RWC Railway car
STD
Stadium
TAV
Tavern
THR
Theatre
License type
DL
Delivery license
MB
Mini bar license
SL
Sale license
TB
Temporary transfer - trustee in bankruptcy
TF
Temporary transfer - franchiser in possession
TL
Temporary transfer - landlord in possession
TM
Temporary transfer - Mortgagee in possession
TR
Temporary transfer - Receiver
unit_no
Street_no
Street_name
Box
Plaza
City
Postal_code
Prov
country
C(5)
N(6)
C(30)
C(30)
C(30)
C(30)
C(10)
C(2)
C(3)
Unit number
Street address number
Street name
P.O. Box
Name of the plaza/mall
Name of city
Canadian postal code
Provincial abbreviation
Country abbreviation
15
fin_stat
C(1)
intro_dt
lcbo_admin
loc_name
bri_supply_store
alt_bri_supply_store
D(8)
C(5)
C(30)
N(4)
N(4)
Financial status
A
Active
I
Inactive
P
Pending approval
D
Pending deletion
Date customer was introduced - yyyymmdd
Store/depot that normally supplies product to customer
Alternate Store/depot that can supply product to customer
16
Price Data File (PRICyyyymmdd.DAT)
Lists date effective prices for all stores, brands, packages.
date
brand_code
D(8)
N(4)
size_code
N(3)
price_list
N(3)
stat
content_price
pst
gst
tot_dep_value
cart_dep_value
C(1)
M(10)
M(10)
M(10)
M(10)
M(10)
Effective date of price - yyyymmdd
This code identifies an unique brewer/brand combination. Descriptive text
is available in the file brand.dat
Identifies a package size. Descriptive text is available in the file
package.dat
Identifies a type of customer related to these prices.
20
Home consumer
35
Embassy
60
license
97
TBS use
Status (A=Active, I=Inactive)
Consumer price of contents (volume only)
Provincial sales tax
Goods and services tax
Total dollar value of the bottles (or liquid container)
Dollar value of the carton (ie. the case containing the bottles)
17
Charge Type Data File (CTYPyyyymmdd.DAT)
Provides a list of all possible TBS transfer charge types.
chg_typ
desc
C(1)
C(30)
Uniquely identifies a type of transfer charge. see appendix IV
Descriptive text (shown above)
18
Transaction Files
General Information
Each record on a file has a transaction date. The transaction date determines whether a particular
transaction should be included or excluded in a balancing period.
Price information is stored in three fields: content, deposit and GST.
"Content" does not include GST.
Pricing fields are available for sale and customer return transactions only. Any other transactions will have
null values in the pricing fields.
The transaction id field (trans_id) is used to link a single record from a header file to one or multiple
records in a detail file.
Transaction codes 254,255 represent a transaction to be deleted.
On the occurrence of TC=255, the trans_id is the key to previous entries, and the transaction should be
considered as deleted.
Each header file will be delivered as a separate file, however all detail information for Customer
Sales/Returns, Brewer Shipment, Full Goods Return to Brewer, Transfers and the other miscellaneous
inventory transactions will be merged and delivered in one file, FGDTyyyymmdd.DAT.
Note that certain transactions do not have transaction headers.
Period ending transaction information is available in a series of data files, according to the type of
transaction, as follows:
x
CSHDyyyymmdd.DAT (Customer Sales/Returns Transaction Header)
x
BSHDyyyymmdd.DAT (Brewer Shipment Transaction Header)
x
BRHDyyyymmdd.DAT (Brewer Return Transaction Header)
x
TRHDyyyymmdd.DAT (Transfer Transaction Header)
x
FGDTyyyymmdd.DAT (Full Good Detail)
x
MTHDyyyymmdd.DAT (Empty Shipment Transaction Header)
x
MTDTyyyymmdd.DAT (Empty Shipment Details)
19
Customer Sales/Returns (CSHDyyyymmdd.DAT)
CRHDyyyymmdd.DAT (Customer Sales/Returns Transaction Header) Includes general
information for each customer sale or return transaction. Transaction headers are available for
Sales and Returns to/from Licensee, LCBO/Agency and Southern Agency customers.
The customer sales/returns files contain daily detailed licensee orders (TC = 60), licensee returns
(14),Southern agency sales (TC = 55), SA returns (TC= 17), LCBO sales (TC=50), LCBO returns
(TC = 13) and deleted transactions (TC=255).
The customer sales /returns data resides in two files: header and detail files. See full goods detail
file layout.
The following is the layout of the header file:
Trans_id (key)
Trans_code (key)
Date (key)
Store (key)
Customer_no (key)
Cust-type (key)
Order_no (key)
Sub_customer_no
No_of_orders
Supplying_store
Delv_date
Transaction id - link to detail
Transaction code
Transaction date yyyymmdd
Store
Customer number
Customer type code
Order number
Sub customer number
Number of orders
Supplying store number
Delivery date yyyymmdd
20
N(10)
N(3)
C(8)
N(4)
C(9)
C (1)
C(10)
C(2)
N(3)
N(4)
C(8)
Brewer Shipment (BSHDyyyymmdd.DAT)
Includes general information for each brewer shipment transaction.
Daily detailed brewer shipments are included by date, by store, by brand and by size.
Brewer shipment data resides in two files: header and detail files. See full goods detail file layout.
The following is the layout of the header file:
Trans_id (key)
Trans_code (key)
Store (key)
Date (key)
Brewer_code (key)
Delv_date
Order_no (key)
Add_on
Order_canc
Order_adj
Authorization
Transaction id - link to detail
Transaction code
Reporting TBS store
Transaction date yyyymmdd
Brewer_code
Delivery date, format yyyymmdd
Order number
Add_on (values: Y,N,null)
Order cancellation flag (Y,N,null)
Adjustment on previous order (Y,N,null)
Authorization Number
21
N(10)
N(3)
N(4)
C(8)
C(2)
C(8)
C(10)
C(1)
C(1)
C(1)
C(9)
Full Goods Return to Brewer Header (FRHDyyyymmdd.DAT)
Includes general information for each return to brewer transaction.
Daily full goods returned to brewer details are included by date, by store , by brand and by size.
Full goods return to brewer data resides in two files: header and detail files. See full goods detail
file layout.
The following is the layout of the header file:
Trans_id (key)
Trans_code (key)
Date (key)
Store (key)
Brewer_code (key)
Plant_code
Pall_no
Authorization
Waybill
Transaction id - link to detail
Transaction code
Transaction date yyyymmdd
TBS store#
Brewer_code
Plant code
Number of pallets
Authorization number
Waybill number
22
N(10)
N(3)
C(8)
N(4)
C(2)
N(3)
N(5)
C(9)
C(10)
Transfer Header (TRHDyyyymmdd.DAT)
Includes general information for each transfer transaction.
Daily detailed full goods transfers are included by date, by store, by brand and by size.
Transfer data resides in two files: header and detail files. See full goods detail file layout.
The following is the layout of the header file:
Trans_id (key)
Trans_code (key)
Date (key)
Store (key)
To_from_store
Ref_no
Pallet_no
Chg_typ
Trans_amt
Km
GST
Del_date
Transaction id - link to detail
Transaction code
Transaction date yyyymmdd
Reporting TBS store
To/from store number
Reference number (order #)
No. of pallet
Charge type(appendix IV)
Transfer amount
Mileage in km
GST on transfer charge
Delivery date yyyymmdd
23
N(10)
N(3)
C(8)
N(4)
N(4)
C(10)
N(5)
C(1)
F(18)
N(5)
F(18)
C(8)
Full Goods Detail (FGDTyyyymmdd.DAT)
The Full Good Detail contains details of the following header files, as well as other inventory transactions
that do not have headers:
y
y
y
y
Customer Sales/Returns (CSHDyyyymmdd.DAT)
Brewer Shipment (BSHDyyyymmdd.DAT)
Full Goods Return to Brewer (BRHDyyyymmdd.DAT)
Transfer (TRHDyyyymmdd.DAT)
The layout of the full good detail file:
Trans_id (key)
Brand_code (key)
Size_code (key)
Reason_code
Trans_code (key)
Date (key)
Store
Brewer_code
Qty
Content_amt
Tot_dep_amt
GST
Transaction id - link to header
Brand_code
Size_code (see Appendix II)
Reason code, available only for TC = 13, 14,17,70,71)
Transaction code
Transaction date yyyymmdd
TBS store number
Brewer code
Quantity
Dollar amount of content
Dollar amount of deposit
Dollar amount of GST
24
N(10)
C(4)
C(3)
N(3)
N(3)
C(8)
N(4)
C(2)
S(10)
F(18)
F(18)
F(18)
Empties shipment Header File (MTHDyyyymmdd.DAT)
Includes general information for empty shipment to the brewer.
Trans_id (key)
Trans_code (key)
Date (key)
Store_no (key)
Brewer_code
Plant_code
Waybill_no (key)
Ship_adj
Pall_no
Pall_surplus
Tot_amt
Authorization
Transaction id - link to detail
Transaction code
Transaction date yyyymmdd
TBS store#
Brewer_code
Plant code
Waybill number
Shipment adjustment flag (S or A)
Number of pallets
Number of surplus pallet
Value of waybill
Authorization Number
25
N(10)
N(3)
C(8)
N(4)
C(2)
N(3)
C(10)
C(1)
N(5)
N(5)
F(18)
C(9)
Empties shipment Detail File (MTDTyyyymmdd.DAT)
Daily detailed empties shipment to brewer are included by date, by store.
following transaction codes:
82 - Empty waybill or Adjustment (non pooled sizes)
85 - SAK waybill or Adjustment (pooled sizes)
Trans_id (key)
Pmb_code (key)
Size_code (key)
Qty
Trans_Code
date
Store
Brewer_code
Plant_code
Trans_amt
Transaction link number to Header
PMB code
Size code
Quantity
Transaction code
Transaction date yyyymmdd
Store number
Brewer code
Plant code
Value of this item
26
N(10)
C(3)
C(3)
S(10)
N(3)
C(8)
N(4)
C(2)
N(3)
F(18)
It includes the
Industry Files
Balanced industry summary data is available on a weekly and split week basis. The data files, according to the type
of transaction, are as follows.
1.
Store Industry Summary
Each store, transaction code, size and beer type for each sales transaction code (See appendices
I,II,III) includes a summary of the industry quantity
For all non-sales transaction codes (See appendix I) includes a summary of the industry quantity for each
store, transaction code and size.
2.
Customer Industry Sales/Returns Summary
Includes a summary of the industry for each store, customer, size and beer type for Licensee,
LCBO/Agency and Southern Agency sales and returns.
27
Store Industry Summary (STINyyyymmdd.DAT)
Includes a summary of the industry quantity for each store, transaction code, size and beer type
for all transaction codes in appendix I except TC=255.
Note:
Beer-type will appear as "null" for transactions other than sales.
The layout of the file:
Field Name
Store (key)
Trans_code (key)
Size_code(key)
Beer Type (key)
Qty
Description
Store number
Transaction Type
Size Code
Beer type
Quantity
Data type
N(4)
N(3)
C(3)
C(3)
S(10)
28
Customer Sales Industry Summary (CSINyyyymmdd.DAT)
Industry summary of each customer sales and returns. This information is available by date, by
store, by customer,by size and by beer type.
The following transaction codes are included:
licensee sales (TC = 60),licensee returns (14),Southern agency sales (TC = 55), SA returns (TC=
17), LCBO sales (TC=50) and LCBO returns (TC = 13).
Note:
Beer-type will appear as "null" for transactions other than sales.
The following is the layout of the file:
Trans_code (key)
Store (key)
Cust_type (key)
Customer_no (key)
Size_code (key)
Beer_type (key)
Qty
Transaction code
TBS store#
Customer type code
Licensee, LCBO, or S.Agency #
Size code
Beer Type
Quantity
29
N(3)
N(4)
C (1)
C(9)
C(3)
C(3)
S(10)
Frequency of Delivery
A full set of files will be provided for each TBS period. A TBS period-end is defined to be close of business on
Sunday or close of business on the last day of the month, whichever comes first. All dates specified within a
delivered set of files fall within the same TBS period. The information will be made available four business days
following the end of a TBS period if the period-end is not the end of the month. Otherwise, the information will be
made available five days following the end of the month. These are both “worst-case” delivery lag time estimates.
Special Notes
It should be noted that the information presented here includes no references to year-to-date, or month-to-date
summary information. This is to say that “running totals” will not be maintained and transmitted weekly. Daily
closing inventory positions are not given.
Distribution Media and Transfer
Files will be provided to you via Internet email. It will be the brewers responsibility to set up and pay for an
Internet account with a local Internet Service Provider. The mailbox associated with this account must be large
enough to accommodate weekly file sizes of greater than 2 megabytes. Files sizes vary by brewer.
30
Appendix I - Transaction Codes
Trans Code
Trans Description
Trans Type
9
11
12
13
14
15
16
17
18
20
22
25
27
35
40
50
55
60
65
70
71
72
73
74
75
76
77
90
99
254
255
Brewery shipment
Transfer in
Special Occasion Permit (SOP) return
LCBO/agency return
Licensee return
Repack in
Adjustment in
Souther Agency return
Brewery Shipment Adjustment
Counter sale
Variance full goods TIPS
Brewery Retail sale
Home Consumption (Counter) return
Embassy sale
SOP sale
LCBO/Agency sale
Southern Agency sale
Licensee sale
Brewery Retail Licensee sale
Transfer out
Full goods return to brewer
Repack out
Full Goods Damage, TBS
Full Goods Damage, Brewer
Insurable Loss
Authorized disposal
Full goods write off (Display)
Relay sale
Closing Inventory
Deleted Transaction
Deleted Transaction
Inventory Receipts
Inventory Receipts
Customer Return
Customer Return
Customer Return
Inventory Receipts
Inventory Receipts
Customer Return
Inventory Receipts
Sale
Inventory Issues
Sale
Customer Return
Sale
Sale
Sale
Sale
Sale
Sale
Inventory Issues
Inventory Issues
Inventory Issues
Inventory Issues
Inventory Issues
Inventory Issues
Inventory Issues
Inventory Issues
Sale
Closing Inventory
31
Appendix II - Size Code
Size-code
001
002
005
006
008
009
010
019
020
022
023
026
027
028
030
031
033
038
039
041
042
046
047
048
049
052
Short Name
6SB
12SB
24SB
1TSB
500B
24UB
PSB
1SB
1LB
750C
1TUC
12QB
58PK
30PK
6UC
12UC
24UC
6TC
750B
24TC
12TC
PMP
56NK
19NS
20SK
630B
Long Name
Standard Bottles - 341ml - 6
Standard Bottles - 341ml - 12
Standard Bottles - 341ml - 24
Standard Bottles - 341ml - one trip
Bottle
- 500 ml - 1
Universal Bottle - 355 ml - 24
Bottle - 341 ml - Plastic Carton
Bottles
- Cooler Special
1 Litre Bottle
Cans
- 750 ml - 1
Universal Can
- 355 ml - one trip
Quart Bottle
- 625 ml - 12
Private Keg
- 58.6 Litre
Private Keg
- 30.0
Universal Can
- 355 ml - 6
Universal Can
- 355 ml - 12
Universal Can
- 355 ml - 24
Tall Can - 473 ml - 6
750 ml Bottle
-1
Tall Can - 473 ml - 24
Tall Can - 473 ml - 12
19 Litre Pump
Northern Keg
- 56.8 Litre - Golden Gate
Northern Sphere - 19 Litre
Southern Keg
- 20 Litre
630 ml Bottle - 1
32
Appendix III - Type of Beer
Type of Beer
ALE
LAG
LIT
MIX
MLT
STT
Description
Ale
Lager
Light
Mixed Case
Malt
Stout/Porter
33
Appendix IV - Transfer Charge Type
Transfer Charge Type
Description
0
A
B
C
No charge
Two Way
TBS/Brewer One Way
Hired truck
34
Appendix V - Customer Type
Customer Type Code
Description
0
A
E
G
L
P
S
Undefined
Agency (not southern)
Embassy
Government (LCBO)
Licensee
Public
Southern agency
35
Appendix VI - Store Types
Store Code
Description
BRW
WHR
RWD
RET
DEP
Brewery Retail
Wholesale/Retail
Retail with Deliveries
Retail
Depot
36
Appendix VII - POS Transaction Types
POS Trans Type
Description
0
1
2
3
4
5
6
7
Undefined
Over the counter (pickup)
Pre-payment
Pre-paid (pickup)
Pre-paid (delivery)
Delivered normal (delivery)
Return
Drive through (pickup)
37
Appendix VIII - Electronic Receipt of Data
Distribution Media and Transfer
Files will be provided to you via Internet email. It will be the brewers responsibility to set up and pay for an
Internet account with a local Internet Service Provider. The mailbox associated with this account must be large
enough to accommodate weekly file sizes of greater than 2 megabytes. Files sizes vary by brewer.
Brewers data files will be emailed to an Internet email address to be provided by the brewer. Each brewer will
receive two files each week:
BREWERNAME.EXE
This file will contain the nine brewer reference files as well as the seven transaction files for each brewer. The file
is a self-extracting, password encrypted, pkzip file. We encrypt files to protect the privacy of your data being sent
over the Internet.
To extract files, enter: BREWERNAME.EXE –PASSWORD=yourpassword
This command will extract each brewers nine reference files and seven transaction files.
IND_SUM.EXE
This file will contain two industry files which are also compressed, but not encrypted. These files are not encrypted
because the information is provided to all brewers and hence are specific to a particular brewers.
To extract files, enter: IND_SUM.EXE
PASSWORD
We ask that each brewer choose and frequently change the password to be used to extract their
files. A few tips on choosing a password:
1.
2.
3.
4.
5.
Passwords should be a minimum of six and a maximum of 30 characters.
Avoid passwords that would appear in a dictionary.
Avoid obvious passwords such as your brewer name, a brand name, brewer number, etc.
Any valid ASCII character can be used. (Any key on a computer keyboard).
Keep in mind that passwords are case sensitive. Kitten, kitten, or KITTEN, would all be
unique passwords.
Data Recovery Requests
The Beer Store maintains eight weeks of data online and will provide re-transmissions of data
during that period free of charge. Requests for retransmission of data beyond that eight-week
period will require retrieval from tape backup and will be charged on a time and materials basis
including a $100/hour labour charge. While The Beer Store endeavors to provide complete and
accurate data, it is incumbent on the receiving brewer to identify any data problems to TBS
within an eight-week period. Requests for data corrections beyond the eight-week period will be
charged on a time and material basis including a $100/hour labour charge.
38
Download